Release Notes Le

Landmark PetroWorks/LogEdit
PetroWorks/LogEdit
R2003.12.1.1
Release Notes
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . 3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing Landmark Licensing . . . . . . . . . . . . . . . . 12
Printing from Acrobat . . . . . . . . . . . . . . . . . . . . . . 14
Fixed Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . 16
R2003.12.1.1 Release Notes Page 1 of 23 August 2006

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.
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.
Release Highlights
The PetroWorks R2003.12.1.1 patch is a patch release for R2003.12.1.0. This is not a full
installation and you must install PetroWorks 2003.12.1.0 first. Please see the R 2003.12.1.0
Release Notes for complete installation instructions. This release is compatible with R2003.12.x.x
OpenWorks installations.
R2003.12.1.1 fixes defects in mathpack and tablist. The defects exist on all three released
platforms (Solaris, IRIX, and Linux).
For more information, see Fixed Problems.
R2003.12.1.1.Release Notes Page 2 of 23 August 2006

System Requirements
This patch is compatible with R2003.12.x.x OpenWorks installations.
Operating System Requirements
Release 2003.12.1.1 is supported on the following operating systems:
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.1.1
3. PetroWorks 2003.12.1.1 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

Platform/OS Graphics Cards Tested

Linux Red Hat Enterprise 3.0 Fire GL4
Matrox 400/450
NVIDIA GeForce 2MX
NVIDIA Quadro4 900XGL
NVIDIA Quado4 980XGL
Dependencies
Several of the applications found in Release 2003.12 (and later) have dependencies on the order of
installation. The notes below outline phases of the installation process and specific requirements
encountered with subsequent application installations.
Install Oracle. (See R2003.12 Release Notes)
Install Landmark Licensing. (See R2003.12 Release Notes)
Install OpenWorks.(See R2003.12 Release Notes)
Install Acrobat Reader 4 or higher.(See R2003.12 Release Notes)
Install PetroWorks and other individual products.
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.

Disk Space Requirements
The R2003.12.1.1 patch requires approximately 70 megabytes of disk space.

Installation
These instructions describe how to install the PetroWorks patch R2003.12.1.1.
Customer support will instruct you how to download the appropriate file for your system. Your
install file will be one of the following: PetroWorks_2003.12.1.1_LINUX.tar.Z,
PetroWorks_2003.12.1.1_SUN.tar.Z, or PetroWorks_2003.12.1.1_SGI.tar.Z appropriate for
your system.
1. Set the $PWHOME environmental.
2. You must install as root.
3. Backup the files to be updated:
Backup mathpack & tablist executables and 3 launcher scripts as follows:
cd $PWHOME/bin
mkdir Pre_2003_12_1_1
mv mathpack tablist lgel pwal pwpl Pre_2003_12_1_1/
Backup the library as follows:
cd $PWHOME/mb/lib
mkdir Pre_2003_12_1_1
mv libmbsys.so Pre_2003_12_1_1/
Backup the Release Notes as follows:
cd $PWHOME/docs
mkdir Pre_2003_12_1_1
mv ReleaseNotesPW.pdf ReleaseNotesLE.pdf Pre_2003_12_1_1/
4. Untar the 2003.12.1.1 patch bundle file for your platform as follows:
cd $PWHOME
uncompress -c PetroWorks_2003.12.1.1_<platform>.tar.Z |tar xopvf-
5. Verify that the new files have the proper ownership and execution status. All files should have
-rwxr-xr-x permissions.
ls -l bin/mathpack bin/tabist bin/lgel bin/pwal bin/pwpl

