Is there a reason you have `-m 16` set on dcuair? That sets:
-m maxtim Set the maximum number of times
Maybe your data/gempak/upperair/YYYYMMDD_upa.gem file has exhausted
available time slots?
Also, you are positive `decoders/dcuair` points to a GEMPAK installation
and not something else?
On Thu, 9 Feb 2017, Christopher Hennon wrote:
I'm running GEMPAK7. Moving this from ldm-users to gembud.
On Wed, Feb 8, 2017 at 10:07 AM, Gilbert Sebenste <gilbert@xxxxxxx> wrote:
Although the LDM version you are running is old (6.13.6 is
current/stable), it shouldn't be doing this. This sounds more like a GEMPAK
issue. What GEMPAK version are you running?
On Feb 8, 2017, at 8:22 AM, Christopher Hennon <chennon@xxxxxxxx> wrote:
For some time now, our LDM only writes the 0000 UTC upperair data. The
dcuair log file has a lot of entries like this:
 170207/1245[DCUAIR 2] INVALID DATTIM: 170205/1200 170207/1745
Our pqact.conf entry looks like this:
# upper air reports
PIPE decoders/dcuair -b 24 -m 16
We are running version 6.10.1 (I know, we need to update). Did I miss a
change? Any ideas?
Dr. Christopher C. Hennon
Chair and Associate Professor
Department of Atmospheric Sciences
1 University Heights
Asheville, NC 28804
1.828.232.5159 <(828)%20232-5159> (phone)
1.828.232.5046 <(828)%20232-5046> (fax)
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web. Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.
ldm-users mailing list
For list information or to unsubscribe, visit:
* daryl herzmann
* Systems Analyst III -- Iowa Environmental Mesonet