Improving counting of threads and CPUs for MPI jobs - #439
Open
LMurphy186232 wants to merge 1 commit into
Open
Conversation
mpaiao
approved these changes
Jul 30, 2026
Contributor
|
Thanks for PR @LMurphy186232, I went through it and it looks good to me. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix for array overruns when reporting MPI core usage.
Description
Changed the reporting of cores and threads in MPI runs to count core and thread IDs in dynamically allocated arrays, allowing for correct reporting no matter how these IDs are assigned.
Previously, the code assumed that when reporting on core and thread assignments to ED2 in MPI runs, ID numbers would be numbered sequentially starting at 0, and that there would be a maximum of 64 of each. Current HPC systems break both of those assumptions and this led to occasional array overflows.
Collaborators
@xiangtaoxu
@mpaiao
Types of changes
Changes in Settings, Input Files or Output Files
Expectation of Answer Changes:
No change expected in model output, just in the capacity of certain runs to proceed at all.
Checklist:
Testing :