NAME
batch_dbevproc - wrapper for dbevproc execution via cron job
SYNOPSIS
batch_dbevproc [-v] [-V] [-l lddate_lagdays] [-p dbevprocpf] [-s origin_subset_expression] [-t tmpdir] db
SUPPORT
Contributed code: NO BRTT support.
THIS PIECE OF SOFTWARE WAS CONTRIBUTED BY THE ANTELOPE USER COMMUNITY. BRTT DISCLAIMS ALL OWNERSHIP, LIABILITY, AND SUPPORT FOR THIS PIECE OF SOFTWARE.
FOR HELP WITH THIS PIECE OF SOFTWARE, PLEASE CONTACT THE CONTRIBUTING AUTHOR.
SUPPORT
Contributed: NO BRTT support -- please contact author.
DESCRIPTION
batch_dbevproc is intended to be run as a cron job or
end-of-day job to
calculate magnitudes across an entire database. The motivation was to lower analyst
frustration when having to wait for a magnitude to calculate after reviewing an event.
The script reviews the database for all origins that have no netmag records
and attempts to calculate magnitudes based on the modules specified in the available
dbevproc.pf file. Additional subsets can be applied to reduce the number
of origins reviewed.
OPTIONS
-
-v
Verbose output. This will also toggle the verobse output to the dbevproc program.
-
-V
Very verbose output, useful only for debugging.
-
-l days
Lag time in days before calculating magnitudes. If not specified, all orids matching the -s origin_subset
and the auth_accept in dbevproc.pf have magnitudes calculated.
-
-p parameter_file
Alternate dbevproc parameter file to use. The default parameter file name is dbevproc.pf.
-
-s origin_subset_expression
Subset to apply to the origin table. Example: -s "lddate>='1/1/2011'&&auth=~/UCSD.*/".
-
-t tmpdir
Directory where temporary database for dbevproc execution is saved. If not specified
the output directory /fI./tmp_dbevproc/fP will be used. The output
database is called nomags.
-
db
Database which contains the origin, assoc, arrival, netmag, site, and wfdisc
tables. If no netmag table is available, it will be generated by dbevproc.
ENVIRONMENT
Need to have sourced $ANTELOPE/setup.csh and environment variable $PFPATH set.
PARAMETER FILE
There is no specific parameter file for
batch_dbevproc but the
dbevproc
parameter file is used.
EXAMPLE
recently than 1 January 2001.
% batch_dbevproc -v -s "origin.auth=~/ANF.*/&&lddate>='1/1/2011'" db/usarray
added to the crontab section of rtexec.pf
batchmags UTC 0 13 * * * batch_dbevproc -s "review=='y'" $DB
RETURN VALUES
0 if success, 1 if no.
SEE ALSO
dbevprod
BUGS AND CAVEATS
Remember to verify which dbevproc.pf is in use and that the parameters for calculating
magnitudes (i.e. sta_expr and auth_accept) and output magnitude picks via orbwfmeas are
what you want them to be.
If you choose to run this as a cron job via your rtexec.pf, you should probably make
sure that it does not run at the same time as rtbackup and rtdbclean.
AUTHOR
Jennifer Eakins
Univ. of California, San Diego
Antelope User Group Contributed Software