Changes between Version 5 and Version 6 of gmew


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

--

Legend:

Unmodified
Added
Removed
Modified
  • gmew

    v5 v6  
    8888In 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. 
    8989 
    90 command arg1     function 
    91 Add STA COMP NET LOC    Event and Trace Commands 
     90The following list is organized by: 
     91 
     92command [argument here] 
     93 
     94 
     95'''Add [STA COMP NET LOC]'''[[BR]] 
     96Function: Event and Trace Commands 
     97 
    9298Add 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. 
     99{{{ 
    93100Default: all traces are selected from a trace source 
    94101Example: Add * BH * 
    95102         Add SEA EH UW 
    96 AddSpectraResponseAt period     Miscellaneous Commands 
     103}}} 
     104 
     105'''!AddSpectraResponseAt [period]'''[[BR]] 
     106Function: Miscellaneous Commands 
     107 
    97108Add 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. 
     109{{{ 
    98110Default: 0.3, 1.0 and 3.0 
    99111Example: AddSpectraResponseAt 2.0 
    100112         AddSpectraResponseAt 2.5 
    101 Debug D Miscellaneous Commands 
     113}}} 
     114 
     115'''Debug [D]'''[[BR]] 
     116Function: Miscellaneous Commands 
     117 
    102118Set 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: 
     119{{{ 
    1031201: 
    104121trace and search times and P and S arrival estimates (relative to event origin time) 
     
    115132256: 
    116133Input and output trace data including in padded arear to STDOUT. Produces several thousand lines for each SCNL, which should be saved to a file. 
     134}}} 
     135{{{ 
    117136Default: 0; no debug output 
    118137Example: Debug 3 # turns on options 1 and 2 
    119 Del STA COMP NET LOC    Event and Trace Commands 
     138}}} 
     139 
     140'''Del [STA COMP NET LOC]'''[[BR]] 
     141Function: Event and Trace Commands 
     142 
    120143Delete 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. 
     144{{{ 
    121145Default: all traces are selected from a trace source 
    122146Example: Del SEA BH UW -- 
    123 getEventsFrom INST MOD   Earthworm Setup 
     147}}} 
     148 
     149'''getEventsFrom [INST MOD]'''[[BR]] 
     150Function: Earthworm Setup 
     151 
    124152Get 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. 
     153{{{ 
    125154Default:  none 
    126155Example:  getEventsFrom INST_WILDCARD MOD_EQPROC 
    127 HeartBeatInterval H      Earthworm Setup 
     156}}} 
     157 
     158'''!HeartBeatInterval [H]'''[[BR]] 
     159Function: Earthworm Setup 
     160 
    128161Send TYPE_HEARTBEAT messages every H seconds to the transport ring. 
     162{{{ 
    129163Default:  none 
    130164Example:  HeartbeatInterval 30 
    131 log switch: -lS Earthworm Setup 
     165}}} 
     166 
     167'''log switch: -lS'''[[BR]]      
     168Function: Earthworm Setup 
     169 
    132170This 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: 
     171{{{ 
    1331720: 
    134173Do not create a log file. Some logging data will be printed to the screen (stdout or stderr.) 
     
    1371762: 
    138177Create a log file as for option `1', but do not write anything to the screen (stdout or stderr.) 
     178}}} 
     179{{{ 
    139180Default: 1 
    140 Example (on the command-line):  -l0 (lower-case ell zero; turns off creation of 
    141         log file) 
    142 MappingFile map-file    Miscellaneous Commands 
     181Example (on the command-line):  -l0 (lower-case ell zero; turns off creation of log file) 
     182}}} 
     183 
     184'''!MappingFile [map-file]'''[[BR]] 
     185Function: Miscellaneous Commands 
     186 
    143187Specifes 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. 
     188{{{ 
    144189Default: no mapping file if this command is not given 
    145190Example: MappingFile NCSN.map 
    146 maxSta N        Memory Allocation 
     191}}} 
     192 
     193'''maxSta [N]'''[[BR]] 
     194Function: Memory Allocation 
     195 
    147196At 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. 
     197{{{ 
    148198Default: none, this command is required. 
    149199Example: maxSta 100 
    150 maxTrace M      Memory Allocation 
     200}}} 
     201 
     202'''maxTrace [M]'''[[BR]] 
     203Function: Memory Allocation 
     204 
    151205Allocate memory for MtraceTimes command and the estimated P and S phase arrival times. 
     206{{{ 
    152207Default: none, this command is required 
    153208Example: maxTrace 60000 
    154 MyModuleId mod_id       Earthworm setup 
     209}}} 
     210 
     211'''!MyModuleId [mod_id]'''[[BR]] 
     212Function: Earthworm setup 
     213 
    155214Sets 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. 
     215{{{ 
    156216Default: none 
    157217Example: MyModuleId MOD_LOCALMAG 
    158 respSource SOURCE [params]      Auxilliary Data Sources 
     218}}} 
     219 
     220'''respSource [SOURCE [params]]'''[[BR]] 
     221Function: Auxilliary Data Sources 
     222 
    159223Tells gmew where to find instrument response data. This command is required. Choices for SOURCE are: 
     224 
    160225FILE dirname pz-filename-format 
     226 
    161227find 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. 
     228 
    162229The 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. 
    163230 
    164231The 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: 
    165232 
    166  
     233{{{ 
    167234CONSTANT    0.50280E+11 
    168235ZEROS       3 
     
    177244       -0.75400E+03    0.00000E+00 
    178245       -0.10560E+04    0.00000E+00 
     246}}} 
     247 
    179248EWDB 
     249 
    180250Query an Earthworm Database for reponse information. Not currently implemented. 
     251{{{ 
    181252Default: none 
    182253Example: File /earthworm/responses %S_%C_%N.pz 
    183 RingInName ring Earthworm setup 
     254}}} 
     255 
     256'''!RingInName [ring]'''[[BR]] 
     257Function: Earthworm setup 
     258 
    184259Tells 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. 
     260{{{ 
    185261Default:  none 
    186262Example:  RingInName HYPO_RING 
    187 RingOutName ring        Earthworm setup 
     263}}} 
     264 
     265'''!RingOutName [ring]'''[[BR]] 
     266Function: Earthworm setup 
     267 
    188268Tells 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. 
     269{{{ 
    189270Default:  none 
    190271Example:  RingOutName SM_RING 
    191 saveTrace ST [params] DIR FORMAT        Event and Trace Commands 
     272}}} 
     273 
     274'''saveTrace [ST [params] DIR FORMAT]'''[[BR]] 
     275Function: Event and Trace Commands 
     276 
    192277Tells gmew whether and how to save synthetic traces. If the saveTrace command is absent, no traces will be saved. Choices for ST include: 
     278 
    193279SAC baseDir dirFormat filename-format 
     280 
    194281Save 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. 
     282 
    195283baseDir 
     284 
    196285Specifies 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. 
     286 
    197287dirFormat 
     288 
    198289Gives 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: 
     290{{{ 
    199291%C 
    200292Century number (the year divided by 100 and truncated to an integer as a decimal number [1,99]); single digits are preceded by 0. 
     
    233325%Y 
    234326Year, including the century (for example 1993), 
     327}}} 
     328 
    235329filename-format 
     330 
    236331Gives 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. 
    237332Gmew 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. 
     333{{{ 
    238334Default:  command is absent (no traces are saved) 
    239335Example: SAC /earthworm/SAC/GM %Y%j%i %S.%C.%N 
    240 SCNLpar STA COMP NET LOC special-parameters     Auxilliary Data Sources 
     336}}} 
     337 
     338'''SCNLpar [STA COMP NET LOC special-parameters]'''[[BR]] 
     339Function: Auxilliary Data Sources 
     340 
    241341Set 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: 
     342 
    242343@scnl_param_file 
     344 
    243345Note 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: 
    244 magnitude correction 
    245 This value is ignored by gmew; it is used only by the localmag module. 
    246 taper low-freq off 
    247 The 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. 
    248 taper low-freq on 
    249 The 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. 
    250 taper high-freq on 
    251 The frequency at the high end of the passband below which the cosine taper has a value of 1. 
     346 
     347'''magnitude correction''': This value is ignored by gmew; it is used only by the localmag module. 
     348 
     349'''taper low-freq off''': The 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. 
     350 
     351'''taper low-freq on''': The 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. 
     352 
     353'''taper high-freq on''': The frequency at the high end of the passband below which the cosine taper has a value of 1. 
    252354taper high-freq off 
    253355The 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. 
    254 clipping limit 
    255 The 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. 
    256 taper time interval 
    257 The 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. 
     356 
     357'''clipping limit''': The 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. 
     358 
     359'''taper time interval''': The 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. 
     360{{{ 
    258361Default: as described above 
    259362Example: SCNLpar SEA EHE UW -- 0.2   0.1 0.1 20 25   2.9e4 1.0 
    260 searchWindow A B C D    Amplitude Controls 
     363}}} 
     364 
     365'''searchWindow [A B C D]'''[[BR]] 
     366Function: Amplitude Controls 
     367 
    261368Specify 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: 
    262 A: 
    263 The 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. 
    264 B: 
    265 The minimum number of seconds before estimated S arrival to start the peak search. 
    266 C: 
    267 The multiple of the estimated interval P - S to end the search after the estimated S arrival. 
    268 D: 
    269 The minimum number of seconds after estimated S arrival to start the peak search. 
     369 
     370A: The 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. 
     371 
     372B: The minimum number of seconds before estimated S arrival to start the peak search. 
     373 
     374C: The multiple of the estimated interval P - S to end the search after the estimated S arrival. 
     375 
     376D: The minimum number of seconds after estimated S arrival to start the peak search. 
     377{{{ 
    270378Default: searchWindow 0.0 2.0 0.0 30.0 # Search window runs from 2 seconds 
    271379        before to 30 seconds after the estimated S arrival, independent of 
    272380        the P - S interval. 
    273381Example: searchWindow 0.1 2.0 2.0 15.0 # some random values 
    274 staLoc LOC [params]     Auxilliary Data Sources 
     382}}} 
     383 
     384'''staLoc [LOC [params]]'''[[BR]] 
     385Function: Auxilliary Data Sources 
     386 
    275387Tells 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: 
    276 File loc-file: 
    277 Get 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. 
    278 EWDB 
    279 Query the Earthworm database for station locations. Not currently implemented. 
     388 
     389File loc-file: Get 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. 
     390 
     391EWDB: Query the Earthworm database for station locations. Not currently implemented. 
     392{{{ 
    280393Default: none; this command is required 
    281394Example: staLoc File /earthworm/run/params/hypoinverse/stas/uw_sta.hinv 
    282 TempDir temp-dir        Miscellaneous Commands 
     395}}} 
     396 
     397'''!TempDir [temp-dir]'''[[BR]] 
     398Function: Miscellaneous Commands 
     399 
    283400Specify 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. 
     401{{{ 
    284402Default: none; this command is required if XMLDir is given 
    285403Example: TempDir Shake/temp 
    286 tracesource SOURCE [params]     Event and Trace Commands 
     404}}} 
     405 
     406'''tracesource [SOURCE [params]]'''[[BR]] 
     407Function: Event and Trace Commands 
     408 
    287409Directs gmew to obtain trace data from SOURCE. Choices are: 
    288 waveServer server-list 
    289 Obtain 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. 
    290 waveServer File server-file 
    291 Command 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. 
     410 
     411waveServer server-list: Obtain 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. 
     412 
     413waveServer File server-file: Command 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. 
     414 
    292415Gmew 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. 
    293  
     416{{{ 
    294417Default:  waveServer with list of servers read from the file $EW_PARAMS/servers 
    295418Example: traceSource waveServer 123.45.67.89:16021 123.45.67.89:16022 
    296 extraDelay DelaySecs    Event and Trace Commands 
     419}}} 
     420 
     421'''extraDelay [!DelaySecs]'''[[BR]] 
     422Function: Event and Trace Commands 
     423 
    297424This is the delay in seconds to wait after receiving an Event message to hit the waveServers for traces. 
    298 DelaySecs: 
    299 is the number of seconds to sleep. 
     425 
     426!DelaySecs: is the number of seconds to sleep. 
     427{{{ 
    300428Default: extraDelay 0 
    301429Example: extraDelay 20 
    302 traceTimes START END    Event and Trace Commands 
     430}}} 
     431 
     432'''traceTimes [START END]'''[[BR]] 
     433Function: Event and Trace Commands 
     434 
    303435Specify the start and end times of trace data to be used from any trace source. 
    304 START: 
    305 is the number of seconds before estimated P arrival to start the trace. 
    306 END: 
    307 is the number of seconds after estimated S arrival to end the trace. 
     436 
     437START: is the number of seconds before estimated P arrival to start the trace. 
     438 
     439END: is the number of seconds after estimated S arrival to end the trace. 
     440{{{ 
    308441Default: traceTimes 5.0 60.0 
    309442Example: traceTimes 10.0 40.0 
    310 velocity model  Auxilliary Data Sources 
    311 Read in the one-dimensional velocity model to be used to estimate P and S phase arrival times. This is done using the syntax: 
    312 @velocity_file 
     443}}} 
     444 
     445'''velocity [model]'''[[BR]] 
     446Function: Auxilliary Data Sources 
     447 
     448Read in the one-dimensional velocity model to be used to estimate P and S phase arrival times. This is done using the syntax: @velocity_file 
     449 
    313450Typically 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. 
     451{{{ 
    314452Default:  none 
    315453Example: @/earthworm/run/params/uw_velovity.d 
    316 watchForAlarm duration  Miscellaneous Commands 
     454}}} 
     455 
     456'''watchForAlarm [duration]'''[[BR]] 
     457Function: Miscellaneous Commands 
     458 
    317459Read 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. 
     460{{{ 
    318461Default: ignore ACTIVATE_MODULE messages 
    319462Example: watchForAlarm 10 
    320 wsTimeout M     Miscellaneous Commands 
     463}}} 
     464 
     465 
     466'''wsTimeout [M]'''[[BR]] 
     467Function: Miscellaneous Commands 
     468 
    321469Set 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. 
     470{{{ 
    322471Default: 5000 milliseconds 
    323472Example: wsTimeout 10000 
    324 XMLDir xml-dir  Miscellaneous Commands 
    325 Gmew 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.) 
     473}}} 
     474 
     475'''XMLDir [xml-dir]'''[[BR]] 
     476Function: Miscellaneous Commands 
     477 
     478Gmew 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.) 
     479{{{ 
    326480Default: XMLDir command not given; no XML file is written 
    327481Example: XMLDir  Shake/input 
     482}}} 
    328483 
    329484=== Sample Configuration File ===