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 Carissa, I apologize for not getting to this before now... re: > In order to get the request moving forward to get this IP changed I really > need to know what this machine is used for? Are you going to be pulling > data from CONDUIT consistently? Or is it for testing? And who is > responsible for this machine? atm.ucar.edu will be used as a backup CONDUIT ingest in Unidata. We intend to REQUEST CONDUIT data sporadically on this machine mostly for testing, but it would act as a primary ingester if our current CONDUIT ingest machine (daffy.unidata.ucar.edu) goes down. Unidata User Support (address@hidden) is responsible for this machine. If you need a specific person as the contact, you can list me: Tom Yoksas <address@hidden> We would prefer, however, that address@hidden be used since multiple Unidata staffers monitor email for this address. re: full DNS information for atm.ucar.edu is: > 128.117.12.35 <-> atm.ucar.edu 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: PGY-808322 Department: Support CONDUIT Priority: Normal Status: Closed