Input Core Dips

Input/Edit Core Dips................................................................................................................................................................

Running the Input/Edit Core Dips program............................................................................................................................

RGLDIP planes coding convention..........................................................................................................................................

Using the Feature attributes dialog box...................................................................................................................................

File PLANTYP.........................................................................................................................................................................

Error messages..........................................................................................................................................................................

0
Input/Edit Core Dips
Summary:

Input/Editing of dip data measured directly on oriented cores, with storage in RGLDIP format so that it can be
merged with Dipmeter, BHTV and/or OPTV dips for further interpretation.

Source files used (from working directory off \RGLDIP\WELL):

1. Borehole information file CORE.INI, DIPM.INI, BHTV.INI or OPTV.INI (if one exists).

2. Borehole deviation file ORIENT, ORIENTB or ORIENTG (if one exists).

Data files produced (in working directory off \RGLDIP\WELL):

1. Core dips file ALLFC.

2. Planes information file PLANTYP.

3. Borehole information file CORE.INI.

1
Running the Input/Edit Core Dips program
When the program is executed it displays the current RGLDIP working directory and information about the
borehole it contains in the program window, together with a summary of the RGLDIP planes coding
convention:

Program commands are accessed from either the toolbar or the Commands and Help menus:

2
The currently selected RGLDIP working directory can be changed by selecting the Select working directory
command, , dropping down the box in the resulting dialog window and selecting the required
directory:

The new working directory name and information about the borehole it contains are updated in the program
window.

Initial Input Mode.

On selection of the Select input options command, , the program looks for any existing borehole
deviation data file in the working directory. If one is found the Borehole deviation data dialog box appears:

In this example a BHTV deviation data file, ORIENTB, has been identified and is the default selection as the
source of deviation data. The alternatives here are to select the dipmeter deviation data, or, if the cores on
which the dips were measured are independently oriented, is to select the Do not use borehole deviation data
option. In this case the dips should be input in geographic coordinates (see below).

When there are no existing core dips for the current borehole, the Define number of dip types dialog box
appears:

Enter the appropriate number of dip types and select the coordinate system in which they are measured, then
close the box with O.K. and the Define dip types dialog box appears:

3
Enter the required type index (see the RGLDIP planes coding convention for further information), and up to
50 characters of text describing the dip type. The program will cycle through this dialog box for the number of
times there are dip types to be defined.

When definition of the dip types is finished, the Core dip data dialog box appears:

Enter the appropriate information, depth, dip-azimuth, dip and type-index, for the current dip. The Band Off,
Band Upper limit and Band Lower limit buttons are a group of radio buttons, one of them is always selected,
normally this is Band Off. Select the Band Upper limit to start defining a bed or band, then close the box with
O.K. The input data is displayed in the program window and a verification message box pops up:

4
When this is closed with Yes, the Feature attributes dialog box appears:

This is divided into 3 parts:

a. The upper part of the box, containing depth, dip and borehole deviation (if available) information, is for
information only. It can not be changed.

b. The central part of the box has 4 drop-down boxes listing standard repertoires of short, descriptive texts for
the feature: Type, Form, State and Remark. Select the appropriate entries. 4 lines of additional descriptive text
can also be entered. These may contain information not normally available from wire-line logging: results of
laboratory analyses, slickenline directions etc.

c. The lower part of the box has 4 edit boxes, where new descriptive texts for Type, Form, State and Remark
can be entered. When this part of the box is closed with Apply, the new texts are added to the standard
repertoires.

See topic Using the Feature attributes dialog box for further information.

The dip data can be input in any sequence depth-wise, except that once a feature has been assigned as a Band
Upper limit, the next feature input should be the corresponding Band Lower limit. There is a sort by depth
algorithm on termination of the program. The default type index displayed is the last one entered, it may be
more convenient to enter all the data of that type in succession, then move on to another type. Select the finish
after this data set box to terminate input and return to the main RGLDIP menu.

Edit mode.

When the program is executed and the working directory is found to contain existing core dips, this
information is displayed in the program window:

5
Selection of the Select input options command pops up a dialog box with the various available options:

1. Overwrite it: this will delete the existing core dips and you input new data to replace it.

2. Edit it: this will cycle through the existing data, from some selected start depth, with the possibility of
deleting it or changing it.

3. Add new data to it: this enables additional core dips to be added to the existing data.

4. Retain it unchanged: will terminate the program leaving the existing core dips unchanged.

Select one of these options. If the Edit option is selected Edit depth dialog box appears:

Enter the required start depth for editing the existing dips. Close the box with OK and the Edit core dip data
dialog box appears:

6
Select the delete this data set box to delete the current dip, otherwise leave the data unchanged or edit it as
necessary. Select the finish after this data set box to terminate editing. On closing the box with O.K. edited
data is displayed in the program window and a verification message box appears. Close this with Yes and the
Feature attributes dialog box appears (see above). If the finish after this data set box was selected the program
terminates and control returns to the RGLDIP master menu, otherwise the Edit core dip data dialog box
reappears containing the next dip upwards.

If the current working directory contains no borehole information file, i.e. no Dipmeter, BHTV or OPTV
processing has been done, prior to termination of the program the Set borehole information dialog box appears:

Enter the appropriate information and close the box with O.K. This will be displayed in the program window
and a verification message box pops up:

7
Close this with Yes and the borehole information file, CORE.INI, is created. The program terminates and
control returns to the RGLDIP master menu.

8
RGLDIP planes coding convention
Planes may be coded by type, 0 thru 9. Conventional RGLDIP type-indices are:

0: general ‘bedding’ (dipmeter interval correlation), user-defined (BHTV/OPTV).

1: dip data that has been edited out.

2: general ‘tectonic’, user-defined (dipmeter/BHTV/OPTV).

3: dip data from BHTV.

4: dip data from dipmeter pattern recognition.

5: dip data from OPTV.

6: dip data from core-logging.

7-9: user-defined.

Note:

a. the structural interpretation programs only know about types 0-6.

b. the fracture analysis programs also know about types 7-9.

Using the Feature attributes dialog box

The 4 standard repertoires of short, descriptive texts for features: Type, Form, State and Remark, are initially
read from file ATTRIBUTES.INI, in \RGLDIP. This file is copied into the current working directory
automatically if it does not already exist there and any subsequent additions to the descriptive texts, using the
Add new edit boxes, are added to this local copy of the attributes file, which becomes tailored to the particular
borehole.

File ATTRIBUTES.INI is also used in dipmeter, BHTV and OPTV processing. The descriptive texts that it
contains are oriented towards descriptions of features as seen by wireline-logging techniques. At the best these
include high-resolution borehole-wall imagery. Further information can be obtained from core samples:

1. Results of laboratory studies.

2. Nature of material in altered or mineralised fractures.

3. Features seen on the surface of fractures, e.g. slickenlines.

To accommodate this extra information 4 extra lines of user-supplied text can be entered in the middle part of
the Core dips Feature attributes dialog box. These are stored in the dip data file, ALLFC, rather than the local
copy of the attributes file.

9
File PLANTYP
Plantyp is a text file containing details of the plane types in the core dips file, e.g:

6 Core_dips

Line 1 contains the number of plane types. There is then a single line for each plane type, containing the type-
index (0 thru 9), a space and up to 50 characters of descriptive text. Each line is terminated with a newline
character.

Error messages
A variety of error-messages may appear. Fatal errors are shown in message-boxes with either an Exclamation
or a Stop icon:

Non-fatal errors are shown in message-boxes with a Question mark or Information icon:

Those with a question mark require a YES/NO user-response (the incorrect response may be fatal), those with
an information icon usually result from an illegal input by the user - close the message-box with OK and the
program takes you back to the stage where you can input a valid value or response.

FILE HANDLING. The program uses:

Standard RGLDIP files contained in directory \RGLDIP. Possible error messages are:

a. "failed to set the working directory" - this means that the default RGLDIP working directory,
\RGLDIP\WELL\DATA has been deleted. Recreate it by selecting the Create new RGLDIP working directory
option on the Core Processing page of the main RGLDIP menu and entering the name Data.

b. “failed to read dip data from file allfc” - this means that the existing core dips file, ALLFC, in the current
working directory, is unreadable. Unless it can be recovered from someplace else, the only option is to delete it.

c. “failed to copy file Attributes.ini to working directory” - this means that the copy file operation of
ATTRIBUTES.INI, from \RGLDIP into the current working directory, failed. Exit the program and perform
this operation manually in Explorer.

Data files for individual logging runs in working directories off \RGLDIP\WELL. When editing an existing
core log file the original data exists in the existing file ALLFC, the edited data is built up in file TEMP. Finally
the original ALLFC is removed and TEMP renamed to ALLFC. Possible error messages are:

“failed to open file allfc”, “failed to open file temp”, “failed to read file allfc”, “failed to write file temp”,
“failed to delete dip data file allfc” or "failed to rename file temp to allfc" - terminate the program and
perform this operation manually in Explorer.

Existing file PLANTYP is also read when editing an existing core log. Possible error messages are:

10
“failed to open file PLANTYP” or “failed to read file PLANTYP” - terminate the program, open file
PLANTYP with Notepad and edit it. It is a text file. See topic File PLANTYP for further details.

11