timestat_date and export CDO_TIMESTAT_DATE no effect on ymon or yseas
Added by Mika Lanzky over 3 years ago
Does timestat_date only work on non-multi year statisticals?
I use ymonmean and yseasmean on my data set to make multi-year climatology.
My file has reverse time axis from normal - so newest date is first entry.
The output for the montlhy and seasonal do not use the same type of timestamps. Monthly use the oldest timestamps (or the last ones in the file), and yearly use the newest time stamp (or first in the file).
Would be nice if this was the same.
I tried using timestat_date and also CDO_TIMESTAT_DATE. But it has no effect, the respective output for yearly and monthly are unaffected by the setting.
Is timestat_date only defined for not-multi-year?
I understand that having a mean going across years and months makes first, middle, and last mean more than just (1., 15. and 31.) if it was dates.
Is there another control on how to set the timestamps for multi-year statistics? At least it would be nice to have the same default behaviour across the different multi-year choices.
Replies (1)
RE: timestat_date and export CDO_TIMESTAT_DATE no effect on ymon or yseas - Added by Uwe Schulzweida over 3 years ago
Yes, the CDO option timestat_date works only on non-multi year statistics!
You can use the CDO operator settaxis to set the date and time to your preferred values.