Release Notes

Landmark PetroWorks/LogEdit
PetroWorks/LogEdit 2003.12.1
Release Notes
Landmark/Asia Pacific Landmark/EAME Landmark/The Americas

11th Floor Menara Tan & Tan Hill Park South Building 1, Suite 200, 2101 CityWest
207 Jalan Tun Razak Springfield Drive Houston, TX 77042
50400 Kuala Lumpur Leatherhead, Surrey GU22 7NL P.O. Box 42806, Houston, TX 77242
Malaysia England U.S.A.
Tel: 011-60-3-2164-1121 Tel: 011-44 (0) 1372 868-600 Tel: 713-839-2000
Fax: 011-60-3-2164-1135 Fax: 011-44 (0) 1372 868-601 Help Desk: 713-839-2200
Help Desk: 011-61-8-9481-4488 Help Desk: 011-44 (0) 1372-868-686 Fax: 713-839-2169
Email: apsupport@lgc.com Email: eame_helpdesk@lgc.com Email: support@lgc.com
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Enhancements and New Functionality . . . . . . . . . . 4
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Command Menus (Launcher Bars) . . . . . . . . . . . . . 26
PetroWorks Family of Applications . . . . . . . . . . . . . 27
PetroWorks Software Notes . . . . . . . . . . . . . . . . . . 34
Special Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 41
R2003.12.1 Release Notes Page 1 of 48 September 2005

Copyright 2005Landmark Graphics Corporation

All Rights Reserved Worldwide
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by
Federal copyright law and by US Patents 6,765,570 5,570,106 5,615,751. No part of this publication may be copied or distributed,
transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any
means, electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:
Landmark Graphics Corporation

15150 Memorial Drive, Houston, TX 77079, U.S.A.
Phone: 281-560-1000
FAX: 281-560-1401
Telex: 750203 LNDMARK HOU UD
Internet: www.lgc.com
Trademarks
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, Asset Development Center, Asset Development Centre, Asset Performance, AssetView,
Atomic Meshing, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Manager, DataStar,
DBPlot, Decision Suite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView, DecisionSpace
Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace Nexus, DecisionSpace PowerGrid,
DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion,
DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3, DepthTeam Extreme, DepthTeam Interpreter,
Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Discovery Asset, Drill-to-the-Earth Model,
Drillability Suite, Drilling Desktop, DrillModel, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EDM,
eLandmark, Engineers Data Model, Engineer's Desktop, Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker, FG+,
FastTrack, FieldPlan, FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink,
GeoProbe, GeoProbe GF DataServer, GES, GESXplorer, GMAplus, GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS,
IsoMap, iWellFile, Landmark, Landmark and Design, Landmark logo and Design, Landmark Decision Center, LandScape,
LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth, MagicDesk, MagicStation, MagicVision, Make Great
Decisions, MathPack, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, OpenExplorer, OpenJournal, OpenSGM,
OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView,
Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, Power
Interpretation, PowerJournal, PowerModel, PowerSection, PowerView, Production Asset Manager, PRIZM, PROFILE, Project
Administrator, ProMAGIC, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx,
QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RTOC, Real-Time Asset
Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company, Real-Time Operations Center, Real
Time Production Surveillance, Real Time Surveillance, Reference Data Manager, RESev, ResMap, RMS, SCAN, SeisCube,
SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, Sierra, Sierra (design), SigmaView, SimResults,
SIVA, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks, StressCheck,
STRUCT, Surf & Connect, SynTool, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs The Oilfield
Workstation, TracPlanner, Trend Form Gridding, Turbo Synthetics, VIP, VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE,
VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Web OpenWorks, Well Seismic Fusion,
Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in
Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark
Graphics Corporation.All other trademarks are the property of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by
Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this
manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore,
this statement may not apply to you.

Introduction
The PetroWorks product family is a set of applications designed to offer the right solution for your
wellbore data requirements, from data management tools to advanced interpretation. Scalability
assures you of finding the right fit for your needs, without incurring unnecessary expense or
complexity. Because PetroWorks is a native OpenWorks product family, integration with other
Landmark products is exceptionally tight, enabling unprecedented productivity for petrophysicists,
log analysts, geoscientists, engineers, data managers, and others who deal with wellbore data.
For demanding wellbore data management requirements, the LogEdit product extends the
capabilities of the OpenWorks utilities by providing utilities especially designed for viewing,
editing, and quality-controlling wellbore data curves and parameters, including especially those
from well logs. As such, this product is not only a component of the Landmark scalable solution
for formation evaluation, petrophysics, and the broader wellbore data interpretation world, but is
also a component of a scalable data management solution.
For those needing basic interpretive capabilities for logs and other wellbore data, with seamless
integration to other popular Landmark products such as StratWorks, SynTool, and Z-MAP Plus,
PetroWorks Asset offers a perfect solution. In addition to the editing and data management tools
in LogEdit, it adds an extensive suite of interpretive tools such as crossplotting, mapping,
interpretive processing, environmental corrections, and many other functions.
PetroWorks Pro has all the features in PetroWorks Asset plus advanced user-programming, a
number of advanced interpretive applications, and a sophisticated graphical tool for managing well
completion information and integrating it with wellbore data plots.

Enhancements and New Functionality
Release 2003.12.1
The following enhancements to PetroWorks were made for R2003.12.1.
This PetroWorks release focused on usability and performance enhancements. The following areas
had the greatest change:
Performance is dramatically improved over the 2003.12.0.0 release when processing multiple
wells over stratunits. The more complex the stratigraphic column, the greater the performance
enhancement you will see. It is now possible to process hundreds of wells in seconds to a couple
of minutes. Performance enhancements are across all PetroWorks applications that process
stratunits such as Crossplot, Mathpack, Summation, Tabular List and the interpretation models.
LogEdit underwent a complete redesign of the main window and significant enhancements for
usability and to reduce the number of mouse clicks. Users now select editing and display
functionality via icons rather than pull down windows. New functionality includes:
Option to Show Edits Continuously allowing the user to see the edited curve as it is edited
rather than only intermittently
Improvements to Multiple Tie Line Depth Shifting
Improvements to Curve Splicing: it is now very easy to apply splices from one set of curves to
another set within a given well
Search / Filter capability for Well Templates
Tabular List underwent a complete redesign of well and curve selection windows going from
several pop-up windows to a single tabbed window. New functionality includes:
Option to write output to a comma delimited file that can be imported into a spreadsheet.
Sort wells by Well ID, UWI, Common Name, etc.
Search / Filter capability for wells, stratunits, and curves
Improved curve selection
Stratunit names no longer truncated in Report Viewer
Ability to turn on / off discriminators
Option to report statistics only

