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.
On Thu, 25 Feb 1999, Gregory Grosshans wrote: > Yes, the data is getting in the queue. I see it with ldmadmin watch > and its in the ldmd.log file. Outside of spacing here is what one > entry looks like from ldmadmin watch: Greg, Good, Sometime questions may trivial to you, but I need to have a base to compose a solution. If I can solve the problem. > > Feb 25 23:25:23 pqutil: 906773 19990225232522.849 FSL5 000 > NOAAPORT.GOES_EAST.IMAGE.TIGQ01.KNES.252315.1999056232414504.* > So an entry like; FSL5 ^NOAAPORT FILE data/noaaport/test.np Doesn't produce any output? I'm trying to create a generic entry to see if any data can be captured by pqact. An observation, the date looks future wrong, ie 1999056232 If this is an date? > The above two lines are actually on one line. > > In the pqact file I've tried using the WMO header 'TIGQ01' and also the > entire string from NOAAPORT...TIGQ01. > > Is the way the data being injected into the queue incorrect for naming > purposes? That's a good question. Does FLS have any sample pqact entries that they could share with you. It might help our guessing here. > > Should I have just the WMO header? So the SSEC software does place the > control > characters in the product prior to ingesting the product into the queue, > correct? > Yep, They create a complete WMO type of product from the NOAAport stream to be handed off to the LDM. Robb... > Thanks, > Gregg > > > ______________________________ Reply Separator > _________________________________ > Subject: Re: Re[2]: NOAAPORT and LDM > Author: Robb Kambic <address@hidden> at NSSLGATE > Date: 2/25/1999 4:09 PM > > > On Thu, 25 Feb 1999, Gregory Grosshans wrote: > > > Robb, > > > > I've recently obtained code, after much paper work, from FSL that > > injects the NOAAPORT data feed into the LDM queue as a specified feed > > type (e.g. FSL5). However, pqact never sees or acts on any items that > > i've configured in the pqact.conf file to work on the FSL5 data > > stream. > > Greg, > > Are you sure the data is getting into the LDM queue? What's the output > of: > > % ldmadmin watch > > If it isn't showing FSL5 product headers then no data is entering the > queue.The product headers will show the feed type and pattern. Are there any > error log messages? If no product headers then the process of entering > the data to the queue is the culprit, at that point I would contact FSL. > I don't know anything about the FSL code. > > > > > > > From what I've been told LDM waits until it sees a control-A and then > > goes into a special state and processes data until it receives a > > control-C. From what I can tell the data coming off of NOAAPORT > > doesn't contain control-As or Cs. > > Again this is FSL's implementation of reading NOAAport and making > products. > > > > > If NOAAPORT is missing these control characters, is that why pqact > > isn't doing anything with the data in the LDM queue? Did UNIDATA or > > SSEC have to modify the SSEC/UNITDATA hardware/software to place > > control characters at the beginning and end of each file for LDM and > > the IDD to work correctly? > > The SSEC processes the NOAAport products by eating the Np header and then > making a WMO header for the product with the control chars. > > > > As an example, I modified pqact.conf to send email of the ACUS1, > > ACUS2, and ACUS3 bulletins when received from the FOS and > > NOAAPORT/FSL5. I only receive the bulletins from the FOS feed. > > Similarly, I configured pqact.conf to decode metar obs from the FSL5 > > feed but it doesn't work, yet I already decode metar obs from the FOS > > and AFOS feeds. > > > It appears that no NOAAport data is entering the LDM. > > > Robb... > > > Thanks, > > Gregg > > ---------------------------------------------------------------------- > > Gregory Grosshans > > NWS/NCEP/Storm Prediction Center > > Norman, OK > > 405-579-0720 fax : 405-579-0700 > > address@hidden > > address@hidden > > /* standard disclaimer */ > > ---------------------------------------------------------------------- > > > > > > > > =============================================================================== > > Robb Kambic Unidata Program Center > Software Engineer III Univ. Corp for Atmospheric > Research > address@hidden WWW: http://www.unidata.ucar.edu/ > =============================================================================== > > > =============================================================================== Robb Kambic Unidata Program Center Software Engineer III Univ. Corp for Atmospheric Research address@hidden WWW: http://www.unidata.ucar.edu/ ===============================================================================