Sei sulla pagina 1di 12

Output Core Dips Log

Output core dips log.................................................................................................................................................................

Running the Output core dips log program.............................................................................................................................

Tailoring the program to personal tastes and available resources...........................................................................................

Printing.....................................................................................................................................................................................

Saving the log as an enhanced metafile...................................................................................................................................

Saving the log as a device independent bitmap.......................................................................................................................

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

0
Output core dips log
Program summary:

1. Reads core dip data files and plots the core dips log.

2. User options for plotting include choice of:

a. Depth range to be plotted.

b. Vertical scale.

c. Plot stick plots, Borehole deviation and Comments, according to space and availablity.

d. Plot header information or not.

e. Output language for header information (English or French).

f. Page numbers in place of date.

g. Store the log as a Device Independent Bitmap for export or future on-screen viewing.

h. Store the log as an Enhanced Metafile that can be used by Viewlog.

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

1. Core dip data file ALLFC.

2. The borehole information file CORE.INI.

3. Feature attributes file ATTRIBUTES.INI.

4. Borehole deviation file (if it exists).

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

1. COREDIPS.DIB, the Device Independent Bitmap.

2. COREDIPS.EMF, the enhanced metafile.

1
Running the Output core dips log program
On execution of the program the current RGLDIP working directory is shown in the program window:

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

The Styles menu enables the software to be tailored to personal tastes. Not all commands are available all the
time. When disabled the command text in the menu and corresponding icon on the toolbar are greyed. In
particular the Select section-length command is only available prior to opening a logfile.

2
Select the Select working directory command to change the working directory if necessary. This
displays the dialog box where the working directory can be selected:

Select the Select plotting options command to get to the dialog box where these options can be set:

The information displayed initially is taken from the borehole information file CORE.INI, or is set according
to the availablity of other data files: ORIENTB.

Borehole name. This is a character string. It is reproduced in the header block of the printed log, in exactly the
form that it is displayed here. Edit it as necessary.

Processing depths. These are displayed in m or ft and are initially the start and finish depths for the dip data in
the working directory. Edit them as necessary to plot only a section of this data.

Nominal borehole diameter. This is displayed in m or ft according to depth units. Edit it if necessary.

Feature types. Two character strings up to 10 characters long contain the labels for the two feature types
available:

1. The 1st (upper) was associated with features assigned type-index 0, e.g. bedding, banding or some sort of
pervasive planar structure.

2. The 2nd (lower) was associated with features assigned type-index 2, e.g. fractures or veins.

Edit these as necessary.

Vertical scale. This only concerns the printed log, it should be in the range 4 thru 500. When viewed on screen
vertical scale depends on screen resolution. Some images on the log: core, sinusoids, stick-plots, are plotted
with horizontal scale = vertical. Your choice of vertical scale will determine whether or not there is the
horizontal space available, on A4 paper, to plot your selection of plots.

Direction in core facing observer. The default is 45 , edit this value as appropriate. If there is a dominant dip
direction in the log it is conviently displayed by having it oriented towards the right in the core, i.e. the
direction in the core facing the observed is the dominant dip direction +90 . The 1st stick-plot is draw at -90
to the direction you specify here, the 2nd in that direction.

3
Shade identified units. Leave this option selected to stipple the units you identified by associating two features
of the same type.

Optional plots. According to availability, Borehole deviation and Comments channels become
available/unavailable for plotting. Availability is shown greyed and cannot be changed. Compose the selection
of available channels you require by selecting or deselecting the individual plot check boxes.

Screen display. Creation of the screen display bitmap is time consuming for long logs. Print preview (File
menu) provides a sort of page by page browsing of the log.

The dialog box is closed by selecting O.K. to retain your selection of options, or Cancel to abort your selection
of options. If the dialog box was closed with OK an ‘O.K. to continue?’ message box appears:

Select Yes to carry on with the program according to selected options, No to go back to the commands menu
aborting the selected options, or Cancel to go back to the commands menu retaining the selected options.

If the screen display option has been selected the hourglass cursor appears while the bitmap is being calculated.
A progress bar appears which is progressively filled as the calculation proceeds. When complete the log is
shown in the program window and the program waits for a user command:

If the screen display option has not been selected the program waits for a user command. Select the Print
preview and/or Print commands to perform standard windows printing. Use the Save log in
4
metafile command to save the log in enhanced metafile COREDIPS.EMF, or the Save log in bitmap
command to save it as a device independent bitmap COREDIPS.DIB.

If the log length exceeds the current section-length the Up50m and/or Down50m commands are
available. Use these to display the next section of log upwards or downwards.

The borehole/log information command can be used at any stage to display information about the log
and the current processing parameters:

This is for information only, nothing can be changed here. The Exit command terminates the Output
core dips log program and returns control to the main RGLDIP menu.

Tailoring the program to personal tastes and available


resources
Use the Styles menu to access commands that enable the log to be shown according to personal tastes and
available system resources:

Unrolled image format. This provides a choice between N-oriented or S-oriented format for the borehole wall
image.

Numeric dips. This provides choice between dip-azimuth and dip format, or strike and dip format, for
reporting dips.

5
Feature colors. This provides selection of colors to represent features assigned to bedding/banding and
fractures/veins.

Output language. This provides a choice between English or French as the language for header information on
the printed log.

Section length. Select this command to change the current section-length for multisection processing of long
logs. Optimum section length is controlled by the amount of memory available. Any of the following error
messages indicate insufficient memory:

"Insufficient memory to store bitmap array"

"hBitmap*: CreateDIBitmap failed"

"hmDC*: CreateCompatibleDC failed"

The only solutions are to reduce the section-length, or to deselect screen display of the log. Printing and print
preview are not subject to these memory constraints.

Printing
When an image is displayed on the screen, or the Plotting options dialog box is closed with screen display
deselected, the Print and Print preview commands are available. Selection of either gives a
Printer plotting options dialog box where various options can be selected:

6
LOG DEPTHS - 3 pre-set depth ranges are available for plotting: the complete log, the depth range selected for
processing, or the current section. None of these can be changed at this stage, if one of these ranges is
appropriate select its corresponding Plot button. If none of these is appropriate enter the required Start and
Finish depths for the User-defined depth-range, then select the Plot user-defined depth range button.

HEADER INFORMATION - If this check box is selected a header block is printed at the top of the first page of
the log.

NUMBER PAGES - If this check box is selected successive pages of the log will be numbered lower-right of
the page when printed, in place of the current date. If selected, when the dialog box is closed with OK, a Page
numbering dialog box appears:

The default start page number is 1, successive pages will be numbered sequentially. Edit this number if the log
is to be bound into a report, where the page numbering should start at a different number.

Saving the log as an enhanced metafile


When the log is displayed on the screen, or the Plotting options dialog box is closed with screen display
deselected, the Save image in metafile command is available. This command saves the log image in an
enhanced metafile COREDIPS.EMF. If this command is selected and an existing metafile COREDIPS.EMF is
found in the current working directory, the Metafile name for saving the image dialog box appears:

Drop down the box to get a list of all filenames in the working directory with the .EMF extension. Either select
an existing file and modify its filename, or enter the new filename in the box. The Metafile/Bitmap plotting
options dialog box appears:

7
3 pre-set depth ranges are available for plotting: the complete log, the depth range selected for processing, or
the current section. None of these can be changed at this stage, if one of these ranges is appropriate select its
corresponding Plot button. If none of these is appropriate enter the required Start and Finish depths for the
User-defined depth-range, then select the Plot user-defined depth range button.

Once created there is an option to view the image stored in the metafile:

If it is displayed use the Remove displayed metafile image command to clear the display if necessary.

The enhanced metafile can be imported into Viewlog for presentation along with other log data.

Saving the log as a device independent bitmap


When an image is displayed on the screen, or the Plotting options dialog box is closed with screen display
deselected, the Save image in bitmap command, , is available. This saves the log image in a device
independent bitmap COREDIPS.DIB. If this command is selected and an existing bitmap COREDIPS.DIB is
found in the current working directory, the Bitmap name for saving the image dialog box appears:

Drop down the box to get a list of all filenames in the working directory with the .DIB extension. Either select
an existing file and modify its filename, or enter the new filename in the box. The Metafile/Bitmap plotting
options dialog box appears:

8
3 pre-set depth ranges are available for plotting: the complete log, the depth range selected for processing, or
the current section. None of these can be changed at this stage, if one of these ranges is appropriate select its
corresponding Plot button. If none of these is appropriate enter the required Start and Finish depths for the
User-defined depth-range, then select the Plot user-defined depth range button.

9
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.

Errors fall into 2 groups:

1. FILE HANDLING. The program uses:

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

a. "ss10font.dat file not found in \RGLDIP" or "failed to read ss10font.dat file" - this file has been deleted
or become unreadable. Reinstall it from the distribution CD by selecting a custom installation, then select the
RGLDIP files group.

b. "color file not found in \RGLDIP" or "failed to read color file" - file BTVCOLOR has been deleted or
become unreadable. Try reselecting the color palette on the Acoustic Televiewer Processing page of the main
RGLDIP menu. If this does not work, reinstall it from the distribution CD by selecting a custom installation,
then select the RGLDIP files group.

c. "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.

Data files for individual logging runs in working directories off \RGLDIP\WELL. Possible error messages are:

a. "failed to open dips file allfc" or "failed to read dips file allfc" - this file has been deleted or become
unreadable. If you can not recover it from some backup try rerunning the Input core dips program, this may
recover some of the dips in readable form. Failing this the only option is to delete the existing file ALLFC and
repeat the Input core dips stage, which will recreate it.

b. "No sonde orientation data read from file orientN" - this file has been deleted or become unreadable. If
you can not recover it from some backup try rerunning the relevant dipmeter/BHTV/OPTV data input
program, which will recreate it.

c. "Failed to create screen bitmap arrays" - this message indicates that some file operation to do with
creation of the screen display has resulted in an untrapped error. This may involve the core dips file ALLFC, or
the selected borehole deviation data file ORIENTn.

2. MEMORY MANAGEMENT.

The length of log that can be displayed on the screen depends of the amount of memory available on the local
system. Any of the following error messages, or a blank screen appearing where you were expecting a log to
appear, mean that the currently selected section-length should be reduced:

10
“Out of memory”

"Insufficient memory to store screen bitmap arrays"

"hBitmap*: CreateBitmap failed"

"hmDC*: CreateCompatibleDC failed"

"hPrevBitmap*: SelectObject failed"

"p*Brush: CreateSolidBrush failed"

"hmDC*: BitBlt failed"

Optimum section length should be established by trial and error for the local system.

11

Potrebbero piacerti anche