Beruflich Dokumente
Kultur Dokumente
Software Installation
Memory Requirements
For any platform, memory requirements vary by:
the size and type of image file, if imagery is used
the size of the survey being processed, with greatest memory demands
made during binning calculations and writing SEGY data to disk
On UNIX workstations, binning calculations make demands on swap space in
direct relation to survey size (number of traces). Approximately 4 bytes of swap
space are required per survey trace. For example, for a 6,000,000 trace survey
the following swap space is recommended:
The figures stated above indicate the bare minimum amount of swap space
required to optimize the capability of MESA. If this amount of swap space is not
available, MESA will run, but will do so much more slowly. Additional swap
space is required for the operating system, windowing system, window manager,
and any other concurrently running process.
File Extension
File Size
Bin Grid
.bin
28 bytes/bin
Midpoints
.mid
12 bytes/midpoint
Stations
.sta
168 bytes/station
Sources
.sor
216 bytes/shot
NOTE: Image files may require large amounts of disk space, depending on
image size and pixel resolution. On UNIX workstations, the
rasterization of a CGM file (as output from GMG Plot), especially one
containing imagery, also utilizes large amount of disk space. Consult
your plotting software documentation for further information.
CAUTION: Different versions of operating systems, windows, and Motif may
require different executables. We support only those system
configurations noted below. Attempting to run an executable on other
system configurations may produce unreliable or unpredictable
software behavior.
SOFTWARE INSTALLATION
GMG-Image
GMG-Plot
Mesa
gmgimage.exe
gmgplotb
Mesa.uid
gmgimage.uid
gmgplot.exe
mesa.csc
gmgimage.csc
gmgplotb.uid
xvtprolg.ps
gmgplotb.csc
device.1st
base/CGMGEN.apl
base /CGMINT.apl
base /CGMMAST.cmp
base /GKSMAST.cmp
base /HCPRF.apl
base /HCPRG.apl_bourne
base /PRFROOT.apl
base /ROOTMAST.cmp
base /UNIMAST.cmp
base /unicld.dat
base /unihlp.dat
lib/libAgx.so (SGI only)
lib/libdum.so (SGI only)
lib/libdum.so.6.4 (Solaris only)
Add the path to the software installation directory(ies) to each users .cshrc.
SOFTWARE INSTALLATION
All Programs:
In order to take advantage of the improved features associated with
file importing, it is required that the GMG_EXE_PATH environmental
variable be set. To accomplish this, type the following in each users
.cshrc file:
setenv GMG_EXE_PATH /directorypath/gmg
(replacing directorypath/gmg with the appropriate path to the MESA
software).
It is also recommended to set the GMG_DATA_DIRECTORY
environmental variable, if you havent done so previously. This sets
the default working directory for your MESA sessions:
setenv GMG_DATA_DIRECTORY /working/directory/path
(replacing working/directory/path with the appropriate path name).
The following variable must also be set for each user:
setenv UIDPATH /directorypath/gmg/%U
replacing /directorypath/gmg with the software installation directory
path on your system. If several executables are installed to separate
directories, or if you have other Motif applications on your system, use
the following syntax to set multiple UIDPATHs as follows:
setenv UIDPATH /directorypath/gmg/%U:/directorypath/mesa/%U
again replacing the directory paths appropriate for your system.
To use the Print utility in the File menu, it is necessary to set the
following variable in each users .cshrc:
setenv XVTPATH /directorypath/gmg
replacing /directorypath/gmg with the software installation directory
path on your system. The file xvtprolg.ps (included in the software
distribution) must reside in this directory, and all users must have read
permissions for this file.
SOFTWARE INSTALLATION
Image Caching
If imagery is to be used, the image handling can be optimized by setting the
image caching. Optimal caching depends on the memory of the system,
and the size of the imagery.
Edit each users .cshrc and add the following line to set the number of
megabytes for the image library to use in caching image operations:
setenv GMG_IMAGE_CACHE 4
OR, for the Korn shell:
export GMG_IMAGE_CACHE = 4
replacing the value 4 with the desired number of megabytes.
Caching defaults to 4 if the variable is not set. For systems with large
amounts of memory, the cache can be increased. For systems with 8 MB or
less, the cache should be reduced. The smaller the cache, the greater the
frequency of reading from disk, resulting in slower program speed. The
default value of 4 MB is adequate for smaller images (20MB or less). Large
images (115 MB, for example) will require at least 6 MB of cache to run
efficiently. If the cache is too small, the program will still run, but will do so
very slowly. The cache value must not exceed the amount of available
memory on the system.
For large images, you may set the image cache to the available
memory.
The following formula can be used to estimate the recommended cache size
for a given image:
Recommend cache size = (pixels per row)*(bytes per pixel)*255*2
where (pixels per row) is the number of pixels in the X direction of the
image, and (bytes per pixel) is equal to 8 for grayscale, and 24 for color
images.
The image dimensions (in pixels) and bytes per pixel are reported by the
"Coordinate Entry" dialog, in GMG-Image. This formula represents the
maximum memory made by the image library, i.e. the time at which the
image is stored in memory and simultaneously being written to disk as a
layer file. Subsequent display of a layer file is much less demanding of the
system resources.
If the recommended cache value (as calculated by the above formula)
exceeds available memory, you should pursue one of the following
alternatives:
crop the image in portions using the Crop option in GMG-Image, load and
unload each portion in turn
upgrade the hardware by increasing memory and swap space
8
NOTE: Caching defaults to 4 if the variable is not set. For systems with
large amounts of memory, the cache can be increased. For system
with 8 MB or less, the cache should be reduced. The smaller the
cache, the greater the frequency of reading from disk, resulting in
slower program speed. The default vale of 4 MB is adequate for
smaller images (20 MB or less). Large images (115 MB, for example)
will require at least 4 MB of cache to run efficiently. If the cache is too
small, the program will still run, but will do so very slowly. The cache
value must not exceed the amount of available memory on the
system. (Refer your manual for the formula used to estimate the
recommended cache size for a given image.)
For large images: you may set the cache to the available system
memory.
SOFTWARE INSTALLATION
Memory Requirements
For any platform, memory requirements vary by:
the size and type of image file, if imagery is used
the size of the survey being processed, with greatest memory demands
made during fold calculations
On UNIX workstations, fold calculations make demands on swap space in direct
relation to survey size (number of traces). Approximately 12 bytes of swap
space are required per survey trace. For example, a 6,000,000 trace survey
requires the following swap space:
7.2 x 107 bytes (/1024) = 7.03 x 104 KB(/1024) = 68.8 MB
The figures stated above indicate the recommended amount of swap space
required to optimize the capability of MESA Advisor. If this amount of swap
space is not available, MESA will run, but will do so much more slowly.
Additional swap space is required for the operating system, windowing system,
window manager, and any other concurrently running process.
10
NOTE: The amount of free disk space required for MESA depends
primarily upon survey sizes and imagery use. See the
Hardware/Software Requirements, All Platforms for general
information regarding survey database sizes. Windows also requires
space from your hard disk for swap files. Image use, numerous
windows, and 3D fold calculations increase the memory demands
made on your system. Running multiple Windows applications and
switching between applications also increases the demand for
memory. Adequate RAM and disk space are absolutely required for
good system performance.
SOFTWARE INSTALLATION
11
Installing MESA
Microsoft Windows must be running before the installation of MESA software
may be performed. Please see the Microsoft documentation for Windows
installation instructions.
Be sure to have installed the security block before attempting installation.
The PC software is distributed on CD-ROM. To transfer the software to a
permanent installation directory on your hard drive insert the CD into its
appropriate drive, an install script should start the install program, if not look at
the contents of the CD and run the Autorun.exe application. This will open a
window with a list of the programs on the CD to install. Select Mesa 6.0. A
MESA installation script automates the installation.
To start the program from the Windows desktop, double click on the MESA icon.
12
All Programs
In order to take advantage of the improved features associated with
file importing, it is required that the GMG_EXE_PATH environmental
variable be set. To accomplish this, add the following to the
autoexec.bat file and restart Windows:
set GMG_EXE_PATH=c:\directorypath\gmg
replacing c:\directorypath\gmg with the appropriate path to the MESA
software.
It is also recommended to set the GMG_DATA_DIRECTORY variable, if
you haven't done so previously. This sets the default working directory for
your MESA sessions:
set GMG_DATA_DIRECTORY=c:\working\directory\path
replacing c:\working\directory\path with the appropriate path name.
SOFTWARE INSTALLATION
13
Image Caching
If imagery is to be used, the image handling can be optimized by setting the
caching. Optimal caching depends on the memory of the system, and the size
of the imagery. The image cache should be set when using GMG-Plot or GMGImage.
On the PC, the image cache is set in the autoexec.bat. Edit this file, and
add the following line to set the number of megabytes for the image library
to use in caching image operations:
set GMG_IMAGE_CACHE=4
Replacing the value 4 with the desired number of megabytes. Reboot the
system to implement the change.
For large images, you may want to set the cache to the available
memory for your system.
The following formula can be used to estimate the recommended cache size
for a given image:
Recommend cache size = (pixels per row)*(bytes per pixel)*255*2
where (pixels per row) is the number of pixels in the X direction of the
image, and (bytes per pixel) is equal to 8 for greyscale, and 24 for color
images.
The image dimensions (in pixels) and bytes per pixel are reported by the
"Coordinate Entry" dialog, in GMG-Image. This formula represents the
maximum memory made by the image library, i.e. the time at which the
image is stored in memory and simultaneously being written to disk as a
layer file. Subsequent display of a layer file is much less demanding of the
system resources.
CAUTION: The cache value must not exceed the amount of available
memory on the system.
If the recommended cache value (as calculated by the above formula)
exceeds available memory, you should pursue one of the following
alternatives:
crop the image in portions using the Crop option in GMG-Image, load and
unload each portion in turn
upgrade the hardware by increasing memory and swap space
14
NOTE: caching defaults to 4 if the variable is not set. For systems with
large amounts of memory, the cache can be increased. For system
with 8 MB or less, the cache should be reduced. The smaller the
cache, the greater the frequency of reading from disk, resulting in
slower program speed. The default vale of 4 MB is adequate for
smaller images (20 MB or less). Large images (115 MB, for example)
will require at least 4 MB of cache to run efficiently. If the cache is too
small, the program will still run, but will do so very slowly. The cache
value must not exceed the amount of available memory on the
system. (Refer your manual for the formula used to estimate the
recommended cache size for a given image.)
For large images: you may want to set the cache to the available system
memory.
SOFTWARE INSTALLATION
15
16