1. About Correlator 4.0

The Correlator application facilitates stratigraphic correlation of cores from multiple holes at a drill site. Its features support for

• depth shifting of cores based on high-resolution core logging data, including images, to construct a core composite depth below sea floor (CCSF) depth scale; and
• splicing of selected core intervals to construct the most complete stratigraphic representation possible at a site. 

On the JOIDES Resolution (JR), the Correlator application documented here is used in conjunction with other applications within the stratigraphic correlation support (SCORS) ecosystem (Fig. 1-1), which are covered in a separate user guide (Table 1-1). 

Figure 1-1. Stratigraphic correlation support (SCORS) applications.

Table 1-1. Stratigraphic correlation support (SCORS) application documentation

Version 4.0 was released on 31 March 2022. It can be downloaded at

<GitHub link>

On the JR you don't need to download the application - access will be obvious, or assisted by JRSO staff.

Correlator installs a directory for its internal database at a default location that looks something like this:

• Documents [or other system folder] > Correlator > 4.0 > db | default.cfg | log | temp

When you import correlation data from a directory of choice, Correlator indexes the data and places them in this directory for internal use. You don’t have to be aware of this directory but can change the path if needed (Fig. 1-2).

Figure 1-2. Correlator File menu.

Affine tables created in Correlator versions 3 and 4 differ from those in version 2: they include additional information (last three columns, see Appendix 2) that allow Correlator to reconstruct the relationship between cores. Affine tables created in the production version, 2.1_rc2 can still be imported in 4.0 by right-clicking "Saved Tables" in the Data Manager (available once data are loaded) and choosing Import legacy affine table. However, because legacy affine tables have no record of the reference core used to create a TIE, all cores shifted by a TIE will be converted to status REL on import into 4.0. This has no effect on their cumulative offsets, which will be preserved, but users will have to rebuild the TIEs manually (as was the case in version 2). 

2. Correlator basic functions overview

2.1. Data Manager view

Correlator operates within a single window that can be expanded as much as available monitor space permits. The window can be toggled between the Data Manager view (Fig. 2.1-1) and the Display view (next section). To navigate between these views, use the button in the lower left corner of either window (Figs. 2.1-2).

Figure 2.1-1. Data Manager view. Also shown is the floating tool bar, where the top button can be used to toggle to the Display view.

 
The Data Manager view has two functional tabs across the top:

• The Data Manager tab (Fig. X) lists the files imported into Correlator and provides the functions for adding and managing the data in Correlator.
• The Generic Data tab displays data from files being imported when such an import is triggered in the Data Manager tab (otherwise it’s an empty grid). 

2.2. Display view

Correlator operates within a single window that has two major views: Data Manager view (previous section) and Display view (Fig 2.2-1). The views can be toggled with the button in the lower left corner of either window (Figs. 2.2-2).

Figure 2.2-1. Display view, with the Display Preferences tab open on the right.

Figure 2.2.-2. Button to switch to Data Manager view.

 
The Display view has three areas, two for data plotting and one for the functional controls, organized in four control tabs.

• The left plot area is for depth shifting, and the corresponding controls are in the Shift Cores tab.
• The right plot area is for the construction of splices, and the corresponding controls are in the Splice Cores tab. This plot area can be turned off at the top of the Display Preferences tab if more display space is preferred for depth shifting.
• The control area can be toggled among the following four tabs:
  • Close: This tab acts like a button and closes the control panel. The control panel can be opened again by clicking any of the other four tabs.
  • Shift Cores: This tab has controls for depth shifting, which are described in the Depth shift cores section.
  • Splice Cores: This tab has controls for splicing, which are described in the Construct the splice section.
  • Display Preferences: This tab has general data display controls, as shown in Fig. X.
  • Data Filters: This tab offers data filtering options, including decimate, smooth and cull (Fig. X).

2.2.1. Shift cores tab

This tab has functions for shifting cores, which are explained in the Depth shift cores section.

2.2.2. Splice cores tab

This tab has functions for shifting cores, which are explained in the Depth shift cores section.

2.2.3. Display Preferences tab

This tab offers numerous display options that applying to core shifting and splicing. These options should be self-explanatory. Load some data, shift some cores, make some splices, and the simply explore the options be clicking around - nothing will affect the data.

Figure 2.2-3. Display preferences.

2.2.4. Data Filters tab

The Data Filters controls are largely self-explanatory but require some commentary (Fig. 2.2-3).

• Data filters are applied to the data from all cores for a specified data type. For a more specific filtering of known intervals with severe core disturbance, etc., you have the option to apply a file with those intervals specified in the Correlator Downloader application, at the time of data download.
• At this time, data culling can only be specified for top of cores (to remove data from “exotic” material washed down from higher up in the hole). A future version will include culling from core bottoms (“exotic” material “sucked in” when the piston core was removed) and culling from section ends (“edge effect”).
• Some odd behavior has been observed when deleting a cull filter under certain circumstances, and this has not yet been repaired (no user pressure). An easy workaround is to re-load the data.

Figure 2.2-4. Three data filtering options on the Data Filter tab: Decimate, Gaussian Smoothing, and Cull. Shown is a 9-point Gaussian filter applied to the magnetic susceptibility data whereby both original and smoothed (white trace overlay) are plotted. The filter can be edited or deleted.

2.3. Application menus

The application menus are rarely needed and presented here for completeness.

2.3.1. File menu

Figure 2.3-1. File menu.

2.3.2. Edit menu

Figure 2.3-2. Edit menu.

2.3.3. View menu

The View menu has a few fundamental display preferences not available in the Display Preferences tab of the Display view (Fig. 2.3.3-1.)

Figure 2.3-3. View menu.

3. Manage data in Correlator

3.1. Prepare correlation data

Data directories

Correlator is relatively flexible in terms of data file content and formats. Its import functions allow you to specify the only columns it really requires: depth and data. However, having the data files in a consistent format makes the process simpler and reliable. The following are the recommendations should be considered to be best practices on the JR.

• Use the Correlator Downloader application to download data from the LIMS database. Refer to the separate user guide for that application.
• Create a folder for each site (example in Fig. 3.1-1).
• Download one file for each data type and hole into the site folder. Append data for each new core measured using the Append core feature in Correlator Downloader.
• Create an images folder in each site folder where you place all reduced section images for the hole.
  • Batch-download the cropped section half images for a hole into a separate folder.
  • Use the R script provided to crop and reduce the images, then move the reduced images to the images folder in the correlation data site folder.
  • A separate user guide describes how to use the R script.
• If you have existing affine and splice tables for the site, place them in the site folder as well.

Figure 3.1-1. Example of a site folder with correlation data.

Special case: multiple files for the same data type

One of the primary objectives of stratigraphic correlation is to correlate section data from a new hole rapidly to the data from one or more previous holes to check if coring gaps in previous holes are recovered in the current hole. If coring gaps are not covered adequately due to the change in water depth (mostly due to tides, but also other environmental and operations factors), you want to provide relative coring offset (drill down interval) instructions to the drillers in near-real time.

In order to achieve this objective, we implemented a special task multisensor logger (STMSL), also referred to as ‘fast track’, with the same type of magnetic susceptibility (MS) instrument as the one mounted on the primary whole-round multisensor logger (WRMSL). The two instruments are the same for all practical purposes, however, users have found that slight differences in the data may exist (normally negligible compared to the overall analytical error). In any case, the ultimate goal is to measure all sections on the WRMSL in the sequence they are recovered to provide a consistent final MS data set. The STMSL is only and specifically used to measure selected sections from a new hole as needed, thus out of sequence, to provide rapid assessments and instructions to the driller.

Here comes the trick: In order to be able to correlate data from the STMSL with data from the WRMS in Correlator, the two data sets must be imported as two different data types, MSTL and STMSL, even though they are in fact both MS.
The Correlator Downloader application assists you with that: make sure you check the Split by instrument check box when downloading MS data, which results in two separate data files. When importing to Correlator, you assign the explicit custom names WRMSL STMSL for the two data files and you'll be able to correlate them.

3.2. Summary of Data Manager functions

When launching Correlator, you land on the Data Manager page. If you arrive there for the first time, you have only one function available:

• Root: right-click to add data

As soon as the first data file is imported, Correlator creates a data directory for the site, using the site name from the data file, and the following data group folders:

• One folder for each imported data type. Within each data type, the imported data are represented by a line item for each hole.
• The Section Summaries folder described above, which needs one file and list item per hole.
• The Saved Tables folder where Correlator saves affine and splice tables for the site.

Here, the functions available at each directory level are summarized for general reference (Table 3.2-1).

Table 3.2-1. Summary of data management functions.

3.3. Add new data

Basic correlation data

To import data files:

• Right-click on the top item in the Data Manager window and select Add new data. 
  • A browser window opens that allows you to browse to the data files in your directory of choice (the path will stick for future imports and updates).
• Select a single file, or multiple files of the same type (and format). In the example in Fig. 3.2-1, magnetic susceptibility was selected for holes 361-U1476A and 361-U1476B.
  • The first 30 rows of data for each hole are displayed in the Generic Data tab (Fig. 3.2-1).
  • For commonly used data types, all column headers and column data should be automatically and correctly populated.
  • If that is not the case, you get a warning and must specify at least the Depth and the Data columns.
• Click the Import button at the bottom right and the focus returns to the Data Manager tab where a data summary line is added (Fig. 3.2-2).

Figure 3.2-1. The Import button opens in Generic Data window, where user may have to fill in the Data Type column by clicking on the header “Data Type” and selecting the appropriate item (in this case, Natural Gamma).

Figure 3.2-2. Upon importing data, line items for each data type and each hole are added in the Data Manager tab . Note the Saved Tables folder created for affine and splice tables later created. Also note the Section Summaries folder automatically created and populated with the section summaries from the LIMS registry (more on that below).

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 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 the Data Type column in the Generic Data tab empty and will not allow you to import until you have specified a name.
• 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 two MS files:

• Right-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. 
  • 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. However, 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 of an arrow from REF to SHIFT core, Correlator draws a line across the entire screen.

Adding more data

If you are correlating cores in real time, you will frequently add new data. 

To add more data:

• Go to the Data Manager window.
• If you  are returning from the Display window, you will get a message alerting you that the Display window will be cleared (Fig. 3.2-5).
• After you have imported the new data, you need to Load the data again anyway to get a current display. 

Figure 3.2-5. When a user adds new data to an existing, plotted data set, a warning is displayed to make the user ware that the display will be cleared with this action.

Note: if you want to update the existing data, e.g., because you added another core to the hole file, use Update from the context menu.

3.3. Import section summary files

What is the section summary for?

Correlator needs top and bottom depths of sections to compute splice intervals correctly. The application maintains an internal table for that purpose. Three options exist due to the evolution of the program and its use in different environments.

Method 1 (not recommended on the JR)

In Correlator version 1, the tops and bottoms of sections were computed by Correlator based on the imported data, which often resulted in small and sometimes larger errors in splice tables. This functionality still exists in version 4 for backward compatibility, however, it is disabled by default in the Correlator > Preferences menu (Fig. 3.3-1). In situations where users do not have a section summary file for upload, they can enable the Infer Section Summary if none is provided feature and for each data file loaded (those with "Enable" on in the Data List), Correlator gathers the minimum and maximum depths of data points for each section. If multiple data types are loaded for a hole, all data types are considered and the minimum of minima offsets is used as the top of section and the maximum of maxima offsets is used for the bottom of section.

Figure 3.3-1. The Preferences menu.
          

If this method is enabled, Correlator will give a message at the time of data import that the section summary was inferred from the data (Fig. 3.3-2).

Figure 3.3-2. Message if Correlator infers section boundaries from the data.

Method 2 (standard method on the JR)

Starting with Correlator version 2, a section summary file is uploaded automatically when the user imports data to Correlator, if that section file exists in the same directory as the data file(s). This is the standard process on the JR because the Correlation Downloader application automatically downloads a section summary file from LIMS along with the data files, and also updates the section file along with the data file when a new core is appended in the real-time correlation workflow. The user will see the section summary file in the data folder but must not upload it separately (Correlator would try to load it like a regular data file). If the section summary does not exist or cannot be uploaded because of an incompatible format, an error dialog appears.

Method 3 (not needed on the JR)

