[Thread Prev][Thread Next][Index]

Re: [ferret_users] **TMAP ERR: Message not found



Richard,
Good clue. It's true that the syntax parsing for Ferret, and the plotting routines that it uses to convert time steps to dates, do not allow for years with more than four digits.  So the first of these is OK but the second is not.
yes? define axis/t=9001:11000:`1:12`/units=years tlong

yes? define axis/t=1-jan-9999:1-jan-11000:1/units=months tlong
 **ERROR: command syntax: 1-jan-10001
One possibility for working around this might be to regrid to an axis with units of years (if that makes any sense for your data), as in the first example above.

Another idea, to at least be able to look at the data, is to define a time axis of the same length and units, but ending before the year 10000. (3000 years earlier perhaps?) Then regrid using the @ASN regridding transformation.  The dates wouldn't be the same as the model output but Ferret should then be able to handle everything.

Ansley

Richard Slater wrote:
Leela,

I have not tried it recently, but there used to be a fatal error in ferret whenever one plotted time axes with years of 5 digits. I always needed to do a "cancel mode calendar" before doing the plots. Unfortunately, the plots then use the underlying time unit, which was seconds, in my case.

Hope this helps.

Rick

Leela Frankcombe wrote:
Dear ferret users,

I've got a (hopefully simple) problem that has been plaguing me for the last few days. I have data from a model run that spans model years 9001 to 12000 but I can't seem to get ferret to do anything with the years after 10000. I can plot years 9001 to 9999, but put in that extra year and I get an error message: **TMAP ERR: Message not found. Any ideas?

Thanks,
Leela.

-- 

~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~> 

Ansley Manke, NOAA/PMEL   ansley.b.manke@xxxxxxxx
7600 Sand Point Way NE, Seattle WA
Phone 206-526-6246,  FAX 206-526-6744


[Thread Prev][Thread Next][Index]

Contact Us
Dept of Commerce / NOAA / OAR / PMEL / TMAP

Privacy Policy | Disclaimer | Accessibility Statement