[CMIP6 CMOR-ization & ESGF-publication] NorESM2-LM - ssp370 (realisation 2)

[DirkOlivie]

Mandatory information:

Full path to the case(s) of the experiment on NIRD
/projects/NS9560K/FRAM/noresm/cases

experiment_id
ssp370

model_id
NorESM2-LM

CASENAME(s) and years to be CMORized
NSSP370frc2_02_f19_tn14_20191118, 2015-2054

Optional information

parent_experiment_id
historical

parent_experiment_rip
r2i1p1f1

parent_time_units
'days since 1850-01-01'

branch_method
'Hybrid-restart from year 2015-01-01 of historical'

other information
realisation = 2

[YanchunHe]

Rsync all data to NS9034K

[jgriesfeller]

started transfer to /projects/NS9560K/noresm/cases/NSSP370frc2_02_f19_tn14_20191118

[jgriesfeller]

Transfer complete

[YanchunHe]

cmorized and ready to publish
(note, only realisation 2 has been fully cmorized so far)

data path

• /tos-project1/NS9034K/CMIP6/.cmorout/NorESM2-LM/ssp370/v20191108
• /tos-project1/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370/r2i1p1f1

version

• v20191108

sha256sum*

• /tos-project1/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370/.r2i1p1f1.sha256sum_v20191108

---

$ ./checkcmorout.sh
real: r2i1p1f1
Ofx, fx, etc 9
yyyy1 yyyy2 nf
2015 2020 542
2021 2030 542
2031 2040 542
2041 2050 542
2051 2054 542
Total: 2719

[monsieuralok]

@YanchunHe realisation 1 and realisation 3 are pending but, I have seen checksum files in directory .r1i1p1f1.sha256sum_v20191108 .r3i1p1f1.sha256sum_v20191108; Is anything wrong or issues are not updated?

[YanchunHe]

@YanchunHe realisation 1 and realisation 3 are pending but, I have seen checksum files in directory .r1i1p1f1.sha256sum_v20191108 .r3i1p1f1.sha256sum_v20191108; Is anything wrong or issues are not updated?

You are right, realisation 1 and 3 are not complete yet. Those checksum files for .r1*, .r3* are generated by some automatic processes. And they will be updated once those experiments are completely cmorized.

Please go ahead with realisaiton 2 for publish, and ignore the realisation 1 and 3 (I will update their own Issue once this is done). Thanks!

[monsieuralok]

@DirkOlivie @YanchunHe published

[YanchunHe]

cmorized new data version to fix bugs reported in issues: #109 #178 #179

data path

• /projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370
• /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/ssp370

version

• v20200218

sha256sum
/projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370/

• .r2i1p1f1.sha256sum_v20200218

(Note, only dmsos are cmorized and included, no 6hourly and 3hourly data).

[monsieuralok]

@YanchunHe published

[YanchunHe]

Data of the first month, 201501 is missing, see issue #277
Could you retract all Emon, Lmon and LImon datasets of this ssp370? @monsieuralok

I have recmorized these data, and can be republished to ESGF after retraction.

data path

• /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/ssp370
• /projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370

data version

• v20210319

sha256sum
/projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370

• .r2i1p1f1.sha256sum_v20210319b

(note, only 2015-2050 available)

[monsieuralok]

@YanchunHe published

[YanchunHe]

cmorized burtFractionAll related to issue #286

data path

• /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/ssp370/v20210818
• /projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370

version

• v20210818

sha256sum

• /projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp370
• .r2i1p1f1.sha256sum_v20210818

[monsieuralok]

@YanchunHe realization 2 and 3 for ssp370 have only data upto year 12 2054. Is that correct?

[YanchunHe]

@YanchunHe realization 2 and 3 for ssp370 have only data upto year 12 2054. Is that correct?

Yes, that is correct.

[monsieuralok]

@YanchunHe published