-
Notifications
You must be signed in to change notification settings - Fork 5
add an input option to short-circuit post-init-comms #121
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
Conversation
lroberts36
left a comment
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.
This looks ok to me as a temporary fix since (I think) the PostInitializationCommunication is only necessary for periodic boundary conditions.
| params.Add("do_post_init_comms", | ||
| pin->GetOrAddBoolean("phoebus", "do_post_init_comms", false)); |
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.
Should this default to off or on? I would say default to on.
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 think default off is OK since it is currently broken -- can switch to on when it gets fixed
brryan
left a comment
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
| params.Add("do_post_init_comms", | ||
| pin->GetOrAddBoolean("phoebus", "do_post_init_comms", false)); |
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 think default off is OK since it is currently broken -- can switch to on when it gets fixed
|
This runs successfully on 4 devkit nodes. |
|
Dang it. Sorry. Didn't mean to close. |
jti-lanl
left a comment
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.
Okay by me.
PR Summary
Given the segfaults happening due to
PostInitializationCommunication, I'm adding a runtime option to disable it. Adds an input parameter in thephoebusblock.In the long term, we need to pull #118 through. Alternatively, changes upstream in Parthenon may make this driver stage unnecessary. @brryan what are your thoughts?
PR Checklist
scripts/bash/format.sh.