Petrel 2009.2 - Ocean - Schlumberger

Schlumberger Public 

Petrel 2009.2 

Release Notes 

1


Copyright Notice 

Copyright 1998 - 2009 Schlumberger. All rights reserved. 

No part of this document may be reproduced, stored in a retrieval system, or translated in 

any form or by any means, electronic or mechanical, including photocopying and 

recording, without the prior written permission of Schlumberger Information Solutions, 

5599 San Felipe, Suite 100, Houston, TX 77056-2722. 

Disclaimer 

Use of this product is governed by the License Agreement. Schlumberger makes no warranties, 

express, implied, or statutory, with respect to the product described herein and disclaims 

without limitation any warranties of merchantability or fitness for a particular purpose. 

Schlumberger reserves the right to revise the information in this manual at any time without 

notice. 

Trademark Information 

*Mark of Schlumberger. Certain other products and product names are trademarks or 

registered trademarks of their respective companies or organizations . 

This software uses the FreeImage open source image library. See 

http://freeimage.sourceforge.net for details. 

FreeImage is used under the FreeImage Public License version 1.0. 

2


Contents 

Petrel 2009.2 ................................................................................................................................... 1 

Release Notes .............................................................................................................................. 1 

Copyright Notice .............................................................................................................................. 2 

Disclaimer ........................................................................................................................................ 2 

Trademark Information ................................................................................................................... 2 

What's new in Petrel 2009.2 ........................................................................................................... 4 

Software Download ......................................................................................................................... 5 

Geophysics ....................................................................................................................................... 6 

Geology ............................................................................................................................................ 6 

Geological Modeling ........................................................................................................................ 6 

Uncertainty & Optimization ............................................................................................................ 6 

Petrel Reservoir Engineering ........................................................................................................... 7 

Introduction ............................................................................................................................. 7 

Support for model initialization in Intersect ............................................................................... 8 

Results Tree Navigation Enhancements ...................................................................................... 9 

Development Strategy ............................................................................................................... 10 

Separator Definition .................................................................................................................. 13 

Petrel plug-ins for 2009.2 .............................................................................................................. 14 

Petrel Data in Context 2009.2 Plug-In ....................................................................................... 14 

OpenSpirit 2009.2 Plug-in.......................................................................................................... 14 

System Requirements.................................................................................................................... 15 

Petrel 2009.2 System Requirements ......................................................................................... 15 

Petrel 2009.2 Seismic Server System Requirements ................................................................. 15 

Ocean ............................................................................................................................................. 16 

Core and Geology – Known Issues ................................................................................................ 17 

Geophysics – Known Issues ........................................................................................................... 19 

Uncertainty and Optimization – Known Issues ............................................................................. 20 

Reservoir Engineering – Known Issues .......................................................................................... 22 

Core and Geology – Resolved Issues ............................................................................................. 24 

Geophysics – Resolved Issues ........................................................................................................ 26 

Reservoir Engineering – Resolved Issues ...................................................................................... 31 

Petrel - system crashes fixed by Microsoft hotfix. ........................................................................ 33 

3


What's new in Petrel 2009.2 

The 2009.2 release of Petrel* seismic-to-simulation software brings to the petrotechnical 

desktop a host of improvements that have been built upon the earlier 2009.1.1 release. Note 

that this is a major release - meaning that 2009.2 will install in parallel with any pre-2009.2 

Petrel installations. Approximately 200 issues have been fixed in this release. 

After receiving many requests for full 64-bit support on XP 64, we are pleased to announce that 

this is now available with 2009.2. Petrel now runs 64-bit on both Windows® Vista 64 and XP 64. 

Note that 32-bit compatibility mode on XP 64 is no longer supported. 

The OpenSpirit plug-in, created and owned by OpenSpirit Corporation, is ready for use with 

2009.2. See the OpenSpirit section for more details. 

The Petrel 2009.2 release will be delivered as a download only. Note also that the download will 

only be available through the SIS Support Portal to maintenance paying customers. 

(http://support.slb.com) For security reasons, the old completely public Petrel download site will 

now be closed. See the Software Download section for more details. 

Please note that any Petrel projects saved from 2009.2 are not backwards compatible - they 

cannot be opened with earlier releases of Petrel. 

4


Software Download 

The Petrel 2009.2 release will be available as an online software download only. There will be no 

hard media produced. A change in the download system has also been made - Petrel will no 

longer be available via a public internet download site; but will be available via the Support 

Portal to registered customers. 

A user account is required on this portal - if you do not have one, please visit the website and 

choose the option to Register. (As shown below) 

5


Check for software update 

When running Petrel 2009.1 or 2009.1.1, if you choose to run a Check for software update as 

shown below, you will be directed to the Support Portal login page. Enter your user credentials 

and, when successfully logged in, you will be able to download Petrel 2009.2. 

Geophysics 

No new features in this release. 

Geology 


Geological Modeling 


Uncertainty & Optimization 


6


Petrel Reservoir Engineering 

Introduction 

The purpose of the 2009.2 release of Petrel Reservoir Engineering is to support Intersect 

simulation workflows. Intersect is the Schlumberger next generation reservoir simulator 

constructed under an alliance program with Chevron. The first commercial release of Intersect 

(version 2010.1) is expected at the end of November 2009. A huge effort has been made to 

ensure that Petrel 2009.2 will be able to support Intersect 2010.1. However, as Intersect will still 

be undergoing beta testing when Petrel 2009.2 is commercial, there may be issues of 

incompatibilities arising at a later stage. Unless these issues are critical, we plan to resolve them 

in the Petrel 2010.1 version to be released early 2010. 

Petrel users will need to install a separate plug-in to enable Intersect workflows. The plug-in will 

be deployed with Intersect. The Petrel-Intersect plug-in will allow users to define and run 

Intersect simulation cases. The plug-in extends the Define Simulation Case process and provides 

access to the Intersect simulator through the simulator selection drop-down menu. Unlike 

ECLIPSE, Intersect does not use a keyword interface for model input. In place of the keyword 

editor, the Petrel-Intersect plug-in provides the Intersect Command Editor (IXCE) tool. IXCE 

provides access to Intersect features that are not available through the Petrel UI. Overall, the 

user experience conducting simulation workflows remains the same. Detailed description of the 

Petrel-Intersect plug-in, IXCE will be provided with the Intersect documentation. 

Several new developments and enhancements introduced in Petrel 2009.2 related to Intersect 

support are described below. Some of these enhancements can also be useful for ECLIPSE and 

FrontSim workflows. 

7


Support for model initialization in Intersect 

Intersect requires that the simulation grid and related properties (for example, cell-to-cell 

connections, transmissibility, pore volumes, etc.) are completely specified externally. This input 

is provided by Petrel, using the generic-simulation-grid (GSG) format. 

Grids with local grid refinements are processed to remove the global-local hierarchical 

relationship, non-neighbor connections across faults or with aquifers are processed and 

provided to Intersect. Equilibration information is provided to Intersect from Petrel. Likewise, 

3D simulation results need to be post-processed for visualization. All this is done automatically 

for the user by Petrel. 

Warning: Loading results (initial and recurrent grid properties) of an Intersect simulation into an 

existing project purely for the purpose of visual analysis is not supported. Therefore, it is advised 

to conduct the entire Intersect simulation workflow from within Petrel to avoid inconsistencies 

in results loading and visualization. 

8


Results Tree Navigation Enhancements 

A target workflow for Intersect is reservoirs with large number of wells. To improve the handling 

of large number of wells, saved searches and folder organization of wells in the Results tree has 

been implemented. The Results tree can be filtered and the active saved searches on the Input 

tree can be applied to the Results tree. The user can organize wells on the Results tree in a 

folder hierarchy as done on the Input tree. The actual organization is done on the Input tree and 

when applied, the Results tree inherits the folder structure and organization. Petrel will report 

any ambiguities if these exist. 

9


Development Strategy 

The Make Development Strategy now supports the Intersect simulator. Field management logic 

(well, group controls, constraints, etc.) in Intersect is handled by a distinct module called 

Intersect Field Management (FM). 

(1) Rules 

Several new rules have been introduced, while several existing rules have been made Intersect 

FM compatible. Some of the new rules are specific to Intersect FM. Note that some existing 

ECLIPSE/FrontSim rules are not supported by Intersect. By selecting the appropriate simulator, 

Petrel will filter down the list of available rules to reflect the simulator(s) selected. 

Historical Strategy Rules 

Intersect 

ECLIPSE 

10


Prediction Strategy Rules 

Intersect 

ECLIPSE 

11


(2) Rule Validation Enhancements. 

The logic used to validate rules containing parameters that are not supported by a specific 

simulator has been improved. A new rule state "Valid with Warnings" is provided. The icon and 

text for such a rule on the Strategy tree is colored blue. 

(3) Enhancements to Development Strategies UI 

Targeted drag/drop of wells/linked folders/well folders within and between well folders. 

Targeted drag/drop of wells within groups (i.e., the drag well is dropped immediately below the 

selected well). Targeted paste of wells/linked folders/well folders. Similar logic is applied to that 

for drag/drop as to exactly where the item is pasted. This targeting is also supported for the 

Replace functionality for well folders. Targeted addition of new wells/linked folders/well 

folders/groups to the strategy tree. 

12


Separator Definition 

Single- or multi-stage Separators can be defined using the new Separator modeling process in 

Petrel. When the separators are created, they stored on the Input tree. Separators can be 

imported as part of the fluid model or created when existing ECLIPSE simulation data decks are 

converted to a Petrel case. The imported separators can be edited using the Separator 

modeling process. 

The separators are associated with a field or region fluid-in-place separators from the Define 

simulation case process. Separators are associated with wells using the Development strategy 

process and the new Well separator rule. 

13


Petrel plug-ins for 2009.2 

Petrel Data in Context 2009.2 plug-in 

The Data in Context plug-in works with Petrel to provide the ability to quickly locate information 

using the search context (such as user profiles, project location, and objects) provided by Petrel 

to retrieve the most relevant information pertinent to your project. 

Data in Context provides you with an instant view of all the relevant data within the context of 

your project area, within your geographical area of interest, and within the information with 

which you are working. By comparing the geographical and contextual proximity, you can 

quickly see new relevant data, and use it to make better and more informed decisions. 

You can refine your information search using the following features: 

• Spatial proximity—Enables you to search for data in a specific geographical area of 

interest. 

• Object context—Enables you to search for information based on the object context 

defined in a Petrel project. 

Once the relevant data is retrieved, you have several different viewing options in which to 

display the results, such as a map, a timeline, or a list. 

From the views available, you can select relevant data and save it for future use, or send it to E- 

Mail, KML (for use in Google Earth®), or Microsoft® Excel® spreadsheet. 

New Features Petrel Data in Context 2009.2 includes the functionality as Petrel Data in Context 

2009.1, but is compatible with Petrel 2009.2. 

OpenSpirit 2009.2 Plug-in 

The new plug-in from OpenSpirit is currently in the closing stages of its commercialization cycle 

and will be available shortly for use with Petrel 2009.2. 

Petrel's existing OpenSpirit links will continue to function with this release. Petrel 2009.2 has 

been commercialized using OpenSpirit 3.1.4. 

14


System Requirements 

Petrel 2009.2 System Requirements 

This document outlines the hardware (HW) and operating system (OS) requirements for Petrel 

2009.2. To ensure that Petrel functions and performs as expected, we are constantly testing the 

latest hardware available from major suppliers, as well as optimizing it for maximum 

performance. In our attempt to minimize unexpected problems and costs, we tend to use 

branded solutions, such as those offered by HP, Dell, AMD/ATI and nVidia. However, we do not 

exclude hardware from other vendors. 

Petrel 2009.2 Seismic Server System Requirements 

The Petrel Seismic Server is a cluster-based visualization, interpretation, and attribute analysis 

tool. It represents a cost-effective way for rapid prospect analysis and working with mega survey 

seismic over several hundred gigabytes in size. This document outlines the system requirements 

for the Petrel 2009.2 Seismic Server version. The Seismic Server admin utility and ZGY utility is 

not covered by this document. Petrel is the front-end application for accessing the Seismic 

Server. See the Petrel 2009.2 System requirements for details of the Petrel system needs. To 

ensure that the server functions and performs as expected, we are constantly testing the latest 

hardware available from major suppliers, as well as optimizing it for maximum performance. In 

our attempt to minimize unexpected problems and cost, we tend to use branded solutions, such 

as those offered by Sun, HP, IBM®. However, we also test on Hardware from smaller vendors 

such as Rackable Systems® and Vxtech. 

Please follow the link below to read the documents for Petrel 2009.2 System Requirements and 

Seismic Server System Requirements: 

http://support.slb.com 

Go to Product/Discipline -> Petrel -> Software Release Announcements 

15


Ocean 

Reservoir Engineering 

UI extensibility for plug-in reservoir simulators 

Uncertainty workflow API 

Well segmentation, liners, keywords 

Data analysis / modeling 

Data selection filters 

Correlation & function data 

Variograms 

Seismic 

Seismic bulk order of magnitude speedup 

Multithreaded seismic bulk access 

Surface bulk order of magnitude speedup 

Fault & fracture patches 

Multi-input seismic attributes 

Other Domain API 

Reference project tool awareness 

Improved points, surface & well data attributes 

UI and look & feel 

Well-known tools and modes toolboxes 

Settings, import/export & data analysis dialog launch 

Keyboard events 

Improved explorer tree control 

Insensitive processes 

Workflow editor folders 

Asynchronous task manager 

Other 

64-bit native 

16


Core and Geology – Known Issues 

Issue ID Short Description Long Description 

2419077 Problems with graphics in Vista can 

occur if the Aero theme is switched 

on. 

Turn off Aero by: Open Appearance 

Settings by clicking the Start button, 

clicking Control Panel, clicking 

Appearance and Personalization, clicking 

Personalization, and then clicking 

Window Color and Appearance. If the 

Appearance Settings dialog box is not 

displayed, at the bottom of the page, click 

Open classic appearance properties. In 

the Color scheme list, select 

Windows Vista Basic, and then click OK. 

2404177 Visualization problems on Well 

Fence in 3D. 

3D visualization of Well Intersection 

Fence. Sections of a fence that should be 

behind the front section appear in front. 

2300152 Problems loading some SIF files. The problem occurs because some SIF/TIF 

files contain a second log curve panel in 

the file with the same MD ranges as the 

first. If there is just one panel, the file will 

be loaded correctly 

2420604 Rotated 2D grid/surface produces 

incorrect volume using volume 

below surface. 

2418401 Reference Project Tool does not 

transfer well names when moving 

well tops created in Petrel into a 

working project without wells. 

2421477 US Feet not recognized by 

Reference Project Tool. 

Volumes can be different when using 

volume below surface with rotated grids. 

Calculated volumes decrease with respect 

to true volumes as a function of the 

rotation angle, resulting in zero volume 

and area in highly rotated surfaces. 

When creating well tops, if the user is 

using RPT to move these into an empty 

project, the well tops in the new project 

will be unlinked to wells and will have 

incorrect well names under the Well filter 

such as "Well 1", "Well 2", etc. If the user 

imports well tops into Petrel and move 

them to the same empty project, the 

proper well names will be remembered 

even though they are also not linked to 

any wells. 

When using the RPT to move data from a 

reference project into a new working 

project, the RPT does not recognize units 

as being in “US feet.” However, if the units 

are set as “US feet” inside the reference 

project when the units and coordinate 

system are copied into the working 

project, the units come across as “feet.” 

17


2398139 Checkshot (velocity data) missing 

after copy of wells. 

2411075 Workflow Editor functionality to 

generate Truncated Lognormal 

distribution with Latin Hypercube 

sampling gives wrong output. 

2386132 Images rotated when displayed 

textured on a surface. 

If the user creates a subfolder under the 

Well folder and move some of the wells 

into this new folder and then use 

Ctrl+C and Ctrl+V to make a copy of the 

new sub folder. For any of the wells in the 

"Copy new sub folder,” there is no velocity 

data (checkshots, sonic logs, etc.) listed in 

the Settings/Time tab. 

Truncated Lognormal distribution with 

Latin Hypercube sampling in the 

uncertainty manager gives wrong output. 

The functionality works properly without 

Latin Hypercube sampling. 

When an image is displayed as textured 

over a surface, the image gets rotated to 

align on an N-S direction. 

18


Geophysics – Known Issues 


2408726 Seismic Well Tie: Start time at top 

of sonic. 

Under the Datuming folder, the user can 

set the field for Two way travel time at the 

top of the sonic to blank. A blank field is 

not an allowed entry and can lead to 

wrong results. 

2357039 Velocity modeling: Border effects 

when generating an average 

velocity cube. 

2414417 Reference Project Tool - Transfer 

between projects with Coordinate 

Reference System created by 

OpenSpirit . 

The border effects are still present when 

generating an average velocity cube using 

the INC (user defined increment cubes) 

mode. The issue is fixed for cubes 

generated based on existing survey 

geometries (RES). 

The Petrel project CRS string created with 

OpenSpirit versions 2.9x are different from 

those created with OS 3.14 or later. Thus, 

it is possible to have two Petrel projects 

populated with data from the same OS 

source and have them seen by the RPT 

tool as having different CRS. This prevents 

data copy between the two projects. A 

work around is to set the project CRS 

created by OS 2.9x to NULL and then 

reconnect to the source via the 3.14 

version of OS and choose the CRS. 

19


Uncertainty and Optimization – Known Issues 


2370052 Case collections limitations Case collections are not yet 

supported by the History match 

analysis process, Export dynamic 

result data and Make volumetric 

report. Workaround is to convert to 

folder of cases. 

2370229 Uncertainty and Optimization 

process: Automatic variable 

initialization not performed 


process: Contact set used in Make 

fluid model process 


process: Number of layers in scale 

up structure 


process: Property calculator 

command detection 


process: Variables not autodetected 

from well top calculator 

2370224 

Uncertainty and Optimization 

process: Orthogonal Array sampler 

in sensitivity analysis 

Initial values cannot always be 

determined automatically for 

variables in some processes. The 

user will have to enter the base case 

value manually in the variables tab. 

If variables have been introduced in 

the Make contact set process and 

the same contact set is being used in 

the, this task may fail. Workaround is 

Make fluid model to add contact 

variables in the Make fluid model 

directly. 

Setting No of layers in the Scale up 

structure process to a variable in an 

uncertainty workflow does not reset 

the grid to the state it was before the 

run. Therefore, it is recommended to 

make a copy of the grid before the 

run. 

When dropping in the base case, the 

system may not recognize all 

calculations that were previously 

applied to a property. 

When typing a $variable into the well 

top calculator, this variable is not 

detected by the system. The 

workaround is to define a user 

variable with the same name in the 

variables tab. 

The Orthogonal Array sampler 

should not be used in sensitivity 

tasks. By variable: Only one variable 

is active at a time, so Orthogonal 

Array Latin Hypercube is equivalent 

to normal LH sampling. By process: A 

different number of variables may be 

active at a time, so it is not possible 

to specify a valid number of runs. 

20



process: Base case workflow update 

and performances 

2370228 Uncertainty and optimization 

process: Make fluid process not 

detected for imported fluid models 

Adding new steps to the workflow 

may impact on the execution 

performances, as all processes may 

then be automatically activated, 

even if not required. The 

workaround is for the user to change 

the command status to Disabled. 

If a simulation contains an imported 

fluid model, the make fluid process is 

not auto-discovered in the base case 

workflow. The workaround is for the 

user to drop in the Make fluid 

process manually. 

21


Reservoir Engineering – Known Issues 


2356514 Applying 1-D streamline filters to 3-D 

properties with local grids. 

There is a known issue with applying a 

1-D filter created on a streamline to the 

display of a 3-D property in the 3-D 

window, when the case which 

generated the streamlines contained a 

local grid refinement. In this case Petrel 

will not report an error and the filtered 

cells will be incorrect. 

2325247 Segment numbering – Well section 

window. 

The numbering of well segments as 

displayed and as exported could be 

different if the well path crosses 

inactive cells. When a simulation case is 

exported segments are uniquely 

defined so exported segment nodes are 

correct. 

2298250 Import of Schedule tubing file. Tubing imported from Schedule .TUB 

files that spans multiple wells is not 

imported correctly. Currently tubing 

ends at kickoff depth. 

2332101 Sector modeling with Local Grid 

Refinement. 

2370525 Fracture properties are not written 

when equal to matrix. 

Sector models created from Petrel with 

ECLIPSE 2009.1 or earlier that contain 

an LGR that crosses inactive cells (e.g. 

inactive layers or pinch outs) will report 

an error saying that the LGRs cannot be 

placed across the boundary. This is a 

known issue in ECLIPSE100 (Issue 

ID=2338600). Only ECLIPSE300 can 

handle this situation. 

When fracture array properties (grid 

tab and regions from the functions tab) 

are defaulted in Petrel, the user 

expects them to be the same as the 

matrix. However, Petrel does not write 

out the arrays for the fracture cells, and 

ECLIPSE does not copy them - it only 

does it for a limited set of GRID section 

properties, listed under the DPGRID 

keyword. 

2403814 LGRs in inactivated global grid cells. Under certain circumstances Petrel 

exports LGRs for inactivated global grid 

cells leading to errors during 

simulation. A workaround is to load the 

PORV array processed by the simulator 

(INIT file) and use it to filter out inactive 

22


2419353 Loading simulation results - LGR 

properties 

2374748 Well stimulation data not correctly 

processed to skin. 

2414453, 

2420726 

Intersect workflow only: Cannot view 

or load PLT or RFT results into Petrel. 

2425685 Intersect workflow only: Numerical 

aquifer datum depth is exported with 

incorrect sign. 

cells and redo the 'Make local grids' 

process to update the LGRs. This is an 

issue in 2009.1 as well. 

Run time loading of LGR results will fail 

if the Define simulation case process 

window is closed by selecting the OK or 

if the Apply button is selected. The 

problem can be worked around by 

selecting the close window(X) button 

instead. 

Petrel uses the default open hole 

diameter on the global completions 

setting instead of the specified well 

diameter to compute skin for 

stimulation events. A possible 

workaround is to re-specify the open 

hole diameter to be the same as the 

perforation diameter if all the 

perforations are of equal diameter. 

Petrel is not converting the Intersect 

cell numbering correctly when 

importing the RFT/PLT results from an 

Intersect simulation run. The RFT/PLT 

results can be viewed using ECLIPSE 

Office. 

This issue does not affect ECLIPSE 

simulations. 

Petrel is not converting the datum 

depths for a numerical aquifer from the 

Petrel convention of negative depths 

below sea level to the Intersect 

convention of positive depths below 

sea level. The workaround is to specify 

the depth as positive for numerical 

aquifers that will be exported to 

Intersect. 

This issue does not affect ECLIPSE 

simulations; the datum depths entered 

in Petrel for aquifers exported to 

ECLIPSE/FrontSim should follow the 

Petrel sign convention; they will be 

correctly converted. 

23


Core and Geology – Resolved Issues 


2404089 Displaying a k-layer higher than 

100 in a map window causes Petrel 

instability. 

When displaying a property in a Petrel 

window and then selecting a k-layer to 

view in the window (from the property 

settings); If the k-layer is higher than 100 

and the settings dialog is closed, Petrel 

become unstable. If Petrel is closed 

down and the project is reopened, 

displaying a property in a map window 

will make Petrel unstable. Issue fixed in 

Petrel 2009.2. 

2394207 Function window - crossplot of 

properties, raw logs filter still 

shows upscaled data. 

2398276 Deletion of many data points 

makes Petrel unstable. 

2401934 Saved Search automatically filters 

wells in Scale Up Well Logs 

2388084 Make horizons/zones - Poor 

results using Well adjustment in 

some cases. 

If you crossplot two 3D properties in the 

function window and activate the filter 

on the right side toolbar in order to look 

at the raw log data, you will see that the 

data is exactly the same as the upscaled 

data. Issue fixed in Petrel 2009.2. 

Make/edit polygon - When deleting data 

points from a large point set, the 

memory allocation is increasing very 

quickly; Petrel will become unstable 

above 1.5 Gig. Petrel Tools/Free memory 

does not improve the situation. This is 

caused by the undo/redo function. 

Multiple undo was added on pointsets, 

prior to that there was only one undo. 

Petrel stores a full copy of the pointset 

for each undo operation. Large pointsets 

will take up a lot of memory. Issue 

resolved by limiting the undo function to 

20. 

When a Saved search is used, it 

automatically applies to the Well 

Selection list in Scale Up Well Logs. 

When All is selected, the only the wells 

included in the Saved Search are used for 

the Scale-Up process. Can cause 

incorrect results any time a Saved Search 

is left on. Issue fixed in Petrel 2009.2. 

Wrong results obtained in Make 

horizons/zones process using "Well 

adjustment". The difference between 

the well tops and horizons were getting 

worse/bigger after well adjustment. This 

issue seems to occur only on some Pillar 

24


2397845 Reference Project Tool might be 

unstable when using spatial filter 

against reference project with 

checkshots. 

2394727 Error when pasting additional lines 

into deviation spreadsheet. 

2403133 Make log creates incomplete log 

along well. 

2370935 Minimum curvature interpolation 

gridding does not honor fault 

polygons. 

geometry, or steep horizons. 

When a background reference project is 

created from OpenWorks via OpenSpirit, 

it always sends the default checkshots 

for the wellbores. A standard practice to 

create user projects is to use the 

reference project tool and apply a spatial 

filter against the background project to 

filter the background project inside of an 

AOI, and then send this data to the 

working project. In 2009.1.1, when the 

background project has checkshots and 

the user applies a spatial filter against 

this project, the background project tree 

after filtering contains two well trees. 

The first with only the global logs as a 

child, and the second with all of the true 

wells as a child. When the user tries to 

perform a copy to their working project 

Petrel gets unstable. Issue fixed in Petrel 

2009.2. 

When updating the deviation 

spreadsheet by first adding additional 

rows, then pasting from an Excel 

spreadsheet, Petrel either freeze or 

receive an error message as follows: 

“Md array is not increasing”. Issue fixed 

in Petrel 2009.2. 

When moving a project with a 3D model 

with saturation from Petrel 2007 to 

2009.1.1 (32-bit); If you make a synthetic 

log in all wells of the project (and there 

are no logs in the project before creating 

the synthetic logs), Petrel makes the 

synthetic logs with "holes" along the well 

bore. This feature occurs mainly in 

horizontal wells. Issue fixed in Petrel 


Under Utilities->Make/Edit Surface, if 

you input horizon and a fault centerline, 

set geometry and select the algorithm: 

Minimum curvature interpolation, then 

the output surface does not honor the 

fault centerline. Issue fixed in Petrel 


25


Geophysics – Resolved Issues 


2349288 

2349290 

2349298 

Annotation of seismic survey in 2D 

and 3D window. 

Various issues concerning the annotating 

of 3D seismic surveys have been addressed 

(font size, annotation direction, 

annotation visibility when viewing survey 

from the side). 

2351547 

2362908 

Neural network probability and 

principal component cubes output. 

When using classification neural network 

on seismic cubes, it is possible to create 

probability and principal component cubes 

as additional output 

2374009 Volume Attributes: Petrel freezes if 

volume attributes are created on 

seismic cubes with volume 

rendering on. 

2378414 Genetic Inversion: Petrel crash due 

to increased number of hidden 

layers. 

2373337 Virtual Cropped Volume: The OK 

button does not close the dialog in 

the settings dialog under the 

Cropping tab. 

2383879 The new color table slows down 

the turning on and off of data 

items in the tree when there are 

active (3D) window(s). 

2401837 Surface Attributes: Offset 

parameter for local loop surface 

attributes. 

Volume visualization style option for 

virtual cubes is not available anymore. This 

mode triggers a full cube calculation of the 

attribute, making the virtual attribute non 

performing. 

The user is now presented with a message 

"Number of weights in Neural Network too 

large compared to number of learning 

samples" and the number of hidden layers 

can be adjusted as required. 

Now working as expected. 

Fixed in Petrel 2009.2. 

The horizon offset parameter for surface 

based loop attributes as set in the GUI was 

neglected. This has now been fixed. 

2392575 Memory fragmentation for 64-bit 

version when reloading project in 

the same Petrel session. 

The memory fragmentation is fixed. 

26


2398043 Seismic Interpretation corruption 

when project is saved on Samba 

mounted disk. 

Fixed. Note that this problem is only 

observed in certain version scenarios of 

Samba, network and operating system. 

2405900 Coordinate filter options. In the Project Settings dialog for 

Coordinate Systems, one can now also 

filter the list based on ESRI codes. 

2412045 Slow Reference Project transfer. Reference Project takes a long time to 

transfer data - message that it is 

computing derived data observed. This is 

resolved. 

2404704 Domain conversion fails when 

average velocity cube does not 

start at time=0 

Fixed. Now it is possible to have average 

velocity cubes, not starting at zero time, as 

input to the domain conversion process. 

2357039 Velocity modeling: Border effects 

when generating average velocity 

cube generation 

The border-effects problem is fixed for 

cubes generated as RES (picking up 

existing seismic geometries in the project). 

2370785 

2345940 

Velocity modeling: Problems when 

generating instant velocity cube. 

Issues with negative velocities and bulls 

eyes are resolved. 

2374496 Velocity modeling: Issues when 

generating average seismic velocity 

cube from velocity model when 

using welltop correction. 

2372339 Time logs and velocity logs are not 

properly generated when 

generated via the Output tab from 

"Create a velocity model" using an 

average velocity cube. 

2374496 Velocity logs not overwritten/ 

updated when the velocity model 

is rerun. 

In certain scenarios, the average velocity 

extracted from the velocity model contains 

extreme negative and positive values. This 

problem is resolved. 

Logs are now properly generated when 

they are toggled on in the Output tab in 

the Velocity model dialog. 

Now, a rerun of the velocity model will 

update the velocity logs with the new data 

and update the visualization. 

2372834 Velocity modeling: problem with 

Vo-k from Well TDR-surfaces. 

In certain scenarios, when changing an 

existing Vo-k velocity model, a message 

"Cannot find enough TDR data in the 

zone..." prevents the model from building. 

In 2009.2 the model will build, omitting 

27


the boreholes which have out-of-range k- 

values. 

2415744 Velocity modeling: Spike effects at 

well locations when using (v0-k) 

constants and correction surface in 

the Velocity model. 

2384887 

2411151 

Geobodies: Wellprobes hard to 

manipulate. 

2396065 Geobodies: Thickness property 

miscalculated for seismic horizons. 

Problem first seen in Petrel 2009.1, but is 

now fixed. 

The wellprobe thickness manipulator is 

changed. To increase/decrease the probe 

thickness: Activate the probe manipulator 

tool. Press the ctrl key and click on the 

probe using the left mouse button. Hold 

the left mouse button down while moving 

up/down on screen. 

There was an issue with the scaling of the 

thickness property. Now the thickness 

property is properly calculated. 

2411420 Geobodies: Freeze when picking 

multiple geobodies on the same 

horizon probe. 

Issue resolved in Petrel 2009.2. 

2402295 Geobodies: Units of the reported 

volume statistics not clear. 

Values are converted to and annotated 

with project specified volume and area 

units. 

2368436 Fault plane triangulation causes 

Petrel crash in certain scenarios. 

2398203 Ocean requires to set and get the 

seismic context associated with a 

fault polyline. 

Erroneous situations in the fault plane 

triangulation process are now captured 

and the user is presented with an error 

message window. The triangulation for 

this fault will be switched off. 

This is now implemented in both Petrel 

and Ocean. 

2379166 Performance of Interpretation 

Manager. 

Interpretation Manager is now performing 

as expected for large number of 

interpretation objects (faults and 

horizons). 

28


2393432 Survey Manager performance. Various improvements to the survey 

manager are implemented (performance, 

changing filters, switching windows) 

2379354 Petrel crashed when trying to 

perform autotracking on a 

calculator cube. 

2396273 Seismic Interpretation corruption 

after "Save As" operation. 

Performing a 3D autotrack operation on a 

calculator or virtual attribute cube is 

deactivated and a warning message is 

generated. The calculator or virtual 

attribute cube has to be realized to allow 

3D autotracking activities 

Issue resolved in Petrel 2009.2 

2396488 Error accessing the statistics of a 

seismic horizon after using Save 

Project, followed by Free Memory. 

Horizon gets a black cross. 

2368211 Multithreading event prevents 

save project from Workflow 

Manager while process runs. 

An error message "Trying to retrieve data 

for Seismic horizon 1 on the file... Cannot 

read the format on the file" is presented, 

and the horizon gets a black cross. The 

workaround was to reopen the project. 

Now this issue is fixed and the problem 

will not appear anymore. 

While running a SaveProject in a workflow 

which has multithread calculations going 

on, the workflow will not be interrupted 

by error message pop-ups. 

2362225 Seismic Well Tie: Wavelets 

overwritten by the Reference 

Project Tool (RPT) do not get 

correct status in RPT dialog 

window. 

2366898 Seismic Well Tie: Different 

Calibrated Sonic values when 

transferred by Reference Project 

Tool (RPT). 

2384389 Seismic Well Tie: Crash caused by 

clicking Print in the New wavelet 

viewer. 

2400194 Seismic Well Tie: Start time at top 

of sonic. 

Overwritten wavelets, like overwritten 

LogSets, will now get the correct status in 

the RPT dialog window. 

A wrong unit handling of the Seismic 

Reference Datum (so for SRD0) in the 

Sonic Calibration process caused values of 

Calibrated Sonic to differ. This is now fixed 

by proper handling of the value/unit pair 

for the Seismic Reference Datum. 

A standard print dialog is added which 

allows the user to select a printer. If no 

printers are available, the Print button on 

the dialog will be inactive. 

Start time at top of the sonic log is added 

where there are no checkshot survey data 

available in the project 

29


2400195 Seismic Well Tie: Extracted wavelet 

in empty Wavelet Extraction 

window. 

A time shift issue was fixed for extracted 

wavelets that were dropped in an empty 

Wavelet Extraction window. 

2392571 Seismic Rendering in 3D window. Display gets striped appearance when 

zooming in on a displayed section from a 

ZGY cube in the 3D window. This issue is 

resolved. 

30


Reservoir Engineering – Resolved Issues 


2385405 Export of LGRs in ECLIPSE keyword 

format 

Exporting a grid in keyword (.GRDECL) 

format using Models>Export>GRDECL in 

Petrel 2009.1 did not export the LGR 

keywords. This has been fixed in 2009.2 

2407428, 

2400642, 

2418648 

2205298, 

2386274 

2395794, 

2368933 

Coal Bed Methane Modeling Issues. 

Increased precision handling PVT 

properties to reduce simulator 

errors. 

Corrected export for simulation 

cases with multiple PVT and 

equilibration regions. 

2408553 Importing several PVT tables from a 

simulation keyword case/dataset. 

2411262 Loading production data using VOL 

file format 

2390240, 

2377858 

Problems with using historic 

(echoed observed) summary 

vectors. 

(a) The following ECLIPSE Coal Bed 

Methane option grid array keywords 

(COALNUM, GASCONC, GASSATC, 

MLANG, MLANGSLV, ROCKDEN) are now 

available for export on the Grids tab in 

the Define Simulation Case Process. 

(b) Fixed issues with extracting flux 

boundary conditions from CBM cases. 

a) Earlier very small values of oil-in-gas 

