noEvent doesnt work correctly

[fixed-term.Sven.Baetzing@…]

Hello,

I am using the nightly build from 20.11.2013.
In one of my models I am using the noEvent-operator, but it doesnt work correctly.

I reduced the model to a minimal and the error still apear.

The variable should be either s or Smax, depending on the movement of s.
If s should be smaller then a previous smax should hold on the maximum.

Find the model attached

[Per Östlund]

Could you please elaborate on what isn't working correctly? max/min does not generate events, so noEvent has no effect in your example and is optimized away by the compiler. The only issues I can see are modelling related, i.e. you have the equation system

Smax = max(Smax, s)
flange_a.s = s
flange_b.s = Smax

which can't be solved since there are four variables involved but only three equations. Likewise you get the equation system

flange_a.f = 0.0  // Automatically generated since flange_a.f is an unconnected flow variable.
flange_a.f = 0.0  // Added by you.

So the equation system generated by the model is simply unsolvable. To make it possible to simulate the model you'd need to remove the flange_a.f equation and add another equation to the first equation system.

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

[Per Östlund]

Closed due to lack of feedback.