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 Patrick, re: > It appears that there's some problem with castor, which I am looking > into. You did not miss any announcement; the old name "castor.itap" now > points to pollux.rcac.purdue.edu (the secondary L2 server) because > Central Region couldn't manage to get the new IP for castor.rcac added > to their setup and working. OK, that explains why we could successfully switch the feed "back" to castor.itap.purdue.edu. re: > Thanks for the notice, I'm looking at castor and will attempt to get it > back up shortly. In the mean time, you should be able to feed from > pollux.rcac.purdue.edu still. Very good. We switched to requesting directly from pollux.rcac.purdue.edu immediately after seeing your note. We will switch back to castor.rcar.purdue.edu when you give us the all clear to do so. Thanks for the quick response! 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: MXE-616655 Department: Support IDD Priority: Normal Status: Closed