-
Notifications
You must be signed in to change notification settings - Fork 5
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
Register source_id PCMDI-AMIP-1-2-0 #87
Comments
Add dataset_collection DOI entry, after changes @MartinaSt implemented the higher-level citation info, for PCMDI-AMIP-X this is https://cera-www.dkrz.de/WDCC/ui/cerasearch/cmip6?input=input4MIPs.CMIP6.CMIP.PCMDI or https://doi.org/10.22033/ESGF/input4MIPs.10449 |
Updated to reflect the |
Will need to redefine the Is it possible to define this in the input files Make sure to check groupId before writing data to import grp
a = grp.getgrall()
for count,x in enumerate(a):
print(count,x,type(x),x[0]) |
@mauzey1 I am planning on writing some new data with a newly defined In the table files we have e.g. input4MIPs_Omon.json
What is the best path forward to generate data with the new mip_era? Would a change to
work? ping @taylor13 |
I suspect as we move to new eras, the CMIP tables will evolve, so I think we will need to preserve the old .json table files with mip_era=CMIP6, and generate a new set, as needed, for CMIP6Plus. In these new tables, we would set mip_era to CMIP6Plus. I know in the current case, nothing is changing really, but we should think about the future and how we'll organize tables for new eras. |
I'm of two minds about this, we have version control, so you can always just dial up a previous version. Accumulating dead repos/tables doesn't seem like a great idea either |
If we don't create a new set of tables for future eras, could we create an index pointing to the versions that were used in a particular era? |
In some ways we already have that Releases https://github.com/PCMDI/input4MIPs-cmor-tables/releases And tags https://github.com/PCMDI/input4MIPs-cmor-tables/tags As input4MIPs is more continuous, building off the CMIP6 standards, I think we're good with that path. For CMIP7 for e.g. I am sure much will change, so a completely new repo would make sense |
@mauzey1 no need to bother with my query above (#87 (comment)) - I have just tested adding |
@taylor13 I have just updated a pull request with updates to table etc files that allow |
In preparation for the
1.2.0 - 187001-201906
update, the revisedsource_id
needs to be registered. Some tweaks to https://github.com/PCMDI/amipbcs will also likely be required to conform with the new input4MIPs_required_global_attributes.jsonFollowing example in #57 and #94
The text was updated successfully, but these errors were encountered: