[GEMPAK #MGX-553390]: nex2gini "Too old" message when radar file is current

Hi Pete,

re:
> Hi again.. nex2gini is providing "Too old:" message for radar data that
> seems to be current or at least within the minutes specified in RADDUR.
> Here are the details.
> 
> In order to debug, am testing nex2gini using only one rad file -
> $RAD/LOCAL/CLE/BREF1/BREF1_20080407_1121 (no other files in the
> $RAD/LOCAL)
> ls of this file provides   -rw-r--r-- 1 peter peter 27466 Apr  7 07:40
> BREF1_20080407_1121
> Verified file contains valid data (via gpmap shows CLE radar with ground
> clutter and a valid time of 080407/1121)
> The system time was  Mon Apr  7 07:44:42 EDT 2008  (or 11:47 UTC)
> Running nex2gini gives no errors but the following messages
> [NEX2GINI 1]  Too old: $RAD/LOCAL/CLE/BREF1/BREF1_20080407_1121
> [NEX2GINI 4]  Write image 080407/1144
> Starting compression
> The result is a blank composite file in the destination directory
> ls /internal1/peter/data/radar/natl/raw/bref_1.00 gives    -rw-r--r-- 1
> peter peter 13165 Apr  7 07:44 natl_raw_20080407_1144
> nex2gini settings are as follows:
> GRDAREA   19.315;-121.415;49.5727;-62.4067
> PROJ      lcc/38;-98;38
> KXKY      4300;3000
> CPYFIL
> GFUNC     bref1
> RADTIM    current
> RADDUR    45
> RADFRQ    0
> STNFIL    nexrad.tbl
> RADMODE   pc
> SATFIL
> /internal1/peter/data/radar/natl/raw/bref_1.00/natl_raw_YYYYMMDD_HHNN
> COMPRESS  yes

Question:

- did you get the 5.11.1 distribution built on your machine

> Why would nex2gini think this file is old???

We have now seen 4 reports of strange behavior with the 5.11.1 version of
nex2gini.  If you are running 5.11.1, our suggestion is to get the nex2gini
binary from a previous release and try it.  In the meantime, we will be
searching for the bug causing this problem and will provided and updated
distribution after the fix has been created and tested.

> I even changed the name of
> the file to BREF1_20080407_0721 thinking nex2gini is somehow using local
> time and that didnt work either.

Your report echos that from the other users that have reported problems with
nex2gini (and img2gd).  I am guessing that a calling sequence changed in
some procedure being used, but can not say for sure until code diving is
complete.

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: MGX-553390
Department: Support GEMPAK
Priority: Normal
Status: Closed