Changes between Initial Version and Version 1 of v5.0


Ignore:
Timestamp:
01/17/12 12:54:25 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • v5.0

    v1 v1  
     1{{{ 
     2 
     3Earthworm Release Notes V5.0 
     4 
     5(June 12, 2000) 
     6Earthworm V5.0 Release 
     7********************** 
     86/12/00 
     9 
     10V5.0 Is Released 
     11**************** 
     12It can be retrieved from the Earthworm ftp site 
     13ftp://ghtftp.cr.usgs.gov/pub/OUTGOING/earthworm/release_v5.0 
     14 
     15 
     16New Features of EW V5.0 
     17*********************** 
     18Earthworm v5.0 contains an OPTIONAL Server Package. This server consists of: 
     19        *  a DBMS Server (Oracle v8, Standard Edition),  
     20        *  a web server (Apache), and  
     21        *  a map server (based on GMT).  
     22The initial suite of functions of this server are fairly minimal, but the idea 
     23is that the infrastructure is in place, and we will be in good position to 
     24produce additional capabilities. 
     25                Note that the Server Package is not required to run the 
     26Earthworm system. If no DBMS server is available, all Earthworm functions will 
     27continue to operate as before, and will be supported and enhanced as before. 
     28There will, however, be a growing suite of features which will be available 
     29only if a Server is available. 
     30 
     31The initial set of DBMS-based server features are: 
     32        * The DBMS is presumed to be a network-based service. That is, the DBMS 
     33server may reside in the local Earthworm computer, in another computer at the 
     34installation, or at a remote site.  
     35        * All event data, both parametric and waveform, known to the local 
     36Earthworm system can be loaded into the agreed-upon DBMS servers as it is 
     37computed (or received). 
     38        * An Earthworm system can send and/or accept real-time data to/from any 
     39number of DBMS servers (local or distant). 
     40        * A DBMS server can support any number of concurrent, authorized 
     41clients. 
     42        * All data feeds from a local Earthworm system to any DBMS servers are 
     43under exclusive control of the local Earthworm configuration. 
     44        * The DBMS server supports a web site offering rapid-response, 
     45interactive seismicity maps. The maps, and the associated pages, provide 
     46graphic access to event, trace, and station data in the DBMS. 
     47        * Event and station data, including instrument response, can be pushed 
     48to a browser client in SAC format. Other formats will be incorporated. 
     49        * Archiving of parametric and waveform data. 
     50 
     51For additional information about the Server Package, or for installation 
     52assistance, please contact me. 
     53 
     54OTHER NEW MODULES 
     55***************** 
     56 
     57LISS2EW 
     58Liss2ew is the earthworm module for receiving trace data from the Live Internet 
     59Seismic Server. The LISS is a protocol that provides trace data in mini-SEED 
     60format in near-real-time over an IP link. The liss2ew module will connect to 
     61one LISS, read selected streams of trace data, and write that trace data into 
     62the earthworm transport ring.  
     63 
     64EW2LISS 
     65Ew2liss is the Earthworm module for serving Earthworm trace data in LISS (Live 
     66Internet Seismic Server) format. The ew2liss module will convert selected SCNs 
     67(station-component-network) of trace data from an Earthworm transport ring, 
     68convert that data to miniSEED format, and serve the data to a single LISS 
     69client (such as liss2ew) over a IP network connection.  
     70 
     71 
     72CONTRIBUTED SOFTWARE 
     73************************** 
     74 
     75The contributed software can be found at  
     76   
     77ftp://ghtftp.cr.usgs.gov/pub/OUTGOING/earthworm/contributed_software 
     78 
     79UNIVERSITY OF UTAH: 
     80REFTOEW: Reftoew collects data from a UNR RefTek Data Server, a disk file or 
     81an  Earthworm transport ring.  The data (DT) packets are forwarded to the 
     82Earthworm Transport layer as TRACE_BUF format packets and optionally written to 
     83disk as binary SAC files. 
     84 
     85VOLCANO PROGRAM: 
     86The wonderful people at CVO have modified Carlsubtrig, Trig2disk, 
     87Heli_standalone, and Sgram for the greater flexibility required in the volcano 
     88networks. 
     89 
     90CARLSUBTRIG: Many new options regarding how subnets are triggered and which 
     91stations are saved. 
     92 
     93TRIG2DISK:  Functions Putaway.c SudsPutaway.c and AhPutaway.c were modified to 
     94use the named subnets now supplied by Carlsubtrig in naming the directories. 
     95 
     96HELI_STANDALONE:  Ported to NT.  
     97 
     98SGRAM: Ported to NT.  
     99 
     100In addition, an NT-based Earthworm interface has been developed by CVO, which 
     101replaces startstop, statmgr, and provides a GUI interface to various Earthworm 
     102functions.  
     103 
     104}}}