Release Notes

Petrel 2005 Release Notes
Petrel 2005 is very much a user driven release. Our focus has been on improving existing
functionality guided by input from the user community. You will find plenty of great
enhancements to existing modules and one new module for evaluating economics.
In terms of workflow improvements the greatest change will be in the evaluation of
Uncertainty. The new uncertainty features will open up analysis to a much larger population
and will be a great benefit to both the novice and the expert user. The Uncertainty workflow
spans static and dynamic processes and includes sensitivity analysis as well as standard
Monte-Carlo techniques.
Reservoir Engineers will be happy to see the improvements to the Reservoir Engineering core
functionality, including the submission of simulation runs to remote machines and many
visualization enhancements.
Many of the other improvements focus on the core G & G workflow with upgrades to the
plotting, well correlation and structural modeling in particular. Users interested in workflows
with Neural Network analysis will be pleased to see the new Principal Component Analysis
feature.
Please read on more a more extensive review on the release highlights. We hope you enjoy
the new Petrel release.
Trond Skjerven, Lead Product Champion – Petrel, January 2006

Petrel 2005 Release Notes ..........................................1
Uncertainty............................................................................................................ 1
Uncertainty Process ...................................................................................................... 1
Integrated Structural Uncertainty ................................................................................... 1
Capture and Storage of Variables ................................................................................. 2
Global Seed .................................................................................................................. 3
Latin Hypercube Smart Sampling .................................................................................. 4
Multiple Histogram Plot for Sensitivity Analysis ............................................................. 5
Core System & General........................................................................................ 8
New Process Manager Functionality ............................................................................. 8
Visualization Upgrades.................................................................................................. 9
Principal Component Analysis (PCA) .......................................................................... 10
Utilities - Add Point Digitizing....................................................................................... 10
Ergonomics - Clean up Insert and Windows Menus .................................................... 10
32bit Compatibility Mode on 64bit Windows ................................................................ 11
Run Petrel from a command line ................................................................................. 12
OpenSpirit upgrades ................................................................................................... 13
Prosource Results Manager Connection ..................................................................... 17
Checkshot sharing....................................................................................................... 17
Improved calculation of well path geometry in time domain. ........................................ 17
Small enhancements................................................................................................... 17
Well Correlation .................................................................................................. 19
Well Section = Well Fence........................................................................................... 19
Well Filter .................................................................................................................... 20
Tracks in Well Section................................................................................................. 21
Fluids from Contact Set ............................................................................................... 21
Flatten on Multiple Tops (Reference Well)................................................................... 21
Account for Missing Tops when Flattening .................................................................. 22
Page Size Indication and Removal of Fit to Page*....................................................... 23
Highlight Fault Tops Tied to 3D Grid............................................................................ 23
Plotting ................................................................................................................ 24
Filtered Interval on Maps and Intersections ................................................................. 25
Structural Modeling ............................................................................................ 26
Correction to Zone Log for deviated and horizontal wells ............................................ 26
Improve display of well correction results .................................................................... 27
Report well mis-ties even without correction................................................................ 27
Geometrical Modeling ........................................................................................ 27
Connected Volumes Improvements............................................................................. 27
Well Index Added to Geometrical Modeling ................................................................. 28
Petrophysical Modeling ..................................................................................... 28
Co-Located Co-Kriging ................................................................................................ 28
Generate Variance during Kriging ............................................................................... 29
Geophysics ......................................................................................................... 30
Improved Ant Tracking* ............................................................................................... 30
Seismic Calculator....................................................................................................... 31
Wavelet autotracker .................................................................................................... 31
Other interpretation improvements .............................................................................. 32
SEG-Y loader update .................................................................................................. 32
Synthetic tied to 2D seismic ........................................................................................ 32
2D/3D Seismic Lines on Map/Intersection ................................................................... 32
CDP /SP Posting on Basemap and Interpretation Window .......................................... 34
UKOOA navigation import utility update ...................................................................... 35
Memory management of seismic volumes: .................................................................. 35
Reservoir Engineering ....................................................................................... 35
Flow Controls .............................................................................................................. 35
Remote Simulation Run Submission ........................................................................... 36
Workflow Editor ........................................................................................................... 36
Keyword Editor Fixes .................................................................................................. 37
Local Gridding ............................................................................................................. 37
RESCUE upgrades ..................................................................................................... 37
Convert Keyword Case to Petrel Case ........................................................................ 37
Bubble Maps for Simulation and Production Data........................................................ 38
Ternary Saturation Display .......................................................................................... 38
Vector Property Display............................................................................................... 39
Isosurfaces.................................................................................................................. 40
Simulation Faults......................................................................................................... 40
Merak Economics ............................................................................................... 42
Petrel Plug-Ins..................................................................................................... 43
Introduction ................................................................................................................. 43
Osprey Risk Plug-in for Petrel ..................................................................................... 43
SNESIM Plug-in example ............................................................................................ 44
Adjacent Cell Example Plug-in .................................................................................... 45
Facies Cleaner example plug-in .................................................................................. 46
General Enhancements...................................................................................... 47
Online Manual Upgrade............................................................................................... 47
Major 2004 Bug Fixes ................................................................................................. 47
Hardware Recommendations ............................................................................ 53
Known Issues...................................................................................................... 56
Uncertainty
Uncertainty analysis could be performed in Petrel 2004 but required expert knowledge of the
Process Manager. The Petrel 2005 development focus has been to facilitate and improve
uncertainty analysis so it can be used by a larger section of the Petrel community. The
improvements can be broken up into the following key areas:
Uncertainty Process
A new process called Uncertainty Workflow Editor is added to the Utilities node in the
Process Diagram. When launched the user selects a previously defined Case which
automatically populates the process dialog with the Petrel processes used to create that Case.
Any process can now be selected to make it uncertain. Opening the process allows
replacement of any of the numeric values in the process with variables which are then
parameterized. For example a fluid contact might be replaced with $CON which could then
be defined as a random number between two depths. For stochastic processes the user simply
defines the seed variable and standard deviation (structural processes). Once this is in place
either a full Monte Carlo analysis or a Sensitivity run can be chosen.
There is also an option to use Latin Hypercube sampling of the probability distribution
functions.
The user has the option to run directly from the Uncertainty Workflow Editor or to generate a
workflow. This approach allows the process to remain simple but provides flexibility for the
expert user to create more complex workflows.
Integrated Structural Uncertainty

The structural processes Make Horizons, Make Velocity Model and Make Zones now have
the option to be stochastic, i.e., uncertain. This option is turned on using the Activate
Petrel 2005 Page 1

Uncertainty Page icon but is normally only used as part of an uncertainty workflow. The
stochastic uncertainty is based on the equation:
Sr = Sbc + U1σ * Usgs

Where:
Sr = Surface realization to be used in Velocity Model, Make Horizon or Make Zones.

Sbc = Is the base case surface calculated without uncertainty
U1sσ = 1 standard deviation depth error on the base case, can be a surface or a constant
Usgs = SGS with mean=0, σ=1 with zero value control points (i.e. at wells)
The user simply enters the value of U1sσ to the new column in the process table and if needed
changes the default values for the SGS algorithm settings in the new Uncertainty Tab. Each
time the process is run with a new seed a new error surfaces are created and added to the base
case surface using the equation shown above.
Uncertainty tab to
setup the SGS
parameters
Icon to turn on uncertainty
Column to enter the 1std

deviation error as a constant or a
surface.
Capture and Storage of Variables

In uncertainty workflows many results are produced so one of the key challenges is data
management. It is very important to know what values were used for the different variables
and to be able to regenerate cases for further analysis. Petrel 2005 has added the automatic
management of variables to the case system to facilitate this.
Petrel 2005 Page 2

When a looping workflow is run which includes Volumetrics or Simulation any variables in
the loop have their values stored in the Case. When a volumetric report is run a listing of each
variables value is produced for each case. It is also possible to automatically regenerate a case
simply by selecting Rerun Workflow from the right mouse menu on the case. Later releases
will allow the plotting of variables against volume and simulation results.
Variable values are

listed in the
volumetrics report
Option to recreate the case using the stored

variables
Global Seed
A new automated approach to generate a global seed for each case is introduced for this
version when running uncertainty from the Uncertainty Workflow Editor. When multiple
uncertainty workflows using stochastic uncertainty are generated each one can have a unique
global seed identifier that has stored random offset seed information for all the stochastic
processes used in the workflow. The advantage of the global seed is that the value reported
in the output sheet for any case can be re-entered in to any process to regenerate it.
When a stochastic process is launched from the Uncertainty Workflow Editor and the “Seed”
checkbox is selected in the uncertainty page (structural processes) or main page (property
modeling processes) then the input field is automatically populated with the variable $SEED.
This variable is added to the variables list in the Uncertainty Workflow Editor when the
process is applied. Any combination of processes can share this variable and the variable will
be associated with these processes in the same way as any other variable (see capture and
storage of variables).
Petrel 2005 Page 3

Seed setting for Make Horizons
Seed setting for Petrophysical Modeling
$Seed becomes associated with the processes and is added to the variables list.
$SEED is the integer value which represents the start of the random number sequence for
each process. This means that each subsequent layer or zone in the model will get a different
seed value to preserve the random nature through the model. All this information is captured
internally and $SEED is reported for each case when the Volumetrics report is run. Note that
$SEED is optional, if the Seed checkbox is de-selected than a random number will be
generated for each stochastic datum in the process. The difference is that no reference to the
seed is reported.
The command “Generate new seeds” is no longer used in this version. When new workflows
are generated that require new seed generation on any of the stochastic processes this must be
set explicitly in the process dialog. Projects saved in previous versions containing workflows
with “Generate new seeds” flagged in commands will be honoured.
Latin Hypercube Smart Sampling
Latin Hypercube sampling is a method of sensitivity analysis that requires fewer model
iterations to approximate the desired variable distribution than the simple Monte-Carlo
method. It achieves this by ensuring that the entire range of each variable is sampled. The
Latin Hypercube sampling method is activated in the uncertainty dialog. When selected all
probability distribution functions defined will be sampled according to the Latin Hypercube
Petrel 2005 Page 4

method. A new function is available in the Process Manager for seasoned users who want to
experiment with smart sampling outside of an uncertainty workflow
In the example plot below the upper histogram shows the result from a random distribution
function for 20 samples on a hydrocarbon contact height. The lower histogram shows the
results from the same function but with Latin Hypercube activated. Note the entire range is
sampled in the lower plot with no duplication of results.
Future releases will include the more advanced orthogonal array sampling based on Latin
Hypercube method allowing for more detailed sampling of multiple variables.
Multiple Histogram Plot for Sensitivity Analysis

Once a sensitivity analysis has been run the results are stored in the Case Tree. A new folder
management system ensures that each new case is placed in a folder named after the type of
uncertainty that was run. New folders can be added in the Case tree manually if desired.
A new sensitivity plot allows users to rapidly analyze the range of uncertainty graphically.
The plot is launched by right clicking on any folder in the case tree. A multiple histogram
plot with scaled axes is generated and the user simply selects which result to display from the
results tree. The plot is an excellent way to distinguish the parameters that are most sensitive
to uncertainty.
Petrel 2005 Page 5

New folder management: Folders
are created, re-named and cases are
stored in the appropriate folder
Launch sensitivity plot to visualize

all uncertainty results in a multi -
histogram plot
Petrel 2005 Page 6

Improved number
formatting All plots share the
same scale
Petrel 2005 Page 7

Core System & General
New Process Manager Functionality
New operations have been added to the Process Manager to extend the flexibility of the
uncertainty functionality and allow interchange of results and uncertainty parameters between
applications. These commands and functions can be found on the Utilities tab of the
Workflow Editor.
New function “List()” allows for

user defined numerical input
Sample variables using Latin

Hypercube
Import a tab separated text file
Read variables from output sheet
Export active output sheet to a tab

separated text file*
Export active window as emf file*
When deployed in a loop, Latin

Hypercube sampling optimizes parameter
value selection to ensure the maximum
range of uncertainty in the specified
number of iterations (see chapter on
Uncertainty for details).
Display the values in an output sheet and
export it to a tab separated text file with
the specified name and path
Define and store parameter values in an

external file and load to a workflow. The
file is imported as an output sheet and the
cells read to provide parameter values to
the workflow.
Export a map of each horizon in the 3D

Grid as an emf file with the specified
name and path
Petrel 2005 Page 8

Visualization Upgrades
Turn off Spin Animation

Spin animation in the 3D window can now be disabled at the system level. This option is
found in system settings and stored locally on the machine rather than specific projects such
that each user can define their own default behavior.
Improved surface rendering
V2004 V2005
Adaptive rendering of surfaces introduced in v2004 has been improved. The adaptation now
occurs over three tiers resulting in a smoother surface and improved representation across the
rendered edge boundaries.
Transparency on Surfaces
Surface attributes now support transparency in the same way that volume rendered seismic
supports transparency. This is exposed to the user via the color template for the attribute in
question in much the same way as for SEG-Y data. See also Improve display of well
correction results.
Improved ZGY volume rendering

Petrel now checks the graphics board of the host pc in order to allocate more memory
resources to the volume rendering. Currently this is activated for the most popular graphics
boards on the market.
3D Well/Log Display Performance

A new smart decimation algorithm has been introduced to display wells and logs in 3D to
improve performance when many wells or large amounts of log data are displayed. In the
case of log data the resolution of the display is controlled by camera angle and proximity to
the data such that the full resolution is only shown when the camera is up close. The color of
the well log is always shown at full resolution.
Example: 320 wells with 150-550 points per well displays at 16 fps on a standard Dell M60
laptop. Displaying a gamma log on these same wells (15 cm interval, 3000 - 13000 points per
well) reduces the display to 7 fps but is still interactive. Without decimation the scene motion
reduces to less than 2 fps.
Other Visualization Improvements

• 3D rendering of very large images is now consuming less memory
Petrel 2005 Page 9

• Full Screen mode is now displaying the status bar.
• 3D rendering of attributes on surface is faster and the quality is improved
• 3D decimation now supported for surfaces as well as well data.
Principal Component Analysis (PCA)

Principle component analysis is a data processing set prior to running the train estimation
model process. It is used to create optimized properties for the process, preserving all of the
relevant information from the full suite of data but condensing it into a few principal
attributes.
The analysis is integrated into the train estimation model user interface in much the same way
as the correlation coefficients. The contribution of each of the initial properties into the
principle components is shown in a table (see image). The principle components can then
compared to the training data using the correlation table and be used or rejected for the
estimation as required. When applying the estimation model the conversion to components is
taken care of behind the scenes and thus hidden from the user.
Utilities - Add Point Digitizing

The Make/Edit Polygons process has been extended to
allow direct creation and editing of points in the 2D and 3D
windows. There is a new tool “Make/Edit Points” on the
function bar for Make/Edit Polygons. New points are added
using the “Add new points” tool . New points will have
the domain of the object on which they are digitized.
This feature will help streamline the workflow for making, for example, well design targets,
source points for channel modeling, training points for estimation models and other
applications where previously a polygon would have to be converted to points. Future
development will allow the user to interactively add attributes to the selected points.
Ergonomics - Clean up Insert and Windows Menus
Petrel 2005 Page 10

An effort has been made to
improve Petrel ergonomics by re-
ordering the Insert and Windows
menus.
These menus developed rather
haphazardly as Petrel evolved.
We have now standardized on an
alphabetic order for Windows
and Objects
Petrel 2004
Petrel 2005
Petrel 2005
32bit Compatibility Mode on 64bit Windows

Petrel 2005 will be certified as a 32 bit application to run on certain 64bit machines running
XP 64.
• Petrel 2005 will be supported on Windows XP 64 as a 32-bit application

• The dongle is not supported on Windows XP 64 and must be installed on another 32-
bit machine.
• Future versions of Petrel will support a completely standalone Windows XP 64 install
Windows XP 64 gives each 32-bit application access to additional 2GB of memory,

increasing the accessible memory for Petrel to 4GB.
Due to OS memory fragmentation, the application can only access 1GB continuous memory
on Windows XP 64 and 700MB on Windows XP 32. (No calculations were done on
Windows 2000).
It should be noted that after Petrel has been running for some time, its allocated memory
becomes more and more fragmented as items are turned on/off, windows opened and closed
etc. If you find yourself unable to load a seismic volume of a reasonable size it is always
worth first saving your project and restarting Petrel - thus creating a fresh continuous piece of
memory to work with.
A powerful new workflow would be to run Petrel together with 64bit FrontSim streamline
simulation on the same workstation, thus allowing much larger models to be simulated
locally without the need to submit jobs to remote machines
Petrel 2005 Page 11

Run Petrel from a command line
Petrel can now be launched (and shutdown) from the command line. It is also possible to
specify a workflow to run and values for variables in that workflow.
It may be desirable to set up a default project environment for a set of Petrel users or user
community. For example, an asset team or department would like to share a project template
that all Petrel users share. This may include projection system information, Well symbols,
color templates, folder structure and naming conventions, for example.
The command line syntax is as follows:
Petrel [/runWorkflow myworkflowname|/runAllWorkflows] [/exit] [/quiet] [/[s|n]parm
myvar1=9,myvar2=3] /licensePackageCol n d:\work\myprojectfile.pet
• /runWorkflow - will run the named workflow in the named project
• /runAllWorkflows - will run all workflows in the named project
• /[s|n]parm - pass variables to the workflow (s for string, n for numerical)
• /exit - terminates Petrel after running workflow
• /quiet - runs the workflows without launching the workflow window
• /licensePackageCol n - column number of license package that you want to check out
without being asked
Example workflow
1. Open a new Petrel project and set the projection system information, color
templates, folder structures, window set ups, variable values etc desired for the
target petrel user community.
2. Save the project to a shared area.
3. Make a batch file that launches the application with the new default project
parameters. Example text: "C:\Program Files\Schlumberger\Petrel 2005\Petrel
2005.exe" "D:\Petrel\Template.pet".
4. Save the batch file and distribute it to the target user community.
Petrel 2005 Page 12

OpenSpirit upgrades
Introduction
Petrel 2005 requires OpenSpirit 2.8.1 or higher. Petrel workflows with OpenSpirit have been
extensively tested with GeoFrame 4.2 and OpenWorks 2003.12 on both Linux and Solaris
What’s new with this release