Crossplot underwent many usability changes in the previous release (2003.12.0.0). In this release
(2003.12.1.0) major improvements include:
Performance enhancements mentioned above
Histogram displays enhanced to make values and bars easier to read
Composite histogram overlay of all wells functionality that was removed in the 2003.12.0 has
been reinstated and the display enhanced
Other Changes:
Multiple Occurrences of a StratUnit: All applications that process over stratunits have been
changed to not list multiple occurrences of a stratunit if multiple wells are selected. This affects
Crossplot, Summation, Sensitivity, Tabular List, Log Export, and the interpretive models.
(This functionality was already in Mathpack 2003.12.0.0). For Example: When a single well is
selected, the multiple occurrence of stratunit Mineral City is listed as Mineral City<1>, Mineral
City<2>, Mineral City <3>. When multiple wells are selected, it is listed as Mineral City without
the occurrence number. (Note: Geofeatures are not considered to be multiple occurrences. For
example Mineral City stratunit with a different geofeature is listed separately: Mineral City:Fault
Block A, Mineral City:Fault Block B.)
Measurement System: All applications now initialize using the Measurement System set in
Project Status. The Depth Type widget has been removed from all applications expect for Curve
Utility. The documentation for Sensitivity and the interpretive models has not been updated to
reflect this change.
Release 2003.12.0
The R2003.12.0 release of the PetroWorks family of products was focused on significant usability
and functional enhancements.
The following applications had the most significant changes, and detailed in the list below.
Crossplot underwent a complete redesign of the data selection and configuration windows,
going from a large number of pop-up windows to a single tabbed window. This change
improves the efficiency of the entry of data to create crossplots, log tracks, and histograms.
Parameter defaults and interface behaviors were changed to make the creation of displays
easier and faster. Substantial new functionality was added in determining gradients and the
intersection of gradient lines, as for example, to determine fluid types and fluid contacts from
pressure data. Other new functionality was also added, mostly related to the display of overlays
on crossplots, and the plotting and regression of lines on crossplots. As a result of this work,
the Crossplot documentation has been completely revised.
MathPack had significant changes made to its functionality while retaining essentially the

same interface. MathPack now honors the resample ability of log curve data; that is, if an non-
resampable (i.e., aperiodic) curve is used as input to an algorithm, the resulting curve will
inherit that same sample framework. MathPack now processes StratUnits (named units)
correctly in a variety of geometric situations, including horizontal wells which may penetrate
the same formation multiple times. MathPack also now replaces the use of SDF files with
access to Global Parameters, which are shared by the other PetroWorks applications, and by
applications written with ModelBuilder. Given exclusive, uniform use of Curve Details in its
algorithms, MathPack preserves that context (service, run, pass) in all outputs within a well.
The MathPack documentation has also been substantially revised.
Curve Utility has had its performance enhanced, especially for large numbers of wells. Its
interface has been changed slightly to improve user efficiency, and it now has the ability to
send (via PD) wells and curves to other applications.
Summation has had several significant improvements. There are more options for calculating
sums over formation intervals. Sums calculated in TVD and TVDSS depth modes no longer
interpolate the data, and there is more user control over the naming and output of calculated
values.
Strat Column Editor provides greater flexibility and control of surfaces within strat units and
columns. This enhancement allows surfaces to have different ages in different columns so that
a user can change the ages of the bounding surfaces of a unit without affecting other strat
columns. This will allow interpreters to adjust the surfaces in their own columns without
impacting the columns owned by other interpreters. The surfaces in each column become
attached to that column and this attachment of surface and column is created as soon as the
general surface in specified in the definition of a unit in any column.
For more information, see Working with Surfaces in a Column in Setting up StratWorks.
General Application Behaviors
Application Colors
Running the applications in 24-bit color mode (true color) eliminates the color limitation problems
that were present in previous versions, which ran in 8-bit color mode.
Specific Application Enhancements
Crossplot
In general, the new user interface (described below) has significantly decreased the time required
to create crossplots and associated plots.

Changed behavior
Point display and color

A functional change for Crossplot R2003.12 is that if a crossplot is set up to use a z-axis curve, and
if the z-axis curve has null values, then these data points will be counted in Total Points, and so
long as the X and Y values are not null, then these points will also be used in regression fits. The
points will be displayed in grey. The R2003 version of Crossplot discarded points with null z
values for counting Total Points and also for computing regressions. In R2003, the points were not
displayed.
In order to duplicate the behavior of R2003, the user must explicitly exclude the Z values that are
null. This can be done in the Discriminators tab, by setting the curve to include data points greater
than the null value.
The other functional change is that if the Color of the data points is set to Z-Axis, data points which
have a z-axis value of NULL but which have valid x- and y-axis values will be grey, and will be
used in regressions. This highlights an ambiguity in the use of the color grey. The use of a polygon
in crossplot or equivalent filtering mechanisms in histograms and log plots will turn excluded
points grey. These grey points will NOT be used in regression fits
Display behavior with many wells

The limit of 100 wells in a crossplot has been removed.
New user interface
A tabbed interface puts related items on the same tabs, or in the same tab groupings. This
minimizes the number of button clicks, text entry, and windows necessary to create basic or
specialized plots.
Defaults from Curve Dictionary or from common usage minimize data entry in text boxes.
Redesigned interface eliminates unnecessary crossplot redraws.
Displays, Overlays, and other crossplot features can be toggled on and off without returning to
specific interface tabs.
Improved well selection
The limit of 100 wells in a crossplot has been removed.
Search/filter capability.

More well parameters shown.
Ability to sort on each well parameter column.
Improved Interval (StratUnit) selection
Improved Curve Selection
Selection by Alias, Name, or Details.
Sort capability.
Improved crossplot specification
Curve Scales default to Curve Dictionary values. Other choices are Inverted Curve Dictionary,
Curve Min/Max, Curve Max/Min, and User Selected.
Scale divisions can be specified, but do not drive the endpoint scale values as with the old
Increment entry.
One line of user annotation is now available.
Cumulative Crossplot option: the OpenWorks Current Well can be displayed over other wells.
Improved Log Tracks plot specification
Improved Histogram plot specification
True Cumulative Histogram option: the OpenWorks Current Well can be displayed over other
wells.
The user can choose to show only the Cumulative Histogram.

Frequency Crossplot
Posted Values Single Option uses Roman Numerals to signify ranges of counts in cells
containing more than 10 data points; e.g., a cell with 34 data points will show X because it
contains between 10 and 49 data points.
Discriminators
Can be selectively turned off or on, making What if scenarios easier.
Crossplot overlays
Lithology-Porosity crossplots
Spectral Density (RHOB-Pe) overlay is added to Neutron-Density, Neutron-Sonic, and Sonic-

Density.
In Neutron-Sonic and Sonic-Density crossplots, the Raymer-Hunt-Gardner (Schlumberger

empirical) equation is added as an option to the Wyllie Time-Average equation.
Overlays are available from the following acquisition companies: Baker Atlas, Baker Hughes
INTEQ, Gearhart, Halliburton, PathFinder, Precision Wireline (Computalog), Reeves,
Schlumberger, Schlumberger LWD, Sperry-Sun, Tucker, Welex.
Overlays respond to changes in measurement system and to user-input values for fluid density
and fluid acoustic traveltime.
Mineral points are increased to 11, including 2 user minerals. Mineral values respond to
measurement system changes and can be modified by the user.
More user control over display attributes.
Apparent Matrix (Mineral Identification (MID)) plot
Apparent matrix density-Apparent matrix traveltime (RHOmaa-DTmaa) overlay is added to

Apparent matrix density-Apparent matrix volumetric cross section (RHOmaa-Umaa).
Overlays respond to changes in measurement system.
Mineral points are increased to 11, including 2 user minerals. Mineral values respond to
measurement system changes and can be modified by the user.
M-N Lithology plots

Mineral points are increased to 11, including 2 user minerals. Mineral values can be modified
by the user.
Statistics and regressions
Display and control of up to 5 polynomial lines, each up to a fifth-order polynomial. Multiple

instances of the same order line can be calculated and plotted. Coefficients can be modified by the
user and the line replotted.
Addition of 4 other equations which can be plotted according to user-input coefficients.
Gradient Methods to support Pressure Data-Fluid Contacts, Velocity-Velocity Modeling.
Independent control of up to four linear equations.
Calculation of X and Y intercepts for each line.
Calculation of the intersections of the gradient lines with each other.
Configuration files
Plot format (configuration) files save more interface information.
Default configuration files for porosity crossplots, Rwa, and Pickett plots are provided for the
following measurement systems: US Oil Field, Canadian Metric, SPE Preferred Metric.
Printing
Additional print format options: PostScript, JPEG, XPM.
Curve Utility
Performance enhancement for large numbers of wells. Tests have shown a 10x to 100x
improvement in retrieval time for curve information.
Quick refresh.
PD Send Wells and Curves.

