source: trunk/params/rtm2ew.d @ 7968

Revision 7968, 5.1 KB checked in by paulf, 2 months ago (diff)

updated common params dir with latest .d .desc from source

  • Property svn:executable set to *
1# @(#)rtm2ew.d  1.0 08/01/13
2# rtm2ew parameter file
4#  Basic Earthworm setup:
6MyModuleId         MOD_RTM2EW     # module id for this process
7WaveRing           WAVE_RING      # output ring for TRACEBUF2 messages
8HeartBeatInterval  30             # seconds between heartbeats
10# At least one of WaveRing and RawRing must be defined.
12# If you have selected a WaveRing to output TRACEBUF2 messages, then it
13# is necessary to define a mapping between the digitizer, stream, channel
14# information that is contained in each packet to the station, channel,
15# net, location and pin number that is required by the TRACEBUF2 messages. 
16# There is no standard way to do this in vanilla Earthworm, therefore reftek2ew
17# defines yet another parameter file.  If you don't specify this file,
18# then reftek2ew issues a warning message on start up and then generates
19# its own names.  Station name is the unit id, channel name is built up
20# from the channel value in the DT header (Cxx where xx=chan), the
21# networm name is built from the stream number in the DT header (Sx),
22# the location code is set to "--", and the pin number is set to -1.
24SCNLFile             rtm2ew.scnl
26# Set a flag to control whether channels not listed in the SCNLFile are
27# written to the WaveRing.  Zero means unlisted channels will not be
28# written to WaveRing, non-zero means they will be written using the
29# SCNL generated from the DAS packets as described above.
31# The program has two modes of operation:
32#     1) Track only the data for channels listed in the SCNLFile
33#     2) Track all channels for which data is received.
35#  Under mode 1, memory will be allocated to track the channels
36#  when the SCNL file is read.  Once the channel list is read
37#  from the file, no further data allocation, or list sorting
38#  will be done, but data from all channels that are
39#  NOT IN THE SCNL LIST, will be dropped.
41#  Under mode 2, memory will be allocated to track any channels
42#  that are encountered by the module.  Each time a new channel
43#  is encountered, it will be added to the list, and the list
44#  will be resorted.  Channel list allocation is done in blocks,
45#  and it is possible that if a new channel was added to the
46#  input stream while the program was running, that it could
47#  require the program to:
48#              a) allocate a new large block of memory
49#              b) copy the list from one memory block to another
50#              c) free an old block of memory
51#              d) resort the list
52#  all before any other packets could be processed.
53#  This would probably not be the end of the world, but does
54#  add another degree of volatility to the program.
56#  Mode 1 essentially requires the operator to predefine all
57#   of the desired channels in the SCNLList, but is very stable.
58#  Mode 2 is more flexible, but has more volatility.
59#  Set SendUnknownChan to 0 for Mode 1, and to 1 for Mode 2.
61SendUnknownChan     0
64# AcceptableSampleRates
65# The program will attempt to determine the nominal sample rate for each
66# channel.  The channel rate will only be set if it matches a valid
67# sample rate as specified in the config file.
68# So if reftek2ew starts up, and the first 3 packets it sees from
69# a channel have respective rates of 125.9, 40.0, 40.0
70# it will set the sample rate to 40.0.
71# Default: AcceptableSampleRates 40.0 80.0 100.0 200.0
73AcceptableSampleRates 10 40 80 100 200
76# SendTimeTearPackets
77# ReftekEW observes the starttime of the packets coming from
78# the reftek data stream.  If there is a gap between the "estimated" end
79# of the previous packet, and the start of the current packet, then some
80# sort of time tear occurred.  It is not certain where the time tear
81# occurred and what if any data is corrupted.  Theoretically, the data
82# in the previous packet could be invalid, the data in the current packet
83# could be invalid, or both, or neither.  Because packets may be quite
84# long (8+ seconds), you may wish to risk validity of some data in order
85# to have access to all of the data in the packet.  The default behavior
86# is to SEND the packets around a time tear.  Set to 0 to NOT SEND the
87# packet after a time tear.  The packet previous to the time tear is
89# Default: SendTimeTearPackets 1
91SendTimeTearPackets 1
94# Give the fully qualified host name, or the IP address of the server in
95# the usual decimal dot notation, followed by the port number for the RTP
96# service.  If you are running this on the same computer as the RTP server,
97# then specify "localhost" as the host name.
99Server    2543
101# The API allows you to request data from a single, specific, DAS or from
102# all DAS(es).  There is no provision in the API for requesting data from
103# a subset of the available digitizers.  If you want data from a single DAS,
104# give its unit id here, otherwise enter 0 to select all digitizers.
106DASid              B215
109# The maximum amount of time (in seconds) before the module will abandon
110# filling a gap (but will continue to wait to fill newer gaps)
112# MaxGapLatency      0.5
113# Setting for USGS debug  - 2015Nov19
114MaxGapLatency      10.0
116# Debugging
117# DebugLevel 2
Note: See TracBrowser for help on using the repository browser.