-
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
[CMORization request] ssp245-covid; r1i1p1f2 - r8i1p1f2 #250
Comments
Hi Yanchun, @YanchunHe jerry |
Then I have to reconfigure and restart the recmorization. These information can not be changed once the variable is cmorized. |
All cmorized. data path
realisations
version
(Not to publish now). |
Please publish the above-mentioned experiments, @monsieuralok |
This is fine for now, @YanchunHe. |
@YanchunHe published |
Hi @monsieuralok, many thanks, |
@tjiputra I see r1-r10 all experiments on ESGF server... |
I assume this is not an issue. I close this issue now. Reopen if needed. |
Mandatory information:
Full path to the case(s) of the experiment on NIRD
/projects/NS2345K/noresm/cases, for r1i1p1f2 - r3i1p1f2, r7i1p1f2, r8i1p1f2
/projects/NS9560K/noresm/cases, for r4i1p1f2 - r6i1p1f2
experiment_id
ssp245-covid
model_id
NorESM2-LM
CASENAME(s) and years to be CMORized
r1i1p1f2: NSSP245frc2covtwobli_01_f19_tn14_20200823; 2015-2050
r2i1p1f2: NSSP245frc2covtwobli_02_f19_tn14_20200823; 2015-2050
r3i1p1f2: NSSP245frc2covtwobli_03_f19_tn14_20200823; 2015-2050
r4i1p1f2: NSSP245frc2covtwobli_04_f19_tn14_20200723; 2015-2050
r5i1p1f2: NSSP245frc2covtwobli_05_f19_tn14_20200723; 2015-2050
r6i1p1f2: NSSP245frc2covtwobli_06_f19_tn14_20200723; 2015-2050
r7i1p1f2: NSSP245frc2covtwobli_01b_f19_tn14_20200922; 2015-2050
r8i1p1f2: NSSP245frc2covtwobli_02b_f19_tn14_20200922; 2015-2050
Optional information
parent_experiment_id
historical
parent_experiment_rip
r1i1p1
r2i1p1
r3i1p1
r1i1p1
r2i1p1
r3i1p1
r1i1p1
r2i1p1
parent_time_units
'days since 1800-01-01'
branch_method
'Hybrid-restart from year 2015-01-01 of historical',
other information
Do not publish first in ESGF!!
The text was updated successfully, but these errors were encountered: