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 Deb, re: > So FILE is compiling a data file as the CONDUIT data packets come in via > the LDM feed, FILE writes an LDM data product to disk. In the LDM a product is defined as an arbitrary collection of bytes, and it is that unit that one LDM sends to another LDM. If the FILE action includes a '-close' flag, then the thing being written to a disk file is flushed from system buffers to disk and closed. If there is no '-close' flag, then succeeding LDM data products that match the same extended regular expression used in the action will be written to the end of the file. re: > and EXEC as described above runs on every data packet, correct? The EXEC action tells the LDM (pqact actually) to run the named executable. re: > Is there any way to make EXEC only run when the complete CONDUIT file has > been ingest (I know I'm grasping here, > but also know you guys work miracles sometime). In LDM/IDD data streams products are moved from one LDM to another. The product in CONDUIT is a full GRIB2 message. If by "complete CONDUIT file" you mean a full GRIB2 message, then the answer to your question is yes IF you first 'FILE -close' the product, as the succeeding EXEC action will run on the full product that has been written and flushed to disk. Again, the reason for the '-close' flag on the FILE action is to tell the operating system to flush its buffers to disk and then close the file. This should insure that the LDM product that was received is written to disk before the succeeding EXEC action is run. re: >Hope all is well with you. I'm good, thanks. Anything interesting happening way up north in Ft. Collins? 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: JXK-104385 Department: Support LDM 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.