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

Re: 20060323: Radar Level II question

David,

I have been able to duplicate your problem on one of our older systems.
I have fixed gpnexr2 and am looking at nexr2rhi now. I'll
send you an update when available.

Steve Chiswell
Unidata User Support

On Fri, 2006-03-24 at 08:01, David Novak wrote:
> Hi Steve,
> 
> No go. The $GEMTBL variable is pointing to 
> /usr1/programs/nawips5.9/gempak/tables so that looks good. Gemenviron is 
> sourced (I see the very fast performance of the speed patch). And I see 
> the path:
> 
> /usr1/programs/nawips/os/linux/bin (nawips is linked to nawips59)
> 
> If it helps, I also noticed that for more recent data my map background 
> has totally changed. I've attached a recent case radar plot using 5.7 
> and now with the update to 5.9.
> 
> If you want, I can give you a call or you can call me (631-244-0134) to 
> troubleshoot.
> 
> Thanks,
> Dave
> 
> Steve Chiswell wrote:
> 
> >David,
> >
> >there is a failsafe that if no other location can be found, it just uses
> >FTG so that it has something...which is what you are seeing, but this
> >shouldn't be happening. I get the correct display over NY here.
> >
> >The NEXRII template is in $GEMTBL/config/datatype.tbl and the
> >file template is there which matches what you used, but
> >it could be that your $GEMTBL is not pointing to the correct release,
> >or didn't source the Gemenviron for the new version?
> >
> >The garbage seems like more of a symptom of a prpogram connecting to
> >a gplt or device driver from an older version. Make sure you have
> >shut down your old gplts (either gpend or "cleanup -c").
> >
> >Check your $PATH variable and make sure the 5.7.2p2 executables aren't
> >in that path. The Gemenviron will add $NAWIPS/os/linux/bin to your
> >path for the 5.9.1 version.
> >
> >Steve Chiswell
> >Unidata User Support
> >
> >On Thu, 2006-03-23 at 14:07, David Novak wrote:
> >  
> >
> >>Hi Steve,
> >>
> >>It's now plotting, but it is plotting over Denver, when the radar site 
> >>is in New York (see attached). You mentioned the
> >>
> >>datatype.tbl entry for NEXRII
> >>
> >>Where do I look for this? Anything else that could be checked?
> >>
> >>Also, I'm finding when runing my screen text becomes wild (see second 
> >>attachment). Any ideas?
> >>
> >>Thanks very much,
> >>Dave
> >>
> >>Steve Chiswell wrote:
> >>
> >>    
> >>
> >>>David,
> >>>
> >>>Yeah...thats a couple of years old now. The first iteration
> >>>was based on files received in the IDD where the dcnexr2 decoder would
> >>>add the station ID to to the file in the appropriate bytes.
> >>>
> >>>My subsequent development works with the many iterations of the
> >>>data formats, bzip2, older format headers etc. and eliminated
> >>>the need to munge the file headers pre build 5.0.
> >>>
> >>>Steve Chiswell
> >>>Unidata User Support
> >>>
> >>>
> >>>On Thu, 2006-03-23 at 11:21, David Novak wrote:
> >>> 
> >>>
> >>>      
> >>>
> >>>>Steve,
> >>>>
> >>>>I'm runing 5.7.2p2, so I bet that's it. I'll update to 5.9 and let  you 
> >>>>know what happens...
> >>>>
> >>>>Dave
> >>>>
> >>>>Steve Chiswell wrote:
> >>>>
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>>>David,
> >>>>>
> >>>>>I was able to display your file, so the format is fine.
> >>>>>Are you using 5.9.1 (comparing apples to apples)?
> >>>>>Are you using my datatype.tbl entry for NEXRII which specified the file
> >>>>>name is %SITE%_YYYYMMDD_HHNN?
> >>>>>
> >>>>>Its OK to use a full file path to the file, but the code will use the
> >>>>>NEXRII template to get the file alias when the site ID is not in the
> >>>>>data, so that %SITE% string must match your KOKX part of the file-
> >>>>>which it should, unless your datatype.tbl doesn't have the NEXRII
> >>>>>template (if you had an NCEP datatype.tbl file for example).
> >>>>>
> >>>>>Double check that your path is correct. Is that OKX correct and not
> >>>>>KOKX?:
> >>>>>/usr1/data/dnovak/radar/001230/OKX/
> >>>>>
> >>>>>Try running gpnexr2 from the directory containing the data and check the
> >>>>>file permissions if all else fails.
> >>>>>
> >>>>>Steve Chiswell
> >>>>>Unidata User Support
> >>>>>
> >>>>>
> >>>>>
> >>>>>On Thu, 2006-03-23 at 10:34, David Novak wrote:
> >>>>>
> >>>>>
> >>>>>     
> >>>>>
> >>>>>          
> >>>>>
> >>>>>>Hi Steve,
> >>>>>>
> >>>>>>Yup did the gunzip, and now I used the od command and see what you see. 
> >>>>>>HOWEVER, I get the same error message.
> >>>>>>
> >>>>>>An example data file and my script is at:
> >>>>>>
> >>>>>>Do you see anything strange?
> >>>>>>Thanks!
> >>>>>>Dave
> >>>>>>
> >>>>>>Steve Chiswell wrote:
> >>>>>>
> >>>>>>  
> >>>>>>
> >>>>>>       
> >>>>>>
> >>>>>>            
> >>>>>>
> >>>>>>>David,
> >>>>>>>
> >>>>>>>NCDC has compressed the individual files within the tarfile
> >>>>>>>(each file has a .Z extension).
> >>>>>>>
> >>>>>>>You have to use the uncompress command on the file. At that point, the
> >>>>>>>first 9 bytes should be "ARCHIVE2.", eg:
> >>>>>>>%od -c KOKX_20011230_0959 | head -1
> >>>>>>>0000000   A   R   C   H   I   V   E   2   .   3   8   4  \0  \0   ,   :
> >>>>>>>
> >>>>>>>With your file naming as shown below, gpnexr2 will be able to obtain 
> >>>>>>>the
> >>>>>>>site id from the file name which is required in pre build 5.0 files
> >>>>>>>that lacked the station ID or location within the data.
> >>>>>>>
> >>>>>>>Steve Chiswell
> >>>>>>>Unidata User SUpport
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>On Thu, 2006-03-23 at 09:49, David Novak wrote:
> >>>>>>>
> >>>>>>>
> >>>>>>>    
> >>>>>>>
> >>>>>>>         
> >>>>>>>
> >>>>>>>              
> >>>>>>>
> >>>>>>>>Thanks Steve and all,
> >>>>>>>>
> >>>>>>>>One other question...I recently downloaded Nexrad Level II radar data 
> >>>>>>>>for a Dec 2000 case from the NCDC HADS website:
> >>>>>>>>http://hurricane.ncdc.noaa.gov/pls/plhas/has.dsselect
> >>>>>>>>
> >>>>>>>>The data in 2000 is apparently in a different format than more recent 
> >>>>>>>>data, since a more on the data files shows different text at the top. 
> >>>>>>>>Consequently, I get the following error upon trying to plot using 
> >>>>>>>>gpnexr2:
> >>>>>>>>
> >>>>>>>>Enter <cr> to accept parameters or type EXIT:    : No such file or 
> >>>>>>>>directory
> >>>>>>>>wsr88d_to_radar: No valid site ID info found.
> >>>>>>>>[IM -3]  Image file
> >>>>>>>>/usr1/data/dnovak/radar/001230/OKX/KOKX_20001230_0959 not a supported 
> >>>>>>>>format
> >>>>>>>>[IM -8]  Could not open LUT file ...
> >>>>>>>>[GEMPLT -15]  NIPROJ - Invalid projection specified.
> >>>>>>>>[GG -7]  No map drawn.
> >>>>>>>>[GEMPLT -15]  NIPROJ - Invalid projection specified.
> >>>>>>>>[GG -13]  Error drawing lat/lon grid.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>Has anyone else noticed this? Is there a workaround?
> >>>>>>>>
> >>>>>>>>Thanks,
> >>>>>>>>Dave
> >>>>>>>>P.S. The data file was too large to post...
> >>>>>>>>
> >>>>>>>>Steve Chiswell wrote:
> >>>>>>>>
> >>>>>>>> 
> >>>>>>>>
> >>>>>>>>      
> >>>>>>>>
> >>>>>>>>           
> >>>>>>>>
> >>>>>>>>                
> >>>>>>>>
> >>>>>>>>>David,
> >>>>>>>>>
> >>>>>>>>>We decode the NLDN data from binary files into GEMPAK surface
> >>>>>>>>>files and use SFMAP to plot the data, points, etc.
> >>>>>>>>>
> >>>>>>>>>Since your data is not of the same format as our IDD feed to
> >>>>>>>>>use our dcnldn decoder, you can put your data into the
> >>>>>>>>>ascii format used by SFLIST for importing into a GEMPAK
> >>>>>>>>>surface file using SFEDIT as shown here:
> >>>>>>>>>
> >>>>>>>>>http://www.unidata.ucar.edu/cgi-bin/getfile?file=/content/support/help/MailArchives/gempak/msg04454.html
> >>>>>>>>>
> >>>>>>>>>Steve Chiswell
> >>>>>>>>>Unidata User Support
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>On Wed, 2006-03-22 at 13:58, David Novak wrote:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>   
> >>>>>>>>>
> >>>>>>>>>        
> >>>>>>>>>
> >>>>>>>>>             
> >>>>>>>>>
> >>>>>>>>>                  
> >>>>>>>>>
> >>>>>>>>>>All -
> >>>>>>>>>>
> >>>>>>>>>>Is there a GEMPAK program to plot lightning data? It's not obvious 
> >>>>>>>>>>to
> >>>>>>>>>>me. I have text files with that contain
> >>>>>>>>>>(1) date, (2) time, (3) latitude, (4) longitude, (5) peak current 
> >>>>>>>>>>and
> >>>>>>>>>>polarity, (6) chi square value
> >>>>>>>>>>
> >>>>>>>>>>Thanks!
> >>>>>>>>>>Dave
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>     
> >>>>>>>>>>
> >>>>>>>>>>          
> >>>>>>>>>>
> >>>>>>>>>>               
> >>>>>>>>>>
> >>>>>>>>>>                    
> >>>>>>>>>>