Do not populate HEMCO data arrays for dry-run simulations #31
Conversation
This file contains 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
In HEMCO/src/Core/hcoio_read_std_mod.F90, we have removed calls to FileData_ArrInit that populate arrays with dummy values when doing a GEOS-Chem or HEMCO dry-run simulation. This causes an excessive amount of memory to be allocated. With this fix, even a geosfp_2x25_standard benchmark now only requires 5.3 GB of memory (instead of 32GB, as was the case previously). Signed-off-by: Bob Yantosca <[email protected]>
This was referenced May 14, 2020
|
This update came in as part of commit 0828192, "Updates in GEOS-Chem 12.8.1 HEMCO subdirectory." I am therefore closing this PR without a git merge. |
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.
In HEMCO/src/Core/hcoio_read_std_mod.F90, we have removed calls to
FileData_ArrInit that populate arrays with dummy values when doing
a GEOS-Chem or HEMCO dry-run simulation. This causes an excessive
amount of memory to be allocated.
With this fix, even a geosfp_2x25_standard benchmark now only requires
5.3 GB of memory (instead of 32GB, as was the case previously).
Signed-off-by: Bob Yantosca [email protected]