-
Notifications
You must be signed in to change notification settings - Fork 18
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
[CMIP6 CMOR-ization & ESGF-publication] NorESM2-MM ssp245 (realisation 2) #236
Comments
Hi @adagj , I understand this is hybrid restart from the realisation 2 of the MM historical run. but I see the So if you agree, I will update the 'parent_time_units' (which matters for a parameter 'branch_time_in_parent' for the cmorized data). |
Hi @YanchunHe , |
cmorized and can be published: data path
version
sha256sum
|
@YanchunHe published |
Cmorized with additional iLAMB variables (#262), AERday They are ready to be published to ESGF. data path
version
sha256sum
|
@YanchunHe published |
New dataset version to fix issues #269, #270, #271, #272, #273 is ready to be published: data path
version
sha256sum
|
@YanchunHe published |
cmorized data path
version
sha256sum
|
@YanchunHe published |
@YanchunHe retracted |
Mandatory information:
Full path to the case(s) of the experiment on NIRD
/projects/projects/NS9560K/noresm/cases/
experiment_id
ssp245 (r2i1p1f1)
model_id
NorESM2-MM
CASENAME(s) and years to be CMORized
NSSP245frc2_02_f09_tn14_20200629, 2015 - 2100
Optional information
(additional information, if the experiment is branched/hybrid restart from previous parent experiment; you may find more information relevant to the experiment_id here: https://github.com/NorESMhub/noresm2cmor/blob/master/tables/CMIP6_CV.json)
parent_experiment_id
historical
parent_experiment_rip
r2i1p1f1
parent_time_units
'days since 1850-01-01 '
branch_method
e.g.,
'Hybrid-restart from year 2015-01-01 of historical',
other information
parent case name: /projects/projects/NS9560K/noresm/cases/NHISTfrc2_02_f09_tn14_20200519
The text was updated successfully, but these errors were encountered: