FMS1: Don't create IO domains for single-PE domain #1522
Merged
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.
FMS mpp domain creation is done in the
clone_MD_to_d2D
function, andcurrently an IO domain is always created within the MPP domain.
This has caused problems with single-PE runs in FMS1, where the
write_field
logic was not able to reach the part which removes halodata if an IO domain was present, and halo data was being written to the
restart files.
This issue arose when
PARALLEL_RESTARTFILES
was set toTrue
forsingle-PE tests.
This does not appear to be a problem with FMS2, and no action is needed
by the FMS team.