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.
Rob and Rorik, Sounds good! Let us know if you experience any problems. Cheers, Jeff --------------------------------------------------------------------- Jeff Weber address@hidden : Unidata Program Center PH:303-497-8676 : University Corp for Atmospheric Research 3300 Mitchell Ln : http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 : --------------------------------------------------------------------- On Thu, 31 Mar 2005, Rob Cermak wrote: > Jeff, > > Probably better to leave CMC with Yukon. Looks very low bandwidth. > > End result is daved.ims.uaf.edu will go with: > > request IDS|DDPLUS|CONDUIT ".*" rossby.met.sjsu.edu > request FNMOC ".*" usgodae3.fnmoc.navy.mil > request HDS|NNEXRAD|UNIWISC ".*" sundog.atmos.ucla.edu > > Everything is a go once the military make adjustments. > > Rob > > > Hi Rorik and Rob, > > > > Yes, CMC and GEM are the same, and are point to point. > > > > There is not an issue to pass the GEM data along within your instition, > > but if we want to change the ingest host we would need to request that > > change with the CMC, and that can take days to weeks. So if we want to > > change ingest that is fine, but we should keep it going on yukon until we > > get the confirmation from CMC that david is now allowed... > > > > > > Thoughts...? > > > > Jeff > >