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 Daryl, > So I suppose hope springs eternal that I can somehow figure out what is > happening. I added some more instrumentation over night and greatly expanded > my queue size. Sadly, the expanded queue did not stop the blips overnight. > Some observations: > > the rtstats plots seem to clearly show the troubles happening when the GFS > CONDUIT data is flowing, but I am seeing troubles at seemingly other random > times too, but not as severe. > > My present conduit request line is: > > request NMC2 > "RUC2|prod/gfs.*[012]p[^2]|prod/rtma|ndfd|nccf/com/nam.*awip3d.*grib2" > idd.aos.wisc.edu In case you don't know this, you can determine how many products are in the queue that match your request via this command: pqcat -f NMC2 -p "RUC2|prod/gfs.*[012]p[^2]|prod/rtma|ndfd|nccf/com/nam.*awip3d.*grib2" -o 99999 >/dev/null The redirection of standard output to "/dev/null" is *very* necessary if you value your terminal session. :-) Regards, Steve Emmerson Ticket Details =================== Ticket ID: RKL-664278 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.