...
Figure 2.2-2. Display preferences.
2.3. Application menus
...
Correlator is trying to help you with file naming upon import. However, sometimes you may need to help Correlator learn the import data file, such as when you use correlation data from sources other than the JRSO Downloader app.
One JR workflow, however, requires you to help a little even when using the Correlation Downloader. As described in section 3.1, you may have split the MS data into two files based on which core logger they were obtained from. What happens upon import depends to some degree on the file naming:
- If the files don't have 'susceptibility' in the file name, Correlator leaves auto-selects the Data Type column in the Generic Data tab empty and will not allow you to import until you have specified a namewith Susceptibility.
- If both files have 'susceptibility' in the file name, Correlator with automatically use 'Susceptibility' as the data type for the first file, but it will not import the the second one because it already has a 'Susceptibility' file (Fig. 3.2-3).
...
Figure 3.2-3. Correlator does not allow import of multiple files it thinks are the same data type.
To give unique data type names to you your two MS files:
- Right-click Click on the Data Type column header.
- Use the Custom data type item from the choice list (Fig. 3.2-4).
- For example, label the two files <SiteHole>_MS_WRMSL and <SiteHole>_MS_STMSL, respectively. susceptibility data types 'MS WRMSL' and 'MS STMSL', respectively (Fig. 3.2-4).
- If you click the check box Add Data Type to List, the The new data type labels will stick in the data type list for future use in your session.
- Proceed to selecting the appropriate items from the column menus for at least the following parameters, if they are not already auto-selected:
- Section
- TopOffset
- BottomOffset
- Depth
- Data
...
Figure 3.2-4. Registering a data type not available in the Correlator choice list.
Now you can correlate the STMSL data rapidly acquired on critical sections from a new hole to the WRMSL data from previous holes. HoweverNote, however, that because Correlator was not designed to correlate different data types (usually makes no sense) the affine table currently only keeps track of the SHIFT core (could be from either data file), with the assumption that the REF core tie point is from the same data type as the SHIFT tie point. Instead In Display view, instead of an arrow from REF to SHIFT core, Correlator draws a line across the entire screen.
...