Missing_values in CMOR output when running cdo info
Added by Fabian Wachsmann over 5 years ago
This subject is from a user who got lost in between CDO and CMOR, see https://github.com/PCMDI/cmor/issues/505.
I think it could be a CDO issue so I open it here.
I’m running the examples for GPCP monthly and daily files, CMOR version 3.4.0 and Python 2.7.15. The cmor output files show all nan and missing values using cdo infon, although the values are identical with the input files using ncdump.
@jhz0
Is the output of GPCP examples accessible for me? Or can I reproduce what you did?
Otherwise, could you add it here and give us information about the CDO Version you are using?
Best regards,
Fabi
Replies (2)
RE: Missing_values in CMOR output when running cdo info - Added by judy hertz over 5 years ago
Thanks for your help. Was using 1.9.1 so doing a quick test with 1.9.7 and will report back.
RE: Missing_values in CMOR output when running cdo info - Added by judy hertz over 5 years ago
It turns out the CMOR demo script includes attributes for valid_min and valid_max, which I hadn't used before and neglected to comment out or edit for values appropriate to my variable. Once I removed it or added appropriate values the issue went away. It seems that cdo info was working properly to filter the out-of-range values but if that's not the case, let me know and I will test further. thanks Fabi!