Opened 10 years ago
Last modified 3 years ago
#3116 new defect
Make warning/error message from the nonlinear solver more informative
| Reported by: | Francesco Casella | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Backend | Version: | trunk |
| Keywords: | Cc: |
Description
When simulating the ThermoPower.Examples.CISE.CISESim120501 example using OMEdit, a lot of red warning messages pop up, saying:
- Matrix singular!
- under-determined linear system not solvable!
- Warning: maximal number of iteration reached but no root found
These messages succeed in conveying the message that something goes wrong with the solver and scaring off the user.
However, when it comes to try to understand the cause of the problem and fix it, these messages leave the poor user utterly clueless.
I would definitely suggest to make these messages a bit more informative, e.g. by adding the number of the system that becomes singular, possibly with a direct link to the declarative debugger (Debug more!), or writing which matrix exactly has singularity problems and how can one understand why it is so (nullspace, rank, etc). This will give users a chance of understanding the cause of the problem and hopefully fix it.
Otherwise, troubleshooting the model would require supernatural divination abilities that few people (if any) in the community possess :)
Change History (15)
comment:1 by , 10 years ago
| Milestone: | 1.9.2 → 1.9.3 |
|---|
comment:6 by , 8 years ago
| Milestone: | 1.11.0 → 1.12.0 |
|---|
Milestone moved to 1.12.0 due to 1.11.0 already being released.
comment:8 by , 7 years ago
| Milestone: | 1.12.0 → 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.
comment:9 by , 7 years ago
| Milestone: | Future → 1.13.0 |
|---|
I think this is still relevant since it is very much into the face of new users and causes lots of confusion. Any improvement as to giving the user clues of what to do with these messages are appreciated.
comment:10 by , 7 years ago
@dietmarw I do have some ideas on how to improve the situation here. In a nutshell, the plan is to enhance the existing debugger, which currently shows (most of the) structural information, by integrating all the information that can be obtained by the various logging features when something goes wrong.
For this specific case (singular Jacobian matrices), I also have some ideas about using the analysis of the nullspaces of the Jacobian to pinpoint the root cause of the singularity.
I am just about to prepare a proposal for a master's thesis project @ LiU, I can share it if you are interested.
comment:12 by , 5 years ago
| Milestone: | 1.14.0 → 1.16.0 |
|---|
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0
comment:14 by , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Milestone changed to 1.9.3 since 1.9.2 was released.