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.
Hi Chris, re: > If we have the following statement in ldmd.conf, will we get ALL GFS data > including the 0.25 degree when it begins? > > REQUEST CONDUIT ".*" upstream.host.name You will be REQUESTing all of the CONDUIT data. Your ability to receive the data will most certainly depend on your network connection. The reason I say this is that many users who REQUEST all CONDUIT have found the need to split their REQUEST into several, mutually-exclusive sub REQUESTs. Splitting the REQUEST will result in several channels by which the data will be sent from the upstream.host.name, and this will help keep the latency down for all of the data REQUESTed. re: > I guess this assumes that our upstream host will also be receiving all GFS > data? Yes. At least initially, there will only be 3 top level relays for all of the CONDUIT data. Hopefully, this situation will change over time, but over time there will invariably be more data to relay. 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: PNI-592429 Department: Support CONDUIT Priority: Normal Status: Closed