v12: Update regress, fix bug in gcm_run for OpenMP#725
Merged
mathomp4 merged 2 commits intofeature/sdrabenh/gcm_v12from May 6, 2025
Merged
v12: Update regress, fix bug in gcm_run for OpenMP#725mathomp4 merged 2 commits intofeature/sdrabenh/gcm_v12from
mathomp4 merged 2 commits intofeature/sdrabenh/gcm_v12from
Conversation
mathomp4
added
the
0 diff
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
1 participant
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.
This PR has two purposes.
gcm_run.jwhen running with more than one OpenMP thread. This fix was already ingcm_regress.jbut apparently was not ported togcm_run.jgcm_regress.jscript to use less resourcesI've also removed the
NUM_WRITERSchange in steps 4 and 5. It's causing some sort of issue, see GEOS-ESM/MAPL#3687