FS#221 Exceptions lead to freeze or fatal error during parallel computations
Metadata
Property | Value |
---|---|
Project | dumux |
Category | Implicit models |
Reported by | Alexander Kissinger (alexander.kissinger@iws.uni-stuttgart.de) |
Reported at | Feb 21, 2014 13:39 |
Type | Bug Report |
Version | Git |
Last edited by | Alexander Kissinger (alexander.kissinger@iws.uni-stuttgart.de) |
Last edited at | Mar 23, 2015 17:37 |
Closed by | Alexander Kissinger (alexander.kissinger@iws.uni-stuttgart.de) |
Closed at | Mar 23, 2015 17:37 |
Closed in version | 2.7 |
Resolution | Fixed |
Description
As already indicated by Ali in the mailing list ([DuMuX] Exception while updating Ali Nowamooz) the exceptions thrown in the fluidsystem or also from my own experience in the constraint solvers lead to a freeze of the system since the communication between the processors fails. The ideal behavior should be that either the time step is reduced once unphysical values come up (-> one process throws an exception caught by the newton controller), or that the newton solver is allowed to proceed hoping that it will come back to physical values in the next step (if this is not the case it will not converge and reduce the time step). Either way the exception handling during parallel computations should be fixed.