1. Enhanced Sync Tool
2. Improved Well top handling
3. Improved connectivity and logging
4. Well Symbol mapping improved
5. Shared checkshots Support
6. Substantially robust Petrel ↔ OpenSpirit transfers
Synchronization Tool
Projects and sessions are

different. Clear warning label
Project information
clearly visible
Individual item selection in

sync tool possible
LMD’s updated
only on demand
Quickly undo
mistakes; change
direction
Improved Well Top Handling
When transferring data via OpenSpirit, individual Well tops can be selected for transfer.
Selection can be done on a per-well basis or for a given well top for all wells or any
combination.
Petrel 2005 Page 13

Improved Well Top Handling
• Sync tool shows well top folders
• Allow the user to select objects on
a folder basis
• The user can select to export all
well tops for a well, by selecting
the well tops folder.
• Allows the user to export a single
well top for all wells.
• Filter when exporting Well Tops Individual
handling of
• Export data only for selected wells well tops
Improved Connectivity and Logging

Improved and more consistent messages
during OpenSpirit transfers
Automatically logging to
file (optional)
Timestamps (optional)
Session Connectivity Enhancements
• Petrel’s automatic reconnection to
OpenSpirit on startup is more robust
• Possible to launch OpenSpirit
DataSelector from OpenSpirit Settings
• Data Selection events is enabled by
default
• Object selection option is obsolete and
is removed
Petrel 2005 Page 14

Well Symbol Mapping
10 new symbols (Petrel default)
More consistent mapping
User controlled mapping (using xml files)
16 wells are consistently mapped
Petrel
60 different well symbols – maps to 41
unique OSP attributes.
Petrel – GF – Petrel
41 wells are consistently mapped
Petrel – OW – Petrel
GeoFrame – Petrel 60 different well symbols – maps to 19
147 IESX definitions – maps to 63 unique unique OW well descriptions
OSP attributes. These 63 wells map to 36
unique Petrel wells
Checkshot Improvements
Shared Checkshots are now possible;
• Enables users to post their wells on seismic in time
• OpenSpirit allows transfer of shared checkshots
• During transfer the well that owns the checkshot in GeoFrame is automatically
transferred
• Shared checkshots will not be enabled for any synthetics workflows
Log Curve Mnemonics and Well Symbol Mapping

Petrel 2005 and later version support custom mapping for log curve mnemonics and well
symbols. XML files exist in the installation directories (in Petrel base installation
directory/XML) and these can be customized to the user’s specifications.
LogNamesToPropertyTypeCatalog.xml Controls Log Curve Mnemonic mapping
WellTypesToOpenSpiritWellSymbol.xml Controls the transfer from Petrel to

OpenSpirit
OpenSpiritWellSymbolsToWellType.xml Controls the transfer from OpenSpirit to

Petrel
Editing the XML files is self explanatory. Comments embedded are in the files to help the
users. In the case of Well Symbols, both independent files must be edited to the same values
to ensure consistency.
Petrel 2005 Page 15

Editing these files is a more system administrator task than something that a “normal” user
will would do. Making changes to these files can substantially impact application behaviour.
Wells
Well matches are done using the UWI in Petrel 2005 onwards instead of the name. This
means the user is able to properly import two wells even both wells have the same name.
Well tops, checkshots and logs all automatically import the owner well as well, if that well is
missing in the project.
Other Open Spirit Improvements

There have been a large number of improvements and fixes resulting in substantially more
robust Petrel-OpenSpirit transfers.
• Grids
o Improved memory handling for large grids.
o Imported attribute maps from Charisma no longer drops data points.
o Attribute maps import no longer flips signs incorrectly
• Seismic
o IESX 2D seismic lines are correctly imported.
o Negative Increment volumes export now supported.
o Sending 3D Seismic from Petrel to Seisworks is more robust.
• Wells
o Exporting edited wells to GeoFrame is now more stable.
o Borehole bottom depth is automatically updated in Petrel.
o Deviation survey exported back to GeoFrame is more stable.
o Deviation survey is now visible in OpenWorks Deviation Data Manager.
o Edited well deviation export works with GeoFrame.
o NULL elevation references for wells in GeoFrame projects now supported
o Last modified dates for boreholes are updated correctly
• Logs
o Exporting new Well Logs to OpenWorks honors OpenSpirit settings for
interpreter settings
• Checkshots
o Large number of checkshots can be imported to Petrel
o Checkshot import honors session time units
• Horizons & Faults
o Horizon import from Seisworks no longer corrupt data
o Last modified dates for horizons are updated correctly
Petrel 2005 Page 16

o Re-importing edited Faults into Petrel is more stable
o (Fixed in OpenSpirit) Depth faults are no longer imported with incorrect signs
Prosource Results Manager Connection

Petrel 2005 will include extended support for ProSource Results Manager 3.5. ProSource RM
is scheduled to be released March 2006.
Checkshot sharing
It is now possible to share Time/Depth information in the form of checkshots from one well
for use in any other. When checkshots are loaded to a in a Petrel project the information can
be stored on one well and used by other wells by selecting the new “Share checkshot” option
in the Time page in well settings. When applied a new time log is generated on the target
well(s) based on the information from the operator well. This option is useful when importing
regional checkshot data.
Improved calculation of well path geometry in time domain.

During time conversion of wells the trace is now sampled at the resolution of the deviation
survey. In Petrel v2004 the well path was linearly interpolated between the tie points
sometimes resulting in unrealistic well paths displayed in the time domain. In Petrel 2005
velocity is calculated at each point in the well trace ensuring the shape of the well path is
honored in both domains
Petrel 2004: Time well path linearly interpolated between tie points.
Petrel 2005: Velocity calculated at each point in the well survey to restore the true well geometry.
Small enhancements
• New function available in calculators: InvCumNormal. User supplies the Mean, Std
Dev and probability of a data range. Petrel returns the value of the range at the chosen
probability.
Petrel 2005 Page 17

• Improved Oil & Gas properties settings layout in Volume Calculation process.
• New intelligent symbol display “auto” in style page for points data sets displayed in a
2D and 3D viewer. With this option set, if point set contains more than 20,000 data
values then the display is 2D squares, otherwise 3D spheres.
• New option in well design to specify upper and lower Dog Leg Severity constraints at
design points in the well trace.
Petrel 2005 Page 18

Well Correlation
Well Section = Well Fence
The old well intersection fence
functionality where you could
generate a vertical intersection
based on a series of wells has been
rolled into the well section and can
be used to display the Well Section
Fence in 3D, Intersection and Map
views. Any well section now
automatically contains a Well
Intersection Fence.
The location of the tie point is under

user control either through the well
at the top, middle, bottom or
through a user selected well top. In
addition a second tie point can be
added at the bottom of the well
(very useful for highly deviated
wells). We have incorporated a
smart logic to try to ensure the best
possible polygon through the tie
points.
This works as any other vertical
intersection and can be used to
display seismic, models, properties
etc. between the wells.
Petrel 2005 Page 19

Well Filter
A new folder has been added to wells called Well Filters.
Filters can be created based on absolute

Z value or based on Well Tops or
Surfaces. They include an optional
blanking region above and below the
chosen subject.
Missing Top logic is included so that if
a well misses a selected top then the
system will try to use the next available
top or the top or bottom of the well
(Zone logic)
The filter can be applied to all or a
selection of wells.
Filters are additive so more than one
range can be filtered.
Filters replace the Simplification option
on wells and can apply to 3D, Maps,
Intersections and Well Section.
Petrel 2005 Page 20

Tracks in Well Section
In Petrel 2005 when a curve is added to a Well
Section it is placed in a Track. The new Track
object replaces the Group Panel found in previous
versions but has additional display controls:
Track Widths
The width of the track is controlled from the track
settings. This replaces the width control which was
found on individual logs. The width on logs now
only applies in other single track views such as 3D
and intersections; it is therefore grayed out in Well
Sections windows.
Grid Line Control for Tracks

Display of grid lines is now under user control via
the Track settings. This includes how the vertical
divisions are created, their color and width as well
as controls on the Track background.
Fluids from Contact

Set
A new option has been created
on Contact Sets to
Insert/Update Fluids Log. This
will create a new global well
log which represents the fluid
column seen in the well based
on the chosen contact set.
The behavior is very much
like the Insert/Update Zone
Log which is available from
the Tops folder.
Flatten on Multiple Tops (Reference Well)

A new option has been added to the Well Position settings which takes a reference well and a
Well Tops set. With this option all tops are flat with the wells stretched and squeezed
between the tops to match the reference well. This is a very interesting display for picking
tops within a stratigraphic sequence seen across multiple wells.
Petrel 2005 Page 21

When many wells are used with a single log curve, no depth track and minimum well spacing
then the display starts to look similar to seismic correlation. This is a very good way of
controlling and presenting field wide correlations for large numbers of wells.
Account for Missing Tops when Flattening

A very useful feature of Well Section is the ability to flatten on a Well Top. However wells
not containing the chosen Top had to be positioned manually in Petrel 2004.
Petrel 2005 implements a “Missing Top” logic:
• If the chosen well top is missing then Petrel will look for the next top up in the
stratigraphic column, if there is no top above then the search will look down in the
column.
• Wells will be aligned based on the nearest top present.
Petrel 2005 Page 22

