Geoview & eLog:

Well Log Interpretation

Workshop SAMPLE IMAGE

BALI, INDONESIA
JANUARY 21, 2008
Geoview and eLog Course
Outline
Introduction to Geoview
User Interface Overview
Loading Well Logs
Deviated Wells
Exercise 1: Data Loading and Checkshot Corrections
Depth-time Tables
Well Log Data Management
Exercise 2: Well Log Editing
Exercise 3: Well Log Data Management
Exercise 4: Log Type Mapping
Introduction to eLog
Log Editing Tools
Exercise 5: Log Editing and Cross-plotting
Log Math Operations
Log Transforms
Exercise 6: Log Math

Exercise 7: Log Transforms

2
Introduction to Geoview
Geoview is the toolbar from which all of the Hampson-Russell software
products are launched.
Geoview is also the main database for the storage of well data.
The well database is managed through the Well Explorer program.
Within the Well Explorer, you can view and edit wells, logs, tops, and
deviation surveys.
Well data are loaded into Well Explorer either as:
ASCII Files (comma delimited, tab delimited, etc…)
LAS files
transferred directly from GeoFrame or OpenWorks.
typed into a table manually
Logs can be loaded individually or in groups
Logs can be measured in depth or time

3
 The Geoview and Well Explorer
Interfaces
Geoview, the Program
Launcher:

The Well Explorer:

4
The Geoview User Interface

Software Version

Program
Launch
Buttons

Location and name of the current well database

5
The Geoview User Interface
Under File > Settings:
Paths: Allows you to set commonly used directories for the default path
when opening well databases or projects or for importing for data.
Preferences: Allows you to change the appearance of the interface,
length of History list and “Most Recently Used” lists.
Measurement System: Allows you to specify the measurement system
defaults to either metric or imperial units.

Paths Menu Preferences Menu Measurement

System Menu 6
The Geoview User Interface

Under Database:
Open existing databases, create new databases, copy
databases or select from list of previously opened
databases.

Under Help:
View software information and support
information, view error messages, run debugging
tests and to access documentation.

7
 The Well Explorer User Interface
The Well Explorer program allows you to actively explore, view and manage
the well database.

< Table View

Curve View >

< Map View

Summary View >

8
The Log Display Window Interface
The Log Display Window
shows the well logs for
an individual well.
Overlying multiple logs
on the same track,
displaying the log tops,
selecting log colors,
setting log scales, color
fill and other features are
all available.
Log readouts are also
possible by clicking on
the window with the
cursor.

9
 Loading Well Logs

Well log information can be loaded into a Geoview database by importing the
information from ASCII files, by importing wells from OpenWorks or GeoFrame
well log databases, or by copying wells from another Geoview well database.

Other information that can be imported are well locations (spots) and DXF
drawing files containing culture information.

10
 Loading Wells From ASCII Files
The supported well log ASCII formats are: LAS, GMA, GeoQuest IES, and general
ASCII-format files.
Loading ASCII-format Well Logs is a straight-forward procedure and requires the
user to identify the data locations in the file.
1) Select the file(s)

2) Select the file format and data type

3) Identify the required file parameters

11
Loading Wells with the
OpenWorks Well Exchange:
To import well information from an OpenWorks well database:
First, Start OpenWorks Well Exchange program

and then, in the Hampson-Russell Well Log Exchange program, select the
File > Load OpenWorks Logs… option

12
Loading Wells with the
OpenWorks Well Exchange:
Select the wells, logs and tops that you want to import.

13
Loading Wells with the
GeoFrame Well Exchange:
The GeoFrame Well Exchange is an almost identical workflow.
First, start the GeoFrame Well Log Exchange program

and the select the File > Load GeoFrame Logs… option

14
 Loading Wells with the
GeoFrame Well Exchange:
And select the wells, logs and tops that you want to import.

15
Loading Well Logs by
Typing in a Table
For simple modeling exercises, you may
find it convenient to enter logs by typing
them in manually. This is done by first
creating a well or opening up an existing
well and then choosing to Create a new
log in table from the list of Log Options.

You will then be provided with an empty

log table that you can fill in by either
typing in the values or pasting from the
computer clipboard.

16
Deviated Wells

• Files of well path deviation data are loaded into the Well Explorer in the
same import menu as importing logs from files.
• Deviations are measured in either absolute X & Y coordinates, relative X
& Y coordinates (offsets) or dip and azimuth pairs.
• If you are transferring log data from OpenWorks or GeoFrame, the
deviation survey will automatically be picked up and transferred.
• The deviation information will be used to correct the log to vertical
(convert from MD (measured depth) to TVD (true vertical depth) ).

17
 Loading Deviated Geometry Files

Here is an example of a deviated

geometry file. It is a simple ASCII < Header
file with a number of header lines
followed by three columns of data:
measured depth, X and Y.
In this case, the deviation is in terms
of absolute X & Y coordinates.
Relative coordinates (offsets) would
also be acceptable as would dip and
azimuth pairs.

18
 Loading Deviated Geometry Files

When loading the deviated

geometry file, ensure that the
Type of Data is marked as
Deviated Geometry.

The file is read in by defining the

parameters of the ASCII file such
as the number of header lines
and the column numbers of the
data.

19
Log Types and Log Names

Every log within Geoview should have a ‘type’ and a ‘name’ associated
with it.
P-wave, density, neutron porosity, gamma ray are ‘log types’. It is
important that the log type is set correctly. The log type controls the
parameters and functionality you can perform with that log, e.g. displaying
different measurement units, relations and transforms etc…
The log names are used to distinguish logs of the same type from each
other by using a distinct name - for example, “P-wave_corr_1” and “P-
wave_corr_2” are different names for logs of type P-wave.
To make your project work easier, take the time to set the log types (and
log units) correctly in Geoview before you start working on a project.

20
Log Types and Log Names
Well Explorer Table View display of the logs for one well.

Log Name Log Type

21
Log Type Mapping
Hampson-Russell log types may not match other software log types. You can
define a table of log aliases to match imported log types to Hampson-Russell
log types.
For example, you may already
have a database with
compressional velocity logs
mapped as type “SONIC”. HRS
does not recognize logs of type
“SONIC” but it does recognize
“P-wave”. Log Type Mapping will
match the “SONIC” log type to
the HRS “P-wave” log type.
An ASCII file of commonly used
aliases can be created and
imported into other HRS well
databases.

22
 Depth-Time Logs
Some logs are automatically and internally computed – such as depth-time logs.
We usually want to know where our logs (measured in depth) correspond to the
seismic (measured in time). The depth-time log controls the conversion of
depth measurements to
time measurements for
each well.
A depth-time table is
usually computed
automatically from the
sonic velocity log.
Check shots and
manual correlations to
the seismic can be used
to modify the depth-
time table.
We will discuss this in
further detail after the
next exercise. 23
Exercise 1: Data Loading and
Check Shot Corrections
In this exercise, we will read in a real set of well logs from an LAS file and by
typing in a table. Next, we will explore the software interface, set the datum
and perform a simple checkshot correction. After the exercise, we will discuss
the depth-time curves, check shot corrections and the datum.

First, we will set the paths for the default

starting locations for data, project and
database locations.

Start Geoview.
(this will be either a Desktop icon or under
the Start > Programs > HRS Applications
menu)

We will not open or create a database

yet.

Click Cancel on the first menu.

24
Click on File > Settings > Paths… in the Geoview menu bar.

The Paths Preferences menu

allows you to set the default
starting path locations when
opening data (logs, horizons,
seismic), opening projects or
opening databases.
Set the Default Data Directory
path location as shown.
Click OK.
25
Now select Database > New.

Create a new well database called: geoview_database.

On the Well Explorer, select

Import Data > Logs,….

26
Find the file geoview_logs.las. Select the file and click Add >>

In this case, the software has

correctly identified this data to
be in LAS format.

Click Next >

Accept the destination well name

of Well 1 and click Next >

27
Now specify the Well Type to GAS WELL. You can also define X and Y
locations and the elevation properties, as well as the units:

In this case, the KB and surface elevations are contained within the
file headers and have automatically been read.

28
 Click on Next > to get the final log table:

Click on View File Contents.

29
This will open a Window that
shows you the log names and
units. In this case, the
parameters look correct.

Close this window and click

on OK on the log loading
window to complete the log
loading process.

Warning windows will

appear: click Yes to
complete the loading.

These messages refers to

the recorded Density and
Gamma Ray values found
between the KB and the
surface elevations (i.e., data
not in the ground)
30
The Measurement System window will appear.
Click OK to accept that the default measurements
will be using the Metric system.

For projects with a mixture of measurement, the

specific measurement units can be individually
changed.

31
Now that all the logs have been inserted into the database,
select Well 1 under the well name column and click Display Well.

This will make the Log Display

Window appear, showing the
logs and tops in Well 1.

32
 In the Log Display window, click on View > Display Options.
A menu appears that allows you to change the display
parameters. It has a number of tab pages as follows:

LAYOUT
The log display is
organized as a
series of tracks,
allowing multiple
log runs to be
plotted on top of
each other.
If you wish to
overlay logs,
simply tick both
logs in the same
track column.
In this example,
we will not overlay
any logs.

33
Active logs are the logs that will be
used in any operation, such as:
• the P-wave and density logs used to
compute the internal impedance (the
internal impedance log is used to
create the zero-offset synthetic)
• the P-wave and S-wave logs used to
compute Poisson’s Ratio
The active P-wave log also controls
which depth-time table is being used.

34
The Curves menu allows you to change the ranges of the log
amplitude tracks and the color of the logs. We will test this in a
later exercise.

35
Click on the Scale & Details tab and set the scale as shown below:

36
Click OK and scroll down to see the following display:

37
Now, in the Well Explorer,
click once on the blue
arrow to the left of Well 1
to list the logs in the well

Click on the arrow next to Tops

The tops can be edited from here >

Click the back arrow to return

to the previous window.

38
This well, in the foothills of the Rocky Mountains in
Alberta, ties to a seismic volume that was processed
with a seismic reference datum (SRD) of 2700 m.a.s.l.
In the Well Explorer, click on the SRD button to specify
the Seismic Reference Datum.
Set the Seismic Reference Datum elevation to 2700 m
and choose to Map datum to time zero. Click Next >>.

39
Right now, this well only has one depth-time curve that was computed
automatically. Check Recalculate option and select the Change option and
then click OK at the bottom of the menu.
Click OK to acknowledge the change in the message window.

40
Scroll up in the Log Display Window to the top of the log. The
red horizontal line represents the SRD and the location of time 0.

SRD = Time 0

41
Now we will apply a check shot correction to this well. To do this, we must
first enter check shot values.

On the Well Explorer window, click on Log Options > Create a new log in table
and select Check Shot for the log type.

42
A 7th log will appear with the log name of Check Shot 1.

Click on the arrow to the left to access the table. Complete the
table as shown below.

Depth Time
620 619
687 671

The check shot contains two pairs of values consisting of a depth and a two-
way time in ms.
Click Update, then click Yes to save the log values,

and then click the back arrow.

43
The new log is now listed in the Well Explorer. However, we have incorrectly
told the software that the log is relative to the KB when in fact it is relative to
surface.
Correct the Measured From reference for the Check Shot log to Surface and
click Update and then Yes when prompted. Now view the Log Display Window. 44
Even though the check shot log has been added, the check shot does not
modify the travel time correction until we choose to apply it.

45
To apply the check shot correction, click on Option > Check Shot Correction:

The Check Shot Parameters

menu appears. This allows
multiple choices of how to
apply the check shot
correction:

46
Also, the Check
Shot Analysis
window will be
displayed: By using the Apply
Relative Changes
option, the log
velocity values have
been changed here.

The curves on the right of the display show the sonic log before (red) and
after (black) check shot correction. The smooth curves on the left are the
depth-time tables before (red) and after (black) the check shot correction. The
middle track, the “drift curve” is the difference between the two depth-time
curves. 47
There are a number of modifications which could be made to the
automatic calculation:

1. Data points from the

checkshot survey can be
deleted.

Simply highlight the value to

remove and use Edit > Delete
Point to remove it.

We will not do this here as we

only have two points.

48
2. Change the “Type of
Interpolation” option.
Try different types and
click Apply to see how
they affect the time
depth curve correction.

A smoother may also

be applied to the
interpolation type.

49
3. Change the “Sonic Log
Changes” option and
test different methods.

This options controls

whether or not the log
velocities will be
altered by the check
shot application.

Apply relative
changes and Change depth-time
Apply all changes curve only leaves the
both modify the velocities untouched.
log velocities.

50
When you have finished testing all the parameters, we will save
the check shot corrected log.
Ensure that you have selected “Change depth-time curve only”
and “Spline” interpolation without a smoother.

Click Ok on the Check Shot Analysis window.

51
This menu now appears:

Click Ok on the menu. This will create a new check shot corrected
sonic log, with the name P-wave_chk.

-- End of Exercise 1 --
52
Depth-Time Logs
The depth-time logs control the depth-to-time conversion of each well.
The depth-time log is usually automatically calculated from the sonic log
velocities by integrating the quotients of the depth interval by the
interval velocity. Multiplying by two yields the two-way travel time. This
is expressed in the following equation:
i where: ti = time down to layer i
dj
ti = 2* ∑ dj = thickness of layer j
j =1 Vj Vj = velocity of layer j

Note: The time to an event depends on all

the velocities above that layer, including the
first velocity to the surface, V1. That
velocity is unknown and is usually
approximated by extrapolating the first
measured velocity back to the surface:

53
Depth-Time Logs
P-wave and Depth-Time logs are always paired.
In the example below, there are two P-wave logs and two associated
Depth-Time logs.

54
Depth-Time Logs
If you load:
a log of type P-wave, a DT_ curve is automatically created by integrating the
velocity values.
a log of type Depth-Time, you can either (1) create a new P-wave log or (2)
tie the Depth-Time log with an existing P-wave log.

If you delete:
• a DT_ log from Geoview, it is automatically recalculated.
• a P-wave log, the corresponding Depth-Time log will also be deleted.

55
Depth-Time Logs
Another option in the Well Explorer is to Copy the
Depth-Time curve from another well and replace an
existing Depth-Time curve.

56
Check Shot Corrections
Applying Check Shot Corrections to a sonic log is a standard process used
to ensure that the sonic log is placed at the correct time-depth location.

Seismic shots are detonated at the surface and receivers down the borehole
record the one-way travel times for a particular depth. This data is used to
modify the existing depth-time table.

The check shot correction can be applied

from any number of log display locations:
•Well Explorer

•eLog

•AVO Modeling

57
 Applying Check Shot Corrections
The Check Shot Analysis menu allows you to determine the method by which
you will update the depth-time table.
Since the depth-time table is tied to the P-wave velocity log, you will have to
make decisions about if and how to change the sonic log velocities and how to
interpolate the depth-time corrections between the check shot data pairs.

58
Applying Check Shot Corrections
The interpolation of points on the drift curve uses one of three options:

Linear: Honors the points exactly with straight line segments between.

Spline: Honors the points exactly with smooth curves between.

Polynomial: Fits a smooth curve using least-squares optimization.

59
Types of Check Shot Corrections

Changing the depth-time table implies a possible change in the original

sonic log velocities. There are three options:

1. Apply all changes.

This option changes all the velocities in
the log in such a way that the new log will
integrate to exactly the desired times.

Note: This involves a ramped velocity

above the first measured depth to handle
the bulk time shift and to minimize the
effect of spurious reflections on the
synthetic.

60
Types of Check Shot Corrections

2. Apply relative changes

This option changes the velocities for
layers between the first and last
check shot depth only.

No ramp is added above the first

measured depth.

The resulting log will integrate to the

desired times except for a bulk time
shift.

61
Types of Check Shot Corrections

3. Change depth-time curve only

This option does not change the
velocities in the sonic log.

The resulting log will not integrate to

the desired times, but GEOVIEW will
use the new depth-time table.

This option has the effect of

maintaining the original reflection
coefficients for synthetic calculations.

62
Types of Check Shot Corrections

The choice of which of these check shot options to use depends on what
the user is trying to achieve.

Use of either option 1 or 2 above can result in significant changes in the

measured sonic log velocities of the well. Therefore, in all cases where
the actual measured velocity values are going to be used, the user should
use the final option (Change depth-time curve only).

If you are going to use the velocity logs to build a velocity function for
time-to-depth conversion later on, the first option (Apply All Changes),
will guarantee that the velocity function will correctly tie the seismic times
to the log depths.

63
 Well Log Data Management
The Well Explorer Table View will list all of the wells in the database and
provides information for each well: X & Y surface location, Kelly Bushing (KB)
elevation, Surface elevation, Measurements units, Well Type, etc…

A vertical line indicates a vertical well

A wiggly line indicates a deviated well 64
Well Log Data Management
The well log database can be explored by using
the arrow keys to move into the wells, logs, tops
and deviated geometry files.

Clicking on these arrows will access the stored digital log data. 65
Manual Editing of Log Data

Log data can be edited manually using the Log Data Options button. As well,
the data can be quickly copied to and from the computer clipboard. 66
 Log Tops (Markers)

Log Tops can be entered

and modified easily in the
Well Explorer.

67
 Deviated Geometry
Deleting the
In the Log Table Deviated Geometry
View, click on the is also possible in
Deviated Geometry the Table View.
arrow to view the
well path deviation
surveys.

The Deviation
Survey Data can
also be edited if
required.

68
Deviated Geometry by Dip/Azimuth
If the deviated geometry is
specified in terms of Dip and
Azimuth there are two calculation
methods for interpreting the well
path: Minimum Curvature and
Tangential.
These can be changed in the Well
Explorer Table View of the
Deviated Geometry.
Tangential Method Minimum Curvature
The default method is Minimum Method
Curvature and accounts for the
bending of the well bore between
measurement points. The
Tangential Method uses straight-
lines to interpolate between
points.

69
Exercise 2: Editing data in Geoview
In this exercise, we will edit an erroneous data point in the density log.

From the Well Explorer window, access the density log data. With this data
window open, look at the Density log in the Log Display Window.
On the Density log
you will see a very
low log value at about
686.2 m vertical
depth. This data point
has to be removed
from the log values.

70
In the Well Explorer, try and find this low density value from
the log listing and delete it.

71
Can’t find the density value to delete?
Observe that the log window is displaying the depths from Surface – the input
log values are relative to Kelly Bushing. The difference between the Kelly
Bushing and the Surface is 7.89 m.
Therefore, to find the data point, add 7.89 m to the depth being read from the
log display.
The erroneous point is actually at 694.2 m measured from the KB.

72
Another method to find values in the logs is to use the
Curve View display.
Click on the Curve View and zoom in until the bad data
point is clearly visible. Click on the Highlight icon.

73
Using the cursor, highlight the area around the spike (start from the
top and drag down). The zone will be highlighted in yellow.

Now, go into the Density

table view…

74
The area that was highlighted in the Curve View is now highlighted in the Log
table view. (If this doesn’t work, start a new Well Explorer window and try
again).

75
Select the row with the bad data point by clicking somewhere in the row.

Use Log Data Options > Delete Selected rows from table to remove it.
Click Update and Yes to apply the edit.

Now go back to the Curve View. The data point has now been removed.
76
 In the Log Display Window, the edited data point will still be
visible in gray.

If the edit is not visible, or if you want

to turn it off, you can change this in
the View > Display Options menu and
toggle on/off Previous Log Curves in
the Layout tab.

77
Click on the History tab of the Well Explorer to view the history
of the log.

You can add your own

comments to the History file if
you want to have more
details. Click File > Save to
save your comments.

78
-- End of Exercise 2 --
 Exercise 3: Well Log
Data Management
We will now load a new Geoview database – one that contains multiple
wells – and look at more data management tools.

On Geoview, click Database > Open

and select the blackfoot.wdb well
database.
Click OK. It will take a few seconds
to load.

79
This database has 23 wells already loaded; these are a mixture of vertical and
deviated wells.
Geoview has the ability to filter the well list. This allows the user to list all the
wells within the database that contain a particular log type.

80
For example, to find all the wells that start with 1 and contain a Gamma Ray,
enter 1* in the Well name field, select Gamma Ray as the Log type and “apply
to wells and logs”. Click Apply Filter

81
The result will be a list of the 8 wells that satisfy the Well name and Log type
conditions.

82
Click on the Summary Report and then Generate Report. This will produce a
report of all the statistics for the Gamma Ray logs in wells that start with 1*.

After, click Clear to

remove the well
and log filter. The
full well list will
appear.

83
Now, on the Log Type drop down menu, select Check
Shot , “apply to wells only”and click Apply Filter.

Once the filter has been applied, only the wells that contain a Check Shot log
are listed in the Table View. In this case, there are 3 wells in the database with a
Check Shot.

Click on Curve View to graphically view the logs in the wells.

84
Click on the [+] in front of each well to
expand and display all of the logs within the
three wells.

Using the Ctrl key, select one of the DT

logs in each of the three wells…

85
 1
2

In the Curve View Menu, (1) select the view Profile Mode and (2) click on the
Plot button…

86
 Now, in the Well Data List, (1) using the Ctrl key, select
1
the three Depth-Time curves for each of the three DT
logs…

3
In the Curve View, (2) change the View Mode to Overlap
Mode and (3) click the Plot icon.
Two of the Depth-Time
curves look similar but the
generic31 log in well 03-21
does not look correct. It is
actually a check shot log
that has been incorrectly
mapped as a depth-time
table.
87
 2 3

Let us remove the last

track.
(1) Look at the bottom of
the display. The track
with the Depth-Time
curves is listed as Track
4.
(2) Select Track 4 from
the selection list and
(3) click on the single red
x.

1
88
 1 2

We can also view the logs

relative to a selected Log Top.

(1) Select Flatten On Top as the

Datum and
(2) Select the BASAL BELLY
RIVER from the list of tops.

89
 Well 03-21 is missing several log markers. We can
graphically add them using the Curve View display.

First, click on the “Pick Tops” icon…

Then select Well 03-21 and enter the Top

name as OLDMAN FM. (This top name is
the same as in the other two wells).

90
This is just an exercise, but choose
the depth location where you
think the OLDMAN FM top is
1
present in the 03-21 well.
(1) Click on the log track with the
cursor,
(2) Click Apply to create the top
(3) Click Close to close the menu.

91
The new top will now be displayed in all three wells. If it is not
shown, click on the View > Display Parameters and Show All
Tops.
Now click on the Base Map tab…

92
Use the Shift key to select all three wells in the Well Data List.
The selected wells are now highlighted in red in the Base Map.

Remove the log filtering by clicking on the Clear

button. Now all 23 wells are displayed in the Well
Data List. 93
The default map is not to scale. Click Map Scale = 1: 50000 to
display to scale.

Well locations are marked with the

appropriate symbol for the well
status.

For deviated wells, the top hole

locations are marked X.
94
We can also load culture information from
DXF drawing files.
Click Import Data > Load Culture Data
Add All >> the DXF files in the DXF
directory and Start Read.
Then click OK.

95
The DXF files are now
displayed as a map overlay.

Now, click on the cube icon

to enter the 3D Well Path
display.

96
These options allow the
user to display the well path
cube from above or from
either of the cube’s sides.
The default is to display in
perspective view.

This mini-cube allows you

to change the orientation of
the display.
Click & drag within this
window. The cube will
rotate accordingly.

97
 Click View > Navigation Tools
and switch the Orientation
Controls option on.
The Depth Scalar allows the user to set the vertical
display scale.
Now, as you rotate the cube, the Rotation Angles
will track the changes made.

Using these controls and the View Location option,

you can define the display precisely. This allows for
consistency between displays.

The Annotations allow you to chose whether or not

to display the well names, tops etc.

Further alterations to these annotations can be made

under View > Well Annotations.
98
The Track Cursor Mode gives the user a print-out of the well positions as
the volume is scrolled through.
Using the Constant Slice option, click and drag the mouse within the
perspective base map view. Your position in depth will be tracked and the
well intersection (X,Y) values posted.

Now select the 3D Tracker option. Purple crosshairs will appear; these
indicate the cursor position. Moving the mouse within the window moves
the crosshairs; the (X,Y) position is posted by the ball.

Experiment with the 3D Well Path window for yourself.

When you have finished, close the window and return the Well Explorer
window back to Table View.
99
Exercise 4: Log Type Mapping
All logs within Geoview should be assigned a type. More than 60 types
have been set up within Geoview, although it is possible to add more.
These include:
P-wave
S-wave
SP
Temperature
Saturation
Gamma Ray
Elastic impedance
Caliper
Density
Porosity
Resistivity
…

100
From the Table View, access the log
listing for Well 12-16.

The log named DTS has no log type

associated with it.

One option is to select the log type

from the selection menu. However,
this requires that we do the same for
every well in the database.

We will use the mapping options to

apply this change to all the wells.

101
On the Well Explorer menu, select Options > Log
Type Override….

This menu will appear. Fill it out as

shown here and click Apply.

Click Yes to the confirmation request

and Yes to reload the data.

102
The DTS log is now defined as type S-wave.

This process was applied to all the

wells in the database that had a log
named DTS. The messages in the
menu show which wells were
affected.

Click Close on the mapping menu

to dismiss this window and end
this exercise.

-- End of Geoview Exercises --

103
Introduction to eLog
eLog is the well log editing and interpretation software. eLog is run either
as a stand-alone program or it is embedded within programs such as
AVO, Strata, Pro4D and ProMC.

Functionality available within eLog includes:

• Well-to-seismic correlations.

• Fluid Replacement Modelling (FRM) - this is used to model saturated log

responses for AVO analysis.

• Log cross-plotting.

• Log generation from mathematical operations or applying standard

geophysical relationships.

• Wavelet generation and extraction.

104
HRS Projects and Well Databases
When a user launches the eLog (or any other HRS ) software, the system
forces the user to open a project: either an existing project or to start a new
project.
When a project is created for the first time, the Geoview well log database is
copied into the project. This means that there are now two well log
databases: the Geoview (or external) database and the project (or internal)
database.
The name of the internal well database that the project is using is displayed
in the lower right corner of the eLog main window.

105
HRS Projects and Well Databases
The concept of the internal database allows the user to make as many
changes and edits to the wells within the project without making a
permanent change to the external database.
In order to export the
modified log data from the
eLog project to the Geoview
well database, the user
must explicitly specify
which wells and which logs
need to be exported from
the project back into the
Geoview database.

Doing a Database Export will synchronize the two databases and reduce the
chance of overwriting or losing information. When you exit eLog, the
software will prompt you to export your changes to Geoview. If you choose
not to export the modified logs from eLog, the logs will still always be
available in the project.
106
HRS Projects and Well Databases
If you are adding more data to the Geoview database while you still are
working on an active project, then:
1) New wells will be available in your project right away.
2) New logs and new tops that were added to any well in Geoview will
become available in your project.
3) If a well was never modified within the project, then it will be the same as
the well in Geoview and no additional import is required.
4) If the log has been modified in the project and then you modified the data
in Geoview, you will have to import the changes to the project using
“Database > Import Well changes to project” option.

For example, if you filtered a log in the well within an eLog project and then,
in Geoview, you modified the log (changed the units, deleted a point, etc…),
you will have to import the Geoview changes into the project.
107
 Log Editing
Some log editing
facilities are available
on the Edit Logs
sidebar button.
Here are the options:

108
Log Blocking

Blocking is used to block and simplify log responses.

The blocking tool allows multiple logs to be blocked simultaneously.
One log is chosen to guide the blocking process.
Blocking options are
Automatic uniform
Automatic non-uniform
Single
The first two of these require the user to specify the average block size.
The value assigned to a block is the average of the log samples covered by the
block.

109
Blocking Options

1. Automatic uniform:
Automatically blocks the log with blocks of the given block size.

2. Automatic non-uniform:
The defined average block size is used to determine the number of
blocks within the depth range to be blocked by dividing the length of
the range with the average block length.
Based on the guide log response, the blocks are defined to describe
the largest changes in that log response using a maximum-likelihood
algorithm.

In both cases, the smaller the defined average block size, the better
the blocked description of the logs.

3. Single:
A single block is inserted covering the defined depth range.

110
Boundary Tool
The interface between blocks is called a boundary. The boundary
tool is used to modify the blocked log responses.

Boundary options are

Add boundary
Delete boundary
Move boundary
Change thickness

There is no limitation to the number of boundary operations that you

can perform and you can add multiple boundaries.

111
Boundary Options
1. Add boundary:
Simply select the location for the new boundary by clicking on the log
display.

2. Move boundary:
Select the boundary to be moved from the log display and type in the new
depth (or TWT) of the boundary.

3. Delete boundary:
Click on the log display near to the boundary to be deleted.

4. Change thickness:
Highlight the log interval to be modified and type in the new thickness (in
terms of depth or time thickness).

112
Draw Tool
Used for manual editing of logs
Inserts straight lines between user defined points (left mouse button)
Simply click on the line ends and apply (right mouse button to end)

113
Cross-plot
Cross-plot two logs with a third log as colour attribute
Regression functionality for determining relationships between logs.
Identify zones on the crossplot and their location in the logs.

114
 Cross-plot
Zones are easily edited.

Edit Zone Handles Bulk Shift Zones

115
Cross-plot
Overlapping zones
can also be
ordered. The zone
on top takes
precedence.

116
Exercise 5: Cross-plotting and
Blocking
In this exercise, we will use the crossplot and blocking facilities within eLog.
From your current Geoview database, click on the eLog button…

and Start New Project. Call the project ELOG_PROJECT.

117
The eLog main window will appear and you will be
prompted to select a well. Choose the 08-08 Well and
click Open.
The well log data will appear in the eLog window.
Click on the View > Display Options to set the viewing
parameters.

118
On the Layout page, click on the Clear All Tracks button.

Now select the Gamma Ray (GR) and

SFL log to display in the first two tracks.
Click OK.

119
Zoom in and scroll to the bottom of the logs to see both
the SFL and GR logs side-by side.

Click on the Edit Logs

button on the side menu
bar to display the log
blocking menu on the
bottom of the log display
window.

120
Select Automatic uniform for the blocking method and 10 m blocks.

Click Parameters to reveal this

menu.
Enter 1375 and 1605 as the Vert
Depth. This is the range that the
logs will be blocked.
Click Apply and then click OK on
the next window.

121
After the uniform blocking process,
the newly blocked logs are shown
in red, the original logs in black.
Examining the locations of the log
boundaries shows that they are,
indeed, at 10 m intervals.
Click Undo to revert the logs and
try another blocking method.

122
The range of data to be blocked can be set interactively
by clicking on the eLOG window to define the start of the
window then dragging the cursor down until the end of
the intended blocking run is reached.
Set the blocking method
to Automatic non-
uniform, block size to 10
m and, using the cursor
and clicking on the SFL
log, highlight the zone as
shown.

Make sure the blocking

guide log is SFL.

Click Apply and then OK.

123
Again, after the non-uniform
blocking process, the newly
blocked logs are shown in red, the
original logs in black.
Examining the locations of the log
boundaries shows that the blocks
are not uniformly blocked and they
follow the appearance of the SFL
log rather than the Gamma Ray log.

On the Edit selection menu, select

Add Boundary.

124
The block boundary positions have been determined by
the SFL log. Therefore, the Gamma Ray log is over-
simplified.
We can use the Add Boundary tool to correct this and
add block boundaries where we wish.

At an obvious
unblocked Gamma
Ray break, add a
boundary by clicking
in the log.
Click Apply and OK
and notice how the
blocking is
recalculated with the
new boundary
location.

125
You can add as many boundaries as you wish: the log block amplitudes will
adjust in value to accommodate your changes.

Try adding, moving and deleting boundaries.

Drawing your log edits is another useful log editing tool. Select Draw and
set the parameters as shown with 1.0 m sampling.

126
On the GR log, draw in your curve and click Apply to see the
result.
(note that the log must be in a linear
scale for drawing to work correctly, e.g.,
the SFL log is displayed in log scale by
default)

After your testing, click on the Reset button to

reset all of the log edits and confirm the reset by
clicking Yes.

127
Go back to the Block option, set to Automatic non-
uniform and block size = 1.0 m.

Click on the Input Logs button and remove the SFL log from the list so that
just the GR log is being blocked.

128
Using the mouse, select the log range as shown, and
click Apply.

129
Log Blocking is commonly used to simplify logs and
reduce the amount of data in a well log. With modern
computers, there is no longer such a need to block logs
but some processes, such as Elastic Wave Synthetics,
can be be computationally intensive and may benefit from
using blocked logs.
Blocking the Gamma Ray log may be a helpful process to repair the smearing
effect of the moving log tool and improve the definition of sedimentary bed
layers
Click Ok to finish editing the logs, give the blocked Gamma Ray log a new name,
such as GR_Block, and click OK to save the log.

130
In the Log Display Window, click
View > Display Options to change
the display parameters.
On the Layout menu page, select
to display only the blocked
Gamma Ray log and deselect the
Original Log Curves option.
On the Curves page, set the
parameters as shown below with
Fill Option = Fill By Curve, Fill
Colour = Use Color Key and Fill
By Curve = the blocked Gamma
Ray log.

131
In this display, low
Gamma Ray
values are more
easily identified
with the green fill
color. Low gamma
ray values are a
good indicator of
sands.
We can improve
the interpretation
of this well by
examining the
other logs.

132
Fortunately, the petrophysicist has created a log display
template file that we can import into this project. The
name of the file is called Blackft_Petrx_baseView.vwtmp.
We can import this file so that all the log displays will be
consistent with the other petrophysical work.
Click on the View > Display
Options menu and then go to
the Template page. Click the
Load… button.

Find the file called

Blackft_Petrx_baseView.vwtmp in
the HRS_DATA\geoview_data
directory and load it into the
project. Click OK on the
Parameter Menu.

133
The Log Display should now appear like the following.
By overlaying logs and using color fill, the interpretation
of the well is greatly enhanced.

134
 The separation of the
Medium and Deep When the Neutron
Induction logs indicate a Porosity log and the
difference in fluids with Density log are plotted in
distance from the well this manner, large
Low Gamma Ray values
bore caused by drilling separations indicate
are indicators of clean
mud invasion. A higher shales, close separations
sands. Deflections in the
resistivity in the deep indicate sands and
SP curve are indicative of
induction log indicates reverse separations
bed permeability.
hydrocarbons. indicate gas sands.

135
Further analysis can be performed by cross-plotting the
well logs. On the side menu bar, click on the Crossplot >
Vp/Vs vs AI …

Include other well logs such

as the Gamma Ray and the
Porosity log by adding them
to the selection list.

136
 Only include the 08-08 well.

Provide more details to the

Plot Name such as:
wlxplot_Zp_VpVs

137
Click Next >> (twice).
On the Set Domain Ranges page, select to crossplot the data from the
TOP GLAUC VALLEY to the BASE GLAUC VALLEY tops.
Click OK to display the Crossplot.

138
The crossplot window will appear:

Note that the

Color Key is
currently
displaying the
vertical depths of
the cross-plotted
P-Impedance and
Vp/Vs pairs.

139
We can display the color to another attribute such as Gamma Ray.
Select the View > Change Color Attribute.

Choose Gamma Ray, set the ranges

and click OK

140
Your crossplot should now look like this with the
Gamma Ray values plotted in color.

141
We can highlight areas on the crossplot and identify them on the well
logs. Click the Zones button and select Add…

Change the zone Drawing

Mode to Polygon.
Double clicking the Color
Selection will allow you to
change its color. Change
the color to red.

142
“Zone Filters” are collections of crossplot zones. You can have multiple
Zone Filters in a project and a separate name can be used to distinguish the
Filters. Similarly, the Zones can be distinguished with proper names.

Change the current filter name to

“08-08: Zp vs VpVs”.

Change the name of the Current

Zone to “gas”

143
 Click the outline over the set of data
points as shown. The points will be
highlighted red. A right mouse click will
close the polygon.

Click Apply on the

Add Zone Menu.

The points will now be highlighted

within the zone.

144
Click the Cross Section option to see these zones located on the
computed Impedance and Vp/Vs Ratio logs. You may need to zoom in.

145
The highlighting of points is two-way: you can also highlight a section of
log on the cross section and see where it is on the cross-plot.

First, select the drawing tool on the cross-section.

Then, draw a rectangle around the log pairs that you want to highlight on the
crossplot.
The selected points will flash on the crossplot.
The flashing is disabled by clicking on the other icon.

146
Let’s add some more interpretation to our crossplot. On the Add Zones
menu, click Add new zone at the Current Zone Selection list and name the
new zone “wet”. Change the color to yellow.

147
Add the wet sand zone
something like this …>

148
Add another zone called shale, and set the color to grey. Select
the zone around all the high gamma ray values and click Apply.
Click Ok to save the Crossplot filter.

149
We can make a new crossplot with the
other data that we included. Click on
New Plot > P-Impedance vs VpVs Ratio

Change the Item # for Y-axis to 6

which corresponds to the 6th item
on the list, Porosity. This will
create a cross-plot of the the
Porosity log versus P-Impedance.
Change the title of the description
and click Ok.

150
 The crossplot now displays Porosity versus P-Impedance.

We can filter out the shale

data based on the Gamma
Ray values. Click Filter >
Filter Points to remove
the high gamma ray
values associated with
shales.

151
In this example, filter out the gamma ray values that are
greater than 40.
Click OK.

152
We can now use the crossplot
data to determine a relationship
between the acoustic
impedance and porosity for the
sands.

On the crossplot window,

chose the Regression > Least
Squares option.

Keep the defaults

for the Regression
Menu and click
Ok.

153
 A regression line appears on
the crossplot.

The equation and the

normalized standard error for
the line is given at the bottom
of the crossplot window.

Finally close the crossplot

window (File > Exit) or use the
exit door icon.

Click Yes to save the crossplot in the

project.

154
 In the Log Display window, click
on the Eye icon to display the
Display Parameters Menu for
eLog. Go to the Layout tab.

On the bottom right of the menu, choose the Zone

Filter that we just created by clicking on the […]
selection button. Choose the Computed Impedance
as the X log and Computed Vp/Vs as the Y log.

155
On the Layout matrix, select to display the Computed Cross Plot Zone in it’s
own track.

156
On the Curve menu, set the Computed Cross Plot Zone display options as
shown.

Start Amp = 0, End Amp = 3, Scale = Linear, Color = Grey, Fill Option = Fill By
Curve, Fill Color = Use Color Bar, Area = From Left Edge, Constant = -1, Fill By
Curve = Computed Cross Plot Zone.
Click Ok to display the projected crossplot log.

157
The projection of the well log crossplot interpretation
matches our previous well log interpretation. This
indicates that a successful pre-stack seismic inversion
could allow us to identify gas sands, wet sands and
shales.

158
We can now move our interpretation to another
well. Rather than opening the previous log
display template, we can save the current log
display as the default project template.
Click on the View > Display Options menu item.
On the bottom of any menu, select to Save
settings as project template and then select Yes
on the following warning window.

Click Ok to close the Parameter menu window.

159
 Now click Open Well… from the
sidebar menu.

Select Well 05-16 and Open in new window and

Use project template when open.

Click Open.

160
A new eLog window will open with 05-16 well. This
well does not have a DTS log and so the Computed
VpVs Ratio log is not available nor is the Computed
Cross-plot.

Also, notice
how spiky the
DT and the
Computed
Impedance log
are. Filtering
the DT log will
help to remove
the noise
spikes and
create a better
Impedance
log.

161
Now, click Project > Save.
The software will determine that
there are differences now between
the external Geoview database and
the eLog project database. Click
Yes to see what these changes are.

The software found the new blocked

Gamma Ray log in the project – which
is not found in the Geoview database.
Click Deselect All to choose not to
import these logs at this time. Now
click OK. 162
-- End of Exercise 5 --
Math Tool
The Math Tool is used for applying common mathematical
transforms to logs.
Operations that can be applied are:
Add
Clip
Divide
Exponential Relationship (y = axb)
Frequency Filter
Linear Relationship (y = ax + b)
Log Maths
Median filter
Merge
Multiply
Normalize Log
Running Average
Shift
Splice
Subtract
163
Math Tool
The Math tool interface
consists of a list of
selectable Math options and
a description of the
operation.
The next slides will discuss
the Frequency Filter,
Running Average, Clip and
Median Filter for filtering
noisy logs. As well, we will
discuss some other
important functions
available in the eLog Math
menu.

164
Frequency Filter
Each well log usually has a P-wave log. P-wave logs always have an
associated depth-time curve. Therefore, logs can be manipulated by the
software in either the depth domain or in the time domain. (Logs without a
P-wave log will be converted to time based on the relation that 1 depth unit
(m or ft) = 1 ms).
The user selects the bandpass frequencies for filtering.
Removing the 0-0 low frequencies will result in logs
losing their bulk shift component and so logs that
were all positive (i.e., Impedance logs) will now have
negative values.
This method is not used too often for well log filtering as it tends to remove
too much of the high-frequency signal.
Bandpass filtering logs is typically calculated for inversion projects.
Inversion results are typically band-limited and, to compare the seismic
inversion with actual well logs, requires that the impedance logs also have
the same bandwidth for a better and direct comparison.

165
Frequency Filter

Original Sonic Log 0-0-512-1024 0-0-80-100 4-8-80-100 Hz

166
Running Average Filter

The Running Average filter is sometimes used for removing noise spikes
from well logs.
The process is: An averaging window length is designed for the log. The
values in the window are then added together. The sum is divided by the
number of samples in the window to yield the average value. This
computed average value then replaces the actual log value at the window
center location. The window moves down a sample and the process is
repeated.
The result of the Running Average filter is similar to a low-pass frequency
filter. The longer the averaging window, the smoother the result is.
The big weakness of this method is that it is sensitive to spikes in the
logs and thus, it is not very robust.
As well, the original log values are not retained after the averaging
process.

167
Running Average Filter
Example
To demonstrate the Running Average, the filter will be applied to the
following array with a window size of 3, repeating edge values in blue:

x = [2 80 6 3]

y[1] = Average[2 2 80] = 84 / 3 = 28

y[2] = Average[2 80 6] = 88 / 3 = 29
y[3] = Average[80 6 3] = 89 / 3 = 30
y[4] = Average[ 6 3 3] = 12 / 3 = 4

so
y = [28 29 30 4]
where y is the running average filtered output of x.

168
Running Average Filter

Original Sonic Log 3 Pt Avg. 7 Pt. Avg. 11 Pt. Avg.

169
Clip
Clip is another process commonly used for removing noise spike.
The user identifies a maximum and minimum value in the log amplitudes.
The algorithm then searches for these spikes and either replaces them
with the user-specified clip value or replaces them with the preceding
good value.
The Well Explorer Summary Report can help with identifying the minimum
and maximum range of values for a log – but the minimum and maximum
clip values are still subjective.
The weakness with this method is that noise spikes may still exist that are
within the min/max limits.

170
Clip
Original Sonic Clip & Replace by Clip & Replace by
Log Preceding Value Min/Max Clip Value

171
Median Filter
The Median Filter is a non-linear filtering technique, well-suited to
removing noise from signal.
The process is: The values in the window are sorted into numerical
order; the median value (i.e., the sample in the center of the window) is
determined; the median value then replaces the original log value as the
window center location.
The length of the window determines how long a noise burst has to be
after which it is not considered noise and it will be retained.
The general description of the median filter length is m = (2n + 1) where n
is the length of noise. For example, in a 3 point median filter, noise
samples of length n=1 will be removed. In a 15-point operator, noise
trains of length 7 or less will be removed.
When working with well logs, we generally want to remove noise spikes
that are of length 1 or 2 samples. Median filter lengths of 3 and 5 are
common for log filtering.

172
Median Filter
Example
To demonstrate the median filter will be applied to the following array with a
window size of 3, repeating edge values in blue:

x = [2 80 6 3]
unsorted sorted
y[1] = Median[2 2 80] = Median[2 2 80] = 2
y[2] = Median[2 80 6] = Median[2 6 80] = 6
y[3] = Median[80 6 3] = Median[3 6 80] = 6
y[4] = Median[ 6 3 3] = Median[ 3 3 6] = 3

so
y = [2 6 6 3]
where y is the median filtered output of x. The 1-point noise spike is
effectively removed by the 3 point filter.
For comparison, the running average filter results were: y = [28 29 30 4]
173
Median Filter

Original Sonic Log 3 Pt Median 7 Pt. Median 11 Pt. Median

174
Filtering P-wave Logs
In most cases, you do not have to think much about the consequences of
filtering logs.
The exception is the P-wave log. This log also has a depth-time table
attached to it. Whenever you do any process to the P-wave log, you will also
have to make a decision about what you want to do with the associated
depth-time table.
In most cases, you have two choices:
recreate the depth-time table or use the
depth-time table of the original log.

If you have already applied check shot corrections or correlated to the

seismic, you will want to use the depth-time table of the input P-wave log –
otherwise you will have to reapply the check shot correction or re-do your
correlations to the seismic.

175
Log Maths
Log Maths allows you
to programmatically
create your own
mathematical function.
The scripting language
is based on the C
programming syntax.
Similarly, a Trace
Maths and a Map Maths
tool is available for
seismic volumes and
maps.
Examples of Trace
Maths and Log Maths
scripts can be
downloaded from the
Hampson-Russell web
site. 176
Splice
The Splice option has two different
uses: to splice a portion of a log into
another log, or to copy a log.

177
Exercise 6: Log Math
In this exercise, we will apply common filtering techniques used for
removing spikes from logs.

In the 05-16 well, select Math from the eLog window, and chose Running
Average from the list of operations.

178
Select to use 05-16 for the input data and as the output well.
From the list of available logs for this well, use Add>> to select the P-wave
log called DT. Click Next.

Rename the output log to

P-wave_Avg_5pt and set the Depth-
time table option to:
Use depth-time table of DT.
Click Next >>

179
Define the operator length as 5
and click Next >>:

Specify the entire

depth range to filter
and click OK.

180
The new filtered log is
added to display
window in the last
track. Let’s set-up the
Parameter Menu to just
view the P-wave logs.
Set up the Layout menu
as shown. Use the
Clear All Tracks button
to clear the tracks then
select the DT and
filtered P-wave. Make
sure the Display Only
Active Logs is
deselected. Also,
select the Original Log
Curves option.

181
On the Curves tab menu, set the range for one of the
logs from 1000 to 7000 m/s. Then click the Apply
Selected Log ranges to all the wells to update the log
range for the other log.

Click Ok to save the changes.

182
Now let’s see what the
median filter looks like in
comparison.
Click Math… again and
select the Median Filter
option.

183
Select the 05-16 well again and the original DT log.

Set the output name to something

useful like P-wave_Med_5pt.
Again, Use depth-time table of DT.
Click Next >> , enter 5 points and
OK to process the entire log
range.

184
Let’s now try the Clip filtering. Select Math again and select the Clip option.

Again select the 05-16 well

for the input and output
logs. Select the original DT
P-wave log.
For the Output Log Type,
select P-wave and m/s.

185
Change the output log name
to P-wave_clip7k and,
again, Use depth-time table
of DT.

186
Set the Maximum value after
which the value is clipped at
7000 m/s.
Click OK and view the logs.

187
Zoom in on various areas in the logs and compare the filtering techniques.

-- End of exercise -- 188

Transforms Tool
The Transforms Tool is used for generating logs from other
logs using common geophysical relationships.

Available transformations are:

AVO supplemental curves
Poisson’s Ratio
Vp/Vs ratio
Vs/Vp ratio
Castagna’s Equation
Vs = a * Vp + b
Gardner’s Equation (and reversed Gardner’s Equation)
Rho = a * Vpb
P-impedance & S-Impedance
Zp = Vp * rho & Zs = Vs * rho
Krief’s Equation
Vs2 = a * Vp2 + b 189
Transforms Tool

Elastic Impedance
Using Connolly’s equation
Elastic density
Using Connolly’s equation
Poisson’s ratio from Gamma Ray
Uses shale and baseline GR cut-offs to set constant PRs
Porosity to density and density to porosity
Using log porosities and matrix & fluid densities
Faust’s Equation
Vp = a * (depth*resistivity)1/6
Water saturation
Using formation resistivity factor & the resistivity of the
formation water and the formation (from log)

190
Transforms Tool
The transforms menu has the same format as the Math menu. It allows the
same transform to be applied to multiple logs.
A description of the function is also provided.

191
Castagna’s Equation

Castagna’s equation is an empirical relationship between Vp and Vs.

ARCO’s original mudrock derivation (Castagna et al, Geophysics, 1985)
is:
Vp = 1.16 Vs + 1360 m/sec
The two coefficients can be changed to match your reservoir trend.
This is one common method of estimating shear wave logs.
192
Gardner’s Equation

Gardner’s equation is an empirical

relationship between Vp and Density.
The Gardner equation (Gardner et al,
Geophysics, 1974) is:

ρ = 0.23VP 0.25

for V in ft/s and density in g/cc.

193
P- and S-Impedance
The equations for the acoustic impedance (AI, Zp) and shear impedance (SI,
Zs) are well known:

AI = ρVP
SI = ρVS
The transform simply multiplies the (P or S) velocity log with the density
log. If the density log is missing, the system will then use a Gardner-type
relation to estimate the density log.
For wells with missing density logs, the transforms become:

AI = 0.23 ∗ VP
1.25

SI = 0.23 ∗ VS
1.25

194
Elastic Impedance

Connolly(1998) proposed an impedance concept for non-zero offsets

called the Elastic Impedance (EI) :

EI (θ ) = V P
( 1+ sin 2 θ )
V S
( −8 K sin 2 θ )
ρ ( 1− 4 K sin 2 θ )

VS2
where K= 2
VP

• Note that if θ=0o, far offset EI also reduces to Acoustic Impedance (AI).

AI = ρVP
195
Elastic Density

The Elastic Density log was also introduced in the Connolly (1998) paper. The
Elastic Density log is a log of type Density that is found by dividing the
Elastic Impedance (EI) log by the P-wave log.

The benefit of this log is that the P-wave remains unchanged and, therefore the
depth-time table remains the same. The elastic impedance information is
now only contained within the density log.

This means that for Elastic Impedance projects, you can correlate the log as
normal with the correct depth-time curve, but the impedance log that is
calculated by multiplying the original P-wave log with the elastic density log
corresponds to the angle stack.

196
Faust’s Equation

In many older fields, the only logs that are available are Resistivity logs. It
has been observed that, in wet clastic rocks, the resistivity log and the P-
wave sonic tend to track each other.
A number of empirical relationships have therefore been derived to allow
the geophysicist to derive a P-wave velocity from a resistivity log. The
oldest relationship is from Faust (Geophysics, V18, p271-288):

VP = a ( Rd ) c

where
a,c = constants
R = resistivity
d = depth

197
Faust’s Equation
A more recent formulation does not involve using depth in the equation.
The most general expression for this equation is:

Δt = a + bRc

where
Δt = transit-time
a, b, c = constants.

This transform will have to be applied as a Math operation using

Exponential Relationship.

198
The FRM tool

FRM is an acronym for Fluid Replacement Modelling.

• FRM uses the Biot-Gassmann rock physics equations to model

the impact of the presence of fluids on log response.
• FRM can also be used to correct Castagna S-wave log estimates
for the presence of gas.
• FRM can also be used to correct logs that have been affected by
drilling mud invasion.
• FRM also contains the Greenberg-Castagna method of shear
wave estimation.
• Fluid replacement requires input P-wave, density and S-wave,
water saturation logs and information about the fluids.

The FRM tool is an important but complicated tool and is dealt

with in more detail in the AVO course.

199
Exercise 7: Log Transforms
For this exercise, we will use two of the log transforms available
for predicting P-waves.

Select Transforms from the eLog window and then

Faust’s Equation from the list. We will use this to create a
sonic log from the resistivity curve.

200
Select to use 05-16 for the input and as the output well. For the input
resistivity log type, select the Induction Medium log type.

201
Name the new output sonic log to P-wave_Faust_ILM, and set the units to
m/s. Click Next >>, use the default coefficients and click OK.

202
Remove all the old P-wave tracks
and put both the original DT curve
and the new Faust P-wave curve in
the same track. Also, deselect
the Original Log Curves option
and click Ok.

203
There is a big discrepancy
between the actual P-wave log
and the Faust-derived log. The
Faust derived velocity log is
about 600 m/s faster than the
recorded sonic log.

Click on the Math… button to

correct this.

204
Select the Linear
Relationship option.
Select the 05-16 well
and the new Faust-
derived P-wave log.
Set the Output Log
Type to P-wave, m/s.

205
Give the Output Log a
useful name like P-
wave_Faust_shift.
Set the Depth-time table to
Use depth-time table of the
original P-wave log.

206
On the last page, set up the coefficients as above. In this case, we
just want to subtract 600 m/s from the Faust P-wave log. Click OK to
process the entire log range.

207
Again, set the Layout to overlay
all three logs in the same track
and click OK.

208
The shifted log looks to fit a lot
better.

Now let’s use the Reverse

Gardner’s Log and create a P-
wave log from the Density log.

Click on Transform again and

select Reverse Gardner’s
Equation…

209
Select the 05-16 well and
give the output P-wave log
a useful name like P-
wave_reverseGardner.
Accept the default
coefficients and create the
log over the entire range.

210
Under View > Display Options
(eyeball icon) select to display
the Faust-derived P-wave, the
shifted Faust, the reverse
Gardner P-wave and the original
P-wave logs all in the same
track.

211
The quality of the reverse Gardner
derived P-wave log, in this case,
clearly highlights the noise in the
density log. As well, the low density
coal layers in the well cause very low
and unrealistic velocities.

Probably, some combination of the

Resistivity and the Density log would
give the best estimate of the P-wave
log. This can be done in the
EMERGE software program.

-- End of exercise --
212
The Help Menu

Help > About Geoview

This will display the program splash
screen with the
• software version number,
• compilation date, and
• all relevant support contact
information.

213
The Help Menu

Help > View Runtime Messages

This will display the software
runtime debugging messages.
This information can be useful
in debugging difficult issues.
The information is written to a
file on the disk.

214
The Help Menu

Help > System Tests

This will allow the user to perform
basic system tests to ensure that
their system is operating
correctly.

215
The Help Menu

Help > Internal Data Viewer (dbEditor)

Hampson-Russell information files are
stored in binary format. This viewer
will allow you to view the information
in ASCII format and edit it, if
necessary. However, only do this if a
HRS technical support person tells
you to do this – you can badly corrupt
your well database and projects if you
are not careful.
216
 The Help Menu
Documentation

New Features document

Guides are tutorials the new features in
that describe the major release updates
basic workflow for such as CE8R1.
each program.

217
The Help Menu
Documentation: Hampson-Russell Assistant

The Hampson-Russell
Assistant is a
searchable
documentation utility
that describes the
program operation in
detail.

218
More Help
More documentation can
be found on the Hampson-
Russell website under
Support > Knowledgebase.
The Knowledgebase is a
categorized repository of
PDF documents of various
topics and is available to
everyone.

219
Summary

Geoview is the Hampson-Russell program launcher and also holds the well
database.
The Well Explorer is used to manage the well database. The Well Explorer is
the program that is used to load the wells into the database, view the logs,
the base map and the 3D well path viewer and the well log statistic reports.
Depth-time curves and P-wave logs are always tied together. The default
depth-time curve is computed internally by the software and can be modified
by applying check shot corrections or by correlating to the seismic.
eLog is the program that allows log filtering, log cross-plotting and analysis,
log maths and transforms and log correlation.
Hampson-Russell Software projects use two databases: the external
Geoview database and the internal project database. Logs generated or
edited in eLog are only applied to the internal database and can be exported
back to the Geoview well database later.

220