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

[IDD #YBV-495737]: Fwd: No NDFD on CONDUIT

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: [IDD #YBV-495737]: Fwd: No NDFD on CONDUIT
  • Date: Mon, 05 May 2014 12:35:47 -0600
Hi Mike,

re: CONDUIT status
> Thanks for the info.

No worries. Interestingly, you are the only CONDUIT user that has
noted the lack of NDFD files since late last week...

re:
> Here's what we have in ldmd.conf, will this get all of CONDUIT?
> 
> REQUEST WMO|FNEXRAD ".*" flood.atmos.uiuc.edu
> REQUEST NIMAGE|NEXRAD3 ".*" flood.atmos.uiuc.edu
> REQUEST FSL2|UNIWISC ".*" flood.atmos.uiuc.edu
> REQUEST CONDUIT "[09]$" flood.atmos.uiuc.edu
> REQUEST CONDUIT "[18]$" flood.atmos.uiuc.edu
> REQUEST CONDUIT "[27]$" flood.atmos.uiuc.edu
> REQUEST CONDUIT "[36]$" flood.atmos.uiuc.edu
> REQUEST CONDUIT "[45]$" flood.atmos.uiuc.edu
> 
> REQUEST WMO|FNEXRAD ".*" idd.unidata.ucar.edu
> REQUEST NIMAGE|NEXRAD3 ".*" idd.unidata.ucar.edu
> REQUEST FSL2|UNIWISC ".*" idd.unidata.ucar.edu
> REQUEST CONDUIT "[09]$" idd.unidata.ucar.edu
> REQUEST CONDUIT "[18]$" idd.unidata.ucar.edu
> REQUEST CONDUIT "[27]$" idd.unidata.ucar.edu
> REQUEST CONDUIT "[36]$" idd.unidata.ucar.edu
> REQUEST CONDUIT "[45]$" idd.unidata.ucar.edu
> REQUEST CRAFT ".*" pollux.rcac.purdue.edu
> REQUEST CRAFT ".*" castor.rcac.purdue.edu

> REQUEST NLDN ".*" striker2.atmos.albany.edu

Your feed REQUESTs look good:

- redundantly feed from two different upstreams

- the split in CONDUIT REQUESTs is what is typically recommended

  The pattern specified splits the REQUEST into 5 mutually-exclusive
  subsets and, on average, splits into more-or-less equal subsets.

So, barring any data reception problems (e.g., exceedingly high
latencies, etc.) you should get everything that is sent.  Again, I
think that the reason for the missing NDFD products was due to the
outage of the Boulder CONDUIT top level operated by NOAA.

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: YBV-495737
Department: Support CONDUIT
Priority: Normal
Status: Closed