-
Notifications
You must be signed in to change notification settings - Fork 18
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-MM - ssp585 #151
Comments
sync all data to NS9034K |
Started syncing to /projects/NS9560K/noresm/cases/NSSP585frc2_f09_tn14_20191105 as ns9560K has enough quota for 14TB |
updates: cmorisation has been ongoing for this experiments for some days. |
cmorized and ready to be published to ESGF data path
version
*sha256sum
|
@matsbn @YanchunHe published |
cmorized new data version to fix bugs reported in issues: #109 #178 #179 data path
version
sha256sum
|
@YanchunHe published |
Cmorized with additional iLAMB variables (#262), AERday They are ready to be published to ESGF. data path
version
sha256sum
|
@YanchunHe published |
@YanchunHe I have rerun the SSP585 simulation with NorESM2-MM. The aim of the run was (1) to have extra high-frequency fields to force FLEXPART (these should not be cmorized), and (2) to have extra monthly aerosol diagnostics (hopefully these can be cmorized). The new simulation is called NSSP585frc2_f09_tn14_20200919 and is on NS2345K. The results of this simulation are bit-identical to the original simulation (NSSP585frc2_f09_tn14_20191105). I have checked that. We are mainly interested in the cmorization of missing AERmon fields. Is it possible to run the cmorization for AERmon? It is probably not a good idea to run the cmorization for all model components and all frequencies again. This new simulation contains for the atmosphere only the high-frequency fields needed for FLEXPART, and not the standard CMIP6 high frequency output (I think the cmorization would run into problems treating the high-frequency fields). I hope this is possible. |
Hi @DirkOlivie, it is nearly straightforward to redo the cmorisation for only the AERmon fields, as long as they are in I will try this and keep the updates here. |
cmorized data path
version
sha256sum
|
@YanchunHe published |
@YanchunHe retracted |
@monsieuralok Could you retract all the data of this experiment. It will be extended and will be publish again. Refer to #326 |
CMORized the whole SSP585 2015 to 2100 with extension from 2101 to 2298, see #326 data path
version
sha256sum
|
Hi I have received a question from the community on when the SSP585 data will be available again. Given the label ESGF publish I presume that it is a matter of days? |
I have an impression, the ESGF is now quite healthy, so it should be published soon. @monsieuralok has better command on this. |
@oyvindseland @YanchunHe published it |
Mandatory information:
Full path to the case(s) of the experiment on NIRD
/projects/NS9560K/FRAM/noresm/cases
experiment_id
ssp585
model_id
NorESM2-MM
CASENAME(s) and years to be CMORized
NSSP585frc2_f09_tn14_20191105, 2015-2100
Optional information
parent_experiment_id
historical
parent_experiment_rip
r1i1p1f1
parent_time_units
'days since 1850-01-01' atm/lnd
'days since 0001-01-01' ice
'days since 1800-01-01' ocn
branch_method
'Hybrid-restart from year 2015-01-01 of historical'
other information
The text was updated successfully, but these errors were encountered: