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 Paul, re: > From srh-ls-cpnrs2.srh.noaa.gov and I get the same from > srh-ls-cpnrs1.srh.noaa.gov. > I will start my request from srh-ls-cpnrs1.srh.noaa.gov and I will work on my > fail-over script, so you should not see both machines, you should only see one > at a time. Very good. Comment: - depending on how much of CONDUIT you are wanting to get, you should consider splitting your feed REQUEST into fifths (this insures that the product latencies be as low as possible. For example: Instead of: REQUEST CONDUIT ".*" idd.cise-nsf.gov Use: REQUEST CONDUIT "([09]$)" idd.cise-nsf.gov REQUEST CONDUIT "([18]$)" idd.cise-nsf.gov REQUEST CONDUIT "([27]$)" idd.cise-nsf.gov REQUEST CONDUIT "([36]$)" idd.cise-nsf.gov REQUEST CONDUIT "([45]$)" idd.cise-nsf.gov re: > I appreciate the quick response and excellent customer service! No worries. We are curious about what you intend to use the CONDUIT data for especially since your job title contains the tantalizing bit: 'Technology Infusion Branch'. Curious minds want to know :-) 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: RLV-675697 Department: Support CONDUIT Priority: Normal Status: Closed