Information required in the CLM5 Spinup procedure.

Status
Not open for further replies.

Han Lubin

Han Lubin
Member
The compset and resolution you are using in release-cesm2.2.0:

--compset HIST_CAM60_CLM50%BGC-CROP_SICE_SOCN_MOSART_SGLC_SWAV --res f09_g17

comes out of the box with

START_DATE=1979-01-01

and this initial file:

/glade/p/cesmdata/cseg/inputdata/lnd/clm2/initdata_map/clmi.BHIST.2000-01-01.0.9x1.25_gx1v7_simyr2000_c200728.nc

So, that's the initial file I would use. I'm not sure what your reasons are for running a hybrid with RUN_REFCASE=b.e20.BHIST.f09_g17.20thC.297_01_v3, or for using clmi.I2000Clm50BgcCrop.2011-01-01.1.9x2.5_gx1v7_gl4_simyr2000_c190312.nc.

That said, my own run using this initial file crashed with the same error. Since this is coming from the atmospheric model, I would suggest posting to the CAM forum. For reference, here are the steps that I took, you might try repeating these:

git describe
cesm2.2.0

cd cime/scripts
./create_newcase --case cesm220_FHISTClm50BgcCrop --compset HIST_CAM60_CLM50%BGC-CROP_SICE_SOCN_MOSART_SGLC_SWAV --res f09_g17 --run-unsupported
cd cesm220_FHISTClm50BgcCrop
./xmlchange STOP_OPTION=nmonths
./xmlchange STOP_N=1
./case.setup
qcmd -- ./case.build
./case.submit
Many thanks, Mr. Oleson. I will post this error to the CAM forum.
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
@Xiaoyu yu , The second method you describe (branch) is more robust. In that method the river runoff model will also use a spunup file. River water spins up very quickly so we don't always use the branch method.

You can query available spatial resolutions by changing directory to cime/scripts and running:

./query_config --grids

hcru_hcru should appear as a possible grid.
So you would need to specify --res hcru_hcru in your create_newcase command, e.g.,

./create_newcase --case cesm220_hcru_GSWP3V1_2000 --res hcru_hcru --compset I2000Clm50BgcCrop --run-unsupported

However, an appropriate surface dataset does not appear to be available for hcru_hcru for that release of the model (the domain file does exist), so you would need to create one using the mksurfdata_map tool:

cd components/clm/tools/mksurfdata_map
./mksurfdata.pl -res 360x720cru -years 2000

and then in user_nl_clm, point to the dataset you created using:

fsurdat = 'your_dataset'
 

Xiaoyu yu

New Member
@Xiaoyu yu , The second method you describe (branch) is more robust. In that method the river runoff model will also use a spunup file. River water spins up very quickly so we don't always use the branch method.

You can query available spatial resolutions by changing directory to cime/scripts and running:

./query_config --grids

hcru_hcru should appear as a possible grid.
So you would need to specify --res hcru_hcru in your create_newcase command, e.g.,

./create_newcase --case cesm220_hcru_GSWP3V1_2000 --res hcru_hcru --compset I2000Clm50BgcCrop --run-unsupported

However, an appropriate surface dataset does not appear to be available for hcru_hcru for that release of the model (the domain file does exist), so you would need to create one using the mksurfdata_map tool:

cd components/clm/tools/mksurfdata_map
./mksurfdata.pl -res 360x720cru -years 2000

and then in user_nl_clm, point to the dataset you created using:

fsurdat = 'your_dataset'
Many thanks for your reply! I have tried the first method of spin-up, but there may be some mistakes in the output of first step.

The steps I followed are:
./create_newcase --case /scratch01/yuxy/test_cesm2/I2000CLM50_spin --res f09_g17 --compset 2000_DATM%GSWP3v1_CLM50%SP_SICE_SOCN_MOSART_SGLC_SWAV --run-unsupported --compiler intel --machine sofie
./xmlchange CLM_ACCELERATED_SPINUP=on,CLM_FORCE_COLDSTART=on
./xmlchange DATM_CLMNCEP_YR_START=1901
./xmlchange DATM_CLMNCEP_YR_END=1905
./xmlchange RUN_STARTDATE=1901-01-01
./xmlchange STOP_N=5
./xmlchange STOP_OPTION=nyears
./case.setup
vi user_nl_clm
./case.build --skip-provenance-check
./case.submit


I want to spin-up the case from 1901 to 1905, but the output in $casename/land/hist are from 2000 to 2005. The related files are attached below.
Am I following the right steps to spin up? What settings should I changed?

Thanks in advance.
 

Attachments

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Hmm, that's strange. I tried that and I got what I expect, e.g.,

cesm220_1deg_I2000CLM50_spin.clm2.h0.1901-01-01-00000.nc

I don't see anything wrong with your setup. Are you sure those files are from that simulation?
 

Chengyun

Chengyun
New Member
Hello Mr.Oleson,

Sorry to bother you. I am also confused about spinup period. I try to simulate GPP from 1980 to 2010 and the future GPP(SSP585) from 2020 to 2050 using CLM5-FATES to run compset I2000Clm50FatesGs and res f05_g16. Here is my confusion about the steps.

(1) First creat a spin-up case (I2000Clm50Fates_spinup) to evaluate the model's equilibrium and change CLM_ACCELERATED_SPINUP=on, CLM_FORCE_COLDSTART=on.
The query I have is to carry on such an experiment do I require to Spin-up the model for over 600 years? Would it be sufficient to recycle 30 times form 1960 to 1979 for spinup in I2000Clm50FatesGs, then is it reasonable to use the 600-year spunup file as initial file to simulate GPP for 1980-2010(I2000)?

(2) Then creat a common case (I2000Clm50Fates) running from 1980 to 2010, and set the finidat in user_nl_clm as the output of spin-up case.
Is this the right approach for simulating GPP from 1980 to 2010? The CLM-FATES model doesnot have IHISTClm50Ftates--compset, and the CO2 is constant. I wonder to know whether I need to change the amount of co2 to simulate the history GPP?

(3) When I try to simulate the future GPP(SSP585) from 2020 to 2050 using CLM5-FATES to run compset I2000Clm50FatesGs and res f05_g16, I am not sure how to choose the surfacedata, domain data, and finiidat.
So at first, I want to build a case ISSP585Clm using compset ISSP585Clm50BgcCrop, The ISSP585 compset would give domain, surface, and finidar data containing transient landcover, CO2, aerosol and nitrogen deposition, year-specific atmospheric forcing, etc. Then I want to use the inputdata from compset ISSP585ClmBgcCrop to compset I2000Clm50FatesGs to simulate the future GPP(SSP585).

Is it reasonale for I to use the inputdata from ISSP585ClmBgcCrop to run compset I2000Clm50FatesGs using CLM5-FATES model?
If it works, what should I pay attention to? If it doesnot, What should I do to simulate the future GPP?

Any suggestions will be appreciated! Thanks in advance.
 
Status
Not open for further replies.
Back
Top