search

NorESMhub / noresm2cmor

A command line tool for cmorizing NorESM output
http://noresmhub.github.io/noresm2cmor/
5 stars 16 forks source link

[CMIP6 CMOR-ization & ESGF-publication] NorESM2-LM - PAMIP pdSST-pdSIC members 101-200 #182

Closed lisesg closed 1 week ago

lisesg commented 4 years ago

Mandatory information:

Full path to the case(s) of the experiment on NIRD

Full path to post-processed fields epfy, epfz, utendepfd, vtem, wtem (Eliassen-Palm fluxes and friends):

experiment_id pdSST-pdSIC

model_id NorESM2-LM

CASENAME(s) and years to be CMORized

Optional information

parent_experiment_id amip

parent_experiment_rip r1i1p1f1

parent_time_units days since 1975-01-01 00:00:00

branch_method 'Hybrid-restart from year 2000-04-01 of amip'

other information The experiment is a hybrid run starting from /projects/NS9560K/noresm/cases/NFHISTnorpddmsbc_f19_mg17_IC4PAMIP_20190816, which is an extension of the amip experiment carried out to provide restart and initial-condition files for the start date April 1st 2000.

YanchunHe commented 4 years ago

Hi @lisesg , please check the permission of all the experiment folders so that I can have read access.

I would suggest that you change the group of the files/folders to ns2345k, use command as:

chown -R lisesg:ns2345k parent_folders_to_change

And also add r-s permission to users of the same group

find parent_folder_to_change -type d -print -exec chmod g+rxs {} \;

After you have done this, I can start the cmorization process. Thanks!

Yanchun

lisesg commented 4 years ago

Sorry about that! I've updated the permissions of the files. Hope everything is OK now.

YanchunHe commented 4 years ago

Thanks, cmorization now starts!

YanchunHe commented 4 years ago

cmorized and ready to publish to ESGF

data path

*data version

sha256sum

monsieuralok commented 4 years ago

@YanchunHe published

lisesg commented 2 months ago

It seems like zg500 for AERday has not been cmorized with the additional members.

YanchunHe commented 1 month ago

cmorized zg500 and ta850 for members 101-200. And can be published to ESGF

data path

data version

sha256sum

monsieuralok commented 1 month ago

@YanchunHe ta850 with Eday frequency with same version is already published

YanchunHe commented 1 month ago

@YanchunHe ta850 with Eday frequency with same version is already published

OK, I see indeed ta850 is published, but the ensemble member r101 is missing in locally on NIRD but findable on ESGF.

I am a bit confused now what happed.

What is the best way to proceed?

Is that OK to retract all ta850 and republish them again together with zg500?

monsieuralok commented 1 month ago

@YanchunHe I retracted datasets ta850 but, it is not possible to publish them with same version number.

YanchunHe commented 1 month ago

@YanchunHe I retracted datasets ta850 but, it is not possible to publish them with same version number.

OK, I renamed the datasets to the latest v20230616, please see the updated threads above.

YanchunHe commented 3 weeks ago

@YanchunHe I retracted datasets ta850 but, it is not possible to publish them with same version number.

OK, I renamed the datasets to the latest v20230616, please see the updated threads above.

Hi Alok, @monsieuralok

Just wondering is this still in the process for publishing?

monsieuralok commented 3 weeks ago

@YanchunHe I have published atleast a week earlier but, I should open errata issue regarding retract then, I will update

monsieuralok commented 1 week ago

@YanchunHe published Eratta issue:- https://errata.ipsl.fr/static/view.html?uid=372c2185-7d71-58a7-821a-b47c3b42e3af