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 Art, re: > Okay... Penn State has switched from ncepldm4 to conduit.ncep.noaa.gov. We added split REQUESTs to conduit.ncep.noaa.gov in addition to ncepldm4 this morning as well. re: > Tom @ Unidata: Are we to leave it there once ncepldm4 comes back up? The plan was to do extensive testing of the feed from conduit.ncep.noaa.gov on a machine that does not relay into the IDD, but that has not been implemented yet. Because of this, I would suggest that the best move would be to switch back to REQUESTing from ncepldm4. After comparisons have between the feed from ncepldm4 and conduit.ncep.noaa.gov have been made and discrepancies found and fixed, all of the top level CONDUIT relays will be asked to redundantly REQUEST from ncepldm4 and conduit.ncep.noaa.gov. 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: SRJ-384993 Department: Support CONDUIT Priority: Normal Status: Closed