Export area as REAL8 #10
Open
Conversation
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
lizziel
force-pushed
the
bugfix/import_area_as_real8
branch
from
17c484d to
2e370ed
Compare
Signed-off-by: Lizzie Lundgren <[email protected]>
lizziel
force-pushed
the
bugfix/import_area_as_real8
branch
from
2e370ed to
e9bb62c
Compare
This was referenced Sep 30, 2025
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.
This is a companion PR to geoschem/geos-chem#3050. It updates the area export in offline advection from REAL4 to REAL8. This export is received as an import in GEOS-Chem where it is stored in the
State_Gridobject as double precision floating point. Since it is computed as REAL8 in FV3 we should be exporting it as REAL8 not REAL4.This PR fixes geoschem/GCHP#514 when merged with the companion GEOS-Chem PR.