Changes between Version 2 and Version 3 of gmew


Ignore:
Timestamp:
05/09/12 10:27:21 (8 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • gmew

    v2 v3  
    3131 
    3232== Configuration File Commands == 
     33On startup, gmew reads commands from a configuration file. Commands in this file set all the parameters for configuring the Earthworm gmew module. In the control file, lines may begin with a valid gmew command (listed below) or with one of 2 special characters: 
     34{{{ 
     35#  marks the line as a comment (example: # This is a comment). 
     36    
     37@  allows control files to be nested; one control file can be  
     38   accessed from another with the command "@" followed by  
     39   a string representing the path name of the next control file  
     40   (example: @model.d). 
     41}}} 
     42 
     43Command names must be typed in the control file exactly as shown in this document (upper/lower case matters!). Blank lines are also permitted in the control file. 
     44 
     45=== FUNCTIONAL COMMAND LISTING === 
     46{{{ 
     47Earthworm system setup: 
     48MyModuleId      Required 
     49RingInName      Required 
     50RingOutName     Required 
     51getEventsFrom   Required 
     52HeartBeatInterval       Required 
     53log switch      Optional         
     54Memory allocation commands 
     55maxSta  Required 
     56maxTrace        Required 
     57Event and Trace commands 
     58traceSource     Optional        -t 
     59extraDelay      Optional         
     60traceTimes      Optional 
     61Add     Optional 
     62Del     Optional 
     63maxDist Required 
     64saveTrace       Optional 
     65searchWindow    Optional 
     66Auxiliary Data Sources 
     67respSource      Optional 
     68staLoc  Required 
     69velocity model  Optional 
     70SCNLpar Optional 
     71Miscellaneous Commands 
     72Debug   Optional 
     73wsTimeout       Optional 
     74XMLDir  Optional 
     75TempDir Optional 
     76MappingFile     Optional 
     77watchForAlarm   Optional 
     78AddSpectraResponseAt    Optional 
     79}}} 
     80 
     81 
     82=== ALPHABETIC COMMAND LISTING & DESCRIPTION === 
     83 
     84In the following section, all configuration file commands are listed in alphabetical order. Listed along with the command (bold-type) are its arguments (in red.) A detailed description of the command and is also given. Default values and example commands are listed after each command description. 
     85 
     86command arg1     function 
     87Add STA COMP NET LOC    Event and Trace Commands 
     88Add the trace(s) with station name STA, component name COMP, network name NET , and location code LOC to the selection list. Any of STA, COMP and NET may be the wildcard character `*'. COMP may be given as the first two letters of the component name, to select all direction desgnators (North and East) are accepted for that component. Zero, one or many Add commands may be listed in the configuration file. If no Add commands are given, all SCNLs from the trace source will be selected. The Del command may be used to narrow the selection implied by wildcard values in an Add command or by the absence of any Add commands. 
     89Default: all traces are selected from a trace source 
     90Example: Add * BH * 
     91         Add SEA EH UW 
     92AddSpectraResponseAt period     Miscellaneous Commands 
     93Add the period to the list of those processed. If this is the first occurrence of this command, then replace the standard list (0.3, 1.0 and 3.0) with period. 
     94Default: 0.3, 1.0 and 3.0 
     95Example: AddSpectraResponseAt 2.0 
     96         AddSpectraResponseAt 2.5 
     97Debug D Miscellaneous Commands 
     98Set the debug level to D. There are many different debug options; one or more of them may be activated using the Debug command. More than one Debug command may be used, or the different values (from the table) may be added together into one Debug command. Except as noted, the debug information is printed to STDERR and the log file (depending on the setting of log switch.) Select from these debug options: 
     991: 
     100trace and search times and P and S arrival estimates (relative to event origin time) 
     1012: 
     102SCNL selection tests 
     10316: 
     104ws_client debugging 
     10532: 
     106poles. zeros and gain values 
     10764: 
     108trial frequency response functions to STDOUT. Produces about 1500 lines for each SCNL, which should be saved to a file. 
     109128: 
     110full frequency response function to STDOUT. Produces several thousand lines for each SCNL, which should be saved to a file. 
     111256: 
     112Input and output trace data including in padded arear to STDOUT. Produces several thousand lines for each SCNL, which should be saved to a file. 
     113Default: 0; no debug output 
     114Example: Debug 3 # turns on options 1 and 2 
     115Del STA COMP NET LOC    Event and Trace Commands 
     116Delete the trace(s) with station name STA, component name COM, network name NET , and location code LOC from the selection list. Any of STA, COMP ,  NET and LOC may be the wildcard character `*'. COMP may be given as the first two letters of the component name, to select all direction desgnators (Vertical, North and East) are accepted for that component. Zero, one or many Del commands may be listed in the configuration file. 
     117Default: all traces are selected from a trace source 
     118Example: Del SEA BH UW -- 
     119getEventsFrom INST MOD   Earthworm Setup 
     120Get event messages (TYPE_HYP2000ARC) from installation INST and module MOD. These installation and module IDs are found in earthworm.d and earthworm_global.d. Use as many getEventsFrom commands as necessary. 
     121Default:  none 
     122Example:  getEventsFrom INST_WILDCARD MOD_EQPROC 
     123HeartBeatInterval H      Earthworm Setup 
     124Send TYPE_HEARTBEAT messages every H seconds to the transport ring. 
     125Default:  none 
     126Example:  HeartbeatInterval 30 
     127log switch: -lS Earthworm Setup 
     128This is not a config-file command but a command line switch Sets the value of the logging switch to S. Possible values of S are: 
     1290: 
     130Do not create a log file. Some logging data will be printed to the screen (stdout or stderr.) 
     1311: 
     132Create a log file in the directory named by the EW_LOG environment variable. The log file name will based on the config-file name and the current data. A new file will be created for each day (but only if there are logging entries to be made.) Some logging data will be printed to the screen (stdout or stderr,) as with option `0' above. 
     1332: 
     134Create a log file as for option `1', but do not write anything to the screen (stdout or stderr.) 
     135Default: 1 
     136Example (on the command-line):  -l0 (lower-case ell zero; turns off creation of 
     137        log file) 
     138MappingFile map-file    Miscellaneous Commands 
     139Specifes that name of a mapping file for use in writing XML files (see XMLDir). This file provides for three different mappings: from station-net codes (used in SCNL) to descriptive station names; from net codes to descriptivce agency names, and from station-component-network codes to instrument type. See the file NCSN.map in the gmew source distribution for an example of this file. This file is not required by gmew, and the descriptivce names are not required by shakemap. 
     140Default: no mapping file if this command is not given 
     141Example: MappingFile NCSN.map 
     142maxSta N        Memory Allocation 
     143At startup, gmew will allocate space for N individual stations (unique station/network names.) Each station may have any number of different components (BHE/BHN/HHE/HHN.) If gmew tries to read more than N stations, the excess ones will be skipped with a logged warning message. The order that stations are read into gmew is determined by the trace source and thus may be arbitrary. 
     144Default: none, this command is required. 
     145Example: maxSta 100 
     146maxTrace M      Memory Allocation 
     147Allocate memory for MtraceTimes command and the estimated P and S phase arrival times. 
     148Default: none, this command is required 
     149Example: maxTrace 60000 
     150MyModuleId mod_id       Earthworm setup 
     151Sets the module id for labeling all outgoing gmew, heartbeat, and error messages. mod_id is a character string (valid strings are listed in earthworm.d) that relates to a unique single-byte number. In general, a different module ID is needed for each instance of gmew. 
     152Default: none 
     153Example: MyModuleId MOD_LOCALMAG 
     154respSource SOURCE [params]      Auxilliary Data Sources 
     155Tells gmew where to find instrument response data. This command is required. Choices for SOURCE are: 
     156FILE dirname pz-filename-format 
     157find response files in the dirname directory. pz-filename-format is a string similar to the printf format: %S, %C, %N are replaced by station, component and network names, respectively, all in upper case. Similarly %s, %c, %n work for lower-case station, component and network. The digraph %% stands for %; all other characters are taken literally. 
     158The response file format is similar to that used by SAC POLEZERO files with some extra requirements. The options in the file are keyword driven and the numbers are in free format. You may specify a multiplicative scaling constant by putting a line in the file containing the keyword "CONSTANT" followed by a floating point number. The default for this constant is 1.0 if you omit this line. You specify the number of poles by putting a line in the file with the keyword "POLES" following by an integer number. The next lines in the file until another keyword is read become the poles for this instrument. Each such line contains two floating point numbers specifying the real and imaginary parts of one of the poles. If you have fewer lines specifying poles than you stated on the "POLES" line, the remaining poles are assumed to lie at the origin. You specify the zeros in the same way with a "ZEROS" keyword line following by lines specifying the zeros that do not lie at the origin. You may specify up to as many poles and zeros as you need. 
     159 
     160The poles, zeros and gain constant of the response file MUST be for an input of displacement in nanometers. See the documentation provided by the NEIC AutoDRM for more details. The poles and zeros specify the Laplace transform of the analogue instrument response. Currently gmew has no provision for handling digital FIR or IIR filter responses. For example, the following is the specification for the NSN broadband seismometer OCWA.BHE.US: 
     161 
     162 
     163CONSTANT    0.50280E+11 
     164ZEROS       3 
     165        0.00000E+00    0.00000E+00 
     166        0.00000E+00    0.00000E+00 
     167        0.00000E+00    0.00000E+00 
     168POLES       6 
     169       -0.31420E-01    0.00000E+00 
     170       -0.19790E+00    0.00000E+00 
     171       -0.20110E+03    0.00000E+00 
     172       -0.69740E+03    0.00000E+00 
     173       -0.75400E+03    0.00000E+00 
     174       -0.10560E+04    0.00000E+00 
     175EWDB 
     176Query an Earthworm Database for reponse information. Not currently implemented. 
     177Default: none 
     178Example: File /earthworm/responses %S_%C_%N.pz 
     179RingInName ring Earthworm setup 
     180Tells gmew which shared memory region to use for input transport. ring is a character string (valid strings are listed in earthworm.d) that relates (in earthworm.d) to a unique number for the key to the shared memory region. Gmew reads TYPE_HYP2ARC messages from this ring. 
     181Default:  none 
     182Example:  RingInName HYPO_RING 
     183RingOutName ring        Earthworm setup 
     184Tells gmew which shared memory region to use for output transport. ring is a character string (valid strings are listed in earthworm.d) that relates (in earthworm.d) to a unique number for the key to the shared memory region. Gmew writes TYPE_STRONGMOTIONII, TYPE_HEARTBEAT and TYPE_ERROR messages to this ring. RingOutName can be the same as RingInName if desired. 
     185Default:  none 
     186Example:  RingOutName SM_RING 
     187saveTrace ST [params] DIR FORMAT        Event and Trace Commands 
     188Tells gmew whether and how to save synthetic traces. If the saveTrace command is absent, no traces will be saved. Choices for ST include: 
     189SAC baseDir dirFormat filename-format 
     190Save synthetic traces in SAC-format files. The full pathname for each SAC file will be made up of base directory, formatted directory, and formatted filename plus a descriptive ending; all concatenated together with appropriate path separators. The endings are "-acc", "-vel", "-disp", "-psa03", "-psa10" and "-psa30" for the appropriate traces. 
     191baseDir 
     192Specifies a fixed directory name. This can be an absolute directory path or a path relative to the current directory. It can contain one or more parts with pathname separators. This all components of this path (except possibly the last) must exist before gmew is started. 
     193dirFormat 
     194Gives a formattted subdirectory name; the format string is that used for the Unix date command applied to the event origin time, with the addition of `%i' to indicate the event ID. Be careful with this; some formats produce output not compatible with directory names. The directory name derived from dirFormat must not contain any path separators. Suitable format strings include: 
     195%C 
     196Century number (the year divided by 100 and truncated to an integer as a decimal number [1,99]); single digits are preceded by 0. 
     197%d 
     198Day of month [1,31]; single digits are preceded by 0. 
     199%h 
     200Locale's abbreviated month name. 
     201%H 
     202Hour (24-hour clock) [0,23]; single digits are preceded by 0. 
     203%i 
     204The Earthworm event ID. Currently this event ID can only be read from a hyp2000 archive message. 
     205%j 
     206Day number of year [1,366]; single digits are preceded by 0. 
     207%m 
     208Month number [1,12]; single digits are preceded by 0. 
     209%M 
     210Minute [00,59]; leading zero is permitted but not required. 
     211%R 
     212Time as %H:%M 
     213%S 
     214Seconds [00,61] 
     215%T 
     216Time as %H:%M:%S 
     217%u 
     218Weekday as a decimal number [1,7], with 1 representing Sunday. 
     219%U 
     220Week number of year as a decimal number [00,53], with Sunday as the first day of week 1. 
     221%V 
     222Week number of the year as a decimal number [01,53], with Monday as the first day of the week. If the week containing 1 January has four or more days in the new year, then it is considered week 1; otherwise, it is week 53 of the previous year, and the next week is week 1. 
     223%w 
     224Weekday as a decimal number [0,6], with 0 representing Sunday. 
     225%W 
     226Week number of year as a decimal number [00,53], with Monday as the first day of week 1. 
     227%y 
     228Year within century [00,99]. 
     229%Y 
     230Year, including the century (for example 1993), 
     231filename-format 
     232Gives the formatted file name using % to introduce one of the format specifiers "sScCnNLl%" `s' is the station name in lower case; `S' is upper case. Likewise for component and network names; `%' stands for itself. All other characters are taken literally. This works in the same way as the format string for response files. 
     233Gmew adds the following special fields to SAC file headers. The peak amplitude is written to user0; in t0 is the time, relitive to event origin, of the peak amplitude. In kuser0 and kt0 are the labels for these user values. For the acceleration, the labels would be "Acc_max" and "Acc_amp", respectively. Other traces have similar labels. The SAC header variable kinst has the units for the trace, such as "cm/sec^2" for acceleration. 
     234Default:  command is absent (no traces are saved) 
     235Example: SAC /earthworm/SAC/GM %Y%j%i %S.%C.%N 
     236SCNLpar STA COMP NET LOC special-parameters     Auxilliary Data Sources 
     237Set certain parameters (described below) for specific traces identified by their SCNL: STA, COMP, and NET (station/component/network name.) No wildcards are permitted here; each SCNL must be given explicitly, but only if special values are needed for that SCNL. Often, the default values will be adequate for most SCNLs. If there are only a few of these commands, they may be listed in the configuration file. But if a large number of them are needed, it may be more convenient to place them in a separate file. Then that file will get included with the configuration file by the syntax: 
     238@scnl_param_file 
     239Note that the format of this files is identical to the one used by the localmag module. Each SCNLpar command must include the STA, COMP, NET, LOC names followed by the following seven decimal values. Use spaces between all elevent items in each SCNLpar line. All values must be present; no default values are used for an SCN if it has an SCNpar line. The seven decimal values are: 
     240magnitude correction 
     241This value is ignored by gmew; it is used only by the localmag module. 
     242taper low-freq off 
     243The frequency at the low end of the passband below which the cosine taper has zero value. This taper is applied to the frequency response function before it is convolved with the trace. Frequency units are Hz. 
     244taper low-freq on 
     245The frequency at the low end of the passband above which the cosine taper has a value of 1. The low-end taper can be eliminated by setting the off and on values to the same value. The default low-end taper is turned off, passing all low frequencies. 
     246taper high-freq on 
     247The frequency at the high end of the passband below which the cosine taper has a value of 1. 
     248taper high-freq off 
     249The frequency at the high end of the passband above which the cosine taper has a value of 0. The high-end taper can be eliminated by setting the off and on values to the same value. The default high-end taper has an off value equal to the trace Nyquist frequency (one half the sample rate.) The default on frequency is 90% of the Nyquist frequency. 
     250clipping limit 
     251The value, in digital counts, beyond which in absolute value the unprocessed trace should be considered clipped. If the trace is declared clipped by gmew, it will synthesized into ground motion traces, but it will not have amplitude picks performed. The default clipping limit is 7.55e+06 counts, 90% of 2^23, the limit of a 24-bit digitizer. 
     252taper time interval 
     253The number of seconds for which a cosine taper will be applied to both ends of the input time series before it is transformed to the frequency domain. This taper will shorten the useful length of the time series from the length specifed by the traceTimes command by twice this taper interval. The default value is 0 - no taper is applied to time series. 
     254Default: as described above 
     255Example: SCNLpar SEA EHE UW -- 0.2   0.1 0.1 20 25   2.9e4 1.0 
     256searchWindow A B C D    Amplitude Controls 
     257Specify the time interval in which gmew will search for peak amplitudes in the synthetic traces. Together with the P- and S-phase arrival times estimated from the velocity model, these four parameters set the start and end times of this search window. The four parameters are: 
     258A: 
     259The multiple of the estimated interval P - S to start the search before estimated S arrival. Use a negative value to start after the S arrival. 
     260B: 
     261The minimum number of seconds before estimated S arrival to start the peak search. 
     262C: 
     263The multiple of the estimated interval P - S to end the search after the estimated S arrival. 
     264D: 
     265The minimum number of seconds after estimated S arrival to start the peak search. 
     266Default: searchWindow 0.0 2.0 0.0 30.0 # Search window runs from 2 seconds 
     267        before to 30 seconds after the estimated S arrival, independent of 
     268        the P - S interval. 
     269Example: searchWindow 0.1 2.0 2.0 15.0 # some random values 
     270staLoc LOC [params]     Auxilliary Data Sources 
     271Tells gmew where to find station location information. Station locations are used to find the station-epicenter distance, which is then used in the estimate of P and S phase arrivals. The choices for LOC are: 
     272File loc-file: 
     273Get station locations from a hyp2000-format station location file named loc-file. This file must be in text format, not the binary-format file sometimes used by hyp2000. If the file is not located in the current directory, partial or full path information must be included in loc-file. 
     274EWDB 
     275Query the Earthworm database for station locations. Not currently implemented. 
     276Default: none; this command is required 
     277Example: staLoc File /earthworm/run/params/hypoinverse/stas/uw_sta.hinv 
     278TempDir temp-dir        Miscellaneous Commands 
     279Specify the temporary directory for writing an XML file (see XMLDir). This command is ignored unless an XMLDir command is given, in which case TempDIr is required. 
     280Default: none; this command is required if XMLDir is given 
     281Example: TempDir Shake/temp 
     282tracesource SOURCE [params]     Event and Trace Commands 
     283Directs gmew to obtain trace data from SOURCE. Choices are: 
     284waveServer server-list 
     285Obtain trace data from the wave servers in server-list, a space delimited list of one or more server:port pairs. The server can be an IP address or a hostname for the wave server. The port is the port number used by that wave server. 
     286waveServer File server-file 
     287Command line: -tvObtain trace data from the wave servers listed in the file named server-file. This file consists of lines listing server and port, one server to each line. The two entries on a line may be separated by space or colon. 
     288Gmew will connect to one server at a time. For each connection, it will obtain the server's current menu, match SCNLs on the menu against the selection list from Add and Del commands, obtain and process the trace data segment for each of the selected SCNLs. The time interval for each trace is established by the traceTimes command. After all the selected SCNLs for one wave server have been processed, the connection to that server will be closed and the next server will be accessed. 
     289 
     290Default:  waveServer with list of servers read from the file $EW_PARAMS/servers 
     291Example: traceSource waveServer 123.45.67.89:16021 123.45.67.89:16022 
     292extraDelay DelaySecs    Event and Trace Commands 
     293This is the delay in seconds to wait after receiving an Event message to hit the waveServers for traces. 
     294DelaySecs: 
     295is the number of seconds to sleep. 
     296Default: extraDelay 0 
     297Example: extraDelay 20 
     298traceTimes START END    Event and Trace Commands 
     299Specify the start and end times of trace data to be used from any trace source. 
     300START: 
     301is the number of seconds before estimated P arrival to start the trace. 
     302END: 
     303is the number of seconds after estimated S arrival to end the trace. 
     304Default: traceTimes 5.0 60.0 
     305Example: traceTimes 10.0 40.0 
     306velocity model  Auxilliary Data Sources 
     307Read in the one-dimensional velocity model to be used to estimate P and S phase arrival times. This is done using the syntax: 
     308@velocity_file 
     309Typically this will be the same file as used for binder_ew. Gmew will always look for this file in the current directory, so appropriate path information must be included if the file is located elsewhere. Ask Earthworm Central for documentation of this long-used file format. 
     310Default:  none 
     311Example: @/earthworm/run/params/uw_velovity.d 
     312watchForAlarm duration  Miscellaneous Commands 
     313Read ACTIVATE_MODULE messages tagged for gmew from the input ring, and process similarly to a HYPOARC2000 message, but instead of computing the window, use the timestamp included in the message as the start of the window and duration as its length in seconds. 
     314Default: ignore ACTIVATE_MODULE messages 
     315Example: watchForAlarm 10 
     316wsTimeout M     Miscellaneous Commands 
     317Set the timeout for wave server connections to M milliseconds. If no response is heard from the wave server after this time, gmew will assume this wave server is dead and proceed to the next one. 
     318Default: 5000 milliseconds 
     319Example: wsTimeout 10000 
     320XMLDir xml-dir  Miscellaneous Commands 
     321Gmew can optionally write an XML file for an event. This file will be in the format used by ShakeMap (version 2). While the file is being written, it will reside in temp-dir. When the file is completed, it will be moved to xml-dir. The file's name will be "_dig_dat.xml" with the Event ID prepended. By writing to a temporary directory and moving the completed file to xml-dir, gmew will ensure that only a complete XML file will be in xml-dir. (On Unix, you must ensure that temp-dir and xml-dir are on the same filesystem; otherwise the file movement will not be an atomic operation.) 
     322Default: XMLDir command not given; no XML file is written 
     323Example: XMLDir  Shake/input 
     324 
     325=== Sample Configuration File === 
     326{{{ 
     327# Configuration file for gmew 
     328# Some of these parameters can be overridden on the command-line; 
     329# some of them only make sense on the command-line. 
     330# 
     331# Required Commands:  
     332# The following five commands are always required by gmew. 
     333# Other commands below may be required when certain options are given. 
     334# 
     335# Earthworm Transport commands 
     336# RingInName : specify the name of the earthworm transport ring from 
     337#  which to read TYPE_HYP2000ARC messages for event notification. 
     338 
     339RingInName HYPO_RING 
     340 
     341# RingOutName : specify the name of the earthworm transport ring from 
     342#  which to write Magnitude, Heartbeat and Error messages. This may be 
     343#  the same is the RingInName if desired. 
     344 
     345RingOutName GM_RING 
     346 
     347# MyModId <module-id>: specify the module ID for gmew 
     348 MyModId MOD_GMEW 
     349 
     350# HeartBeatInterval int: How often gmew should beat its heart. 
     351 
     352HeartBeatInterval 30 
     353 
     354# getEventsFrom  INST_ID MOD_ID 
     355# Specify the installation ID and module ID names from which to get 
     356# hypoinverse archive messages to read event data. These names may be 
     357# selected from earthworm.d and earthworm_global.d. No default values. 
     358Use as many of these commands as necessary. 
     359 
     360getEventsFrom INST_UW MOD_WILDCARD 
     361getEventsFrom INST_MENLO MOD_WILDCARD 
     362 
     363 
     364# maxSta number 
     365# The number of stations to be used by gmew must be specified with 
     366# the maxSta command. This is the number of unique SNs to be used; each 
     367# SN combination can have any number of components. The maxSta command 
     368# must come before any "Pri" commands. 
     369 
     370maxSta 100 
     371 
     372# maxDist km 
     373# The maximum epicenter - station distance in kilometers.  
     374# Stations lying outside this radius will not be used by gmew. 
     375# 
     376maxDist 600 
     377 
     378 
     379# maxTrace nsamples 
     380# The maximum number of trace data samples to process from one SCNL. 
     381# This is the product of the trace length in seconds and the highest  
     382# expected sample rate. For example, 10 minutes of data at 100 samples per 
     383# second gives 60000 samples. 
     384 
     385maxTrace 60000 
     386 
     387 
     388# staLoc: station location source 
     389#    Choices: File < loc-file> - get station locations from a hyp2000-format 
     390#                               file named loc-file 
     391#             EWDB - query the EW database for station locations; access info 
     392#                    given below. 
     393 
     394staLoc File /earthworm/run/params/hypoinverse/stas/uw_sta.hinv 
     395 
     396 
     397# Regional Velocity model: must be specified as "@vel_model_file". Typically 
     398#    this will be the same file as used for binder_ew. 
     399 
     400@uw_velocity.d 
     401 
     402 
     403# traceSource: Where gmew will obtain trace data 
     404#    choices are: waveServer  - raw traces from wave_servers;  
     405#                              server-list is either a space separated list 
     406#                              of ip-address:port or  
     407#                           "File " 
     408#    default: waveServer with list of servers read from $EW_PARAMS/servers 
     409 
     410traceSource waveServer 123.45.67.89:16021 123.45.67.89:16022 
     411 
     412 
     413# Add STA COMP NET 
     414# Del STA COMP NET 
     415# SCNL selection is done by a selection list and a rejection list. 
     416# The station selection command `Add' specifies the names of  
     417# STA (station), COMP (component), and NET (network).  
     418# The wildcard `*' may be used for any or all of STA, COMP, NET. 
     419# COMP may be given as the first two letters of the component name, 
     420# to select all direction desgnators are accepted for that component. 
     421# If no Add commands are given, all SCNLs will be selected. 
     422# The Del command is used to put SCNLs on the rejection list: 
     423# for example: "Add * EL UW" followed by "Del LAB EL UW" to include 
     424# all ELE and ELN components from UW except LAB.ELE.UW and LAB.ELN.UW. 
     425# List as many Add and Del commands as desired, one to a line 
     426 
     427Add * BH * 
     428Add * HH * 
     429Add * SL * 
     430Add * EL * 
     431Del LAB * UW 
     432 
     433 
     434# respSource: Tells gmew where to get response information;  
     435#    Choices: EWDB - query the EW databse for pole-zero-gain responses. 
     436#             File < dirname*gt; < pz-filename-format> - find response files in the  
     437#                            directory dirname. dirname can be  
     438#                            a full directory name, or relative to $EW_PARAMS. 
     439#                            filename-format is a string similar to printf 
     440#                            format: %S, %C, %N are replaced by station,  
     441#                            component and network names, respectively, 
     442#                            all in upper case. Similarly %s, %c, %n work 
     443#                            for lower-case station, component and network. 
     444#                            The digraph %% stands for %; all other  
     445#                            characters are taken literally. 
     446#                            The response file format is that used by SAC. 
     447#  
     448#    default: none; you must specify one of the above choices. 
     449 
     450respSource File responses %S_%C_%N.pz 
     451 
     452 
     453# traceTimes start end 
     454# The start and end times for traces is set here.  
     455#   < start> is the number of seconds before estimated P arrival to start 
     456#           the trace. 
     457#   <end> is the number of seconds after estimated S arrival to end the trace. 
     458#   default: traceTimes 5.0 60.0 # starts trace 5 seconds before estimated P 
     459#           arrival and ends trace 60 seconds after estimated S arrival. 
     460 
     461traceTimes 5.0 60.0 
     462 
     463 
     464# searchWindow A B C D 
     465# The time window for searching for peak amplitudes is set here. 
     466#    <A> is the multiple of the estimated interval P - S to start the  
     467#        search before estimated S arrival. 
     468#    <B> is the minimum number of seconds before estimated S arrival to 
     469#        start the peak search. 
     470#    <C> is the multiple of the estimated interval P - S to end the 
     471#        search after the estimated S arrival. 
     472#    <D> is the minimum number of seconds after estimated S arrival to 
     473#        start the peak search. 
     474# default: searchWindow 0.0 2.0 0.0 30.0 # Search window runs from 2 seconds 
     475#        before to 30 seconds after the estimated S arrival, independent of 
     476#        the P - S interval. 
     477 
     478searchWindow 0.0 2.0 0.0 30.0 
     479 
     480#saveTrace: whether and how to save synthetic ground-motion traces 
     481#            If saveTrace command is absent, no traces will be saved. 
     482#   Choices: SAC <baseDir> <dirFormat> <filename-format> -  
     483#                  save gm traces in SAC-format files.  
     484#                baseDir specifies a fixed directory name. 
     485#                dirFormat gives a formattted subdirectory name; the 
     486#                  format string is that used for the "date" command applied 
     487#                  to the event origin time, with the addition of `%i'  
     488#                  to indicate the event ID. Be careful with this; some 
     489#                  formats produce output not compatible with file names. 
     490#                filename-format gives the formatted file name using 
     491#                  % to introduce one of the format specifiers "sScCnN%" 
     492#                  `s' is the station name in lower case; `S' is upper case 
     493#                  Likewise for component and network names; `%' stands for 
     494#                  itself. All other characters are taken literally. 
     495# 
     496#   default: None (no traces are saved.) 
     497 
     498 
     499# XMLDir dirname 
     500# Optional command to cause ground-motion results to be written to 
     501#   a ShakeMap XML file. This directory must already exist. 
     502XMLDir Shake/input 
     503 
     504# TempDir dirname 
     505# Temporary directory for writing XML file. If XMLDir is given, TempDir must 
     506#   also be given. On Solaris (Unix), these two directories should be on  
     507#   the same filesystem. This will ensure that the XML file will be complete 
     508#   as soon as it is moved into XMLDir. This directory must already exist. 
     509TempDir Shake/temp 
     510 
     511# MappingFile filename 
     512# To provide descriptive names in the shakemap XML file, a mapping file 
     513#   may optionally be given. This file contain mappings of SCNL to instrument  
     514#   type, SN to long station names, and N to agency names. 
     515MappingFile   PNSN.map               
     516                                     
     517 
     518# Debug N 
     519# There are several different debug features, listed below.  
     520# You can give one Debug command for each feature you want to turn on,  
     521# or you can add together the values of desired features and give  
     522# one Debug command. 
     523# value   feature 
     524#     1   trace and search times and P and S arrival estimates 
     525#     2   SCNL selection tests 
     526#    16   ws_client debugging 
     527#    32   poles. zeros and gain values 
     528#    64   trial frequency response functions to STDOUT 
     529#   128   full frequency response function to STDOUT 
     530 
     531 
     532# SCNL Parameters: normally this command will be given as "@SCNL_param_file" 
     533# to cause the separate file "SCNL_param_file" to be processed. 
     534 
     535# watchForAlarm S 
     536# Recognize ACTIVATE_MODULE messages to initiate processing for a window 
     537# S seconds long 
     538#watchForAlarm 30 
     539 
     540# AddSpectraResponseAt period 
     541# Add period to the list being processed 
     542# The first replaces the default list (0.3, 1.0, 3.0) 
     543# This does NOT affect what gets written to the ShakeMap XML 
     544#AddSpectraResponseAt 2.0 
     545#AddSpectraResponseAt 2.5 
     546}}} 
     547 
    33548 
    34549== Helpful Hints ==