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

[LDM #JEK-162128]: Using scour with grbfile.sh

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: [LDM #JEK-162128]: Using scour with grbfile.sh
  • Date: Thu, 11 Oct 2018 11:11:27 -0600
Hi Carol,

re:
> Ok I thought the scour wasn't going to work.

Well, it would work, but not completely.  Leaving empty directories
will be confusing, so it is best to use something else.

re:
> Yes, can you send me your Tcl-based scouring routines to typhoon?

I just copied over the scripts to the ~yoksas/util directory on
typhoon.  For reference, here is how we are running the scripts from
the 'ldm' account on our server, lead.unidata.ucar.edu:

00 19 * * *   util/scourBYday      /data/ldm/pub/native/satellite         14 
>/dev/null 2>&1
00 19 * * *   util/scourBYday      /data/ldm/pub/decoded/gempak/areas     45 
>/dev/null 2>&1
00 19 * * *   util/scourBYday      /data/ldm/pub/decoded/mcidas/NEXRCOMP  45 
>/dev/null 2>&1
30 * * * *    util/scourBYnumber   /data/ldm/pub/decoded/gempak/nexrad    96 
>/dev/null 2>&1

NB:

- the argument to scourBYday script is how many days of data to keep on disk

  The argument to scourBYnumber is how many files to keep in the specified
  directory.

- lead.unidata.ucar.edu's clock is not UTC (or, at least, the clock in the 'ldm'
  account is local time), and this is why the hour specified in the first three
  crontab entries is 19

  If the clock on your LDM machine(s) is running in UTC for your 'ldm' user, 
simply
  change 19 to 0 (and change the minute from 00 to something a bit larger like
  05).

- both scourBYday and scourBYnumber are configured to use 'tclsh' located
  in the /usr/bin directory

  You could either install TCL on your machines so that this location for
  'tclsh' will be valid, or you can modify the reference to the location
  that will match the installation on your machines.

  If you have McIDAS-X installed, you will find the version of 'tclsh'
  that is built by the McIDAS-X installation in the ~mcidas/tcl/bin directory.

re:
> Thanks so much for your help!

No worries.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: JEK-162128
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.