ls l mb/lib/libmbsys.so mb/lib/libwdgt-tablist.so (libwdgt-

tablist.so is on the Solaris only)
ls -l docs/ReleaseNotesPW.pdf docs/ReleaseNotesLE.pdf
6. Launch LogEdit, PetroWorks Asset, or PetroWorks Pro. The launcher bar should display the
version as 2003.12.1.1.
Mathpack and Tablist should show version 2003.12.1.1 under Help->On Version.
All other apps will still have 2003.12.1.0 under Help->On Version
Changed Files
Files Updated for the 2003.12.1.1 Patch
$PWHOME/bin/mathpack
$PWHOME/bin/tablist
$PWHOME/bin/lgel
$PWHOME/bin/pwal
$PWHOME/bin/pwpl
$PWHOME/mb/lib/libmbsys.so
$PWHOME/mb/lib/libwdgt_tablist.so (new file on Solaris only)
$PWHOME/docs/ReleaseNotesPW.pdf
$PWHOME/docs/ReleaseNotesLE.pdf

Post-Installation
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.
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 Removing Unnecessary Files.)
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.
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
PreMrian.exe
Marian.exe
SwbMrian

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.

Installing Landmark Licensing

Licensing allows controlled use of Landmark applications in a networked environment. When you
license a Landmark application, you also purchase one or more licenses. The number of licenses
determines the number of users who can access the application simultaneously. The license system
should be transparent to the user and, once installed, require minimal configuration and
maintenance by the network administrator.
The OpenWorks Release 2003.12 License Application Manager (LAM). LAM is based on
GLOBEtrotter Softwares (http://www.globetrotter.com) updated Flexible License Manager (FLEXlm)
v7.2 technology. The OpenWorks Release 2003.12 LAM Server software must be installed and
configured as part of the OpenWorks installation process as previous FLEXlm server versions will
not work with this release. This should be completed before installing any point product.
A detailed guide for managing LAM on UNIX or Windows appear in the LAM 2003.12 Guide.
Note
Before installing LAM Release 2003.12 server, please uninstall all existing
previous versions of LAM servers.
Every Release 2003.12 application requires a Release 2003.0 license to run. If you have updated
your licenses for R2003.0, they will not have to be re-issued for R2003.12. The process for
obtaining and installing a license is discussed in the next section.
Upon receiving the license request, a Landmark representative will generate and return your
license. The license will contain information such as product name, version, expiration date,
number of copies, encrypted key. For example, a license for five versions of Z-MAP Plus would
be similar to below:
FEATURE ZMAPPLUS licsrv 2003.000 10-jan-2002 5 AKEY42AAD7898675309F VENDOR_STRING="Ewing Oil
Once you receive your license, you must add it your license.dat file (typically in the $OWHOME/
lam directory) and restart the license manager. After the license manager has been restarted your
newly installed software will be able to run.
For more information on managing the LAM, refer to the LAM 2003.12 Guide or to the OpenWorks
2003.12 Installation Notes.

Obtaining a license
After installing any point product the following dialog box message will remind you to obtain a
proper license:
Attention Landmark Customer
Please contact Landmark for your new software licenses. To receive your licenses, contact the
license administration team via email (license@lgc.com), the World Wide Web (http://
www.lgc.com/customersupport/licensemanagement/default.htm), or phone (The Americas
713-839-2000 and outside the Americas at 44-1932-832100). Please refer to the R2003.12.1.1
Release Notes for instructions on how to retrieve your lmhostid information.
Please have the following information in your email or available when you call:
Company name:_____________________ Location:________________________________
Server lmhostid:_________________ Client lmhostid(s):____________________________
Server Hostname:__________________ Platform:__________________________________
Model:____________________________ Operating System Version:__________________
Site#:____________________________ Reference#:_______________________________
Send the license to:

Name:_____________________________ Phone#:________________________________
Send the license via:

email - email address__________________________________________
diskette - shipping address____________________________________
fax - fax number_______________________________________________
This window is for information only. Click on OK to continue.
You must have the hostid for your system in order to request a license. To obtain the hostid, enter
the following command:
lmhostid
This will display the FLEXlm host ID of the machine. The length of the hostID will depend on the
platform.

Printing from Acrobat

The documentation for all R2003.12 products are included on the OpenBooks CD. The
documentation is provided in Acrobat Portable Document Format (PDF), which can be read using
Adobe Acrobat Reader. Acrobat Reader is free software that lets you view and print PDF files.
If you do not already have Adobe Acrobat Reader, you can download it from the Adobe website
www.adobe.com.
It may be simpler for you to print the manuals or release notes rather than to use them online. When
printing ranges of pages in Adobe Acrobat Reader, you must use the status bar at the bottom of
Acrobat Reader to get the most accurate indicator of which page you are looking at. The page
numbers at the bottom of an online page or other page number references in the online document
are not the page numbers that Acrobat uses when you select a range of pages in its Print dialog.
This situation is especially true in online books, where the table of contents uses one page
numbering scheme and the body of the book uses another.
For example, to print a chapter from the DepthTeam Workflow Guide, follow a procedure similar
to the following:
1. In the bookmark pane of Acrobat, select the name of the chapter that you want to print.
2. Note the page number in the status bar.
3. Display the last page in the chapter.
4. Note the page number of the last page in the status bar.
5. Select File > Print to display the Print dialog.
6. Enter the page numbers that you noted in the From and To text boxes in the Print dialog.
7. Click OK. Acrobat will then print the pages of the chapter.
Note: Acrobat reader must be installed in /usr/bin before documentes can be opened.

Fixed Problems
The following are the fixed problems for PetroWorks R2003.12.1.1:
Mathpack writes incorrect depth range for pseudo curves DEPTH-MD, DEPTH -TVD ,
DEPTH _TVD when processing over Total Depth Range (721850 )
Mathpack cannot create a curve deeper than 17895 or shallower than -17896 ft. using Depth
Interval and curve = a constant value (722305)
Mathpack: If input curve is deeper than 18000 ft, then the output curve bottom depth is clipped
to a shallower depth (723238)
Mathpack rounds the sample rate of the input curve when processing a log stored in feet but
processed in a Metric measurement system. Therefore, resamples curve but should not.
(717265)
Mathpack output curves do not have the correct start depth (therefore resamples curve) when
processing in measurement system other than the curve was created. (718049)
Mathpack: Does not process start and end samples when processing over Depth Intervals when
specifed start/end depths are not on samples. (715646)
Mathpack can't process more than 333 wells in one run. Error message: too many files open.
(728629)
Mathpack: After processing many wells, File->Open Algorthm fails to open the selected
algorthm. (722871)
Tabular List launches Report Viewer with a PetroWorks license. Should use license feature of
launcher bar (i.e. LogEdit, PTW, or PTW Pro) (722324)

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.
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, AssetJournal, Asset Performance, AssetView, Atomic
Meshing, Automate, BLITZ, BLITZPAK, CasingSeat, COMPASS, Contouring Assistant, Corporate Data Archiver, Corporate Data
Store, DataManager, DataStar, DBPlot, DecisionSuite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner,
DecisionSpace AssetView, DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace
Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir,
DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express,
DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery,
Discovery Asset, Drill-to-the-Earth Model, Drillability Suite, Drilling Desktop, DrillModel, DrillVision, DSS, Dynamic Reservoir
Management, Dynamic Surveillance System, EarthCube, EDM, eLandmark, Engineers Data Model, Engineer's Desktop,
Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker, FG+, FastTrack, 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 & Design,
Landmark Logo & Design, Landmark Decision Center, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,
Magic Earth, MagicDesk, Make Great Decisions, MathPack, MIMIC, MIMIC+, MIRA, Model Builder, MyLandmark, Nexus,
Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks
Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher,
PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, Power Interpretation, PowerJournal, PowerModel,
PowerView, Presgraf, PRIZM, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX,
ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+,
QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, Quickwell, Quickwell+, RAVE, RayMap, RayMap+,
RTOC, Real Freedom, Real Time Asset Management Center, Real Time Asset Management Centre, Real Time Operations Center,
Real Time Production Surveillance, Real Time Surveillance, Reference Data Manager, Reservoir Framework Builder, RESev,
ResMap, RightTime, RMS, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks
PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisXchange, Sierra, Sierra (design), SigmaView,
SimResults, SIVA, SIVA+, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel, StrataSim,
StratWorks, StressCheck, STRUCT, Surf & Connect, SynTool, SystemStart for Servers, SystemStart, SystemStart for Clients,
SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs Revenue
Interface, TracPlanner, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIP-DUAL,
VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, 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, service marks and product or service names are the trademarks or names of their respective owners.
All other trademarks are the property of their respective owners.
2006 Landmark Graphics Corporation. All rights reserved.

Release Notes Le

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Release Notes Le

Uploaded by

Copyright:

Available Formats

Landmark PetroWorks/LogEdit

R2003.12.1.1 Release Notes Page 1 of 23 August 2006

For more information, see Fixed Problems.

R2003.12.1.1.Release Notes Page 2 of 23 August 2006

Operating System Requirements

Release 2003.12.1.1 is supported on the following operating systems:

SUN SGI Linux

3. PetroWorks 2003.12.1.1 was also tested on Redhat Enterprise Linux WS 3 update 4.

5. The Sawfish window manager is recommended for the Gnome Desktop.

Graphics cards tested with PetroWorks:

Platform/OS Graphics Cards Tested

R2003.12.1.1 Release Notes Page 3 of 23 August 2006

Platform/OS Graphics Cards Tested

Install Oracle. (See R2003.12 Release Notes)

Install Landmark Licensing. (See R2003.12 Release Notes)

Install OpenWorks.(See R2003.12 Release Notes)

Install Acrobat Reader 4 or higher.(See R2003.12 Release Notes)

Install PetroWorks and other individual products.

Model Builder and make

StratUtils must be installed before any PetroWorks applications can be run.

R2003.12.1.1.Release Notes Page 4 of 23 August 2006

Disk Space Requirements

The R2003.12.1.1 patch requires approximately 70 megabytes of disk space.

R2003.12.1.1 Release Notes Page 5 of 23 August 2006

1. Set the $PWHOME environmental.

2. You must install as root.

3. Backup the files to be updated:

Backup mathpack & tablist executables and 3 launcher scripts as follows:

mv mathpack tablist lgel pwal pwpl Pre_2003_12_1_1/

Backup the library as follows:

Backup the Release Notes as follows:

mv ReleaseNotesPW.pdf ReleaseNotesLE.pdf Pre_2003_12_1_1/

uncompress -c PetroWorks_2003.12.1.1_<platform>.tar.Z |tar xopvf-

ls -l bin/mathpack bin/tabist bin/lgel bin/pwal bin/pwpl

R2003.12.1.1.Release Notes Page 6 of 23 August 2006

ls l mb/lib/libmbsys.so mb/lib/libwdgt-tablist.so (libwdgt-

Files Updated for the 2003.12.1.1 Patch

$PWHOME/mb/lib/libwdgt_tablist.so (new file on Solaris only)

R2003.12.1.1 Release Notes Page 7 of 23 August 2006

Data Supplied with the Installation CD

To restore the training project:

2. In the Project Administration dialog box, select Project > Restore.

Removing Unnecessary Files

R2003.12.1.1.Release Notes Page 8 of 23 August 2006

Deletable Executable Files for LogEdit and PetroWorks Asset

R2003.12.1.1 Release Notes Page 9 of 23 August 2006

Source Interpreter Priority File (PetroWorks and LogEdit)

Interactive LogEdit (PetroWorks and LogEdit)

A file named last_session.logedit_cfg is created upon exiting LogEdit, or when the

MathPack (PetroWorks and LogEdit)

If this file is absent, a default file is taken from $PWHOME/dat.

R2003.12.1.1.Release Notes Page 10 of 23 August 2006

Curve Utility (PetroWorks and LogEdit)

User Default Configuration File

R2003.12.1.1 Release Notes Page 11 of 23 August 2006

Installing Landmark Licensing

R2003.12.1.1.Release Notes Page 12 of 23 August 2006

Attention Landmark Customer

Company name:_____________________ Location:________________________________

Server lmhostid:_________________ Client lmhostid(s):____________________________

Server Hostname:__________________ Platform:__________________________________

Model:____________________________ Operating System Version:__________________

Send the license to:

Send the license via:

Company name:_ Location:____________

Server lmhostid:_ Client lmhostid(s):____________

Server Hostname: Platform:________________

Model:__________ Operating System Version: