NAME

dbpick, .dbpickrc - waveform review, pick arrivals, and edit a CSS relational database

SYNOPSIS 

dbpick [-sc sta:chan] [-ts tstart] [-te tend] [-tw twin]
       [-noexist] [-nostarttalk] [-nostdin] [-winfile winfile]
       [-appname tksend_appname]
       [-gaps {segment|zero|interp|none}]
       [-comout comfile] [-geom WxH+X+Y]
       [-switchbuttons] [-showfm] [-showdetections] [-showassocs]
       [-iconic] [-bg trace_background] [-fg trace_foreground]
       [-bga arrival_background] [-fga arrival_foreground]
       [-bgsa sel_arrival_background] [-fgsa sel_arrival_foreground]
       [-fgdt detection_foreground] [-fgtm timemark_foreground]
       dbname

DESCRIPTION

dbpick is an X-windows based interactive graphical program for displaying seismic waveforms, analyst picked phase arrivals and temporary predicted arrivals. dbpick also provides functionality for creating and/or editing phase arrivals. The data must be represented in a CSS (Center for Seismic Studies) relational database implemented as a set of ASCII flat files, each file corresponding to one of the CSS relations. Currently the program will work only with version 3.0 of the database schema. Editing causes immediate changes to the database flat files without copying to new files.

COMMAND LINE ARGUMENTS

RESOURCE DATABASE .dbpickrc

This program makes use of the X11 resource database software and a number of program parameters can be set by the user through the use of X11 resource files. The user can specify these resource parameters either through the normal X-window resource path (in .Xresource or .Xdefaults file or any other file that is loaded with xrdb), or in special resource files with name .dbpickrc that are always loaded by dbpick at run time. The program first looks for .dbpickrc in the user's home directory and then in the current working directory. If .dbpickrc files reside in both directories, then the contents of both files are read with the file in the current working directory overwriting parameters from the file in the user's home directory. A typical .dbpickrc file would be as follows: 

dbpick.traceWindow.twin:	300.0
dbpick.filter1.label:		0.1 HP
dbpick.filter1.tpad:		100.0
dbpick.filter1.lcoFreq:		0.1
dbpick.filter1.lcoOrder:	3
dbpick.filter1.ucoFreq:		0.0
dbpick.filter1.ucoOrder:	0

The resource names and values are defined as follows.

PROGRAM INTERACTION

Upon initial startup the station-channel values after sifting are displayed, along with the total number of existing waveform data samples, and the user is queried about continuing. If the user answers `n', then the program exits and the user can try different sifting keys. (This startup dialog is suppressed if the -nostarttalk flag is specified in the command line.) If the user answers `y', then a summary help listing is printed, the data is displayed in a graphical window and the program goes into command input mode. Command input mode is indicated by the prompt dbpick> displayed in the original text window and whenever this prompt is displayed the user may either enter text commands at the prompt or interact directly with the various graphical display windows through the mouse and keyboard. The currently implemented text commands are as follows:

In addition to entering text commands at the command prompt, the user can also enter certain commands directly by typing single keys while the mouse pointer is in the graphical display window. These keys can be thought of as accelerators and for the most part they simply replace typing at the command prompt. The accelerator keys are as follows. (Note that some window managers may not allow this behavior by default. When using SUN's OpenLook window manager, olw or olwm, for instance, the line
OpenWindows.FocusLenience: True
must appear in the user's .Xdefaults file in order for the accelerator keys to work.)

All other commands and interaction take place directly within the graphical display windows. The main display window initially shows all of the selected station-channel data streams with phase arrival flags. Control buttons appear at the top of the window. The effects of mouse pointer and button events in the display windows depend on where the mouse is currently located.

The Main Window control buttons are as follows.

If new display windows have been previously created, then they will appear as button items in this menu:

The Trace Region is the area, excluding the arrival flags, where the traces are displayed. Within this region the mouse acts as follows:

The Station Region is the area to the left of the traces where the Station/Channel information is displayed. Within this region the mouse acts as follows:

The Arrival Region is the area within an arrival flag. Within this region the mouse acts as follows:

The magnification window allows the user to make more sensitive interactive measurements than would be possible in the original window. All changes in the arrival flags and time marks are synchronized among the windows. The secondary windows behave in all aspects like the original window.

The Time Mark Region is the area within a time mark label (the time mark label is drawn at the very bottom and to the right of the time mark). Within this region the mouse acts as follows:

The Scroll Region is the area around the scroll bars. Within this region the mouse has the following effects:

VARIABLE SUBSTITUTION

A simple variable substitution syntax is implemented in dbpick. This substitution, only done within the arguments in the echo and exec typein commands, provides a generalized mechanism for passing program state and configuration information to other processes. At present, all of the variables relating to the state of the display apply only to the main trace display window and not to any of the various sub-windows. Variables are substituted using a %name syntax. A listing of the currently supported variable names is given here:

ENVIRONMENT

The environment variables ANTELOPE, SCHEMA_DIR, TAUP_PATH, and TAUP_TABLE are used by this program. See antelopeenv(5) for descriptions of these environment variables.

BUGS

In many cases where changes are made to a display by typing in a command or through interactive mouse input, the other displays may not be updated as one might expect. This occurs, for example, when arrival flags are hidden through the soa off typein command, which will cause the arrivals in the primary display window to be hidden but not in the other windows. The other windows can be brought up to date by repainting the windows (with the R key command in each window). When there is a break in the waveform data and a new wfdisc record is generated (i.e. end of day), dbpick will show what looks to be a gap in data at the boundary. This is not a problem: it is how dbpick is intended to work. The waveforms are not 'healed' (i.e. no connection is drawn between the two separate segments) as dbpick is intended to display the data in its most raw form. Programs such as dbwfmeas(1) heal the data assuming that the last sample from the previous record is close to the start time of the first sample of the new wfdisc record (how close is 'ok' is configurable in trdefaults.pf(5)). dbpick can not read from standard in or use "-" as the database name.

SEE ALSO

dbintro(3), dbschema(5), antelopeenv(5),tt(3), trdisp(1)

AUTHOR

Danny Harvey
Boulder Real Time Technologies, Inc.

Table of Contents
Antelope Release 4.11 Linux 2.6.22.5-31-bigsmp 2009-09-07
Boulder Real Time Technologies, Inc For more information, contact support@brtt.com