Skip to content

error when mapping cmip6 to cmi6plus #9

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

Closed
klauswyser opened this issue Feb 21, 2025 · 8 comments
Closed

error when mapping cmip6 to cmi6plus #9

klauswyser opened this issue Feb 21, 2025 · 8 comments

Comments

@klauswyser
Copy link
Contributor

I tried ./map-cmip6-to-cmip6plus.py Amon tas and got

Cloning into 'mip-cmor-tables.wiki'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
@treerink
Copy link
Contributor

Ok I will commit the created cmip6 - cmip6Plus table as well, then this step will be skipped

treerink added a commit that referenced this issue Feb 21, 2025
@treerink
Copy link
Contributor

Should be solved now? i.e. avoided.

@klauswyser
Copy link
Contributor Author

Thanks a lot Thomas. Yes, it works fine now. I found a few inconsistencies in the metadata of the converted files and have some suggestions for improvements. Probably easiest if I do this in a branch, but not sure if I find time for this today.

@treerink
Copy link
Contributor

I actually found some differences where I believe the newly directly cmip6plus cmorised output is less correct. We can also go through quickly together and see which final solution we prefer.

@klauswyser
Copy link
Contributor Author

It's very well possible that the new tables for CMIP6Plus are buggy (e.g. PCMDI/cmor#776), yet it doesn't help to simply correct them in our cmorisation process. The ESGF publishing works with the official tables and if our metadata are different (even if we believe they are more correct) it will trigger an error and the files cannot be published.

@treerink
Copy link
Contributor

Yes I noticed that one for instance. There are another few tiny deviations, not sure whether they will really trigger publishing errors, but maybe you found out already?

@treerink
Copy link
Contributor

Anyway, I can in-correct them if we wish :) and get it identical.

@treerink
Copy link
Contributor

treerink commented Mar 3, 2025

The issue with the table is solved by adding it to the repo. The later raised issues have been reviewed and handled as far the can.

@treerink treerink closed this as completed Mar 3, 2025
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

2 participants