Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Allow for flexible precision I/O #18

Open
msulprizio opened this issue Feb 7, 2020 · 3 comments
Open

[FEATURE REQUEST] Allow for flexible precision I/O #18

msulprizio opened this issue Feb 7, 2020 · 3 comments
Assignees
Labels
category: Feature Request New feature or request never stale Never label this issue as stale topic: Structural Modifications Related to HEMCO structural modifications (as opposed to scientific updates)

Comments

@msulprizio
Copy link
Contributor

msulprizio commented Feb 7, 2020

To reduce differences between single and multi-segmented GEOS-Chem simulations, we need to be able to save out and read in restart fields at REAL8. Right now, HEMCO is hardcoded to use REAL4 for data I/O.

@msulprizio msulprizio added the category: Feature Request New feature or request label Feb 7, 2020
@yantosca yantosca added the never stale Never label this issue as stale label Jan 13, 2021
@yantosca
Copy link
Contributor

This is related to issue geoschem/geos-chem#111.

@msulprizio msulprizio removed the never stale Never label this issue as stale label Mar 3, 2021
@yantosca yantosca added the topic: Structural Modifications Related to HEMCO structural modifications (as opposed to scientific updates) label Jan 24, 2023
@lizziel
Copy link
Contributor

lizziel commented Jan 18, 2024

I am going to take a look at this and see if I can update HEMCO to read and store R8 as well as R4. It looks like we need this capability for CESM. It would also be good to finally get bitwise reproducibility when running GC-Classic.

Copy link

stale bot commented Apr 22, 2024

This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue.

@stale stale bot added the stale No recent activity on this issue label Apr 22, 2024
@lizziel lizziel added never stale Never label this issue as stale and removed stale No recent activity on this issue labels Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Feature Request New feature or request never stale Never label this issue as stale topic: Structural Modifications Related to HEMCO structural modifications (as opposed to scientific updates)
Projects
None yet
Development

No branches or pull requests

4 participants