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.
Jim, the rpc.ldmd command uses the -o "offset" flag to request data from a certain time. The default is "maxlatency" which is generally 1 hour. You can add the -o flag to the ldmadmin line which invoked rpc.ldmd. Chiz On Thu, 4 Mar 1999, Jim Cowie wrote: > > > List, > > Is there any way to control the "start" time of a data request > from a downstream site when you start up the ldm? In other > words, I want to request a feed of data but only those products > from "now" (system time) to TS_ENDT (end of time). Normally, > the LDM asks for data from the downstream site from the current > time minus 1 hour to TS_ENDT. > > Example: > > Mar 04 03:44:08 ds1-comt rpc.ldmd[678]: Starting Up (built: Dec 8 1998 > 10:49:08) > Mar 04 03:44:08 ds1-comt ldm[681]: run_requester: Starting Up: > ldm.comet.ucar.edu. > Mar 04 03:44:08 ds1-comt ldm[681]: run_requester: 19990304024408.795 > TS_ENDT {{MCIDAS, "^satx.*"}} > > In this example, the data start time for the request (19990304024408.795) > is an hour before the current system time (03:44:08). Is this > hard-coded in the ldm, or can it be controlled? > > I want to be able to specify that I want only data from "now" forward > in time so that I don't get inundated by old data. > > thanks, > > -jim > > > ----------------------------------------------------------- > Jim Cowie address@hidden > NWS/UCAR-COMET (303) 497 - 8358 > PO Box 3000 > Boulder, CO 80307-3000 > >