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

20041220: Problem with feed from atm.geo.nsf.gov

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: 20041220: Problem with feed from atm.geo.nsf.gov
  • Date: Mon, 20 Dec 2004 11:11:24 -0700
Bob,

ATM had some switch work done this weekend, and 
traffic behavior looks like some packet shaping is
occuring on all IDD traffic.

We're looking into this with the NSF contacts.

Steve Chiswell
Unidata User Support

>From: Bob Lipschutz <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200412201705.iBKH56lI021670

>
>Unidata folks,
>
>There appears to be a problem with the CONDUIT service 
>from atm.geo.nsf.gov.  Starting around 0307Z on 12/19
>(Saturday night) latency began increasing dramatically.
>Since then, we've had very incomplete grids coming
>through.  Presently, notifyme to atm is not providing
>anything.
>
>This morning, I switched our client (conduit.fsl.noaa.gov) 
>to request from idd.unidata.ucar.edu, which seems to be
>doing just fine.
>
>FWIW, we're relying on the CONDUIT feed to acquire the 
>Eta (NAM) 212 grids that are used for RUC and WRF/NMM 
>(DWFE) initialization.  This service has been quite reliable, 
>and much more timely than our previous slow ftp-ing from 
>NCEP or TG...
>
>    Happy Holidays!
>
>       Bob Lipschutz
>       NOAA / FSL
>       303-497-6636
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.