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

Re: ldmprods(1) (was: Re: LDM 6.3.0 released)

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: Re: ldmprods(1) (was: Re: LDM 6.3.0 released)
  • Date: Mon, 14 Mar 2005 16:10:50 -0700
Mark,

>Date: Mon, 14 Mar 2005 15:59:05 -0600 (CST)
>From: "Mark J. Laufersweiler" <address@hidden>
>Organization: University of Oklahoma
>To: Steve Emmerson <address@hidden>
>Subject: Re: ldmprods(1) (was: Re: LDM 6.3.0 released)

The above message contained the following:

> Okay cool. So how do I usse it so that I can see the stats as
> well?  The example (and how it is set up) is for the stats to go
> back to Unidata.

Change the rtstats(1) EXEC entry in the LDM configuration-file,
ldmd.conf, so that statistics are sent to your LDM.  For example

    EXEC        "rtstats -h my.local.system"

Process the rtstats(1) data-products by selecting them in a pqact(1)
configuration-file.  For example, we processes them via a GEMPAK decoder

    EXP ^rtstats        PIPE    decoders/dcrtstats data/rtstats/%Y%m%d.nc

You can do something similar (GEMPAK was used because the person who
wrote the rtstats(1) processing-system, Steve Chiswell, is also the
GEMPAK guru).

The data-products are formatted text and the format is documented in the
rtstats(1) man(1)-page.  Personally, I'd probably massage them via
awk(1) into something that can be plotted via gnuplot(1).

Regards,
Steve Emmerson