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

Re: 20050720: LDM offset

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: 20050720: LDM offset
  • Date: Wed, 20 Jul 2005 10:46:37 -0600
Carl,

>Date: Wed, 20 Jul 2005 10:51:16 -0500
>From: Carl Sinclair <address@hidden>
>Organization: University of Oklahoma
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20050720: LDM offset

The above message contained the following:

> The version on the downstream node is 6.3.0.

Then the "from" time in the request-for-data that a downstream LDM makes
will be the more recent of

    1.  The current time minus the "maximum age".  The "maximum age" is
        either

            A.  The argument of the "-o toffset" option, if specified; 
                otherwise,

            B.  The argument of the "-m max_latency" option (default
                3600 seconds).

    2.  The creation-time of the last, successfully-received
        data-product from the upstream LDM.

The logic for this is contained in the function prog_requester() in the
file "src/server/acl.c".

> Carl

Regards,
Steve Emmerson