Changes between Version 1 and Version 2 of eqcoda


Ignore:
Timestamp:
05/28/12 07:41:39 (8 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • eqcoda

    v1 v2  
    88 
    99== Details == 
    10 Eqcoda is a sub-module in Earthworm's event-processing mega-module. It processes the event messages output by either eqproc or eqprelim, and writes its own output in a format that can be read by either eqverify or hyp2000_mgr. Eqcoda is often the third link in the mega-module, started by eqbuf. It could, however, be started directly by eqprelim or eqproc. Eqcoda in turn starts the next link specified in its "PipeTo" command (generally eqverify) and communicates to the next link via a one-directional pipe. 
     10Eqcoda is a sub-module in Earthworm's event-processing mega-module. It processes the event messages output by either eqproc or eqprelim, and writes its own output in a format that can be read by either eqverify or hyp2000_mgr. Eqcoda is often the third link in the mega-module, started by eqbuf. It could, however, be started directly by eqprelim or eqproc. Eqcoda in turn starts the next link specified in its "!PipeTo" command (generally eqverify) and communicates to the next link via a one-directional pipe. 
    1111 
    1212Once the next link is started, eqcoda's job is to read the TYPE_EVENT2K messages produced by either eqprelim or eqproc, perform some coda envelope calculations, build a TYPE_HYP2000ARC message, and pass it on to the next link in the mega-module. Eqcoda passes all message types other than TYPE_EVENT2K directly to the next link without modifying them in any way.