Page Size Indication and Removal of Fit to Page*
Previously wells added to a Well Section were adjusted to fit to the page. This made it very
difficult to setup a plot with a fixed track width for the wells. The “fit to page” option has
now been removed so well tracks get a default width which can be adjusted via the Track
settings. In addition the Well section now has a black dotted line which indicates the edge of
the page. Wells that go beyond the page limit will be grayed out.
Black dotted line indicates the page

edge. Wells outside the page are greyed
out.
Highlight Fault Tops Tied to 3D Grid

A Fault Top can be locked to the 3D model faults in the Fault Modeling Process. Now any
Tops that are locked in this way will get a lock icon both in the main and sub labels in a well
section.
Petrel 2005 Page 23

Locked Fault Tops with lock icon
Plotting
Improved Contour Labeling*
A new control has been added to contour

annotation called “Start”. This controls the
distance along a contour before a label will
be inserted, the next label will be controlled
by the “Interval” setting. The result is more
contours getting labels but without
repetition on a given contour.
Petrel 2004 June Petrel 2005
Improved Contour Width Control*
Petrel 2005 Page 24

In previous Petrel releases it was found that on certain plotters it was difficult to distinguish
between bold and normal contours. In Petrel 2005 the difference in width between a bold and
normal contour has been recoded to give better results particularly on high resolution plotters.
Transparency on Polygons*
Polygons now have a transparency control in the
settings.
Zero Contour Lines*

Surfaces which had a minimum Z value of zero
did not show a zero contour in previous Petrel
releases. The zero line has been implemented in
Petrel 2005. This is particularly interesting for
isochore maps.
Filtered Interval on Maps and Intersections

The Well Filter can be used in any of the views (see Well Filter in Well Correlation section).
Map: Well filtered on reservoir interval Intersection: Well filtered on reservoir interval
Lock Scales on Map and Intersection*

The new tick box in the settings for maps will
lock the scale. You will no longer be able to
zoom on the map (scroll wheel on the mouse
or + and - on the keyboard)
Petrel 2005 Page 25

Independent Printer per Plot Window
This development should help a great deal in producing plotter output. Previously each plot
could have separate page size, rotation, margins etc. but the project could only have a single
printer defined. Changing the printer would often mess up the plot layouts. Now each plot
can have its own printer defined so for example a project might have some plots setup for a
large plotter with others set for standard A4 printer.
Copy / Paste on Annotation Table

The Annotation table now supports copy and paste with Excel. Many companies have
external data sources for information they wish to display on maps and it was very tedious to
type this into Petrel. The solution now is to import the data to Excel then paste into the
annotation table. Of course the Excel sheet will need to have the correct columns but this is
easily checked by first making a paste from the annotation table to Excel.
Remember that annotations in Petrel can be linked to data objects (horizons, wells, points,
etc.) so that they are only displayed if the linked object is displayed.
Overposting Control on Plot Labels

A control has been included in the
display setting for well tops on map
views to avoid labels writing on top of
each other. Several overpost options are
available from the drop down menu.
* denotes implementation in Petrel 2004 October patch release.
Structural Modeling
Correction to Zone Log for deviated and horizontal wells
Well correction in Make Horizons, Make Zones, Make Velocity Model and Make Surface
will now take account of more of the information in the zone log. If the zone log indicates
that a section of the well is within a certain zone, the horizons above or below that section
will be forced up or down to ensure that this is the case. This is treated as 'soft' data so the
correction is not done unless the sections appear in the wrong zone after a standard well
correction. The general shape of the horizons in these areas is preserved during this operation.
This operation naturally requires that the zone log is defined correctly. In situations with
many erosive horizons or faulting it is recommended the user QC the zone log carefully to
make use of this option.
Petrel 2005 Page 26

Improve display of well correction results
Residuals from the well correction can now be written to the well tops as attributes rather
than to a separate point set. This makes it easier to search in the well top spreadsheet and
toggle off well correction for well tops with low confidence (sort the spreadsheet based on
the residual). Or find the appropriate well and QC the data.
Outputting a residual surface now creates the final surface as a 2D grid with the modeled
residual as an attribute. Areas where the correction is close to zero are rendered transparent,
and positive or negative corrections rendered red or blue respectively. This makes it very
quick to identify which wells are controlling the well correction and where problems may be
occurring.
Report well mis-ties even without correction
In many situations it is useful to run the modeling without any well correction initially to
understand the quality of the data. If the data is poor then the result will be heavily dependant
upon the well correction and the cause of the poor model may not be obvious to the user.
By selecting the well tops as normal and choosing 'none' for the well correction the user can
run the modeling and understand the mis-ties without correcting the model.
Geometrical Modeling
Connected Volumes Improvements
The connected volumes functionality in Geometrical Modeling has been improved.
Petrel 2005 Page 27

Stop at faults - There is now the option to force the algorithm to stop at faults and ensure that
volumes crossing the faults are treated separately.
Seeded tracking - The algorithm can now be seeded by a single well, a folder of wells or all
the wells in the project. It can return all of the volumes connected to the well or group of
wells or all of the volumes not connected to the wells. This may be used to give an indication
of the volumes available to proposed wells or identify the areas that new wells should target.
The speed of the algorithm has also been improved.
Well Index Added to Geometrical Modeling
Within Geometrical Modeling there is now the option to create an index property based on
the well passing through a particular grid cell. The color template is updated to give the
correct name and color of the well.
This can be used to color points in the function window to identify which well each point
belongs to. It can also be used to filter out data from a particular well either for display in 3D
or a function histogram window, or within a workflow. A common method of testing the
suitability of a particular property population method is to perform the modeling repeatedly,
removing input data from the modeling and then estimating the result at that point. This index
will help advanced users to do this with the help of the process manager.
Petrophysical Modeling
Co-Located Co-Kriging
Co-located co-kriging has been added to the GSlib kriging options in Petrophysical modeling
and in Make Surface (in Make surface this required the addition of the kriging by GSlib
option). The ‘none GSlib’ kriging does not have this option but has been retained because it
can work in real coordinates rather than simple simbox space.
The option takes a correlation coefficient of between 0 (which results in standard kriging) and
1 (the same as kriging with a trend). This is regarded as a basic statistical method that has
been missing from Petrel until now. The option allows the user to effectively choose the
weight given to the secondary data as demonstrated below.
The original porosity property.
Petrel 2005 Page 28

Permeability property modeled using
kriging with no trends.
Permeability modeled using co-located

co-kriging against the porosity model
and a correlation coefficient of 0.55.
Permeability modeled using co-located

co-kriging against the porosity model
and a correlation coefficient of 0.95.
Generate Variance during Kriging
Variance calculated internally during kriging can now be exposed as a property

(petrophysical modeling) or an attribute (Make Surface) after the modeling. The variance
property is a factor of the input data and the chosen variogram and describes some of the
spatial variation in uncertainty in the model. Areas close to input data will have a low
variance (i.e. are predicted with confidence, low uncertainty) whilst areas away from input
data will have high variance (i.e. are predicted with low confidence, high uncertainty).
To calculate the correct variance the sill should be defined correctly (without the normal
score transformation being done). This is the principal reason for the request to allow
variograms with a sill<>1. Due to usability issues and problems with using a sill<>1, this has
not been enabled. Instead the calculations are done internally to ensure that the correct
variance is reported based on the true sill of the data. If the sill needs to be changed then it
can be done by using a scale shift in the data analysis process.
Petrel 2005 Page 29

The original kriged result.
The associated variance property,

normalized with values from 0 (blue)
close to wells to 1 (red/pink) away from
the wells.
Geophysics
Improved Ant Tracking*
The workflow has been redesigned based on user feedback and recommendations. New
features include:
• Decoupling of fault patch generation from Ant-tracking attribute generation. This
allows users to use other attribute cubes (e.g. internal propriety attributes) to extract
faults. Users can also use GigaViz 3.1 to generate ant volumes using cluster
technology and then move them to Petrel to extract faults
• Improved parameter control: enhanced control over fault patch extraction
• Greater accuracy honouring original seismic
• 10+ times faster than previous method for batch extraction mode
• Interactive seeded fault-patch auto-picker - A step change compared to conventional
fault interpretation workflows
Workflow example:
Digitize seed points Extract fault patches Merge Convert to fault segments
Petrel 2005 Page 30

* Originally released as part of September 2004 patch
Seismic Calculator
A new calculator based on the standard Petrel calculators has been added to the SEG-Y
volume subject. The calculator can be used by interpreters to combine volumes, scale seismic
data and perform other mathematical operations.
Workflow example: The simple example below illustrates its use in combining an ANT
tracked volume highlighting faults, with migrated amplitude volume.
Launch seismic calculator

and enter script
Input cubes
(Amplitude &
Ant cube)
Resulting output volume

with enhanced faults
Wavelet autotracker
A new wavelet auto tracking feature
has been added to the Seismic
Interpretation module. The wavelet
tracker works by testing potential
expansion points using correlation of
a seismic trace window around the
pick location.
The tracker is applied as a final
constraint after a pick has been
passed by the other parameters.
Petrel 2005 Page 31

This new feature, requested by many of the Petrel geophysics community, brings more
control to the interpreter in areas of poor data quality
Other interpretation improvements