Alternatively, section summary files can also be imported “manually” by right-clicking on the Section Summaries item in the Correlator Data Manager and selecting the Import Section Summary Files(s) option. Once the user browses to the appropriate file and selects it, an import dialog window opens showing (part of) the file content (Fig. 3.3-3). You can Import or Cancel.

Fig. 3.3-3. Manual section summary import.

Note: the section summary can also be uploaded the same way as any data file, but that is usually meaningless because we don’t need to plot the sections that way. If you need to upload section summaries manually, make sure you do so from the Section Summaries item so Correlator uses them as intended.

3.4. Import core section images

Starting with Correlator version 4.0, you can use images for correlation. You need to prepare the images as described in section 3.1.

Important:

• You must first import some primary correlation data (and the associated section summary data) before you can import images.
  • If you don't, you get a warning (Fig. 3.4-1)
• The images must be JPEG format.
• The images should be ~230 pixels across since that is the maximum Correlator will display. That corresponds to maximum image sizes of ~200 kb.
  • If you try to import images >1 Mb you get a warning (Fig. 3.4-2).

To import images:

• Right-click on Images in the Data Manager window.
• Navigate to your local data directory
• Select the folder containing the JPEG images you want to import and click import.

3.4. Load

Once correlation data have been imported to Correlator and are listed in the hierarchy of the Data Manager window, they reside in Correlator’s own local database. You still need to load the data for display and correlation.

To load data:

• Select, then right-click on a line item in the Data Manager window
  • You can load an individual file, a set of files for a data type, or all files for a site.
  • Typically, you just load the entire site because it is lightning fast.
  • Make sure that the files you want to load are enabled. If saved, affine and splice tables are enabled and will be applied to the loaded data. 
• Select Load.
  • The Data Manager view turns into the Display view, where the data is plotted and correlation and splicing functions are available.
• If you import data and switch to the Display view without loading, a message will appear in the plot window reminding you that you need to load the data for them to be plotted (Fig. 3.4-1).

Figure 3.4-1. Message when switching to the Display window after a data import without using the Load function.

3.5. Update Correlator data

During the typical JR workflow, you will download the correlation data from LIMS each time the data from a new core are available. This iterative process is facilitated in at least two ways:

1. The Correlation Downloader application has features that allow the download to be executed efficiently with pre-configured parameters and, most importantly, by appending core data sets to the hole data file so the entire data sets do not need to be downloaded each time (see SCORS Downloader user guide).
2. The Correlator application remembers the source directory for each data file name so it can update its internal database efficiently.

To update the Correlator internal database with updated files:

• Select the highest practical item in the Data Manager, right-click and select Update.
  • If an update took place, you should get a confirmation (Fig. 3.5-1).
  • If you don’t get a confirmation, the data in Correlator were presumably up to date already.
• Select the top directory item and select Load to display the updated data in the Display window.
  • If you simply switch to the Display window without loading the data, you will get a message reminding you (Fig. 3.5-2).
  • Make sure you also load the affine and splice tables again, if applicable.

Figure 3.5-1. Data update context menu and confirmation dialog.

Figure 3.5-2. Reminder that you need to load the data after an update.

3.6. Export data

Export affine and splice tables

When working with the LIMS database, users on the JR will typically only be exporting affine tables and splice interval tables. Users will subsequently upload these two tables to the LIMS database for each correlated site, using the SCORS Uploader and Manager application, so all necessary data reports can be computed in, and reported from LIMS via the LORE reporting interface. This has the advantage that any LORE user can download any LIMS data type with the CCSF depth scale, or by splice, including data not used in the correlation process. 
To export an affine or splice table, right-click on the item and select Export from the context menu. Browse to your data folder for the site (if necessary) and save.
When you export affine and splice tables, you give them a name, and Correlator adds extensions *. affine.csv and *.sit.csv, respectively. It is advisable that you assign names to these files that make sense as the files will ultimately be uploaded to, and available from the LIMS database. In particular, use a naming scheme that helps you and others recognize associated affine and splice tables. 
Should you import an affine or splice table that you exported in an earlier session, be aware that Correlator will rename the files according to its internal rules.
•    It will ignore your name.
•    It will use the expedition, site and hole number information according to the data in your folder.
•    It will add the extension *.#.affine.table and *.#.sit.table, respectively, where # is an incremental number relative to the existing tables in the Data Manager. 

