simulation fails with measureTime=true

[Volker Waurich]

Hi,

While running the msl 3.2 with measureTime=true some models are
failing when simulated. Its always because an assert was called, like in Modelica.Blocks.Examples.Filter :

assert | assert | Referenced 'CriticalDamping.cr' that was not declared as <variable>

Here the variable CriticalDamping.cr is actually an array and possibly occurs just as CriticalDamping[i] in the variables and therefore cannot be found.

This assert comes from
SimulationRuntime/c/simulation/simulation_info_xml.c line 72.

The if where the measureTime flag is checked is in
startNonInteractiveSimulation i.e. in simulation_runtime.cpp line 519.

[Martin Sjölund]

This was fixed in r18448 so simulations do not crash by adding a <variable> tag as a copy of the first element but with a different name.

The debugger will probably not work satisfactory. It seems that the SIMVAR does not contain information about the length of the array. So I cannot expand it to point to all its children or vice-versa. So you would have no logical link between cr and cr[1] among the dependencies (so if an equation depends on cr[1], and this is defined only in an equation assigning to cr, you would not find this in the debugger).

Can Lennart or Willi add the required functionality (dimensions of the array) to the SimCode?

[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.