[CONDUIT #APE-897679]: Missing data on idd.unidata.ucard.edu feed

Hi Justin,

re:
> Can you check to see if any of the other CONDUIT providers had any
> problems connecting to our LDM systems during the same time period?

I will send an email to the LDM/IDD administrators at UWisc/AOS and
Penn State.

NB: I am confident that the answer from UW and PSU will be that
they saw more-or-less the same thing that we saw.  The reason I say
this is:

- CONDUIT input into the top level IDD relay node idd.unidata.ucar.edu
  is multiply redundant (as I noted in my first reply, data gets to
  this cluster from 3 independent upstream sources)

- if data was available from at least one upstream, it would have made
  it into the datastream relayed by idd.unidata.ucar.edu

- since Doug reported that the GEFS data was missing from his feed, and
  since he feeds from idd.unidata.ucar.edu, it must be the case that no
  upstream had the data

Make sense?

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: APE-897679
Department: Support CONDUIT
Priority: Normal
Status: Open