[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:20:37 -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.

Thinking some more about it, the data is already in a format that can be
processed via gnuplot(1) -- so the pqact(1) configuration-file entry would
only need to be something like

    EXP ^rtstats        FILE    data/rtstats/%Y%m%d

You would need to do something with old versions of the above files.
You could use scour(1) or archive them.

You could have a crontab(1)-entry that periodically plotted the
rtstats(1) data.

Regards,
Steve Emmerson