Project

General

Profile

Possible bug in CDO 2.0.4 regarding yseas.

Added by Abdul Azim Amirudin about 2 years ago

Any command involving "yseas" will produced weird results, as example:

cdo yseasstd infile outfile

-1 : Date Time Level Gridsize Miss : Minimum Mean Maximum : Parameter ID
1 : 2005-02-28 00:00:00 0 12000 12000 : nan : -1
2 : 2005-05-31 00:00:00 0 12000 12000 : nan : -1
3 : 2005-08-31 00:00:00 0 12000 12000 : nan : -1
4 : 2005-11-30 00:00:00 0 12000 12000 : nan : -1

When I do the same command on other version, the only old version that I had was 1.9.3.

-1 : Date Time Level Gridsize Miss : Minimum Mean Maximum : Parameter ID
1 : 2005-02-28 00:00:00 0 12000 5551 : 0.72038 0.85158 1.0061 : -1
2 : 2005-05-31 00:00:00 0 12000 5551 : 0.77867 0.90541 1.1183 : -1
3 : 2005-08-31 00:00:00 0 12000 5551 : 0.75364 0.87955 1.1136 : -1
4 : 2005-11-30 00:00:00 0 12000 5551 : 0.72366 0.82841 1.0406 : -1

Which makes more sense since it is a temperature gridded data. I try with my other laptop with the same exact CDO version and it produced the same problem. yseasmean, yseassum, all produced weird results. seas is fine, ymon or other y command is fine, but only yseas had this problem. Does anyone else have this problem too?


Replies (2)

RE: Possible bug in CDO 2.0.4 regarding yseas. - Added by Uwe Schulzweida about 2 years ago

This bug was fixed in release 2.0.5, see also #10615.

RE: Possible bug in CDO 2.0.4 regarding yseas. - Added by Abdul Azim Amirudin about 2 years ago

Thanks for the reply, I will update to the newer one.

    (1-2/2)