Changes between Version 2 and Version 3 of v6.3_to_v7.1


Ignore:
Timestamp:
01/17/12 12:45:33 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • v6.3_to_v7.1

    v2 v3  
    1111= Frequently Asked Questions = 
    1212 
    13 1. Which modules care about SCNL vs SCN? 
     13'''1. Which modules care about SCNL vs SCN?''' 
    1414 
    1515The simple answer is any module that deals with Tracebuf, Pick, or Coda messages cares. Thus, you will need to review the documentation for each module and see how it is affected. In short, look at your data_source modules and make sure that you have decided on a SCNL scheme and get them configured first. Then work your way downstream through your processing chain. The fir and pick_ew modules are next, followed by the binder module, and ultimately hypoinverse (aka hyp2000). Note that example SCNL .d files are provided in the src dir with each module. 
    1616 
    17 2. Can I use v7.X modules in a v6.3 environment? 
     17'''2. Can I use v7.X modules in a v6.3 environment?''' 
    1818 
    1919Yes, you can intermix messages since all V7.X messages are new types, so old and new can reside on the same rings. However you need to take care that you rename module names so that they do not collide with old versions. It is best to  limit those running newer versions of the modules and newer messages to reside on different rings. 
    2020 
    21 3. Can I use my old v6.X module in a v7.0 environment? 
     21'''3. Can I use my old v6.X module in a v7.0 environment?''' 
    2222 
    2323Yes, you can intermix, but realize that the v6.X module will only look for SCN message types and thus you will need to use a converter (scnl2scn) to get the SCNL data onto a separate ring in SCN format so that the v6.X module can operate. 
    2424 
    25 4. How can I get old messages into the new format? 
     25'''4. How can I get old messages into the new format?''' 
    2626 
    2727Easy, there are 2 converters that go forward and backward: scn2scnl and scnl2scn that will map all messages to the new or old format. They can be found in the data_exchange module directory. 
    2828 
    29 5. How can I import v7.X waveform data into my v6.X environment? 
     29'''5. How can I import v7.X waveform data into my v6.X environment?''' 
    3030 
    3131Simply grab the v7.X module you need to use to import the data (any of the data_exchange modules or data_source modules) and make sure it is named uniquely (so that it doesn't overwrite a v6.X version) and install it on your v6.3 system in the bin directory. Also grab the scnl2scn converter from v7.X and install that. Then, update your earthworm_global.d with the new message types found in v7.X (see the earthworm_global.d from the distro). Import the data into a new ring called WAVE_RING_SCNL and then setup scnl2scn to convert the data to where you want the waveforms. 
    3232 
    33 6. startstop v7.X won't work with my old configuration because it complains about missing messages, what did I miss? 
     33'''6. startstop v7.X won't work with my old configuration because it complains about missing messages, what did I miss?''' 
    3434 
    3535Because new features were added into startstop, Earthworm's core module, you need to add in new message types to your old earthworm.d and earthworm_global.d files. Add in the new message types, by doing a diff on the files 
    3636 
    37 7. How do I deal with my old v6.X SCN wave_serverV tanks? 
     37'''7. How do I deal with my old v6.X SCN wave_serverV tanks?''' 
    3838 
    3939 * If you have only a small amount of data you need to move from v6.X to v7.X, you can use waveman2disk to write the section of data you need in tankplayer format, then use the tankplayer module to replay that data back into a ring. Once it's in a ring, you can convert it with scn2scnl, and then import the converted tracebufs into a v7.X wave_serverV tank. Tankplayer doesn't have a fast forward mode, so this may take some time.