...
Table 1-21. Stratigraphic correlation support (SCORS) applications and documentation
Software application | Task | Documentation |
Correlator | Stratigraphic correlation of cores from multiple holes at a drill site, by depth shifting cores using high-resolution core logging data and constructing a core composite depth below sea floor (CCSF) depth scale, and by splicing selected core intervals to construct the most complete stratigraphy possible at a site. | scors_correlator_ug_20190321 |
Correlation Downloader | Download core logging data from the LIMS database, with options to filter the data as appropriate, and to append new core data to hole files. | scors_lims_ug_20190321.docx |
SCORS Uploader and Manager | Load affine tables and splice interval tables created by an external application (e.g., Correlator) to the LIMS database where the information can be reported and applied to all data in LIMS. | |
LORE Reports for Stratigraphic Correlation | Provide (A) lists of existing affine tables and splice interval tables, with links to uploaded user files; (B) detailed, LIMS-computed affine and splice interval tables; (C) CCSF (alternate) depths for any data set in the LIMS; and (D) data sets by selected splice. |
2. Manage data in Correlator
3. Depth shift cores
4. Construct the splice
4.1. Splice concepts
(update)
4.2. Create a basic splice
(update)
4.3. Insert a core into an existing splice
(update)
4.4. Change the affine during the splicing process
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 'This core and all related cores below' or only a single core are shifted, and whether the core(s) are shifted up or down. No worries, Correlator will guide you through the process of fixing the gaps and overlaps! Let's go through the four cases by example (Fig. X).
Shift 'This core and all related cores below' down
- 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 and all related cores below” and click OK:
- 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.
- Maintains all ties below the new one.
- Extends the CCSF scale by dz m.
- Because this is a frequent and standard operation, no user dialog is triggered for the shift unless at least one of the cores A3 and B3 is part of a splice.
- All splice intervals associated with the shifting cores naturally shift as well by dz. This is computationally done by adding dz to the CCSF depth of the splice interval boundaries. No change occurs to the sample identities (Hole-Core-Section-Offset) or the CSF-A depth of the splice interval boundaries, they remain as explicitly defined by the user.
- Because this action has extended the CCSF scale, a gap is created at the top of the shallowest of the shifted cores.
- The gap can be covered 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:
- "This shift creates a gap in the splice. How do you want to proceed?’
- Extend the splice interval from core A3 downwards
- Extend the splice interval from core B3 upwards
- Leave the gap and let me fix the splice manually
- Cancel shift
- "This shift creates a gap in the splice. How do you want to proceed?’
Note: This menu and messaging will change based on the scenarios and edge cases.
6. Filling the gap means revising one or two splice interval boundaries. The new splice interval boundary is defined at the CCSF depth scale, from which we can obtain the CSF-A depth of each section top using the cumulative offset (m) of the core, and then the offset (cm) from top of section.
6a. For the first two options, this is done with 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:
- ‘This solution is not valid, interval boundary falls outside the core. {OK}’
- The user falls back on the four options.
Note that alternatively, this validation could be carried out before showing the dialog in (5), and the dialog wouldn’t even show the invalid option.
6b. 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. These existing functions already trigger the calculation of the core identities for the modified splice intervals. Note: Implementing only this option (i.e., no auto-fix at all) should be considered too.
7. The final option cancels the shift and nothing happens to cores or splice intervals.
A very similar logic applies to the other shift cases (shifting related cores upwards, shifting a single core only, downwards or upwards), which we can spec out if and when we decide to move forward with the proposed approach.