Changes between Version 16 and Version 17 of Installation_and_Configuration


Ignore:
Timestamp:
11/16/11 15:15:05 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Installation_and_Configuration

    v16 v17  
    1818 
    1919=== Analog data acquisition === 
    20 (e.g., [wiki:adsend adsend]): 12 or 16 bit A/D conversion, up to 256 channels per Windows 2000 machine, any number of such machines per system. 
    21  
    22 1.2. Digital acquisition (e.g., [wiki:slink2ew slink2ew]): Currently, most commercial data loggers (e.g., Q330, Reftek 130) are supported. All data streams, whether analog or digital, can be processed in the same manner. 
    23  
    24 1.3. Auto Location (e.g., [wiki:eqproc eqproc]): Automatic P-picking, event association, and hypo-inverse solutions. 
    25  
    26 1.4. Auto Notification (XXX): Selective event notification via e-mail or pager system. 
    27  
    28 1.5. STA/LTA Events ([wiki:carlstatrig carlstatrig] and [wiki:carlsubtrig carlsubtrig]): Traditional STA/LTA coincidence event generation. 
    29  
    30 1.6 Event Archive (e.g., [wiki:ew2mseed ew2mseed]): Events can be archived in various existing formats, including PC-SUDS, SAC, MiniSEED, AH, and UW2. Other archive formats will be integrated as required. 
    31  
    32 1.7. Error Processing ([wiki:statmgr statmgr] and [wiki:copystatus copystatus]): email and pager notification of system malfunctions. 
    33  
    34 1.8. Manual Events (XXX): Events can be declared manually within the time interval available in the on-line trace data storage. 
    35  
    36 1.9 On-line Trace Data Storage (XXX): all acquired trace data can be made available via an IP server for a configurable time period, ranging from hours to weeks. 
    37  
    38 1.10. Distributed systems (XXX): Any number of Earthworm systems can be linked via IP communication links. The extend of such linkages is configurable. Possible configurations include a 'master' central site and any number of remote nodes operating as one integrated system, as well as limited, negotiated linkages between two sovereign central systems. 
    39  
    40 1.11. Multi-machine configurations (XXX): Any number of networked Linux, Windows or Solaris computers can be combined to run one Earthworm system. 
    41  
    42 1.12 Data Exchange (e.g., [wiki:export_generic export_generic], [wiki:import_generic import_generic]): Any type of internal data can be exchanged in real time with other Earthworm systems. This exchange mechanism has proved to be quite reliable, and has performed well in numerous applications. It requires a communications link capable of physically interfacing to a computer's ethernet port and capable of carrying IP messages. It functions over the public internet as well as private dedicated links. 
    43  
    44 1.13. Long period Events (XXX): A volcanic long-period event detector, developed by John Evans at Menlo Park.  
     20(e.g., [wiki:adsend adsend]) 
     21 
     2212 or 16 bit A/D conversion, up to 256 channels per Windows 2000 machine, any number of such machines per system. 
     23 
     24=== Digital acquisition === 
     25(e.g., [wiki:slink2ew slink2ew]) 
     26 
     27Currently, most commercial data loggers (e.g., Q330, Reftek 130) are supported. All data streams, whether analog or digital, can be processed in the same manner. 
     28 
     29=== Auto Location === 
     30(e.g., [wiki:eqproc eqproc]) 
     31 
     32Automatic P-picking, event association, and hypo-inverse solutions. 
     33 
     34=== Auto Notification  ===  
     35(XXX) 
     36 
     37Selective event notification via e-mail or pager system. 
     38 
     39=== STA/LTA Events === 
     40([wiki:carlstatrig carlstatrig] and [wiki:carlsubtrig carlsubtrig]): 
     41 
     42Traditional STA/LTA coincidence event generation. 
     43 
     44=== Event Archive === 
     45(e.g., [wiki:ew2mseed ew2mseed]) 
     46 
     47Events can be archived in various existing formats, including PC-SUDS, SAC, MiniSEED, AH, and UW2. Other archive formats will be integrated as required. 
     48 
     49=== Error Processing === 
     50([wiki:statmgr statmgr] and [wiki:copystatus copystatus]) 
     51 
     52Email and pager notification of system malfunctions. 
     53 
     54=== Manual Events=== 
     55(XXX) 
     56 
     57Events can be declared manually within the time interval available in the on-line trace data storage. 
     58 
     59=== On-line Trace Data Storage === 
     60(XXX) 
     61 
     62All acquired trace data can be made available via an IP server for a configurable time period, ranging from hours to weeks. 
     63 
     64=== Distributed systems === 
     65(XXX) 
     66 
     67Any number of Earthworm systems can be linked via IP communication links. The extend of such linkages is configurable. Possible configurations include a 'master' central site and any number of remote nodes operating as one integrated system, as well as limited, negotiated linkages between two sovereign central systems. 
     68 
     69=== Multi-machine configurations === 
     70(XXX) 
     71 
     72Any number of networked Linux, Windows or Solaris computers can be combined to run one Earthworm system. 
     73 
     74=== Data Exchange === 
     75(e.g., [wiki:export_generic export_generic], [wiki:import_generic import_generic]) 
     76 
     77Any type of internal data can be exchanged in real time with other Earthworm systems. This exchange mechanism has proved to be quite reliable, and has performed well in numerous applications. It requires a communications link capable of physically interfacing to a computer's ethernet port and capable of carrying IP messages. It functions over the public internet as well as private dedicated links. 
     78 
     79=== Long period Events === 
     80(XXX) 
     81 
     82A volcanic long-period event detector, developed by John Evans at Menlo Park.  
    4583   
    4684  
     
    5088Earthworm has been developed under the mandate of speed and reliability. It therefore tends to use fast, low-level operating system services rather than high-level end-user packages. A side effect of this is that Earthworm is fairly economical in terms of hardware requirements. In general, a contemporary Pentium- or Ultra- class machine is adequate for most regional network loads. Specifically, the hardware requirements can be divided into four categories: 
    5189 
    52 a. Data acquisition: This can be via the ethernet network port, system bus, or serial ports. In practice, we have not observed problems in the first two cases. We have observed problems with serial port acquisition, especially when running on the same machine as the bus-based A/D acquisition. The symptoms are intermittent data loss from the serial ports, and warning messages from the A/D subsystem. 
    53  
    54 b. Numeric processing: This is not generally a problem when the current, common processing features are enabled. A contemporary machine (PentiumII or Sparc Ultra) has been demonstrated to be capable of supporting the numeric and I/O requirements of processing a large events on over 500 channels in rear-real time. However, modules are currently being worked on which may require considerable numeric resources. 
    55  
    56 c. On-line Trace Storage: This is provided by the [wiki:waveserverV waveserverV] module, which maintains a circular, on-line history of trace data . Each channel is maintained in a separate file, and the user is free to specify the location and size of each such file. In operation, trace data is written to these files as it is acquired, and multiple concurrent client programs can request data via network connections. Therefore, the critical hardware resources are disk storage capacity, disk access time, and network bandwidth. Disk storage requirements can be estimated by multiplying the number of channels to be served, the sampling rate, the number of bytes per sample, the time interval to be available, and an overhead factor of perhaps ten percent. Disk access time depends on the anticipated usage. A write is generated as each trace packet is acquired, and a burst of reads is generated with each client request. In practice, a contemporary 10,000 RPM SCSI disk supporting 64 channels seems conservative; twice that load is successfully functioning at some sites. 
     90=== Data acquisition === 
     91This can be via the ethernet network port, system bus, or serial ports. In practice, we have not observed problems in the first two cases. We have observed problems with serial port acquisition, especially when running on the same machine as the bus-based A/D acquisition. The symptoms are intermittent data loss from the serial ports, and warning messages from the A/D subsystem. 
     92 
     93=== Numeric processing === 
     94This is not generally a problem when the current, common processing features are enabled. A contemporary machine (PentiumII or Sparc Ultra) has been demonstrated to be capable of supporting the numeric and I/O requirements of processing a large events on over 500 channels in rear-real time. However, modules are currently being worked on which may require considerable numeric resources. 
     95 
     96=== On-line Trace Storage === 
     97This is provided by the [wiki:waveserverV waveserverV] module, which maintains a circular, on-line history of trace data . Each channel is maintained in a separate file, and the user is free to specify the location and size of each such file. In operation, trace data is written to these files as it is acquired, and multiple concurrent client programs can request data via network connections. Therefore, the critical hardware resources are disk storage capacity, disk access time, and network bandwidth. Disk storage requirements can be estimated by multiplying the number of channels to be served, the sampling rate, the number of bytes per sample, the time interval to be available, and an overhead factor of perhaps ten percent. Disk access time depends on the anticipated usage. A write is generated as each trace packet is acquired, and a burst of reads is generated with each client request. In practice, a contemporary 10,000 RPM SCSI disk supporting 64 channels seems conservative; twice that load is successfully functioning at some sites. 
    5798 
    5899Network bandwidth requirements are critical on the input side, as the trace input streams are real-time. The server-side responses, or course, are not. In situations where this is a concern, a second, dedicated ethernet subnet is usually established to carry real-time trace data, and the participating machines are equipped with two (or more) network adapters. 
    59100 
    60 d. Event storage and processing: As mentioned above, Earthworm can produce directories of event files from various triggers in various formats. Adequate disk space has to be provided to hold such events until they are moved to off-line media. Considerations there include the expected worst-case seismicity levels, time of storage, and off-line media capacity and life-time. 
     101=== Event storage and processing === 
     102As mentioned above, Earthworm can produce directories of event files from various triggers in various formats. Adequate disk space has to be provided to hold such events until they are moved to off-line media. Considerations there include the expected worst-case seismicity levels, time of storage, and off-line media capacity and life-time. 
    61103 
    62104* Determine the hardware required (or available) at each node and the central site.