[IDD #BKI-822215]: LDM feed sites

Hi Adam,

re:
> As far as processing...
> 
> Here is my ldmd.conf's pqact section:
> 
> exec    "pqact -f CONDUIT etc/pqact.gempak_decoders_conduit"
> exec    "pqact -f NGRID etc/pqact.gempak_decoders_ngrid"
> exec    "pqact -f HDS|CMC|FNMOC|FNEXRAD|WMO|DDPLUS|IDS|FSL2|GPS|PCWS 
> etc/pqact.gempak_decoders_other"
> exec    "pqact -f WMO etc/pqact.gempak_nwx"
> exec    "pqact -f MCIDAS|NIMAGE etc/pqact.gempak_images"
> exec    "pqact -f NNEXRAD|WSI|FNEXRAD etc/pqact.gempak_nexrad"
> exec    "pqact -f CRAFT etc/pqact.gempak_craft"
> exec    "pqact -f IDS|DDPLUS|INTNL|HRS|MCIDAS|NLDN|WMO etc/pqact.wxp"

OK, thanks.  Your setup could be cleaned up a bit for readability
sake.  I say this because there are duplicates of feed types
in some of your processing lines.  For instance:

exec    "pqact -f HDS|CMC|FNMOC|FNEXRAD|WMO|DDPLUS|IDS|FSL2|GPS|PCWS 
etc/pqact.gempak_decoders_other"

This can be written more simply as:

exec    "pqact -f CMC|FNMOC|FNEXRAD|WMO|FSL2|GPS|PCWS 
etc/pqact.gempak_decoders_other"

The reason:

WMO == IDS|DDPLUS|HDS

Also in:

exec    "pqact -f NNEXRAD|WSI|FNEXRAD etc/pqact.gempak_nexrad"

The WSI feedtype is reserved for data sent point-to-point from
WSI Corporation.  While I am not sure if you are paying for this
feed, I am guessing that you are not, so the line could be written
as:

exec    "pqact -f NNEXRAD|FNEXRAD etc/pqact.gempak_nexrad"

Also:

exec    "pqact -f IDS|DDPLUS|INTNL|HRS|MCIDAS|NLDN|WMO etc/pqact.wxp"

can be more simply written as:

exec    "pqact -f MCIDAS|NLDN|WMO etc/pqact.wxp"

The reason:

WMO   == IDS|DDPLUS|HDS
INTNL == IDS

Making the above changes will not change anything in your
processing, but it will make it easier to read/understand the
feeds that the various 'pqact' invocations are working on.

> I was told of do this on our last machine that was seriously
> underpowered....I have the high load feeds on their own pqact.  Is this
> still correct?

Yes.  It is much better to have the processing split up among
multiple, disjoint 'pqact' invocations.

> Pavan is allowing me IDS|DDPLUS|HDS|NEXRAD3|NEXRAD2

OK.  This looks correct.

> My ldmd.conf file's request now look like:
> 
> #
> request UNIDATA     ".*"    pavan.srcc.lsu.edu PRIMARY
> #request UNIDATA     ".*"    stokes.metr.ou.edu SECONDARY
> request FNEXRAD|FNMOC|FSL2|GEM|NIMAGE    ".*"   idd.unidata.ucar.edu
> request NGRID    ".*"    idd.unidata.ucar.edu
> request UNIDATA  ".*"    idd.unidata.ucar.edu
> #
> # CONDUIT
> #
> #request CONDUIT "([09]$)" idd.unidata.ucar.edu
> request CONDUIT "([09]$)" idd.cise-nsf.gov
> #request CONDUIT "([18]$)" idd.unidata.ucar.edu
> request CONDUIT "([18]$)" idd.cise-nsf.gov
> #request CONDUIT "([27]$)" idd.unidata.ucar.edu
> request CONDUIT "([27]$)" idd.cise-nsf.gov
> #request CONDUIT "([36]$)" idd.unidata.ucar.edu
> request CONDUIT "([36]$)" idd.cise-nsf.gov
> #request CONDUIT "([45]$)" idd.unidata.ucar.edu
> request CONDUIT "([45]$)" idd.cise-nsf.gov
> #
> # Nexrad Level 2/3 Feeds
> #
> #request NEXRAD2 ".*"    idd.unidata.ucar.edu SECONDARY
> request NEXRAD2 ".*"    pavan.srcc.lsu.edu PRIMARY
> #request NEXRAD3 ".*"    idd.unidata.ucar.edu SECONDARY
> request NEXRAD3 ".*"    pavan.srcc.lsu.edu PRIMARY
> #
> # NLDN Feeds
> #
> request NLDN     ".*"    striker2.atmos.albany.edu
> #
> 
> I guess we will see how the latency's go for today.

Very good.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: BKI-822215
Department: Support IDD
Priority: Normal
Status: Closed