Interpreter/Source Priority
PetroWorks now shares a common Interpreter/Source Priority List Manager with StratWorks.
The StratWorks Interpreter/Source Priority List Manager has been adopted by PetroWorks, giving
a new look to that functionality in PetroWorks.
MathPack
Improved curve selection; ability to search and filter on curve identifiers.
Curve Alias, Curve Name, and Curve Details formats can be used for input curve identifiers.
MathPack honors the sample framework of input curves. Curves created by algorithms using core
data and other non-resampleable curves maintain proper sample frameworks.
The pre-defined Global Parameters, used by other PetroWorks algorithmic applications and user-
created ModelBuilder applications, are available for use in MathPack. This functionality replaces
the use of SDF files, which are no longer supported.
Parameters obey parent/child inheritance; with the most spatially-specific parameter being used at
any given sample point. This behavior of selection of the most specific parameter is consistent, and
does not depend on the requested processing interval.
Parameter Maps can be output as blocked, irregularly-sampled curves.
New pre-defined Symbolic Equations, written with Curve Aliases and Global Parameters for
increased processing flexibility.
Curve references within an algorithm may now be expressed with Curve Details. Furthermore, if
all Curve Details use the same keys for service name, run number, and pass id, the output curves
are given these keys. If uniform acquisition keys are not used, or if one or more curve references
use a Curve Name or Curve Alias, the output curves are given the keys: service name =
PETROWORKS; run number = C (composite), pass id = NONE.
New pre-defined Algorithm Element: function Random( )
Remarks can be added to the Curve History of output curves. The Curve History can be displayed
in Curve Utility.
Single Well Viewer
Single Well Viewer and Well Template Editor have been combined into a single application. You
can move between the Single Well Viewer Edit Mode (Well Template Editor) and the Single Well
Viewer display mode (Single Well Viewer) by selecting icons on the interface, or from the main
menu of the application.

Summation
Renaming of output curves
On/Off Control of output curves
Renaming of computed attributes
On/Off Control of computed attributes
Non-interpolation of log data in deviated wells TVD calculations
Surface/Pick snap control
Easy setup modes - Spreadsheet, Default
User control of sample rate
Configuration/Session file to save application interface settings
MD/TVD/TVDSS depth modes
Well Template Editor
Single Well Viewer and Well Template Editor have been combined into a single application. Well
Template Editor functionality can be accessed directly at Utilities > Single Well Viewer Edit
Mode.You can move between the Single Well Viewer Edit Mode (Well Template Editor) and the
Single Well Viewer display mode (Single Well Viewer) by selecting icons on the interface, or from
the main menu of the application.

Installation
Supported Operating Systems and Software
PetroWorks requires the following operating systems and supporting software:
SUN SGI Linux
SunOS 5.8 (Solaris 8.0 Operating IRIX 6.5.11m OS RedHat Enterprise Linux WS 3.0
Environment 0202) plus patch X11R6.4OSF/Motif 2.1 window (aka Advanced Workstation 3.0)3.
108940-52 or higher. 1 manager Full installation (not just Workstation
X11R6.4OSF/Motif 2.1 window Oracle 8.1.7.4 or 9i installation).
manager OpenWorks 2003.12 RedHat Gnome Desktop
Oracle 8.1.7.4 or 9i StratUtils 2003.12 environment 4,5
OpenWorks 2003.12.x FLEXlm 7.2e license manager Oracle 9
StratUtil 2003.12.x Adobe Acrobat Reader 4.x 2 OpenWorks 2003.12.x
FLEXlm 7.2e license manager StratUtil 2003.12.x
Adobe Acrobat Reader 5.x 2 FLEXlm 7.2g license manager
Adobe Acrobat Reader 5.x 2
1. SUN patches can be downloaded from www.sunsolve.sun.com. A username and password are
required.
2. The Acrobat Reader is now required for viewing PDF-format user guides and other
documents included with PetroWorks 2003.12.0.
3. PetroWorks 2003.12.1.0 was also tested on Redhat Enterprise Linux WS 3 update 4.
4. PetroWorks was tested on both the Gnome Desktop the KDE Desktop.
5. The Sawfish window manager is recommended for the Gnome Desktop.
Graphics cards tested with PetroWorks:
Platform/OS Graphics Cards Tested

SUN/Solaris 2.8 Creator 3D
Expert 3D
XVR 1000
XVR 500
SGI/IRIX 6.5.11m ESSI
ESI
Linux Red Hat Enterprise 3.0 Fire GL4
Matrox 400/450
NVIDIA GeForce 2MX
NVIDIA Quadro4 900XGL
NVIDIA Quado4 980XGL

Installation Notes
Installing PetroWorks with the CD-ROM Installer

The Landmark Release Manager provides a consistent GUI-based interface for installing
PetroWorks and other Landmark applications released on CD-ROM. After you specify the
programs to be installed and the directories in which to install them, the program provides a
graphical status display of the installations progress. Use the following procedure to install
PetroWorks for IRIX and Sun Solaris.
This following sections explain:
how to prepare for the installation
how to install the software
how to select the applications to be installed
how to select the file systems where the applications are to be installed or upgraded.
All PetroWorks products follow the same installation procedure.

The following installation procedures apply to all PetroWorks products
(LogEdit, PetroWorks Asset, and PetroWorks Pro). All three are
generically installed as PetroWorks.
Dependencies
Model Builder and make
Model Builder is an end user program development environment that requires some OS-supplied
programmer tools, such as make and object assemblers.
Some very basic Solaris and SGI platforms may lack make and an assembler required to support
use of Model Builder (available only in PetroWorks Pro). These platforms include Sparc Ultra 5
and Ultra 10 systems configured without compiler licenses.
Users of affected systems should contact SUN Microsystems. Free, open-source versions of
make may be downloaded and built from source available via the GNU Project:
http://www.gnu.org/
http://www.gnu.org/software/software.html

StratUtils
StratUtils must be installed before any PetroWorks applications can be run.
Installation Procedure
Preparing for Installation
1. If a previous version of PetroWorks exists on your machine, delete this directory before
installing version R2003.12.1. You should remove the link to the deleted directory; otherwise,
you will be prompted to do so during installation.
2. Determine where you have enough disk space available to install the software.
Platform/OS Disk Space Required (MB)

SUN/Solaris 264
SGI/IRIX 640
Linux 340
Installing the Software
1. As root, insert the PetroWorks CD into your CD drive. Change directories to
/cdrom/volume_12/install
and type the following command:
./setup
The following message appears:
If you have not previously defined the OWHOME environment variable, you will be prompted
for the location of OpenWorks:
Please enter the full path to the OpenWorks installation location (OWHOME):

2. Enter the full pathname to your OpenWorks R2003.12 installation. (If the path does not exist,
you will be prompted to create the path.)
Watch the response of the Release Managerit will return the OWHOME directory path and
automatically detect your machines operating system. Then, it will display a message telling
you which OS version of PetroWorks it will install.
For example:
OWHOME is set to: <OWHOME directory path>
Release Manager (cdi.exe) starting in background.

After a few moments, the Release Manager Release Notes window appears:
3. Click the OK button.
The Product Selection window appears:

This window shows the applications that are available for installation, any special installation
parameters to be used, the version number of the application, the space in megabytes required
to install the application, and the location where the application is to be installed.
Use this window to select the applications you wish to install and to specify the location where
they are to be installed.
There are five buttons at the bottom of the window:
Start starts the installation process.
System Info displays a window showing information about your systems configuration.
Release Notes displays a window containing the release notes document for the application
selected for installation.
Display Log displays any messages written by the Release Manager.
Exit terminates the installation procedure.
4. Select the application(s) to be installed.
When you click on a field in the Install Option column, a selection toggle appears:
Select one of the following:
Install if the application is not on your system.
Upgrade (Do not use this option.)
Do Not Upgrade!
Do not use the Upgrade option. You must install, not upgrade,
PetroWorks.
No Action if you do not wish to install the application.

5. Select the location in which to install the application.
The Location column shows the default locations.
To change the location displayed, click on the button next to the location.
The Location Selection Dialog appears:
This dialog box shows all file systems mounted to your system and the space available on each.
To select a file system, click on it. Directories that are available on the file system appear in the
Path area.
6. If you wish to change the installation directory from the default, click on the file system
mount point where you wish to install PetroWorks and type PetroWorks at the end of the path
in the selection box.
The name of the directory appears in the Selection field. (Note: you can create a directory by
typing a name for it into the Selection field.)

Click OK to select the directory and dismiss the window.
Click Cancel to dismiss the window without selecting a directory.
7. After you have selected the applications and the locations in which to install them, click on
Start in the Product Selection window.
8. If you deleted a previous installation of PetroWorks and did not remove the link to the
directory, the following dialog appears:
Press OK to remove the link and proceed with the installation.
9. The Installation Status window appears:

The installation program begins to copy files to the selected file system. A PetroWorks
directory is created with app-defaults, bin, dat, docs, help, install, mb, and templates
subdirectories.
As the installation proceeds the status bars at the bottom of the window are updated.
10. Click on Close to close the Release Manager window.
Several windows appear, as described below.

The Product License Information window describes the procedure for upgrading your
PetroWorks license:
PetroWorks incorporates FLEXlm license management software from Globetrotter, which

uses software versioning in the license.dat file.
This release of PetroWorks (R2003.12.1) will work with license files from Release 2003.12.x.

In addition to the license information window, an xterm window opens. It tells you that
PetroWorks R2003.12.1 has been installed successfully. The cell for the product in the Install
Status column in the Production Selection window also displays the word Successful.
11. Press OK to dismiss the Product Installation Status window.
12. Press Exit to close the installation program.
13. A confirmation dialog appears. Select Yes to close the installation program.
14. You will be prompted whether you wish to delete the log files recorded during installation.
These files are useful for troubleshooting installation problems. Choose one of the following:
Select OK to delete the log files and close the installation program.
Select Cancel if you do not wish to delete the log files. The installation program closes.

Completing the Installation
1. Install StratUtil R2003.12.x PetroWorks applications will not execute if StratUtils is not
installed.
2. You are now ready to begin a PetroWorks session from the OpenWorks Command Menu.
Select Applications > PetroWorks > PetroWorks Asset (or PetroWorks Pro) to initialize
the Command Menu.
3. If you purchased only LogEdit or PetroWorks Asset, you may want to delete the executable
files that you will not need to free up disk space. (See the section Removing Unnecessary
Files on page 32.)
4. For PetroWorks Pro, some Solaris and SGI systems lack the needed operating system files to
run Model Builder. See the section Supported Operating Systems and Software for more
information.

Data Supplied with the Installation CD
In the directory $PWHOME/dat/projects, you will find a training project and an LAS file that can
be restored in OpenWorks 2003.12.x. The following files are on the installation CD:
PETROTRAIN.bck contains the data needed to run the exercises in the PetroWorks Basics
training manual. It consists of 15 wells (vertical and deviated) with curves, surface picks, and
engineering and production data.
PLATINUM.LAS contains a well in LAS format that you can load into the PETROTRAIN
project.
To restore the training project:
1. Select Project > Project Administration from the OpenWorks Command Menu.
2. In the Project Administration dialog box, select Project > Restore.
3. Specify a name for the restored project and select the project file PETROTRAIN.bck (type
echo $PWHOME to determine the location of the $PWHOME/dat/projects directory), and
click OK.
4. When you are prompted for the project size, use the Novice setting.

Command Menus (Launcher Bars)

The PetroWorks R2003.12.1 application suite launcher bar menus have the options shown below.
Note that PetroWorks Asset and LogEdit contain subsets of the full functionality of PetroWorks
Pro.
The illustration below is from the first page of the Online Manual.
From this page, you can go directly to the documentation specific to each PetroWorks application
(by clicking on the application name), or you can access the individual sections of the complete
documentation manual set by clicking on the blue links at the bottom of the page.

PetroWorks Family of Applications

The PetroWorks applications consists of PetroWorks applications as well as StratUtil and
OpenWorks applications that can be launched from the PetroWorks and LogEdit command menus.
In the table below, applications are grouped by functionality. The table also shows which
applications are available in each PetroWorks family productLE, LogEdit; PA, PetroWorks
Asset; PP, PetroWorks Pro. StratUtil and OpenWorks applications are noted with SW and OW in
the margin. New applications for this release are also noted in the margin. New and/or enhanced
functionality for individual applications is described in the following section.
PetroWorks Family Applications

Application LE PA PP Application Description
Project Management
SW Source Priority List Enables you to establish separate prioritized lists for petrophysical
Manager data sources and geologic (stratigraphic) data sources. Many
interpreters can be working in the same project at the same time, and
the Interpreter/Source Priority settings tell the program whose data
you want to use. The geology list option in the Interpreter Source
Priority List Manager replaces the Session menu option Interpreter/
Source Priority available in previous releases.
OW Curve Alias List Allows you to maintain and manipulate ordered lists of curve names
Manager (mnemonics) represented by a single identifier (Curve Alias),
representing a general curve type similar to POSC trace
classifications. Curve aliasing allows you to use a single identifier for
a curve type, which is reconciled to the actual name of the curve that
exists in each well at the time of processing.
Preferences Allows you to establish the stratigraphic framework for the session,
that is, you control which project stratigraphic column is used to for
displaying surfaces and unit in dialog boxes in PetroWorks
applications for the session
SW Strat Column Editor Allows you to build multiple stratigraphic columns, thereby defining
the project stratigraphic framework.
Data Export and Conversion
Log Export Utility Enables you to export curves to StrataModel (SM1) and LAS
formats.
Wellbore Data Creates log curves from conventional core analysis data stored in the
Converter core tables in the OpenWorks database.
Lithology Curve Enables you to transform computed lithology data intervals

Generator determined in StratWorks into equivalent depth-based log curves that
have unique integer log values for each lithology type.
Data Preparation
Environmental Provides more than 200 corrections for Baker Atlas, Gearhart,
Corrections Halliburton, Schlumberger, Sperry Sun, and Welex tools.

PetroWorks Family Applications (continued)

Temperature Curve This utility enables you to create a temperature curve over the length
Creation of the well. The curve is necessary to account for resistivity changes
with temperature in water saturation and other equations.
Curve Smoothing This utility enables you to smooth, or filter, curve data. The pre-
defined filters are intended to smooth data with fine vertical
resolution to the coarser vertical resolutions of other data, such as
deep resistivity measurements. The filters assume a periodic sample
rate of 2 samples per foot.
Well Data Management and Editing
LogEdit Enables you to perform interactive or manual log edits on log curves.
Log Edit options include depth shifting, baseline shifting, patching,
splicing, rescaling, resampling, and gap filling.
Wellbore Parameter Enables you to edit petrophysical parameter values stored in

Editor OpenWorks via a table interface. It works interactively with the all
PetroWorks interpretive applications for selecting input and output
curves and editing both Global (shared earth) Parameters and
parameters specific to interpretive applications.
Strat Unit Editor Allows you to easily add, modify, and delete units and picks
Curve Utility Enables you to copy users curves, delete curves for which you are
the source, bulk depth shift curves, and generate curve history reports
on data from one or more wells. You can customize the interface by
sorting, filtering, and/or hiding any of 32 data types.
Basic Interpretive Applications
Preliminary Calculates a number of quantities of interest for quick look and

Reconnaissance standard interpretation techniques. These include single measurement
porosities, crossplot porosities, apparent matrix values, water
resistivity from the SP, and apparent water resistivity and apparent
mud filtrate resistivity using crossplot porosities.
Log Functions Allows you to do basic log calculations such as porosity corrections
and water saturations using the Archie formula.
QuickInterp Provides you with a quick look interpretation in which you can
calculate shale volume, porosity, water saturation, and permeability
index by various algorithms in each of the above categories. Because
it can be set up to make all the calculations in a single pass, it is ideal
for reconnaissance-type applications, or to determine reservoir
parameters at a general first-cut level. Output curves from
Preliminary Reconnaissance can be used to determine some of the
parameters required by QuickInterp.
Progressive Interpretive Applications


Shale Volume Calculates up to 11 different shale volumes from up to 8 input curves.
The program also calculates a minimum or average of selected shale
volume curves. Output from this program can be used as input to
other programs that require or allow input of an externally-derived
shale volume.
Complex Lithology Allows you to process formations consisting of up to three different

minerals. The application returns mineral properties as well as the
conventional results of water saturation and corrected porosity. This
application requires at least three different porosity measuring logs.
OnePhiSw Calculates water saturation from one of several shaly sand equations
using a single input porosity. If density, sonic, or neutron is input, an
effective porosity is calculated, or an externally determined effective
porosity can also be input. Outputs included undisturbed zone water
saturation, Sw, flushed zone water saturation, Sxo, if an Rxo curve is
available, bulk volume water, and coal and salt indicators. An Archie
water saturation can be calculated if shale parameters and inputs are
turned off.
Shaly Sand Lets you determine corrected porosity and water saturation from
various shale determination routines. You have the option of which
tool to use for shale volume determination (GR, SP, Neutron, etc.), as
well as whether to use linear and non-linear shale determination
formulae. You can also choose from three different complex water
saturation equations (Indonesian, Simandoux, and Modified
Simandoux).
Dual Water Uses only the Dual Water shaly sand method to solve for water
saturation. The program also outputs total and effective porosities
and volumes of the main constituents of the rock: wet clay, dry clay,
silt and matrix. Hydrocarbon density can either be input or calculated
within the program. Matrix density can either be entered as a fixed
value or as an input curve. The program uses the neutron and density
logs to determine porosity, and corrects them for clay and
hydrocarbon effects through an iterative technique. Sxo is determined
from Rxo, or from the EPT measurement, or from an empirical
equation if neither measurement is available. If both measurements
are available, a variable cementation exponent can be calculated.
MultiMineral Similar to Complex Lithology in that it allows you to process rock
matrices consisting of three or more different minerals. The
application returns mineral properties as well as the conventional
results of water saturation and corrected porosity. This application
requires either three or four different porosity measuring logs.
Pulsed Neutron Allows you to process thermal decay neutron logs. It calculates
saturations using the dual water model given an intrinsic formation
sigma value from any pulsed neutron tool. It can also calculate
borehole corrected porosity from TDT-K Ratio and Sigma.


PreMRIAN, Swb Used in sequence, enable you determine total and effective
MRIAN, MRIAN porosities, total, effective, and bound water saturations, bulk volume
water estimates, and reconstructed resistivities and SP curves using
not only conventional logs but also NMR data. MRIAN uses the Dual
Water model.
User Programming
Model Builder Allows you to design your own petrophysical model, a mathematical
description of how you want to manipulate the physical
measurements taken from well curves. Then, from your own
specifications, Model Builder builds an executable PetroWorks
application, which you and others can run to analyze and interpret
well log data. A working knowledge of C or FORTRAN is required
to effectively use this feature.
MathPack Enables you to build algorithms and apply them against one or more
curves on multiple wells and units. You can solve virtually any
equation mixing curves and constants.
User Models See and run published user-written models
Visualization
Crossplot/Histograms Allows you to plot up to three different curves, with multiple

discriminators, using industry standard overlays. You can visualize
the data in three dimensions in histograms and log views, and easily
transfer parameter information to other applications.
SW Single Well Viewer Enables you to use templates created in the SWV Edit mode to
display wellbore data in log formats. This version of Single Well
Viewer displays vector, or multi-valued, data as well as the more
common single-valued data.
SW Wellbore Manager Enables you to track the history of a well from beginning to end, to
examine the characteristics of a hole and the equipment in the hole, to
design a new or altered completion and production string, and to add,
edit, query, and delete mechanical data alongside your equipment
Tabular List Generates a report of digital curve data for particular depth points or
units for any selected set of curves and depths. By comparing the
report with the graphical display in LogEdit, you can verify data or
confirm that data exists for a particular depth.
Visualization Utilities
SW Single Well Viewer The templates specify display parameters and are necessary to view
Edit Mode well log data in Single Well Viewer and LogEdit. Now includes the
Well Template Transfer utility.
SW Header/Trailer Editor Create customized header and trailer templates for display in Single
Well Viewer and other PetroWorks and StratWorks applications.


SW Color Control: Enables you to create special color files and use them to highlight
Seismic and Log variable attributes in certain PetroWorks and StratWorks
Variable Fills / applications.
Contour and
Geocellular
SW Wellbore Symbol Allows you to create your own custom symbols for well equipment
Editor as well as edit existing symbols.
SW Marginalia Editor Marginalia Editor enables you to create templates that include map
scales, north arrow, title box, etc. for hardcopy plotting
Report Viewer Displays reports generated by Tabular List, Summation, Sensitivity

and Curve Utility and enables you to save and print reports.
Mapping and Volumetrics
SW MapView Provides you with the ability to easily construct maps of

petrophysical properties, structural maps of surfaces, isochore maps
of thicknesses, etc. Well logs can be displayed at well locations and
bubble maps can be generated to show fractional formation attributes.
Summation Generates a summary of reservoir production parameters required for

determining volumetrics. Includes thin zone discriminators and
honors exact unit boundaries.
Sensitivity Enables you to vary multiple reservoir cut-off parameters to

determine the potential for hydrocarbon production

Removing Unnecessary Files
LogEdit and PetroWorks Asset are subsets of PetroWorks Pro. All three offerings are distributed
in a single installation package. The license file controls whether the application within the
PetroWorks directory launches from the LogEdit, PetroWorks Asset, or PetroWorks Pro launcher.
If you do not intend to license PetroWorks Pro, deleting executable files associated with these
applications will free approximately 100 MB of disk space. Exact size savings vary from platform
to platform. To realize the savings, remove the files shown in the following table from the
$OWHOME/PetroWorks/bin directory.
Deletable Executable Files for LogEdit and PetroWorks Asset

File Name Delete for LogEdit Delete for PetroWorks Asset
pwal
pwpl
mbenv_setup
mb_make_new_root_dir
mb_make_new_model_dir
mbsh
mbRunModel
gdbddd
gnuman
spe.exe
ShaleVolume.exe
QuickInterp.exe
bhc
sensitivity
summation
mm.exe
crossplot
Dual_Water.exe
Complex_Lith
PulseNeutron.exe
OnePhiSw.exe
LogFunctions.exe
Shaly_Sand.exe
Recon.exe
mb.exe
mbaut.exe
xptui

Deletable Executable Files for LogEdit and PetroWorks Asset (continued)

File Name Delete for LogEdit Delete for PetroWorks Asset
PreMrian.exe
Marian.exe
SwbMrian

