-
Notifications
You must be signed in to change notification settings - Fork 16
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
Comments
I can't find the casename under above path. ls /projects/NS9560K/FRAM/noresm/cases/NSSP126frc2_f19_tn14_20191014 |
OK, I need to change a login node. Please ignore above message. |
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. |
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. |
Years of model output (from the first to the last) needs to rsync to NIRD: /projects/NS9034K/noresm/cases/ 2031 2040 |
@jgriesfeller @YanchunHe cab be look at ssp* for NorESM-LM. They should be also prioritized. |
Started copying of the specific years to /tos-project1/NS9034K/noresm/cases |
started first period only since the others are still copying, just to see if there's still something working |
transfer complete. I will start the last 2 decades when I know if 2031 2040 succeeds. |
current status:
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. |
Status of cmorized files:
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
version
sha256sum
|
@oyvindseland @YanchunHe published |
should remove the cmorized original model output. |
cmorized new data version to fix bugs reported in issues: #109 #178 #179 data path
version
sha256sum
|
@YanchunHe @DirkOlivie published |
Redo the cmorization for @monsieuralok Please publish this to the ESGF. data path version
sha256sum commit: 2725389 |
@YanchunHe published |
cmorized data path
version
sha256sum
|
@YanchunHe published |
@YanchunHe retracted |
@YanchunHe |
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 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, |
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 |
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! |
Retracted the whole Removed the affected files, and reprocess the rest as dataset of version data path
version
sha256sum
|
@YanchunHe published with new version |
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
The text was updated successfully, but these errors were encountered: