Changes between Initial Version and Version 2 of Ticket #5139


Ignore:
Timestamp:
2019-05-10T08:56:43Z (6 years ago)
Author:
Francesco Casella
Comment:

Widened the scope of the ticket and made it a blocker for 1.14.0, as it involves ModelicaTest 3.2.3. Should be a quick fix.

Andreas, Karim, Lennart, please have a look and decide who takes care of it.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5139

    • Property Milestone 1.13.0 → 1.14.0
    • Property Cc Lennart Ochel Andreas Heuermann added
    • Property Owner changed from Willi Braun to Andreas Heuermann
    • Property Status new → assigned
    • Property Summary Initialization failure due to min/max violations do not trigger the homotopy-based initialization → Initialization failures due to min/max and assert() violations do not trigger the homotopy-based initialization

  • Ticket #5139 – Description

    initial v2  
    88               x-2.65);
    99  der(y) = x;
     10  annotation(__OpenModelica_commandLineOptions = "-d=nowarnMinMax");
    1011end Test;
    1112}}}
    12 with {{{-d=nowarnMinMax}}}. The simulation fails with
     13The simulation fails with
    1314{{{
    1415assert | warning | The following assertion has been violated at time 0.000000 x > = 0.0
    … …  
    2324If this was actually done, homotopy would ensure the convergence of the nonlinear solver to the positive solution, which would then be accepted by the min/max checks.
    2425
    25 Please make sure that the triggering of an assertion during initialization does not abort the simulation but rather invokes the homotopy-based solution process.
     26A similar issue takes place with [https://libraries.openmodelica.org/branches/newInst/ModelicaTest_3.2.3/files/ModelicaTest_3.2.3_ModelicaTest.Blocks.LimitersHomotopy.sim ModelicaTest.Blocks.LimitersHomotopy], which currently fails with the message:
     27{{{
     28Regular simulation: ./ModelicaTest_3.2.3_ModelicaTest.Blocks.LimitersHomotopy -abortSlowSimulation -alarm=480   
     29assert            | warning | The following assertion has been violated during initialization at time 0.000000
     30|                 | |       | abs(mustUseHomotopy.x - 100.0) < 1e-06
     31assert            | error   | Wrong solution selected
     32assert            | info    | simulation terminated by an assertion at initialization
     33}}}
     34In both cases I would suggest to print out the following notification message:
     35  Invalid initial solution obtained without homotopy. Trying with homotopy-based initialization. You can skip the attempt without homotopy with the -homotopyOnFirstTry simulation flag.
     36
     37then restart the solution process with the homotopy-based solver.