[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #ZGC-437176]: Dealing with unreadable GRIB files

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.

  • Subject: [LDM #ZGC-437176]: Dealing with unreadable GRIB files
  • Date: Mon, 25 Feb 2013 10:00:06 -0700
Rich,

> Here are our LDM  "ldmd.conf" and "pqact.conf" files.
> 
> If you can figure out why we are getting extra grib records, that
> would be great!

The LDM configuration-file, "ldmd.conf", only has a single EXEC entry for 
pqact(1) -- so we only need to look at one pqact(1) configuration-file.

The pqact(1) configuration-file, "pqact.conf", has two entries for CONDUIT 
data. The sets of data-products selected by the two entries are disjoint, as 
are the sets of output files.

Assuming that the output directories are disjoint (e.g., they are not 
symbolically linked) it is, therefore, impossible that the same data-product is 
being written into the same output file more than once (at least as long as the 
data-product resided in the product-queue and can, thus, cause duplicates to be 
rejected).

I don't know the data, so I don't know if an output file might contain more 
than one data-product. If that isn't the case, then you might try adding the 
"-overwrite" option to the FILE actions because this will ensure that the 
output file only contains a single data-product.

> Thanks,
> Rich
> --
> Dr. Richard P. Signell   (508) 457-2229
> USGS, 384 Woods Hole Rd.
> Woods Hole, MA 02543-1598


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ZGC-437176
Department: Support IDD
Priority: Normal
Status: Closed