|
Hi Ryo,
Thank you for the report. We've had another report of a bug with
modulo time axes that seem to be related to the new handling of
coordinate data as dynamically allocated storage. I suspect this
is also associated with that. Please watch for an update once we
get this sorted out.
Ansley
On 12/20/2017 10:32 AM, Ryo Furue
wrote:
Hi Ferret users,
I must be missing something but I haven't been able to use
the 360_day calendar with an mc (multi-CDF) file.
(This sample mc
file is shown below.) It's 360 days after "1-JAN-1900
00:00", which should be displayed as "1-JAN-1901
00:00 360_DAY".
Incidentally,
I came across this strange result:
yes? define
axis/calendar=360_day\
/t0="01-JAN-1900
00:00:00"/units=days/t=360:360:1 mytax
TIME
: 01-JAN-1901 00:00 360_DAY
When
first listed, the time axis uses the 360_day calendar, but
after test.mc is loaded, it's switched
to another calendar.
Regards,
Ryo
---- test.mc:
Ferret's etopo20.cdf is wrapped in it. ----------
&FORMAT_RECORD
D_TYPE = 'MC' ,
D_FORMAT = '1A',
/
&BACKGROUND_RECORD
D_TITLE = 'test mc file',
D_T0TIME = '01-JAN-1900 00:00:00',
D_TIME_UNIT = 86400.0,
D_CALTYPE = '360_DAY',
/
&MESSAGE_RECORD
D_MESSAGE = ' ',
D_ALERT_ON_OPEN = F,
D_ALERT_ON_OUTPUT = F,
/
&EXTRA_RECORD
/
&STEPFILE_RECORD
S_FILENAME = 'etopo20.cdf'
S_AUX_SET_NUM = 0,
S_START = 360,
S_END = 360,
S_DELTA = 1,
S_NUM_OF_FILES = 1,
S_REGVARFLAG = ' ',
/
&STEPFILE_RECORD
s_filename = '**END OF STEPFILES**'
/
---- Ferret version -----------
$ ferret
NOAA/PMEL
TMAP
FERRET
v7.3 (optimized)
Linux
2.6.32-696.13.2.el6.x86_64 64-bit - 12/04/17
21-Dec-17
03:14
|