Professional Documents
Culture Documents
GeoProbe 3.3
Release Notes
Introduction to GeoProbe 3.3. . . . . . . . . . . . . . . . . . 2
System Requirements
IRIX . . . .................................. 3
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Kernel Configuration
IRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installation
IRIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Starting GeoProbe 3.3 . . . . . . . . . . . . . . . . . . . . . . . . 50
Enhancements and New Functionality . . . . . . . . . 51
Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
This software is protected by US Patents 6,765,570 5,570,106 5,615,751 and 6,690,820 and additional patents pending, copyrights,
and trade secrets
GeoProbe is a volume visualization and interpretation software product, designed for use in
immersive environments as well as desktop workstations. GeoProbe allows the interpreter to
quickly and easily interpret multiple seismic volumes using ezTracker, multi-attribute autopicking,
ezFault/ezSurface interpretations, and a variety of tools for advanced attribute analyses with
unprecedented speed.
GeoProbe 3.3 is a major release providing fixes and new functionality which are detailed in the
Enhancements and New Functionality section. Each new addition to the GeoProbe toolkit allows
for better and faster interpretations.
For example, Horizons can now be merged, filtered, and displayed with attributes. In addition,
there is now the ability to edit horizon points directly on the horizon surface with unlimited Undo
and Redo options. ezSurfaces and ezFaults have been enhanced to allow for style changes such as
removing the visible fault segments, showing annotation and displaying the surfaces in a faster,
non-spline mode. These *.eds surfaces can also be converted to TSurfs with just the click of a
button.
In 3.3, we now have a new object called SWFaults whereby associated fault segments from
SeisWorks can be loaded into and displayed in GeoProbe. Also, a new display option called Probe
Intersection displays Horizons, Surfaces, Faults and TSurfs as lines on the face of the active probe.
Finally, several new features are delivered in this release that improve the usability of the software,
enhancing the users experience. To name a few: volume size is now displayed in the load dialogs;
new viewer options allow for better spin control and rotatable views from the hotkeys; and multi-
object save is now available.
System Requirements
The GeoProbe system requirements are a combination of workstation model, graphics hardware,
operating system version, system settings, and installed software.
IRIX
The most basic system requirement for 3.3 IRIX is GeoProbe only runs on Silicon Graphics (SGI)
64-bit workstations. The best way to determine if an existing system can run GeoProbe is to check
the SGI system model and version of IRIX (the operating system), then work through the detailed
requirements for hardware and software.
If you are ordering a workstation to run GeoProbe, it is best to contact Customer Support for
current recommendations.
Hardware Requirements
GeoProbe 3.3 runs on SGI 64-bit supported hardware. The following table lists the tested
configurations for the current and past releases.
Note
Xinerama mode is neither tested nor supported for use with GeoProbe.
Software Requirements
One of the following IRIX versions, and its associated patch, is required to run GeoProbe 3.3.
Note
GeoProbe 3.3 was tested using IRIX Version 6.5.25. The following versions and
their associated patches are expected to work with GeoProbe, based on previous
experience and the assumption of binary compatibility.
NOTE
To determine the IRIX version of an existing system, type the following command in a shell
window.
% uname -R
To determine the IRIX patches of an existing system, type the following command in a shell
window.
Internet Browser
Mozilla 1.6 or higher is the supported html browser for GeoProbes online help. Please contact
Landmark Support for this executable if it is not already on your system.
In addition, this browser must appear first in the your PATH environment variable. If the system
already has an older version of Mozilla on it, you will need to rename the older version and create
a symbolic link to the new version. For example:
% cd /usr/bin/X11
% mv mozilla mozilla.backup
% ln -s /usr/freeware/bin/mozilla ./mozilla
Solaris
The most basic system requirement for 3.3 Solaris is GeoProbe only runs on Sun Microsystems
(SUN) 64-bit workstations. The best way to determine if an existing system can run GeoProbe is
to check the SUN system model and version of Solaris (the operating system), then work through
the detailed requirements for hardware and software.
If you are ordering a workstation to run GeoProbe, it is best to contact Customer Support for
current recommendations.
Hardware Requirements
GeoProbe 3.3 runs on SUN 64-bit hardware, with the following recommended hardware:
Workstation Recommended
Sun Blade 2000 2-XVR1000 or XVR1200 graphics boards
2 - 1.2 GHz CPUs
minimum of 4 GB RAM
Sun Blade 2500 2-XVR1200 graphics boards
2 - 1.2 GHz CPUs
minimum of 4 GB RAM
Note
Xinerama mode is neither tested nor supported for use with GeoProbe.
Software Requirements
The following operating system is required to run GeoProbe 3.3 on a Sun Blade 2000.
The following operating system is required to run GeoProbe 3.3 on a Sun Blade 2500.
To determine the Solaris version of an existing system, type the following command in a shell
window. (8 or 5.8 may be returned, either is correct)
% cat /etc/release
To determine the version of OpenGL current running, type the following commands in a shell
window:
% /usr/openwin/demo/GL/ogl_install_check
% /usr/openwin/demo/GL/xglinfo
To determine the version of CDE, type the following command in a shell window:
% showrev -c /usr/dt/bin/dtlogin
Internet Browser
Mozilla 1.4.3 or higher is the supported html browser for GeoProbes online help. Please contact
Landmark Support for this executable if it is not already on your system.
In addition, this browser must appear first in the your PATH environment variable. If the system
already has an older version of Mozilla on it, you will need to rename the older version and create
a symbolic link to the new version. For example:
% cd /usr/bin/X11
% mv mozilla mozilla.backup
% ln -s /usr/freeware/bin/mozilla ./mozilla
Patch List
The following patches are required for installation of GeoProbe 3.3 on Sun Blade 2000 systems
using Solaris 8, Update 7 (02/02). The exact patch number as listed below may not be available
from Sun as they continually update version numbers. Sun recommends installing the latest version
of any patch; however, GeoProbe 3.3 is only certified on the following versions, and later versions
may not be downward compatible.
The following patches are required for installation of GeoProbe 3.3 on Sun Blade 2500 systems
using Solaris 8, HW 07/03.
To determine the current patches installed on your machine, type the following command in a shell
window:
% showrev -p | grep patch-number
Patches can be downloaded from the following location in the SUN website:
http://sunsolve.sun.com/pub-cgi/show.p1?target=patches/patch-access
Linux
GeoProbe 3.3 runs on Linux 32- and 64-bit workstations. The best way to determine if an existing
system can run GeoProbe is to check the Linux system model and version of Linux (the operating
system), then work through the detailed requirements for hardware and software.
If you are ordering a workstation to run GeoProbe, it is best to contact Customer Support for
current recommendations.
Software Requirements
GeoProbe 3.3 for 32-bit and 64-bit Linux, has been qualified on the Red Hat Enterprise Linux
WS 3.0, Update 7 operating system. The following tables list the minimum and recommended
requirements for the current and previous releases.
To determine the Linux version of an existing system, type the following command in a shell
window.
% cat /etc/redhat-release
For downloads and additional information on Red Hat Linux, see www.redhat.com.
Window Manager
Internet Browser
Mozilla 1.4.3 or higher is the supported html browser for GeoProbes online help. Please contact
Landmark Support for this executable if it is not already on your system.
In addition, this browser must appear first in the your PATH environment variable. If the system
already has an older version of Mozilla on it, you will need to rename the older version and create
a symbolic link to the new version. For example:
% cd /usr/bin/X11
% mv mozilla mozilla.backup
% ln -s /usr/freeware/bin/mozilla ./mozilla
Perl Update
It is strongly recommended that users update their Perl version to Perl V 5.8.3, which is included
with the GeoProbe Installation.
1. Login as root.
2. cd to GeoProbe/Linux32/3.3/RPM/
Hardware Requirements
32-bit Linux
GeoProbe 3.3 for 32-bit Linux runs on selected models of the IBM IntelliStation, Dell Precision,
Sun, and HP Compaq, running Red Hat Enterprise Linux WS 3.0, Update 7. The following
hardware configurations are customized to give balanced CPU, memory, and graphics
performance.
Note
Testing for the 32-bit version of GeoProbe was completed only on an IBM
IntelliStation Z-Pro with Quadro4 900 graphics. However, based on previous
releases, it should work with all the above boxes and their replacements.
http://www.nvidia.com/content/drivers/drivers.asp
64-bit Linux
GeoProbe 3.3 for 64-bit Linux runs on selected models of the IBM IntelliStation, Dell Precision,
Sun, and HP, running Red Hat Enterprise Linux WS 3.0, Update 7.
The following hardware configurations are customized to give balanced CPU, memory, and
graphics performance.
1. The HP XW 9300 is a dual-pipe, 64-bit Linux system. However, until a Nvidia graphics driver problem
is fixed, GeoProbe cannot run in stereo in multi-pipe mode on this system. Once Nvidia has resolved this
problem, users will be able to run GeoProbe in stereo over both pipes.
This workstation can be configured in a variety of modes, but was only tested in the following dual-pipe,
three-channel mode. The first pipe, or graphics card, used both channels to run two screens in twinview
mode; while the second card used a single channel to run a single monitor. An XF86Config-4 file for this
configuration has been included for your use in the XFree96 subdirectory of the GeoProbe installation.
For each of the above workstations, we recommend Nvidia graphics driver #87.62. However, it is
recommended that you download the driver specific to your workstation.
http://h20000.www2.hp.com/bizsupport/TechSupport/Home.jsp
For all other workstations download the driver from the Nvidia website:
http://www.nvidia.com/content/drivers/drivers.asp
*This is the same driver available from the Nvidia website, but HP has put a wrapper around it that modifies
grub.conf to configure it for the system RAM and also loads a new XF86Config-4. The old XF86Config-4 is
saved as XF86Config-4.save and you may want to revert to your original one after the driver is installed.
In GeoProbe 3.3, we are supporting multiple graphics card configurations. However in the last stages of
testing, we observed instability when active stereo (Option stereo 3) is enabled in the /etc/X11/
XF86Config-4 file. We are working with Nvidia to resolve these issues.
At the time of release, we recommend the following configuration to maximize stability for multi-graphics
card configurations:
We recommend that the size of swap space be equal to or greater than the size of physical memory.
Specifically, we recommend that swap space be sized between one and two times the size of
physical memory. Inadequate swap space allocation can cause system hangs and/or crashes. The
free command can be used to list the amount of system memory and swap space:
% free
total used free shared buffers cached
Mem: 30341548 736328 29605220 0 81124 488356
-/+ buffers/cache: 166848 30174700
Swap: 34040236 0 34040236
Detailed information on partitioning the hard disk and allocating swap space for systems running
Red Hat Enterprise Linux can be found in the manual Red Hat Enterprise Linux Installation Guide for
the x86, Itanium, and AMD64 Architectures, 4.16.4 Recommended Partitioning Scheme (http://
www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/pdf/rhel-ig-x8664-multi-en.pdf) . As
a general rule, swap space should be equal to 2x physical RAM for up to 2Gb of physical RAM,
and then 1X physical RAM for any amount above 2GB. Using this formula here are the swap
requirements for systems with varying amounts of physical RAM:
Note
The swap space is the sum of all swap partitions and swapfiles configured on the
system. In some systems with a large amount of swap space, performance can be
improved by splitting that space in to swap partitions or swap files located on
different disks. Red Hat Enterprise Linux supports up to 32 swap files.
Sometimes it is necessary to add more swap space after installation. There are three ways to do this,
you can: create a new swap partition, create a new swap file, or extend swap on an existing LVM2
logical volume. All of these methods are documented in Red Hat Enterprise Linux System
Administration Guide, 11.2 Adding Swap Space (http://www.redhat.com/docs/manuals/enterprise/
RHEL-4-Manual/sysadmin-guide/s1-swap-adding.html).
1. Determine the size of the new swap file in megabytes and multiply by 1024 to determine the
number of 1KB blocks. For example, the block size of an 16GB (16 * 1024 = 16384MB) swap
file is 16777216.
2. At a shell prompt as root, type the following command with count being equal to the desired
block size:
mkswap /swapfile
4. To enable the swap file immediately but not automatically at boot time:
swapon /swapfile
The next time the system boots, it will enable the new swap file.
Kernel Configuration
Before installing GeoProbe, you must first configure your workstation kernel parameters as
described below for each platform. Omitting these steps may result in GeoProbe not being able to
execute on your system.
IRIX
The GeoProbe Distribution CDROM has a script to perform some system requirement checking.
To use it, insert the GeoProbe Distribution CDROM and run the following command in a shell
window.
% /CDROM/IRIX64/syscheck
The script will display information about your system and point out potential problems.
GeoProbe recommends the following SGI kernel parameters, stored in the file /var/sysgen/
stune, to correctly and efficiently load a volume into shared memory:
rlimit_rss_cur Current limit to resident set size The size of physical memory.
(number of pages in memory).
rlimit_rss_max Maximum limit to resident set size The size of physical memory.
(number of pages in memory).
rlimit_vmem_cur Current limit for virtual memory. 1-2x the size of physical memory
rlimit_vmem_max Maximum limit for virtual memory. 1-2x the size of physical memory.
The total size of swap space should be greater than or equal to the size of physical memory. To
determine the current swap space settings, use the following command:
% /etc/swap -l
1. Create a 500 MB file named swapfile2 in /data1 (for example purposes, only).
SGI systems can run out of graphics contexts when multiple sessions of GeoProbe are run
simultaneously. The solution is to increase the number of GLX contexts, using the following steps:
1. Login as root.
2. Edit the file /var/sysgen/master.d/rrm, and change the maximum value for RRM_MAXRN.
The default value is 128, while we recommend a value of 512.
3. Run:
% /etc/autoconfig
Solaris
Before running GeoProbe on your SUN workstation, you must first change the following
configurations:
There is a limitation on the number of GLX windows that an application can use
simultaneously. Each GLX window that has an attached GLX context uses a file descriptor for
DGA (Direct Graphics Access) information. For running GeoProbe, it is recommended that
you increase this value to 128 using the following command:
% limit descriptors
descriptors 64
To be able to load large volumes into GeoProbe on SUN, the following parameters must be
changed in the /etc/system file:
The /etc/system file is a plain text file and can be edited in any text editor. It is recommended
that a back-up copy be made before any edits take place. The system must be rebooted for
changes to take effect. Values may be specified as either hexadecimal or decimal values,
depending on system administrator preference.
The prtconf command displays the system configuration, including the size of physical
memory:
host% /usr/sbin/prtconf
More information on these system parameters, and on the procedure for changing them, can be
found in the SUN document, "Solaris Tunable Parameters" (http://docs.sun.com/db/doc/806-
6779)
For example, the modified lines for a SUN Blade 2500 with 6 Gbytes of RAM might appear as
follows:
******
* added for geoprobe
******
set shmsys:shminfo_shmmax = 0x180000000
set shmsys:shminfo_shmmni = 0x1000
set shmsys:shminfo_shmseg = 0x100
Linux
If you are building your own Linux box, or upgrading your current Linux operating system,
perform the following steps:
1. Install Red Hat Linux EWS 3.0, Update 7 with all the packages. (Select Everything under the
Package Group Selection window).
3. Install the Nvidia driver. Contact customer support for information on obtaining these
drivers. Install the 87.62 driver for both 32-bit and 64-bit Linux. The driver needs to be
installed when the OS is in init run level 3 (no graphics) when you are logged into the console
as root.
% init 3
% chmod a+x NVIDIA-Linux-x86-1.0-8762-pkg0.run
% sh NVIDIA-Linux-x86-1.0-8762-pkg0.run
4. Install the dual head x-config file. In the GeoProbe installation, the directory
${GEOPROBE_HOME}/Linux64/3.3/XFree86 contains a set of example XF86Config-4
files. Copy the appropriate file to /etc/X11, or copy a working XF86Config-4 file to /etc/X11/
XF86Config-4. For example:
% cp ${GEOPROBE_HOME}/Linux64/3.3/XFree86/XF86Config-
4.twinview.dfp /etc/X11/XF86Config-4
5. Set shared memory limits. The value for kernel.shmmax is defined in bytes, while the value
for kernel.shmall is defined in blocks. For x86_64 and em64t the default page size is defined
as 4kb.
There is an error in some versions of the RedHat Enterprise Linux 3 Reference Guide, where
it is erroneously stated that the kernel.shmall is expressed in bytes. This is not true;
kernel.shmall should be expressed in pages. This value specifies the amount of shared memory
that can be used at one time on a system. It should be at least (kernel.shmax/PAGE_SIZE),
where PAGE_SIZE is the page size on the machine (4kb on x86_64 and em64t).
Set virtual memory parameters. Set virtual memory parameters as documented below.
For example, for a system with 8Gb of physical memory, add the following lines to /etc/
sysctl.conf:
# Controls whether core dumps will append the PID to the core
# filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
#
# System wide resource limits
#
* soft memlock unlimited
* hard memlock unlimited
* soft stack unlimited
* hard stack unlimited
* soft as unlimited
* hard as unlimited
* soft rss unlimited
* hard rss unlimited
* soft data unlimited
* hard data unlimited
* soft fsize unlimited
* hard fsize unlimited
7. For EM64T machines ONLY: Increase swiotlb buffer size. Edit the /boot/grub/grub.conf
file to change the line:
to:
8. Specify non-NUMA Behavior. In the /boot/grub/grub.conf file, add 'numa=off' to the end of
the kernel parameter line. Change:
to:
9. Set nVidia Device Driver Permissions. Set permissions on device drivers in accordance with
nVidia recommendations:
% vi /etc/security/console.perms
By opening up device driver permissions, you will avoid getting the error Error: Could not
open /dev/nvidiactl because the permissions are too restrictive.
10. Reboot.
Installation
GeoProbe 3.3 is a stand-alone release, and can be installed in its entirety on machines with no
current installations of GeoProbe. In addition, when GeoProbe 3.3 is installed on machines running
previous versions of GeoProbe, the previous versions will remain intact.
For example, installing GeoProbe 3.3 creates a new subdirectory in your GeoProbe directory
structure:
/home/magic/GeoProbe/<OS>/3.3
And will not overwrite any directories specific to earlier versions of GeoProbe. In addition, the
generic links to the GeoProbe executable geoprobe and geoprobe.pod found in the /home/
magic/bin_<OS> directory will be reset to point to the 3.3 executable.
WARNING!
Once you have installed GeoProbe, it is best not to move this directory manually
on your system... but instead install a fresh copy where you would like it to reside.
While we do not hard code any paths in the installation, after installation the
following files are hard coded:
Tcl/dp4.0/pkgIndex.tcl
Tcl/rcmd1.0/pkgIndex.tcl
Utils/GPprint
Utils/install.tk
Utils/*.shell
bin/run_geoprobe.EXAMPLE
Platform dependent files:
IRIX:
bin/geoprobe.pod
bin/gplaunchIr64.csh
bin/geoprobe.newpod
bin/geoprobe.3pipeflat
Solaris:
bin/gplaunchSn64.sh
Linux32:
bin/gplaunchLx32.sh
Linux64:
bin/gplaunchLx64.sh
Tcl/Tcl8.3/dp4.0/pkgIndex.tcl
Tcl/Tcl8.3/rcmd1.0/pkgIndex.tcl
IRIX
Installing GeoProbe requires several steps to check the hardware and software, copy files to the
computer, and setup GeoProbe.
Before installing, it is a good idea to determine if the workstation can run GeoProbe. Check the
System Requirements and Kernel Configuration sections first.
If you are already using GeoProbe and have customized some files, be aware that installing the
same version of GeoProbe may overwrite some of these files.
The following list of files are possible candidates for customization that may be overwritten:
The files on a CDROM drive are normally under /CDROM. After you place the CD in the drive,
wait a minute before the files appear in this directory.
Some SGI workstations may not have a CDROM drive. Check with the system administrator on
how to remotely mount the CDROM. As a last resort, use ftp to copy all the files from the CDROM
to a temporary directory and install from that directory.
Install GeoProbe
To install GeoProbe from the GeoProbe Distribution CDROM, perform the following steps in a
shell window. Please note that the directory /home/magic is used only as an example. GeoProbe
will install and run in any directory configuration, but it does need its own directory. Make sure
Read and Execute permissions are available to all users planning to run GeoProbe.
1. Create a GeoProbe Install Directory with the following command. This exact path name is not
required. You can choose the location for the GeoProbe Install Directory.
% /bin/mkdir /home/magic
% cd /home/magic
3. Determine the location of the installation media (such as /CDROM/IRIX64) and the Install
directory (such as /home/magic). Run the following command, optionally specifying the
installation media as SOURCE and Install directory as TARGET. Please specify the SOURCE
and TARGET directories using absolute paths (start with /). If the TARGET directory is the
same as your current working directory (pwd), you may omit TARGET=/home/magic. If the
path of the makefile (gpinst.mk) is the same as the installation media, you may omit
SOURCE=/CDROM/IRIX64.
There is one sample data set that comes with GeoProbe. Demo data is installed in Data/Demo under
the TARGET directory.
WARNING!
Do not install the Demo Data when running as root on your workstation. Installing
as root will limit the write permissions to the data directories.
Uninstall GeoProbe
All GeoProbe files live in the TARGET directory. To remove ALL versions of GeoProbe, simply
remove all the directories recursively:
% rm -r /home/magic
This command will delete all the files and directories in the magic directory. Be careful with this
command! It will not prompt the user for permission on the files.
GeoProbe 3.3 contains FLEXlm which includes the license manager (lmgrd) and vendor daemon
(licsrv). The vendor daemon for the Irix release of GeoProbe 3.3 (licsrv) is compatible with the
license server of Landmark Graphics OpenWorks and other Landmark applications. Users can use
an existing Landmark license server to run GeoProbe instead of starting a separate instance from
the GeoProbe install directory. For instructions on how to do this, please see your Landmark
representative.
Before installing the 3.3 license over a previous installation, it is best to shutdown the old license
manager, install the GeoProbe license software and license, then start the new license manager
using the following steps.
% cd /home/magic/License_Ir64
2. Then type
% ./S99GeoProbe stop
GeoProbe requires a license file. The file is a short, ASCII file delivered separately from the
GeoProbe Distribution CDROM, usually sent in an E-mail message.
The FLEXlm Support Files live in /home/magic/License_Ir64. To install this directory, use the
following command.
To install the license file, perform the following steps in a shell window.
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command:
% cd /home/magic/License_Ir64
2. Copy or create the license file in this directory and name it license.dat.
3. Be sure to keep a copy of the original license file in case the edited license file does not
work.
4. Edit the license.dat file and make sure the line beginning with VENDOR (or DAEMON)
has the correct full path name to the vendor daemon licsrv (/home/magic/License_Ir64/
licsrv).
5. Also check that the license file has the correct server name. The server name is the second
word on the SERVER line. The server name refers to the workstation running the FLEXlm
license manager.
Please note the only words you can change in the license file are the following.
Please note the following caveats when changing or creating a license file.
The character case of NOTICE, HOSTID, the feature name (second word on the FEATURE
line), and the authorization key (the sixth word on the FEATURE line) is not important.
The character case of the NOTICE value (the contents in double quotes) is not important.
White space in the NOTICE value is not important.
Make sure there is a space between the end of the authorization key and forward slash (\).
There should not be a space or any characters following the forward slash at the end of the
FEATURE line.
(# cpus - 2) / 2
cpus are licensed in pairs
MEPIPEADD64 1 pipe system - not required
2 pipe system - requires 1 count
3 pipe system - requires 2 count
# pipes - 1
pipes are licensed individually
SpecDecomp Utils/spectralDecomp MESPECDECOMPI Enables utility
Interactive
WellborePlanner Utils/WBPServer MEWBPLANNER Enables utility
Connect
Remote bin_Ir64/geoprobe.33I64 MEREMOTESESSION Enables remote rendering
Execution
Remote MEREMOTECOLLAB Enables remote rendering
Collaboration
Connection to lmgplink License for the OpenWorks
OW/SW DataServer, for use in accessing files
from OW/SeisWorks. This feature
also requires an OpenWorks license.
For installations that count the number of licenses, a license manager must be accessible by all
workstations planning to host GeoProbe. The license manager (lmgrd) and vendor daemon (licsrv)
are SGI IRIX executables, so they need to run on an SGI 64-bit system. Note, however, that you
can use a license manager on another system as long as the licsrv license variable is pointed to it.
To tell if your license has a count, check the sixth word on the FEATURE or INCREMENT line.
If this word is a number, then the license is counted and requires a license manager. If the word is
0 or uncounted, then a license manager is not necessary.
Please note that you should not be the superuser (root) when starting the license manager.
To start the license manager, perform the following steps in a shell window.
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command.
% cd /home/magic/License_Ir64
2. Run the script S99GeoProbe in this directory. You will not see anything displayed on the
screen. The server starts silently in background (it is a daemon).
% ./S99GeoProbe
3. Test the license, license manager, and vendor daemon using the following command.
The results displayed should look something like the following. Verify the license server is UP
and the vendor daemon licsrv is UP.
licsrv: UP v7.2
4. Check the license manager log file with the following command.
% more ./FLEXlm.log
Please note that other software products may use FLEXlm. A license file and server may already
be running at your site. GeoProbe uses version 7 of FLEXlm. Each version of FLEXlm is
compatible with previous versions, but older versions of the license manager and file may not be
compatible with version 7. It is fine to run more than one license manager, just make sure the port
number (the fourth word on the SERVER line) is different. Use port numbers 27000 through 27009
to prevent collisions with other daemons.
Trouble Shooting
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command.
% cd /home/magic/License_Ir64
2. Run the script S99GeoProbe in this directory and look at the commands it has available.
% ./S99GeoProbe help
3. Now type ./S99GeoProbe with the desired command to help you trouble shoot.
Note
The following are some common problems and how to check for them:
License server port ./S99GeoProbe checkport Change port number already in use
in license file
To have the license manager automatically start when the license server workstation is rebooted,
have the system administrator copy the S99GeoProbe file to the /etc/rc2.d directory.
For more information about FLEXlm, please see the FLEXlm End User Manual.
Solaris
Installing GeoProbe requires several steps to check the hardware and software, copy files to the
computer, and setup GeoProbe.
Before installing, it is a good idea to determine if the workstation can run GeoProbe. Check the
System Requirements and Kernel Configuration sections first.
If you are already using GeoProbe and have customized some files, be aware that installing the
same version of GeoProbe may overwrite some of these files.
The following list of files are possible candidates for customization that may be overwritten:
The files on a CDROM drive are normally under /cdrom. After you place the CD in the drive, wait
a minute before the files appear in this directory.
Some SUN workstations may not have a CDROM drive. Check with the system administrator on
how to remotely mount the CDROM. As a last resort, use ftp to copy all the files from the CDROM
to a temporary directory and install from that directory.
Install GeoProbe
To install GeoProbe from the GeoProbe Distribution CDROM, perform the following steps in a
shell window. Please note that the directory /home/magic is used only as an example. GeoProbe
will install and run in any directory configuration, but it does need its own directory. Make sure
Read and Execute permissions are available to all users planning to run GeoProbe.
1. Create a GeoProbe Install Directory with the following command. This exact path name is not
required. You can choose the location for the GeoProbe Install Directory.
% /usr/ccs/bin/mkdir /home/magic
% cd /home/magic
3. Determine the location of the installation media (such as /cdrom/cdrom0/SunOS64) and the
Install directory (such as /home/magic). Run the following command, specifying the
installation media as SOURCE and optionally specifying the Install directory as TARGET.
Please specify the SOURCE and TARGET directories using absolute paths (start with /). If the
TARGET directory is the same as your current working directory (pwd), you may omit
TARGET=/home/magic.
There is one sample data set that comes with GeoProbe. Demo data is installed in Data/Demo under
the TARGET directory.
WARNING!
Do not install the Demo Data when running as root on your workstation. Installing
as root will limit the write permissions to the data directories.
Uninstall GeoProbe
All GeoProbe files live in the TARGET directory. To remove ALL versions of GeoProbe, simply
remove all the directories recursively:
% rm -r /home/magic
This command will delete all the files and directories in the magic directory. Be careful with this
command! It will not prompt the user for permission on the files.
GeoProbe 3.3 contains FLEXlm which includes the license manager (lmgrd) and vendor daemon
(licsrv). The vendor daemon for the Solaris release of GeoProbe 3.3 (licsrv) is compatible with the
license server of Landmark Graphics OpenWorks and other Landmark applications. Users can use
an existing Landmark license server to run GeoProbe instead of starting a separate instance from
the GeoProbe install directory. For instructions on how to do this, please see your Landmark
representative.
Before installing the 3.3 license over a previous installation, it is best to shutdown the old license
manager, install the GeoProbe license software and license, then start the new license manager
using the following steps.
% cd /home/magic/License_Sn64
2. Then type
% ./S99GeoProbe stop
GeoProbe requires a license file. The file is a short, ASCII file delivered separately from the
GeoProbe Distribution CDROM, usually sent in an E-mail message.
The FLEXlm Support Files live in /home/magic/License_Sn64. To install this directory, use the
following command.
To install the license file, perform the following steps in a shell window.
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command:
% cd /home/magic/License_Sn64
2. Copy or create the license file in this directory and name it license.dat.
3. Be sure to keep a copy of the original license file in case the edited license file does not
work.
4. Edit the license.dat file and make sure the line beginning with VENDOR (or DAEMON)
has the correct full path name to the vendor daemon licsrv (/home/magic/License_Sn64/
licsrv).
5. Also check that the license file has the correct server name. The server name is the second
word on the SERVER line. The server name refers to the workstation running the FLEXlm
license manager.
Please note the only words you can change in the license file are the following.
Please note the following caveats when changing or creating a license file.
The character case of NOTICE, HOSTID, the feature name (second word on the FEATURE
line), and the authorization key (the sixth word on the FEATURE line) is not important.
The character case of the NOTICE value (the contents in double quotes) is not important.
White space in the NOTICE value is not important.
Make sure there is a space between the end of the authorization key and forward slash (\).
There should not be a space or any characters following the forward slash at the end of the
FEATURE line.
For installations that count the number of licenses, a license manager must be accessible by all
workstations planning to use GeoProbe. The license manager (lmgrd) and vendor daemon (licsrv)
are SUN Solaris executables, so they need to run on a SUN 64-bit system.
To tell if your license has a count, check the sixth word on the FEATURE or INCREMENT line.
If this word is a number, then the license is counted and requires a license manager. If the word is
0 or uncounted, then a license manager is not necessary.
Please note that you should not be the superuser (root) when starting the license manager.
To start the license manager, perform the following steps in a shell window.
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command.
% cd /home/magic/License_Sn64
2. Run the script S99GeoProbe in this directory. You will not see anything displayed on the
screen. The server starts silently in background (it is a daemon).
% ./S99GeoProbe
3. Test the license, license manager, and vendor daemon using the following command.
The results displayed should look something like the following. Verify the license server is UP
and the vendor daemon licsrv is UP.
licsrv: UP v7.2
4. Check the license manager log file with the following command.
% more ./FLEXlm.log
Please note that other software products may use FLEXlm. A license file and server may already
be running at your site. GeoProbe uses version 7 of FLEXlm. Each version of FLEXlm is
compatible with previous versions, but older versions of the license manager and file may not be
compatible with version 7. It is fine to run more than one license manager, just make sure the port
number (the fourth word on the SERVER line) is different. Use port numbers 27000 through 27009
to prevent collisions with other daemons.
Trouble Shooting
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command.
% cd /home/magic/License_Sn64
2. Run the script S99GeoProbe in this directory and look at the commands it has available.
% ./S99GeoProbe help
3. Now type ./S99GeoProbe with the desired command to help you trouble shoot.
Note
The following are some common problems and how to check for them:
License server port ./S99GeoProbe checkport Change port number already in use
in license file
To have the license manager automatically start when the license server workstation is rebooted,
have the system administrator copy the S99GeoProbe file to the /etc/rc2.d directory.
For more information about FLEXlm, please see the FLEXlm End User Manual.
Linux
Installing GeoProbe Linux requires several steps to check the hardware and software, copy files to
the computer, and setup GeoProbe.
Before installing, it is a good idea to determine if the workstation can run GeoProbe. Check the
System Requirements and Kernel Configuration sections first.
If you are already using GeoProbe and have customized some files, be aware that installing the
same version of GeoProbe may overwrite some of these files.
The following list of files are possible candidates for customization that may be overwritten:
The files on a CDROM drive are normally under /mnt/cdrom. After you place the CD in the drive,
wait a minute before the files appear in this directory. You may need to mount the CDROM drive.
To do so, run the following command in a shell window:
% mount /dev/cdrom
Install GeoProbe
To install GeoProbe from the GeoProbe Distribution CDROM, perform the following steps in a
shell window. Please note that the directory /home/magic is used only as an example. GeoProbe
will install and run in any directory configuration, but it does need its own directory. Make sure
Read and Execute permissions are available to all users planning to run GeoProbe.
1. Create a GeoProbe Install Directory with the following command. This exact path name is not
required. You can choose the location for the GeoProbe Install Directory.
% /usr/bin/mkdir /home/magic
% cd /home/magic
3. Determine the location of the installation media (such as /mnt/cdrom/Linux32 or Linux64) and
the Install directory (such as /home/magic). Run the following command, specifying the
installation media as SOURCE and optionally specifying the install directory as TARGET. Please
specify the SOURCE and TARGET directories using absolute paths (start with /). If the TARGET
directory is the same as your current working directory (pwd), you may omit TARGET=/home/
magic. You must always include the SOURCE parameter.
or
There is one sample dataset that comes with GeoProbe. Demo data is installed in Data/Demo under
the TARGET directory.
WARNING!
Do not install the Demo Data when running as root on your workstation. Installing
as root will limit the write permissions to the data directories.
or
Uninstall GeoProbe
All GeoProbe files live in the TARGET directory. To remove ALL versions of GeoProbe, simply
remove all the directories recursively:
% rm -r /home/magic
This command will delete all the files and directories in the magic directory. Be careful with this
command! It will not prompt the user for permission on the files.
GeoProbe 3.3 contains FLEXlm which includes the license manager (lmgrd) and vendor daemon
(licsrv). The vendor daemon for the Linux release of GeoProbe 3.3 (licsrv) is compatible with the
license server of Landmark Graphics OpenWorks and other Landmark applications. Users can use
an existing Landmark license server to run GeoProbe instead of starting a separate instance from
the GeoProbe install directory.
In the event you wish to re-install the 3.3 license, it is best to shutdown the old license manager,
install the GeoProbe license software and license, then start the new license manager using the
following steps.
% cd /home/magic/License_Lx32
or
% cd /home/magic/License_Lx64
2. Then type
% ./S99GeoProbe stop
GeoProbe requires a license file. The file is a short, ASCII file delivered separately from the
GeoProbe Distribution CDROM, usually sent in an E-mail message.
or
To install the license file, perform the following steps in a shell window.
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command:
% cd /home/magic/License_Lx32
or
% cd /home/magic/License_Lx64
2. Copy or create the license file in this directory and name it license.dat.
3. Be sure to keep a copy of the original license file in case the edited license file does not
work.
4. Edit the license.dat file and make sure the line beginning with VENDOR (or DAEMON)
has the correct full path name to the vendor daemon licsrv (/home/magic/
License_Lx32(or License_Lx64)/licsrv).
5. Also check that the license file has the correct server name. The server name is the second
word on the SERVER line. The server name refers to the workstation running the FLEXlm
license manager.
Please note the only words you can change in the license file are the following.
Please note the following caveats when changing or creating a license file.
The character case of NOTICE, HOSTID, the feature name (second word on the FEATURE
line), and the authorization key (the sixth word on the FEATURE line) is not important.
The character case of the NOTICE value (the contents in double quotes) is not important.
White space in the NOTICE value is not important.
Make sure there is a space between the end of the authorization key and forward slash (\).
There should not be a space or any characters following the forward slash at the end of the
FEATURE line.
Note
The 32-bit Linux GeoProbe executable can check out either the 32-bit or the 64-
bit license for use.
For installations that count the number of licenses, a license manager must be accessible by all
workstations planning to use GeoProbe. The license manager (lmgrd) and vendor daemon (licsrv)
are Linux executables.
To tell if your license has a count, check the sixth word on the FEATURE or INCREMENT line.
If this word is a number, then the license is counted and requires a license manager. If the word is
0 or uncounted, then a license manager is not necessary.
Please note that you should not be the superuser (root) when starting the license manager.
To start the license manager, perform the following steps in a shell window.
1. Change to the FLEXlm directory in the GeoProbe Install Directory with the following
command.
% cd /home/magic/License_Lx32
or
% cd /home/magic/License_Lx64
2. Run the script S99GeoProbe in this directory. You will not see anything displayed on the
screen. The server starts silently in background (it is a daemon).
% ./S99GeoProbe
3. Test the license, license manager, and vendor daemon using the following command.
The results displayed should look something like the following. Verify the license server is UP
and the vendor daemon licsrv is UP.
licsrv: UP v7.2
4. Check the license manager log file with the following command.
% more ./FLEXlm.log
Please note that other software products may use FLEXlm. A license file and server may already
be running at your site. GeoProbe uses version 7 of FLEXlm. Each version of FLEXlm is
compatible with previous versions, but older versions of the license manager and file may not be
compatible with version 7. It is fine to run more than one license manager, just make sure the port
number (the fourth word on the SERVER line) is different. Use port numbers 27000 through 27009
to prevent collisions with other daemons.
Trouble Shooting
1. Change to the Flexlm directory in the GeoProbe Install Directory with the following
command.
% cd /home/magic/License_Lx32
or
% cd /home/magic/License_Lx64
2. Run the script S99GeoProbe in this directory and look at the commands it has available.
% ./S99GeoProbe help
3. Now type ./S99GeoProbe with the desired command to help you trouble shoot.
Note
Always provide a command to S99GeoProbe. Without a command the license manager will be
started. Try to only start the license manager once since there may be a delay in starting and stopping
its multiple processes.
The following are some common problems and how to check for them:
License server port ./S99GeoProbe checkport Change port number already in use
in license file
To have the license manager automatically start when the license server workstation is rebooted,
have the system administrator copy the S99GeoProbe file to the /etc/rc5.d directory.
For more information about FLEXlm, please see the FLEXlm End User Manual.
For IRIX:
% /home/magic/bin_Ir64/geoprobe
For Solaris:
% /home/magic/bin_Sn64/geoprobe
For Linux:
% /home/magic/bin_Lx32/geoprobe
or
% /home/magic/bin_Lx64/geoprobe
GeoProbe 3.3
The following section gives a brief overview of the new features and functionality of the GeoProbe
3.3 release. For a more detailed description of each feature, please refer to the New Features
Tutorial that can be launched from GeoProbes help menu.
New Features
Horizons, Surfaces, Faults and TSurfs can now be easily displayed on the face of the active
probe using the new Probe Intersection option. From the Style dialog of these objects, simply
toggle on the intersection option. When toggled on, the object will be displayed only on the
faces of the active probe. In this same dialog, you will also have the option to change the color
and width of the intersection line.
Well plan targets and seedpoints are no longer limited to the face of the active probe. They can
now be picked on Horizons, Surfaces, Faults, and TSurfs.
Associated SeisWorks fault segments can now be displayed in GeoProbe using the new
SWFaults object manager.
Viewer
Improvements have been added into the Spin Animation option. The CTRL key will toggle
the direction of the spin, while using the left and right CTRL keys allows you to confine the
spin. Finally, holding down the SHIFT key before spinning the scene will let you start the spin
in a clockwise direction.
When using Spin Animation, a new option has been added to the User Preferences > Viewer
dialog called Keep the Elevation Constant while Rotating/Spinning. This option is toggled
on by default and keeps the scene from turning over on itself when spun at an angle.
The F# function hotkeys have been de-coupled from the traditional saved Views. Now when
using these hotkeys, the scene will jump to the appropriate view for orientation, but you are
able to rotate out of this view simply by using MB1.
Volumes
When loading volumes from either a SeisWorks or GeoProbe directory, the volume file size
will now display below the volume list for any volume selected. In addition, if you have
selected several volumes, the cumulative size will be displayed.
Wells
Using WellborePlanner with GeoProbe now no longer draws the scene with multiple wellbore
refreshes.
ezFaults/ezSurfaces
In the Style dialog, there is a new option called Show Ribs. When toggled off, *.eds surfaces
and faults will be displayed without the white ribs, or segments, where their picks were
made.
In the Style dialog, there is a new option called EDS Fast Mode. When toggled on, *.eds
surfaces and faults will be displayed with only a linear interpolation between rib locations, as
opposed to the normal spline interpolation. This will greatly speed up the display of these
objects when the scene is moved.
In the Style dialog, there is a new option called Show Annotation. When toggled on, *.eds
surface and fault names will be displayed in the objects color at the top-center of the object.
Coloring *.eds faults/surfaces by Volume has been improved upon to remove data artifacts
seen in previous releases.
ezFaults and ezSurfaces can now be converted to TSurfs using the To TSurf option in each
Object Manager.
In both the Surfaces and Faults Object Managers there are now buttons called ezSurface and
ezFault, respectively, that will launch the ezFault/ezSurface dialog.
Horizons
We can now Merge two or more horizons into a new, combined horizon. When merging these
horizons, you can set which will be the overriding horizon, or select to use a computed average
horizon.
The new Horizon Attributes dialog allows you to color the active horizon by its Dip, Azimuth,
and Dip/Azimuth attributes. These attributes can help reveal fault trends, lineations, and
mispicks that may not normally be apparent. In addition, we have added a new circular azimuth
Horizon generation and editing tools now have unlimited Undo and Redo options.
The new Horizon PolyEdit tool, in the Edit Tools dialog, allows you to manually delete an area
of horizon points either by simply clicking on the segments you wish to delete, or by specifying
a region for deletion.
Using Edit Tools > Horizon Filter you can edit any existing horizon using a smoothing
function, a median filter, or a spike reduction filter.
TSurfs
TSurfs can now be clipped to the active Probe by either toggling on the Clip to Probe option
in the TSurf Style dialog, or by selecting MB3 > Options > Limit TSurfs.
GeoAnomalies
GeoAnomalies can now be converted into pointsets and geobodies, for additional editing
capabilities and volumetric calculations. Using the Selected Anomalies to Multiple Pointsets
icon, each selected anomaly will be converted into its own pointset. These pointsets will
appear in the Points List using the same naming convention as the anomaly. Using the Selected
Anomalies to a Single Geobody and Pointset icon, all selected anomalies will be converted
into a single pointset, and will launch the Geobody builder to create a single geobody.
2D Data
General Usability
Saving multiple files at once is now available. Simply select the files you wish to save in the
Object Manager list, then click Save. If any files already exist on disk, you will be asked if you
wish to overwrite them.
There are now three options for moving values in your colormap colorbar: Normal Move will
move only the selected thumb; Proportional Move will evenly shift all the thumbs to the right
or left of the selected thumb; and the new Symmetric Move will perform a proportional move
entered around the mid-point of the colorbar
There are no longer two buttons for Enable and Disable on the Object Managers. Now, the
button will display the appropriate state depending on what is selected in the list.
Fixed Problems
HP XW 9300 - multipipe only. Saved states were not restoring when running in Xinerama
mode. GeoProbe would sometimes stall when loading an OpenWorks object or restoring a state
file. Conflicts between Xinerama mode and Tcl caused problems in the interaction between
GeoProbe and its auxiliary applications. (#7016, #712447)
HP XW 9300 - multipipe only. When loading a volume while in Xinerama mode, the volume
load status box would hang during the loading process. However, the volume was in fact loaded
into shared memory, and could be attached from the Volumes Object Manager. (#7019)
When running Remote Collaboration, if a bad or empty session file is loaded, or if you click
Cancel before loading a session; the collaboration license does not get released. This will result
in an error message of GP attempted to initiate a Collaboration session - no licenses available
the next time the user tries to run Remote Collaboration. You must exit out of GeoProbe to
release the license. (#719644)
When converting objects to *.eds surfaces using the To Eds option, the conversion options
have been increased to allow up to 250 points per rib, and 250 ribs per editable surface.
However, the user can enter any value, but the only valid ones range from 2 - 250. (#720624)
In the ezTracker gate window, you will not be able to drag the gate boundaries or seedpoint if
the NumLock or CapsLock setting on the keyboard is on. (#4443, #6708)
Similar to the previously documented problem with the ezTracker gate window; if the
NumLock or CapsLock setting on the keyboard is on, placing the cursor over a surface, fault
or horizon in the main GeoProbe window will not display the objects name. (#720041)
On occasion, when coloring a horizon, the horizons colormap may contain NaN, or null,
values. Reproducing the workflow seems to remove these NaNs, and will display the correct
value in the colormap.(#6813)
If a state file is saved with GeoAnomalies groups disabled from the view, upon restoring the
state these files will automatically be enabled. (#6820)
Coloring a TSurf by Z will post different values in the colormap display than the actual values
of the TSurf. (#6839)
When saving a state with TSurfs, where one is loaded with Flip z-values toggled on, and one
is not... they are both restored in the state with Flip z-values toggled off. (#6761)
Known Problems
The following problems can be found in the IRIX, Solaris and Linux versions of GeoProbe, unless
otherwise noted. Numbers in parentheses denote the items id number in the bug tracking system.
Memory holes have been observed on the 64-bit systems, where the system itself is reserving
a select amount of memory for drivers and other utilities. For example, on the IBM
Intellistation A Pro, a system with 8 GB RAM might only have 6.8 GB available for use.
Memory tools such as the KDE System Monitor will show the reduced amount as Total
Memory.
Volumes loaded into shared memory are also loading into cache, therefore when you look at
the memory manager a 2GB volume will be taking up 4GB of memory space. When a volume
is removed from shared memory, it is not removed from cache until the machine is rebooted or
another application requires the same memory address space. (This has also been observed
occasionally on 32-bit systems)
Workaround
To alleviate this problem, we have implemented a new volume file loader for
Linux systems. This prevents the double loading of data into memory, but only for
volumes loaded from a GeoProbe directory with no trimming or decimation
applied.
While this is a workaround to the memory issue, volumes will load approximately
25% slower than before. To disable the new volume loader, set the following
environmental variable before launching GeoProbe:
% setenv GEOPROBE_NO_DIRECT_IO 1
The new volume loader can cause a warning when GeoProbe is run:
OpenWorks Connectivity
To enable the OpenWorks connectivity for a GeoProbe session, the following 5 environmental
variables must be set before launching GeoProbe: OWHOME, OWSYSSID, OW_PMPATH,
ORACLE_SID, and ORACLE_HOME.
You may get a popup Error: Problem in getting a valid OWSYSSID if you run GeoProbe
after running it (or another Landmark app) and changing your environment to use a new
OWSYSSID. To fix this problem you can either type the following:
% xprop -root | grep <username>
% xprop -root -remove <based on what the above command returns>
State Files
GeoProbe does not support loading multiple state files in a single session. This operation often
causes instability in the GeoProbe session. (#4359)
When loading a state file created on an older version of GeoProbe, there may be times when
all the data loads into the session, but isnt visible in the viewer window. The scene has
centered incorrectly and can be fixed by clicking the Center on Probe icon. (#5177)
When saving a state file that contains a SeisWorks volume, make sure that this volume is saved
to disk as opposed to simply attaching to it from within shared memory. Otherwise, the state
file will not recognize the volume. (#6378)
If a horizon created in the current GeoProbe session is not saved explicitly from the Horizon
Object Manager, upon saving a state the horizon will be saved with the default Horizon
name. The user will not be prompted to rename it at that point. This can cause multiple files to
be named Horizon. (#5151)
Volumes
If the first volume loaded into a session does not contain World Coordinates, there may be
problems loading other data types into the session. (#6052)
When loading a volume, fractional numbers are not allowed in the trim/decimate options for
X, Y and Z values. (#725559)
Surfaces/Faults
When displaying a probe with transparency applied and a fault with transparency applied,
moving the probe about the fault may cause areas where the probe does not display correctly.
(#6408)
While the Surface Merge/Trim dialog box is open, the user cannot manipulate the scene in the
viewer window. (#2099)
When creating two faults that will later be used in a trimming process, make sure to make edits
to the main fault at the same line you are beginning interpretation on the crossing fault, or the
trimming process may select the wrong part of the fault to trim. (#713544)
When creating ezFaults/ezSurfaces, you cannot set handles at the last inline or crossline of the
volume, then have those handles be honored if you move the probe backwards. (#711863)
We have allowed the ability to move probes outside the volume space for interpreting oblique
faults. In the event that a fault exceeds 10% outside the volume, the fault will not be able to be
edited at those extents.
When slicing a surface, even if you have the Move Low Res option toggled on in Surface Style,
the slicing will be performed in Hi Res when using the keyboard keys. (#727528)
Linux 64-bit only. If AGP is not enabled on your Linux 64-bit system, performance may
degrade when large surfaces are loaded. To check the status of AGP on your system, perform
the following steps:
1. In an xterm window:
$ cat /proc/driver/nvidia/agp/status
Status: Disabled
Status: Enabled
Driver: AGPGART
AGP Rate: 8x
Fast Writes: Disabled
SBA: Disabled
4. Remove all occurrences of that line (or comment it out) and reboot the machine.
Points
Digibrush points are not snapping to the set values of max/min attribute or when Snap to Value
is set. (#3491)
Horizons
In GeoProbe 3.2, we have introduced a new horizon file format to enable saving of Tile Sizes
and heredity mapping. Therefore, horizons generated on GeoProbe versions older than 3.2 will
no longer have valid heredity information.
ezTracker Standard will only operate in an evolving seed mode. You are not given the option
for a non-evolving seed, as you are in ezTracker Plus.
ezTracker will veer from the desired amplitude when the seed offset is set to the max or min
value. The workaround is to not set this offset to the extreme values.
If the user deletes a horizon from the Horizons List while it is being created in ezTracker,
GeoProbe will crash. (#5823)
When ezTracking a horizon using Interactive Build, the horizon surface will not update when
using the hotkeys to move the probe. As a workaround, the user can click on Update Horizon.
In addition, it has been seen on some systems that if the probe is moved too quickly about the
volume, some points might be skipped.(#6251)
ManuTrack was not designed to pick on time/depth slices, only on inlines, crosslines, and
arbitrary lines. (#4088)
If a horizon has been interpreted using ManuTrack, then a larger volume is loaded into the
session, the horizon will disappear from the display. This problem also occurs when a state is
restored, and you attempt to extend an existing ManuTracked interpretation. Toggle on Display
Mesh and the horizon will re-appear in both cases. (#4338)
When converting a surface to a horizon, and also converting the same surface to a pointset, the
number of points in the horizon will be less than the number of points in the pointset. This is
due to the fact that pointsets can contain multi-z values, and is expected behavior. (#5505)
When loading a SeisWorks horizon into a decimated volume session of GeoProbe, then editing
and saving it back to SeisWorks under the same name, the horizon will only be sampled at the
decimated rate.
Switching between ezTracker Standard and ezTracker Plus while creating a horizon may cause
the Undo option to leave points behind when Interactive Build is toggled on for both dialogs.
(#6891)
If a horizon created in the current GeoProbe session is not saved explicitly from the Horizon
Object Manager, upon saving a state the horizon will be saved with the default Horizon
name. The user will not be prompted to rename it at that point. This can cause multiple files to
be named Horizon. (#5151)
Wells
Well Synthetics are brought into GeoProbe in time as it exists in OpenWorks. To use a
synthetic on a GeoProbe depth volume, it must be saved as a log curve and re-loaded into
GeoProbe.
The user can no longer insert a well build control point using the Insert key on the keyboard.
(#2771)
For wells native to GeoProbe (not loaded from OpenWorks), well marker depth is displayed in
Measured Depth along the wellbore. In a time volume, this is not a true depth value, as
GeoProbe does not do a time/depth conversion. It does, however, give a unique value for each
location along the wellbore. (#1966)
When in SeisWorks mode, loading a well from the GeoProbe working directory does not give
you the option to limit the wells extents. (#4409)
Loaded and displayed volumes may disappear from the view if a well is loaded that contains
bad values, such as NaNs or unreasonably large values, in the well path or well log. As it
would negatively impact loading performance if each well had to be checked for these values,
it remains unfixed. (#718542)
GeoAnomalies
Irix and Solaris only. GeoAnomalies will not be performant on older SGI and SUN
workstations that do not support the newer graphics hardware extensions.
Irix and Solaris only. Whats This context-sensitive help is not available on SGI and SUN
workstations for the GeoAnomalies dialog. Please refer to the main, html help system instead.
(#6780)
Solaris only. Multi-line comments cannot be added to GeoAnomalies on this platform.
However, single-line comments can still be added from within the Anomaly Table spreadsheet.
(#6834)
When a state file is saved, all of the GeoAnomalies (*.agr) included will be duplicated in a file
named <state_name>.agr. For example, a session with five 1 MB geoanomaly .agr files saved
as a state will create a 5 MB combined file, which is loaded when the state is restored. (#6592)
When depressing MB1 or MB1+MB2 in the main window while drawing GeoAnomalies, the
scene will flash. This is expected behavior, as it indicates to the program to stop the process
underway. This allows the user to interrupt the rendering at any point. (#5650)
GeoAnomalies will allocate some amount of virtual memory upon initialization that will be
kept until the end of the GeoProbe session. Once GeoProbe exits, this virtual memory will be
released. (#6534)
Be aware that if an anomaly is colored black, it will not be visible against GeoProbes black
background. (#6157)
TSurfs
Tsurf files that contain an end of line character /r will not load into GeoProbe. Instead, the
end of line character should be denoted by \r, as it comes from DOS files.
If the first volume loaded into a session does not contain World Coordinates, Tsurf files may
not load in their correct locations. (#6052)
When displaying a probe with transparency applied and a TSurf with transparency applied,
moving the probe about the TSurf may cause areas where the probe does not display correctly.
(#6408)
Coloring a TSurf by Z will post different values in the colormap display than the actual values
of the TSurf. (#6839)
When saving a state with TSurfs, where one is loaded with Flip z-values toggled on, and one
is not... they are both restored in the state with Flip z-values toggled off. (#6761)
Shapes
Linux only. Shape files that reference a *.rgb file will not load into the GeoProbe session.
(#5187)
2D Data
When working with both 2D and 3D data, you must load the 3D data into the session first, or
the data may not display in the correct space. (#2388)
2D seedpoints are not supported by the Seed Points dialog. While they may appear in the
dialog, the location information associated with them is incorrect. (#3025).
Remote Collaboration
When loading a session for Remote Collaboration, all clients listed in the session must be
available. If one client is logged out, the the Load Session dialog will appear to hang,
eventually crashing the remote rendering server. (#3607)
When running GeoProbe without the -collaboration command line flag, the Collaboration
Object Manager will still be available for display, but the collaboration functionality will be
disabled. This is only applicable if the user has a collaboration license feature.
WellborePlanner Connect
Solaris only. WellborePlanner Connect has a shared library dependency that /usr/java1.2 be on
SpecDecompInteractive
SpecDecompInteractive will not execute when the volumes and selected surfaces sample
rates do not match due to decimation. When running this tool on a decimated volume, be sure
to first save decimated surfaces to disk. (#2014)
Utilities
When using the projectSwap utility to flip legacy projects to a new orientation, be aware that
culture files may not display as expected. For example, files with text in them may appear
upside down and illegible when swapped in x and y. (#5212)
Only POSC RESCUE models created before VIP 2003.4 can be imported to GeoProbe. To
import your 2003.4 model, save it to an older version within VIP, then import it using the
Import RESCUE model in the Utility Launcher.
Utilities Launcher > Miscellaneous > Convert VIP to Volume(s) operates on a DeskTop VIP
single flat binary simulation database ".vdb" file. With DeskTop VIP R2003.4, a new multi-file
hierarchical format for vdb files has been established that cannot currently be handled by
GeoProbe. The work-around is to first use DeskTop VIP's utility VIPConvert to switch from
the new hierarchical vdb back to the old style single vdb format and then import the old style
vdb into GeoProbe. (#2195)
POSC RESCUE models have cells that can be tetrahedral shaped, while GeoProbe voxels are
always brick shaped. Therefore, in the event that no smoothing is used (as is the default), the
user may see grey voxels in their converted GeoProbe volume. To alleviate, call customer
support to get the recommended command line syntax for a non-default level of smoothing.
(#2456)
Linux Only. Due to a problem with Perl Version 5.8.0 that comes standard with Linux WS 3.0,
some utilities may not run correctly. It has been determined that updating the Perl Version will
fix this problem. The correct Perl RPM package has been included in the GeoProbe installation
files. To update Perl, complete the following steps: (#4714)
1. Login as root.
2. Change to the RPM directory:
% cd GeoProbe/Linux32/3.3/RPM
or
% cd GeoProbe/Linux64/3.3/RPM
or
Stereo/Multi-Threading/Multi-Pipe Issues
In GeoProbe 3.3, we are supporting multiple graphics card configurations. However in the last stages of
testing, we observed instability when active stereo (Option stereo 3) is enabled in the /etc/X11/
XF86Config-4 file. We are working with Nvidia to resolve these issues.
At the time of release, we recommend the following configuration to maximize stability for multi-graphics
card configurations:
EM64T systems only. GeoProbe makes efficient and heavy use of system and processor
resources, and is multi-threaded. If multiple-threads are competing as they try to share the
resources of a single processor, dead-locks and other problems can occur. Turning off the
hyperthreading option is different from workstation to workstation. For information on how to
setup the hyper-threading field in the BIOS interface for Intel systems, see http://
www.intel.com/support/platform/ht/bios.htm.
When running GeoProbe on a system with more CPUs than the GeoProbe ME2CPUADD64
license features, a warning appears stating: GeoProbe is attempting to run on the (#) available
CPUs, however, there are only enough CPU licenses available to permit use of (#) CPUs at this
time. Do you want to continue? When the user presses Continue, GeoProbe unexpectedly
exits. To avoid this problem, use the startup executable tag of -cpuLimit to match the number
of available CPUs licensed. (#720499)
If two graphics cards are installed on a system, but only one is configured... GeoProbe will
hang. The workaround is to remove the unused graphics card from the system. (#727534)
When running in multi-pipe mode across blended screens for spherical projections, changing
to an orthographic projection results in geometry errors. This option can be disabled using the
GEOPROBE_DISABLE_ORTHO_MODE environmental variable. (#729511)
64 bit Linux only. On some Linux 64-bit systems, if you exit GeoProbe while in stereo mode
the framelock hardware/nVidia driver can be left in a bad state. This will prevent you from
being able to run GeoProbe with framelock the next time you launch the program. To recover,
use the nvidia-settings file to disable framelock, and then re-enable it. (#721765)
64 bit Linux only. On some Linux 64-bit systems, some instability was observed when mixing
framelock with TwinView on multiple graphics cards only on the optimized/released build. this
is an Nvidia issue, and it has been reported to them (Nvidia support call 229020)
Miscellaneous
If the user uses the command xkill to end GeoProbe, be aware that the license will not be
released. xkill forces the X server to close the connection to its client. There is no way for GP
to know the connection is broken. In order to release the license, the user has to use kill -9 <GP
process id> to kill the process. (#6221)
Solaris only. While in view mode, toggling off the Decoration option then toggling it back on
reduces the viewing window to a long, narrow display that can only be expanded by
maximizing the window. This occurs due to an error with the Solaris window manager, and
cannot be fixed within GeoProbe. (#5994)
Colormap load histories are kept from session to session. To delete this history file, remove the
.crehistory file in the directory from which GeoProbes run script is called. (#722925)
The Hydrocarbon calculator may not completely draw the dialog upon selection. (#5333)
Linux 64-bit only. Graphics displayed in GeoProbes main window can appear to stutter
when either the window is moved from one screen to another, or while Spin Animation is being
used. (#5323)
Linux 64-bit only. RSI is not included on the installation CD for 64-bit Linux. Please Contact
RSI regarding the availability of 64-bit versions.
GeoProbe may crash on startup if a $HOME/.flexlmrc file is too long, containing too many
characters. An instance has been observed when this file exceeded 4000 characters. (#4674)
There seem to be some issues with SUNs keyboard mappings. Sometimes the Dwmrc key/
pointer mapping changes are not honored, and when displaying remote or local applications
into SUN boxes, there seems to be some issues between Alt and Meta key behaviors. There
are two workarounds available:
We have added the capability to GeoProbe to use the Meta key as the Alt key so that on
those systems with problems, one can use the Meta key instead. These changes will
permit GeoProbe to have a way to behave correctly even when there are keyboard/pointer
binding issues.
On some systems with Alt and Meta keys present, one can press the Alt + Meta
keys together in order to warp/jump into Viewing mode. ( Meta key is the one with the
black diamond on it, next to the space bar on SUNs)
Linux only. If a systems KDE window style is changed from the default settings, there may be
occasions when the Object Manager appears skinnier than it should be, making it difficult to
see all the managers buttons. (#719267) To solve this problem, complete the following steps:
1. cd ~/.kde/share/config
2. Open "kwinrc" with your favorite editor
3. Look for [Style]
4. Replace PluginLib=kwin_keramik with PluginLib=kwin_default
5. Save "kwinrc"
6. Log out and log back in
Linux only. Depending on the window manager you are using, the Alt key may need to be
re-mapped in order to see the expected window behavior in GeoProbe.
1. From the main window manager select Control Center > Index > Desktop > Window
Behavior > Actions Tab > Inner window, Titlebar & Frame area
2. Set Modifier Key = Alt
3. Set Modifier Key + left button = Nothing
4. Click Apply.
% setenv __GL_SYNC_TO_VBLANK
or via the /usr/bin/nvidia-settings interface. We recommend that it be turned off for GeoProbe
3.3 to achieve the best performance.
Support
Landmark/Asia Pacific Landmark/EAME Landmark/The Americas
11th Floor Menara Tan & Tan Hill Park South Building 1, Suite 200, 2101 CityWest
207 Jalan Tun Razak Springfield Drive Houston, TX 77042
50400 Kuala Lumpur Leatherhead, Surrey GU22 7NL P.O. Box 42806, Houston, TX 77242
Malaysia England U.S.A.
Trademarks
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, Asset Development Center, Asset Development Centre, Asset Performance, AssetView,
Atomic Meshing, BLITZ, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Manager,
DataStar, DBPlot, Decision Suite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView,
DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace PowerGrid,
DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace TracPlanner,
DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3, DepthTeam
Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DFW, DIMS, Discovery, Discovery
Asset, Drill-to-the-Earth Model, Drillability Suite, Drilling Desktop, DrillModel, DSS, Dynamic Reservoir Management, Dynamic
Surveillance System, EarthCube, EDM, eLandmark, Engineers Data Model, Engineer's Desktop, Engineers Link, EOS-PAK,
Executive Assistant, ezFault, ezSurface, ezTracker, FastTrack, FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized),
GeoGraphix Exploration System, GeoLink, GeoProbe, GeoProbe GF DataServer, GeoProbe Integrated, GES, GESXplorer,
GMAplus, GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, Landmark, Landmark and Design, Landmark
logo and Design, Landmark Decision Center, LandScape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic
Earth, MagicDesk, MagicStation, MagicVision, Make Great Decisions, MathPack, MIRA, Model Builder, MyLandmark,
OpenBooks, OpenExplorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Well File,
PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP,
PowerCalculator, PowerExplorer, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerSection, PowerView,
PRIZM, PROFILE, ProMAGIC, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP,
pSTAx, QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RTOC, Real Freedom, Real-
Time Asset Management Center, Real-Time Asset Management Centre, Real Time Knowledge Company, Real-Time Operations
Center, Real Time Production Surveillance, Real Time Surveillance, RESev, ResMap, RMS, SafeStart, SCAN, SeisCube, SeisMap,
SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, Sierra, Sierra (design), SigmaView, SimResults, SIVA,
Spatializer, SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks, StressCheck, STRUCT, Surf & Connect,
SynTool, System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Storage, T2B, TDQ, Team Workspace,
TERAS, Total Drilling Performance, TOW/cs, TOW/cs The Oilfield Workstation, TracPlanner, Trend Form Gridding, Turbo
Synthetics, VIP, VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-
THERM, WavX, Web Editor, Web OpenWorks, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect,
WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus
are trademarks, registered trademarks or service marks of Landmark Graphics Corporation or Magic Earth, Inc.