Changes between Version 2 and Version 3 of Example_Configurations


Ignore:
Timestamp:
11/13/11 16:48:07 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Example_Configurations

    v2 v3  
    3737Second a participating module must broadcast periodic heartbeat messages, at or above the promised rate, as stated in its .desc file. These will be received by [wiki:statmgr statmgr]. If [wiki:statmgr statmgr] does not receive a heartbeat within the advertised time period, it will initiate the actions specified in the .desc file. Such actions can include issuing notification, and terminating and restarting the offending module. This restart feature has proven to be very useful for communication modules that are subject to unusual failure modes. 
    3838 
    39 Third, a module may issue status (error) messages in the standard format. These are received by [wiki:statmgr statmgr], and the actions specified in the .desc file are taken. Since the architecture allows one input and one output per module, helper modules called [wiki:copystatus copystatus] are used to move status and heartbeat messages from various rings to the ring to which statmgr is listening. 
     39Third, a module may issue status (error) messages in the standard format. These are received by [wiki:statmgr statmgr], and the actions specified in the .desc file are taken. Since the architecture allows one input and one output per module, helper modules called [wiki:copystatus copystatus] are used to move status and heartbeat messages from various rings to the ring to which [wiki:statmgr statmgr] is listening. 
    4040 
    4141This configuration has three sources of trace data, all of which broadcast into a message ring named Wave_Ring: 
    4242 
    43 Four ref2_ew modules, each of which controls a communications line, receives trace data from a remote RefTek data logger, and broadcasts standard [wiki:Earthworm Earthworm] format trace data. 
    44 A sun_demux module, which receives trace data from UofW's own digitizer, demultiplexes it, and produces standard trace data messages, 
    45 And an import-generic module: this is the long-distance message receiver. It communicates with its companion module export_scn via a TCP socket connection. Any type of [wiki:Earthworm Earthworm] messages can be shipped in this way; in this case, several channels of trace data are being received from Menlo Park. The shipping delay is on the order of several seconds, plus transmission time. 
    46 The trace data messages must be in the standard internal [wiki:Earthworm Earthworm] format, as described in .../src/include/trace_buf.h. Briefly, this format consists of a header followed by a variable number of data samples, represented as either 16 or 32 bit signed integers in either byte order. This format supports two channel identification schemes: The dominant scheme consists of three ASCII strings defining the 'station', 'component', and 'network' (SCN names). The second is the 'pin number'. This is an integer that can be used to identify the sensor and signal path of a channel. It addresses the case where a given sensor is acquired by two different telemetry paths. It also provides support for processing data from sensors that do not have SCN names. 
     43Four [wiki:reftek2ew reftek2ew] modules, each of which controls a communications line, receives trace data from a remote Reftek data logger, and broadcasts standard [wiki:Earthworm Earthworm] format trace data. 
    4744 
    48 Four modules listen to the messages on the Wave_Ring: 
     45A sun_demux module (now extinct), which receives trace data from University of Washington's own digitizer, demultiplexes it, and produces standard trace data messages, 
    4946 
    50 WaveServerV: This module maintains rotating histories of selected channels, and offers a service capable of supplying requested segments of historic trace data. 
    51 export_scn: This is the long-distance shipping module (companion to import_generic), specialized to send specific data channels (Station, Component, Network names). In this application, several selected channels of data are being sent to another installation. 
    52 copystatus, which conducts status messages and heartbeats to the Hypo_ring. statmgr is listening to that ring, and will be able to receive and process them. 
     47And an [wiki:import_generic import-generic] module: this is the long-distance message receiver. It communicates with its companion module export_scn via a TCP socket connection. Any type of [wiki:Earthworm Earthworm] messages can be shipped in this way; in this case, several channels of trace data are being received from Menlo Park. The shipping delay is on the order of several seconds, plus transmission time. 
     48 
     49The trace data messages must be in the standard internal [wiki:Earthworm Earthworm] format, as described in .../src/include/trace_buf.h. Briefly, this format consists of a header followed by a variable number of data samples, represented as either 16 or 32 bit signed integers in either byte order. This format supports two channel identification schemes: The dominant scheme consists of three ASCII strings defining the 'station', 'component', 'network', and 'location' (SCNL names). The second is the 'pin number'. This is an integer that can be used to identify the sensor and signal path of a channel. It addresses the case where a given sensor is acquired by two different telemetry paths. It also provides support for processing data from sensors that do not have SCNL names. 
     50 
     51'''Four modules listen to the messages on the Wave_Ring:''' 
     52 
     53 * [wiki:waveserverV waveserverV]: This module maintains rotating histories of selected channels, and offers a service capable of supplying requested segments of historic trace data. 
     54 
     55 * [wiki:export_scn export_scn]: This is the long-distance shipping module (companion to [wiki:import_generic import_generic]), specialized to send specific data channels (Station, Component, Network names). In this application, several selected channels of data are being sent to another installation. 
     56 
     57* [wiki:copystatus copystatus], which conducts status messages and heartbeats to the HYPO_RING. statmgr is listening to that ring, and will be able to receive and process them. 
    5358pick_ew, as above, listens to selected trace channels, and produces pick and coda messages (along with status and heartbeat messages). These are broadcast into Pick_Ring. 
    5459Three modules listen to the messages on Pick_Ring: