Opened 9 years ago

Closed 8 years ago

#4207 closed defect (fixed)

Frontend evaluation of parameters

Reported by: Lennart Ochel Owned by: Martin Sjölund
Priority: high Milestone: 1.12.0
Component: Frontend Version:
Keywords: Cc: Patrick Täuber

Description

The following brief example contains a parameter size_ which is evaluated within the frontend for some reason. Is that intended or just a bug?

  model Test
    parameter Integer size = 5;
    final parameter Integer size_ = size;
    parameter MyExternalObj MyExtObj=MyExternalObj(size_);
    parameter Real p1 = readFromMyExternalObj(MyExtObj, 1);
    Real p2 = readFromMyExternalObj(MyExtObj, 2);
    Real p3 = readFromMyExternalObj(MyExtObj, 3);
    Real p4 = readFromMyExternalObj(MyExtObj, 4);
    Real p5 = readFromMyExternalObj(MyExtObj, 5);
  end Test;

Attachments (1)

TestMyExternalObj.mo​ (2.3 KB ) - added by Lennart Ochel 9 years ago.

Download all attachments as: .zip

Change History (5)

by Lennart Ochel, 9 years ago

Attachment: TestMyExternalObj.mo​ added

comment:1 by Martin Sjölund, 9 years ago

I think it has to do with some bugs for external objects in the backend before you started sorting them correctly: we considered the inputs structural parameters.

comment:2 by Lennart Ochel, 9 years ago

I see! That should be reverted once #3446 is fixed.

comment:3 by Lennart Ochel, 9 years ago

Type: discussion → defect

#3446 is fixed now, which means that there is no need to consider the inputs as structural parameters anymore.

comment:4 by Martin Sjölund, 8 years ago

Milestone: Future → 1.12.0
Resolution: → fixed
Status: new → closed

This was fixed some time ago

Note: See TracTickets for help on using tickets.