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

[GEMPAK #GYF-432987]: Issue with file naming (Y2K plus 21)

Hi,

First, apologies for the very slow reply!

re:
> I have seen issues on our server (and verified on GEMBUD) about the Y2K-ish
> issue with file naming.

Yes, the problem has been dubbed (by NOAA/NCEP, not us) Y2K21.

re:
> As we installed with precompiled binaries, and the fixes currently require
> changing source and recompiling, I wanted to ask if there were plans for a
> precompiled version with these fixes was going that might come available.

There are no plans in Unidata to create precompiled GEMPAK binaries, so,
for right now, your best bet is to download the source code distribution
and build it on your GEMPAK machine(s).  We are hopeful that we can work
with GEMPAK community members to transition GEMPAK to a true open source
package where the community can contribute bug fixes and enhancements.
More on this will be forthcoming.

Speaking of the need for there to be changes to several GEMPAK routines
that are affected by the Y2K21 bug: I put together a compressed tar
file of the routines that I modified in our GEMPAK 7.5.1 instance
(that is responsible for creating the IDD FNEXRAD national composite
radar products), and stuck it out on our anonymous FTP server were
others can grab it.  Here are the details:

machine:   ftp.unidata.ucar.edu
user:      anonymous
pass:      full_email_address
directory: pub/gempak/Y2K21
file:      gempak_y2k21.tar.gz

This tarball also contains code fixes provided by Steve Chiswell
that update the RSL library so that new NEXRAD Level 2 radar images
are again usable in GEMPAK.

Users who have source distributions of GEMPAK 7.5.1 can install the
updates as follows:

<as 'gempak'>
cd ~/NAWIPS           <- assumes that NAWIPS points to the 7.5.1
                         installation point
-- download the compressed tarball to this directory
tar xvzf gempak_y2k21.tar.gz
make distclean
make
make install

Since I am _not_ a GEMPAK expert (or really even a user), I can not
guarantee that this procedure will work without problem on user
machines.  All I can say is that it did work correctly for us
on our CentOS 6.10 system.


Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: GYF-432987
Department: Support GEMPAK
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.