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

20051006: CONDUIT latency

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: 20051006: CONDUIT latency
  • Date: Thu, 06 Oct 2005 17:10:46 -0600
>From: Unidata User Support <address@hidden>
>Organization: Unidata Program Center/UCAR
>Keywords:

John,

I verified that your "newpsn" LDM host did fall over an hour behind by the 
66 hour forecast fields of the 18Z grid #003:

Oct 06 23:07:52 notifyme[5488448] INFO:    76382 20051006220005.922 CONDUIT 214 
 
/afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.gfs_CY.18/RD.20051006/PT.grid_DF.gr1/fh.0066_tl.press_gr.onedeg
 !grib/ncep/AVN/#003/200510061800/F066/HGT/! 000214

Time inserted was: 22:00Z and time received was 23:07Z.

Once your LDM host fell one hour behind at approximately 22:51Z, your downsteam
LDM on psnldm stopped receiving CONDUIT products and you should see 
the RECLASS messages in your ldmd.log file around that time:

Steve Chiswell
Unidata User Support