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

Issue with Long-Term CLM5 Simulation Using Custom Input Data

lfu

Dylan Fu
New Member
Hi,

I ran a single-point, long-term time-series simulation in CLM5 using my own input data.

I made the following changes in env_run.xml:
./xmlchange DATAM_MODE=CLM1PT
./xmlchange PTS_LAT=10.8785
./xmlchange PTS_LON=274.6594
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=86
./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2100
./xmlchange DATM_YR_END=2014
./xmlchange CLM_USRDAT_NAME=monthly370
./xmlchange CLM_USRDAT_DIR=/glade/derecho/scratch/lfu/ssp_atm_input/IPSL-CM6A-LR/CR_single_sites
Additionally, I added the following input paths in user_nl_datm_streams:
CLM_USRDAT.monthly585:year_first=2015
CLM_USRDAT.monthly585:year_last=2100
CLM_USRDAT.monthly585:year_align=2015
CLM_USRDAT.monthly585:dtlimit=1.5
CLM_USRDAT.monthly585:offset=0
CLM_USRDAT.monthly585:tintalgo=nearest
CLM_USRDAT.monthly585:mapalgo=nn
CLM_USRDAT.monthly585:taxmode=cycle

Issue Description

The model ran successfully. However, when I loaded the output NetCDF file, I noticed that the time coordinate in the dataset spans from 2000 to 2086 (as shown in the attached figure).

Additionally, the simulated temperature suddenly decreases sharply after 15 years from the start of the simulation.

I am unsure what might be causing this issue. Could you please help me identify the problem?

Thank you!
 

Attachments

  • nc_file.jpg
    nc_file.jpg
    86.9 KB · Views: 3
  • temp_plot.jpg
    temp_plot.jpg
    64.4 KB · Views: 3

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I would look at your RUN_STARTDATE in env_run.xml. Is it consistent with the date you want to start the model at?
These settings also seem inconsistent:

./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2100
./xmlchange DATM_YR_END=2014

Do you want:

./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2015
./xmlchange DATM_YR_END=2100

What years do your forcing data span?
 

lfu

Dylan Fu
New Member
I would look at your RUN_STARTDATE in env_run.xml. Is it consistent with the date you want to start the model at?
These settings also seem inconsistent:

./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2100
./xmlchange DATM_YR_END=2014

Do you want:

./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2015
./xmlchange DATM_YR_END=2100

What years do your forcing data span?
Oh I wrote above is incorrect. When I ran the model, I set the date as following in my env_run.xml:
./xmlchange DATM_YR_ALIGN=2015
./xmlchange DATM_YR_START=2015
./xmlchange DATM_YR_END=2100

My forcing data span from 2015-01 to 2100-12, I added the path in user_nl_datm_streams.
My case path is in u/home/lfu/CostaRica_single_b_ssp/I2000_CTSM_singlept_single_b_CR_N1_ssp370/
Thank you!
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
./xlmquery RUN_STARTDATE in your case directory yields:

RUN_STARTDATE: 2000-01-01

I assume you want to start the model in 2015? If so, you should set RUN_STARTDATE to 2015-01-01
 
Top