Opened 10 years ago
Last modified 6 years ago
#2870 new defect
Non-linear solver is unable to handle HeatingSystem (msl32) properly
Reported by: | lochel | Owned by: | wbraun |
---|---|---|---|
Priority: | critical | Milestone: | Future |
Component: | Run-time | Version: | trunk |
Keywords: | Cc: | adrpo |
Description
The non-linear solver is not able to proper handle a system of HeatingSystem (msl32).
Modelica.Fluid.Examples.HeatingSystem
It produces tons of warnings but does not fail:
stdout | warning | While solving non-linear system an assertion failed during initialization. | | | | | 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 stdout | warning | While solving non-linear system an assertion failed at time 0. | | | | | 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 stdout | warning | While solving non-linear system an assertion failed at time 0. | | | | | 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 stdout | warning | While solving non-linear system an assertion failed at time 0.012. | | | | | 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 stdout | warning | While solving non-linear system an assertion failed at time 0.012. | | | | | 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 [...]
Change History (10)
comment:1 Changed 10 years ago by sjoelund.se
comment:2 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.1 to 1.9.2
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).
comment:3 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.2 to 1.9.3
Milestone changed to 1.9.3 since 1.9.2 was released.
comment:4 Changed 9 years ago by sjoelund.se
- Milestone changed from 1.9.3 to 1.9.4
Moved to new milestone 1.9.4
comment:5 Changed 8 years ago by wbraun
- Priority changed from blocker to critical
This seems not to be a blocker, since it's there for longer run.
comment:6 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.9.4 to 1.9.5
Milestone pushed to 1.9.5
comment:7 Changed 8 years ago by sjoelund.se
- Milestone changed from 1.9.5 to 1.10.0
Milestone renamed
comment:8 Changed 7 years ago by sjoelund.se
- Milestone changed from 1.10.0 to 1.11.0
Ticket retargeted after milestone closed
comment:9 Changed 7 years ago by sjoelund.se
- Milestone changed from 1.11.0 to 1.12.0
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:10 Changed 6 years ago by casella
- Milestone changed from 1.12.0 to Future
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.
Got any fixes for this? The clang tests seem to fail, but gcc is fine (albeit very slow).