PetroWorks Software Notes
How PetroWorks and LogEdit Read Curves
Within a well, curves are made unique in the database by name, service name, run number, pass
ID, and version number. Logging runs may overlap or may have gaps between them. Generally,
logging run numbers increase with depth. However, because of the variety of data input sources,
this may not always be true. Therefore, it is prudent to check data depths and run numbers to fully
understand the range of your data.
Each time a curve is modified or recomputed (and the curve name is unchanged), a new version is
created. There are no options to overwrite curves, but the curves you create can be deleted. If using
Curve Aliasing or Curve Name to specify a curve, PetroWorks uses the highest version of the curve
owned by the Interpreter with the highest priority in the Petrophysical Source Priority List for
computation and display. (Curve Details specifies the curve instance exactly.) When several curves
with the same name exist over different depths (with different run numbers), PetroWorks by
default combines the highest versions of those curves to meet the depth requirements of a
processing request, in an operation called autocompositing.
To do so, PetroWorks sorts the curves by top depth and combines the curves to create a composite
image. The curve with the shallowest top depth begins the composite. The remaining curves are
added to the composite according to the following rules:
If a curve is completely overlapped by the composite created so far, that curve is ignored.
When the composite curve ends, the next curve is added to it.
If there is a gap between the composite end and the next curve, null point padding is added
to the gap between the composite and the top of the next available curve.
If there is a partial overlap between curves, the portion of the next curve that is not
overlapping is appended to the composite image.

The process described above is referred to as autocompositing and is illustrated below. (Note: the
figure below may not display properly under some conditions.)
Autocompositing
Autocomposited curve presented to
the application by OpenWorks to
near maximize the available data interval.
surface GR:GR/DIL:r1:MAIN:v1
GR:PETROWORKS:rC:NONE:v1
GR:GR/DIL:r2:MAIN:v1
RUN 1
Well Depth
GR:DIL/BCS:r3:MAIN:v1
RUN 2
TOTAL RUN 3
DEPTH
Original curves stored in OpenWorks.

Resampling Issues
The functionality of PetroWorks 2003 in creating curve data changed completely from previous
versions of PetroWorks. Those changes are carried on in PetroWorks 2003.12.x, and incorporate
the concepts of resampleability, z- index, and sample framework.
Resampleability: As the name indicates, this is the ability of the curve to be resampled or values
interpolated between reported measured values. Most common log curves are oversampled
during acquisition and thus can be resampled at a later time without significant loss or change
of data. Core data is non-resampleable because the measurement represents the physical
properties of the formation at a particular depth.
Note that resampleability replaces the commonly used concept of periodicity as the driver
behind how curves are handled. Core data is the most common example of data that is both
aperiodic and non resampleable. A flag curve is a less common example of data that is
periodic and nonresampleable (to preserve the exact depth of a change in the flag value as
a continuous function). The fact that a curve is aperiodic does not guarantee that it is
nonresampleable; conversely, not all periodic curves are resampleable as a continuous
function.
z-index: The concept of depth to describe the relationship between curve data points has been
replaced with z-index. The z-index can be depth (in its traditional measures of MD, TVD,
TVDSS), time (clock time, two-way time, elapsed time such as LWD acquisition time, and
even geologic time), or event number.
Sample framework: This describes the relationship of the data samples of a group of curves. If
a group of input curves to an application has one (or more) curves that are nonresampleable,
the resampleable curves are resampled to the sample framework of the non-resampleable
curves. If all curves are resampleable, the curves may be resampled, if needed, to an increment
specified by the application or to the finest (smallest) increment in the group of curves.
If two nonresampleable curves (with or without additional resampleable curves) are chosen
as inputs to an application, and the frameworks are compatible, the processing will proceed,
with the output sample framework determined by the compatible framework of the
nonresampleable curves. If the frameworks of the nonresampleable curves are
incompatible, processing either will not proceed or will proceed with a warning to the user
(depending on how the application is written) with one of the nonresampleable curves
being resampled.

Writing Curve Data Back to OpenWorks
If a curve is created in PetroWorks when there is an existing curve of the same name in the well,
the data from the new curve is combined with the data from the old curve to create a new version
of the curve. This process is called autosplicing and is illustrated below. (Note that the figure below
may not display properly under some conditions.)
Autosplicing
GR
ILD
Requested processing interval
NPHI
RHOB Sw (v1) Sw (v2) Sw (v3)
2nd interval
3rd interval
Logs to be used for

processing.

In the example, four curves are processed over the Requested processing interval to create a
water saturation curve (Sw, version 1). At a later time, the logs are processed over a smaller 2nd
interval. Since the curve name is the same, a second version of Sw is created, containing the
original data in version 1, with the new data over the second interval replacing the original data.
Similarly, in a third processing phase over a different, and smaller depth interval, a third Sw curve
is created (version 3) which contains data from all processing events.

Special Files
Source Interpreter Priority File (PetroWorks and LogEdit)
During initialization, as in previous releases, PetroWorks applications attempt to read and use a
source interpreter priority file. If this file does not exist, PetroWorks will create a source interpreter
priority file composed of the current interpreter first, followed by an *, i.e., all other interpreters.
All non-database project-specific files (such as source interpreter files) that will be backed up and
restored are stored in OpenWorks project directories. These OpenWorks project directories are
found in directories listed in the owdir.dat file.
Applications initially look for the owdir.dat file in $OW_PMPATH. If it is not found, the
application examines $OWHOME/conf.
Interactive LogEdit (PetroWorks and LogEdit)
A file named last_session.logedit_cfg is created upon exiting LogEdit, or when the

user selects Save under the File menu. This file can be placed wherever the user wants it. LogEdit
will initialize without a configuration file, and the user may then set up the LogEdit environment
or access any LogEdit configuration file in any directory by selecting Open from the File menu.
MathPack (PetroWorks and LogEdit)
During initialization, this application attempts to use readable mpkEquations.dat files from
the users working directory (./). From the applications perspective, this directory is the one from
which the OpenWorks launcher was started.
If this file is absent, a default file is taken from $PWHOME/dat.
If for some reason this file cannot be opened, an error message is given, and no default equations
are loaded.

Curve Utility (PetroWorks and LogEdit)
Configuration File
A file named dcu_parms.dat is created in the users working directory upon exiting Curve
Utility if the EXIT and SAVE Configuration button is pushed on the Exit Curve Utility
panel.This file contains a snapshot of limited information concerning the run time environment
at the time the program was terminated. This file is placed in the directory from which OpenWorks
was started. Included in the information saved is:
sort keys
column sequence
column visibility
Upon subsequent re-initialization, Curve Utility will attempt to use this information. Once a user
sets up and saves a dcu_parms.dat file, the file can be renamed with a name that describes the
snapshot. Then, when a user wants to use that configuration template, the user need only replace
the contents of the dcu_parms.dat file in the current working directory with the templates
contents and start OpenWorks.
CrossPlot (PetroWorks)
User Default Configuration File
A file named parms.xpt_cfg will be created upon exit of Crossplot if the EXIT and SAVE
Configuration button is pushed on the Exit Crossplot panel. This file is referred to as the User
Default Configuration File and contains parameter settings for your Crossplot session. This file will
be placed in the directory from which OpenWorks was started. Thus, if OpenWorks is started from
a separate directory by each Crossplot user, a private User Default Configuration File is retained
for each user. This file is not required to initialize the Crossplot application.
Configuration Files
In addition to the User Default Configuration File, similar files referred to as configuration files
may be used. These files also contain parameter information, but they are used to save particular
Crossplot setups rather than just the settings for the last session. In addition, these files can be
named by the user and saved or retrieved from any directory while running Crossplot.
Configuration files have the filename extension .xpt_cfg.

