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

[GEMPAK #YLI-320108]: IDD NEXRAD Level II Decoding

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: [GEMPAK #YLI-320108]: IDD NEXRAD Level II Decoding
  • Date: Tue, 10 Jun 2014 15:08:31 -0600
> notifyme and ldmadmin watch both verify.
> 
> My data files are in /data/gempak
> I haven't had a problem with text products in this directory (permissions are 
> all set correctly). Could this be the issue?


The LDM trying to write to "data/gempak/nexrad/..." will write relative to 
~ldm, so will look for ~ldm/data/gempak/nexrad/... I just want to make sure 
this is clear.  If the directory is not available to write in, you will see 
errors in ~ldm/logs/ldmd.log

If nothing else, I would suggest that you stop the LDM, delete the product 
queue, create a new product queue, and then start the LDM with *only* the 
NEXRAD2 feed active, and it would help if you added a "-log" flag to the pqact 
entry like so:

NEXRAD2 
^L2-BZIP2/(....)/([0-9][0-9][0-9][0-9][0-1][0-9][0-3][0-9])([0-2][0-9][0-5][0-9])([0-9][0-9])/([0-9]*)/
FILE -log  data/gempak/nexrad/craft/\1/.\1_\2_\3_\4

where you use TAB between "FILE" and "-log" and again before "data/gempak..."

-Michael

Ticket Details
===================
Ticket ID: YLI-320108
Department: Support GEMPAK
Priority: Normal
Status: Open