• Enhanced 2D seeded tracking and guided tracking. The parameter selection left is
used.
• Manual tracking can now snap to events
SEG-Y loader update

A new option to import SEG-Y data includes more flexibility in loading non standard files. It
enables specification of header location to read parameters from, and includes a SEG-Y scan
utility.
Synthetic tied to 2D seismic

• Loading of ASCII wavelets has been extended. It is now possible to bring your
chosen wavelet in from another application or processing house
• Seismic Reference can be a 2D line.
• Synthetic can be tied to 2D seismic data
2D/3D Seismic Lines on Map/Intersection
Petrel 2005 Page 32

It is now possible to change the heading annotation for interpretation windows. Users can
now select which attribute is to be displayed in the upper and lower annotation lines. Settings
can be applied to all other interpretation windows.
Petrel 2005 Page 33

CDP /SP Posting on Basemap and Interpretation Window
In Petrel v2004 and previous releases it was possible to display seismic line annotations on a
2D window. In this release the functionality has been extended to the map and interpretation
view. The following visual attributes are now supported;
2D Lines:
• Line name, Tick Marks, Header Number
3D volumes:
• Survey outline, Seismic lines interval, Header numbers (visible only or all)
It is also now possible to retrieve mouse

over information on seismic surveys
Surveys can now be displayed from any

level in the data tree allowing for rapid
toggling between data.
Petrel 2005 Page 34

UKOOA navigation import utility update
• Free format definition of columnar ASCII files
• Loading of multiple lines in one run
This will make it much easier and quicker to load 2D seismic data
Memory management of seismic volumes:

Enhancements have been made to enable larger volumes to be loaded to memory, approx
700MB limit. Petrel 2005 runs in 32bit mode on 64bit workstations, offering more available
memory.
Modifications have been made to the autotracker. In Petrel 2005 the program no longer
attempts to grab a large chunk of continuous memory prior to tracking, but works by using
smaller chunks of memory as needed. In previous versions application terminations caused
by a lack of memory during the tracking process sometimes occurred if a large volume was
being tracked.
Reservoir Engineering
Flow Controls
The flow control process allows you set primary controls modes and targets (e.g. oil rate,
target=1,000bbl/d) for folders of wells, and to turn on which secondary constraints you want
(e.g. water cut). To set values for the secondary constraint you go to the spreadsheet
accessible from the flow control subject on the input tree. In the spreadsheet in Petrel 2004
you had to type the value for each individual well – tedious! In Petrel 2005, rows are created
for each well folder in the spreadsheet, so you only have to type the number once. See for
example the ‘Producers’ folder in the screen shot, and note that the value of 0.5 is only bold
in one place (top left cell) – all the others were filled in automatically by Petrel.
Petrel 2005 Page 35

Remote Simulation Run Submission
Petrel 2005 supports submitting simulation runs to remote machines.
Support for this must be installed on the local PC (client) and on each of the remote machines
(servers). Detailed instructions are in the online manual under Remote Simulation.
The use is straightforward in two steps:
• On Tools | System Settings | Queue Definition you define the queues available to
you and specify your userid and password. The queue definition is stored in a
configuration file, so this can be done by a central administrator for the whole
company or site.
• On the Advanced tab of Simulation Case Definition, you choose the queue in which
to run the simulation.
The system handles transferring files to the remote machine, launching the run on the remote
machine (including support for the LSF queuing system) and periodically checking on the
progress of the run and fetching the results back again. Results are loaded into Petrel and
your plots updated as the run progresses.
Workflow Editor
Commands to load simulation results and operate the summary calculator have been added to
the Workflow Editor.
Petrel 2005 Page 36

Keyword Editor Fixes
The keyword editor now preserves the order of user keywords in all sections. This allows the
use of more advanced ECLIPSE features in conjunction with the ever increasing scope of
automation, especially uncertainty analysis, in Petrel.
Local Gridding
An option has been added to use the active property when selecting cells for local gridding.
Use this option with caution – it may result in many very small local grids, with lots of non-
neighbor connections between them and the global grid, which will cause the simulation to
fail. However, this option does allow more complex situations to be handled: for example,
use geometrical modeling to create a property of distance from an unconformity surface, filter
cells on this property, and make a local grid around the unconformity.
RESCUE upgrades
The RESCUE importer and exporter are being upgraded to version 37 of the RESCUE
libraries. In addition, Petrel 2005 supports the following additional items for both import and
export via the RESCUE format:
• Local grids
• Wells
• Fault transmissibilities
• Time varying 3D properties, such as pressures and saturations from simulators.
Convert Keyword Case to Petrel Case

In Petrel 2004, it was possible to bring in many of the bits of an existing ECLIPSE data file,
but it required the user to break the file up into separate pieces, and import each of them
separately, and then create a new case.
Petrel 2005 Page 37

Petrel 2005 greatly simplifies this. Simply import the keyword case, right mouse click and
select convert to Petrel Case. All the data in the file that Petrel understands will be imported
into the Input and Model trees, and added to a new case.
Note: not all data in the file can be imported and the generated case may not be a valid
ECLIPSE case! Keywords that Petrel cannot import will be left in the new case as user
keywords. The user will have to do some work on most converted cases to fix things up.
Future releases will further facilitate the conversion process.
Bubble Maps for Simulation and Production Data

A longstanding user request against both Petrel and ECLIPSE Office – finally we can display
well time varying data such as production rates as bubble maps. The feature works for
imported observed data, flow controls and simulation dynamic or summary results, and is
controlled from the results tree.
Ternary Saturation Display

The ternary display is a popular way of showing oil water and gas saturations at the same
time, using blue for water, green for oil and red for gas. This is now supported in Petrel 2005.
Petrel 2005 Page 38

Simply open the Settings for the Properties folder, choose the new Composite tab, and add a
ternary property.
Vector Property Display

Like the ternary display, this special display uses the composite properties feature to create a
special display based on multiple inputs, in this case the inputs are the flows in I+, J+, K+
directions and the result is a 3D arrow plot display.
Petrel 2005 Page 39

Isosurfaces
Isosurfaces shows the 3D shape of a constant value of a property – a bit like a 3D contour.
They’re useful for seeing the shape of an advancing water front, or a contaminant plume.
To create an isosurface, go to the settings of a 3D property, select the Style tab and the
Isosurfaces sub-tab.
Tip: to see your isosurface, you need to remove the regular 3D solid display. The easiest way
to do this is to use the I, J or K slices on the function bar of the geometrical modeling process.
Simulation Faults
Engineers often want to add barriers to flow as part of the history matching process. This is
now easy: simply use the Make/Edit Polygon process to digitize a line across the grid where
you want the barrier or fault. Then right mouse button click on the polyline, and select
Convert to Fault. Petrel will create a zig-zag fault on the active grid. You can use the Fault
Property Analysis process to assign a transmissibility multiplier to it, or the Edit 3D grid
Petrel 2005 Page 40

process to create throw across it. You can also delete it, unlike faults that are part of the 3D
structural framework of the model.
Petrel 2005 Page 41

Merak Economics
Economics has been added to Petrel by the Merak
Value & Risk portfolio. The economics engine is
based on the market leading Peep product. Petrel
can either inherit oil or gas price scenarios
together with tax regimes from a full Peep
analysis or use the supplied library of over 100
fiscal models. These can then be applied to the
results of multiple simulation runs. The simulation
runs provide the flow inputs such as oil, water, gas
but also feed the economics with events which can
trigger drilling or workover costs. Well costs can
also be taken from the results of the Osprey Risk
plug-in.
Petrel 2005 Page 42

Petrel Plug-Ins
Introduction
Petrel Plug-ins are enabled by the Ocean API for Petrel. This API was introduced with Petrel
2004, and has been extended in Petrel 2005. The API currently exposes the following data
types from Petrel:
• Pillar grid geometry and properties
• 3D seismic
• Wells
• Well logs
• Well markers
• Well completions
The Ocean API for Petrel 2005 enables elegant and efficient augmentation of Petrel end-user
functionality, e.g. through the introduction of new geological model property population
algorithms, or through efficient seismic processing algorithms.
Please note, however, that significant functionality will be added with Petrel 2007.1, and that
the API’s will change during the next release cycle.
For documentation of how to use the Ocean API, please refer to the separate documentation
in the APIDevKit directory under the Petrel installation directory.
The Plug-ins described below are examples that have been developed on top of this API.
Osprey Risk Plug-in for Petrel
Transform well engineering with a smoother workflow
The Osprey Risk plug-in for Petrel workflow tools is the efficient way to assess your
proposed wells and focus on achieving the best balance of risk, time, and cost. For the first
time, you can pick targets, identify surface locations, and iteratively design trajectories in
your reservoir model to find the optimal solution.
This technology ensures that each aspect of the well’s design is updated as you manipulate
your model or proposed well. Perform a reality check on any proposed trajectory and let the
drilling engineers focus on feasible proposals rather than on the feasibility of the proposals.
Your modeling defines your prospect. Modeling also drives how you exploit the prospect.
By creating a detailed operational drilling program using a standardized and consistent
process, you can compare projects with confidence.
Petrel 2005 Page 43

SNESIM Plug-in example
The Petrel Plug-in for SNESIM comes as a separate installer with Petrel 2005. It is designed
to serve as a friendly front-end interface to the SNESIM executable (snesim.exe). The Petrel
Plug-in for SNESIM will allow users to develop usable workflows based on multipoint
geostatistical methods. SNESIM stands for single normal extended equation simulation and
aims at simulating structures borrowed from training images, conditional to well data. The
availability of this functionality as a plug-in may provide valuable user feedback to help
guide the development of this technology in Petrel.
The process dialog provides drop boxes and text areas to identify the necessary input
parameters (Input grid, training images, trends etc) to run SNESIM. The current version of
SNESIM requires the user to supply a minimum input of a target pillar grid, property grid and
training image. Exact details of these input parameters are well documented in the SNESIM
User Guide. Advanced settings allow the user to adjust target proportions, define scaling
parameters and enter various other parameters. See the SNESIM User Guide for more
information.
Petrel 2005 Page 44

Adjacent Cell Example Plug-in
The Adjacent Cell plug-in comes as a separate installer with Petrel 2005. It is designed to
facilitate computations between adjacent cell values in a 3D grid. The plug-in has many
applications currently outside the scope of the property calculator. The plug-in requires an
input grid and property. The input property may be either discrete or continuous. When
executed, the plug-in generates a copy of the input property in which each cell is assigned the
value of the neighbouring cell in I, J, or K directions.
An example workflow might be the identification of cells containing shale that are set next to
reservoir sand. These cells could represent a high transmissibility and after identification by
the property calculator can be used to assign the appropriate multiplier to these cells.
Petrel 2005 Page 45

An extensive help document with further workflow examples is available with the installer.
Facies Cleaner example plug-in
The Facies Cleaner plug-in is designed to facilitate cleaning of “noisy” discrete facies
properties. Such noisy properties are typical of the output of Sequential Indicator Simulation
(SIS). The image below-left shows a property realization after modeling with SIS. The
property to the right is the same property after “facies cleaning”. An extensive help document
with workflow examples is available with the installer.
Petrel 2005 Page 46

General Enhancements
Online Manual Upgrade
A considerable maintenance effort has been put in to the On-Line Help manual. Several
chapters have had a face lift and old images relating to previous versions have been replaced
with images from the latest version. The on-line help manual is always a document in
progress and thus will be upgraded along with each major patch release.
Major 2004 Bug Fixes
Geophysics
Issue ID Component Description
SEGY volume created from a property has limited
909634 Export - SEGY export options.
Geophysics - Interpretation Depth conversion of fault sticks do not fall in the
1155810 Wind right place on the seismic
Import checkshot creates bogus values and when
1153411 Import - Checkshots displayed in time
Import of checkshot in TVDSS the well displayed in
1153413 Import - Checkshots TWT is incorrect
1151417 Geophysics - Vol Rendering several problems with zgy file
Export seismic from petrel to GF, Charisma project
463437 OpenSpirit - Export gets corrupted
Cannot OpenSpirit "shared" GF checkshots into
1147266 OpenSpirit - Import Petrel.
911276 Other - Unspecified Realized seismic is corrupted when zipped
Velocity model generated via velocity cube does
1150311 Struct Mod - Depth Conversion not output full written report
1143038 Import - SEGY OpenSpirit export of seismic volume to IESX fails
Geophysics - Interpretation Wrong inline/xline annotation nr in interpretation
1151949 Wind window
SEGY-Settings tab is missing Byte location options
1137610 Import - SEGY 205-208 and 209-212
1143397 Import - Unspecified Imported wavelet lincorrect.
Core & Modeling

issue id Component Description
1148797 GUI - Main User Interface Project corruption in minor cases.

Import of GeoFrame Well_Symbols drops too
911668 OpenSpirit - Import much classification data
Adding vertex to input tree after loading the
1141732 GUI - Unspecified project.
Problems related to null elevation reference in
911669 OpenSpirit - Import GeoFrame project
1140417 Licensing Petrel Viewer: missing functionality
1151372 Other - Colortable and Attribute map from facies property crashes petrel
Petrel 2005 Page 47

Templates
1149818 Other - Unspecified error on trying to perform well intersection
Petrel crashes when selecting 'connected
1150751 Prop Mod - Data Analysis volumes' in Data Analysis
Export - 3D Grid - All Grid export with traverse first along j option
1150454 Formats selected fails
1158958 OpenSpirit - Import Well queries not unique - switch to using UWIs
Other - Colortable and Crash when changing template from continous to
1150132 Templates discrete & using colour table
1155143 Other - Unspecified Memory problem - project with 1GB .pet file
1158084 Other - Unspecified Project runs extremely slow
LAS files exported do not contain correct log unity
1158213 Export - Well Data of measurement.
Geophysics - Seismic Autotracking parameters don't work for 2D Seismic
1137897 Interpretat lines
Geophysics - Seismic Limited Autotracker - Needs wavelet tracking
1148906 Interpretat option
1146728 Import - CPS Error importing CPS-3 data into Petrel
1141302 Import - SEGY Fail to detect 3D Segy Data
1147141 OpenSpirit - Export Attribute maps might get unwanted extrapolation
1144533 OpenSpirit - Synchronization Undefined LMDs for horizons in existing project

Proportional layering produces discontinuous
1144529 Struct Mod - Layering layers in thin zones
1162898 Utilities - Volume Calculation Filter settings not always updated
1155783 Viz - Map Window crash map window when posting contact
Page Setting when plotting from the Well Section
1155575 Viz - Map Window Window
1152626 Viz - Map Window Petrel crash in Map Window
Problem When using the texture mode all the
1140889 Viz - Unspecified surface become Black
1154599 OpenSpirit - Export Not able to export a new well to OpenWorks
1161919 OpenSpirit - Export New exported Horizon forget its OSP key
Need to post warning about checkshots with non-
1149638 OpenSpirit - Import zero SRD reference datum
Petrel is reading amplitude information
1155129 OpenSpirit - Import inconsistenly
Exported a fault from Petrel->GF, made changes
911776 OpenSpirit - Import in GF, failed trying to reimport
1137563 Strat Mod - Well Correlation Zone thicknesses not calculated for particular well
Layering process appear to collapse cells with
1135928 Struct Mod - Layering toggle to do so disabled
extremely slow read-in of well deviation file if well
1146187 Import - Well Data tops are present
Import of checkshots from deviated wells with
1142517 OpenSpirit preferred surveys in GF -
Petrel 2005 Page 48

General Intersection Zone Transparency doesn't
1118572 Viz - 3D View work
Petrel does not export fault properties when they
1148872 Export - Eclipse are in a folder
462351 Import - Well Data DLIS and LAS Loaders fill memory
OSP_Workflow: Fault export to SeisWorks does
911822 OpenSpirit - Export not work
OSP_Workflow: Get error moving tops to
911613 OpenSpirit - Export OpenWorks
OSP_Workflow: Copying tops doesn't clear OSP
911612 OpenSpirit - Export keys
OSP_Workflow: Well Tops will not transfer from
911534 OpenSpirit - Export Petrel to GF
When importing data from GF/OW to Petrel,
910967 OpenSpirit - Import difficult to know status of transfer.
OSP_Workflow: Boreholes have different last
911689 OpenSpirit - Synchronization modify dates when they shouldn't
1153825 Other - Unspecified Problems with paper size on large scale plotter
1147887 Plotting Crash when negative number in Font size world
1147325 Plotting Color problem when plotting seismic attributes
SIS - modeling fails when using Gaussian
1151770 Prop Mod - Facies Modeling variogram from Data Analysis
Mispositioning of gridlines when showing 3D
1155784 Strat Mod - Well Section property as track
1153242 Utilities - Train Estimation Filter not working for Train Estimation Model
1155630 Viz - Well Section Window Block function output in a Log Editor is incorrect
Issue ID Component Description
Fixed numerous issues MAPAXES coordinate
1122364 Export - Eclipse
transformations on export.
Eclipse fault data export now works from a grid
copied from a portion of another grid
Petrel now exports fault properties when they are
in a folder
1150800 Export - Simulation Data
transformations on export.
Export to RESCUE file now includes all well traces
1138771 Export-RESCUE and the active local grid set. Import of this data is
NOT supported.
290172 Import - 2D Grid Import of binary CPS3 files is now supported.
Import - 3D Grid - All
1159640 Fixed error when loading Open RMS file
Formats
Grids from all sources are unit converted on
1153061 Import - CMG
import if required
Simulation results can now be imported under any
908835 Import - Eclipse
core system license
Fixed problem loading LGRs from grid with split
layers
Petrel 2005 Page 49

