• Antelope Release 5.2-64 Linux Red Hat Enterprise Workstation release 6.2 (Santiago) 2.6.32 2012-04-24

 

NAME

trdisp - inspect waveform data and arrivals

SYNOPSIS

trdisp [-g geometry]
	    [-m max-channels]
	    [-s subset]
	    [-w hours]
	    [-hrTW]
	    database[.table] [start-time [range]]

DESCRIPTION

trdisp reads an arbitrary view which includes wfdisc and displays the associated trace data, in a format very similar to the dbpick(1) window. By default, it tends to display coverage charts when the time range of the input is large, and traces when the time range is small. As you move in on a coverage chart, it switches to trace mode, and as you move out it switches back to coverage mode. Arrival picks are displayed only in trace mode.

If only a database name is specified, trdisp uses the wfdisc table. Otherwise, it reads the specified table, which must include the wfdisc table, or a table like wfdisc, with most of the same fields (sta, chan, foff, calib, dir, dfile, etc) You may also use "-" as the database name, in which case trdisp expects to read the input from stdin.

OPTIONS

ENVIRONMENT

see antelopeenv(5)

PARAMETER FILE

trdisp reads and applies any .dbpickrc file from your home directory and the current directory. This can be used to set a variety of parameters, notably the set of filters that can be applied. Refer to the dbpick man page for details. Note, however, that the lines in your .dbpickrc file may need to be edited to change dbpick. to *., so that parameters apply to both dbpick and trdisp. Beware of the traceWindow.twin parameter: if you change dbpick to * on this line, the initial window displayed will not the range of time from the wfdisc table any more.

EXAMPLE



% trdisp casia

% dbsubset -v input/knetc.event evid==169 | \
            dbjoin - origin :time-120::time+3600#time::endtime wfdisc | \
            trdisp -

% dbjoin -o db.wfdisc origin :sta#assoc.sta assoc arrival | \
	    trdisp -

DIAGNOSTICS

SEE ALSO

dbpick(1)
dbe(1)

BUGS AND CAVEATS

trdisp only displays waveforms and arrival picks; it has no capability to delete or modify picks, though because the underlying library implements these functions, it may appear that it does.
Note that if you use trdisp to view joined tables such as arrival, origin, etc., the order of the join matters: you must start with the wfdisc table. trdisp uses the underlying routine trgetwf(3) and the time field is not qualified. trdisp requires that the initial "time" be read from the wfdisc: not the origin, arrival, or any other table that may have a time field.

AUTHOR

Daniel Quinlan
Printer icon