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

Additional an-hour output in CLM run

Hi all,
I ran a simulation with CLM and set a list of history fields by adding to the user_nl_clm as follows:

hist_mfilt=24,24
hist_nhtfrq=-1,-1


Moreover, I set the RUN_STARTDATE, START_TOD and STOP_N/STOP_OPTION variables for my case to run over the entire time extent of my data as follows:

./xmlchange --file env_run.xml --id DATM_CLMNCEP_YR_START --val 2013
./xmlchange --file env_run.xml --id DATM_CLMNCEP_YR_END --val 2013
./xmlchange --file env_run.xml --id DATM_CLMNCEP_YR_ALIGN --val 2013
./xmlchange --file env_run.xml --id RUN_STARTDATE --val 2013-01-01
./xmlchange --file env_run.xml --id START_TOD --val 00000
./xmlchange --file env_run.xml --id STOP_OPTION --val ndays
./xmlchange --file env_run.xml --id STOP_N --val 365
./xmlchange --file env_run.xml --id NCPL_BASE_PERIOD --val day

However, final output files shown a period from 2013-01-01-00:00 to 2014-01-01-00:00, that have one unexpected extra hour (365*24+1) output compared to my setting (365*24). I wonder konw why it occurred.

Thanks a lot for any suggestions!
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
For history output other than monthly average (e.g., hourly, daily, yearly), the first time sample is output from an initialization step and should be ignored. The first "real" time sample is the second one.
 
For history output other than monthly average (e.g., hourly, daily, yearly), the first time sample is output from an initialization step and should be ignored. The first "real" time sample is the second one.
Hi Oleson,

Thanks for the reply. This is very helpful to me.
 
Top