Skip to content
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-LM - piClim-N2O (phys 2) #205

Closed
DirkOlivie opened this issue Jun 14, 2020 · 13 comments
Closed
Assignees

Comments

@DirkOlivie
Copy link

Mandatory information:

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

experiment_id
piClim-N2O

model_id
NorESM2-LM

CASENAME(s) and years to be CMORized
NF1850norbc_n2o2014_f19_20191025

Optional information

parent_experiment_id
piControl

parent_experiment_rip
r1i1p1f1

parent_time_units
'days since 0421-01-01'

branch_method
'Hybrid-restart from year 1751-01-01 of piControl'

other information
physics = 2
I suggest to call this member r1i1p2f1

@YanchunHe
Copy link
Collaborator

YanchunHe commented Jun 23, 2020

Cmorized and can be published to ESGF.

data path

  • /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/piClim-N2O
  • /projects/NS9034K/CMIP6/AerChemMIP/NCC/NorESM2-LM/piClim-N2O

Version

  • v20200218

sha256sum
/projects/NS9034K/CMIP6/AerChemMIP/NCC/NorESM2-LM/piClim-N2O

  • .r1i1p2f1.sha256sum_v20200218

@monsieuralok
Copy link
Collaborator

@YanchunHe directory /projects/NS9034K/CMIP6/RFMIP/NCC/NorESM2-LM/piClim-N2O does not exists.

@YanchunHe
Copy link
Collaborator

updated

@monsieuralok
Copy link
Collaborator

@YanchunHe published

@DirkOlivie
Copy link
Author

Concerning NorESM2-LM - piClim-N2O (phys2) :

I noticed that there is an error in the NF1850norbc_n2o2014_f19_20191025 simulation setup : it increased the CH4 concentration instead of the N2O concentration (and is therefor de facto identical to the NF1850norbc_ch42014_f19_20191025 simulation).

I have now rerun this simulation, and it is called NF1850norbc_n2o2014_f19_20200908, and is on nird in the directory /projects/NS2345K/noresm/cases.

Is it possible to retract the wrong results from ESGF?
Is it possible to cmorize the new results and publish them on ESGF?

@YanchunHe
Copy link
Collaborator

Hi @DirkOlivie
Yes, then we should retract and recmorize and publish the corrected experiment.

@monsieuralok , could you firstly retract the data, as they are wrong.

And I will update here when the new data are cmorized.

@monsieuralok
Copy link
Collaborator

@YanchunHe I did

@YanchunHe YanchunHe added started and removed Retract labels Oct 1, 2020
@YanchunHe
Copy link
Collaborator

cmorized and ready to be published

data path

  • /projects/NS9034K/CMIP6/AerChemMIP/NCC/NorESM2-LM/piClim-N2O/r1i1p2f1
  • /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/piClim-N2O

version

  • v20201001

sha256sum
/projects/NS9034K/CMIP6/AerChemMIP/NCC/NorESM2-LM/piClim-N2O/

  • .r1i1p2f1.sha256sum_v20201001

@monsieuralok
Copy link
Collaborator

@YanchunHe @DirkOlivie published

@YanchunHe
Copy link
Collaborator

Cmorized with additional iLAMB variables (#262), AERday zg500 (#263) and corrected fNup (#251).

They are ready to be published to ESGF.

data path

  • /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/piClim-N2O
  • /projects/NS9034K/CMIP6/AerChemMIP/NCC/NorESM2-LM/piClim-N2O

version

  • v20210203

sha256sum
/projects/NS9034K/CMIP6/AerChemMIP/NCC/NorESM2-LM/piClim-N2O

  • .r1i1p2f1.sha256sum_v20210203

@monsieuralok
Copy link
Collaborator

@YanchunHe published

@YanchunHe
Copy link
Collaborator

New dataset version to fix issues #270, #271, #272 and #273 is ready to be published:

data path

  • /projects/NS9034K/CMIP6/RFMIP/NCC/NorESM2-LM/piClim-N2O
  • /projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/piClim-N2O

version

  • v20210319

sha256sum

  • /projects/NS9034K/CMIP6/RFMIP/NCC/NorESM2-LM/piClim-N2O
  • .r1i1p2f1.sha256sum_v20210319

@monsieuralok
Copy link
Collaborator

@YanchunHe published

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants