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

20040831: 20040831: 20040830: gpnexr2 problem

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






>From: Michael Brennan <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200408311730.i7VHUh8E017265

>This is a multi-part message in MIME format.
>--------------060802010300030008000108
>Content-Type: text/plain; charset=us-ascii; format=flowed
>Content-Transfer-Encoding: 7bit
>
>Hi Steve,
>
>Here is one of the older files.
>
>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,
>> 
>> Looks ok, but since you said the newer files work, if
>> you could send one of the older files, I can see if the RSL
>> library which is being used can handle it.
>> 
>> Steve
>> 
>> 
>>>From: Michael Brennan <address@hidden>
>>>Organization: UCAR/Unidata
>>>Keywords: 200408311718.i7VHIw8E016042
>> 
>> 
>>>Hi Steve,
>>>
>>>Here is the od -c of the file:
>>>
>>>[mjb@fzra KFFC]$ od -c KFFC_20000124_0002 | head -10
>>>0000000   A   R   C   H   I   V   E   2   .   2   2   6  \0  \0   * 345
>>>0000020  \0 002   M 377                  \0  \0  \0  \0  \t 200  \t 200
>>>0000040  \0 002  \0  \0 004 270  \0 017   < 233   * 343 002 210   O   F
>>>0000060  \0 016  \0 001   * 343 002 304 002 001 002 001 002 001 002 001
>>>0000100 002 001 002 001 002 001 002 001 002 001 002 001 002 001 002 001
>>>*
>>>0002060 002 001 002 001 002 001 002 001 003 003 003 002 003 003 003 002
>>>0002100 003 003 003 002 003 003 003 002 003 003 003 002 003 003 003 002
>>>*
>>>0004060 003 003 003 002 003 003 003 002 001 002 001 005 001 002 001 005
>>>
>>>I was using TILT =.5
>>>
>>>One thing I noticed is that newer files (like from 2003) work with the 
>>>same setup, and the older files are the ones with the problem.
>>>
>>>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,
>>>>
>>>>can you send an "od -c KFFC_20000124_0002 | head -10"
>>>>of the file?
>>>>
>>>>Are you using TILT=list, or are you specifying an angle like TILT=.5?
>>>>
>>>>Steve
>>>>
>>>>
>>>>
>>>>
>>>>>From: Michael Brennan <address@hidden>
>>>>>Organization: UCAR/Unidata
>>>>>Keywords: 200408301508.i7UF8k8E026537
>>>>
>>>>
>>>>>Hi Steve,
>>>>>
>>>>>I'm trying to plot some archived Level II data I downloaded from NCDC 
>>>>>with gpnexr2, and I'm having some problems.  I'm running 5.7.2p2 on Linux.
>>>>>
>>>>>I'm getting this error:
>>>>>
>>>>>   : No such file or directory
>>>>>wsr88d_to_radar: No valid site ID info found.
>>>>>[IM -3]  Image file ./KFFC_20000124_0002 not a supported format
>>>>>[GEMPLT -15]  NIPROJ - Invalid projection specified.
>>>>>[GG -7]  No map drawn.
>>>>>
>>>>>I'm simply setting
>>>>>
>>>>>RADFIL = NEXRII|KFFC
>>>>>
>>>>>I saw that someone else had this same error back with 5.6, but it worked 
>>>>>when they upgraded to 5.7.2p1, and I'm already running 5.7.2p2.
>>>>>
>>>>>Any thoughts?
>>>>>
>>>>>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 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 publically 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.
>>>
>> --
>> ****************************************************************************
>> Unidata User Support                                    UCAR Unidata Program
>> (303)497-8643                                                  P.O. Box 3000
>> address@hidden                                   Boulder, CO 80307
>> ----------------------------------------------------------------------------
>> 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 publically 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 publically 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.