Export correlation data

The correlation data imported to, and managed in Correlator can also be exported using the context menu in the Data Manager window. The Export item is available for data types (all holes) or each hole separately. Such exports may be needed if users work outside of the LIMS ecosystem, such as users working with IODP data on shore or with non-IODP data. Even if generally working with LIMS on the JR, some users prefer to export directly from Correlator to make preliminary or even final plots. In such cases, users are reminded that they still need to upload the affine and splice tables to LIMS, as described in the previous section.

To export data from Correlator:

• Right-click on a data type folder in the Data Manager window
• Select Export from the context menu (Fig. 3.6-1).
  • The dialog in Fig. 3.6-2 appears.
• Optionally enter a prefix and/or suffix to be appended to the default file name created by Correlator.
• If you select neither Apply Affine nor Apply Splice:
  • the same raw data will be exported that were imported to Correlator.
  • A default file name will be created following the pattern Exp-Site-Hole_<data_type>_RAW
• If you select Apply Affine:
  • All the raw data for the specified holes, with the CCSF depth and the cumulative offset columns added, will be exported.
  • A default file name will be created following the pattern Exp-Site-Hole_<data_type>_SHIFTED
• If you select Apply Splice (which also selects the associated Affine):
  • The data belonging to the splice will be exported.
  • If the data type folder with all hole data was selected for the export (typical case), the splice intervals from all holes are combined into the proper splice.
  • A default file name will be created following the pattern:  <data_type>_SPLICED
• Click the Export menu item.
  • A browser window opens.
• Browse to your data folder of choice and click OK.

Figure 3.6-1. Data export context menu.

Figure 3.6-2. Export options. A. Export all raw data for this data type. B. Export all data with CCSF depth column added for this data type. C. Export the splice for this data type.

Export spliced data and images

(New)

4. Depth shift cores

4.1. Depth shift concepts

(Update)

4.2. Shift cores with the TIE method

(Update)

4.3. Shift cores with the SET method

(Update)

4.4. Undo shifts

(Update)

4.5. Manage affine tables

(Update)

5. Construct the splice

5.1. Splice concepts

(update)

5.2. Create a basic splice

(update)

5.3. Insert a core into an existing splice

(update)

5.4. Shifting cores that are already part of a splice

Concept and rules

Ideally, depth shifting should be concluded before a splice is assembled. However, life is not ideal and you may want to shift a core after you have constructed a splice. Because splice intervals are defined by their CCSF depths, shifting their cores invalidates the splice interval boundaries. A core shift results in a gap, an overlap, or both in the splice, depending whether a chain of tied cores or a single core are shifted, and whether the core(s) are shifted up or down. Correlator will deal with each situation in a clearly defined manner and provide you with relevant information.

Splice intervals boundaries are specified relative to the CCSF depth scale defined by the core sifts. The reason we select a certain core interval as being a splice interval is based on our interpretation of core quality based on the proxy data used to correlate the cores. The interval is therefore intrinsically defined by the the core-section-offset-in-section identity. When we shift cores we want to preserve that intrinsic splice interval. Therefore:

• Rule 1: Splice intervals are shifted with the cores they are associated with.
  • This inevitably creates at least one gap or one overlap in splice intervals.
• Rule 2: Overlaps in splice intervals are automatically resolved by 'clipping' the redundant part of the interval that is shifting.
  • We can do that because both overlapping intervals were approved as suitable for the splice and which one to use is typically a toss-up. You can always move the spice interval boundary very easily if that is not your desired solution.
  • The core-section-offset identity of the clipped splice interval boundary is reverse-computed from the CCSF depth to the CSF-A depth, from where the offset (cm) from top of section is obtained.
• Rule 3: Gaps created by the shifting of splice intervals are left open and you need to go and close them.
  • We prefer not to do that automatically because the interval needed to close the gap has not explicitly been assigned to the splice.

Example

Here is an example of your options and the program's responses when you shift cores that are part of a splice.

Case 1: Shift chain down

'This core and all related cores below' down

