You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to inform you of a dating/time issue I noticed with the amwg diag package. The 12 monthly climo files produced by the package have incorrect "time" values. In that the number of days of the January file corresponds to midyear while the number of days in the June file corresponds to the end of the year. This could lead to a lot of confusion by netcdf readers like ncview.
For example:
ncdump -v time F2000.e106.f09f09.raijin.PD_ctrl_01_climo.nc
leads to the following output
...
time = 14448.5 ;
}
14448.5 is halfway through the year and so ncview will display July for this month, even though it's January. I hope that makes sense.
From @cecilehannay on April 21, 2017 20:57
Dear Cecile
I just wanted to inform you of a dating/time issue I noticed with the amwg diag package. The 12 monthly climo files produced by the package have incorrect "time" values. In that the number of days of the January file corresponds to midyear while the number of days in the June file corresponds to the end of the year. This could lead to a lot of confusion by netcdf readers like ncview.
For example:
ncdump -v time F2000.e106.f09f09.raijin.PD_ctrl_01_climo.nc
leads to the following output
...
time = 14448.5 ;
}
14448.5 is halfway through the year and so ncview will display July for this month, even though it's January. I hope that makes sense.
Kind regards
Nicholas.
Copied from original issue: CESM-Development/cime#489
The text was updated successfully, but these errors were encountered: