NAME
ref2db - convert data in REFTEK format to css3.0
SYNOPSIS
ref2db [-d datatype]
[-e]
[-l]
[-m dasmatch]
[-n net]
[-p pfile]
[-s size]
[-v]
[-w]
input dbname [start-time [end_time]]
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
ref2db reads data in REFTEK format, converts it to css3.0 and copies data
to a continuous database
dbname.
ref2db can read REFTEK tapes,
REFTEK raw disks and REFTEK files, which where created with
refdump.
OPTIONS
-
-d datatype
The output datatype may be specified to be "s4". The default
is "sd" - data in mini-seed format.
-
-e
Tells ref2db create data files and wfdisc records based on RefTek
event start and end time. Each data file will contain data for one RefTek
event.
-
-l
Will create logfile representing data in Reftek instrument format.
It contains the instrument set-up information, the state-of-health
information, and records on all events and their start&end&trigger times.
The logfile name will be in a form of DASID_log.
-
-m srcname
Only packets which belong to the DAS with serial number dasmatch
will be converted to css3.0.
-
-p pfile
A parameter file can be specified for ref2db which contains a
"DAS_serial_number to station_name" conversion table. By default
ref2db looks for a parameter file with a name ref2db.pf.
If ref2db can't find a parameter file then it makes
station names as DAS serial numbers.
-
-s size
Specifies size of files which contain waveforms. Size should be specified
in seconds.
-
-n net
If data will be converted to mini-seed format then a network code must
be specified. PS is the default network code.
-
-v
Will print to stderr srcname and time of every packet read.
-
-w
Will not write data to database. This option is useful when the user
wants only to get the RefTek logfile or get information on data time gaps.
-
start_time end_time
Specifies a time range of the RefTek data to be processed.
TIMING ISSUE
Real life shows that RefTek data has many problems related to time. Time
jumps can be discovered in Data ( DT ) packets within one event as
well as between Event ( EH&ET ) packets in a continuous data flow.
The following rule is used to calculate time in ref2db:
PARAMETER FILE
ref2db uses a parameter file to convert DAS_serial_number
to station name.
If an environment variable PFPATH is specified, ref2db
searches along this path for the parameter file; otherwise it
searches in $ANTELOPE/data/pf and then the current directory.
The parameter file should be in form:
Site &Tbl{
DAS_serial_number start_time end_time station_name
}
For eaxample:
Site &Tbl{
7338 1997300:00:00:00.0 1999365:23:59:59.9 PUPE
7358 1997298:00:00:00.0 1999365:23:59:59.9 ELAR
7363 1997299:00:00:00.0 1999365:23:59:59.9 SACA
7432 1997289:20:00:00.0 1999365:23:59:59.0 TELM
7441 1997293:22:00:00.0 1999365:23:59:59.9 ALAM
7442 1997293:02:00:00.0 1999365:23:59:59.0 SAJO
7443 1997293:19:00:00.0 1999365:23:59:59.0 OBTO
7450 1997296:00:00:00.0 1999365:23:59:59.0 LACB
7453 1997290:01:00:00.0 1999365:23:59:59.0 LOQI
7458 1997297:00:00:00.0 1999365:23:59:59.9 SAFE
7465 1997302:00:00:00.0 1999365:23:59:59.9 ROKO
}
EXAMPLE
1. Convert REFTEK data from 7838.raw file to mini-seed volumes with a network code
"XY"; store data in "saudi" database; show srcname and time of each packet.
ref2db -v -n "XY" 7838.raw saudi
2. Convert data on a REFTEK tape which is in /dev/rst5 device
to mini-seed volumes with a network code "XY"; store data in "saudi" database.
ref2db -n "XY" /dev/rst5 saudi
3. Do not create database. Make RefTek logfile and get information about timing
problems.
ref2db -w -l /dev/rst5 tmp
AUTHOR
Marina Glushko
Antelope User Group Contributed Software