Skip to content

Conversation

Steven-Roberts
Copy link
Collaborator

@Steven-Roberts Steven-Roberts commented Sep 4, 2024

This makes SPRKStep's handling of an invalid order consistent with the rest of ARKODE (following #439). Currently an invalid order is an error, but it doesn't leave the integrator in an invalid state or prevent the integration from proceeding. For this reason I wonder if ARK_WARNING would be more appropriate for the error_code.

balos1
balos1 previously approved these changes Sep 4, 2024
Copy link
Member

@balos1 balos1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ARK_WARNING would probably be better, because then the output would go through the warning handler instead of the error handler. See https://github.com/LLNL/sundials/blob/main/src/arkode/arkode.c#L3555. However, we want the behavior to be consistent across all of the steppers and they seem to use ARK_ILL_INPUT.

@balos1 balos1 self-requested a review September 4, 2024 18:44
@Steven-Roberts
Copy link
Collaborator Author

I'll go ahead and make them all warnings across ARKODE in this PR then.

@gardner48 gardner48 merged commit 9f0f337 into develop Sep 11, 2024
24 of 25 checks passed
@gardner48 gardner48 deleted the bugfix/sprk-order-msg branch September 11, 2024 03:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants