WSF ReleaseNotes

DecisionSpace
Well Seismic FusionTM

Release Notes
Introduction ................................................................................................................ 2
System Requirements ............................................................................................... 5
Installation .................................................................................................................. 8
Post-Installation Notes .............................................................................................. 13
The Well Seismic Fusion Workflow .......................................................................... 21
New Features .............................................................................................................. 34
Fixed Problems .......................................................................................................... 37
Known Problems ........................................................................................................ 41
HALLIBURTON | Drilling, Evaluation and Digital Solutions
September 2006 R2003.12.4

Landmark Well Seismic Fusion 2003 Release Notes
Introduction
Welcome to Landmark's latest release of DecisionSpace Well Seismic FusionTM (or Fusion).
Fusion provides elegant tools for petrophysical modeling and prestack seismic AVO analysis. The
goal of Fusion is to use the prestack seismic data to discriminate between fluid and lithology types
within the reservoir. This version of Fusion gives the geoscientist easy access to analyze and
interpret on the prestack seismic data.
Anomaly on stacked
seismic
Real Gather
Extracted Wavelet
Virgin Curve Vp Vs Density

Fluid Substituted Curves
Brine Gas Oil
Offset Synthetic Gathers
Attribute (B)
Background Trend
Brine
Map Views
Oil (one sand or two?)
Gas?
Attribute (A)
Crossplot Analysis
Seismic Views
3D Views
WSF 2003.12.4 Release Notes Page 2 of 51 September 2006

These release notes provide the hardware and software requirements for Well Seismic Fusion,
installation instructions, and a basic workflow. They also describe the typical configuration that
enables Fusion to interact with other applications. The release notes do not describe how to
configure applications that are required by Fusion but not shipped on the Well Seismic Fusion
installation CD.
About this release
Enhancements to this version of Well Seismic Fusion are focused on 2D processing, wavelet
extraction, prestack seismic picking, and multi-well crossplot analysis. Performance, usability, and
stability are other key features of this release. Fusion continues to allow interpreters to squeeze-out
quantitative information from their prestack seismic data. Fusion allows interpreters to thoroughly
validate their prestack seismic response with the log data, then use the prestack data to validate
prospects. As the seismic stacking velocities are of such low resolution, they are only used for data/
amplitude mapping. The velocities are not directly used for fluid or lithology characterization.
Future releases will improve on the qualitative interpretation tools as well as add some quantitative
tools.
As with any complex, full-featured software product, Well Seismic Fusion 2003.12.4.0 contains
some defects. A known problems list for this release is available in the release notes. We have tried
to design this release to allow the interpreter to concentrate on the geology and not on the process
of data manipulation. We welcome any input and thank you for helping make this release a success.
Contents of the Well Seismic Fusion installation CD
The Well Seismic Fusion 2003.12.4.0 package contains the following components.
CD Contents
DecisionSpace Media Kit Well Seismic Fusion components.

(part number 627523) Miscellaneous files and utilities needed for
installation.
DecisionSpace infrastructure components
and J2RE 1.5.
Well Seismic Fusion online help and release
notes.

Licensing
Well Seismic Fusion 2003.12.4.0 requires the following licenses:
WSFUSION
OPENWORKS
In order to run the entire feature set you should also have a SeisWorks and a GeoProbe license.
Well Seismic Fusion Configuration
The Well Seismic Fusion workflow includes interaction with the following products:
Adobe Acrobat Reader

Internet Explorer (Windows)
GeoProbe 3.3+
LogM
Mozilla 1.7+ (Linux)
Netscape 7.0+ (Solaris)
OpenWorks*
Oracle
PowerView 2003.12.1.2+
ProMAX
SeisWorks 2003.12.1.2+
*Through OpenWorks, Fusion provides access to an Oracle 8i or Oracle 9i server (Enterprise

edition) running on a Windows XP Server or a UNIX/Linux server. The Oracle server must have
an OpenWorks SID that stores multiple OpenWorks R2003 databases.

System Requirements
Well Seismic Fusion has the following hardware and software requirements.
Hardware Requirements
The table below lists the recommended hardware requirements for client machines running Well
Seismic Fusion 2003.12.4.0. Well Seismic Fusion will run on the minimum requirements listed
below. However, performance may not reach acceptable levels with large or complex datasets.
Hardware Minimum for

OpenWorks 2003.12.0.1
Operating System (Linux) RedHat Linux Advanced
Workstation 3.0* Update 6
(Full Installation)
Operating System (Solaris) SunOS 5.8* (full installation)
(patch 108940-52 or higher)
Operating System (Windows) Windows XP* Professional -
Service Pack 2 or greater
Processor Type Intel compatible 32-bit
dual processor
Processor Speed 2 GHz or faster
RAM 2.0 Gb or greater
(4.0 Gb or greater w/ GeoProbe)
Hard Disk 3 Gb Minimum, plus
10-500 Gb for each additional

prestack project
Display Dual monitor: 1280 x 1024
Color Depth: True Color (32 bit)
Graphics **nVidia Quadro series
Mouse 3-button mouse
Installation Device Drive CD-ROM
*To find out your operating system level, perform the following:
Linux - cat /etc/redhat-release
Windows - MB3 > My Computer > Properties
Solaris - uname -a
**The following nVidia graphics cards have not been tested on Windows or Linux. However, we
expect them to work: FX 2000, FX 1000, FX 500, 380 XGL, NVS 400, & the NVS 200.

For information on hardware requirements for the Oracle/OpenWorks server and SeisWorks/flat
file data server machines utilized by Well Seismic Fusion, please refer to the System Requirements
section in the OpenWorks 2003 Installation Procedures - Solaris, IRIX, AIX, Linux.
Software Requirements
Windows/Linux Clients
The table below lists the Linux software requirements necessary to run client installations of Well
Seismic Fusion 2003.12.4.0.
Software Version for client

Desktop Environment KDE (Linux only), CDE with Motif Version 2.1 (Solaris only)
X11 R6.4 (XFree86-devel version 4.1.0) (Linux and Solaris)
Oracle client Oracle 8i Enterprise Client 8.1.7.4
(required by OpenWorks 2003.12.0.1+ Client)
OpenWorks client OpenWorks 2003.12.0.1+ Client Installation
LAM (licensing) Globetrotter LAM 7.2g (Linux), LAM 7.2e (Solaris), LAM 7.2e (Windows)
Adobe Acrobat Reader Version 5.x
Exceed* Hummingbird Exceed 8+, installation recommended in DecisionSpace
release notes (Windows only)
*Exceed is not an officially supported platform for Well Seismic Fusion. For
running Fusion on Windows, we recommend running the native Windows
version of Fusion, rather than running the UNIX or Linux version of Fusion
over Exceed.

Windows/Linux Servers
The following table lists the software requirements for Oracle/OpenWorks server installations and
SeisWorks/flat file data server installations utilized by Well Seismic Fusion 2003.12.4.0.
Software Version for server

Oracle server OpenWorks 2003.12.0.1+ environment:
Oracle9i Enterprise Server 9.2.0.4 (Solaris and Linux servers)
Oracle9i Enterprise Server 8.1.7.4* (Windows XP server)
*minimum requirement
OpenWorks server OpenWorks 2003.12+, server installation, no project extensions are
required for Fusion.
LAM Globetrotter LAM 7.2e (Windows, Solaris, and Irix), 7.2.g (Linux)
Samba Version 2.x (necessary for accessing UNIX SeisWorks/flat files from
a Windows client system) (Windows only)
Product Dependencies
To use the full feature set of Well Seismic Fusion, you need an OpenWorks and a SeisWorks
license. Well log curves can come from OpenWorks, LogM, or LAS. Well picks can only come
from OpenWorks. Prestack seismic files can come from SEG-Y or ProMAX, stacked seismic files
can come from GeoProbe or SeisWorks formatted files. Velocity files can come from OpenWorks
or ProMAX.

Installation
The following section provides guidelines for installing Well Seismic Fusion in Linux, Solaris, and
Windows environments. If you have problems setting up your environment, please consult with
your Landmark onsite representative.
Checklist for Linux/Solaris (OpenWorks 2003.12.0.1)
The complete installation requires that you perform the following procedures.
1. Install recommended Operating System:
Red Hat Linux Advanced Workstation 3.0 Update 6 (Full Installation)
or SunOS 5.8 (Operating Environment 02/02)
2. Install Oracle 9i and OpenWorks 2003.12.0.1 through 2003.12.1.3 on the server.
See the OpenWorks 2003.12.0.1 through 2003.12.1.3 release notes. The OpenWorks
installation includes the installation of Adobe Acrobat Reader 5.x, and LAM.
3. Configure OpenWorks so interpreters can see the appropriate projects.
See the OpenWorks 2003.12.0.1 through 2003.12.1.3 release notes.
4. Configure LAM.
See Obtaining a license to run the software on page 11.
5. Install Well Seismic Fusion by following the instructions on the Linux/Solaris Well Seismic
Fusion 2003.12.4.0 installation CD.
Warning
If you have a previous version of Fusion installed, re-uninstall over the top of the old version.
Do not upgrade over the old version.
Note
Well Seismic Fusion does not require any project upgrades or extensions. However, if you are
running Well Seismic Fusion in an environment that attaches to an OpenWorks 2003.12 server,
then any data on that server must have been upgraded to the OpenWorks 2003.12 data model.

Checklist for Windows
Installing Well Seismic Fusion on Windows requires the installation of a supported Oracle Client
and a supported OpenWorks Client. The complete installation requires that you perform the
following procedures.
1. Install recommended Operating System.
Windows XP Professional (Service Pack 2 or greater)
2. Install Oracle Client.
3. Install Hummingbird Exceed 8+
See the installation recommended in DecisionSpace global release notes.

(Exceed is required to install OpenWorks, Exceed is not a recommended platform for running
Fusion.)
4. Install the OpenWorks Client.
See the OpenWorks 2003.12.0.1 through 2003.12.1.3 release notes, as applicable. The
OpenWorks installation includes the installation of Adobe Acrobat Reader 5.x, and LAM.
5. Configure the OpenWorks client to see the appropriate projects.
This includes editing your dir.dat (to see SeisWorks files) and editing your owdir.dat (to see
OpenWorks files). This may also include configuring your network file system so that your
Windows machine can see your SeisWorks/ProMAX file system on UNIX or Linux.
See the OpenWorks 2003.12.0.1 through 2003.12.1.3 release notes for more information.
6. Configure LAM.
See Obtaining a license to run the software on page 11.
7. Configure the Pointing Dispatcher so your Well Seismic Fusion Windows session can
communicate with your SeisWorks map and cross section displays.
See Configuring the PD (Pointing Dispatcher) Variables for Windows on page 18.
8. Uninstall any previous version of Fusion installed on your system.
9. Install Well Seismic Fusion by following the instructions on the Windows Well Seismic
Fusion installation CD.

Permissions needed to install Fusion 2003.12.4.0
Installation of release 2003.12.4.0 should be done as root or administrator. On Linux, use the
command su - root (not su) to get to root so permissions and environments are not inherited
from any login except root.
For all products, the directory being written to must allow the installer permission to write in order
to have a successful install. If you have write permissions on only some files in the directory and
not others, the files to which you do have permissions will be removed, but the other files will not.
This combination of old and new files will prevent a successful installation.
If you install OpenWorks as root, you will need to set full permissions on several directories in the
OpenWorks tree if you subsequently install other products as non-root. These directories are as
follows:
$OWHOME/bitmaps and its contents

$OWHOME/revisions
$OWHOME/templates and its contents
$OWHOME/lib
The Linux/Solaris Fusion installation CD is written in OpenWorks CDINSTALL format. The CD

can be used to install Fusion on all supported Linux/Solaris platforms. Additional reference
information can be found in the sections titled Installing Point Products Using the CDROM
Release Manager in the R2003.12.0 Release Notes.
The Windows Fusion installation CD is written in InstallShield format. The CD can be used to
install Fusion on all supported Windows platforms. Additional reference information can be found
in the installation section of the DecisionSpace 2003.15.0 Release Notes.
For Linux/Solaris installations, please follow the post installation procedures on page 13 to add
Fusion to your executable path.

Obtaining a license to run the software
Before running the released version of Fusion, you must obtain a license file from Landmark
Graphics Corporation. Request the license file from the following address:
http://www.lgc.com/support/licensing
If you have any questions, call your Landmark Customer Services Representative, or see:
http://www.lgc.com
You must have the hostid for your system in order to request a license. To obtain the hostid, enter
the following:
SUN/Solaris and Linux Systems
hostid
IBM/AIX Systems
uname -m
SGI/IRIX Systems
/etc/sysinfo -s
Windows Systems
ipconfig /all (from a Command Prompt window)

Installing the software license
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 DecisionSpace Well
Seismic Fusion would be similar to the example below:
FEATURE WSFUSION licsrv 2003.000 10-jan-2006 5 AKEY42AAD7898675309F VENDOR_STRING="Ewing Oil
Once you receive your license, you must add it to 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.0 Installation Notes for Solaris, IRIX, AIX, Linux which are included in the
Release2003.12 release version of OpenBooks.

Post-Installation Notes
Configuring the OpenWorks Environment (Linux/Solaris Only)
To successfully launch Fusion from OpenWorks, you need to add it to both the path and to the
OpenWorks launcher bar. To add Fusion to the path, you must manually edit your .lgclogin/
.lgcprofile. These files are located in the OpenWorks users home directory.
To .lgclogin add:
if ( -d ${OWHOME}/WellSeismicFusion ) then
setenv FUSION_HOME ${OWHOME}/WellSeismicFusion
set path = ( ${path} ${FUSION_HOME}/bin )
endif
To .lgcprofile add:
if [ -d ${OWHOME}/WellSeismicFusion ]; then
FUSION_HOME=${OWHOME}/WellSeismicFusion
export FUSION_HOME
PATH=${FUSION_HOME}/bin:$PATH
fi
After editing either the .lgclogin or .lgcprofile, be sure to source the edited file prior to starting
Fusion.
Connecting to GeoProbe projects (Linux/Solaris Only)
To successfully connect to your GeoProbe projects, you need a $HOME/.geoprobe_prefs/

projects.dat file. The projects.dat file is a GeoProbe-generated file that Fusion reads to get a list of
GeoProbe projects. The projects.dat file is automatically created by GeoProbe.
The GeoProbe/Fusion connection was developed in conjunction with several clients. The addition
of GeoProbe access broadens the range of visualization options while working to tie wells to
seismic data. The combination of viewing seismic data in SeisWorks/PowerView and Fusion for
2D views and now GeoProbe for 3D views increases insight into the data and decreases workflow
time. The GeoProbe/Fusion connection was designed primarily to supplement the existing
workflows requiring OpenWorks and SeisWorks. The GeoProbe/Fusion connection is not intended
to replace the need for SeisWorks. The Fusion-GeoProbe integration was only designed to work
with an associated SeisWorks project. Please contact Landmark support for options to use
GeoProbe with Well Seismic Fusion without SeisWorks.

Updating the OpenWorks launcher (Linux/Solaris Only)
The OpenWorks menu item for Well Seismic Fusion was not included in the 2003.12.4.0
distribution set and must be added separately to the OpenWorks Launcher. To include an entry for
the Well Seismic Fusion menu item in the OpenWorks Launcher, add the following line between
the WellBore Planner and Z-MAP Plus entries in the OpenWorks launcher.dat file. The
launcher.dat file is located in the OpenWorks users home directory.
[tab]Well Seismic Fusion[tab]Fusion.sh 2>$HOME/run/WellSeismicFusion.err 1>&2 &
Ensure that you place a tab before the quoted Well Seismic Fusion. Otherwise Well Seismic
Fusion will appear in the main part of the OpenWorks Launcher (i.e. at the same level as Project,
Data and Applications). The edited launcher.dat file should appear as shown below:
...
Wellbore Planner WellborePlanner 2>$HOME/run/WellborePlanner.err 1>&2 &
Well Seismic Fusion Fusion.sh 2>$HOME/run/WellSeismicFusion.err 1>&2 &
Z-MAP Plus / Contouring Assistant ZMAPPlus 2>$HOME/run/zmap.err 1>&2 &
...
Set optional environment variables
Some of the seismic processing algorithms in Fusion require scratch disk space. By default
Fusion writes its scratch files to your SeisWorks Project Home/Fusion/scratch directory.
If you want to override this default location, you need to link the scratch directory to where you
would like the scratch files to be written. Alternatively you can set the environment variable
FUSION_TABLEDATA_DIR to point to where you want Fusion to write the output prestack,
scratch, and crossplot data.
If you set the FUSION_TABLEDATA_DIR environment variable after a Fusion project has been
created, then you must manually move the existing SeisWorks Project Home/Fusion
directory to the location pointed to by the environment variable.
System administrators may want to set FUSION_TABLEDATA_DIR in each users .lgc_login in

order to keep all prestack related data in a common location. Refer to FAQs 21, 68, and 69 for
more information on the FUSION_TABLEDATA_DIR environment variable.
If you want to use Fusion to access ProMAX gathers that span onto secondary storage, you need
to tell Fusion where the ProMAX config_file is located. You can point Fusion directly to the
config_file by setting the PROMAX_ETC_CONFIG_FILE_HOME variable. For more
information consult the Fusion FAQs located on the main menu, Help > Well Seismic Fusion >
FAQs.

The LGC_DATA_HOME environment variable can be set to a user-specified path for storing the
files output by most DecisionSpace applications. The default location for LGC_DATA_HOME is
C:\DocumentsandSettings\[username]\Landmark\DecisionSpace on Windows XP and [userhome]/
Landmark/DecisionSpace on Linux and Solaris. The files controlled by this variable include
output message logs, session files, image files (.jpg, .bmp, .tif, etc.), annotation data, and UI
defaults. Colorbars are in [UserHome]/.lgcpalettes. For more details, please refer to the Where the
Output Messages and Files are Stored section of the Post-Installation Notes.
On Solaris, online help will not work if you do not have Netscape in your path. If Netscape is not
in your path, then you can create a link in FUSION_HOME/bin. The format of this link is ln -
s /usr/dt/appconfig/netscape/netscape $FUSION_HOME/bin/netscape.
The LGC_JAVA_XMX environment variable can be set to a user-specified amount of memory

when the default value of 1024 Mb is insufficient. LGC_JAVA_XMX specifies how much heap
memory is reserved specifically for the Java Virtual Machine (JVM), as opposed to the memory
available for non-Java or native code. The larger the XMX value, the more efficiently Fusion can
run. If your system has over 2Gb of memory, you should consider raising this value. If you change
this variable value, the value should be defined in the form:
2048m
where m stands for megabytes, k for kilobytes, and no letter stands for bytes. If the
LGC_JAVA_XMX value is set too high, you may get an OpenGL error message if you are running
AssetView. If this happens, try setting LGC_JAVA_XMX lower until the message no longer
appears.
The LGC_JAVA_XSS environment variable specifies how much stack memory is reserved for
each interface or processing thread spawned by Fusion. The default value is 400k.
If you notice Fusion performing slowly, you may want to set

FUSION_RECOVERY_MESSAGES to loud. This will turn on a diagnostic error dialog that
will pop up whenever Fusion encounters an unknown situation. By default
FUSION_RECOVERY_MESSAGES is set to quiet and all unknown error messages are simply
written to the default error log file. Below are the options for error display dialog:
quiet: (default or other values) Do not show recovery dialog, log errors in the output log
file.
loud: Show the recovery dialog with options to continue, exit or see error exception details.
fallout: log error and immediately exit Fusion.
Environment variables can be set as described in Configuring the OpenWorks Environment

(Linux/Solaris Only) on page 13.

Standard Landmark environment variables include:
FUSION_HOME
LM_LICENSE_FILE
OWHOME
ORACLE_HOME
ERR_LEVEL default = 3
LGC_DATA_HOME
Optional environment variables include:
LGC_JAVA_XMX default = 1024m [amount of Java-Heap memory given to Fusion]

LGC_JAVA_XSS default = 400k [amount of stack memory reserved for each thread]
FUSION_SEISMIC_HOME default = ${USERHOME}/Fusion
FUSION_TABLEDATA_DIR default = SeisWorks Project Home/Fusion
FUSION_HELP_FILES_ROOT default = ${FUSION_HOME}/help
FUSION_LAS_HOME default = ${FUSION_HOME}/data/las
FUSION_LOGM_HOME default = ${FUSION_HOME}/data/logm
FUSION_NO_OPTIMIZE1 default = false [turns off some threading]
FUSION_GC_PRINT default = false [print out java garbage collection activities]
FUSION_RECOVERY_MESSAGES default = quiet [display error pop up dialogs]
Environment variable for running on Red Hat 9
In order to run Fusion on OpenWorks 2003.12 in a Red Hat Advanced Workstation 3.0 update 6
environment, Fusion automatically sets the following environment variable:
setenv LD_ASSUME_KERNEL 2.4.7
Setting this environment variable outside of the startup script will affect any of the 32-bit
Landmark applications.
Where are the output messages and files are stored
Session files
Session files are stored under your USERPROFILE directory or in your LGC_DATA_HOME
directory. Typically these are [userhome]/Landmark/DecisionSpace on Linux/Solaris,
C:\DocumentsandSettings\[username]\Landmark\DecisionSpace on Windows XP.

Error messages and files
On Linux, if you have configured your launcher.dat as described in these release notes, the output
messages are written to your [userhome]/run/WellSeismicFusion.err file. On Windows,
output messages are written to the console window. Each time you start a new session the previous
.err file is overwritten.
Changing the error messages reporting level
To change the diagnostic error level printout, you need to edit your [FUSION_HOME]/config/
logging.properties file. Valid values are:
ALL - show all log messages

FINEST - show highly detailed tracing log messages
FINER - show fairly detailed tracing log messages
FINE - show tracing log messages
INFO - show general informational log messages
WARNING - show only log messages that indicate a potential problem
SEVERE - show only log messages that indicate a serious failure
OFF - show no log messages
The default logging property level is INFO..
Note
It is extremely helpful to rename and save this file for later analysis if you experience problems
while running Well Seismic Fusion. Please rename and save this file before restarting Fusion,
or this file will be lost.
To change the OpenWorks diagnostic error level, you need to change the ERR_LEVEL
environment variable as described below:
4 - No errors reported for OpenWorks programs

3 - Severe or fatal errors
2 - Potentially serious errors
1 - Warnings
0 - Full history of all OpenWorks routines called
The default ERR_LEVEL is 3.

Sticky parameters
Fusion keeps track of your parameter selections on a project-by-project basis. For example, if you
key in a set of Backus averaging parameters for a set of log curves, Fusion will remember your
parameter selection and the next time you run the Backus averaging algorithm, your previous
parameters will be used as the default parameters. These are known as sticky parameters.
Sticky parameters are kept in a file called SerializedProperties in the [OW_PROJ_DATA]/

project name/Fusion/user name directory. If you are working offline, or if you have not
yet selected an OpenWorks project, Fusion keeps your sticky parameters in a file called
SerializedProperties in your [USERPROFILE]/Fusion directory. For more global type sticky
parameters (like the path to your session files), Fusion keeps them in [USERPROFILE]/.java/
.userPrefs/com/lgc/infra/persistence/session/io/fs/prefs.xml. On Windows, the global sticky
parameters are kept in the registry at:
HKEY_CURRENT_USER\Software\JavaSoft\Prefs\com\lgc\infra\persistence\session\io\fs.
Fluid substitution property files
Fluid substitution properties files are saved under [OW_PROJ_DATA]/project name/Fusion/

user name. If you are working offline (outside of OpenWorks), the properties file is saved to your
[USERPROFILE]/Fusion directory. Typically this is /[userhome]/Fusion on Linux or
C:\DocumentsandSettings\[username]\Fusion on Windows XP.
Fusion computed log curves
Fusion computed log curves are stored in memory until you select to save them to the OpenWorks
database via File > Save Data or Data > Save Data.
Fusion computed synthetic seismograms and other Fusion-processed seismic data
Fusion stores its output prestack seismic data in the SeisWorks Project Home/Fusion data
directory unless you have reset the this location via the FUSION_TABLEDATA_DIR
environment variable. This directory is also where Fusion keeps its pointers to all of the pre-
existing prestack seismic data for the active project. The prestack pointers are kept in an index file
called ScannedDatasets.xml. If you want, you can link this directory to a filesystem with more disk
space.
Configuring the PD (Pointing Dispatcher) Variables for Windows
When you launch Fusion from the OpenWorks command menu on Linux or Solaris, you
automatically have PD configured correctly. However, on Windows, PD variable(s) must be set on
both the server and the client in order for Fusion to communicate in real-time with SeisWorks,
PowerView, and GeoProbe. For information on configuring PD, please refer to the OpenWorks
installation notes or contact Landmark support.

Printing from Acrobat Reader
These Release Notes are in pdf format and can be accessed online using Help > Release Notes.
You must have Adobe Acrobat Reader installed. The release package includes an Adobe
Acrobat Reader CD.
It may be simpler for you to print these Release Notes than to use them online while you are trying
to install. When printing ranges of pages in 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 viewing. 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 section from the Release Notes, follow a procedure similar to the following:
1. In the bookmark pane of Acrobat, select the name of the section that you want to print.
2. Note the page number in the status bar.
3. Display the last page in the section.
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 section.
Note
For Acrobat Reader to function properly on some Linux installations, you must the
environment variable LANG equal to C. (setenv LANG C)

Displaying Acrobat Reader help from your Linux browser
Ensure that you have Adobe Acrobat Reader loaded on your Linux system. The latest version of
Acrobat Reader is available via a free download from www.Adobe.com. After installing Acrobat
Reader, ensure that the executable is in your path. For example:
cd /usr/bin
ln -s acrobat_install_directory/bin/acroread acroread
1. From Mozilla 1.7+ (or Netscape 7.0+) select Edit > Preferences.
2. Under Navigator > Applications, add an entry for PDF file and change the Handled By
column to acrobat_install_directory/bin/acroread %s.
This will allow your browser to launch Acrobat Reader in order to read pdf files. Depending
on your version of Mozilla, you may or may not need the %s in the Handled By column.
If you want the pdf file to be displayed within your browser, you will need to install a pdf-
reader plug-in on your browser. Most media plug-ins are available for free on the internet.

The Well Seismic Fusion Workflow

Fusion is divided into five categories: Data Loading, Data Conditioning, Data Modeling, Data
Analysis and Data Reconnaissance. These tools have been tightly integrated into the classic
Landmark application suite as well as integrated into the DecisionSpace environment.
The core functionality of this release includes the following:
Display and condition velocity and density (Vp, Vs, and ) logs
Display the appropriate prestack and poststack traces
Generate brine, oil, and gas fluid substitution velocity and density logs
Generate offset and zero-offset synthetic gathers
(This includes synthetics for the brine, oil and gas cases)
Generate 3D intercept, gradient, and fluid volumes
Tie intercept and gradient volumes with synthetic models
Observe trends from 1D to 4D and across multiple wells
Perturb the fluid substitution models and perform crossplot analysis on the results
Some specific Fusion workflows include:
Workflow 0: Prestack data staging on page 21

Workflow 1: Quick look gather analysis on page 22
Workflow 2: Quick forward modeling of anomaly on page 23
Workflow 3: Tie the well to the seismic on page 24
Workflow 4: Fluid substitution modeling on page 25
Workflow 5: Seismic data conditioning on page 26
Workflow 6: Attribute volume generation on page 27
Workflow 7: Prestack Amplitude Scaling on page 28
Workflow 8: Multi-well Trend Analysis on page 29
Workflow 9: 1D to 4D Amplitude Viewing on page 30
Workflow 10: Lithology and fluid reconnaissance on page 31
Workflow 0: Prestack data staging
This workflow is typically performed by a professional data loader. In this workflow, the data
loader creates an index file that associates the prestack data numbering and grid with the poststack
(SeisWorks) numbering and grid.
The goal of this workflow is to provide the SeisWorks interpreter rapid access to prestack data.

Workflow 1: Quick look gather analysis
This is a very quick workflow to check for an AVO response of the gathers at an anomaly. This is
also a quick check for processing artifacts at an anomaly.
The goal is to check if the poststack amplitude anomalies look interesting/valid on the prestack
gathers.
This workflow assumes that Workflow 0: Stage the prestack data has already been completed!

Workflow 2: Quick forward modeling of anomaly
Vp Vs
Pseudo Logs
Offset Synthetic Real Gathers
Igneous Carbonate
Brine Sand
ln (velocity)
Shale
.5 ln ()
Gas Sand
Shale Brine Sand
Coal
ln (density) or Vp/Vs
Reflection Coefficient
Brine Sand
Gas Sand 5%
Gas Sand 80%

Incident Angle
This workflow is also known as half-space modeling. This workflow is a quick-look LFP
analysis (where LFP stands for lithology-fluid prediction) or poor-mans fluid substitution. First
the Vp, Vs, and density of brine, oil, gas, and shale content are modeled. You then look for
separation of fluids and lithologies in the crossplots. You also look for similarities between the
synthetic gathers and the real gathers.
The goal is to quickly-qualitatively understand the effect of reservoir properties on the seismic
response. If this looks promising, you should continue on to the full fluid-substitution modeling
workflow.

Workflow 3: Tie the well to the seismic
Calibrated Zero Offset Synthetic
Wavelet Selection / Extraction
Real Gather
Backus averaged Backus averaged

reflectivity series reflectivity series
The purpose of creating synthetics is to calibrate nearby seismic data using log data obtained from
a well. This workflow is designed to properly tie your well(s) to your seismic. This workflow is
necessary for any well-seismic analysis on real data because it allows you to properly calibrate
your depth well data with your time seismic data.
The goal is to properly tie the seismic and well data before you begin to analyze their relationship.
If this step is not properly performed, then the entire Fusion analysis may be invalid!

Workflow 4: Fluid substitution modeling
Virgin Curve
Fluid Substitution
Brine Gas Oil
Compare
Offset Synthetics Real Gathers
The goal of this workflow is to understand the effects of fluids in the basin, prospect area, or
stratigraphic interval. You do this by more accurately defining to what extent the seismic offset
response can recognize fluid and lithology changes.
If this modeling response looks promising, then you need to properly condition your prestack data
and generate a set of AVO (amplitude versus offset) stacks.

Workflow 5: Seismic data conditioning
Moved-out, datum corrected, CMP gathers
Decimating, partial stacking
Time Shifting, event alignment
Frequency matching, spectral balancing
Phase matching
Amplitude balancing
Prestack data properly conditioned for quantitative AVO analysis
During Fusion interpretation, you must remember that seismic amplitudes themselves are NOT
reflection coefficients. Seismic amplitudes are affected by a large range of factors. If a Fusion
analysis is going to be successful, the seismic data must be processed in such a way as to eliminate
the effect of these factors as much as possible. That is to say, without properly conditioned/
matched input data, the quantitative LFP analysis is meaningless!
The goal of this workflow is to prepare the seismic data for proper quantitative AVO analysis.

Workflow 6: Attribute volume generation
Brine Gas Oil

Real and Computed Logs Offset Synthetic(s)
Shale / background
Oil
Brine
Intercept and Gradient (and other) Stacks

Crossplot Analysis
AI
Various Attribute Horizons GI

Fluid Stacks
The goal of this workflow is to define a background trend (aka. shale trend) and then define
lithology and fluid trends (angles). With these angles, you can generate many fluid stacks. You
can keep re-stacking the volume until you feel you have arrived at the optimal angle for the stack.
(Care must be taken to avoid any lithology changes in the noise/background trend of the data.)

Workflow 7: Prestack Amplitude Scaling
The goal of this workflow is to truly match the prestack data to the well data. A true match includes
matching the wavelet, matching the intercept, and matching the gradient.

Workflow 8: Multi-well Trend Analysis
The main goal of this workflow is to find multiple ways to discriminate pay from non-pay in a 2D
crossplot. A secondary goal is to determine how your reservoir attributes are affected by depth.

Workflow 9: 1D to 4D Amplitude Viewing

Reflection Coefficient
Brine Sand
Gas Sand 5%
Gas Sand 80%

Vp Vs
Incident Angle
[half-space models] Pseudo Logs
[1D models]
Offset Synthetic
[2D models]
Igneous Carbonate
Shale
.5 ln ()
Brine Sand
Coal

[2D crossplots]
Prestack Gathers
[3D models]
- =
[old seismic] [new seismic] [4D analysis]
In some domains fluids separate, while in other domains lithologies separate.
The goal of these workflows is to quickly, qualitatively understand the effect of reservoir
properties on the seismic response.

Workflow 10: Lithology and fluid reconnaissance
The goal of this workflow is to identify any fluid or lithology type, anywhere in the 3D volume.
This is done by identifying points in the crossplot and broadcasting or spraying those points to 2D
and 3D space. Once the points are in 3D or map space, you can then identify the biggest prospects.
Of course you can always QC the gathers that produced the anomalous fluid or lithology attribute.

Running Fusion
Well Seismic Fusion is launched by selecting Applications > Well Seismic Fusion, from the
OpenWorks launcher.

Content-based help is available from the main menu, Help > Well Seismic Fusion > Contents.
Workflow-based help is available from the main menu, Help > Well Seismic Fusion > Tutorial.
Frequently asked questions are available from the main menu, Help > Well Seismic Fusion >
FAQs.
Dialog-level help is also available, using the Help buttons from any dialog.

New Features
The following new features were added for the R2003.12.4 release of Fusion.
Support for processing and crossplotting of 2D stacked and prestack

data
Fusion now supports processing, picking, crossplotting, wavelet extraction, and synthetic
modeling of 2D seismic data. This is very useful when you do not have 3D data and when
your evaluating large basins.
Support for Roy White wavelet extraction
Fusion now allows for Roy White / SeisWell based wavelet extraction on stacked and
prestack data. The Roy White algorithm appears more robust than the Spectral Division and
the Wiener algorithms. This tool is critical for checking the phase and polarity of your 3D
seismic data. The calculated wavelets can be written to the OpenWorks database. This
makes the Fusion-generated wavelets available to other OpenWorks-based applications.
Seismic processing enhancements
Fusions processing algorithms now have the ability to append to existing seismic volumes.
This very useful when creating large output volumes that you want to quality check.
For AVO processing, Fusion now allows you to use the X/Y values from the SeisWorks
grid instead of the values from the prestack trace headers. You tell Fusion to use the
SeisWorks grid by setting the java property
com.lgc.fusion.seisdata.SeismicManagerImpl.useSeisWorksXY=t in the
$FUSION_HOME/etc/java.properties file. This is a valuable feature when your processing
shop has processed the data with a different measurement system than you SeisWorks grid.
(defect 719233)
Fusion now allows you to browse to new ProMAX prestack datasets based upon their name
instead of their 8-digit hash number.
Fusion now supports the JavaSeis prestack seismic format. This format is very fast and
efficient for parallel processing.

Support for composite trace generation and wavelet extraction along

deviated wellbores
Fusion has a new seismic stacking algorithm titled Composite Trace. This algorithm
generates a single composite trace along the wellbore, in seismic and in log curve formats.
The algorithm can also generate a volume of composite traces along the wellbore in seismic
format.
This is very useful when tying deviated wells to your seismic.
Usability enhancements
Fusion now allows you to edit existing polygons in the crossplot.
Fusion now allows you to move existing polygons in the crossplot.
Fusion now allows you to force the crossplot regression through the origin. (defect 725175)
Fusion has added iso-angle and AVO classifications colorbars to the standard Color Editor
menu. Previously you had to import these specialized colorbars. (defect 724973)
Fusion now properly handles null traces in the viewer. (defects 731709 and 627347???)
The crossplot is now up to 30% faster. (defect ?????)

The icons have been updated to be the same as all the other DecisionSpace applications.
(defects 728411, 728433, 728571, 728572, 728585, 728590, 728593, 729330, 729333,
729378, 729527, 729531, 731376, 731807, 732032, and 732980)

Fixed Problems
The following list describes behaviors and problems that were fixed in the R2003.12.4 release of
Fusion.
Trace header plots are now redisplayed in restored sessions.
Can no longer create multiple display tracks with the same name. (defect 730426)
Can now launch across network when LD_LIBRARY_PATH has not been properly set.
(defect 729551)
The following list describes behaviors and problems that were fixed in the R2003.12.3.1 release of
Fusion.
Fusion can now write a CDP coverage horizon that straddles the SeisWorks project
boundary. (defects 716205 and 625516)
Fusion now handles invalid trace mute header values for TLIVE_S and TFULL_S in
SEG-Y datasets. (defect 633962)
Fixed some problems with gather display when the user navigates outside the range of the
data. (defects 723488 & 723494)
Fixed several restored session and version compatibility errors. (defects 726160, 726422,
726500, & 727080)
Fixed issues related to not being able to launch seismic algorithms when the
SerializedParameters have bad values. (defects 728434 & 725846)
Multi-well crossplot can now produce a plot when no composite curves are available.
(defects 729076 & 725281)
Fusion can now launch across the network with an improperly updated library path. (defect
729551)
The stack seismic versus stack seismic crossplot has been disabled for arbitrary line
displays. (defect 724226)
Fixed issue that certain T-D curves can cause the synthetic to be overstretched at the bottom
of the curve. (defect 728466)
Fusion can now generate a proper attribute header plot when the plotted gather is not full
fold. (defect 730474)
Fusion can now generate a proper offset synthetic when the model gather is not full fold.
(defect 731566)

The following list describes behaviors and problems that were fixed in the R2003.12.3.0 release of
Fusion.
Fusion can now properly handle network configurations that dynamically place dots in the
directory path. (defect 628303)
Note
If the sticky parameters of the last run of Prestack Data Scanning Wizard is from
R2003.12.2.1 or earlier, the sticky parameters may still contain the /.automount/ in the
filepath of the last prestack file scanned, and therefore the file/location listed by default in the
Wizard.
In order to purge the /.automount/ from the Wizard, the user will need to start anew by browsing
all the way to the root level and then mine down to the location of the prestack to have this fix
work properly.
Mining in the upwards direction from the default sticky parameters will still carry the /
.automount/ in the Wizard and thus write the /.automount/ out in the file name in
ScannedDatasets.xml.
Fusion can now properly handle Oracle projects that have long, dashes, or dots in their
OWSYSSID name. (defects 716104, 628071 & 180588)
You can now launch Fusion and browse through prestack gathers in a measurement system
that is not the same as your selected SeisWorks project. However, the spatial units of the
selected measurement system MUST match the spatial units of the prestack data in order
for the seismic processing and synthetic algorithms to work correctly. Hence, Fusion does
not automatically convert the units of prestack data. This is because prestack data does not
contain the unit of measurement in its data store. Therefore, for seismic modeling purposes
Fusion always uses the horizontal and vertical units of the selected measurement system. If
the selected measurement system does not match the values in your seismic trace headers,
then your modeling will not be valid. (defect 714887)
On Linux, the Fusion user interface was observed slowing down after displaying large
amounts of data. We also observed the user interface responding much slower on either the
left or right screen. This was a buffering problem with the X11 graphical display engine.
(defect 698299)
The crossplot no longer treats null log data as real data. (defect 174013)
Fusion can now restore sessions, even if the session color bars are missing. (defect 699368)
Fusion now allows you to navigate, PD, and display gathers when the Fusion selected
measurement system has a different linear distance of the measurement than the SeisWorks
grid.

For example, if your selected measurement system is US Oil Field Metric Depth and your
SeisWorks grid is defined in meters, then PD will not work because the measurement
system has a linear distance of feet and Fusions PD does not convert the X, Y locations
from feet to meters. The workaround is to change the measurement system to SPE Preferred
Metric (or some other measurement system which has linear distance of meters). If you do
not like the log units that come with SPE Preferred Metric, then you can define a custom
measurement system. For example, you could define a measurement system based on US
Oil Field, but change the linear distance to meters (and possibly change the depth
measure to meters). (defects 706567)
The following list describes behaviors and problems that were fixed in the R2003.12.2.1 patch
release of Fusion.
Fusion will now read ProMAX prestack datasets that have their Stack Flag improperly
set to yes. (defect 628785)
Fusion can now read ProMAX prestack datasets that have their Inline and Crossline
numbers in non-standard ProMAX trace header locations. To tell Fusion where the non-
standard header locations are, you need to edit the $FUSION_HOME/etc/java.properties
file. Details of what to edit are commented in the file. (defect 625280)
Fusion can now read SEG-Y prestack data that has its number of traces per ensemble
improperly set as if it were stacked data. (defect 628564)
Fusion can now read SeisWorks horizons that have corrupt colors. (defect 630380)
Fusion can now properly access OpenWorks projects that have corrupt time-depth curves
and corrupt log curves. (defects 625797 and 635466)
Fusion performs better when adding and deleting tracks from the Well Seismic Viewer.
(defects 634164, 634306, 634292, 634295, 634264, 634289, and 634979)
Cancelling out of the Edit Wiggle Color dialog no longer causes the Well Seismic Viewer
to lock. (defect 633299)
The Fusion Viewer Control dialog is now in sync with track title changes made in the Well
Seismic Viewer. (defects 633624 and 627957)
The Data Display Preferences dialog will no longer appear every time you PD a new
location from SeisWorks or GeoProbe, as long as you have seismic data displayed in a
track. (defect 635443)
Fusion no longer requires polygons to include points from every crossplot dataset in order
to PD selected points to SeisWorks. (defect 635457)
Fusion no longer allows users to graphically set zero or negative display track widths.
(defects 635469)

The normal incidence synthetic reflection amplitudes now match the offset synthetic
reflection amplitudes. (defect 619825)
Fusion now properly displays fluid substitution error curves for first time users. (defect
635447)
Sorting columns from the Data Display Preferences dialog no longer causes the sorted
curves to be improperly named. (defect 635463)
Fusion can now save sessions when the Fusion Viewer Control dialog has been closed via
the X in the upper right hand corner. (defects 635230 and 635453)
Fusion no longer allows the user to overwrite their input seismic data. (defect 617546)
Fusion now allows for 500 input SEG-Y datasets per logical SEG-Y volume. (defect
628306)

Known Problems
The following list describes behaviors and problems that the Well Seismic Fusion team has
identified as being bothersome to users. This is not a comprehensive list of all the known problems
in the product.
Installation Issues
Do not upgrade over a previous version of Fusion. You should install the new version
over the old version.
You must manually add Fusion to your path and to the OpenWorks launcher bar.
On Linux/Solaris, Fusion requires a bash shell in order to launch. The bash shell is part
of the full install of the operating system.
Refer to the R2003.12 release notes for any issues concerning the CD installer application
on Linux.
If you are running RedHat 9.0 or any other unsupported platform, you may need to set
LD_ASSUME_KERNEL as described in Environment variable for running on Red Hat
9 on page 16.
OpenWorks Issues
Fusion no longer supports OpenWorks 2003.3.
The input log curves must have valid (non-null) values for the Value Storage Uom. You
can set the Value Storage Uom within Fusion via Tools > Log Curve Algorithms >Set Units
for Log Curves.
Log curve unit values can also be edited via the OpenWorks utilities Well Data Manager
or via the OpenWorks Special Units Editor.
The input log curves must have a valid Curve Unit Type defined in the OpenWorks
Curve Dictionary. You can set the Curve Unit Type within Fusion via Tools > Log Curve
Algorithms >Set Units for Log Curves and when outputting a new log curve.
Alternatively, you can set the Curve Unit Type via the OpenWorks Curve Dictionary.
A valid OpenWorks wellbore is required to run Fusion. This wellbore is used for saving
Fusion created log curves or synthetic data to OpenWorks.

If you are running Fusion, then you delete a log curve from OpenWorks, you cannot display
the curve you just deleted. If you try to display the curve that was just deleted, the Well
Seismic Viewer becomes unstable. (defect 617678)
If you create a new time-depth curve within Fusion, the newly created time-depth curve is
not available for use until you click the Refresh choices button on the Data Preferences tab
of the Fusion Viewer Controls dialog. (defect 619087)
OpenWorks autocompositing of log curves is not enabled in the majority of algorithms

within Fusion. OpenWorks autocompositing is only enabled when selecting curves by
name in the multi-well crossplot. (defect 159245)
In the Well Seismic Viewer, the OpenWorks time-depth conversion preference has not
been implemented in this release. However, you can use any 3D TDQ or DepthTeam
Express velocity models in the seismic processing algorithms. (defect 518028)
Fusion will not be able to initialize if you select a user-defined OpenWorks Measurement
System that has UNKNOWN or missing unit definitions in the selected measurement
system. (defects 618300, 614485)
The workaround is to manually edit out any undefined units or to copy the user-defined
Measurement System into a new Measurement System using the OW2003.12.1.0
Measurement System Manager.
License checkout failure and other immediate license error/warning messages do not
appear when running Fusion on Solaris. (defect 625159)
Graphical User Interface (GUI) Issues
The Fusion user interface is not supported and has not been optimized to run under remote
display emulators, such as Exceed. You can expect very slow GUI performance via Exceed.
For running Fusion on Windows, we recommend running the native Windows version of
Fusion, rather than running the UNIX or Linux version of Fusion over Exceed.
Because of Java system memory garbage collection, the Well Seismic Viewer becomes
slow when you are near the maximum allocated Java Heap Memory. We recommend that
you increase how much memory you allocate for Fusion by adjusting the
LGC_JAVA_XMX environment variable. By default this is set to 512M. To improve
performance, we recommend increasing the value to 1024M, but only for machines with
2Gb of memory or more.
The Well Seismic Viewer will also become slow when you run out of available RAM and
begin swapping memory to and from disk.
Hint: The java memory usage is continuously reported in the lower left portion of the Well
Seismic Viewer.

When running Fusion over a remote display (thin or thick client) you should always change
the host window behavior to Display content in moving windows = NO and Display
content in resizing windows = NO. By turning off the display of moving windows, you
will save many screen redraws and your local display will be faster. For Gnome on Red Hat
Advanced Workstation 3.0 you must launch System Tools > More System Tools-
>Configuration Editor and in the GConfig Editor window select App > Meta City >
General. On the right side of the window, scroll down to Reduced Resources and click
the check box next to it. This will convert all window to wire frame on move and redraw,
thus eliminating the undesired behavior.
The Well Seismic Viewer does not display the distance between the active wellbore and the
displayed seismic gathers. (defects 306710, 619929)
Fusion will not be able to launch help from Advanced Workstation 3.0, if you are pointing
to an OpenWorks 2003.12.0 installation. If you include /lib in your LD_LIBRARY_PATH
definition before $OWHOME/lib you will be able to see Fusions help dialogs. (defect
522024)
A less intrusive workaround to this issue follows:
1. Copy your /usr/bin/mozilla script to $FUSION_HOME/bin/mozilla_WSF

2. Edit this mozilla_WSF file by adding the /lib directory to the LD_LIBRARY_PATH
definition as previously suggested.
3. Edit the $FUSION_HOME/bin/Fusion.sh script adding a line that sets
FUSION_BROWSER in the line just under the PROCESSOR setting near the top of the
file.
export FUSION_BROWSER=${FUSION_HOME}/bin/mozilla_WSF
When the user launches Netscape for the first time in Solaris, two windows pop up: The
Solaris User Registration window and the License agreement window. The user has to click
OK on these windows in order to use the browser. If the user hasnt done this and tries to
launch the Fusion help, Netscape will not come up. The user has to launch the browser from
somewhere other than Fusion first. (defect 623339)
If help does not appear on Solaris, you may need to create a link in /usr/sbin to wherever
you have Netscape installed. From /usr/sbin, the link command would look like ln -s /
directory/where/installed/netscape netscape.. An alternative solution is to
create a link in FUSION_HOME/bin. The format of this link is ln -s /usr/dt/
appconfig/netscape/netscape $FUSION_HOME/bin/netscape.
The name of the colormap listed on the Viewer Controls dialog may not match the actual
displayed colormap, if the displayed colormap has been opacity edited and changed from
the default colormap. (defect 706323)
When selecting items from a dropdown menu on Linux, depending on your window
manager configuration, you may need to hold down MB1 in order to keep the list from
disappearing before you select an item from the list.

Fusion no longer supports true horizontal scale in the tracks of the Well Seismic Viewer.
(defect 718985)
To be sure to get the orientation of the displayed gathers correct, you must have an active
stack volume specified. (defect 719575)
Session Issues
Saved sessions from previous versions of Fusion may not be 100% compatible with the
2003.12.4.0 version of Fusion. However, data from previous versions of Fusion should be
100% compatible.
If the default SID is not accessible on the network, Fusion appears to hang until Oracle
times out.
If your session runs out of memory, you will need to increase the amount of memory you
are allocating for Fusion. This is done via the LGC_JAVA_XMX variable as described in
Set optional environment variables.
You can only set the measurement system and OpenWorks project during Fusion
initialization. (defect 518523)
Once you have launched a Fusion session, you cannot open a new or saved session unless
you first exit Fusion. (defect 521984)
Using certain special characters (such as \ = ;) in data names can cause problems in sessions
and other saved files.
ProMAX velocity tables are only available if you manually insert them into your SeisWorks
Project Home/Fusion/TableData project directory. Refer to the online FAQs on how to
add your 3D velocity tables to Fusion.
Due to permission issues, Fusion can crash during initializing a session. (defect 727078)
Seismic Data Issues
Fusion cannot process memory-only seismic data. This means that before you try to stack
an offset synthetic, the synthetic needs to be saved to disk. (defect 719067)
For proper tracking between prestack and poststack data, Fusion requires valid values for
inline and crossline in the prestack trace headers. To be valid, the inline and crossline trace
headers must match the SeisWorks grid of inline and crossline numbers.
For ProMAX data, inline and crossline default to header words ILINE_NO and
XLINE_NO. You can change the default locations by editing the $FUSION_HOME/etc/

java.properties file.
You can also dynamically edit the prestack trace headers within Fusion via the JIT Trace
Header Math tool.
The prestack inline/crossline/x/y values MUST match your poststack SeisWorks inline/
crossline/x/y values for proper seismic processing with 3D velocity models [this includes
synthetic seismic generation]. If the x/y values in the trace header do not match, you can
use the x/y values from the SeisWorks grid by setting the java property
com.lgc.fusion.seisdata.SeismicManagerImpl.useSeisWorksXY=t.
The spatial units of the selected measurement system MUST match the spatial units of the
prestack data. Hence, Fusion does not automatically convert the units of prestack data. This
is because prestack data does not contain the unit of measure in its data store. Therefore,
for seismic modeling purposes Fusion always uses the horizontal and vertical units of the
selected measurement system. If the selected measurement system does not match the
values in your seismic trace headers, then your modeling will not be valid.
SEG-Y prestack data MUST have the inline and crossline numbers properly mapped in the
SEG-Y headers.
The fundamental sort order of the prestack gathers must be CDP.
When scanning prestack SEG-Y data, you MUST set the fundamental sort order to CDP
and you must set the primary trace header to CDP for Fusions prestack navigation to work
properly.
This version of Fusion does not support the extra 128-byte header in SEG-Y rev1.
Fusion does not support using 3D velocity models when the prestack data does not have
corresponding X, Y data in the prestack trace headers. If you do not have X, Y values in
your SEG-Y trace headers, you can still use a single-value velocity function if you map
some zero-value trace header words to CDP_X and CDP_Y or you can use the X, Y values
from the SeisWorks grid by setting the java property
com.lgc.fusion.seisdata.SeismicManagerImpl.useSeisWorksXY=t.
The Fusion-GeoProbe integration was only designed to work with an associated SeisWorks
project. Please contact Landmark support for options to use GeoProbe with Well Seismic
Fusion without an associated SeisWorks project.
To successfully connect to your GeoProbe projects, you need a $HOME/.geoprobe_prefs/

projects.dat file. The projects.dat file is a GeoProbe-generated file that Fusion reads and
parses to get a list of GeoProbe projects. The projects.dat file is automatically created by
GeoProbe.
Depth gathers cannot be used for intercept and gradient calculations. (defect 623753)
Fusion does not support 2D-3D or 3D-3D merge projects.

Fusion cannot navigate or create a SeisWorks horizon of where the prestack gathers exist,
if the CDP_X and CDP_Y values in the trace headers do not fall within the associated
SeisWorks project grid. (defects 625578)
An overwrite challenge is given for a shared memory volume if there is a .vol file with the
same name. The challenge is misleading in that a shared memory volume and the .vol file
volume are not the same thing. (defect 623999)
Writing GeoProbe .vol files requires much more memory than writing SeisWorks .3dv
files. If you run into memory problems writing GeoProbe .vol files, one workaround is to
write out .3dv files instead.
You cannot perform AVO or dataset math operations on data that has different start times,
sample rates, or number of traces. (defects 718111, 718113, 717098, 717070, 718156, and
718148)
Fusion does not apply bulk shifts [specified in .msc files] to stacked 2D seismic data. This
is by design because the prestack gathers do not have bulk shifts applied.
For Fusion to run with large 2D SeisWorks projects, (> 1000 horizons per seismic dataset)
you may have to increase the number of openable files for your operating system. Linux is
installed with the number of openable files hardwired to 1024. To increase this number you
should file a help-desk ticket or tell your system administrator to increase the number to
100,000 or more. A system administrator should do this because it requires changing two
root-protected files, running a root-protected utility, rebooting, and adding an extra
command in your .login file. Please contact Landmark support for more information.
(defect 719712)
For certain SeisWorks grid orientations Fusion displays stack volumes in the opposite
direction than they are displayed in SeisWorks. (defect 719986)
Fusion cannot read .vol files greater than 2.1 Gb.
Fusion has problems stacking SEG-Y data with a non-zero start time. (defect 716262)
When there is a problem with permissions or stale/disconnected seismic directories, Fusion

reports the following error message:
java.io.IOException: Failed to find any writeable data directories in /network/user/

lgcconf/owsyssid/dir.dat
However, the problem may not be in the dir.dat, the problem could also be with the data
directory defined by the FUSION_TABLEDATA_DIR environment variable. When this
error occurs, check permissions and freshness of mount points for all data directories
defined in the dir.dat and from the FUSION_TABLEDATA_DIR.

Crossplot Issues
For performance reasons, the number of points sent to the crossplot from interactive
prestack analysis is limited to 1000 points per gather. The chosen 1000 points is a random
sampling of all the data in the crossplot analysis window. For poststack crossplotting, the
number of points sent the crossplot is limited to 1,000,000. For log data, the number of
points sent to the crossplot is unlimited. However, when you PD data out of the crossplot,
all of the original data will be broadcast out via PD.
Changes to the Z-color scale in log-log crossplots are not restored from saved sessions.
(defect 614567)
Crossplots generated and saved from memory-only data will not interact with disk-only
data displayed in the Well Seismic Viewer in restored sessions. (defects 718374 and
718385)
Well Curve Issues
Fusion hangs when displaying SeisWorks horizon in zone of well that is horizontal. (defect
700744)
Fusion currently only operates on one well at a time. (defects 519732, 619936, 518939,
619839, 159233, 159235, 159558, 614865, 615354, 614603, 522052, 521870, 159236,
521155, 623909, 618620, 622687, 520633)
You cannot set the vertical scale lines to logarithmic in the Well Seismic Viewer. (defect
518552)
Fusion-created bulk modulus and shear modulus curves are created using the unit of elastic
modulus as defined by your selected Measurement System. The Landmark provided
measurement systems have elastic modulus defined as either lbf/ft2 (pounds of force per
square ft.) or Pa (Pascals). So if you are used to viewing elastic modulus in GPa (the value
referenced in most literature) you will be unfamiliar with the Fusion-created curve values.
To get GPa, you need to edit your measurement system to say GPa.
Synthetic Data Issues
Although you can generate synthetic log curves from an OpenWorks project that does not
contain any curves or time-depth information, you cannot save these synthetic curves back
to OpenWorks. This is by design. A wellbore is required to fully run Fusion.
Using wavelets with time delays work fine if the no stretch NMO option is used, but with
NMO stretch, they will undercorrect events because the NMO is applied at the shifted/
wrong time.

