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

 

NAME

rtp2orb - Import data from a RefTek RTPD data server into an Antelope ORB

SYNOPSIS

rtp2orb [ -v ] configuration_file

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

Rrtp2orb collects data from a Refraction Technology, Inc. data server (RTPD) and writes them to an Antelope ORB as GENC packets raw and/or TRACE_BUF format packets.

OPTIONAL ARGUMENTS

REQUIRED ARGUMENTS

The program requires the path name of a configuration file which contains all the run time parameter specifications, as described in the next section.

PARAMETER FILE

The basic format consists of an identifer followed by one or more arguments. Blank lines and everything following the '#" symbol are ignored. Below is a list of all recognized identifiers and their arguments.

Below is an example parameter file.

<3>
ORB      igpprt.ucsd.edu 6770
RTPD     essw.us 2543
Database rtp2orb.map
DASid    0
StrMask  1 2 3 4 5 6 7 8

LOOKUP TABLE

As mentioned in the above section, the default build of rtp2orb supports mapping from digitzer packet header fields to station, channel, network, location and segment codes, and calib and calper, via a lookup table. In this table blank lines and everything following the '#" symbol are ignored. The table consists of an arbitrary number of lines of exactly 10 tokens each. The first 3 tokens are the unit id, stream number and channel number from the "DT" packet header. The stream and channel numbers are the one-based values that are used by people when configuring the digitizer using RefTek supplied tools, not the zero-based value that is actually in the header. The next four arguments are the character strings giving the station, channel, network, and location codes. This is followed by two floating point numbers which give the values for calib and calper. and

Below is an example lookup table.

<3>

# $Id$
#
# Example table for use with rtp2orb.  This file defines the
# mapping between the unit, stream, and channel entries which
# are in the DT packet headers and the station, channel, net,
# loc, calib and calper values required by the ORB packet.
#
# Note that stream number here is the one-based value that
# is used by people, not the zero-based value that is actually
# in the headers.

#---------- DAS ------------|------------------------ ORB ------------------------
# Unit Id    Stream    Chan    Station   Channel   Net   Loc   Seg Calib   Calper
    9083        1        1      ESSW       BHZ      MN    00    G  1.234    2.345
    9083        1        2      ESSW       BHN      MN    00    G  1.234    2.345
    9083        1        3      ESSW       BHE      MN    00    G  1.234    2.345

If the program encounters a packet which does not have a corresponding entry in the lookup table, then it generates the names as follows. The station code is simply the unit id, the channel code is the given a name of the form "st:ch" where "st" is the stream number and "ch" is the channel number, the network code is given as "N?", the location code as "L?", and the segment type as "S?". Undefined calib and calper values are 1.0 and -1.0, respectively.

NOTES

The RefTek DT packets are incomplete, in that they do not explicitly specify the sample interval. This program works around that by computing the sample interval by comparing sequential packets for each unit/stream/channel combination. Since it takes two packets before the sample interval can be known, the first packet for each unit/stream/channel combination is discarded, and a message to that effect is printed on stdout. This is normal and expected behavior.
Antelope User Group Contributed Software
Printer icon