wrong number of processed timesteps
Added by Josué Bock about 4 years ago
Hello,
When processing a file (cdo yearmonmean), the output message indicating the number of processed variable(s) and timestep(s) displays a wrong number of timesteps (2144 instead of 1980 in the current example).
> ncdump -h semfgdms_Omon_UKESM1-0-LL_historical_r1i1p1f2_gn_185001-201412_mergetime.nc | grep currently
time = UNLIMITED ; // (1980 currently)
> cdo yearmonmean semfgdms_Omon_UKESM1-0-LL_historical_r1i1p1f2_gn_185001-201412_mergetime.nc semfgdms_Omon_UKESM1-0-LL_historical_r1i1p1f2_gn_185001-201412_mergetime_yearmonmean.nc
cdo yearmonmean: Processed 1 variable over 2144 timesteps [0.34s 24MB].
The file is attached.
Is it a bug, or is there something that i misunderstand?
Cheers
Replies (2)
RE: wrong number of processed timesteps - Added by Uwe Schulzweida about 4 years ago
This operator is reading the first timestep of each year twice. This is necessary to find the end of a year.
RE: wrong number of processed timesteps - Added by Josué Bock about 4 years ago
Thanks for the explanation.
Despite the outfile was correct, that is a bit confusing to see that the number of processed (not read) timesteps doesn't match the actual number of timesteps. Now i know why.