Professional Documents
Culture Documents
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Known Problems
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Database/Horizon Transfer
Currently you may not transfer IHD type horizons
directly to the database using this module. There are two
work-arounds. The first is to use the ASCII export option
then import this file in XDB. The second is to copy the
nnnnnnnn.IHD binary file in the LINE directory to
nnnnnnnn.HOR using the UNIX cp command. (301638)
Datum Statics Apply
If you run the Datum Statics Calculation with a new ID
number (e.g 04) for Source/Receiver/CDP parameter
files, you get a notification of "Job completed". If you
immediately go in Datum Statics Apply and try to pick
the new Source/Receiver/CDP parameter files, the new
ID entries i.e (S_STAT04 etc.) will not be visible in first
attempt. However in second attempt the new entries are
there. (120120)
Datum Statics Calculation
When you run this module multiple times different
CSTATxx attributes may be created. However only ONE
version of C_STATIC ever exists that is the same as the
last execution of this module. When you use the module
Apply Datum Statics the user chooses which version to
apply. However some modules such as DMO to Gathers
3D ALWAYS use C_STATIC. Therefore it is best practice
to make the version you wish to apply the last. (301410)
This module fails if the database attribute C_STATIC
does not exist. The work around is to use DBTools to
create this attribute before running this module. Or run
a flow containing Apply Elevation Statics to put
C_STATIC into the CDP database, then run Datum
Statics Calculation. (128231)
DBTools
If NULL values exist at the end of a range of attributes,
only the non-null range is plotted, even if you select to
plot null values. The NULL value count is also lumped
into the first histogram plot. (504860)
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
If there are more than 5 inserts in the flow, and the first
dataset has only one trace. (512619)
Other Docs
Known Problems
Other Docs
Known Problems
DMO to Gathers 3D
Running this module changes your OFB_CNTR and
OFB_NO headers to a constant value. You can use Trace
Header Math before this process to save the offset
values into a user defined header. These may be used to
restore the original values after DMO. (505646)
This module is NOT passing the flow parameters to the
Processing History for subsequent use in Create CGM+
Plotfile labeling or dataset history. (508050)
Using the Offset Squared option for offset sampling
outputs nothing but dead traces (TRC_TYPE=2). The
work around is to only use the OFFSET option for offset
sampling. (514245)
Eigen Stack
If you attempt to use a time gate that was created by
defining the bottom layer first you will get this error.
Request for memory buffer has negative size
Other Docs
Known Problems
Other Docs
Known Problems
Known Problems
option the job fails with an error stating that the data is
not sorted in CDP order. The Exploding Reflector option
does not have the option to use trace header information
and disappears from the menu when using this selection
but is still expecting to pull the geometry information
from the headers. The solution is to make sure you turn
off the "Take geometry from the headers of an input data
set?" parameter before using the Exploding Reflector
option. (140358)
First Break Pick Macro
This module will fail if you attempt to use the NN Picker.
(512768)
First Break picks are not visible if you review or animate
saved images. (130529)
F-K Analysis
On a 3D dataset, if you pick a polygon and save it, then
re-execute the flow, the polygon will not display. It may
still be applied with no problems. (512332)
F-X Decon
SGI Only: This module is running slower in version
2003.x than it did in 1998.6. Work-Around: use version
1998.6 if possible. (149746)
Floppy Input
This process can fail on some operating systems, either
with a SIGSEGV segmentation violation error (Solaris) or with a
Floppy Open Error pointing to an invalid filename (AIX). In
some cases, limiting the input to fewer records
(approximately 300) and processing the input file in
pieces has resolved this problem. (503674)
No facility to input OYO 3 format from a mcseis170
recorder. Currently there is no work around for this
problem. (301359)
Fourier Trace Interpolation
The last output trace may be numbered incorrectly.
Work-around: Use Trace Header Math to re-number the
trace or pad an extra trace prior to interpolation then
delete it afterwards. (305444)
Other Docs
Known Problems
Other Docs
Known Problems
Depending upon the type and size of font chosen and the
amount of re-sizing of the spreadsheet window the last
line in the spreadsheet may be only partially visible.
Potential work-arounds are to delete
the.Spread_parms.xdr file in the users home directory.
Also make sure the 75DPI font is ahead of the 100DPI
font in the font search path. (507740)
Using a Binning Bias of -1 causes an error. This may
make it impossible to get the desired value for the first
CDP. The work-around is to use some other bias value
like 0, -2 etc. then use Trace Header Math to re-number
the CDP values. Afterwards, extract a new geometry.
(301897)
When a database is binned in pieces, and the option to
use the default for offset binning is taken, the last
execution of binning determines the range of OFB_NOs
for the line. It is possible that the resulting min-max
range is not accurate for the entire line. The workaround is to use the User Defined option for offset
binning and always use the maximum range for the line,
regardless of what it is for a particular portion. (510198)
When the values for SRF and SIN do not increase in the
same direction CDP_ELEV may get projected in reverse
order. This appears to occur when you choose the option
CDPs increase from last trace in the binning menu.
(514180)
AIX ONLY: The Cross Domain icon does not work in
XYGraph. (144466)
Hand Statics
Inputting a large number (approximately 1500) of
REC_SLOC/static pairs via an ASCII input file will cause
this process to fail with the error message:
Character parameter is too large to input. Severe memory problem.
Memory buffer overrun detected.
Other Docs
Known Problems
Other Docs
Known Problems
IF
In some cases the end of ensemble flag will not be passed
to subsequent processes. This module was redesigned to
better handle large volumes of data. If this flag is
essential, the work around is to either use Ensemble
Redefine after the IF/ELSEIF. Or use the same primary
key in the IF as you did in the Disk Data Input. (507877)
If you have nested IF/ELSEIF modules in a flow and the
primary key is the same as in the input step you may get
unexpected traces output. The work-around is to use or
create a different header. (512958)
Inline Geom Header Load
When overwriting a dataset, the following warning: Format
is 1, should be 2 indicates that a standard header has been
created with the wrong type. For example, OFFSET
might be inadvertently created using Trace Header
Math prior to loading geometry as an integer value, yet is
required to be a floating point header. The incorrect
header can be deleted prior to the Inline Load step using
the Header Delete process, or the output should be
directed to a new dataset. (503296)
Marine Data Only: This process can fail with a SIGSEGV
error if you run Extract Database Files, and then
attempt to load the geometry based upon the Match by
valid trace number designation. You should be able to
load geometry by matching on SIN, or by creating a
unique trace header such as SOURCE using Trace
Header Math. (503873)
TIM_SHOT values with 7 digits used to match header
and database values fail to load headers properly,
indicating that certain shots are not in the database. If
required, place the TIM_SHOT value in a different
header, such as DAY_SHOT, which will then correctly
match the larger values. (506811)
Linux Only: Marine inline header load may fail if SRF
OPF FOLD attribute does not exist. The work around is
to bin receivers in the spreadsheet. (515840)
Interactive Data Access
When using IDA with Trace Display and displaying large
datasets, (such as 100,000 traces), you can experience
Other Docs
Known Problems
Other Docs
Known Problems
/advance/port/src/lib/agC/Bytemap.C line 70
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
NN Horizon Picker
The program fails with following error message if the
TRC database does not exist (507492,504682):
Database error - error opening database file, Error creating AUTOSTAT
database entry.
Other Docs
Known Problems
Other Docs
Known Problems
The requested trace editing key SKEY isn't in the trace header!
This message may appear if you have Trace
Kill/Reverse in your flow where your parameter table
has been corrupted by the SKEY header. (512541)
work-around: Since tables with the SKEY header cannot
be read in, you will have to Create a new table selecting
the correct primary and secondary keys, then
export/import the values from your old table into the
new one.
Attempting to import an ASCII file into an existing
parameter table that is smaller will either fail or delete
the original data in the table. The work-around is to
create a new table to import into. (515428)
Phase Shift 3D Migration
This module is cutting off the last sample. If you need to
perform an operation where this is critical, such as
removing AGC scalars, run Trace Length to restore data
to the full length. (514071)
Phase-Shift or Stolt 3D Migration can error out in
Remute/Rekill server stage, even if this code is not used.
This seems to be most prevalent when a big proportion of
the data is dead. (In this case, about 40%). Contact
customer support for a possible patch. (129225)
Plot CGM+ Plotfile
Zeh Only: In order to get Zeh 4.2.5.20 to run with
ProMAX 2003, you need to use the
$ZEHOME/config/zeh_plotfile script provided with ZEH.
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Radon Filter
Radon Filter can create an artificial AVO response.
Radon Filter increases amplitude with offset on the
near offset traces and then causes an amplitude
decrease with offset on the far offset traces. (507281)
work-around: Do not band-limit the modeled output in this
program, use Bandpass Filter.
Radon Analysis allows the picking of water bottom
relative mutes. Radon Filter does not. The work-around
is to first flatten on the water bottom and not use water
bottom relative mutes. (512849)
Specifying "Minimum time of interest" other than "0"
multiple gates does NOT work. (141209)
Read Sierra Velocity Model
This process will abort without an error message if there
is a carriage return at the end of the line containing the
model name. The <cr> character must be deleted by
editing the input file order to be read into ProMAX.
(505671)
You may encounter this error when reading some Sierra
Velocity Models.
Unable to interpret model file header
Other Docs
Known Problems
Other Docs
Known Problems
Seg-B Input
SEG-B Input assumes the record length of first record
for entire dataset. If the first record is shorter than the
rest, all other records will be truncated. The work-around
is to specify the record length explicitly in the menu.
(136816)
SEG-D Input
See also SEG I/O General.
You may encounter the following error attempting to
read I/O System Two tapes.
SEGD: I/O System Two, No lines detected.
Known Problems
R_LINE,Receiver Line,2I,,,22/
SRF_SLOC,Receiver Station,2I,,,25/
Some formats of Seg-D are showing a 1 msec. time shift
from pre-1998.6 versions of ProMAX. This has been fixed
in version 2003.3. (304758)
Work-around: Transfer time of first sample in SEG-D
header to new TAPE_T0 header word. Header statics may
be used subsequently to shift trace data up or down.
On some 8048 format tapes ProMAX is not incrementing
the FFID. (133287)
Linux Only: X015 formats are not converting properly.
Contact support@lgc.com for a possible patch. (134764)
SEG-Y Input
See also SEG I/O General.
The option to read in data using a primary sort of
Receiver is inoperable. The process will fail with a
SIGSEGV Signal 11 error, or with a Primary key out of range error if
a Data Output step is included in the flow. The data
should be read into the ProMAX system with the SEG-Y
Input defaults, and resorted as necessary. (503544)
The menu does not currently allow for input of the value
0 for the parameter Number of errors in a row before
aborting job, even though the value of 0 can be used to
indicate that all such errors should be ignored. The
type_desc option in the segy_read.menu file can be
modified as follows: (503652)
parameter: ABORT
type_desc: (int 5 1 99999)
should read
type_desc: (int 5 0 99999)
Known Problems
Known Problems
Any flow with more than one Seg-Y Output in it will fail
unless there is an input module between them. (507871)
Depending on the number of input samples this module
may pad extra samples on the output trace. This only
happens if the output format is 1 or 2 Byte formats.
(509875)
Multiple Seg-Y Output modules in the same flow fail
with the message, "Error trying to open a device". There
is no known work-around at this point. (513366,513782)
The automatic system generated EBCDIC header has the
area name twice, rather than Area and Line. (514169)
If you modify a flow and save it in 1998.6 and the SEGY
Out menu is from 1998.1, the save will delete the SEGY
Out menu. (514108)
The NREW (no rewind) parameter in the device.tts file is
not being honored. (514411,515409)
Linux Only: Flows with multiple Seg-y Outputs will fail.
(137213)
SeisWorks 2D Seismic Info
Trying to run this module with an old menu will give an
error. The option Shift MB2 to overlay a new menu does
not fix it. Users must bring in a new menu from the
processes list. (515674)
SeisWorks Horizon Input*
For 2D data, horizons are input with primary and
secondary keys of LINE_NO and FRN_TRNO. These
horizons can be interactively displayed and manipulated,
but some processes such as Database/Horizon
Transfer, can require different table sorting to work
properly. In this case, the horizon can be exported to
ASCII format, and reimported with the required sort
keys. (503129)
Display of horizons input to ProMAX using this process
may fail if the associated trace data was not created in
the ProMAX system using SeisWorks Seismic Input.
Input of both horizons and data from a SeisWorks
project should resolve this problem. (502983)
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Split / End_Split
Tools which initialize a new header will fail when placed
inside a Split/End Split branch with the error:
Trace headers corrupted
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
View -> Edit colormap -> File -> Open -> greyscale.rgb
Attempting to display a previously picked Auto-Statics
Horizon may not show all the picks. The parameter
table is correct, the problem is in the display. (512949)
First break picks will not display if the primary sort key
in Disk Data Input is SOU_SLOC. The work-around is to
sort on something like FFID or SIN. (512964)
This module may fail with an Ensure failed... message if you
try to display too many samples. The work-around is to
display fewer traces. (513104)
Different results (worse) with NN Picking in Trace
Display compared to batch program NN First Break
Picker. (511000)
Trace scaling is dependent on the number of traces in
the ensemble. (303629)
1) "Entire" scaling is based upon each ensemble.
2) "Individual" scaling is based upon each trace.
3) Smooth is applied to traces within an ensemble.
4) Ensemble boundaries are important to Trace Display
and can have a noticeable impact on the resulting
display.
It is possible to generate parameter tables in Trace
Display that have negative start times. Some tools such
as Spiking/Predictive Decon will fail if one of these tables
is used. If you are making picks near time zero check the
resultant table for negative values (513724)
When Disk Data Output, or another output tool is used
in conjunction with Trace Display, Trace Display may
corrupt the last trace in the dataset if the Output Mode
is set to When Done rather than Immediate. (513405)
Solaris Expert 3D Graphics only: Trace Display does
not refresh properly after other windows display over the
top of the Trace Display. (303915)
Solaris: In Trace Display while picking layers, if you are
running ProMAX on a Solaris systems and displaying
back to an SGI the MB3 option to Pick another Layer
does not function. (513792)
Other Docs
Known Problems
Other Docs
Known Problems
ANGLE=ATAN(TMP)*180.
ANGLE2=ATAN((sou_y-rec_y)/((sou_x-rec_x)*3.1415927))*180.
Trace Kill/Reverse
On 3D lines, if multiple FFIDs have the same sou_x and
sou_y locations, the trace edits called on these FFIDs are
applied only to the last FFID in the group. This will only
happen if the Trace Kill/Reverse list has been opened
with the parameter table editor. The editor attempts to
perform a 3D resolve on the table causing the problem.
(507685)
If the primary key for editing traces, such as
REC_SLOCS, becomes 8 digits or larger, adjacent traces
may get edited. The work-around is to choose a primary
key with smaller numbers or use an IF block to sort off
the REC_SLOCS to be killed and use a universal kill.
(509843)
The requested trace editing key SKEY isn't in the trace header! This
error occurs when your parameter table has been
corrupted by the SKEY header.(512541)
work-around: Since tables with the SKEY header cannot
be read in, you will have to Create a new table selecting
the correct primary and secondary keys, then
export/import the values from your old table into the
new one.
Trace Length
This module does not correctly re-set the trace headers
TLIVE_S and TFULL_S. Therefore it is possible that
applying a re-mute after this module will give incorrect
results. The work around is to use Trace Header Math
to manually re-set the headers. (507786)
Trace Math
When adding traces the OFFSET and AOFFSET trace
headers may get corrupted. The work-around is to either
save them to a user defined header or use a different sort
key, such as CHAN. (147861)
Other Docs
Known Problems
Trace Muting
The re-mute option may not give correct results if the
module Trace Length has been applied previously. The
Trace Length module does not correctly re-set the trace
headers TLIVE_S and TFULL_S. Therefore it is possible
that applying a re-mute after this module will give
incorrect results. The work-around is to use Trace
Header Math to manually re-set the headers. (507786)
Applying a bottom mute to data that has already had a
top mute applied will re-ramp the top of the trace. In
affect, the ramp will be squared rather than linear.
(507816)
The option to Apply where specified does not work
properly. In general, using the option Interpolate over
secondary key will give the desired results. (508337)
Trace Sample Math
When special characters (e.g. !,@,#,$,%,^,&,<,>,? etc) are
included in the equation (e.g 3 + #4 + 5) the program
assigns zero to everything after the special character (the
result from the previous equation is 3) The same is true
when using brackets, Also everything after a space is
ignored. (514024,514023,514022)
When numbers (e.g 1234) or mathematical expressions
(e.g sqrt(16), 1 + 4) are written on the left side of the
equation (e.g 1234=sine(sample)) the program outputs
the value of the left side of the equation instead of the
value of the right side. In the last example the output
would be 1234. This doesnt happen when an
alphanumeric expression is used on the left side.
(514026)
Trace Splice
Problems have been encountered when attempting to
use this process to splice poststack traces. If required,
you should be able to work around the problem using
Disk Data Input and Disk Data Insert in merge mode,
along with trace shifts and Trace Math operations.
(504215)
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
xxxx.xxxx:START DEPTH
should be modified to
STRT.FT
xxxx.xxxx:START DEPTH
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
VSP/CDP Transform
The program uses all the shot and receiver X,Y
coordinates to compute a slope and intercept of a line.
The transformed data will be imaged along this line in
map view. If there are duplicate shot and receiver
coordinates, an improper line gets computed, and the
job may possibly fail. (505491)
This module may generate spikes if the datum is below
the source elevation(513565)
VSP Geometry Spreadsheet
See Also: Geometry Spreadsheet General
VSP Geometry Spreadsheet
The values in the X and Y columns are destroyed when
Station column is filled. It is not required to fill in this
column. (507633)
Vel Table From VSP
Although the option is given in the menu to limit the
offsets used to compute the velocities, this range is not
being used. (507635)
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems
IL1 XL1
IL2 XL2
ProMANAGER Problems
Proloop is not interpreting the & in Disk Data Input
from another line. When passed "area & line & dataset",
proloop is supposed to translate this to populate the
pop-choose for area, line, and dataset in a Disk Data
Input menu reading a dataset from another line.
Currently, it is passing the input string verbatim. The
original character was a pipe |, but this was changed to
a & to accommodate peculiarities of MsAccess. The pipe
still works, but the & doesnt. (509963)
Submitted flows fail to honor product paths in .promax.
The 1998.6 version of ProManager does not use multiple
search paths from a users .promax file during job
submission. (512935)
work-around: Functionally equivalent to defining paths
in a PROMAX_DOT_PROMAX_HOME or
$HOME/.promax file can be arranged by setting any or
all of: PROMAX_SYS_EXE_HOME,
PROMAX_PORT_MENU_HOME,
PROMAX_PORT_HELP_HOME,
PROMAX_PORT_MISC_HOME in the ProManager job
submission environment. These variables will need to be
added to the environment catalog first.
Other Docs
Known Problems
Other Docs
Known Problems
Known Problems
the job.output:
Expected VSN and the observed VSN read from the input volume do not
match.
This error condition has no override option.
Other Docs
Known Problems
Other Docs
Known Problems
Other Docs
Known Problems