Export of FMU 2.0 fails if parameters are used as start values

[rfranke@…]

Using the current nightly build 1.9.1+dev (r21649), the following model

model DIC_start "Double Integrator Continuous-time"
  parameter Real p = 1 "gain for input";
  parameter Real y1_start = 1 "start value for first state";
  parameter Real y2_start = 0 "start value for second state";
  input Real u(start = -2);
  output Real y1, y2;
  Real x1(start = y1_start);
  Real x2(start = y2_start);
initial equation
  y1 = y1_start;
  y2 = y2_start;
equation
  der(x1) = p * u;
  der(x2) = x1;
  y1 = x1;
  y2 = x2;
end DIC_start;

shall be exported as FMU 2.0 with the omc commands:

    loadFile("DIC_start.mo");
    translateModelFMU(DIC_start, version="2.0");

This produces the following error message:

[CodegenUtil.tpl:152:14-152:14:writable] Error: Template error: initial value of unknown type: y1_start
[CodegenUtil.tpl:152:14-152:14:writable] Error: Template error: initial value of unknown type: y2_start

The same model can be simulated using OMEdit.

[Adeel Asghar]

The error is fixed in r22419. But in order to properly fix this problem we need to handle the InitialUnknowns inside ModelStructure of modelDescription.xml.

Willi I have created required data structures for InitialUnknowns in r22421. Makesure you populate them with proper data when you are fixing #2764.

[Martin Sjölund]

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

[Martin Sjölund]

Milestone changed to 1.9.3 since 1.9.2 was released.

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

[Lennart Ochel]

It is fixed for the v1.16.0 and a test is added to the testsuite.