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.
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.