NAME
dbassoc_arrival - associate arrivals with an origin table
SYNOPSIS
dbassoc_arrival [-p delta_p] [-s delta_s] arrival_db origin_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.
DESCRIPTION
dbassoc_arrival attempts to associate p and s phase arrivals
from one database, arrival_db, with origins in a second (distinct) database
origin_db. For each origin, it looks for matching arrivals.
If matching arrivals are found, that origin is added to the
arrival_db origin table, and assoc table entries are made in the
arrival_db assoc table.
OPTIONS
-
-p delta_p
You may specify the maximum p-arrival residual; the default is 3.0 seconds.
-
-s delta_s
You may specify the maximum s-arrival residual; the default is 10.0 seconds.
ENVIRONMENT
-
TAUP_TABLE
This specifies the travel time table used.
EXAMPLE
lemond% dbassoc_arrival -p 2.0 -s 2.0 tests/anza tests/smallcit
DIAGNOSTICS
-
Can't open database origin_dbname
-
Origin table has no records.
-
Arrival table has no records.
-
Site table has no records.
Can't read some necessary information.
-
Can't get new orid id
Probably permissions don't permit writing to the lastid table.
-
Can't add to origin table.
-
Can't add to assoc table.
Probably permissions don't permit writing to the origin or assoc table.
BUGS AND CAVEATS
Dbassoc_arrival will only match arrivals with iphase starting with 'P'
or 'S', and only matches against first P and S arrivals, not later
arrivals.
The origin table records are copied almost verbatim from the
origin_db to the arrival_db; only orid is changed. Commid's
are copied as is, but may be be dangling references in the
new database.
There are no station elevation correction factors added into
the arrival time calculations.
AUTHOR
Daniel Quinlan
Antelope User Group Contributed Software