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
-
-g geometry
Specify standard X11 geometry for trdisp window.
-
-h
ignore miniseed reverse integration constant errors
-
-r
When looking at a realtime database which is being modified, trdisp
may display errors which are related to the changing database.
The -r option makes some buffers in trdisp a bit more dynamic; this
slows trdisp redisplays, but it tends to generate fewer errors.
-
-s subset
The input table may be further restricted by applying a standard Datascope expression.
(Alternatively, you can form the input table using the command line versions
of dbsubset, dbjoin, et al).
-
-w hours
By default, trdisp switches from coverage to trace mode when
the display is a quarter of an hour or less. This option lets you set
the number directly.
trdisp switches back to coverage mode more slowly, waiting for
the window to become ten times larger than this number.
-
-T
This causes trdisp to look for the first and last values in each waveform file that
are not the "missing" value; this becomes the time window range. This
can be handy for data saved with cdorb2db(1) or orb2wf(1) when a large part
of the waveform file might consist of the missing value.
-
-W
Start up in trace mode, regardless of the time window.
-
start-time
By default, trdisp initially displays the entire input time range;
you may cause the display to begin at a particular time by specifying
the start-time. This time may be specified in any of a variety of
familiar formats, for instance, "Jan 25 1993 2:15:35". See str2epoch(3).
Unlike dbpick, trdisp always keeps the entire input range available, so
even if you start later than you intended, you can back up to the beginning
of the data.
-
range
You may also specify either an ending time or a range in hours.
An ending time has the same possibilities for format as the start time.
To specify a range, use the form hh:mm or hh:mm:ss.
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
-
Can't match a record in the site/sitechan/... tables
For some reason, the trace record couldn't be matched in the site, sitechan,
sensor and instrument tables. The program joins these last four tables
together, so it's unclear which table is at fault.
-
Multiple sensor/site/sitechan/instrument records match wfdisc record.
There appear to be multiple records in the joined
sensor/site/sitechan/instrument table which match a particular trace record.
-
Couldn't get an index on table.
Some problem computing an index.
-
Can't open table
Some problem opening a table.
-
Table table has no records.
The input had no records.
-
Couldn't start.
The gpl library returned an error -- probably couldn't open a window; are
you running x-windows?
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