Hi David,
Good idea! We'll just add these new axes to the file
climatological_axes that is distributed with Ferret, so they'll be
available along with the old ones. If anyone would like to replace
their
existing climatological_axes.cdf file from the Ferret distribution,
I've attached a climatological_axes.cdf with the ones we have always
had in the climatological_axes dataset, plus David's new ones. As
David says, TAX_GREGORIAN is the same as MONTH_IRREG. The existing
file can be found in $FER_DIR/go
yes? use climatological_axes
*** NOTE: regarding ./climatological_axes.cdf ...
*** NOTE: Climatological axes SEASONAL_REG, MONTH_REG, MONTH_IRREG,
TAX_GREGORIAN, TAX_NOLEAP, TAX_360_DAY defined.
(Note that the message is cut off by existing versions of Ferret; this
will be fixed in the next release)
Ansley
David Wang wrote:
Hi Ferreters,
I created three additional pre-defined monthly climatological axes in
the attached netcdf file. The purpose is to speed the common practice
of computing monthly climatologies and anomalies when the original data
are not defined on a Gregorian time axis. TAX_GREGORIAN is the same as
MONTH_IRREG in climatological_axes.cdf; TAX_NOLEAP is for NOLEAP
calendar axes, and TAX_360_DAY is for 360_DAY calendar axes.
Hope it helps,
David
yes? use climatological_axes.nc
*** NOTE:
regarding ./climatological_axes.nc ...
*** NOTE:
Climatological axes TAX_GREGORIAN, TAX_NOLEAP, TAX_360_DAY defined.
yes? show axis
tax_gregorian,tax_noleap,tax_360_day
name
axis # pts start end
TAX_GREGORIAN
TIME 12mi 16-JAN 12:00 15-DEC 17:49
T0 = 01-JAN-0000
00:00:00
Axis span (to
cell edges) = 365.2425 (modulo length = axis span)
TAX_NOLEAP
TIME 12mi 16-JAN 12:00 16-DEC 12:00
T0 = 01-JAN-0000
00:00:00
CALENDAR = NOLEAP
Axis span (to
cell edges) = 365 (modulo length = axis span)
TAX_360_DAY
TIME 12mr 16-JAN 00:00 16-DEC 00:00
T0 = 01-JAN-0000
00:00:00
CALENDAR = 360_DAY
Axis span (to
cell edges) = 360 (modulo length = axis span)
|