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

Re: 19990607: large ldm.pq

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: 19990607: large ldm.pq
  • Date: Mon, 7 Jun 1999 10:24:44 -0600 (MDT)
On Mon, 7 Jun 1999, Unidata Support wrote:

> >To: Unidata Support <address@hidden>
> >From: Tom Priddy <address@hidden>
> >Subject: large ldm.pq
> >Organization: .
> >Keywords: 199906071302.HAA01870
> 
> From:  Tom Priddy
> 
> We noticed an ldm.pq file is 61 meg in size this morning.
> Isn't that too large?  

Tom,

If you are getting NOAAport and McIDAS the ldm queue should be 100MGS.
61MGS is ok for a filter down NOAAport only.  If your run with a smaller
queue the LDM has to delete products out of the queue early then the hour
time limit, so one  could loose data.

Robb...



Can I erase that file or zero it out?
> /ktp
> 
> --
> ============================================================
> Tom Priddy                                address@hidden
> Extension Ag. Meteorologist          ph:  606-257-3000ext245
> Ag. Weather Center                  fax:  606-257-5671
> 243 Ag. Engineering Bldg
> Dept. of Biosystems and Ag. Engr.
> University of Kentucky
> Lexington, KY 40546-0276
> HOMEPAGE   http://wwwagwx.ca.uky.edu
> ============================================================
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================