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 Mike, re: > Not sure why I forgot about support-idd, but thanks for the reminder. And > thanks for looking into this issue. (Data sort of flowed for a few hours > this morning.) We saw the same thing on our machine that REQUESTs from the NOAA/GSD relay: https://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_vol_nc?FSL2+lead.unidata.ucar.edu (NB: lead.unidata.ucar.edu is also known as hrrr.unidata.ucar.edu) re: > One related aspect we may want to incorporate into this inquiry is that, > when the data is flowing, it seems to be injected late relative to when > it's available via nomads server: > https://nomads.ncep.noaa.gov/pub/data/nccf/com/hrrr/prod. I sent off a note to one of the people that we have listed as a site contact for the NOAA/GSD machine. So far, we have not received a reply, so it may well be the case that the person is at AMS. We just need to sit tight and wait for a reply... 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: VQU-262651 Department: Support IDD Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.