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

Re: 20001110: SPECI's in pqsurf



Peter,

The problem was speci reports were grouped together in a bulletin that had
a metar header. So the speci reports were ignored.

I believe the problem is that some of the "beta" releases of ldm-5.1.2 did
not have the following fix in the code.  Here's the log messages for the
missing speci type reports.


                Changed pqsurf/surf_split.c to handle SPECI reports that
                arrive in METAR bulletins.

revision 1.32
date: 2000/08/07 19:37:42;  author: rkambic;  state: Exp;  lines: +6 -1
added code to catch SPECIs reports that arrive under METAR reports.

I would reinstall/rebuild the latest release or just get the latest binary
release and use the new pqsurf program, this should fix the problem. 

I heard that you quit RAP?  What's the scoop.

Robb...




On Fri, 10 Nov 2000, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >From: Peter Neilley <address@hidden>
> >Subject: SPECI's in pqsurf
> >Organization: NCAR/RAP
> >Keywords: 200011101918.eAAJIoD10128
> 
> LDM guru's:
> 
> I'm having trouble figuring out this one.  On some (but not all) of our
> local LDM installations, pqsurf is no longer processing SPECI's.  I can't say
> for sure when it started.  I asked a bunch of other LDM users that I know
> use pqsurf and I got a mixed bag response.  Some said they had no problems,
> others say they noticed the problem a couple weeks ago.  All sites for which
> there is no successful SPECI processing happening, are indeed receiving and
> filing the SPECI's by the regular version of pqact.  So its definitely not
> an issue of getting SPECI's to the LDM, but limited to pqsurf's attempts
> to get/process them.
> 
> Here's some of the sets of OS/LDM versions that I know of
> 
> OS        LDM Vers         Process SPECI's successfully?
> --------  ------------     ----------------------
> Sol 2.7   LDM 5.1.2        no
> Sol 2.7   LDM 5.1.2        yes
> Sol 2.6   LDM 5.1.2        yes
> Sol 2.7   LDM 5.0.5        no
> Sol 2.7   LDM 5.0.8        no
> Deb Lnx 2.2.3 LDM 5.0.6    yes
> Deb Lnx 2.2.3 LDM 5.0.8    yes
> IRIX 6.2  L.D.M 5.0.6      yes
> 
> I've been running pqsurf manually in verbose mode in order to try to 
> understand
> or debug this problem.  Indeed even when a
> SPECI shows up at the parent LDM, no speci is ever reported in the log
> output of pqsurf.  Here's the command line I used to manually start pqsurf:
> 
>   pqsurf -f WMO -i 2 -l- -v -Q /home/ldm/data/pqsurf.pq -d /home/ldm 
> /home/ldm/etc/pqsurf.conf
> 
> with pqsurf.conf containing just the one line:
> 
>   WMO     ^(metar|speci) (....) ([0-3][0-9])([0-2][0-9])  DBFILE
> /weather/ddp/(\3:yyyy)(\3:mm)\3/(\3:yyyy)(\3:mm)\3\4.metar_gdb \2
> 
> The metar's are properly handled in pqsurf so its not an issue with the 
> pqsurf.conf file,
> or other data connectivity between pqsurf and the parent LDM.
> 
> The same manually run pqsurf on another machine (e.g. Deb Linux 2.2.3) 
> with the same pqact command line and pqsurf.conf file get/processes the
> SPECI's fine.... but it doesn't work on the Sol 2.7 machines we have.  
> 
> Tom McDerrmott reports success in SPECI processing on his 5.1.2 Sol 2.7 
> configuration, but Chris Vandersip reports the same problem as we
> are having.
> 
> Anyway, I'm not sure what else I can do to understand this
> problem any better.  Might you guys have a suggestion?
> 
> Peter Neilley
> 
> 
> 
> 
> -- 
> Dr. Peter P. Neilley
> Research Applications Program
> National Center for Atmospheric Research
> 3450 Mitchell Lane
> PO Box 3000
> Boulder, CO 80307-3000
> (303) 497-8446
> address@hidden
> 
> 
> ------- End of Forwarded Message
> 
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================