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.
Harry, It depends on the load on your system. Our bsd box was bogging down in some instances, and with trying to bring up the nwstg2 grib2 data as well shortly, you may find that running separate actions will keep pqact from falling behind. You can issue (2) "kill -USR2 pqact_pid" commands to cycle to debug mode and see if you have "delay" messages that indicate significant time between product arrival and when it gets processed by pqact. My gotcha is trying to combine some data from HDS and CONDUIT which require more explicit pqact patterns (eg eta212, etc). Steve Chiswell >From: Harry Edmon <address@hidden> >Organization: UCAR/Unidata >Keywords: 200407011948.i61JmlWb005796 >I notice in 5.7.2 that the default pqact.gempak_decoders the GRIB decodes are > by >default broken up into a number of actions instead of the global filing. Is >there any reason to prefer one over the other if you are decoding everything? > >-- > Dr. Harry Edmon E-MAIL: address@hidden > 206-543-0547 address@hidden > Dept of Atmospheric Sciences FAX: 206-543-0308 > University of Washington, Box 351640, Seattle, WA 98195-1640 > -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publically 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.