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

CE2COAST recipe to compare CMIP6 data over regional oceanic domains #2114

Open
tomaslovato opened this issue Apr 12, 2021 · 4 comments
Open

Comments

@tomaslovato
Copy link
Contributor

In the framework of CE2COAST project (https://www.ce2coast.com/),
we aim to use ESMValtool to generate regional scale assessment of CMIP6 models,
to support the development of downscaling activities.
CE2COAST project is funded through JPI Oceans and JPI Climate.

Following indications provided by @zklaus, I opened this issue to:

  1. include the project within the config-references.yml list
  2. contribute to ESMValTool with example recipe(s) for regional assessments developed within CE2COAST
@zklaus
Copy link

zklaus commented Apr 13, 2021

Nice! I think in principle you can open a new issue for every recipe you want to integrate and just include the addition to the project list in the corresponding PR.

@tomaslovato
Copy link
Contributor Author

@zklaus thanks for your feedback!
I think I can use the present issue by revising the title to appropriately match the recipe scope.

@tomaslovato tomaslovato changed the title include CE2COAST to project lists CE2COAST recipe to compare CMIP6 data over regional oceanic domains Apr 14, 2021
@tomaslovato
Copy link
Contributor Author

@zklaus I made few modifications to the ESMValCore code as well to have this recipe (and the related code changes) working... Do you agree if I open an issue on ESMValCore and I create a ce2coast branch in there as well?
In addition there are several update to the cmor fix for CMIP6 ocean variables that I can also include.

I added few features to the ocean timeseries script to enable plotting climatological data... @ledm do you see any overlap/mismatch in these changes with respect to your on-going developments?

@zklaus
Copy link

zklaus commented Apr 15, 2021

@tomaslovato opening an issue in the core is definitely the way to go. 👍

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

No branches or pull requests

2 participants