Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

spin up in FHIST_BGC case

xiaxs

xiaxs
New Member
Hi,

I am runing a FHIST_BGC case for output some specific variables, such as GPP, NPP and so on from 1901-2000 with a monthly frequency. we designed two plans to do this.

At first, basic information of FHIST_BGC case is as follows,
./create_newcase --compset FHIST_BGC --res f09_f09_mg17 --case ~/CESM2/scratch/FHIST_BGC_s2
[sysu_syli_3@ln42%tianhe2-H FHIST_BGC_s2]$ ./xmlquery RUN_TYPE,CONTINUE_RUN,RUN_REFCASE,RUN_REFDATE,RUN_STARTDATE,RUN_REFDIR,GET_REFCASE

Results in group run_begin_stop_restart
RUN_TYPE: hybrid
CONTINUE_RUN: FALSE
RUN_REFCASE: b.e20.BHIST.f09_g17.20thC.297_01_v3
RUN_REFDATE: 1979-01-01
RUN_STARTDATE: 1979-01-01
RUN_REFDIR: cesm2_init
GET_REFCASE: TRUE

plan 1: we will have to run 1890-1900 as a spin-up, and the continue run 1901-2000 to output some variables of interest.
my method is :
./xmlchange RUN_TYPE=startup,RUN_STARTDATE=1890-01-01,GET_REFCASE=FALSE
[sysu_syli_3@ln42%tianhe2-H FHIST_BGC_s2]$ ./xmlquery RUN_TYPE,CONTINUE_RUN,RUN_REFCASE,RUN_REFDATE,RUN_STARTDATE,RUN_REFDIR,GET_REFCASE

Results in group run_begin_stop_restart
RUN_TYPE: startup
CONTINUE_RUN: FALSE
RUN_REFCASE: b.e20.BHIST.f09_g17.20thC.297_01_v3
RUN_REFDATE: 1979-01-01
RUN_STARTDATE: 1890-01-01
RUN_REFDIR: cesm2_init
GET_REFCASE: FALSE

plan 2: we want to save the cost of extra 10 years for spin-up, we would like to choice a new available reference case as spin-up.
we choice the b.e21.B1850.f09_g17.CMIP6-piControl.001_v2 as the REFCASE, which has spin-up for 600 years.


./xmlchange RUN_STARTDATE=1901-01-01,GET_REFCASE=TRUE,RUN_REFCASE=b.e21.B1850.f09_g17.CMIP6-piControl.001_v2,RUN_REFDATE=0601-01-01

./xmlquery RUN_TYPE,CONTINUE_RUN,RUN_REFCASE,RUN_REFDATE,RUN_STARTDATE,RUN_REFDIR,GET_REFCASE

Results in group run_begin_stop_restart
RUN_TYPE: hybrid
CONTINUE_RUN: FALSE
RUN_REFCASE: b.e21.B1850.f09_g17.CMIP6-piControl.001_v2
RUN_REFDATE: 0601-01-01
RUN_STARTDATE: 1901-01-01
RUN_REFDIR: cesm2_init
GET_REFCASE: TRUE

But, a mismatch of dimension error happend as follows:
Reading initial conditions from
b.e21.B1850.f09_g17.CMIP6-piControl.001_v2.clm2.r.0601-01-01-00000.nc
(GETFIL): attempting to find local file
b.e21.B1850.f09_g17.CMIP6-piControl.001_v2.clm2.r.0601-01-01-00000.nc
(GETFIL): using
b.e21.B1850.f09_g17.CMIP6-piControl.001_v2.clm2.r.0601-01-01-00000.nc
in current working directory
Reading restart dataset
check_dim ERROR: mismatch of input dimension 50525 with expected value
62100 for variable landunit
Did you mean to set use_init_interp = .true. in user_nl_clm?
(Setting use_init_interp = .true. is needed when doing a
transient run using an initial conditions file from a non-transient run,
or a non-transient run using an initial conditions file from a transient run,
or when running a resolution or configuration that differs from the initial conditions.)
ERROR:
ERROR in /BIGDATA1/sysu_syli_3/CESM2/my_cesm_sandbox/components/clm/src/main/nc
dio_pio.F90.in at line 368


In a word, there are two questions we want to fix.
1. Is plan 1 scientific?
2. what is the proper and available reference case for plan 2. or what should we do to avoid the spin-up cost.

pardon my poor expression.

Best wishes.
 
Top