• Antelope Release 5.5 Linux 2.6.32-220.el6.x86_64 2015-04-21

 

NAME

dbpick_combine - combine a subset of two separate databases and view in dbpick

SYNOPSIS

dbpick_combine  [-v]
	[-keep  outputdb]
	[-chan  channel_subset]
	[-start start_time]
	[-end   end_time]
	{-sta station_subset | -nearby sta [-dist distance]}
	db1 db2

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

dbpick_combine is intended to make waveform review of data from two distinct database easier by combining a subset of each input database and viewing it in dbpick. This assumes that the two input databases are related in some fashion and have data from overlapping time windows. For instance, db1 may contain your seismic waveform data while db2 may contain your state of health data (mass positions, system voltage, etc.). Rather than starting two separate instances of dbpick, you can create a view that shows all traces in the same dbpick window.

dbpick_combine subsets the arrival, site, and wfdisc tables from the input databases, db1 and db2 and makes them available in the output database used for dbpick. You must have a site table available for db1 if you are using the -nearby option. No attempts are made to clean up duplicate picks or "del" picks from the input database. The arrival table is not necessary.

A dbpick waveform window is generated with the dbpick prompt appearing in the same window where you run the dbpick_combine command. Make sure you type "quit" at the dbpick prompt rather than using Cntrl-C or the window manager close button on the waveform display window. Not following this step may result in the temporary database cleanup failing.

OPTIONS

FILES

/tmp/db1.arrival
/tmp/db1.site
/tmp/db1.wfdisc
/tmp/db2.arrival
/tmp/db2.site
/tmp/db2.wfdisc

Temporary database files are also created in the directory of the input databases. They look something like: dbpick_combine19166 and should be automatically removed upon exit of the program unless -keep is used. See BUGS AND CAVEATS!

ENVIRONMENT

You must be able to run X-windows programs.

EXAMPLE

Nearby station mode

Station mode

DIAGNOSTICS

I have seen errors like:


2007-234 16:25:49 dbcp *log*: Bad record id 81 in db pointer
2007-234 16:25:49 dbcp *log*: bad db type in dbputv

when this program is run on large real-time databases. I have not been able to reliably reproduce the error yet. The only work-around I can suggest is that you use -end with a time before the most recent time in the wfdisc table.

SEE ALSO

dbpick(1)

BUGS AND CAVEATS

This was "in shop" code that I am freeing into the world. It may not do what you want it to do, but it worked for me. Requests for upgrades and changes may be taken into consideration, but action on them may take a long while.

No support yet for expanded subsetting capabilities (i.e. sta !~/A0.*/ && sta=~/A1.*/). I am considering this and may end up re-writing code in such a way that may not be backward compatible with the -sta and -nearby options.

Better error message and check is needed if the -sta subset is for a station that is not in the site table.

Can leave detritus database files and descriptors around if program exits abnormally.

Some of the subsets can take a significant amount of time if the database tables are large. Have patience.

There are some rm commands in this script. Bad choice of input dbs could cause an important database to be removed. Please do not use /tmp/db1.wfdisc or /tmp/db2.wfdisc as either of your input databases. Save a backup of the input dbs if you are paranoid like me.

The -keep option is untested at the moment....

AUTHOR

Jennifer Eakins
ANF
Univ. of California, San Diego

Antelope User Group Contributed Software
Printer icon