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 Randy, re: > do you mean that those pqact files show us how to basically file the data. Yes. > Does it actually do the cating of the grib data so we have one file per model > per run? The way that the FILE action works in the LDM is that new products received that match the extended regular expression specified in the patter-action file entry are written to the end of the file specified ** unless the '-close' flag is included (i.e., unless one has 'FILE -close'). Writing the new products to the end of an existing file _is_ a 'cat' of the products. When you review the actions in the files I sent you, you will see part of the pattern specified matches the model runtime. The entries will, therefore, write all of the fields for a model runtime into a single file. > Side note. We are still trying to setup on our end so that our noaapxcd > machine > can access the CONDUIT. OK. I never heard back if your 'notifyme -vl- -f CONDUIT -h idd.cise-nsf.gov' test worked or not. 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: JUG-478150 Department: Support THREDDS Priority: Normal Status: Closed