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

a question when I use DATM_MODE= CLMGSWP3v1 in CLM

Status
Not open for further replies.
Z

zzwflood

zzwflood
New Member
Dear everyone,

I have a question when I use DATM_MODE= CLMGSWP3v1,I had already set my forcing data is from 1996 to 2014,but I set
./xmlchange RUN_STARTDATE=1996-01-01
./xmlchange RESUBMIT=9
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=2
I would like to know clearly how CLM5.0 achieved its output in 2015? I did not have input data for this year, but I obtained output data for this year.
Here are the basic settings for my submit case：
Code: 
./create_newcase --case 5SHJ0.1X0.1 --res CLM_USRDAT --compset HIST_DATM%GSWP3v1_CLM50%SP_SICE_SOCN_SROF_SGLC_SWAV --mach tc4600 --run-unsupported

./xmlchange ATM_DOMAIN_PATH=/home/zzw/cesmwork/cesm/cime/tools/mapping/gen_domain_files,LND_DOMAIN_PATH=/home/zzw/cesmwork/cesm/cime/tools/mapping/gen_domain_files

./xmlchange LND_DOMAIN_PATH=/home/zzw/cesmwork/cesm/cime/tools/mapping/gen_domain_files,LND_DOMAIN_PATH=/home/zzw/cesmwork/cesm/cime/tools/mapping/gen_domain_files

./xmlchange ATM_DOMAIN_FILE=domain.lnd.SHJ0.1X0.1_noocean.230327.nc

./xmlchange LND_DOMAIN_FILE=domain.lnd.SHJ0.1X0.1_noocean.230327.nc

./xmlchange CLM_USRDAT_NAME=CLMGSWP3v1

./xmlchange DATM_MODE=CLMGSWP3v1

./xmlchange CPL_NTASKS=15,ATM_NTASKS=25,LND_NTASKS=45,ICE_NTASKS=15,OCN_NTASKS=15,ROF_NTASKS=10,GLC_NTASKS=20,WAV_NTASKS=15,ESP_NTASKS=1

./xmlchange DATM_CLMNCEP_YR_ALIGN=1996

./xmlchange DATM_CLMNCEP_YR_START=1996

./xmlchange DATM_CLMNCEP_YR_END=2014

./xmlchange DIN_LOC_ROOT_CLMFORC=/home/zzw/software/inputdata/atm/datm7

./xmlchange RUN_STARTDATE=1996-01-01

./xmlchange RESUBMIT=9

./xmlchange STOP_OPTION=nyears

./xmlchange STOP_N=2

./xmlchange CLM_ACCELERATED_SPINUP=on

change env_build.xml---line155----<entry id="CALENDAR" value="GREGORIAN">

vim user_nl_clm

hist_empty_htapes = .true.

hist_fincl1 = 'QFLX_EVAP_TOT:A', 'QRUNOFF:A', 'QH2OSFC:A', 'QOVER:A','RAIN:A', 'QRUNOFF_R:A', 'QRUNOFF_U:A'

hist_fincl2 = 'QFLX_EVAP_TOT:A', 'QRUNOFF:A', 'QH2OSFC:A', 'QOVER:A','RAIN:A', 'QRUNOFF_R:A', 'QRUNOFF_U:A'

hist_mfilt = 1461,12

hist_nhtfrq = -24,0

fsurdat = '/home/zzw/software/inputdata/lnd/clm2/surfdata_map/release-clm5.0.18/surfdata_SHJ0.1X0.1_hist_16pfts_Irrig_CMIP6_simyr2000_c230328.nc'

flanduse_timeseries = '/home/zzw/software/inputdata/lnd/clm2/surfdata_map/landuse.timeseries_SHJ0.1X0.1_hist_16pfts_Irrig_CMIP6_simyr1850-2015_c230328.nc'

finidat='/home/zzw/software/inputdata/lnd/clm2/initdata_map/clmi.I2000Clm50BgcCrop.2011-01-01.1.9x2.5_gx1v7_gl4_simyr2000_c190312.nc'

use_init_interp = .true.

check_dynpft_consistency = .false.

./preview_namelists

./check_input_data

./case.build --skip-provenance-check

./case.submit

If you could give me some useful suggestions, then I would be very grateful！
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Normally, taxmode in your datm_in is set to "cycle" which means that when the end of the atmospheric data is reached (2014) the datm will cycle back to the first year of data (1996). So your model year 2015 is likely using 1996 forcing data. You can verify this by looking at your atm log to see what forcing files are read in.
 
