[CMIP6 CMORization & ESGF-publication] CMOR-ization of first two PAMIP experiments about noresm2cmor HOT 18 OPEN

pdSST-pdSIC and pdSST-futArcSIC are cmorized and stored now under:
/tos-project1/NS9034K/CMIP6/.cmorout/NorESM2-LM

But does not pass PrePARE quality-check, with "list index out of range" error.
see Issue #31

from noresm2cmor.

Qality-check PrePARE passed, see Issue #31
CMORized data is ready to publish to ESGF. See Issue #37

from noresm2cmor.

Member 94 of pdSST-futArcSIC contains fewer files than the other members according to the checksum file. @YanchunHe , can you check and fix it?

@monsieuralok will need to republish this member after its fixed

from noresm2cmor.

This is caused by conflict of json files when serval task runs for the same experiment (which has been fixed).

I will redo part of the cmorization for this realisation.

from noresm2cmor.

Hi, Member 72 and 85 pdSST-futArcSIC and member 84 and 91 pdSST-pdSIC also seems to have problem. Please can you check it.

from noresm2cmor.

Member 94,72,85 for pdSST-futArcSIC; member 84 and 91 for pdSST-pdSIC have been updated. sha256sum and QCreports have been updated.

Ready to publish to ESGF (refer Issue #37 )

from noresm2cmor.

@YanchunHe Published

from noresm2cmor.

Thanks a lot for CMOR-izing and publishing the first set of variables! I've just had a request for daily zg500 from someone working on a study on blocking, and it's not among the variables that have been CMOR-ized so far. Would it be possible to CMOR-ize zg500 or is it not supported yet?

from noresm2cmor.

I see zg500 is in the AERday table, which is not supported yet.
I am currently cmorization the experiment with current supported tables, and will work to add more fields soon later.

I foresee that I will include quite some more tables/fields in about two weeks. And then redo the cmorization for all finished experiments with these additionally supported fields with new data version. Will that be too late?

I don't want to add only a few variables and publish a new release. That will increase the workload for cmorization, publication a lot, considering so many experiments.

from noresm2cmor.

Daily zg500 is a key variable for many atmospheric studies that focus on dynamics. If we wait a couple of weeks then we risk that NorESM2 will not contribute to community papers central to IPCC. Therefore I'd suggest to prioritise the implementation of AERday and subsequent cmor-ization of zg500 and not make this dependent on the cmor-ization of other tables and variables.

from noresm2cmor.

It looks like a lot of the other MIPs and the DECK have requested the full 3-D daily zg, which includes the 500 hPa surface, and makes daily zg500 redundant. From the CMIP6 data request spreadsheet, it looks like PAMIP and PMIP are the only MIPs that explicitly ask for daily zg500 (unless I'm missing something), probably because daily zg is not a requested field for those MIPs.

Edit: some columns where for some reason not visible when I was searching the spreadsheet, looks like daily zg500 is also a priority 1 field for AerChemMIP and DCPP.

from noresm2cmor.

I have added support for the tables Eday, CFday and AERday in the latest commit NorwegianClimateCentre@66ed977

I have created a namelist specification for NorCPM1 to output selected daily variables https://github.com/NorwegianClimateCentre/noresm2cmor/blob/master/namelists/CMIP6_NorCPM1/dcppA-hindcast_i1_v20191005/var.nml (note that it uses the "old" column order)

from noresm2cmor.

Great, thanks, I will later incorporate this to NorESM2.

from noresm2cmor.

Note that I also fixed a bug (missing r

I've just configured another daily variable TMQ -> prw to NorCPM1's daily output. NorCPM1 daily output variables I've so far configured that are not in table "day" are (old column order):

&table_AERday
dAERday = .true.
tAERday = 'CMIP6_AERday.json',
rAERday = 1000000,
vAERday =
'Z010 ','zg10 ',' ',
'Z500 ','zg500 ',' ',
'U010 ','ua10 ',' ',
'V010 ','va10 ',' ',
/

&table_Eday
dEday = .true.
tEday = 'CMIP6_Eday.json',
rEday = 1000000,
vEday =
'TMQ ','prw ','kg m-2',
'PRECTMX ','prhmax ','kg m-2 s-1',
'T500 ','ta500 ',' ',
'T850 ','ta850 ',' ',
/

&table_CFday
dCFday = .true.
tCFday = 'CMIP6_CFday.json',
rCFday = 1000000,
vCFday =
'OMEGA500 ','wap500 ',' ',
/

&table_SIday
dSIday = .true.
tSIday = 'CMIP6_SIday.json',
rSIday = 1000000,
vSIday =
'aice_d ','siconc ',' ',
'hi_d ','sithick ',' ',
'fs_d ','sisnconc ',' ',
'uvel_d ','siu ','zero2missing',
'vvel_d ','siv ','zero2missing',
/

&table_Oday
dOday = .true.
tOday = 'CMIP6_Oday.json',
rOday = 1000000,
vOday =
'sst ','tos ',' ',
'maxmld ','omldamax ',' ',
/

from noresm2cmor.

A bug in the namelist file (refer to #78), which cause identical cmorized output among different members/realisations for *day tables., has been fixed.

*day fields (including only zg500_AERday and ta850_Eday) have been recmorized, and tagged as v20191018

cmorized files are now ready to publish to ESGF, in order to replace the wrong v20191009 version.

data path

• /projects/NS9034K/CMIP6/PAMIP/NCC/NorESM2-LM/pdSST-pdSIC
• /projects/NS9034K/CMIP6/PAMIP/NCC/NorESM2-LM/pdSST-futArcSIC

version

• v20191018
  (all the 100 members)

other information

• sha256sum updated
• PrePARE QC passed

May need to retract the v20191009 data at some point.

I think this should be put with high-priority.

from noresm2cmor.

@YanchunHe published

from noresm2cmor.

cmorized with additional fields

data path

• /projects/NS9034K/CMIP6/PAMIP/NCC/NorESM2-LM/pdSST-pdSIC
• /projects/NS9034K/CMIP6/PAMIP/NCC/NorESM2-LM/pdSST-futArcSIC

version

• v20191108
  (all the 100 members)

sha256sum

• .r*i1p1f1.sha256sum_v20191108b
  ( * include 1-100)

from noresm2cmor.

@YanchunHe @IngoBethke @Kirkevag published

from noresm2cmor.