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

Re: 20010830: suominet LDM feed

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.


  • Subject: Re: 20010830: suominet LDM feed
  • Date: Thu, 30 Aug 2001 10:18:15 -0600 (MDT)

Hi David, 

What is the full name of mugps?

Are you still seeing the same problem?

What do you get when you do an ldmping to mugps, or a notifyme -vl - -h
mugps.(...).(..) [i do not know the full domain]

This will help us decipher the issue.

Thanks,


-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-COMET Case Study Library                  FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Thu, 30 Aug 2001, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: David Fitzgerald <address@hidden>,
> >To: "address@hidden" <address@hidden>
> >From: Teresa Van Hove <address@hidden>
> >Subject: Re: suominet data reception problems
> >Organization: GST
> >Keywords: 200108301604.f7UG4t105529
> 
> David Fitzgerald wrote:
> > 
> > Theresa,
> > 
> > Your probably getting sick of hearing from me, but I am still not able to
> > get any data from MUGPS.
> > Checking its logs, I see twister (my "regular" ldm) connecting but then I
> > get a nullproc....RPC:Unable to Receive error.
> > I see the same message for your machine as well.  Is there something I don't
> > have configured right or is it something out of my control?
> 
> Well, I had a permission problem after rebooting on my processing box such
> that no new file netcdf files were getting inserted into the ldm queue, 
> this last week,but that doesn't explain the problem with MUGPS, 
> so I'm cc'ing the unidata support alias for expert advice.  
> 
> Teresa   
> 
> 
> > 
> > Thanks!!
> > 
> > Dave
> > 
> > **************************************************************************
> > David Fitzgerald                        Phone:  717-871-2394
> > Distributed System Specialist   Fax:    717-871-4725
> > Millersville University                     E-mail:
> > address@hidden
> > Millersville, PA 17551
> 
> ********My email to David, yesterday*********
> 
> > David Fitzgerald wrote:
> > > 
> > > Theresa,
> > > 
> > > Thanks, I did forget to uncomment out the lines in my ldmd.conf file that
> > > requested and allowed/accepted the data.  DUH!  Anyway I still do not see
> > > any data coming to me from
> > > MUGPS.  My ldm lines looks like:
> > > request AFOS ".*" 166.66.44.148
> > > accept AFOS ".*" 166.66.44.148
> > > allow  AFOS  166.66.44.148
> > 
> > UNIDATA had us call these binex files GPSSRC, so change AFOS to GPSSRC,
> > or to ANY and I think that you only need the request line.
> > 
> > my pqact.conf lines are:
> > ANY     
> > (.*)([0-9][0-9][0-9][0-9])-([0-9])-([0-9][0-9][0-9][0-9][0-9]).([bB][nN][xX])
> >         FILE    data/binex/\2.\3/\1\2-\3-\4.bnx 
> > #and#
> > GPS     (suoPWV_20[0-9][0-9].[0-3][0-9][0-9].......[0-2]..._nc)
> >         FILE    -overwrite      data/ncpwv_test/\1
> > 
> > this files the binex data in ~ldm/data/binex/gpsweek.dayweek/*.bnx
> > and the netcdf pwv files in ~ldm/data/ncpwv_test/
> > 
> > you can translate the binex files to rinex obs, nav and met files
> > with teqc (http://www.unavco.ucar.edu/software/translation) if
> > your not already familiar with it.  UNIDATA did write us a basic
> > netcdf (fortran based) reader to help folks who are not familiar
> > with netcdf extract the pwv data.
> > 
> > 
> > Teresa
> 
> 
> ------- End of Forwarded Message
> 
>