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

20000907: new LDM and RECLASS

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: 20000907: new LDM and RECLASS
  • Date: Thu, 07 Sep 2000 15:35:00 -0600
>From: weather <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200009071730.e87HU0N03745

>I am losing model data today (RECLASS statements..data over 3600 seconds
>old).  I am running ldm-5.1.2 and I thought that if I made my queue
>big enough (350MB) that I would be able to keep this data thta
>is past the latency limit.  Is this not the case?
>
>Thanks,
>Robert Mullenax
>

Robert,

If you aren't running pqexpire, you will keep data older than 3600s until
the space is needed.

You will still reclass on receipt of data older than 3600s unless you
tell rpc.ldmd to request and accept this data - this is independent of
how long you keep that data in your queue.

In your ~ldm/bin/ldmadmin script, you can add the -m offtime to the
rpc.ldmd command line which is built. For instance, adding "rpc.ldmd -m 7200"
will request data up to 2 hours old from your upstream, and your ldm will
reclass when you fall behind that time. This still relies on how big 
the upstream queue is- and how long they keep the data of course.

Steve Chiswell