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

Why the date of the atm forcing did not match the date model starts?

xiaoxiaokuishu

Ru Xu
Member
Hi, all,
I run a single-point simulation in ctstmdev040 model, when I set

/xmlchange DATM_CLMNCEP_YR_START=2001
./xmlchange DATM_CLMNCEP_YR_END=2010
./xmlchange DATM_CLMNCEP_YR_ALIGN=2001

the streams = "datm.streams.txt.CLM1PT.CLM_USRDAT 2001 2001 2010" is correct,
My runstartdate is 1993-01-01, but when I check the atm.log files, I can see the model use 2003-01 for 1993-01...
the 1993-01 should use the data of 2001-01, right? do you know what happens.

Additional information, in my simulation, I combine the scattered variables into one nc,
that is datm.Solar, datm.Pre, datm.TPHW into one nc, in my case it is 2001-01.nc... not *Solar-2001-01.nc

not sure is that because of the combine process...
I attach part of atm.log and user_xx file for your reference......
 

Attachments

  • tocesm-for.zip
    34.1 KB · Views: 0

slevis

Moderator
Staff member
If your run starts in 1993 and you want to read 2001 for that year, then I think you should
./xmlchange DATM_CLMNCEP_YR_ALIGN=1993
If this works the way I think, then you will align model year 1993 with the 2001 datm data. This also means that model year 2001 will align with the 1999 datm data. Are you sure you want that? If not, then maybe you had it correct to begin with.
 
Top