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

19991229: GARP is not quite Y2K compliant!

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: 19991229: GARP is not quite Y2K compliant!
  • Date: Thu, 30 Dec 1999 09:58:50 -0700
David,

COMET did notifyme of the availability for Garp 2.1 on late on the day 
Dec 17 just before I left for Christmas. I will Make sure that the 2.1 
distribution does address your problem and make a release.

Steve Chiswell


>From: David Ovens <address@hidden>
>Organization: .
>Keywords: 199912292227.PAA23439

>Unidata Support wrote:
>> 
>> >From: David Ovens <address@hidden>
>> >Organization: University of Washington
>> >Keywords: 199912291618.JAA09839 GARP Y2K
>> 
>> David-
>> 
>> >I have generated some GEMPAK files with dates of 000101/1200 F00
>> >through F12.  Garp is labelling the date as Jan 01 1970, but is
>> >listing these times after 991229/ stuff in the "Model Plan View"
>> >window.  So, it looks like part of it thinks it's the year 2000 while
>> >another part thinks it's 1970.  Any idea on how to easily fix this?
>> 
>> Steve Chiswell is out of town until next week and he knows the most
>> about GARP's inner workings.  In the mean time, can you put one of
>> your grid files out on an FTP site so I can download it and take
>> a look?  For the files we have that have forecast periods into
>> the new year, the labelling is correct.  But they all have analysis
>> times before the new year.
>> 
>> I'm a little unclear about what you mean in the second sentence.
>> Could you please clarify this?
>> 
>> Don Murray
>
>Don,
>
I have placed two Y2K files into ftp.atmos.washington.edu in directory
>ovens/.  They are titled 2000010112_mm5d1.gem and
>2000010112_mm5d2.gem.
>
>As you note, cross-over dates are working fine.
>
>As for the 2nd sentence, if you pull up the "Model Plan View" widget
>in GARP, the data for the model you select is listed in date order
>991227 follows 991226 (and so on).  One good thing is that 000101
>follows 991228.  In the plot that is generated in GARP, however, the
>date label is Jan 01 1970 for those 000101 files.
>
>Thanks for looking into this.  It sounds like we'll probably just have
>to live with it for the near future, which is no big deal.
>
>David
>
>-- 
>
>David Ovens            e-mail: address@hidden
>(206) 685-8108
>Dept of Atmospheric Sciences, Box 351640
>University of Washington 
>Seattle, WA  98195
>
>Subject: Re: 19991229: GARP is not quite Y2K compliant!
>To: address@hidden (Unidata Support)
>Date: Wed, 29 Dec 1999 17:04:13 -0800 (PST)
>
>Don,
>
>We are running on SUN's Solaris 2.6 using GARP v2.02 under
>/home/disk/ldm/NAWIPS-5.4.12/bin/sol/garp.  We also see the same
>behavior on DEC (OSF1 V5.0 910 alpha).
>
>Thanks again,
>
>David
>-- 
>
>David Ovens            e-mail: address@hidden
>(206) 685-8108
>Dept of Atmospheric Sciences, Box 351640
>University of Washington 
>Seattle, WA  98195
>