Unexpected behaviour of ydaypctl
Added by Stefano Materia over 2 years ago
Hi all,
I am getting headache using the ydaypctl function.
My commands
cdo -O -runmean,5 -select,season=MAM ./anom/t2mmax_land_dyanom_wmed_spave_1950-2021.nc outfile.nc
export CDO_PCTL_NBINS=651
cdo -O -ydaypctl,90 outfile.nc -ymonmin outfile.nc -ymonmax outfile.nc ./anom/t2mmax_land_dyanom_wmed_spave_MAM90pc.nc
The output
+ cdo -O -runmean,5 -select,season=MAM ./anom/t2mmax_land_dyanom_wmed_spave_1950-2021.nc outfile.nc
cdo(1) select: Process started
cdo(1) select: Processed 6624 values from 1 variable over 26190 timesteps.
cdo runmean: Processed 6624 values from 1 variable over 6624 timesteps [1.90s 45MB].
+ export CDO_PCTL_NBINS=651
+ CDO_PCTL_NBINS=651
+ cdo -O -ydaypctl,90 outfile.nc -ymonmin outfile.nc -ymonmax outfile.nc ./anom/t2mmax_land_dyanom_wmed_spave_MAM90pc.nc
cdo(1) ymonmin: Process started
cdo(2) ymonmax: Process started
cdo ydaypctl (Abort): No data for day 65 in (pipe1.3) and (pipe1.5)
terminate called without an active exception
terminate called without an active exception
./era5_tmax_euregions.sh: line 78: 164524 Aborted cdo -O -ydaypctl,90 outfile.nc -ymonmin outfile.nc -ymonmax outfile.nc ./anom/t2mmax_land_dyanom_${region}_spave_MAM90pc.nc
I really do not understand what is going on, in the beginning I thought the problem was related to the moving average, but I get the same output when "-runmean,5" is removed.
For ease, I attach the input file outfile.nc
outfile.nc (354 KB) outfile.nc |
Replies (1)
RE: Unexpected behaviour of ydaypctl - Added by Stefano Materia over 2 years ago
SOLVED.
There was a bug in my code that I couldn't spot.
cdo -O -ydaypctl,90 outfile.nc -y*mon*min outfile.nc -y*mon*max outfile.nc ./anom/t2mmax_land_dyanom_wmed_spave_MAM90pc.nc
should have been
cdo -O -ydaypctl,90 outfile.nc -y*day*min outfile.nc -y*day*max outfile.nc ./anom/t2mmax_land_dyanom_wmed_spave_MAM90pc.nc