Known Problems
This section addresses problems you may encounter while operating PetroWorks. If an application
does not perform as you expect, consult this section. You may need to follow a procedure or
workaround outlined below.
Up-to-date information on known problems and solutions are on the Landmark Customer Support
website:
www.lgc.com/customersupport/default.htm
General Issues
Open Applications Do Not Convert Feet / Meters when Measurement System is Changed
All PetroWorks applications correctly use the Measurement System set in Project Status when they
are launched. But if the Measurement System is changed in Project Status while an application is
open, many applications incorrectly use the current depth values as the depth values in the new
measurement system (no feet / meters conversion is performed). For example: An application
initialized in US Oil Field reads a stratunits depths as 12000 to 12100 feet, but if the Measurement
System is changed to SPE Preferred Metric while the application is open, it will use the stratunits
depths as 12000 to 12100 meters. This problem only affects depths of stratunits and Depth
Intervals. If you are changing between Measurement Systems that have the same depth type (e.g.
the depth type in both systems is meters), there is no problem. (defect # 714456)
Workaround: Exit the PetroWorks launcher to close all PetroWorks applications before
changing Measurement Systems in Project Status. Then re-open the applications.
Some Applications Slow Down when Processing 1000s of Wells in One Run
This release of PetroWorks (2003.12.1.0) has greatly increased the initialization and processing
speed when working with multiple wells over stratunits. This performance enhancement is robust
when processing 100s of wells. But some of the applications (Summation, Sensitivity, and the
Models) slow down when processing 1000s of wells at one time. (defect # 714174)
Workaround: Break up the Well List so you are processing 100s of wells at one time.
Initialization and processing speed is dependent on the number of stratunits and picks per well,
but tests have shown good performance processing 500 to 1000 wells at one time in these
applications.

Some Applications only process the First Occurrence of a Multiply Defined Stratunit if Mul-
tiple Wells Selected
A well can penetrate a stratunit multiple times. When working with multiple wells, some
applications (CrossPlot, Sensitivity, Tablist, and the Models) only process the first occurrence of
the selected stratunits in each well. (defect # 706151)
Workaround: To process more than the first occurrence of a multiply defined stratunit, select
only one well at a time. When working with one well, each occurrence is listed individually
in the Units List and all selected occurrences will be processed. Applications that do process
all occurrences when multiple wells selected: Mathpack, Summation, and Log Export.
OpenWorks Returns Unexpected Curve Version (specific case)
In one specific case, PetroWorks and StratWorks applications appear to deviate from the rule of
processing/displaying the highest version number of the selected curve. This case is when two
composite curves (i.e., Run Number = "C" or "-1") in a well have the same curve name but different
service names. Since the Curve Name is used (i.e. the service name is not specified when selecting
the curve), it uses the curve whose service name comes first alphabetically. This rule is so strong
that a composite curve with the highest version will not be used because its service name is lesser
alphabetically. (defect #167166)
Workaround: Select the curve using Curve Details instead of the Curve Name.
Note: Remember that PetroWorks and StratWorks applications use Petrophysical Interpreter
Source priority when processing/displaying curves. A curve created by another interpreter may
have a higher version number, but it will not be used if the current interpreter using a default
Interpreter/Source Priority list has a curve by the same name.
Graphic Windows Slow to Resize on Linux
The default settings for both the Linux Gnome and KDE window managers cause the resizing of
graphic windows in Landmark applications to be very slow. (defect #163584)
Workaround: Change the Window Manager setting to prevent multiple redraws during
resizing. Set as follows:
For the Gnome Window Manager: Go to
Programs > Settings > Sawfish Window Manager > Moving/Resizing Window. Change
Opaque to Box for both moving and resizing.
For the KDE Window Manager: Go to
Control Center icon > Look & Feel > Window Behavior > Advanced tab.

Uncheck Display contents in moving windows and Display contents in resizing windows.
Fonts not bold when using KDE window manager on Linux
The default settings for the Linux KDE window managers are not the standard Landmark
application fonts.
Workaround: Change the KDE window manager settings as follows.
Open Control Center > Select Fonts and choose General.
Change the font to Helvetica Bold.
Applications Occasionally Hang after Project Change
PetroWorks applications are designed to exit when a Project Change is initiated. Under certain
circumstances, a PetroWorks application will not properly exit and will hang. If this happens, first
look to see if there is a window prompting to save a configuration file - this will properly close the
application. Otherwise the hanging application process will need to be killed from the command
line.
Common Desktop Environment
Working in a Common Desktop Environment (CDE) on Solaris platforms may greatly reduce the
number of screen colors available to PetroWorks applications, depending on your CDE settings.
We recommend that you set the CDE Style Manager > Color > Number of Colors to Most
Colors for Applications. You must restart X-windows to see the change.
When using a Common Desk Environment, we recommend you enter the Style Manager Window
and turn off the Allow Primary Windows on Top option. Turning this functionality off, prevents
child windows from going behind the main application window.
Naming Conventions
When naming templates, curves, pointsets, grids, surfaces, faults, etc. do not use special characters
such as punctuation, etc. Use alphabetic and numeric characters only. Underscores, dashes, and
spaces are acceptable.
When naming StatUnits do not use colons. Colons are used by the program to delineate between
the statunitname:geofeature:occurance. Stratunit with a colon in the name will not be processed by
PetroWorks applications.

Color Problems
The problems listed below occur most often if you are running in 8-bit color mode. If you are
running in 24-bit (true color) mode, the problems will be minimized or eliminated.
Problems that occur when an application cannot allocate enough colors:
Wellbore Parameter Editor highlight color is black instead of yellow.
background color of the graphics area is neither black nor white
icon buttons on left side of window are blank
color palettes do not display properly, and colors no longer change gradually from dark to
light
changing the color ramp file changes colorfilled contour colors
some of the colorfilled contours are filled with black
all line types display as bold lines on the Line Type selection menu
changing the background color of one application changes the background color of all
applications on that screen
On all platforms, you can run out of colors on a screen depending on how many applications are
open on that screen. Often exiting one or more applications resolves the problem. If closing an
application does not free the colors it used, exit X-windows, turn off the screens, then restart X-
windows and PetroWorks.
Color Indices
If you want to see how colors will look on your plotter, plot the owcolors.cgm file located in
$OWHOME/StratUtil/dat.
Application-Specific Issues
Issues related to specific PetroWorks applications are described below.

CrossPlot
If a well is PDd into Crossplot and selected, the data from that well will be correctly plotted. If the
Setup window is closed and reopened, the previously-PDd well will be missing from the Well
List, but the data will still be present in the crossplot (defect #168928)
When using the Marker Color in the Z-Axis interactively (moving the Marker Color location in
the color bar, while watching the colors on the crossplot change), the response of the Marker Color
may be adversely affected by the presence of too many PetroWorks open windows. In particular,
having the Log Tracks and/or Histogram windows open may cause them to redraw, slowing the
performance substantially. (defect #162701)
When selecting curves for a crossplot, log plot, or histograms, it is best to use the ellipsis (...) button
to the immediate right of the desired text box to re-focus the Curve Selection window, rather than
clicking inside the text box itself. On some machines (with particular machine-specific settings)
clicking in the text box will cause the Curve Selection window to disappear under the main Setup
window. If this occurs, clicking the ellipsis button will bring the Curve Selection window back to
the top of the display. (defect #164771)
Due to the major change in the Crossplot user interface, the Crossplot configuration files have
changed. Configuration files created in 1998.5, 2003.0 and 2003.3 are compatible with 2003.12.x,
but not all parameters are properly used. (defect #168381)
Workaround: Simply close and reopen the Crossplot Setup window. The change of
Measurement System is then correctly applied.
In Overlays > M-N Lithology, the listed M values for fresh and salt water should change with
changing measurement system, but do not. (The N values are constant with measurement system
changes.)
Workaround: In $PWHOME/templates, there are 3 configuration files that contain the proper
values for M and N defaults for the respective measurement systems. (One for each
measurement system.)
If more than 80 wells are displayed in Log Tracks and/or Histograms, Crossplot may show
erratic displays or crash. This limit applies to the Cumulative Histogram feature, even when it is
used without displaying individual histograms.
Displaying large amounts of data may result in exceeding the memory resources of your system.
Crossplot may crash in this situation.
Selecting a point in the 3D Crossplot window will return incorrect location values if the x-axis
scale is decreasing to the right or y-axis scale are decreasing to the top. If it is important to
graphically select points in 3D Crossplot, set the scales to be increasing to the right and top of the
plot.

Curve Smoothing
Curve Smoothing crashes during processing if the base curve name is longer than 26 characters
and selected using Curve Details. (defect # 158986)
Workaround: Select the curve using the Curve Name (turn off Curve
Details).
Curve Utility
Curve History text that is added to a curve cannot be changed or deleted.
Remarks added to a curve cannot be deleted, but they can be changed. Replacing an existing
Remarks entry with a single character which is not a space (like a period ( . ) ) will effectively delete
a remark with minimal impact to the curves record. (defect 166024)
Log Export Utility
Log Export Utility will not export curves that have a single data point. (defect 153595)
MathPack
If you create curves from Global Parameters (by checking Output Petrophysical Parameters as
Curves), the curve parameters must be entered in the OpenWorks Curve Dictionary. Otherwise
the curves will plot with their minimum and maximum values instead of more standard values. The
display parameters can be entered manually in the Curve dictionary, or cdHelper, an unsupported
utility available on isite can be used to load all the Global Parameter display values to Curve
Dictionary at one time. See UserNet 2003-Q3 for a related article:
http://www.lgc.com/news/usernetnewsletter/default1.htm
Pressing the Escape (Esc) key to abort processing occasionally does not work When processing
multiple wells, the user can press the (Esc) to abort processing. The processing is aborted between
wells (when the processing of the current well is completed). But in order for the Escape Key to
stop the processing, the main application window or Progress status window need to be active.
When processing with Petrophysical Parameters, the last sample point in the Stratunit is be treated
differently in Mathpack than in PetroWorks interpretive models, if the Stratunit is not immediately
adjacent to another Stratunit. In this case, Mathpack will use the parameter value for the "well"
while the interpretive models will use the parameter value for the "stratunit' when processing the
last sample point in the Stratunit.
MathPack will not process a well if an input curve has a negative top depth. (defect #167678)

Unit Editor
The Delete option on units removes the specified unit from its logical entry in the database but not
from a global name table for units. Consequently, the deleted unit could appear in other
applications like the Strat Column Editor. Any data associated with the unit is not deleted.
Interpretive Applications and Wellbore Parameter Editor
NULL (undefined) values for parameters affect the behavior of the interpretive applications. The
following general patterns can be used to describe this behavior.
A parameter value can be NULL, if the default value for a parameter is NULL and no value has been
explicitly supplied. Certain specific parameters may have a NULL default if no standard,
recognized value can be assigned the default. Parameters dealing with water resistivity provide a
good example. No default can be known for these parameters without prior knowledge of the
petrophysical context.
Applications will not produce output when dependent on NULL-defaulted parameters, unless the
user has explicitly assigned a value (that hides the default).
If a parameter has a non-NULL default, and the application encounters a NULL value for that
parameter, then the following rules apply.
1. Applications with the primary purpose of generating a single curve as a result will not produce
a result if a parameter is set to NULL. The output simply cannot be generated without a value
for the parameter in question. Applications that fall into this category are:
Complex Lithology
Dual Water
Log Functions
MRIAN, PreMRIAN, and SwbMRIAN
Pulsed Neutron
Shale Volume
Shaly Sand
2. Applications designed to survey and produce an ensemble of curves will produce NULL
output curves, if a required parameter is set to NULL. Generation of some outputs may be
possible, without a value for the parameter in question. Applications that output NULL curves
are:
OnePhiSw
QuickInterp
Preliminary Reconnaissance

Model Builder
Processing Direction in .mds Files
If NSMI (number of samples read in per iteration) is set to greater than 1 in an .mds file, and the
user selects a Processing Direction of Bottom Up, the only value of ISMO (output sample index)
that will work properly is 1. ISMO values greater than 1 will cause the output curve data to be
written at incorrect depths.

Release Notes

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Release Notes

Transféré par

Droits d'auteur :

Formats disponibles

Landmark PetroWorks/LogEdit

Landmark/Asia Pacific Landmark/EAME Landmark/The Americas

R2003.12.1 Release Notes Page 1 of 48 September 2005

Copyright 2005Landmark Graphics Corporation

Landmark Graphics Corporation

R2003.12.1 Release Notes Page 2 of 48 September 2005

R2003.12.1 Release Notes Page 3 of 48 September 2005

Enhancements and New Functionality

The following enhancements to PetroWorks were made for R2003.12.1.

Improvements to Multiple Tie Line Depth Shifting

Search / Filter capability for Well Templates

Sort wells by Well ID, UWI, Common Name, etc.

Search / Filter capability for wells, stratunits, and curves

Improved curve selection

Stratunit names no longer truncated in Report Viewer

Ability to turn on / off discriminators

Option to report statistics only

R2003.12.1 Release Notes Page 4 of 48 September 2005

Performance enhancements mentioned above

Histogram displays enhanced to make values and bars easier to read

R2003.12.1 Release Notes Page 5 of 48 September 2005

General Application Behaviors

Specific Application Enhancements

R2003.12.1 Release Notes Page 6 of 48 September 2005

Point display and color

Display behavior with many wells

New user interface

Redesigned interface eliminates unnecessary crossplot redraws.

Improved well selection

The limit of 100 wells in a crossplot has been removed.

R2003.12.1 Release Notes Page 7 of 48 September 2005

More well parameters shown.

Ability to sort on each well parameter column.

Improved Interval (StratUnit) selection

Improved Curve Selection

Selection by Alias, Name, or Details.

Improved crossplot specification

One line of user annotation is now available.

Improved Log Tracks plot specification

Improved Histogram plot specification

The user can choose to show only the Cumulative Histogram.

R2003.12.1 Release Notes Page 8 of 48 September 2005

Can be selectively turned off or on, making What if scenarios easier.

Spectral Density (RHOB-Pe) overlay is added to Neutron-Density, Neutron-Sonic, and Sonic-

In Neutron-Sonic and Sonic-Density crossplots, the Raymer-Hunt-Gardner (Schlumberger

More user control over display attributes.

Apparent Matrix (Mineral Identification (MID)) plot

Apparent matrix density-Apparent matrix traveltime (RHOmaa-DTmaa) overlay is added to

Overlays respond to changes in measurement system.

More user control over display attributes.

M-N Lithology plots

R2003.12.1 Release Notes Page 9 of 48 September 2005

More user control over display attributes.

Statistics and regressions

Display and control of up to 5 polynomial lines, each up to a fifth-order polynomial. Multiple

Addition of 4 other equations which can be plotted according to user-input coefficients.

Gradient Methods to support Pressure Data-Fluid Contacts, Velocity-Velocity Modeling.

Independent control of up to four linear equations.

Calculation of X and Y intercepts for each line.

Calculation of the intersections of the gradient lines with each other.

Plot format (configuration) files save more interface information.

Additional print format options: PostScript, JPEG, XPM.

PD Send Wells and Curves.

R2003.12.1 Release Notes Page 10 of 48 September 2005