-
Notifications
You must be signed in to change notification settings - Fork 37
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
UserWorkBeforeRestartOutput #1062
Conversation
@brryan is this ready for review? It's still marked WIP |
@Yurlungur Yes it works but I just wanted to see what people think about including |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am fine with outputting OutputParameters
. Also I wonder if this should be in StateDescriptor
in addition to or instead of ApplicationInput
?
Also should the flag be documented in the docs?
A few comments below. However, consider this non-blocking. I'll approve now.
…non into brryan/userworkrestartoutput
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned on Thursday, I'm happy with forwarding output params (even if its' a breaking change).
With that in mind, I could also imagine a solution to the original problem without introducing new callbacks by just checking on output type internally downstream, but having additional callbacks also probably doesn't hurt.
OK I updated this to reintroduce explicitness around
That would pick up two breaking changes so maybe we want to get some consensus on a separate PR that refactors some of these hooks sometime in the future? If so I think this is ready to go, @pgrete if you are OK to approve (and others don't want to pause before merge) I will then go ahead and merge this in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR Summary
We have a downstream need to call a third party library's restart capability when writing our own restarts. This PR adds hooks for
Mesh
andMeshBlock
analogs ofUserWorkBeforeOutput
that are only triggered during restart outputs.PR Checklist