You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)?
The text was updated successfully, but these errors were encountered:
(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)
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.
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)?
The text was updated successfully, but these errors were encountered: