[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010315: Problem with dattim in gempak 5.6.a

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20010315: Problem with dattim in gempak 5.6.a
  • Date: Thu, 15 Mar 2001 13:08:02 -0700
Greg,

You do not have to change dattim format entries from 5.4. to 5.6.
The dattim is yymmdd/hhnn not 4 digit years.

GEMPAK handles 4 digit years internally, but the format for
dattim entry in the programs is still the same. It assumes that
if yy < 20 then it is 20yy, otherwise 19yy.

Steve Chiswell

On Thu, 15 Mar 2001, Greg Stossmeister wrote:

> Steve,
>    I have some scripts that I had been formerly running under gempak5.4
> with no trouble. I tried updating those script now to use gempak5.6.a
> and am having some trouble. I'm using a date/time for example of
> 20010315/0000f000. Gempak complains:
> 
> [TG -1] Invalid date or time.
> [TG -5] Invalid time range.
> [TG 0]
> 
> I find if I set dattim=010315/0000f000 gempak will produce the plot -
> what gives? I though Gempak could handle 4 digit years now.
> 
> Greg
>