Resolved problem with loading foramtted
summary output from simulators
A bug that prevented Petrel reading an INCLUDE
1143204 Import - Eclipse file within an INCLUDE file in the keyword editor
has been resolved.
Fix loading of INIT files to ignore SEQNUM
462994 Import - Simulation Data
keyword.
1144560, The option to turn of auto-detect of faults when
Import - Simulation Data
1139391 importing a grid has been re-enabled.
Importing streamlines onto a grid no longer
applies unit conversion to the target grid as well as
1144261 Import - Streamlines
the imported streamlines. Previously, this cause
the grid to shrink on repeated imports.
The internal origin of a grid is now set on import
from the OPF file. Streamlins subsequently
1144329 Import - Streamlines
imported ontot he grid should no longer be
displayed miles away from the grid.
A problem in the export of FAULTS keywords for
Prop Mod - Fault Prop models with pinched out layers, which caused too
462854
Modeling many layers to be included in the export, has been
resolved.
Prop Mod - Fault Prop Fixed calculation of transmissibility multipliers
1122101
Modeling when fault perm zero
Fault property analysis now allows a blank or
undefined value to be specified for some or all
Prop Mod - Fault Prop
1143705 fault transmissibility multipliers (TM). Any
Modeling
TM=undefined will not be written out to the
simulator.
Prop Mod - Fault Prop Transmissibility multiplier export now includes
1148471
Modeling threshold pressure controls for ECLIPSE100
The 3DSL streamline simulator truncates long well
names to 8 chars (as expected by Eclipse format)
462884 Simulation-3D Results but does not check for uniqueness of resulting well
names. Petrel now checks for duplicate well
names on import and issues a warning.
An extra point is added to wells imported from
ECLIPSE/FrontSim restart files so that they show
1128732 Simulation-3D Results
above the reservoir. We recommend, however,
the the original deviation paths are loaded instead.
Requesting 3D results from ECLIPSE300 will now
462657 Simulation-Define Case always request saturations; previously, the
simulator default of only compositions was used.
Problems with well and completion dimensions in
1121163 Simulation-Define Case
restart cases have been resolved
When a case is copied, user keyword edits are
preserved
All exported simulation files are now named in
1146490 Simulation-Define Case upper case, consistent with the default for
ECLIPSE on UNIX/Linux systems
A warning message is now generated inthe log
Simulation-Define Case -
462790 window if a well is not written out because no valid
Schedul
diameter is specified for its perforations
ECLIPSE 100 2005a_1 more rigorously checks
Simulation-Define Case - that groups do not contain a mixture of wells and
462898
Schedul groups. Petrel now writes the WELLDIMS keyword
consistent with the new rules
Petrel 2005 Page 50

Wellbore radius units are now converted correctly
463349 when importing event and tubing files into projects
Schedul
set to Field-UTM units
Unit conversion problems with well conection
1136323 factors when simulation units are customized
Schedul
relative to the project units have been resolved
When Petrel is unable to update a user edited
keyword, Petrel now writes a message to the
Simulation-Define Case - message log and carries on. Previously, it would
1143524
Schedul stop exporting the case or issue an error
message, preventing use of the PRocess
Manager on keyword editied cases.
Normalization by %age of the observed data is
now donw on a vector type basis, rather than
Simulation-History Match
463149 individual vector basis. This is now consistent
Analysi
behaviour with the alternative absolute option.
Users should expect significantly different results.
Matches between observed PRESSURE data and
Simulation-History Match simulated WBP, WBP4, WBP5 and WBP9 vectors
1154068
Analysi (1, 4, 5, & 9 cell averages respectively) are now
calculated automatically if the data is present
In the process manager, the local grid process
462860 Simulation-Local Grids command now honors "Use 3D grid" command.
Prviously, it used the active grid.
1125776 Simulation-Local Grids Local grid export to VIP is now supported
Simulation-Make Flow BHP reference detph can now be set as a
463147
Control secondary constraint on a well
Simulation-Make Flow The user can now edit the preferred phase when
463208
Control the control mode is BHP or THP
Simulation-Make Flow WELPI and WPIMULT now available from the
1114479
Control Constraints tab
Simulation-Make Flow User can now control whether report dates are
1130900
Control added when the rate chagnes to/from zero
History flow controls dependent on observed data
that has been deleted now show this on the input
Simulation-Make Flow
1135276 tree. The flow control process allows you to
Control
set/change the observed data set on existing flow
controls.
Simulation-Make Flow
1146489 Wrong detection of well radius errors
Control
Simulation-Make Flow Wells are now SHUT in ECLIPSE when their
1158661
Control observed flow rate goes to zero.
Flow controls using monthly reporting will now
correctly use the last day of the month, instead of
1140263, Simulation-Make Flow getting stuck on the 28th after the first February
1139775 Control 28th was written out. An issue which corrupted
flow controls used from the process manager has
been fixed
Now correctly analyses contact set to make the
462368 Simulation-Make Fluid fluid region property when zones within a segment
have different contacts
It is now possible to make 'general contacts' in the
Make Contacts process called 'Pressure' and
1141974, Simulation-Make PVT 'Datum' and have them picked up by the Make
1122349 Table Fluid process to define intial conditions. This
allows pressure to be varied during an uncertainty
workflow.
Petrel 2005 Page 51

Template Region_ID should be used for ECLIPSE
Simulation-Property region properties, to avoid confusion between
1113955
Modifier Petrel's 0-based discrete properties and
ECLIPSE's 1-based regions
Memory requirements when displaying
462342 Simulation-Streamlines streamlines have been dramatically reduced,
avoiding out of memory crashes.
1118145 Simulation-Streamlines transformations on export, particularly adressing
streamline import
Unit conversion issues for streamline import to
1127558 Simulation-Streamlines
Field-UTM units have been resolved
462396 Simulation-Summary Data Crash on editing line style resolved
Summary data from WOPRH and WOPR etc.
vectors now get different line styles. Note
however, that the preferred workflow is not to use
462569 Simulation-Summary Data
the WOPRH vectors, but instead used the
observed data and flow control data inside Petrel,
reducing duplication
The summary calcualtor now works with simulator
aquifer results
Segment or connection summary vectors can now
be loaded and displayed fromt eh results tree
The summary calcualtor, which was missing from
the original 2004 release, is reinstated
The summary calculator overwrote imported data
when you dropped an imported case into the
1136469 Simulation-Summary Data "destination case" field. It now correctly creates a
"calculator" simulation and puts the derived result
in there.
A problem that prevented user edits to the axis
ranges in functions has been resolved.
Closing secondary project no longer deletes
462858 Simulation-Unspecified
simulation data in primary project
Order of user/generated keywords is now
1146472 Simulation-Unspecified
honoured in all sections
1152471 Simulation-Unspecified Can now create FrontSim restart simulation case
Petrel now uses the ECLVER environment
1160443 Simulation-Unspecified variable to determine the default version of the
simulator to run.
Upscaling - Scale Up A crash in IJK upscaling due to memory limitations
1142181
Zones has been resolved.
Ensure unit consistency with the chosen project
1141742 Viz - Streamlines unit system where Template's units have not been
customized;.
Unit conversion and local/global coordinate
transformation of imported streamlines has been
1143079 Viz - Streamlines
corrected. Streamlines should no longer be
displayed miles away from the grid.
It is now possible to use a property other than time
462524 Viz-Results Tree as the x-axis in a function window when plotting
data from more than one case
Export of Summary, Observed and FlowControl
462865 Viz-Results Tree data is now possible from the results tree by right
mouse button click on the dynamic data node.
Petrel 2005 Page 52

Hardware Recommendations
The time that you as a user spend working with Petrel far outweighs the cost of many high-
end workstations. If you are going to be using Petrel for either geophysical, modeling or
simulation workflows, it is our recommendation that you purchase a fully featured
workstation you can afford.
At SIS we are constantly testing the latest hardware available from major suppliers to ensure
that Petrel both functions as expected, as well as utilizing this hardware as completely as
possible. You minimize the chances of encountering unforeseen issues by using branded
solutions such as those from HP, Dell, Nvidia.
Petrel will run on most PCs with Windows without the need for HW modification..
However, to provide the best user experience we recommend the following:
Recommended Hardware Specifications
Processor Intel or AMD 3 GHz ++ (or equivalent)
Internal Memory 2.5 GB (Win 2000 + XP32) and 4.5 GB (Windows XP 64)
Graphics Card 256 MB OpenGL compatible
Operating System Windows 2000, Windows XP, Windows XP x64
Minimum Hardware Specifications
Processor Intel or AMD 1 GHz
Internal Memory 512 MB
Graphics Card 64 MB OpenGL compatible
Operating System Windows 2000, Windows XP, Windows XP x64
Processor(s)
Processor speed is mostly influential when it comes to large CPU intensive tasks such as
volume calculations, property calculations, upscaling etc. The processor also feeds the
graphics board with information so the story is not quite so straightforward. The minimum
requirement processor might be ok for simple Petrel usage, but we do recommend going for
the highest specified PC available. Petrel does not fully utilise many processors, but there are
definitive advantages to using a dual core or a 2-CPU machine. The second CPU is simply
used for other system activities. Petrel has been tested on Single, Dual and Dual-core
processor systems.
A 64-bit processor is needed to run Windows XP 64-bit. Intel Xeon processors and AMD
Opteron processors are suitable candidates.
Petrel 2005 Page 53

