Eliminate missleading warnings concerning [min, max]-asserts

[Bernhard Bachmann]

model testInit
  Real x(start=1.0, fixed=true);
  parameter Real b(min=0.5,fixed=false);
initial equation
  b = 2;
equation
  der(x) = b;
end testInit;

A warning is issued, although the parameter b is initialized in the
corresponding [min, max]-interval. Seems that the check is performed
too early! Similar warnings are issued throughout most of the
Modelica.Fluid.Examples.

[Lennart Ochel]

I fixed it and will commit the changes as soon as I have stable internet access.

[Adrian Pop]

You posted the message using snail-mail? :) Ah, you said "stable", my bad.

[Lennart Ochel]

I removed wrong asserts for secondary parameters with r24471.
I don't close this ticket by now, since there are some asserts missing in certain cases.

[Lennart Ochel]

There are still two issues with parameter assertions.

The following example shows that there are no assertions for "constant" parameters:

model testInit2
  parameter Real p(min=0.5, max=2) = p2;
  parameter Real p2(min=0.5, max=2) = 0;
end testInit2;

There is only an assertion for p.

assert            | warning | Variable p out of [min, max] interval: p >= 0.5 and p <= 2.0 has value: 0

In addition to that, there are also missing assertions for dependent parameters. The following example will not show any assert.

model testInit3
  parameter Real p(min=0.5, max=2, fixed=false);
initial equation
  p = 0;
end testInit3;

[Lennart Ochel]

I solved the first issue (testInit2) with r24474.

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