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 - ssp126 #134

Closed
DirkOlivie opened this issue Nov 19, 2019 · 44 comments
Closed

[CMIP6 CMOR-ization & ESGF-publication] NorESM2-LM - ssp126 #134

DirkOlivie opened this issue Nov 19, 2019 · 44 comments
Assignees

Comments

@DirkOlivie
Copy link

Mandatory information:

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

experiment_id
ssp126

model_id
NorESM2-LM

CASENAME(s) and years to be CMORized
NSSP126frc2_f19_tn14_20191014, 2015-2100

Optional information

parent_experiment_id
historical

parent_experiment_rip
r1i1p1f1

parent_time_units
'days since 1850-01-01'

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

other information

@YanchunHe
Copy link
Collaborator

I can't find the casename under above path.

ls /projects/NS9560K/FRAM/noresm/cases/NSSP126frc2_f19_tn14_20191014
ls: cannot access /projects/NS9560K/FRAM/noresm/cases/NSSP126frc2_f19_tn14_20191014: No such file or directory

@YanchunHe
Copy link
Collaborator

OK, I need to change a login node.

Please ignore above message.

@YanchunHe
Copy link
Collaborator

Just a notice on the progress:

These SenarioMIP experiments encountered very often 'HDF error' and crashed, and the reason is under investigating.

Please expect some delay of the cmorzation for these experiments.

@YanchunHe YanchunHe added the FRAM label Nov 30, 2019
@YanchunHe
Copy link
Collaborator

This types of error occur very often, so I these experiments can hardly finish.

Please refer to #140 for the discussion.

We will look into this.

@YanchunHe
Copy link
Collaborator

Years of model output (from the first to the last) needs to rsync to NIRD: /projects/NS9034K/noresm/cases/

2031 2040
2061 2070
2081 2090

@monsieuralok
Copy link
Collaborator

@jgriesfeller @YanchunHe cab be look at ssp* for NorESM-LM. They should be also prioritized.

@jgriesfeller
Copy link
Collaborator

Started copying of the specific years to /tos-project1/NS9034K/noresm/cases

@jgriesfeller
Copy link
Collaborator

started first period only since the others are still copying, just to see if there's still something working

@jgriesfeller
Copy link
Collaborator

transfer complete. I will start the last 2 decades when I know if 2031 2040 succeeds.

@jgriesfeller jgriesfeller self-assigned this Dec 18, 2019
@jgriesfeller
Copy link
Collaborator

current status:

(base) [jang@login-nird-0 ssp126]$ pwd
/projects/NS9560K/cmor/noresm2cmor/namelists/CMIP6_NorESM2-LM/ssp126
(base) [jang@login-nird-0 ssp126]$ ./checkcmorout.sh 
real:	r1i1p1f1
Ofx, fx, etc	9
yyyy1	yyyy2	nf
2015	2020	607
2021	2030	607
2031	2040	720
2041	2050	607
2051	2060	607
2061	2070	298
2071	2080	607
2081	2090	442
2091	2100	607
Total:		5111

Unfortunately the cmorisation of the period 2031 2040 produced more files (720 vs 607) than the earlier one run using the NFS link to FRAM. But it went through smoothly at least.
I have started the other decades, but I guess we have to run the remaining decades again before publishing.
But what has changed compared to the earlier run?

@YanchunHe
Copy link
Collaborator

Status of cmorized files:

$ ./checkcmorout.sh
real:	r1i1p1f1
Ofx, fx, etc	9
yyyy1	yyyy2	nf
2015	2020	607
2021	2030	607
2031	2040	720
2041	2050	607
2051	2060	607
2061	2070	695
2071	2080	607
2081	2090	717
2091	2100	607
Total:		5783

I can't check what happens to 2031-2040, 2061-70,2081-2090, but at least there should be a minimum of 607 fields cmorized.

I would push this to publish to ESGF.

data path

  • /tos-project1/NS9034K/CMIP6/.cmorout/NorESM2-LM/ssp126/v20191108

version

  • v20191108

sha256sum

  • /tos-project1/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp126/.r1i1p1f1.sha256sum_v20191108

@monsieuralok
Copy link
Collaborator

@oyvindseland @YanchunHe published

@YanchunHe
Copy link
Collaborator

should remove the cmorized original model output.
Jan, you have to do that since I don't have the permission to delete the data. @jgriesfeller

@YanchunHe
Copy link
Collaborator

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

