-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print summary_callback
as finalizer
#1783
Comments
I like printing the |
Yeah, is already nice. However, our default setup is to have the summary callback as first callback. Thus, if we activate it like this in the last step, the report will miss calls to the other callbacks in the final step (such as the final IO etc.). As far as I understand, |
Yes, that's true. That's also why I just opened a PR there to use |
If this is something we want to have in Trixi.jl, I am happy to prepare a PR that can be included in the next breaking release. |
Let's gather some opinions first. What do @trixi-framework/principal-developers think about this? Pro
Con
|
Since SciML/OrdinaryDiffEq.jl#2061 (comment) just got merged, we could consider printing the output of the
summary_callback
automatically after finishingsolve
without having to call it manually. However, I would consider this to be breaking since it will just be annoying to print it twice if it's already called manually.The text was updated successfully, but these errors were encountered: