On 4/28/25 00:45, Simon wrote:
attached, I have adjusted your "kinsol_06" test to dealii 9.4.0 format
(callbacks return integers rather than throwing exceptions)
and forced it to report an evaluation failure five times in a row. In
that situation, KINSol cannot recover and returns a negative status value.
Ah, I see -- the error in that case does not originate in a user
callback, but instead is a legitimate error code of KINSOL not related
to a programming mistake. Indeed that should result in an exception, not
a program termination (or nothing at all, as currently in release mode).
I can only test the program in dealii 9.4.0, where the .solve() function
ignores in release mode whatever KINSol returns.
But if I understand ...
"This code has been rewritten a couple of years ago, and I think
that it now
does exactly what you want it to do:"
correctly, the attached program behaves differently in dealii 9.6.0 by
throwing an exception, thereby offering the possibility to handle those
errors?
No, in this case the behavior has not changed -- but it should.
Do you know whether KINSOL returns different error codes based on
whether it just can't find a solution, or whether something is
conceptually wrong (i.e., a programming error)?
Would you be willing to create this test case for the current deal.II
sources as well? That would make it easier for me to come up with a patch.
Best
W.
--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see
https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/dealii/58f16a13-e006-43db-bc24-9e943e941de3%40colostate.edu.
