search

PCMDI / cmip6-cmor-tables

JSON Tables for CMOR3 to create CMIP6 dataset
BSD 3-Clause "New" or "Revised" License
31 stars 46 forks source link

COVID Exps #326

Closed wachsylon closed 3 years ago

wachsylon commented 4 years ago

Hi, there are some new COVID experiments in the CVs, e.g. "ssp245-cov". We require an update of the cmip6-cmor-tables. Maybe we should also wait for a new DReq version since the exps must be included there as well. Best, Fabi

taylor13 commented 4 years ago

I think these already are were added to https://github.com/PCMDI/cmip6-cmor-tables/blob/master/Tables/CMIP6_CV.json a couple of days ago. (I think only the 6 most important experiments have been added; they are considered part of the DAMIP activity so that the infrastructure can handle it. CovidMIP is not an authorized CMIP6 activity and so does not appear in the activity_id CV. There are no new variables requested for these new experiments, so you should be able to write anything requested using the current CMOR tables.) Let us know if something is missing or you encounter any problems.

wachsylon commented 4 years ago

Thanks Karl for the quick answer. We can work with the CV, but in my opinion it would be nicer to have a new release of the tables because the quality assurance should not need to relie on a git commit but rather on a release name. Best,Fabi

taylor13 commented 4 years ago

@mauzey1 @durack1 : what is our policy for new table releases vs. commits? Seems like we discussed this at some length a long time ago.

durack1 commented 4 years ago

@wachsylon the releases have been generated in the past to deal with CMOR changes which require minimum versions of tables, or secondarily for updates to the data request from which the cmip6-cmor-tables are built.

As @taylor13 notes the CMIP6_CV.json is updated nightly by cronjob, and we have not been issuing new releases when these updates occur, rather the git commit is how this has been tracked

wachsylon commented 4 years ago

I rethought my point. I agree that it is necessary to use the most recent CMIP6_CV.json although working with old tables which means that there is no need for a new release.

The question then is Why CMIP6_CV is included at all in the tables as a static file? However, I right now do not have an alternative suggestion :) Sorry.

You can close that issue.

durack1 commented 3 years ago

To close this out, the CMIP6_CV.json file is included in the repo for user ease, we have considered plans to also include future CVs (such as a potential CMIP6Plus_CV.json) which would leverage the CMIP6-version tables, but allow a post-CMIP6 experiment/cohort to develop.

Obviously, for CMIP7 many things would need updating, and so cmip7-cmor-tables, and a complete rethink may be necessary at that time