Changes between Version 1 and Version 2 of import_ida


Ignore:
Timestamp:
03/18/12 16:12:39 (9 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • import_ida

    v1 v2  
    88 
    99== Details == 
     10[wiki:Import-Export Import-Export Overview] 
     11 
    1012Import_ida acquires data from one or more Project IDA data servers, reformats them into !TracePackets and loads them into an Earthworm transport ring. The communication with the data server(s) is done using the idatap-1.2.1 toolkit available from the University of California, San Diego via 
    1113 
     
    1618Network timeouts are dealt with transparently to the application by the idatap library, which will retry and reconnect as necessary until successfull or until a more serious error occurs, at which point import_ida assumes the responsibility for reestablishing the connection. The import_ida.d parameter file includes an option for specifying the policy to follow when reconnecting after a loss of communication. One may chose to request the next packet in sequence (to minimize gaps in the acquired data set) or to request the most recently available data (to minimize delays). 
    1719 
     20=== Example Configuration File === 
     21{{{ 
     22# @(#)import_ida.d      1.1 12/26/97 
     23# import_ida parameter file 
    1824 
     25#  Basic Earthworm setup: 
     26 
     27MyModuleId         MOD_IMPORT_IDA # module id for this process 
     28OutRing            WAVE_RING      # output ring 
     29HeartBeatInterval  30             # seconds between heartbeats 
     30 
     31# We need to assign unique pin numbers to each net/sta/chan triple that 
     32# gets sent to the output ring.  Give the name of the file that contains 
     33# this information.  The format of this file must be the same as what 
     34# pick_ew expects.  You can create your own file with IDA specific 
     35# entries (see ida.sta for an example), or you can add the required  
     36# information to the pick_ew station file.  The picker parameters are 
     37# not required here, and as far as this program is concerned those fields 
     38# may be left blank. 
     39 
     40PinnoFile          ida.sta 
     41 
     42# It is up to the user to insure that there are entries in the above file 
     43# for all expected net/sta/chan triples, however the program will work even 
     44# if the database is incomplete.  In such a case, an unresolved net/sta/chan 
     45# will be assigned a default pin number of 12345.  You can override this 
     46# default by specifying an alternate value. 
     47 
     48DefaultPinno       12345 
     49 
     50# Define the policy to follow when reconnecting after circuit timeouts. 
     51# There are two choices: MINIMAL_GAP, or MINIMAL_DELAY.  If the former 
     52# is selected then the program will request the flow start at the end of 
     53# whatever has been received so far.  If the latter is selected then the 
     54# program will request the flow start with the most recent packet available 
     55# on the server. 
     56 
     57Policy             MINIMAL_DELAY 
     58 
     59# The network code for Project IDA stations is II, and that is the default 
     60# code which gets loaded into the packet headers.  If you want to override 
     61# this with some other code, enter it here. 
     62 
     63Network            II 
     64 
     65# List the server(s) and stream(s) that are desired. 
     66# The station channel specifications should follow the syntax 
     67# described in ftp://idahub.ucsd.edu:/pub/pickup/idatap-1.2.1.tar.Z 
     68# 
     69# You can give either the fully qualified host name, or its IP address 
     70# in the usual decmial dot notation (eg, 111.22.333.44) 
     71# 
     72#          Hostname              Station/channel list 
     73 
     74server   nnn.xxx.mmm.5        nna:bhz+pfo:bhz+sur:bhz 
     75}}} 
    1976 
    2077== Helpful Hints == 
     78 
     79== Helpful Hints ==