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.
David, You would generally use the EXEC action from pqact based on receipt of a particular header to execute a shell script that runs a gempak program environment. Most of the time however, you will probably want to generate a series of plots in an Nmeta file, so keying on a single WMO pattern in the data stream is probably not the thing you want to do, unless you are logging the receipt of each 500mb height grid for example, and then will run the script as soon as all the requisite pieces are present (or via cron if as a last resort if some pieces turn up missing). The scripting process is generally a matter of creating a work directory, such as $GEMDATA/tmp/work.$$ (using the process id of the script as a directory name keeps scripts from stelling on each other), and then creating the products and moving them to your $NTRANS_META/... tree. If you have specifics on what product you want to kick off from the LDM, I can give you some pointers there. Steve Chiswell >From: David Fitzgerald <address@hidden> >Organization: UCAR/Unidata >Keywords: 200212022037.gB2Kbj400539 >Quick question for you: > >We want to generate meta files from gempak hds data for viewing in ntrans. It >would be nice if it could be done automatically via the ldm. I didn't see >anything in the support files on how to do this. Is this possible? If so, ho > w? > > >Thanks! > >Dave >++++++++++++++++++++++++++ >David Fitzgerald >System Administrator >Millersville University >Millersville, PA 17551 >Phone: (717) 871-2394 >Fax: (717) 872-4725 >E-mail: address@hidden >