LogM smooths its log curves before calculating the reflection coefficients, Fusion does not.
For most data cases, the synthetic results between LogM and Fusion should be essentially
the same. However, you may notice differences if a well is extremely noisy or has large
velocity changes in thin beds. In this case, the synthetic results will be similar if the input
logs are smoothed before generating the offset synthetic.
The synthetic generation within Fusion has limited functionality. For a more complete
synthetics analysis, we recommend using LogM or SynTool. (defects 615316, 618940,
521415, 519039, 520681, 619601, 521462, 617135, 617126, 615285, 619800)
On Solaris and Windows operating systems, you need to remove synthetics and wavelets
from the view before you delete them from disk with the Data Cleanup Wizard. (defects
721091, 721264, & 721089)
PD Issues
Fusions <Shift>MB1 communication with SeisWorks is only available in SeisWorks

version 2003.12.1.2 or higher.
Fusions <Ctrl><Shift>MB1 communication with GeoProbe is only available in GeoProbe

version 3.2 or higher.
Fusions communication with PowerViews Point Marker is only available in

PowerView version 2003.12.0.2 or higher.
In order for Fusion to PD crossplot information to SeisWorks, SeisWorks must be in PD-

receive mode. SeisWorks will have a green border around any window that is in PD-receive
mode.
Refer to the Configuring the PD (Pointing Dispatcher) Variables for Windows section for
information on how to configure Fusion on Windows to communicate with other classic
Landmark UNIX/Linux applications.

3rd Party Acknowledgments
The following information is provided in accordance with the software manufacturers terms of
usage:
Sun Microsystems: Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. 4150 Network
Circle, Santa Clara, California 95054 U.S.A.
Java Runtime Environ-
ment (JRE) Sun Microsystems, Inc. Binary Code License agreement
This product includes code licensed from RSA Security, Inc.

Some portions licensed from IBM are available at
http://oss.software.ibm.com/icu4j/

Sun Microsystems: Copyright 2002 Sun Microsystems, Inc. All Rights Reserved. 4150 Network
Circle, Santa Clara, California 95054 U.S.A.
Java Runtime Environ-
ment (JRE) Sun Microsystems, Inc. has intellectual property rights relating to technology
embodied in the product that is described in this document. In particular, and
without limitation, these intellectual property rights may include one or more
of the U.S. patents listed at http://www.sun.com/patents and one or more
additional patents or pending patent applications in the U.S. and in other
countries.
This document and the product to which it pertains are distributed under
licenses restricting their use, copying, distribution, and decompilation. No part
of the product or of this document may be reproduced in any form by any
means without prior written authorization of Sun and its licensors, if any.
Unless otherwise licensed, software code in all technical materials herein

(including articles, FAQs, samples) is provided under the (http://
java.sun.com/xml/jaxb/users-guide/examples/users-guide/License-
BSD.html) License.
Third-party software, including font technology, is copyrighted and licensed

from Sun suppliers.
Sun, Sun Microsystems, the Sun logo, Java, the Java Coffee Cup logo,
J2EE, J2SE, Java Naming and Directory Interface, Enterprise JavaBeans,
EJB, JavaServer Pages, and JSP are trademarks or registered trademarks of
Sun Microsystems, Inc. in the U.S. and other countries. UNIX is a registered
trademark in the United States and other countries, exclusively licensed
through X/Open Company, Ltd.
Federal Acquisitions: Commercial Software - Government Users Subject to

Standard License Terms and Conditions.
DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR

IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DIS-
CLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE
HELD TO BE LEGALLY INVALID.

Landmark/Asia Pacific Landmark/EAME Landmark/The Americas

11th Floor Menara Tan & Tan Hill Park South 2101 CityWest Blvd, Building 2
207 Jalan Tun Razak Springfield Drive Houston, TX 77042-3021
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- Fax: 713-839-2168
Email: apsupport@lgc.com 686 Email: support@lgc.com
Email: eame_helpdesk@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, 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.
2005 Landmark Graphics Corporation. All rights reserved.

WSF ReleaseNotes

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

WSF ReleaseNotes

Încărcat de

Drepturi de autor:

Formate disponibile

DecisionSpace

Well Seismic FusionTM

HALLIBURTON | Drilling, Evaluation and Digital Solutions

September 2006 R2003.12.4

Virgin Curve Vp Vs Density

WSF 2003.12.4 Release Notes Page 2 of 51 September 2006

About this release

Contents of the Well Seismic Fusion installation CD

DecisionSpace Media Kit Well Seismic Fusion components.

WSF 2003.12.4 Release Notes Page 3 of 51 September 2006

Well Seismic Fusion 2003.12.4.0 requires the following licenses:

Well Seismic Fusion Configuration

Adobe Acrobat Reader

*Through OpenWorks, Fusion provides access to an Oracle 8i or Oracle 9i server (Enterprise

WSF 2003.12.4 Release Notes Page 4 of 51 September 2006

Hardware Minimum for

10-500 Gb for each additional

WSF 2003.12.4 Release Notes Page 5 of 51 September 2006

Software Version for client

WSF 2003.12.4 Release Notes Page 6 of 51 September 2006

Software Version for server

WSF 2003.12.4 Release Notes Page 7 of 51 September 2006

Checklist for Linux/Solaris (OpenWorks 2003.12.0.1)

1. Install recommended Operating System:

Red Hat Linux Advanced Workstation 3.0 Update 6 (Full Installation)

or SunOS 5.8 (Operating Environment 02/02)

2. Install Oracle 9i and OpenWorks 2003.12.0.1 through 2003.12.1.3 on the server.

3. Configure OpenWorks so interpreters can see the appropriate projects.

See the OpenWorks 2003.12.0.1 through 2003.12.1.3 release notes.

See Obtaining a license to run the software on page 11.

WSF 2003.12.4 Release Notes Page 8 of 51 September 2006

Checklist for Windows

1. Install recommended Operating System.

Windows XP Professional (Service Pack 2 or greater)

2. Install Oracle Client.

3. Install Hummingbird Exceed 8+

See the installation recommended in DecisionSpace global release notes.

4. Install the OpenWorks Client.

5. Configure the OpenWorks client to see the appropriate projects.

See Obtaining a license to run the software on page 11.

8. Uninstall any previous version of Fusion installed on your system.

WSF 2003.12.4 Release Notes Page 9 of 51 September 2006

Permissions needed to install Fusion 2003.12.4.0

$OWHOME/bitmaps and its contents

The Linux/Solaris Fusion installation CD is written in OpenWorks CDINSTALL format. The CD

WSF 2003.12.4 Release Notes Page 10 of 51 September 2006

Obtaining a license to run the software

SUN/Solaris and Linux Systems

ipconfig /all (from a Command Prompt window)

WSF 2003.12.4 Release Notes Page 11 of 51 September 2006

Installing the software license

FEATURE WSFUSION licsrv 2003.000 10-jan-2006 5 AKEY42AAD7898675309F VENDOR_STRING="Ewing Oil

WSF 2003.12.4 Release Notes Page 12 of 51 September 2006

Configuring the OpenWorks Environment (Linux/Solaris Only)

Connecting to GeoProbe projects (Linux/Solaris Only)

To successfully connect to your GeoProbe projects, you need a $HOME/.geoprobe_prefs/

WSF 2003.12.4 Release Notes Page 13 of 51 September 2006

Updating the OpenWorks launcher (Linux/Solaris Only)

[tab]Well Seismic Fusion[tab]Fusion.sh 2>$HOME/run/WellSeismicFusion.err 1>&2 &

Wellbore Planner WellborePlanner 2>$HOME/run/WellborePlanner.err 1>&2 &

Well Seismic Fusion Fusion.sh 2>$HOME/run/WellSeismicFusion.err 1>&2 &

Z-MAP Plus / Contouring Assistant ZMAPPlus 2>$HOME/run/zmap.err 1>&2 &

Set optional environment variables