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.
Unidata Support wrote: > > ------- Forwarded Message > > >To: Unidata Support <address@hidden> > >From: Robert Leche <address@hidden> > >Subject: Re: 20010815: ldm feed problem from noaaport > >Organization: UCAR/Unidata > >Keywords: 200108171628.f7HGSf103729 > > Hello all, > There was a 2nd question in the last request. This has to do with LSU's NOAA > Port. > > I am testing the new and improved ldm configuration on Sirocco from data I am > receiving from Motherlode and Motherlode supplies all my request. This is not > the > case when requests are made from Datoo ( LSU's NOAA Port). Datoo is currently > only > supplying data for requests that are defined in the snippet of Datoo's > ldmd.conf > below: > > > > > >##### DATOO LDMD.CONF > > ># $Id: ldmd.conf,v 1.9 1998/10/07 16:51:16 rkambic Exp $ > > ># Sample ldmd.conf for ldm5 > > >#### > > ># > > ># Programs that share a queue with rpc.ldmd > > ># are started by it and are in the same process group. > > ># > > >#exec "pqexpire" > > >exec "pqbinstats" > > >#exec "/data/tmp/nwstg_mps0" > > >#exec "/data/tmp/goesw_mps1" > > >exec "pqing -f IDS|DDPLUS /tmp/jmb.fifo.1" > > >exec "pqing -f HRS /tmp/jmb.fifo.2" > > >exec "pqact" > > ># exec "pqsurf" > > ># > > > > > Missing in particular is FNEXRAD. So the question is what steps need to be > made to > add extra LDM feed types. > > Looking at Datoo's ldmd.conf, the FIFO's are a concern. Should additional > FIFO's > get defined? Or simply add feed types to the two currently defined pqing > statements such as: > > exec "pqing -f ANY /tmp/jmb.fifo.1" > or create another queue with separate products? > > Also, please point out a source of information on defining this part of the > ingest > process. That is, info on setting up and ingesting from the NOAAPORT SDI card. > > ------- End of Forwarded Message Hi Bob, I'm unclear about what you're asking here. If there was an earlier message pertainent to this one, I missed it. First, you want datoo to get FNEXRAD, is that right? But you also want information on setting up the ingest process in general? FNEXRAD is not available via NOAAPORT. FNEXRAD products are identified from the NEXRAD stream via a web page at DuPage and/or Millersville, which then does an 'ldmsend' of the station names to motherlode. On motherlode, pqact uses a script to find and duplicate the appropriate radar products and put them under the FNEXRAD feed type. Consequently, I believe FNEXRAD is only available from motherlode. (Robb, please correct me if I'm wrong about this.) I see that on motherlode we have the following for you: allow UNIDATA|FSL2|DIFAX|NMC3 ^sirocco\.srcc\.lsu\.edu$ allow UNIDATA|FSL2|DIFAX|NMC3 ^Nafhat\.srcc\.lsu\.edu$ I have added the following: allow UNIDATA|FSL2|DIFAX|NMC3 ^datoo\.srcc\.lsu\.edu$ Are any of these no longer applicable so they can be removed from this conf file? Is nafhat still in the picture? Regarding info about ingesting from the SDI card, we really don't have any formal pages. We do have some experience that I can share with you. Please let me know if I'm on the right track here before I go any further. I will be away on vacation next week. If you have any questions that can't wait until Aug 27, send email to address@hidden. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************