problem with own atmosphere data error

[qian yang]

Dear all
I want to use my own atmforcing data to run a regional case in CLM5.0,and I have processed it the standard format as GSWP3, i.e., monthly precip, solar and tphwl, meanwhile made a domain file for the atm foring) to replace, but I have met some problems:
my forcing data has 3 h temporal resolution and spatial resolution is 0.1x0.1.

error
(shr_dmodel_readstrm) file ub: /home/aircas/cesm/inputdata/atm/datm7/solar/clmforc.0.1x0.1.solar-2010-03.nc 25
(shr_stream_verifyTCoord) ERROR: calendar dates must be increasing
(shr_stream_verifyTCoord) date(n), date(n+1) = 20100303 20100301
ERROR: (shr_stream_verifyTCoord) ERROR: calendar dates must be increasing

I do not know why it happened. I run the case during Jan. or Feb. ,there is no error happened. I try the different year. The same error happened during Mar.
But I create the atmforcing data by the same way .

Can anyone help me ?

 

[oleson]

This indicates either a problem with the time dimension in one of your forcing files or possibly how your forcing files are referenced in your data.streams files. Search for "calendar dates must be increasing" in the Forums to find possible causes and solutions.

 

[qian yang]

dear oleson
thank you for your reply. But I still don not find solution. Can you help me?
I used ncdump -v time clmforc.0.1x0.1.solar-2010-03.nc to check the time dimension of the forcing files. But I can not find error. I also check the data.streams files ,do not find problems either. is there other files should I check?
ncdump -v time clmforc.0.1x0.1.solar-2010-03.nc
netcdf clmforc.0.1x0.1.solar-2010-03 {
dimensions:
scalar = 1 ;
lon = 700 ;
lat = 400 ;
time = 248 ;
variables:
float time(time) ;
time:long_name = "observation time" ;
time:units = "days since 2010-03-01 00:00:00" ;
time:calendar = "noleap" ;
float LONGXY(lat, lon) ;
LONGXY:long_name = "longitude" ;
LONGXY:units = "degrees_east" ;
LONGXY:mode = "time-invariant" ;
float LATIXY(lat, lon) ;
LATIXY:long_name = "latitude" ;
LATIXY:units = "degrees_north" ;
LATIXY:mode = "time-invariant" ;
float EDGEE(scalar) ;
EDGEE:long_name = "eastern edge in atmospheric data" ;
EDGEE:units = "degrees_east" ;
EDGEE:mode = "time-invariant" ;
float EDGEW(scalar) ;
EDGEW:long_name = "western edge in atmospheric data" ;
EDGEW:units = "degress_east" ;
EDGEW:mode = "time-invariant" ;
float EDGES(scalar) ;
EDGES:long_name = "southern edge in atmospheric data" ;
EDGES:units = "degrees_north" ;
EDGES:mode = "time_invariant" ;
float EDGEN(scalar) ;
EDGEN:long_name = "northern edge in atmospheric data" ;
EDGEN:units = "degrees_north" ;
EDGEN:mode = "time-invariant" ;
float FSDS(time, lat, lon) ;
FSDS:long_name = "total incident solar radiation" ;
FSDS:units = "W/m**2" ;
FSDS:mode = "time-dependent" ;
FSDS:missing_value = -32767 ;
FSDS:_FillValue = -32767.f ;

// global attributes:
:source_file = "srad_ITPCAS-CMFD_V0106_B-01_03hr_010deg_201003.nc" ;
:case_title = "3-hourly surface downward shortwave radiation from the ITPCAS China Meteorological Forcing Dataset" ;
data:

time = 0, 0.125, 0.25, 0.375, 0.5, 0.625, 0.75, 0.875, 1, 1.125, 1.25,
1.375, 1.5, 1.625, 1.75, 1.875, 2, 2.125, 2.25, 2.375, 2.5, 2.625, 2.75,
2.875, 3, 3.125, 3.25, 3.375, 3.5, 3.625, 3.75, 3.875, 4, 4.125, 4.25,
4.375, 4.5, 4.625, 4.75, 4.875, 5, 5.125, 5.25, 5.375, 5.5, 5.625, 5.75,
5.875, 6, 6.125, 6.25, 6.375, 6.5, 6.625, 6.75, 6.875, 7, 7.125, 7.25,
7.375, 7.5, 7.625, 7.75, 7.875, 8, 8.125, 8.25, 8.375, 8.5, 8.625, 8.75,
8.875, 9, 9.125, 9.25, 9.375, 9.5, 9.625, 9.75, 9.875, 10, 10.125, 10.25,
10.375, 10.5, 10.625, 10.75, 10.875, 11, 11.125, 11.25, 11.375, 11.5,
11.625, 11.75, 11.875, 12, 12.125, 12.25, 12.375, 12.5, 12.625, 12.75,
12.875, 13, 13.125, 13.25, 13.375, 13.5, 13.625, 13.75, 13.875, 14,
14.125, 14.25, 14.375, 14.5, 14.625, 14.75, 14.875, 15, 15.125, 15.25,
15.375, 15.5, 15.625, 15.75, 15.875, 16, 16.125, 16.25, 16.375, 16.5,
16.625, 16.75, 16.875, 17, 17.125, 17.25, 17.375, 17.5, 17.625, 17.75,
17.875, 18, 18.125, 18.25, 18.375, 18.5, 18.625, 18.75, 18.875, 19,
19.125, 19.25, 19.375, 19.5, 19.625, 19.75, 19.875, 20, 20.125, 20.25,
20.375, 20.5, 20.625, 20.75, 20.875, 21, 21.125, 21.25, 21.375, 21.5,
21.625, 21.75, 21.875, 22, 22.125, 22.25, 22.375, 22.5, 22.625, 22.75,
22.875, 23, 23.125, 23.25, 23.375, 23.5, 23.625, 23.75, 23.875, 24,
24.125, 24.25, 24.375, 24.5, 24.625, 24.75, 24.875, 25, 25.125, 25.25,
25.375, 25.5, 25.625, 25.75, 25.875, 26, 26.125, 26.25, 26.375, 26.5,
26.625, 26.75, 26.875, 27, 27.125, 27.25, 27.375, 27.5, 27.625, 27.75,
27.875, 28, 28.125, 28.25, 28.375, 28.5, 28.625, 28.75, 28.875, 29,
29.125, 29.25, 29.375, 29.5, 29.625, 29.75, 29.875, 30, 30.125, 30.25,
30.375, 30.5, 30.625, 30.75, 30.875 ;
}

 

[qian yang]

I try to use the Jan. solar data to replace the Mar. solar data I change replace time@units="days since 2010-01-01 00:00:00" with" days since 2010-03-01 00:00:00".Because the two file are the same time dimension except time@units. then submit the case
The error happened
(shr_stream_verifyTCoord) date(n), date(n+1) = 20100228 20100101
so I think there is something still relevant the calendar dates except the time dimension. But I do not know what it is.

 

[oleson]

The atm log indicates that although you are starting at March 1, the datm is starting by reading in time samples 225 and 226 from February for precipitation, which is almost 3 days off. So I would look at the time dimension in your precipitation forcing files, in particular, look at the time@units and time values in your February and March files.

 

[qian yang]

dear oleson
thank you for your patient answer. I found the time dimension for the February precipitation forcing file was wrong. Now I can run it successfully.
And can you tell me why the time-stamps of the data should be adjusted so that they are the beginning of the interval for solar, and the middle for the other two. why their time-stamps should be different.

 

[oleson]

They use different interpolation methods and so require different time stamps. Solar is needed at the beginning of the interval in order to properly distribute it over the interval.

 

[qian yang]

thank you for your help . I got it.