Internal memory (RAM)
In a 32-bit application (e.g. Petrel 2005) on a 32-bit operating system (OS) (e.g. Windows
XP) you can access 2 GB of memory per Application.
Petrel 2005 has been commercialised on Windows XP 64-bit operating system. That means
you can run the normal 32-bit Petrel application on the 64-bit OS with no extra installation
needed. XP64 gives each 32-bit application access to additional 2GB of memory, increasing
the accessible memory for Petrel to 4GB.
Due to OS memory fragmentation, the application can only access 1GB continuous memory
on XP 64 and 700MB on XP 32. (No calculations were done on Windows 2000). Also See
“32bit Compatibility Mode on 64bit Windows”
For most datasets 512-1024 MB of internal memory is sufficient to run Petrel, but with larger
datasets, big seismic models or big eclipse runs it is advisable that you install the maximum
your OS can access per application. Also allow a 512 MB overhead for your OS and other
applications.
Graphics cards
Choosing the right graphics card for your computer is important to ensure that Petrel
performance is maximised. Typically a user will see substantial differences between low- and
high-end cards when using large 3D grids, or when performance seismic volume rendering.
Graphics card performance is dependant on several factors outside the control of
Schlumberger. Corporate PC OS images, drivers and board manufacturers all affect graphics
performance.
The following cards were used during the Petrel 2005 testing cycle. Grouping is based on
user feedback.
Top-end cards
Manufacturer Processor Max. Memory PC Type Architechture
nVidia Quadro FX 256 Laptop PCI Express

go1400
nVidia Quadro FX 512 Workstation PCI Express

4500
Mid-end cards
nVidia Quadro FX 128 Laptop AGP

go1000
nVidia Quadro FX 256 MB Workstation PCI Express

3400
ATI FireGL 7100 256 MB Workstation PCI Express
Petrel 2005 Page 54

ATI Radeon 256 MB Workstation PCI Express
X850XT
Low-end cards
nVidia Quadro FX 128 MB Workstation AGP

1100
nVidia Quadro FX 128 MB Workstation PCI Express

1400
Seismic module HW recommendations

When using the geophysics module to view large 2D lines and big 3D surveys, and when
using the volume rendering feature we recommend using a graphics card with at least 256
MB memory. In addition a fast hard drive (e.g. SCSI drive) will increase the read speed of
seismic volumes. It is also advisable to install as much memory as your operating system
permits.
PC hardware
Under is a list of PCs Petrel is tested on. Note this is for reference only and does not mean
any official certification. Grouping of systems is done qualitatively based on the impression
during testing.
High-end systems
PC brand Type Processor Speed RAM Graphics GPU
card RAM
Dell 670 64 bit 2*Xeon 2.8 GHz 4 GB Nvidia 256 MB

Workstation Quadro PCI
FX 3450 Express
x16
Dell M70 Laptop Pentium M 2.13 2GB Nvidia PCI

GHz Quadro Express
FX
go1400
HP xw9300 64 bit 2*Opteron - 4 GB 2x Nvidia 512 MB

Workstation Workstation Quadro
PCI
FX 4500
Express
x16
Petrel 2005 Page 55

Mid-end systems
PC Type Processor Speed RAM Graphics GPU
brand card RAM
Dell Workstation Xeon 3.06GHz 3.5GB Nvidia 128 MB

Precision Quadro FX
AGP
650 1000
Dell M60 Laptop Pentium M - 2 GB GeForce4 PCI

Ti 4200 Express
HP Workstation 2*Xeon 3.2 GHz 2 GB ATI 256 MB

xw8200 FireGL PCI
7100 Express
HP Workstation Intel 2x 3.2 3.5 GB Nvidia 128 MB

xw4200 Pentium D GHz Quadro FX PCI
1400 Express
Low-end systems (not recommended for big Petrel projects)

PC Type Processor Speed RAM Graphics GPU RAM
brand card
Dell Workstation Xeon 2.4 GHz 2.5 GB Nvidia 128 MB

Precision Quadro AGP
450 FX 1100
Dell Laptop Intel 1.7GHz 2 GB ATI 128 MB

Latitude Pentium M Mobility
600 Radeon
9000
Known Issues
Core & Modeling
• Plotting canvasses incorporating transparent polygon fill to hardcopy is dependent on
whether the selected printer supports blending. If your plotter does not support this
feature transparent polygon fill will be drawn solid. The window may be exported to
another Windows application and plotted from there. (This workaround is subject to
the issue below.)
• Exporting plotting canvasses incorporating transparent polygon fill to emf may be
dependent on graphics driver version. Older graphics drivers may draw the
transparent fill in white, instead of the colour selected in Petrel.
• Flattening on well tops may give undesired results if the well section includes wells
with missing tops (1163547).
Petrel 2005 Page 56

• Zone log generation may fail if a well exits the stratigraphy and re-enters it via faults.
It is recommended that users qc zone logs in areas of high structural complexity.
• No zone log is generated for the zone after the last stratigraphic top. User must insert
dummy well top to complete the zone log to TD for use in well correction.
• Zonelog creation now assumes no erosion unless specified on the well top settings.
Where missing zones are not associated with erosional well tops the zones will be
collapsed down instead of up. It is recommended that users qc zonelogs, especially if
the “Adjust for missing well tops” option has been used
• The new convert case operation does not convert the schedule or summary sections.
The converted case will contain duplicate or inconsistent keyword combinations: the
user must open the keyword editor on the converted case and resolve these conflicts
by removing the redundant original keywords, which will be coloured black, before
the simulation will run. Assignment of multiple saturation functions, fluids and/or
initial conditions to regions is also likely to be incorrect and should be checked in the
Define Simulation Case process. See the online help for more details.
• Editing well tops may invalidate relative well completions.
If your well completions (casing, perforations, etc.) are specified with their depths
relative to a marker in a tops set, and you delete a well or a horizon or insert a horizon
into the tops set, the internal calculation of completion items’ positions from relative
depths may be corrupted. This will show up in a well section view and in the
connections exported to the simulator. There are two workarounds. 1) Before making
such a change to the tops set, right mouse button the global completions folder and
select ‘place all completions relative to datum’. Make the required changes to the tops
set, then do the same but choose ‘place completions relative to nearest top’. 2)
Alternatively, if the corruption does occur, simply save the project, close it, and
reload it. The depths used will be recalculated from the relative depths specified. Note
however that any completion items specified relative to a deleted horizon will have to
be redefined.
• The summary calculator does not work with observed data, flow controls, nor tracer
and component results from the simulator
• Summary data from R2SL or Avocet IAM cannot be loaded. This data uses an
extended form of well identifier (well@reservoir) which is not supported by Petrel
• Completions for horizontal or near horizontal wells only display reliably using MD
(measured depth) in the well section window. TVD, TVDSS, TWT, TVT and TST
may produce strange or blank displays.
• Loading of simulation results is slow compared to FloViz or ECLIPSE Office
• Local grid properties do not display in the well section window
• The .max, .min etc. functions in the 3D property calculator do not work correctly
when both the global and local grid(s) are included. Partial workaround is to use the
filter to operate on a single grid domain at a time.
• Constructing well paths from simulation results files produces strange results if wells
are highly deviated or multi-lateral. It is strongly recommended in all cases to load
Petrel 2005 Page 57

well paths from deviation surveys instead of leaving Petrel to reconstruct from
simulation results.
• IJK upscaling can result with some faults included in pillar gridding and some not.
Petrel 2005 Page 58

Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release Notes

Uploaded by

Copyright:

Available Formats

Petrel 2005 Release Notes

Trond Skjerven, Lead Product Champion – Petrel, January 2006

Integrated Structural Uncertainty

Petrel 2005 Page 1

Sr = Sbc + U1σ * Usgs

Sr = Surface realization to be used in Velocity Model, Make Horizon or Make Zones.

Icon to turn on uncertainty

Column to enter the 1std

Capture and Storage of Variables

Petrel 2005 Page 2

Variable values are

Option to recreate the case using the stored

Petrel 2005 Page 3

Seed setting for Petrophysical Modeling

Petrel 2005 Page 4

Multiple Histogram Plot for Sensitivity Analysis

Petrel 2005 Page 5

Launch sensitivity plot to visualize

Petrel 2005 Page 6

Petrel 2005 Page 7

New function “List()” allows for

Sample variables using Latin

Import a tab separated text file

Read variables from output sheet

Export active output sheet to a tab

Export active window as emf file*

When deployed in a loop, Latin

Define and store parameter values in an

Export a map of each horizon in the 3D

Petrel 2005 Page 8

Turn off Spin Animation

Improved surface rendering

Improved ZGY volume rendering

3D Well/Log Display Performance

Other Visualization Improvements

Petrel 2005 Page 9

Principal Component Analysis (PCA)

Utilities - Add Point Digitizing

Petrel 2005 Page 10

32bit Compatibility Mode on 64bit Windows

• Petrel 2005 will be supported on Windows XP 64 as a 32-bit application

Windows XP 64 gives each 32-bit application access to additional 2GB of memory,

Petrel 2005 Page 11

Petrel 2005 Page 12

What’s new with this release

Projects and sessions are

Individual item selection in

Petrel 2005 Page 13

Improved Connectivity and Logging

Petrel 2005 Page 14

Log Curve Mnemonics and Well Symbol Mapping

LogNamesToPropertyTypeCatalog.xml Controls Log Curve Mnemonic mapping

WellTypesToOpenSpiritWellSymbol.xml Controls the transfer from Petrel to

OpenSpiritWellSymbolsToWellType.xml Controls the transfer from OpenSpirit to

Petrel 2005 Page 15

Other Open Spirit Improvements

Petrel 2005 Page 16

Prosource Results Manager Connection

Improved calculation of well path geometry in time domain.

Petrel 2005 Page 17

Petrel 2005 Page 18

The location of the tie point is under

Petrel 2005 Page 19