• Antelope Release 5.5 Mac OS X 10.8.5 2015-04-21

 

NAME

get_predicted_Parrivals  - produce arrival table with predicted P arrivals given an input bulletin

SYNOPSIS


get_predicted_Parrivals [-d] [-n] [-v]
		[-a site_subset ]
		[-c chan ]
		[-s origin_subset ]
		dbcat dbsite dbout

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

There may be occasions where you have waveforms and need predicted arrivals but do not wish to run the data through the dbdetect(1) and dbgrassoc(1) processes. This script generates an arrival table in the dbout database populated with predicted arrivals when given: an input catalog, dbcat and an input site (and optionally deployment) database, dbcat. The script is fairly dumb and performs only minimal checking to see if the station in the site table was "on" during the event of interest.

OPTIONS

ENVIRONMENT

Needs to be run under an ANTELOPE environment.

EXAMPLE

Generate predicted P arrivals for the A*, B*, C*, and D* stations found in the site database, my_experiment, for orid 13781 from the qed bulletin and save the arrivals to the test database.

 % get_predicted_Parrivals -s "orid=='13781'" \
    -a "sta=~/[ABCD].*/" qed my_experiment test 

Show how many arrivals would be added for each event in the big_quakes database. No arrivals will be generated.

 % get_predicted_Parrivals -n big_quakes my_experiment test 

Generate predicted P arrivals using channel HHZ, for stations that are operational according to the deployment table of my_exeperiment. Only use origins with magnitudes greater than 7.0 or depths greater than 500.

 % get_predicted_Parrivals -d -c HHZ \
    -s "(mb>='7.0'||ms>='7.0')||depth>='500'" \
    big_quakes my_experiment test 

SEE ALSO

dbassoc_arrival(1)

BUGS AND CAVEATS

You may not actually have waveforms for all stations where output arrivals are generated (note that no wfdisc is needed for this script).

The output arrivals are likely not in the same database as your wfdisc. You will have to either rename the dbout.arrival, or modify a descriptor file to point to these separate arrivals and your wfdisc.

You should still run dbloc2(1) or some other program such as dbassoc_arrival to associate these predicted arrivals to generate assoc, origin, origerr, and event rows.

This script only puts in the predicted first arriving P arrival. It uses the ptime function from dbexpressions(5).

These are only predicted P arrivals based on the IASPEI travel time model. They should be analyst reviewed.

There is no smart programming to check that you have waveform data for the channel where the pick is to be applied.

Not extensively tested and little support will be provided. This was a quick script that I thought might be useful. If you want to modify it, please do so, and check in the changes to the contrib repository.

AUTHOR

Jennifer Eakins
ANF
Univ. of California, San Diego
Antelope User Group Contributed Software
Printer icon