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

problem about setting of RUN_STARTDATE in compsete CIAF for running from a particular year

Hi,

I am using CIAF in cesm1_2_0. The COREv2 is used as inputdata for compset CIAF. When I set RUN_STARTDATE as "0001-01-01", the model reads inputdata of year 1948 at the first, which can be seen in atm log. When I set it as "1948-01-01", model reads inputdata of year 1973 at the first. Also,I find a rule that, if I want model to read inputdata of year 2000 at first, just set RUN_STARTDATE as 0053-01-01. Here "53" comes from 2000-1948+1=53.

I want to know where to reflect this problem in the F90 code. And, can model start to read inputdata of year 1948 at first if I set RUN_STARTDATE as "1948-01-01"? Because it will be easier to recognize. How to do that?

Thank you very much.

Best regards,
Yao
 

njn01

Member
There is some information about the CIAF and GIAF compsets in the POP2 FAQ in the "Interannual Forcing (IAF) Compsets" section that you may find helpful.
The CESM1.2 version of this FAQ is http://www.cesm.ucar.edu/models/cesm1.2/pop2/doc/faq/#IAF
 
Thank you very much.There are 5 cycles from years 1 to 310. Different cycle have different meaning. If I set RUN_STARTDATE as "0001-01-01", model will read inputdata of 1948. But the name of first year in output files will be "0001-01-01", not "1948-01-01". If I set RUN_STARTDATE as "1948-01-01", the name of first year in output files will be "1948-01-01", but model wil read inputdata of 1973, rather than 1948.  
 
As njn01 said, we should read the FAQ for POP2 carefully.  The RUN_STARTDATE should be set as "0001-01-01", and the model will run start in 1948. For example, the output history data corresponds to the 1948-01, if its name " *h.0001-01.nc".  The output history data corresponds to the 1948-05, if its name " *h.0001-05.nc", and so on.
 
Top