Changeset 2163


Ignore:
Timestamp:
05/19/06 10:21:12 (14 years ago)
Author:
paulf
Message:

mitch's changes for his email address instead of Barbara

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/ewdoc/WEB_DOC/USER_GUIDE/Inst_config_guide.htm

    r2160 r2163  
    6060<FONT FACE="Courier New" SIZE=5><P>4. PRODUCE A NETWORK STATION LIST</FONT><FONT SIZE=1> </P> 
    6161</FONT><FONT FACE="Courier New"><P>* Request an IRIS-sanctioned network identifier from Tim Ahern, IRIS DMC, Seattle Washington. This two-letter code is used throughout the system as part of the trace data naming convention. It is also essential if any data exchange with other networks is contemplated.</FONT> </P> 
    62 <FONT FACE="Courier New"><P>* Request an Earthworm "Installation Id" from Barbara Bogaert, USGS Golden. Barbara will update the distribution to include your new installation id, and issue an updated "earthworm_global.d" to all involved installations.</FONT> </P> 
     62<FONT FACE="Courier New"><P>* Request an Earthworm "Installation Id" from Mitch Withers, CERI, Memphis. Mitch will update the distribution to include your new installation id, and issue an updated "earthworm_global.d" to all involved installations.</FONT> </P> 
    6363<FONT FACE="Courier New"><P>* Earthworm uses the IRIS "Station, Component, Network" channel naming convention. See the IRIS web site for details. An installation is free to define its own naming convention, but this may present problems if linkages to other institutions are desired.</FONT> </P> 
    6464<FONT FACE="Courier New"><P>* Define all station names and locations, and produce a station list in hypoinverse format. If some parameters are not known, use unique temporary names and values which can later be search-and-replaced with real values.</FONT> <BR> 
     
    8080<FONT FACE="Courier New"><P>* Many Earthworm systems can exchange messages.</FONT> </P> 
    8181<FONT FACE="Courier New"><P>To implement this, each message, as it is generated, is given a 'shipping label' which contains the numeric values of "Installation Id", "Module Id", "Message Type". The "Installation Id" is the name of the installation at which this Earthworm is running. The "Module Id" is the name of the module which generated this message, and "Message Type" is the name of the type of message this is (eg. trace data, pick, location, heartbeat, etc)</FONT> </P> 
    82 <FONT FACE="Courier New"><P>Since any message may be shipped to any installation, this combination has to be unique amongst all Earthworm installations. This is assured by keeping the "Installation Id" unique. These are assigned by Barbara Bogaert, USGS Golden Colorado.</FONT> </P> 
     82<FONT FACE="Courier New"><P>Since any message may be shipped to any installation, this combination has to be unique amongst all Earthworm installations. This is assured by keeping the "Installation Id" unique. These are assigned by Mitch Withers, CERI Memphis Tennessee.</FONT> </P> 
    8383<FONT FACE="Courier New"><P>A module specifies which messages it is interested in listening to by specifying the 'shipping label'. Therefore, to be general, the "Module Id" must be unique within an installation. (Note that a module may specify a list of desired 'shipping labels', as well as specify wild-card values for selected portions of a label.)</FONT> </P> 
    8484<FONT FACE="Courier New"><P>In order to facilitate meaningful data exchange, there have to be "Message Type" values which are common to all installations. That is, if two installations decide to exchange pick data, both systems must have the same value for "Message Type" pick. Any installation can, of course, define additional private "Message Type" for its own internal purposes.</FONT> </P> 
    8585<FONT FACE="Courier New"><P>"Ring Names" are used by each module to specify which message ring the module is to 'listen to', and which ring it is to broadcast messages into. These names must be unique to each node. A set of traditional names have evolved, (eg. WAVE_RING, HYPO_RING, etc) and it is recommend to adhere to those, as it greatly reduces the amount of editing required.</FONT> </P> 
    86 <FONT FACE="Courier New"><P>The names appear in the configuration files of each module in the form of ASCII strings. The tables which define the numeric values of those strings are stored in two files: "earthworm.d" and "earthworm_global.d". "earthworm_global.d" contains the definitions which are common to all Earthworm sites: the "Installation Id" and "Message Type" values which are exchanged between installations. Changes to this file are coordinated through Barbara Bogaert, USGS Golden. "earthworm.d" contains definitions for local "Message Type", "Module Id", and "Ring Name".</FONT> </P> 
     86<FONT FACE="Courier New"><P>The names appear in the configuration files of each module in the form of ASCII strings. The tables which define the numeric values of those strings are stored in two files: "earthworm.d" and "earthworm_global.d". "earthworm_global.d" contains the definitions which are common to all Earthworm sites: the "Installation Id" and "Message Type" values which are exchanged between installations. Changes to this file are coordinated through Mitch Withers, CERI, Memphis. "earthworm.d" contains definitions for local "Message Type", "Module Id", and "Ring Name".</FONT> </P> 
    8787<FONT FACE="Courier New"><P>In the Earthworm release these two files are included in the subdirectory "environment". They have to be moved from there to the local /run/params directory (see section 7).</FONT> </P> 
    8888<P>&nbsp;</P> 
     
    125125&nbsp; </P> 
    126126<FONT FACE="Courier New" SIZE=5><P>8. CONFIGURE THE EARTHWORM ENVIRONMENT FILES</FONT><FONT SIZE=1> </P> 
    127 </FONT><FONT FACE="Courier New"><P>* The earthworm_global.d file should contain your Installation Id. Contact Barbara Bogaert, USGS Golden, who acts as control for this file. Local editing of this file is possible, but will prevent the installation form exchanging data with other sites.</FONT> </P> 
     127</FONT><FONT FACE="Courier New"><P>* The earthworm_global.d file should contain your Installation Id. Contact Mitch Withers, CERI, Memphis, who acts as control for this file. Local editing of this file is possible, but will prevent the installation form exchanging data with other sites.</FONT> </P> 
    128128<FONT FACE="Courier New"><P>* Edit earthworm.d: Using your Earthworm software diagram, enter a definition for each each mesasage Ring Name and Module ID at each node. At this point, do not alter the Message Types found there, but use the default entries.</FONT> </P> 
    129129<FONT FACE="Courier New"><P>* Create a .cmd file for each node. This file contains the environment variables used by the Earthworm system. As mentioned above, these files are platform specific, and currently three versions exist: for Windows 2000 and NT: "ew_nt.cmd", for Solaris on Sparc: "ew_sol_sparc.cmd", and for Solaris on Intel: "ew_sol_intel.cmd". (OS/2 has sadly been dropped). Thus, for example, one would create files such as "ew_sol_sparc_central.cmd", "ew_nt_remote1.cmd", and "ew_nt_remote2.cmd".</FONT> </P> 
Note: See TracChangeset for help on using the changeset viewer.