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

domains changing in CMIP6 #6

Closed
larsbuntemeyer opened this issue Nov 29, 2023 · 2 comments · Fixed by #9
Closed

domains changing in CMIP6 #6

larsbuntemeyer opened this issue Nov 29, 2023 · 2 comments · Fixed by #9

Comments

@larsbuntemeyer
Copy link
Contributor

@gnikulin Could you fill this issue and drop those domains that which will change? I would probably add a column called mip_era or something to distinguish between domains in CMIP5 and CMIP6 which (as fas as i understood) have the same CORDEX_domain/domain_id? We can also split the tables then if that is more convenient.

@larsbuntemeyer
Copy link
Contributor Author

See also #5

@gnikulin
Copy link
Contributor

gnikulin commented Nov 29, 2023

Here I would suggest:

  1. to copy and rename the merged table "rotated-latitude-longitude.csv" to e.g. "CORDEX-CMIP5_all_grids.csv"

  2. to add CORDEX-CMIP5 prefix to the current files with some renaming of "CORDEX-CMIP5_domain_boundaries.csv" "CORDEX-CMIP6_domain_boundaries.csv" , "CORDEX-CMIP5_rotated_grids.csv" and "CORDEX-CMIP5_regular_grids.csv" and clean "CORDEX-CMIP5_rotated_grids.csv" leaving only the rotated grids for the 14 continental scale domains.

  3. I'll fill "CORDEX-CMIP5_domain_boundaries.csv", now it's only Europe.

We can keep these files as reference and create a new set of the files with mip_era CMIP6 and then I can update domains with new configuration.

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

Successfully merging a pull request may close this issue.

2 participants