• You define a new tie from REF core A3 to SHIFT core B3 where the tie point in SHIFT core B3 is dz m shallower than the REF tie point in A3. This means the SHIFT core will shift down (Fig. X).
• You select “This core and all related cores below”
• The program asks for confirmation of the action (Fig. X), and assuming you OK it:
  • Replaces the previous tie with the new tie and shifts core B3 with all related cores from all holes that are deeper than REF core A3 downwards by dz m, maintaining all ties below the new one.
  • Shifts all splice intervals from from the shifting cores downwards by dz.
  • Creates a gap of length dz between splice intervals A3 and B3 and extends the CCSF scale by dz m.
• You cover the splice gap with a segment from either core A3 or B3, or partially with segments from both cores - it is up to you to decide.

Fig. X. Dialog for repairing a splice gap 

Figure X. Dialog for non-existent core interval. 

• • This solution is not valid, interval boundary falls outside the core.
  • Click the OK button and you return to the four options.

• The third option on the menu allows users to cover the gap with a combination of extensions from both splice intervals using the normal interactive splicing interface.
• The final option cancels the shift and nothing happens to cores or splice intervals.

Case 2: Shift chain up

'This core and all related cores below' up

• Define a new tie from REF core A3 to SHIFT core B3 where the tie point in SHIFT core B3 is dz m deeper than the REF tie point in A3. This means the SHIFT core will shift up (Fig. X).
• Select “This core and all related cores below” and click OK.
  • Results are analogous to those described in previous case.
• Because this action has shortened the CCSF scale, an overlap is created at the top of the splice interval representing the shifted cores. The overlap can be removed completely with a segment from either core A3 or B3, or partially with segments from both cores - it is up to you to decide. Correlator offers you the options in a pop-up window (Fig. X).

Figure X. Dialog for repairing a splice overlap. 

• • "This shift creates an overlap in the splice. How do you want to proceed?’
    • Clip the splice interval from core A3
    • Clip the splice interval from core B3
    • Leave the overlap and let me fix the splice manually
    • Cancel shift

• The first two options apply an “auto-fix”.  The calculated sample identity is validated and if the section-offset doesn’t actually exist in the same core, an error dialog is presented (Fig. X).

Figure X. Dialog for non-existent core interval.

• • This solution is not valid, interval boundary falls outside the core.
  • Click the OK button and you return to the four options.

• The third option on the menu allows users to remove the overlap with a combination of clipping parts from both splice intervals using the normal interactive splicing interface.
• The final option cancels the shift and nothing happens to cores or splice intervals.

Case 3: Shift single core down

'This core only' up

• Define a new tie from REF core A3 to SHIFT core B3 where the tie point in SHIFT core B3 is dz m shallower than the REF tie point in A3. This means the SHIFT core will shift down (Fig. X).
• Select “This core only” and click OK:
  • Replaces the previous tie with the new tie and shifts core B3 downwards by dz m.
• Because this action has not changed the total length of the CCSF scale, a gap is created at the top of the core and an overlap is created at the bottom of the core. The gap and overlap can each be repaired in two ways (see the first two cases) and Correlator therefore simply reminds you to do so yourself using the normal splice interface, or cancel the shift (Fig. X):

Fig. X. Dialog for repairing a single core splice gap and overlap.

• • "This shift creates a gap and an overlap in the splice. The splice interval associated with this core is therefore deleted and you need to splice it in again".
  • Cancel shift

Case 4: Shift single core up

'This core only' up

• Define a new tie from REF core A3 to SHIFT core B3 where the tie point in SHIFT core B3 is dz m deeper than the REF tie point in A3. This means the SHIFT core will shift up (Fig. X).
• Select “This core only” and click OK:
  • Replaces the previous tie with the new tie and shifts core B3 upwards by dz m.
• Because this action has not changed the total length of the CCSF scale, an overlap is created at the top of the core and a gap is created at the bottom of the core. The gap and overlap can each be repaired in two ways (see the first two cases) and Correlator therefore simply reminds you to do so yourself using the normal splice interface, or cancel the shift (Fig. X):

Fig. X. Dialog for repairing a single core splice gap and overlap.

• • "This shift creates a gap and an overlap in the splice. The splice interval associated with this core is therefore deleted and you need to splice it in again".
  • Cancel shift

5.5. Manage splice tables