ratios (Rv) in input PVT tables were 

rounded off to zero essentially making a 

wet gas a dry gas and caused simulations 

to error. This has now been fixed. 

b) PVT properties export has been 

enhanced to avoid monotonicity errors 

caused by truncated numbers. 

Petrel was exporting PVT tables 

corresponding to equilibration regions 

(EQLNUM) and not PVT regions 

(PVTNUM) and setting the table 

dimensions (TABDIMS#2) to number of 

equilibrations regions. This has now been 

fixed. 

Earlier Petrel would load several PVT 

tables and sort them by name thus if 

more than 10 tables were imported table 

no. 10 actually became table no.2 and so 

on. This caused problems with matching 

PVT tables to imported regions. These 

issues are now fixed. 

Petrel was not consistently interpreting 

the *MISSING_VALUE when processing 

.VOL files. The problem is now fixed. 

a) There were issues with line plotting - 

accessing settings and display toggle, and 

b) and using these vectors in the dynamic 

data calculator. Issues have been fixed by 

not treating historic (echoed observed) 

vectors with a different identifies but as 

the same for other summary vectors. 

31


2417088 Output dynamic data to 

spreadsheet 

2400687 Creating aquifers caused Petrel to 

exit. 

2404423 Configuration error caused 

simulation launch error. 

