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.
>From: Tiziana Cherubini <address@hidden> >Organization: University of Hawaii >Keywords: 200502010005.j1105Fv2005162 IDD CONDUIT Hi Tiziana, >thanks for the informative reply. It looks like we only have to >wait and hope that things get faster soon again. Unfortunately, that is the case. I looked at the real time stats for your CONDUIT ingest machine, kiloaoloa.soest.hawaii.edu: http://my.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+kiloaoloa.soest.hawaii.edu and see that it is as good as can be expected, so there is no additional latency being added by the IDD relay of the data once it is injected at NCEP. >However it's still not very clear to me how come the data were >coming in more or less timely before january 05. Are there more >data in the stream now that there were in 2004? Yes, the 0.5 degree GFS data was added to the CONDUIT stream, and this pushed the processing load past a critical point on the data injection machine. >Thanks a lot, No worries. Ciao, Tom -- +-----------------------------------------------------------------------------+ * Tom Yoksas UCAR Unidata Program * * (303) 497-8642 (last resort) P.O. Box 3000 * * address@hidden Boulder, CO 80307 * * Unidata WWW Service http://www.unidata.ucar.edu/* +-----------------------------------------------------------------------------+