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

20030926: mesodata reorganization (cont.)

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: 20030926: mesodata reorganization (cont.)
  • Date: Sat, 27 Sep 2003 10:11:56 -0600
>From: Unidata Support <address@hidden>
>Organization: UCAR/Unidata
>Keywords:  200309201339.h8KDdPk1012811 LDM scour load average

Hi Gerry,

Another quick note in follow-up to getting things running more efficiently
on mesodata...

We kicked around some ideas on how inefficient scouring is done in
the LDM scour script.  Steve Emmerson suggested a modification that
should make things run a lot faster.  I implemented the suggestion
on a test machine here at the UPC yesterday to make sure that there
were no dire consequences, and, finding none, implemented the same on
mesodata this morning.  I will revisit this tomorrow and most likely
also make a similar modification in the NEXRAD scouring script,
prune_nexrad.csh.

I just wanted to let you know that things are being tweeked behind
the scenes on mesodata...

Tom

>From address@hidden Sat Sep 27 13:37:56 2003

Cool, Tom.  Thanks for the update and the effort.

I'm still looking at the potential for a replacement machine, if needed.

Gerry