dt limit for stream error with my own atmospheric forcing (global run)

Status
Not open for further replies.

hannah0304

New Member
Hello,

I am trying to run global CLM run with my own atmospheric forcings.
I am getting dt limit error, which I am not sure how to solve it.

Here are the details of my problem.

=======
- CESM version: cesm2.2.0-0-g332937b

=======
- My forcing file info:
spatial resolution: 0.5 (lat) x 0.625 (lon)
time unit: minutes since 2001-01-01 06:00:00 (for year 2001)
data: 6-hourly atm. data (precipitation, incoming solar, pressure, specific humidity, air temperature, wind speed)

=======
- Steps I have done so far
1) created the domain of 0.5x0.625 resolution with following steps (domain info attached: newdomaininfo.zip)
=> SCRIP grid file creation with mkscripgrid.ncl
=> map file creation with 'gen_cesm_maps.sh'
./gen_cesm_maps.sh --fileatm ~/CESM2/components/clm/tools/mkmapgrids/SCRIPGrid_geos_s2s_0.5x0.625.nc --fileocn ~/CESM2/components/clm/tools/mkmapgrids/SCRIPGrid_geos_s2s_0.5x0.625.nc --nameatm geos_s2s_0.5x0.625 --nameocn geos_s2s_0.5x0.625 --typeatm global --typeocn global --serial -rc
=> domain file creation with 'gen_domain'
./gen_domain -m /home/hannahoh407/CESM2/cime/tools/mapping/gen_mapping_files/map_geos_s2s_0.5x0.625_TO_geos_s2s_0.5x0.625_aave.241016.nc -o navy -l 0.5x0.625

2) case setup
=> compset: 2000_DATM%CRUv7_CLM50%BGC_SICE_SOCN_SROF_SGLC_SWAV
=> xmlchange
./xmlchange DATM_MODE=CLMCRUNCEPv7
./xmlchange DATM_CLMNCEP_YR_START=$YRSTART
./xmlchange DATM_CLMNCEP_YR_END=$YREND
./xmlchange DATM_CLMNCEP_YR_ALIGN=1

./xmlchange STOP_OPTION=nmonths
./xmlchange STOP_N=3
./xmlchange RUN_STARTDATE=2001-01-01

./xmlchange DIN_LOC_ROOT_CLMFORC="/data2/hannah/BC_forecast_jan01_M2/2001/jan01/ens1"
./xmlchange ATM_DOMAIN_PATH=$DIN_LOC_ROOT/share/domains/domain.clm
./xmlchange LND_DOMAIN_PATH=$DIN_LOC_ROOT/share/domains/domain.clm
./xmlchange RUN_TYPE=startup

3) write user_user_datm.streams.txt for Precip, Solar, TPQW (files attached)
=> I wrote these text files by modifying those for CRUNCEPv7.
=> I have set the offset to -10800 for Precip and TPQW since my forcing data's timestamp is aligned with solar (beginning of the time interval)
as suggested in the link: 1.2.4. Customizing the DATM namelist — ctsm release-clm5.0 documentation


4) change the timestamp of my forcing data as CRUNCEPv7. (time info attached: geos_info.txt)
=> my forcing data timestamp was in the form of 'minutes since 2001-01-01 06:00:00'. So, I changed timestamp into the form of 'days since 2001-01-01 00:00:00'.
=> I have attached the result of 'ncdump -v time 'my_atm_file.nc'' below.

5) error message from atm.log (log files attached)
1729192517200.png
so, in my understanding, it fails to read from the first step..


=====
I would really appreciate any suggestion to this problem.
Thank you.
 

Attachments

slevis

Moderator
Staff member
Initially I would suggest that you browse through the Forums searching for threads addressing dtlimit problems using the search button near the top. I'm hoping that you will find threads that encountered the same or similar errors. Please post back here when you have an update.
 

hannah0304

New Member
Hello, all.
I figured that this is because of the dtlimit checking the cycles of the atmospheric forcing as well.
I have went through all the previous discussions of dtlimit and got a hint for the solution.
I have set the dtlimit to a large number and it solved the problem.
 
Status
Not open for further replies.
Back
Top