How to do a BSSP126 run with cesm2.1.3 and resolution f09_g17 with the extended SSP126 scenario for years 2100-2300

M

m_kliphuis@uu_nl

New Member
Dear all,

I did a BSSP126 run with CESM version 2.1.3. and with resolution f09_g17 run for years 2015-2100.

It was setup with command:

./create_newcase --run-unsupported --case b.e21.BSSP126_BPRPcmip6_hosing.f09_g17.001 --compset SSP126_CAM60_CLM50%BGC-CROP-CMIP6DECK_CICE%CMIP6_POP2%ECO%ABIO-DIC_MOSART_CISM2%NOEVOLVE_WW3_BGC%BPRP --res f09_g17 --output-root /projects/0/prace_imau/prace_2013081679/cesm2_1_3/

I would now like to extend it to year 2300 under the extended SSP 126 scenario.
How do I do this? I guess I only need different files for ozone, aircrafts etc? e.g.

prescribed_ozone_file = 'ozone_strataero_WACCM_L70_zm5day_2015-2100_SSP126_c190221.nc'
aircraft_specifier = 'ac_CO2 -> emissions-cmip6_CO2_anthro_ac_ssp126_201401-210112_fv_0.9x1.25_c20190207.txt'

Where can I get them?

Do I need to think of certain other things?

Many thanks,
Michael
 
erik

erik

Erik Kluzek
CSEG and Liaisons
Staff member
The SSP extensions weren't available at the time that cesm2.1.3 was made. So I recommend that you use:

release-cesm2.1.4

The main change was to add the extensions and get them working. So I'm pretty sure that it will be compatible
with your previous 2.1.3 simulation. However, I do recommend looking over the ChangeLog in the tag to see what
might have changed and if it matters for what you are doing. I just scanned it and only see a couple mentions of things
that sound answer changing (cesm2.1.4-rc.13, and cesm2.1.4-rc.05 has some CAM changes, and SSP emissions updates
in cesm2.1.4-rc.04). With this branch we made efforts to restrict answer changes unless they were absolutely necessary.


Since, the extensions have datasets for most of the components, the list of datasets you need is quite large, and we
wouldn't be able to list them all off.
 
M

m_kliphuis@uu_nl

New Member
erik said:
The SSP extensions weren't available at the time that cesm2.1.3 was made. So I recommend that you use:

release-cesm2.1.4

The main change was to add the extensions and get them working. So I'm pretty sure that it will be compatible
with your previous 2.1.3 simulation. However, I do recommend looking over the ChangeLog in the tag to see what
might have changed and if it matters for what you are doing. I just scanned it and only see a couple mentions of things
that sound answer changing (cesm2.1.4-rc.13, and cesm2.1.4-rc.05 has some CAM changes, and SSP emissions updates
in cesm2.1.4-rc.04). With this branch we made efforts to restrict answer changes unless they were absolutely necessary.


Since, the extensions have datasets for most of the components, the list of datasets you need is quite large, and we
wouldn't be able to list them all off.
Click to expand...
Dear Erik,

I am now looking at my old messages and can't believe that I did not respond to your message! I'm very sorry, I thought I did.
Your suggestion was very helpful though, we indeed used release 2.1.4 and were able to extend our run to year 2300 under the extended SSP 126 scenario.

Many thanks!
Michael
 
L

lucia

luyaohuang
Member
Hi Michael, I was wondering if you could tell me where I can download the extended SSP1-2.6 scenario data up to 2300.
 
L

lucia

luyaohuang
Member
Hello Manishvenu,

I followed your suggestion and downloaded CESM2.1.4; however, I encountered an issue when setting up a case, because I also had a newer CESM2.2.2 installation. My main question is that I still cannot find any climate data for the period 2100–2300 in the CESM inputdata repository, even though it is supposed to be automatically retrieved.

In fact,I realized that I actually only need to run the land component. I need six variables of climate data for the period 2100–2300 – air temperature, precipitation, specific humidity, longwave radiation, shortwave radiation, and wind speed – to drive CLM5.0.

I downloaded the CLM5.0.34 code corresponding to CESM2.1.4, and I found that it includes the following three case options:

