Recently, my site was attempting to configure LDM to get data for the GEMPAK
decoder package.
We added the lines from the examples, specifically:
ANY ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...)
FILE -close data/gempak/nexrad/NIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3
to the pqact.conf file, and got no data at all in the appropriate directories.
Amending the lines to
ANY ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9])
FILE -close data/gempak/nexrad/NIDS/(\1:yyyy)(\1:mm)\1_\2\3
got lots of radar data, but not seperated in the way GEMPAK expects. Since
then, we have noticed that none of our pqact.conf lines which include the
"/p" construction (which, if I'm not mistaken, is supposed to tell pqact to
jump down and start reading the second line of the header) seem to work at
all. Is this a known problem, a change in syntax from when the examples were
written, or what?
Thanks for any help you can give.
--
Josh Sholes
ZedX Inc.
sholes@xxxxxxxxxxx
