Welcome to the new DiscussCESM forum!
We are still working on the website migration, so you may experience downtime during this process.

Existing users, please reset your password before logging in here: https://xenforo.cgd.ucar.edu/cesm/index.php?lost-password/

clm making forcing data problem and running error

syang

Shawn Yang
New Member
Dear all,

I made my own clm meterological forcing data by python, xarray package. I followed the forcing data "GSWP3v1" format. However, the coordinate "time" in GSWP showed float values and the unit is "days since...". I tried the python fucntion "cftime.num2date()" and set the unit as "days since..." to create the coordinate "time" for my own forcing data. However, the values of "time" are "int" format and the unit is "hours since...". The error "calendar dates must be increasing" showed up in the model when I used my own forcing data running over one month. However, if I run the model less than a month, no error showed up and it looks like it worked fine.

I attached the figures below to show the difference between them. I would like to ask how to create the coordinate "time" to meet the requirement of the clm model. Is there a template I can follow? And how to solve this running problem. THANKS!!!
 

Attachments

  • GSWP.png
    GSWP.png
    50.3 KB · Views: 6
  • Heihe.png
    Heihe.png
    32.9 KB · Views: 6
  • cftime_python.png
    cftime_python.png
    12.8 KB · Views: 6
  • cftime_coordinate_python.png
    cftime_coordinate_python.png
    3.7 KB · Views: 6
  • atm.log.1715953.210519-101726.txt
    469.7 KB · Views: 3
  • cesm.log.1715953.210519-101726.txt
    19.3 KB · Views: 2

oleson

Keith Oleson
CSEG and Liaisons
Staff member
The error could be related to the time coordinate of the second monthly file (2000-02?). It should look like something similar to the GSWP3 data:

float time(time) ;
time:long_name = "observation time" ;
time:units = "days since 2000-02-01 00:00:00" ;
time:calendar = "noleap" ;

time = 0.0625, 0.1875, 0.3125, 0.4375, 0.5625, 0.6875, 0.8125, 0.9375,...

Regarding your python questions, I don't have any python expertise, but maybe this example, which extracts domain files, surface dataset, and DATM files at either a single point or a region using the global dataset, would help:

 

syang

Shawn Yang
New Member
The error could be related to the time coordinate of the second monthly file (2000-02?). It should look like something similar to the GSWP3 data:

float time(time) ;
time:long_name = "observation time" ;
time:units = "days since 2000-02-01 00:00:00" ;
time:calendar = "noleap" ;

time = 0.0625, 0.1875, 0.3125, 0.4375, 0.5625, 0.6875, 0.8125, 0.9375,...

Regarding your python questions, I don't have any python expertise, but maybe this example, which extracts domain files, surface dataset, and DATM files at either a single point or a region using the global dataset, would help:

Thanks! I will take a look at this example.
 
Top