non-linear solver issues after ExpressionSimplify changes

[Volker Waurich]

Hi,

after the removal of the cases:
(a+b)c1 => ac1+bc1
and
(a-b)c1 => a/c1-b/c1
in ExpressionSimplify.mo made in rev [17956]

the msl32-model Modelica.Fluid.Examples.BranchingDynamicPipes.mos fails.

The output I get under Windows is:

Error: Simulation did not produce a result-file
Errors: Simulation execution failed for model: Modelica.Fluid.Examples.BranchingDynamicPipes
stdout            | warning | | While solving non-linear system an assert was called.
|                 | |       | | The non-linear solver tries to solve the problem that could take some time.
|                 | |       | | It could help to provide better start-values for the iteration variables.
|                 | |       | | For more information simulate with -lv LOG_NLS
The arguments x_min and x_max to OneNonLinearEquation.solve(..)
do not bracket the root of the single non-linear equation:
  x_min  = 190
  x_max  = 647
  y_zero = -731619
  fa = f(x_min) - y_zero = 657098
  fb = f(x_max) - y_zero = 1.39941e+006
fa and fb must have opposite sign which is not the case

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

[Francesco Casella]

Works fine in v1.13.0-dev.234+g1a074b074