ISSP585ExtClm50BgcCrop : SSP585EXT_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_MOSART_CISM2%NOEVOLVE_SWAV
ISSP534ExtClm50BgcCrop : SSP534EXT_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_MOSART_CISM2%NOEVOLVE_SWAV
ISSP126ExtClm50BgcCrop : SSP126EXT_DATM%GSWP3v1_CLM50%BGC-CROP_SICE_SOCN_MOSART_CISM2%NOEVOLVE_SWAV

However, I noticed that these cases drive the climate forcing only up to 2014, and all climate fields are repeatedly cycled over 2001–2014. Only CO₂ is fully transient from 2015 to 2500. What I actually need is to also have Solar, Precip, and TPQW changing from 2015 to 2100. I need the climate data for this period. But I could not find the corresponding 2100–2300 climate data at https://svn-ccsm inputdata.cgd.ucar.edu/trunk/inputdata/atm/datm7/anomaly_forcing/.

The streams settings are:

streams = "datm.streams.txt.CLMGSWP3v1.Solar 2001 2001 2014",
"datm.streams.txt.CLMGSWP3v1.Precip 2001 2001 2014",
"datm.streams.txt.CLMGSWP3v1.TPQW 2001 2001 2014",
"datm.streams.txt.presaero.SSP1-2.6 2015 2015 2101",
"datm.streams.txt.topo.observed 1 1 1",
"datm.streams.txt.co2tseries.SSP1-2.6 2015 2015 2500"
taxmode = "cycle", "cycle", "cycle", "cycle", "cycle", "extend"

My question is: do I have to run the CAM6.0 atmosphere model within CESM2.1.4 myself to simulate the six climate variables (air temperature, precipitation, specific humidity, longwave radiation, shortwave radiation, and wind speed) for the extended 2100–2300 period under SSP585 and SSP126? Then, based on the simulation results and following the approach described in Koven et al. 2015 – using their "scale factors" method (i.e., applying monthly climate anomalies/scale factors from a CESM1 simulation for RCP8.5 and ECP8.5 to repeating historical meteorology) – should I scale the repeated historical data to obtain the 2100–2300 climate change trends, and then use that data to drive CLM5.0?

For reference, the Koven et al. 2015:

"We force CLM4.5BGC with time-varying meteorology, CO2 concentration, N deposition, and land use change to estimate the C cycle response to global change. The atmospheric forcing data for 1850–2005 are taken from the combined Climatic Research Unit and National Center for Environment Predication (CRUNCEP) dataset (data available at dods.ipsl.jussieu.fr/igcmg/IGCM/BC/OOL/OL/CRU-NCEP/), which merges high-frequency variability from the National Centers for Environmental Prediction−National Center for Atmospheric Research reanalysis (30) with the monthly mean climatologies from the CRU temperature and precipitation datasets (31). Projection period forcing is calculated by applying monthly climate anomalies/scale factors from a Community Earth System Model, version 1 (CESM1) simulation for the scenarios Representative Concentration Pathway 8.5 (RCP8.5) for the years 2006–2100 and Extended Concentration Pathway 8.5 (ECP8.5) for the years 2100–2300 to repeating 1996–2005 CRUNCEP meteorology. For constant climate (control and biogeochemically forced) runs, atmospheric data are repeated over the period 1901–1920. CO2 concentrations follow transient historical (1850−2005), RCP8.5 (2006−2100), and ECP8.5 (2101−2300) concentrations for biogeochemically and fully forced runs, and remain fixed at 1850 levels (284.7 ppm) for control and climatically forced runs. Atmospheric N deposition is from coupled atmospheric chemistry−climate runs (32), land use follows the historical (1850−2005) and RCP8.5 (2006−2100) scenarios (33), and both are transient in all cases. After 2100, land use is static and wood harvest is zero."
Click to expand...

I would like to know whether CESM1 or CESM2 provides ready-to-use climate forcing data for the period 2100–2300(SSP126/SSP245/SSP370/SSP585), including the six variables required to drive CLM5.0: air temperature, precipitation, specific humidity, longwave radiation, shortwave radiation, and wind speed.

Thank you very much for your help!
 
You must log in or register to reply here.
Back
Top