A

akhtert

Tanjila Akhter
New Member
oleson said:
Normally, taxmode in your datm_in is set to "cycle" which means that when the end of the atmospheric data is reached (2014) the datm will cycle back to the first year of data (1996). So your model year 2015 is likely using 1996 forcing data. You can verify this by looking at your atm log to see what forcing files are read in.
Click to expand...
Hello, I have a related question to this. In the upper code, in
DATM_CLMNCEP_YR_ALIGN=1996, if I keep it as 1 (the default) instead, then how the forcing works? Will it still start from 1996?
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
That will mean that model year 1 will be aligned with forcing data year 1996. If your RUN_STARTDATE=0001-01-01, the the model will start with 1996 forcing data.
 
A

akhtert

Tanjila Akhter
New Member
oleson said:
That will mean that model year 1 will be aligned with forcing data year 1996. If your RUN_STARTDATE=0001-01-01, the the model will start with 1996 forcing data.
Click to expand...
What I get is, the RUN_STARTDATE is independent of these. I would want to double check for my case.

RUN_STARTDATE=1994-01-01
DATM_CLMNCEP_YR_ALIGN=1
DATM_CLMNCEP_YR_START=1994
DATM_CLMNCEP_YR_END=2014

I use the initial data (finidat =1994-01-01 from a previous run). I expect the simulation to use 1994-01-01 initial data and forcing. Please comment if I am correct. Thank you for your help. Much appreciated.

Tanjila
 
A

akhtert

Tanjila Akhter
New Member
akhtert said:
What I get is, the RUN_STARTDATE is independent of these. I would want to double check for my case.

RUN_STARTDATE=1994-01-01
DATM_CLMNCEP_YR_ALIGN=1
DATM_CLMNCEP_YR_START=1994
DATM_CLMNCEP_YR_END=2014

I use the initial data (finidat =1994-01-01 from a previous run). I expect the simulation to use 1994-01-01 initial data and forcing. Please comment if I am correct. Thank you for your help. Much appreciated.

Tanjila
Click to expand...
I already did the simulation for years. Does that mean I did not use correct forcing and I need to redo? Thank you again for your reply.
 
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I would look in your atm logs to see what forcing was being used for what model years to confirm.
 
A

akhtert

Tanjila Akhter
New Member
Thank you for the suggestion. I checked the atm log file for a run where:

RUN_STARTDATE=1979-01-01
DATM_CLMNCEP_YR_ALIGN=1
DATM_CLMNCEP_YR_START=1979
DATM_CLMNCEP_YR_END=2014

Here is the log file for the first submission where it ran for 4 years as STOP_N=48 and STOP_OPTION=nmonths. Form the log file I understand that it used the data for 2013 for the first year simulation. Please have a look and comment. Thank you again.
 
A

akhtert

Tanjila Akhter
New Member
akhtert said:
Thank you for the suggestion. I checked the atm log file for a run where:

RUN_STARTDATE=1979-01-01
DATM_CLMNCEP_YR_ALIGN=1
DATM_CLMNCEP_YR_START=1979
DATM_CLMNCEP_YR_END=2014

Here is the log file for the first submission where it ran for 4 years as STOP_N=48 and STOP_OPTION=nmonths. Form the log file I understand that it used the data for 2013 for the first year simulation. Please have a look and comment. Thank you again.
Click to expand...
 

Attachments

  • atm.log.1414985.desched1.230927-151320.gz
    334.2 KB · Views: 3
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
Yes, it looks like it was using 2013 at the beginning. You specified that you wanted model year 1 to line up with 1979 forcing. The datm is going to calculate how to accomplish that even though you aren't actually starting the model at year 1. So, since you are looping over 36 years of forcing, take the remainder of (1979-1)/36, which is 0.9444, and multiply that by 36, to get 34, then add 34 to 1979, to get 2013.
 
A

akhtert

Tanjila Akhter
New Member
oleson said:
Yes, it looks like it was using 2013 at the beginning. You specified that you wanted model year 1 to line up with 1979 forcing. The datm is going to calculate how to accomplish that even though you aren't actually starting the model at year 1. So, since you are looping over 36 years of forcing, take the remainder of (1979-1)/36, which is 0.9444, and multiply that by 36, to get 34, then add 34 to 1979, to get 2013.
Click to expand...
Thank you very much for the explanation. Much appreciated. Was a bit confused about how it works and now it is clear. Thank you again.
 
Status
Not open for further replies.
Top