data path

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

version

  • v20200218

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

  • .r1i1p1f1.sha256sum_v20200218

@YanchunHe YanchunHe reopened this Feb 27, 2020
@monsieuralok
Copy link
Collaborator

@YanchunHe @DirkOlivie published

@YanchunHe
Copy link
Collaborator

YanchunHe commented Jun 11, 2020

Redo the cmorization for snc, snd and snw to include the missing 201501 (Refer to Issue #18).

@monsieuralok Please publish this to the ESGF.

data path
-/projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp126
/projects/NS9034K/CMIP6/.cmorout/NorESM2-LM/ssp126

version

  • v20191108b

sha256sum
/projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp126
.r1i1p1f1.sha256sum_v20191108b

commit: 2725389

@YanchunHe YanchunHe reopened this Jun 11, 2020
@monsieuralok
Copy link
Collaborator

@YanchunHe published

@YanchunHe
Copy link
Collaborator

cmorized burtFractionAll related to issue #286

data path

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

version

  • v20210818

sha256sum

  • /projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp126
  • .r1i1p1f1.sha256sum_v20210818

@YanchunHe YanchunHe reopened this Aug 30, 2021
@YanchunHe YanchunHe removed the Retract label Aug 30, 2021
@monsieuralok
Copy link
Collaborator

@YanchunHe published

@monsieuralok
Copy link
Collaborator

@YanchunHe retracted

@DirkOlivie
Copy link
Author

@YanchunHe
Would it be possible to also cmorize cVegGrass, cVegTree and cVegShrub for this simulation (Emon)? There is a request from a user for these variables in this simulation.
Best regards, Dirk

@YanchunHe
Copy link
Collaborator

@YanchunHe Would it be possible to also cmorize cVegGrass, cVegTree and cVegShrub for this simulation (Emon)? There is a request from a user for these variables in this simulation. Best regards, Dirk

Are they available in the raw output, right?

What are their corresponding names for these?

Could you also update the CMIP6 data request sheet too?

@YanchunHe YanchunHe reopened this Apr 12, 2024
@YanchunHe YanchunHe added CMORize and removed Retract labels Apr 12, 2024
@DirkOlivie
Copy link
Author

@YanchunHe
These variables were available in cmorized output for the experiments deforest-globe, esm-ssp585-ssp126Lu, hist-noLu, ssp126-ss370Lu, and ssp370-ssp126Lu. Therefore I assumed it would be possible to also cmorize them for ssp126. However, the fields for these 3 cmorized variables in the 5 above mentioned experiments are all zero.

Also in the "data request sheet", there is no name given for the original output (or some formula).

I will have a look into the original raw data and try to find out whether the necessary variables (at the moment I don't know what they could be) to do the cmorization are available.

Best regards,
Dirk

@JorgSchwinger
Copy link
Collaborator

Hi @DirkOlivie

I would assume that you need to activate PFT-level outputs for CLM to be able to produce these fields. I do not think it's possible to calculate cVeg for specific vegetation types from the grid-cell averaged standard output.

Best
Jörg

@DirkOlivie
Copy link
Author

Hi @JorgSchwinger

thanks. I indeed only found a variable in the output fields which is carbon for total vegetation (not split out). So I will inform that we don't have available these individual amounts (cVegGrass, cVegTree and cVegShrub) in the standard simulations.

Best regards, Dirk

@YanchunHe
Copy link
Collaborator

YanchunHe commented Apr 29, 2024

Hi @JorgSchwinger

thanks. I indeed only found a variable in the output fields which is carbon for total vegetation (not split out). So I will inform that we don't have available these individual amounts (cVegGrass, cVegTree and cVegShrub) in the standard simulations.

Best regards, Dirk

Hi @DirkOlivie , so to my understanding, all these variables are not available, so will not be able to be cmorized?

If so, we will close the issue for now. Thanks!

@YanchunHe
Copy link
Collaborator

Retracted the whole v20191108 datasets due to superfluous daily files as reported in #367

Removed the affected files, and reprocess the rest as dataset of version v20191109.

data path

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

version

  • v20191109

sha256sum

  • /projects/NS9034K/CMIP6/ScenarioMIP/NCC/NorESM2-LM/ssp126
  • .r1i1p1f1.sha256sum_v20191109

@monsieuralok
Copy link
Collaborator

@YanchunHe published with new version

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

6 participants