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.
Daryl, > The LDM logs have them, they are not emitted from pqinsert. > > Apr 5 11:10:52 iem60 iem-idd0.local[368] NOTE: pq_del_oldest(): MVRT > product: 1508 20110405105848.866 NEXRAD3 134997270 SDUS71 KLWX 051055 > /pNETLWX [pq.c:4687] > Apr 5 11:10:52 iem60 iem-idd0.local[368] NOTE: pq_del_oldest(): MVRT > product: 13822 20110405105851.391 NEXRAD3 134997305 SDUS56 KSTO 051057 > /pN0RBBX [pq.c:4687] OK. I modified the product-queue library, pq(3), so that the messages in question are logged at the INFO level rather than the NOTICE level. This means that they won't appear unless you specify the verbose option, "-v", to pqinsert(1) or ldmd(1). This modification will be in the next release. Since you already know where that message is emitted, you can make the same change to your source-code rather than wait for a new LDM release. Change the line log_log(LOG_NOTICE); to log_log(LOG_INFO); From the timestamps on the messages, it appears that your product-queue isn't large enough to guarantee rejection of duplication products: the size of your product-queue needs to reconciled with your maximum acceptable latency parameter (1 h). > daryl > > -- > /** > * Daryl Herzmann > * Assistant Scientist -- Iowa Environmental Mesonet > * http://mesonet.agron.iastate.edu > */ Regards, Steve Emmerson Ticket Details =================== Ticket ID: TBE-394001 Department: Support LDM Priority: Normal Status: Closed