2379893 Legacy ECLIPSE pre-post products 

launching. 

2389267, 

2422885 

Tensor upscaling issues. 

2378490 Segmenting wells with multi-level 

laterals. 

2406685 Consistent export of looped 

segments 

User defined Quantities (UDQs) can now 

be exported to an output sheet. 

Creating aquifers with top and bottom 

limits using contacts and surfaces caused 

Petrel to exit. This has now been fixed. 

Error in Petrel configuration files caused 

simulation launcher to fail. 

After a standard install EPP products 

(ECLIPSE Office, FloViz, Schedule, ...) 

failed to launch if the user did not have 

write access to the Petrel install 

directory. This problem is now fixed by 

using the particular Petrel project 

directory or a temp directory. 

a) Some weighting options relating to 

flow-based tensor upscaling were not 

correctly passed from the user interface 

to the upscaling algorithms, and tensor 

component selections were sometimes 

incorrectly reset after the upscale has 

been run. This resulted in incorrect 

results and an unsettling user experience 

when using these options. These issues 

are now fixed. 

b) The NTG and porosity weighting 

parameters were interchanged. Now 

fixed. 

Segmentation failed when a well had 

multi-level laterals, i.e. lateral kicked off 

from another lateral. This is now fixed. 

Petrel validation and export segment 

loops updated. ECLIPSE300 2009.1 

versions and later support loops. 

32


Petrel - system crashes fixed by Microsoft hotfix. 

Microsoft provides a hotfix that has proved to solve several issues with regards to XP 

32-bit system crashes when running Petrel. 

Several SMRs (2411716, 2346346, 2292952) regarding operation system crashes (blue screens), 

when working with Petrel (specific projects only), have been reported. These issues are all linked 

to XP 32-bit. 

The reason for why the system crashes is that Microsoft has a bug in the windows kernel. When 

we, in Petrel, draw filled triangles in 2D (property grids and smooth shaded contours on the Map 

window, seismic on the Interpretation window, properties on the Well section window etc.) it 

can corrupt kernel memory and take down windows. Vista 32/64, Windows Server 2003SP1, and 

Windows XP 64 bit ship with the fix. All earlier Microsoft OSs needs to be patched. The problem 

is not necessarily tied to screen drawing. For example, it may draw fine on the screen, but crash 

when printing, or if another application (for example, PowerPoint) reads an EMF containing 

triangles that were generated in Petrel. 

Microsoft has provided a hotfix, and after installing Windows XP-B912196-v2-x86-ENU.exe, 

which can be downloaded for free from the Microsoft web page 

(http://support.microsoft.com/kb/912196), all these issues were solved. No more blue screens 

to be seen. 

33

Petrel 2009.2 - Ocean - Schlumberger

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?