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

20040907: 20040907: 20040831: 20040831: 20040831: 20040830: gpnexr2 problem



Mike,

I have reported the preview linux 5.7.3 distribution so that you
can get nexr2rhi that works for the old format data.

Steve Chiswell


>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata

>
>Mike,
>
>Yes, that would be the same problem, only localized to that program rather tha
> n
>the general library. I'm rebuilding the linux 5.7.3 preview tarfile
>at this time and will let you know when its posted.
>
>Steve Chiswell
>
>>From: Michael Brennan <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200409071948.i87JmKvq012303
>
>>Hi Steve,
>>
>>The new gpnexr2 works great.  Now I'm having issues with nexr2rhi for 
>>the older files.  Would the same issue pose a problem there?
>>
>>Thanks,
>>Mike
>>
>>Michael J. Brennan
>>Graduate Research Assistant
>>Department of Marine, Earth and Atmospheric Sciences
>>North Carolina State University
>>Email: address@hidden
>>Phone: (919) 515-1447
>>
>>Unidata Support wrote:
>>> Mike,
>>> 
>>> I have posted a pre-release of 5.7.3 binary for Linux:
>>> http://my.unidata.ucar.edu/downloads/214/gempak_upc5.7.3_linux.tar.gz
>>> 
>>> This includes the fix for the older NCDC Level II products.
>>> 
>>> Steve Chiswell
>>> Unidata User SUpport
>>> 
>>> 
>>> 
>>>>From: Michael Brennan <address@hidden>
>>>>Organization: UCAR/Unidata
>>>>Keywords: 200408312138.i7VLc78E013128
>>> 
>>> 
>>>>Hi Steve,
>>>>
>>>>Thanks for checking that out.  I'm using pre-compiled binaries for Linux 
>>>>now.  So a temporary upgrade would be great.
>>>>
>>>>Thanks!
>>>>Mike
>>>>
>>>>
>>>>>Mike,
>>>>>
>>>>>I found a fairly simple difference between your old
>>>>>file and what was more recent.
>>>>>
>>>>>The bytes 21-24 of the old file are 4 space characters, whereas the
>>>>>newer files that I have are 4 null characters. The build 5.0 files
>>>>>will have the 4 character station ID in those bytes.
>>>>>
>>>>>My program checks for the null characters and the station ID, but not the
>>>>>station ID being 4 spaces instead, so it is looking for a station "    "
>>>>>in the $GEMTBL/stns/wsr88d_locations.dat file.
>>>>>
>>>>>The fix is simple, in 2 places:
>>>>>$GEMPAK/source/gemlib/im/imrnex2.c
>>>>>$GEMPAK/source/driver/active/gn/crnex2.c
>>>>>
>>>>>Changing:
>>>>>if ( ( nbin < 4 ) || ( callid[0] == 0 ) )
>>>>>to
>>>>>if ( ( nbin < 4 ) || ( callid[0] == 0) || ( callid[0] == ' ' ) )
>>>>>
>>>>>If you compiled locally, you can make those modifications and:
>>>>>cd $GEMPAK/source/gemlib/im
>>>>>make all
>>>>>cd $GEMPAK/source/driver/active
>>>>>make all
>>>>>make install
>>>>>cd $NAWIPS/unidata/programs/gpnexr2
>>>>>make all
>>>>>make install
>>>>>
>>>>>If you have a binary release, I can put together a temporary
>>>>>upgrade for you until 5.7.3.
>>>>>
>>>>>Steve CHiswell
>>>>>Unidata User Support
>>>>
>>>>
>>>>-- 
>>>>Michael J. Brennan
>>>>Graduate Research Assistant
>>>>Department of Marine, Earth and Atmospheric Sciences
>>>>North Carolina State University
>>>>Email: address@hidden
>>>>Phone: (919) 515-1447
>>>>
>>> 
>>> --
>>> ***************************************************************************
> *
>>> Unidata User Support                                    UCAR Unidata Progra
> m
>>> (303)497-8643                                                  P.O. Box 300
> 0
>>> address@hidden                                   Boulder, CO 8030
> 7
>>> ---------------------------------------------------------------------------
> -
>>> Unidata WWW Service              http://my.unidata.ucar.edu/content/support
>  
>>> ---------------------------------------------------------------------------
> -
>>> 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.
>>
>--
>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.
>
--
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.