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

Replication policy for new E3SM data #13

Open
lliming opened this issue Sep 6, 2024 · 3 comments
Open

Replication policy for new E3SM data #13

lliming opened this issue Sep 6, 2024 · 3 comments
Assignees

Comments

@lliming
Copy link
Contributor

lliming commented Sep 6, 2024

Argonne's E3SM modeling team will be publishing new E3SM data between now and the start of CMIP7.
This data will definitely be stored and available on Argonne's data node and indexed in Argonne's ESGF-1.5 index.

Q: Do either ORNL or LLNL want to replicate this data? (It's ~75 TB.)
Q: If the answer to the first question is "no," should the metadata appear in LLNL's or ORNL's ESGF-1.5 indices (with links to Argonne, presumably)?

@climate-dude
Copy link

climate-dude commented Sep 7, 2024

Will these data be from CMIP6 simulations and fully CMORized?

@sashakames
Copy link

(1) E3SM needs to stop publishing to CMIP6. They should migrate their publishing to CMIP6Plus for their CMORized data. its not reasonable for us to not end the project so we can migrate it read-only.
(2) LLNL will not be replicating E3SM-native data (unCMORized)

@sashakames
Copy link

sashakames commented Oct 24, 2024

Looks like E3SM will be able to continue to publish to CMIP6 for existing registrations but new registrations would be CMIP6. the question remains of what they still need to publish for their v2.x registration and what is the timeframe for that. I think this is just DECK and Scenario data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants