Known Problems List
No link to a known problem found for this process.
NOTE:You are linked to this page because no known problem for this process is listed in this document.
If you are accessing this document via Other Docs: Known Problems, please page down to review the Known Problems list for other processes.
This file is updated monthly and placed on our ftp server for retrieval on an ongoing basis. For information on how to download the most recent copy of the Known Problems list please refer toDownloading and Uploading Files with FTP in the Accessing the Internet as a Resource chapter of the
ProMAX 2003.3.2 Known Problems Jan. 1, 2003
When you click the Known Problems icon in your online documentation, it will take you to an entry in this listing if there is a corresponding known problem. If there is not a corresponding problem, you are taken to the start of this file. The number following the description of a problem is used as a reference ID. It is used when contacting the technical support group for additional information regarding the status of the problem. This file is organized as follows:
•Recently Discovered Problems lists problems found after this listing. This list includes problems for all ProMAX products. Each recently discovered problem will also be repeated in the appropriate category below. •ProMAX 2D/3D Problems contains an alphabetical
listing of all problems associated with ProMAX 2D and 3D.
•ProMAX VSP Problems contains an alphabetical listing of all problems specific to ProMAX VSP.
•ProMAX MVA Problems contains an alphabetical listing of all problems specific to ProMAX MVA.
•ProMAX 3D PSDM Problems contains an alphabetical listing of all problems specific to ProMAX 3DPSDM. •Software Development Problems
•FrameViewer Problems contains a list of problems specific to the Frame Viewer software used to display the ProMAX helpfiles.
•ProManager Problems contains a listing of problems specific to the ProManager flow replication tools. This includes MySQL problems.
•Total Tape Solution Problems contains a list of problems associated with
TTS,OPCON,ShowCat,device.tts and resource database problems.
Recently Discovered Problems
ProMAX 2D/3D Problems
General ProMAX
• Database attributes can be lost if you run concurrent jobs that add new attributes to the same Ordered Parameter File (OPF) in a database file. If this occurs, you can get a partial recovery by restoring the OPF index file from your backup media. (502707)
• Database attributes can be lost if you access an OPF file which spans filesystems, but the active config_file does not contain the appropriate OPF flag for the required filesystems. (501718)
• Parameter tables defined with integer values for sort keys larger than plus or minus 2**23 (8388608) may fail with an error such as:
Unable to find SIN given FFID xxxxxxxx
Within the geometry spreadsheets and database, integer attributes can be entered with a precision up to plus or minus 2**31, and trace headers are loaded correctly during Inline Geometry Header Load. However, parameter table access on those keys using the larger values will fail due to truncation problems.
work-around: Repick or recreate the parameter table
based upon key values that are not similarly affected. For example, using SIN or SOURCE rather than FFID. (502967)
• Processes accepting ASCII input lists directly into the menu can fail with memory errors upon execution. A typical limit for ASCII strings is 50 kbytes. (502573) • Parameter Table Editor: When selecting a parameter
table which allows for multiple time gates, select all gates in increasing order. However, if time gates are selected out of order, you can export and then reimport the columns in the correct order using the parameter table editor. For example, after you have added a gate during a subsequent interactive session. (504247) • Display tools memory use: Interactive Data Access,
Analysis can suffer degraded performance if data is viewed outside ensemble boundaries. These problems include: increased usage of memory, CPU, and wall clock time as additional traces are processed within a single flow. The problem is most apparent when passing a large number of traces through Trace Display, and not using the default value of 0 for Number of traces to display per screen. Exit the flow to clear the CPU usage. You are encouraged to maintain input ensemble boundaries where possible when using these display tools. (505892) • Display Tools: When using Exit/Stop in any of the
inter-active display tools, the numeric files in the flow direc-tory are not automatically deleted. It is best to use Exit/Continue flow. (506109)
• Licensing: The user interface may crash if you try to switch to the VSP product and do not have a valid VSP license. (514918)
• Problem: Tape mount dialog window pops-up but you cannot see the text. The solution is to add entries like these to each users .Xdefaults file.
ProMAX Tape*background: MistyRose ProMAX Tape*foreground: sienna4
• Displaying on a dual monitor Solaris system, while running on an IBM may fail with the error:
X Error of failed request: BadWindow (invalid Window parameter)
work-arounds:
Option 1: use Exceed to log into your AIX machine and run display jobs.
Option 2: Change your dual monitor to a single monitor display. On a dual-headed (2 monitor) Solaris system one of the heads can be disable via editing
/etc/dt/config/Xservers file.
NOTE*** You DO NOT edit the /usr/dt/config/Xservers file but instead copy it to /etc/dt/config and edit that one.
line at the bottom of this file:
:0 Local local_uid@console root /usr/openwin/bin/Xsun:0 nobanner -dev /-dev/fb0 --dev /-dev/fb1
Where "fb0" would denote the first monitor and "fb1" would denote the second monitor. The file would need to be edited to allow ONLY a single (i.e., fb0) monitor. Change above line to read:
:0 Local local_uid@console root /usr/openwin/bin/Xsun:0 nobanner -dev /-dev/fb0
Log off and then back on system to restart Xserver. • Linux Only: In the case when the endian order is set in
the config_file as "big" and PROMAX_LITTLE_ENDIAN is set to true in the start up script. Result: The job runs and the data is output as big-endian (it doesn’t consider the value that is set in the start up script,) It doesn’t do what it says in the config_file about the user being able to override the default for a particular job by setting either PROMAX_BIG_ENDIAN or
PROMAX_LITTLE_ENDIAN in the environment. (516151) • Linux Only: When ProMAX gets the endian order from
the config_file it doesn’t report in the job.output which endian order is outputting. (516152)
Admin
• Queues:lp SGI only: Killing an executing lp-queued job, removes it from the lp queue but does not terminate its processes. To kill a series of queued jobs, be sure to kill waiting jobs before any active ones, or waiting jobs will become active and then, in turn, not die when killed. (512936)
Queues:NQS Cannot kill an active process from NQS. (512923)
work-around: You can use
$PROMAX_HOME/sys/bin/qdel to delete local or remote (qdel on that remote host) NQS queues:
* running jobs (qdel -<signo> <requestid>) * waiting jobs (qdel <requestid>)
is not possible there is a work-around. In addition to the steps described in the System Admin. Manual do the following. (513676)
1. (as root)
cp $PROMAX_HOME/sys/exe/lpd/queup /usr/lib 2. cd to /usr/lib
3. (as root) chown root queup 4. (as root) chmod 4755 queup
• ShowCat: The documentation does not explain that in order to run this program $PROMAX_HOME/port/bin and $PROMAX_HOME/sys/bin must be in the users search path. Otherwise users will get an error saying promaxpath not found. (513506)
Tape Devices: ProClient script does not run on 32 bit IRIX Systems. Attempting to access a tape device on one of these systems will generate this error (513567):
ERROR: UNABLE TO CONNECT TO IO2 CLIENT PROGRAM. Possible start-up script error or client program
The work-around is to edit the ProClient script: case ‘uname’ in
AIX) UnameS="rs6000";;
# IRIX*) UnameS="sgimips4";; <- change this line to IRIX64) UnameS="sgimips4";; <- these two lines IRIX) UnameS="sgimips";;
SunOS) UnameS="solaris";; esac
• NQS Queues: In the script
$PROMAX_HOME/sys/lib/nqs/init_nqs,
PROMAX_HOME is set to /advance change to your correct $PROMAX_HOME. (515371)
• Solaris Only: Boot scripts that are K-Shell (/bin/ksh) will not run during the boot process. inet.d will only run scripts that are/bin/sh. The script startrmi is an
example of one that cannot be used “as is”. The work-around is to make the syntax within the script conform to /bin/sh standards. (515494) EG:
PROMAX_HOME=/xx/yy export PROMAX_HOME
• Linux Only: The 2003.3 documentation regarding setting up Linux lp queues is not complete. Please download the file queue_setup.pdf from the Landmark ftp site. (516214)
product/ProMAX/v2003.0/port/help/rel_notes • LINUX Only: The TTS TAPE_REQUEST is not
communicating with opcon. ProMAX hangs with a tape request to opcon. (127983)
• Linux Only: The documentation for setting up Linux stinit.def file. Please download the file quick.pdf from the Landmark ftp site. (516215)
product/ProMAX/v2003.0/port/help/TTS
• LP Queues: There is a limit of 22 LP queues in ProMAX. (138847)
• LINUX Only: A local device name with less than 8 characters causes additional characters to append to name causing jobs to fail with error message: (148604)
FATAL TAPE SYSTEM RUNTIME ERROR:
A matching logical device name: [LOCAL8MMX] was not found in the DEVICES file.
The device.tts shows:
local8mm DEVICE="matterhorn:/dev/st0"
2D/3D Land Geometry Spreadsheet*
• See Also:Geometry Spreadsheet General
• 3D: Do not input a Receiver increment value greater than plus or minus one into the Pattern spreadsheet. If required, receivers can be renumbered to avoid
• 2D: Static column: you cannot interpolate statics in either the SIN or SRF spreadsheet due to existing 0.0s. These 0s cannot be deleted to make the columns blank. If you are importing data in which statics are available for some, but not all stations, they are written in the static column, but the entries between the actual statics will still be 0. This makes it impossible to interpolate between these values.
work-arounds:
1. Import Geometry file into spreadsheet, importing statics into the elevation column.
2. Interpolate using step 1.
3. Export geometry file into an ASCII file.
4. Import geometry file into spreadsheet, importing statics into the static column. (507313)
• Skid and Offset information may be lost if the geometry is being built by assigning midpoints based on existing index numbers in the TRC and the spreadsheet is sorted. This occurs because of the re-mapping in the TRC
domain. This problem can be avoided by sorting before entering skid and offset information. (507707)
• The SPS Import option ignores any uphole information in the SPS file. Upholes must be entered manually. (507758)
• Importing into the spreadsheet only matches by Station not by Line and Station. This could cause uphole times and hole depth to be assigned incorrectly. (512105) • The option to delimit while importing a UKOOA file does
not work. (303275)
• Offset header is not being loaded correctly. Azimuth in the Trace QC is correct; source and receiver locations are correct, but the offset sign is wrong on the near trace. (129292)
• In the binning menu ProMAX allows you to enter more than two values to the right of the decimal point. If you bin at this point these are the values that will be used. However if you save and re-enter this menu the values are rounded off to two digits. To get the greater accuracy
• The 2D Land Geometry Spreadsheet option to bin using existing CDP numbering and coordinate values is
redoing the values: TRC GEOMETRY CDP_X TRC GEOMETRY CDP_Y CDP GEOMETRY CDP_X CDP GEOMETRY CDP_Y
The work-around is to use Database/Header Transfer to put the CDP_X and CDP_Y trace header values into the TRC and CDP database manually, then use just the Finalize Database option of the 2D Land Geometry Spreadsheet, do not bin. (134913)
• Currently the import of SPS is only partially compliant with the documented standards. In the relational file, column 47 is identified as the "channel increment", which we import directly to the pattern spreadsheet as the channel increment. However, the standards allow this value to optionally represent the number of sequentially numbered channels at a given receiver station. There is no means of distinguishing which of these two modes to honor. The work-around via an awk script to modify the relational file to explicitly include all channel groups. (516639)
• AIX ONLY: The “Cross Domain” icon does not work in XYGraph. (144466)
Test
2D/3D Marine Geometry Spreadsheet*
• See Also:Geometry Spreadsheet General
• 3D: UKOOA import does not honor cable entry and will renumber channels if necessary. Our example problem is a 3D marine geometry with 6 streamers, identified by the last column in a UKOOA file, and the channel
numbers decrease from 240-1 on each streamer. The Import definition defines a column for the cable but does not populate column. The Import apply/append menu offers an option to renumber channels, but it starts from x and numbers to x+1. Decreasing channels or cables out of order will not tie to correct data channels.
calculate unique channels for each shot. However, you must make a series of edits. This works, but is hugely time-consuming for a 100MM trace database.
work-around 2: We can provide an awk script that
manipulates the UKOOA file before import. Call support for script. (507355)
• 3D: Multiple streamer patterns with different number of channels are not currently allowed in the spreadsheet. If required, the channels must be renumbered to a
common channel numbering scheme. (502371)
• 2D: If a marine geometry is defined with receivers ahead of the source, such as in a dual boat configuration, the sign of the offset is not calculated correctly. The sign of the offsets is created as if the cable is trailing the source. All other entries, such as Absolute offset, X/Y and Azimuth are correct. If a signed offset is required for any purpose, use Trace Header Math to set the signed offset appropriately. (503508)
• 2D: The Setup dialog box indicates station interval parameters are optional. For the Auto 2D options, these parameters must be entered. Failure to do so can result in incorrect geometry patterns. (505103)
• 2D: In Auto 2D, if the channel increment is -2, the far channel is eliminated.
work-around:Define one more channel than is needed. (507049)
• 2D: You must specify the Sail Line Azimuth entry under Setup in 2D Marine Geometry even though the menu says, “Optional”. If you do not make this entry, the default Azimuth of 1 is used, This can cause CDP fold errors due to “round off” errors. The fold can be doubled when the azimuth is not specified. (507330)
• 2D: The 2D Marine Spreadsheet does not honor multiple patterns for cables and will cause the job to fail.
(507311)
• When importing navigation data, there is an option in the “UKOOA receiver column definition” window that allows an attribute to have math applied. Multiplying by 0.0 has no effect. (507641)
• When importing a UKOOA file with negative northings, trace coordinates are imported correctly, but shots are read as positive coordinates. work-around is to multiply the column in Source spreadsheet by -1. (504235)
• The SIN spreadsheet column values for QC Dist and QC Offset may be switched depending on the specified streamer azimuths. Values such as 0, 90, 180, 270, and 360 are OK, but all other values switch these two
columns. (507760)
• The SOURCE ID column in a standard UKOOA 90 file is not being transferred to the SOURCE column in the sources spreadsheet. The work-around is to use an editor or the grep command to create a separate file containing the ‘S’ Lines from the UKOOA file. Then import these via the ASCII Import option. (508657) • If you start a 2D Land Geometry Spreadsheet in a 2D
Marine Line, you will get cdp_x and cdp_y in your TRC database even though they do not belong there. (They are not there if you start a new line with 2D Marine). If you copy a 2D land line to a new line and use it for a 2D marine line, the cdp_x and cdp_y values in the TRC OPF will remain in the TRC unchanged from the previous line after the 2D Marine geometry finishes. These values should have no affect on subsequent processing. (512220)
• When performing UKOOA Import and trying to change "Record ID" characters user is crashed out of import windows with following error: (513404)
Error: Attempt to unmanage a child when parent is not Composite
• Deleting a shot from the sources spreadsheet will cause CDP binning to fail. The work around is to leave bad shots in the spreadsheet and set the FFID to zero. Then run Geom Header Load by FFID and the zero ffid’s will be dropped. (303998)
• In the binning menu ProMAX allows you to enter more than two values to the right of the decimal point. If you bin at this point these are the values that will be used. However if you save and re-enter this menu the values are rounded off to two digits. To get the greater accuracy you must re-type in the true number. (276579)
• The documentation states that if you are entering binning parameters by hand, you must enter an appropriate X and Y grid origin and an appropriate azimuth relative to the Y axis in order to establish the CDP, inline and crossline numbering scheme. What is not stated is that this is the CENTER of the first bin. (516174)
• Problems have been reported in the Volume Viewer Editor when geometries are created with initial coordinates of X=0, Y=0. The work-around is to bias these values by some non-zero value. (134308).
3-Component Receiver Orientation
• In this process, the maximum value in a gate is a peak. If the maximum value is a trough, and you have picked on a peak, the output will be 180 degrees off. (503259) • In testing the results from the Hodogram Analysis I
compared them to 3C Rcvr Orientation. The 2
component works correctly, but the 3C does not rotate correctly. (513380)
3-Component Transforms
• SGI Only: The Eigen value ratio option accumulates CPU time, but does not produce any outputs. (503919) • If you select a user defined trace header for placement of
this attribute, the trace header must contain real
numbers. If an integer header is used, a single attribute is written to only the last trace of an ensemble. (504222)
3D Mix
• If you had not built a 3D PostStack database, running 3D Mix gives the following error:
Parameter MAX_DTRZ is not of type integer! It is of type character string
work-around:Fill out Number of inlines and Number of crosslines in the LIN database. Use DBTools, click View -> LIN, and Database to unlock the protected fields. (507335)
3D Poststack Geometry
a negative bin dimension) can generate X and Y values for inline and crossline inverse to the documented description. Quality check the database attributes after running 3D PostStack Geometry, and the sign of the Bin size in crossline direction parameter altered if necessary. (502241)
3D Post Stack Regrid
• In surveys where the first inline and crossline does not equal 1 this module may zero traces on the low
numbered inlines. (513857)
• There is a numerical noise problem when the input grid is oriented at exactly 45 with respect to the output grid. The work around is to adjust one of the coordinates so that the relative angle is not exactly 45 degrees. The fix involves only making the processing direction decision once. At 45 degrees, it doesn’t really matter whether the processing direction is inline or crossline (as long as the same direction is used throughout. (130491)
• In the usage section of this help file, it is not stated that a Post-Stack database must exist for the dataset the user wishes to alter in 3D Post Stack Regrid. This can be accomplished by running 3D Post-Stack Geometry. (13489)
3D Ref Statics Model*
• If SOURCES are in descending order in the geometry database, the corresponding receiver XYs appear flipped when describing the mode. This is a visualization
problem; it does not affect the actual model definition. To obtain the correct shot-receiver appearance, sort SOURCES into ascending order and refinalize the database prior to running this process. (503455)
3D Refraction Statics Inversion*
• Linux Only: The interactive mode of this program will not converge. It will run until it reaches the maximum number of iterations. The non-interactive mode does converge. (149431)
will halt. (293557)
Work-Arounds
(1) Use a supergather grid large enough to not violate this condition, then window later.
(2) Select the supergather by individual center-cdp numbers instead of the grid rectangle
3D Supergather Select
• If the trace header word SG_CDP already exists but has the wrong format type, the value of SG_CDP is incorrect. The work-around would be to put a Header Delete in the flow before this module. (513616)
3D Velocity Viewer/Editor
• If you say YES to specifying the bounds of the velocity field and select a sub-set of the data, then toggle the parameter to NO. You will still only get the sub-set previously specified. The work-around is to re-set the range back to the entire field. (301336)
• Using the smoothing option in this tool to create a velocity function at every CDP does not work. Although viewing this velocity field looks correct the resulting table may have missing or duplicate functions. The work-around is to use the Volume Viewer/Editor. Use INLINE and XLINE as coordinates and re-grid to every
INLINE/XLINE then save the volume. (508289)
Additive Noise and Spikes
• The ensemble/trace selection controls for where to place impulsive noise references internal counters of ensemble and trace within ensemble rather than any sort keys and trace header words. Thus 3:4/ refers to the fourth trace encountered within the third ensemble in the input stream. (514184)
• This may generate noise at the water bottom if NMO is not applied before the noise burst edit. (142347)
Alternate Machine
Amoco SIS Input
• This module may hang on the last trace of the input file, never completing properly. (513538)
Apply Residual Statics
• If an attribute is copied using database tools, it will not display in the popup listing after the copy. Exit and renter the menu to display the attribute. (502326)
Archive to Tape
• The current ctar code still exhibits a 127 file name character limit. (507370)
• Cannot archive a file of more than 2 Gbytes to tape or disk. (515505)
• Solaris Only: If you run the archive to tape flow and specify disk image with removal, the ctar session dumps core. This is only a problem if you request that the files be removed. (304597)
Automatic Gain Control
• When the difference between the smallest and largest absolute amplitudes in an AGC gate are extremely large an overflow can occur in the scalar calculation causing the entire trace to be zeroed. (512744) (305313 IRIX Only).
• This module fails using the “Apply and Save” option if the trace length is less than 500 msec. The error is: agc operator longer than trace length
The work-around is to use Trace Length to pad the trace. (513071)
AVO Analysis Gathers
• Running angle limited cdp gathers fails to 'angle limit' the last trace of the ensemble. The current work-around is to ignore this trace in further processing. (512116) • This module will output zero amplitude angle of
around is to eliminate these traces or change the trace type header to = 1. (513486)
• If you run separate jobs with min-max angles set to values like 0-20,20-40,40-60 and re-mute is set to NO., there is more overlap between the gathers than expected. This is currently under investigation. (125584)
AVO Attribute Stacks
• Setting the correlation coefficient sets the appropriate gradient values to zero but not the intercept. (303037) • The fluid factor stack (Attribute 9) is not being calculated
correctly. (513755)
• The Gradient and Correlation calculations are incorrect. Contact [email protected] for a possible fix. (150333)
AVO Interactive Crossplot
• On data with non-integer sample intervals, if you pick seismic polygons and cross-plot them, then stop and re-start the flow, the polygons may be shifted deeper in time. (507771)
• This module will not run properly in conjunction with IDA and DBTools. It is recommended to use Disk Data Input and Insert to pass pairs of traces to this module. (509457)
• Option to save Horizon picks does not function properly. No known work-around at this time. Also “Snapping” a horizon may cause the job to abort. The work-around is to pick and snap horizons in Trace Display then view them in this module.(509845) (509757) (509964)
• In AVO Interactive Crossplot, when you slide the bars on Crossplot Scaling, the labeling on the axes does not change to match the data. (303036)
• Snap option flips display. This may occur when using the horizon pick icon and then using MB3 to snap your pick. (512272)
• Adding points to the polygon may corrupt the polygon table. (512984)
• Setting Label Plots with AVO_ATTR to yes does not give any label at all. (512963)
• Selecting a polygon that encompasses ALL plotted
datapoints should highlight ALL of the seismic traces, it does not. The 1st and last trace are not highlighted. (304141)
• Using Horizon Attributes/Window Horizon can cause time axis and seismic display to flip so time 0 is at the bottom and time xxx is at the top of the display. This seems to happen when your windowed gate extends to the bottom of the display. The windowed horizon polygon is flipped as well. Any other manually entered polygons stay in their original location. When you turn off
Horizon Attributes/ Window Horizon, all goes back to the correct position. (512139)
• This fails to read the crossplot tables generated by IRIX or AIX, but works in Solaris (1998.6 and 2003.0).
(131226)
AVO Volume Reconnaissance
• Although the help file does not state this, the input volume should be padded. Otherwise you will get this error:(508409)
Build Unisec Parmfile
• The following error message is generated if Panel=On, the plot mode is color, and the total length of your plot is expected to exceed the plotter paper length.
Error, unexpected EOF reading color trace
work-around: Make your plot fit the paper. (505023) • There is a problem using the “grey” option in a color
overlay. The positive side of the wiggle trace disappears once a trace is clipped. The work-around is to replace the values in the
$PROMAX_HOME/sys/exe/larson/lstbin/coltab.txt for "GREY" with the values in
$PROMAX_HOME/port/misc/unii_whtblk.rgb. (513419) • Setting PARMS,SIDEL=ONLY disables EVALS,LDIR=90.
and set PARMS,SIDEL=R (for right side), L (for left side) or LR (for both). YOU MUST PASS DATA for EVALS,LDIR to be honored. (513621)
• This module will not read in horizon pairs with CDP values greater than 32,000. (143043)
CDP Binning
• It has been reported that if this module attempts to write to an OPF partition that is 100% full, the database may become corrupted. (138796)
CDP/Ensemble Stack
• Applying Final datum statics after stack updates TLIVE_S and TFULL_S incorrectly. TLIVE_S and TFULL_S are altered by close to 2* fnl_stat instead of 1*fnl_stat. work-around: Use Trace Header Math to add FNL_STAT to TLIVE_S and TFULL_S after stack.’Reapply Mutes’ in further programs will be fine. (513345)
CDP Trim Statics
• On Marine data you will still need to bin receivers to get this to run. An SRF OPF is required. (515166)
Color Edit
• A 3D license is required if you start this process from a flow. If no 3D license is available, start the Color Editor from an interactive display tool. (505907)
Common Offset F-K DMO
• On some datasets the remove padded traces portion of this macro does not work. Checking the job.output file and comparing the number of traces output from the DMOFK_PANEL and RMPAD_TRACES steps will show if this is occurring. The work-around is to use a module like Disk Data Input to eliminate the traces flagged as padded (e.g. PAD_TRC=1). (508875)
Convert 2D Table to 3D
If you try to append a 2D table to an existing 3D table you will get the following error:
The work around is to edit the menu velTo3D.menu, The line outvel2 should have type_desc instead of select_item. (514114)
• The database method for mapping 2D to 3D fails. The other two methods work properly. (136809)
Create CGM+ Montage SDI
• Users have reported that attempting to use this module with Version 2000 SDI_MONTAGE fails with the
message:
libXm.a [shr_32.o] NOT FOUND
One work-around is to create a script called sdi_montage that un-sets the variable LIBPATH before executing the sdi_montage executable. (512895) NOTE: Fixed in 2003.0
Create CGM+ Plotfile
• A signal 10 sigbus error occurs if you try to overplot a header value created in the same flow. You should
output a file with the new header, and bring the new file into Create CGM+ Plotfile with Disk Data Input.
(500653)
• The process dies with a memory fault when creating an automatic sidelabel on an input file lacking a CIND file, such as a SeisWorks Input or Synthetic Trace
Creation. You should output a ProMAX file prior to creating the CGM+ file. (500449)
• If plots are not at 400 or 200 dpi, label text fonts cannot scale exactly. You should scale your plots to 400 or 200 dpi, to get an exact scaling. (501007)
• 3D timeslice only: When plotting timeslice traces, CDP values are null. To plot timeslice traces in CGM+ format, use Trace Header Math to set CDP = xline_no or
inline_no, depending on timeslice orientation. (501790) • Turn off the label for overplot attributes does not
work correctly. When overplotting attributes, turn off labeling by selecting Yes to Include Label, and creating a blank entry for the Label Text field. (501771)
• This process currently handles up to 8000 monochrome samples and 4000 color samples per trace. Using a greater number of samples results in the errors:
scaling mode 8224 illegal scaling mode 8192 illegal Illegal Element Id in Class 2
INVALID point 40556 class code val: 2 0 0
work-around:Run the display using multiple time trapped inputs to create larger plot files. (501908)
• When using Input Trace Order to plot, either the individual trace annotation, or the timing line
annotations can be improperly shifted, depending on the use of a trace gap. Avoid the problem by using Ensemble Redefine before Create CGM+Plotfile, or CDP can be used rather than Input Trace Order. (502165)
• If you have a large number of plot layers for
Traces/Plots, some parameters can be lost at the bottom of the menu. Toggle off the topmost parameters for Enter RMS Explicitly for full access to all
parameters. (502157)
• If the Number of traces for Gain Calc. is specified greater than the number of traces to be plotted, and an Ensemble Gap is specified, the data overplots the timing line annotation. Specify Number of traces for Gain Calc. no larger than the total number of traces to plot. (502608)
• Reset the timing on a zipper cannot be reset from within the interactive menu. A value of 10 is always used. If required, the value can be reset by using a private copy of the cgmplot_socket menu, and editing the default value for zipper_msec. (502756)
• Display a down line only can incorrectly generate text in the seismic data. There is no work-around for this problem. (502885)
• Upon creating a plotfile, the plot control file is set with color_cgm = True, even if the trace display is black and white. This can cause some plotting software to make three passes over the plot. If so, edit the control file (xxxx_cntl) and set this value to False. (503521) • When plotting a large number of traces with a
can appear to disconnect, and then wrap around at the end of the section facing the wrong direction. (503770) • The sidelabel can be truncated if you input a value for
Amount of whitespace greater than zero, and the resulting label is larger than the seismic data used for plotting.
work-around: Find the current length in the cgm_cntl
file; this is the 4th parameter after VDC_VIEWPORT. Add the amount of whitespace required and set the minimum side label size in the menu to the increased size.
(504097)
• When plotting a dataset containing every Nth ensemble or specifying INLINES:XLINES as sort keys, a large cgm.bnxx file may be created in the flow directory if wildcards are used in the Disk Data Input sort list. The work-around is to explicitly specify the range of
ensembles in the input step. (301354)
• If you choose the posting method of ORDER and the selection list begins with 1, the second trace will actually be annotated. In order to label the first trace the
selection list should begin with 0. (301843)
• Solaris Only: Executing the exact same flow on AIX vs. Solaris systems produces two different size velocity boxes. The Solaris version has more space between the time and velocity columns. No known work-around at this time except to use The Unisec modules. (509697) • A Create CGM+ Plotfile flow that has a seismic dataset
and a color cell fill overlay may have the color plot over the wiggle traces, depending on the number of traces for gain calculation. The work-around is to specify in the menu more traces than are being passed for gain calculation. (512199)
• Excess amounts of blank paper may occur as the result of the VDC maximum X coordinate extent being set to 32767 in the generated CGM+ plotfile. The potential length of plot may come out to be (32767)/(dot
resolution of plotter). Contact support to see if a patch is available. (130422)
Crooked Line Geom Spreadsheet
• SGI Only: Attempting to open a saved track will cause the Geometry Spreadsheet interface to crash. (513944) • When you choose the Layout Bins Icon there are 3
options MB1,2,3. If you choose MB1 first then MB2 will no longer work. If you wish to experiment with the various options use MB2 first. (512663)
Database Display
• NULL values for an X/Y database attribute cause
projections to other domains to fail. NULL values can be filled using the Math/Fill operation in XDB Database Display to correct for this problem. (503398)
• AIX Only: Database display is not displaying the null values as triangles on the top and bottom of the graph on an IBM. On the IBM, there is no way of telling where the null values occurred. The only way you know you have nulls is <null>. will be posted by the attributes that have nulls. (515341)
• Using the option 3D - Display - XYGraph then choose any three X,Y,Z attributes from the TRC order. Then enable the “Alternate Domain” option, the display may crash. (120125)
Database/Header Transfer
• When creating multiple user defined headers, the created header name can contain trailing string values from one of the previous entries.
work-around: Place the shortest user defined string first
in the list of header transfers or call the process multiple times. (503391)
• The database will not accept the transfer of 8R floating point headers which can be created in a SEG input step. The fatal error is:
Database format = 2 Header format = 3
work-around: Obtain ASCII files for spreadsheet import in order to place this data in the database. (504225)
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)
• Problems can be encountered when displaying a plot which contains NULL values. An error returned to your shell indicates:
Ensure failed ((int)((xMax-xBase)*xScale)<_nBin), file “/advance/port/src/lib/dbtX/Histogram.C”
NULL values can be filled using the XDB tool to display these attributes. (505282,515339)
• This process fails when attempting to display stations which have 8 digit values. The error will point to a failure in /advance/port/src/lib/dbtX/MarkersO.C. There is no
work-around for this problem. (506097)
• SGI ONLY: Accessing large (in our case 24 million traces) TRC Database attributes may cause DBTools to core dump. For SGI, setting the variable
DBTOOLS_SERIALIZE_LOAD may help for surveys less than 10 million traces. For the larger databases, you will have to create smaller databases for viewing and can merge later on.(507828)
• If you are selecting traces in DBTools and sending them to a process such as Trace Display via IDA. DBTools may appear to hang then eventually return the error: ensure failed line 109 of /71/advance/port/agc/ar.c
This is caused by the user selecting traces from DBTools that are not on the sort list in Disk Data Input. (507869) • In the tabular view, when editing cells, sometimes this
tool will stop accepting edits. At this point in time no cause has been determined and the only work around is to use XDB and ASCII export, make the changes, then re-import. (507973)
• While editing in tabular view entering certain values such as 5.1 will return 5.099999 instead. (507974) • When altering any entry the LIN order it is recommended
that you use the XDB tool rather than DBTools. (508331,508722,301008)
• The ability to interactively display traces to Trace Display will not work if more than one attribute is selected in View - Overlay. (515016)
• Taking the log of an attribute that has a 0.0 in the array will fail. There is no error message DBTools only outputs results up to the trace with the 0.0 value. (515033) • Delimit ranges may report incorrect min/max values if
the bin grid definition is smaller than the actual dataset. (130864,130808)
• Viewing "Summary statistics" "focus” on, “exclude selection" is not working. (130607)
• User brings up DBTools-->File-->XDB Database Display and goes to SIN database to display attribute. If he then tries to switch to another line XDB Display crashes. The workaround is to go back out to ProMAX UI and re-enter DBTools under other line. (128736)
• SGI Only: Attempting to copy an attribute will cause DBTools to crash. Work-around: use XDB or dbmath to copy the attribute. (518323)
Disk Data Input
• See also Interactive Data Access.
• On large datasets which are sorted requiring overlapping groups of traces, such as sort string 1-9999(3)[4], the sort can fail with the following errors:
Failed to locate position of trace within the dataset (Memory sort) Program encountered a significant internal error and cannot continue. The error results from a situation that was not anticipated by the developer (Disk sort)
work-around: Break the input dataset into smaller
pieces. (502021) • The error:
Corrupted trace or trace header encountered
has been encountered after reading in field data which has a non-standard TRC_TYPE value. If this error is encountered, you should use a Trace Header Math step to reset TRC_TYPE =1 during the field tape input flow. (502653)
• Certain combinations of sort keys such as CDP: CDP_Y may generate memory errors. The work-around is to use Inline Sort. (512181)
• It has been reported that users have encountered problems sorting datasets that have individual
TRC/HDR files greater than 2 GBytes. We recommend that users set the size for primary and secondary storage in the config_file to 2000 or less. (512529)
• Certain sort combinations where the group size is larger than the increment e.g. 1-200(4)[19] may generate a null trace in the resulting output dataset. (145744)
Disk Data Insert
• When Observe Dataset Boundaries is set to Yes, the LSEG_END header is not set to 1 on the final trace of the inserted datasets. You can manually override the header by selecting the appropriate trace in an IF block, and resetting the header using Trace Header Math. (502692)
• When inserting sorted datasets in Merge mode the inserted datasets may not be merged into a single ensemble. The datasets are sorted correctly, but can split on the input boundaries. If required, the Inline Sort or Ensemble Redefine process can be used to create single ensembles on the fly. (503659)
• Maximum traces per output ensemble is limited to a value of 9999. To obtain larger ensembles, change the actual MAXDTR values in the disk_insert menu, or use Ensemble Redefine within the job stream itself.
(504159)
• Occasionally this module will fail with an error
indicating that the sample rates of the two datasets do not match, even though a MB2 history of each dataset indicates they are the same. This is due to the executive seeing the sample rate as 1.999 or 2.001 rather than 2.0. The work around is to use the sample rate override option in the menu. (507858)
• SGI ONLY: This module will fail with the message: Typed I/O error - bad file handle
If there are more than 5 inserts in the flow, and the first dataset has only one trace. (512619)
Disk Data Output
• When using the overwrite option after modifying a geometry, the expanded dataset information cannot be updated for the CDP extents. Using the MB2 dataset information listing will show incorrect extents. The problem can be avoided by outputting to a new dataset instead of using the overwrite option. (503387)
• This process writes in round robin fashion to all secondary partitions listed in the config_file until encountering one or more full filesystems. Multiple TRC/HDR pairs are then written to the next non-full filesystem found in the config_file list. For example, if Disk 1 and Disk 2 were full, followed by Disk 3 and Disk 4, Disk 3 would receive TRC/HDR files 1,2,3, 5,6,7,... and Disk 4 would receive TRC/HDR files 4,8,... While this does not create an actual output problem, it can potentially cause disks at the top of the config_file list to fill more quickly than disks at the bottom of the list. (503763)
• If traces are appended to an existing dataset, the Maximum traces per ensemble is reset to the
maximum number of traces in the appended dataset. A subsequent Disk Data Input step using the Get All option will output ensembles based upon the final appended value. An Ensemble Redefine or Inline Sort can be included after the append step to ensure that the number of traces per ensemble is set correctly. A
simple sort on Disk Data Input will also provide a work-around if this situation is encountered. (503949)
• Users have reported that at times the CIND file for a given dataset becomes unusually large. At this time the cause has not been determined. The suggested work-around is to copy this dataset into a line with no
database, or write it out as SEG-Y. Then read it back in. This will shrink the CIND file to a more normal size. (513082)
• If you are using MB2 to check the status of a dataset while it is being written to disk it is possible that ProMAX mistakes this as a duplicate trace being created and stamps the dataset as not matching the database. (513095)
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
The workaround is to re-pick the gate defining the shallow layer first.(513945)
Eigenvector Filter
• SGI Only: This process may stall during execution if the design gate contains zero amplitudes. (507074)
work-around: Use a design gate that encompasses only
live data.
• SGI Only: Program stalls when amplitudes greater than 100 are used.
work-around: Use Trace Math to scale down amplitudes.
(508141)
Emacs Editor
• Linux Only: Does not run from within the ProMAX User interface. (516052,130873)
ESI Disk Data Input
Expand Flex Binning
• Application of this process will reset the global data domain of the relevant dataset to unrecognized. While this will generally not affect any subsequent use of the dataset within the processing system, the global flag can be reset if needed using Trace Header Math (change attributes/data domain). This is fixed in the 2003.3 release.(503954)
• This module will allow data to be input in any sort order. However it will try to hold enough space in memory for 9 ensembles. In datasets where the default primary key is something like INLINE there may not be enough memory to hold 9 ensembles and you will get an “Ensure failed” error message. (513202)
Explicit FD 3D Depth Mig (SMP)
• Using values other than the default for Maximum Depth may generate results that are “stretched” below this depth. (514077)
• Occasionally when the re-start option is selected, the job.log file may get corrupted generating the following message:
Current tool is ST_FXYM3D (number 7 in the flow) Message is: Error reading from socket. The corresponding socket tool probably died. Stopping Program. Errno: 0 (Error 0)
The work-around is to delete the corrupted line. (128572)
Explicit FD 3D Time Mig
• Velocity inversions can cause low frequency artifacts. (301212)
• Increases amplitudes by factor of 100. This happens for all platforms, but only if the menu option Shared-Memory Parallel Version is selected. If the option Network Parallel is selected in the menu, the problem does not occur. The problem has been fixed using the Explicit FD 3D Time Migration (SMP) module. (513014)
Extract 2D Table from 3D
• When you select Stacking Velocity for input this module will also generate an inaccurate interval velocity in depth table. (513138)
Extract Database Files
• A full extraction does not complete the grid information in the LIN database. Appropriate entries should be edited. A more robust approach is to bin and finalize that database using a Geometry Spreadsheet
application. (505914)
• For marine geometries, the marine flag may not be set. (505912)
• This process checks for CDP values in the headers, even when Extract CDP binning is toggled off. Use Trace Header Math to create a temporary integer CDP value. (505939)
• An Invalid CDP X-coordinate error message appears when attempting to project coordinates to CDPs after a full extraction of the database. For example, projecting SRF Geometry Station to CDP Geometry Station.
(507386)
work-around:Use Math->Fill for both the CDP Geometry X_COORD and Y_COORD before projecting.
Finite Difference Modeling
• When inputting a dataset and using the geometry from the headers, if you have a roll-on shot situation, the global shot fold is set by the first input shot. Because the roll-on increases the fold at the next shot, your job can abort with the following error message (507343):
The number of traces in this ensemble is more than specified in the global variables
• Users have reported getting SIGBUS errors with this module while attempting to use the Ormsby wavelet. The work-around is to switch to the Ricker wavelet. (512535) • There is a problem with the menu. If the user first
selects the Normal Point Source option and wants to use a trace dataset for header information (Take
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 Errorpointing 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
Gated SC Decon 4: Cleanup
• This module is designed to delete the INI and SOL scratch files. This module will run and complete normally even if there are no files to delete. (515530)
Geometry Spreadsheet General
• If shots or receivers are deleted in the spreadsheet and the database is subsequently rebinned and refinalized, any previously created database attributes generated outside geometry definition, such as first break picks and statics, will not match the new database description. Those attributes should be recreated if they are required in any subsequent processing. (502579)
• If shots are deleted in a spreadsheet initiated from an extraction or UKOOA import, the File/QC option from the TRC database will hang. (502964)
• Parameter tables defined with integer values for sort keys larger than plus or minus 2**23 (8388608) can fail with the following error:
Unable to find SIN given FFID xxxxxxxx
Within the geometry spreadsheets and database, integer attributes can be entered with a precision up to plus or minus 2**31, and trace headers are loaded correctly during the Inline Geometry Header Load process. However, parameter table accessing keys using the larger values fail due to truncation problems. (502967)
work-around: Repick or recreate the parameter table
based upon key values that are not similarly affected, for example, using SIN or SOURCE rather than FFID. • When interpolating, if zero values are in the spreadsheet
and “Interpolate all values in marked block by record number” is selected, the zero values are replaced with interpolated values. If NULL values are in the
spreadsheet and “Interpolate all values in marked block by station number” is selected, the NULL values are not interpolated. (504995)
• The Undo option in the Edit menu item can fail to operate correctly. (505307)
• 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_NO’s for the line. It is possible that the resulting min-max range is not accurate for the entire line. The work-around 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 “CDP’s 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.
work-around: Break the ASCII file into several smaller
files and run this process several times. (501070)
Header Values
If you attempt to list a trace header name that is only one character long. The work-around is not to create trace headers of one character. (303189)
History Viewer
• The dataset history viewer will not access and display the residual statics database filename if the Normal Database option is not chosen in the Apply Residual Statics menu. If required for display purposes you can save the history viewer session, edit the file, and then read that file back into the display session. (500929)
Hodogram Analysis
• Users have reported this module generating theta and phi polarization angles that make no sense. It is
suggested users check the output listing closely for angles that are too large. (513376)
Horizon Flattening
• Although code says 50,000 samples are allowed in the pick table, we found that only somewhere between 12500 and 15000 picks are allowed. That is, a table with 12500 picks worked, while table with 15000 picks failed with:
Error reading CDPs and TIMES from the horizon table!
work-around:Break into smaller pick tables (~12500 picks per table) and run on subsets of data. (507364)
Horizon to RMS Velocity*
• During the conversion to RMS, velocities are output only for CDPs covered by the first horizon (when multiple horizons are selected). If the first horizon cannot encompass the entire line, run this process multiple times, appending the output files as needed. (503109)
Horizon Velocity Analysis
• The median and mean functions are switched when running in the edit velocities mode. Use median
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 2indicates 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
difficulty using the backwards arrow. Using the back arrow to go back one ensemble works the first few times, however, paging forward and backward three or more times, may take you back to the beginning of the sort. From this point on, the back arrow will take you to the beginning of the sort unless you specify a new sort. (507388)
• When using IDA with Trace Display, IDA can fail when requesting more than 600000 traces. (507462)
• When multiple applications are set up to run IDA from a single X-server, all applications will send and receive the same PD messages. Avoid multiple IDA sessions from a single screen unless it is intended to use the same traces by all active IDA sessions. (506040)
• If IP address is specified rather than host name for display device, IDA displays first ensemble then hangs. the job runs fine without IDA. (511240)
• Inline Geom Header Load in ProMAX 2003 behaves differently on marine and land data. If the input dataset for Geom Load has some dead traces (TRC_TYPE 2), land data processes all the traces while in case of marine data dead traces are dropped. (1147104)
Insight Data Input
• LINUX Only: Fails with a socket error, no known
work-around at this time. (518077)
Interactive Radon/Taup Analysis
• Attempting to use the SUBTRACT option in this module may cause it to fail with a signal 11 error. There is no known work-around at this time. Fixed in version 2003.3 (513560)
Interactive Spectral Analysis
• The process fails with aSIGSEGVerror when using stacked data on input, and the Primary header for trace label is left defaulted to Source. Set the labelling header to CDP, or some other poststack entry. (501620) • If only one trace is input the program fails with the
“/advance/port/src/lib/agC/Bytemap.C” line 70
work-around:Input 2 different traces in Disk Data Input.(506977)
• If you perform an extreme or microzoom on one of the tiles such as the spectral or phase display, you can expe-rience the windows hanging while the screen refreshes or the process can exit out of the X-window. (507133) • Solaris Only: You may experience Grayscale colormap
problems if you:
1) Run a ProMAX session without other applications, such as SeisWorks which will feed ProMAX correct colors.
2) Select Multiple subsets in the ISA menu. (507284)
work-around: If Interactive Spectral Analysis displays
strange colors or black, click Data ->Trace Display -> Color map-> Color. Then select Options -> Spectral Analysis. This sets Trace Display to the strange colors. Go to your original display and select Data -> Trace Display, your colormap is switched back to Grayscale. • If you iconify then restore the display access to the color
map is no longer possible. The work-around is to re-start the flow. (515299)
• The method used to scale the forward FFT in this module differ from the one used in Trace Math Transform. The latter is more accurate. (126876)
• Solaris Only: The T-X display will be all black is the Xdefault *.useColorObj: False is set. (138726)
Interactive Velocity Analysis*
• This process will still run but is no longer supported on the current certified platforms. You are encouraged to useVelocity Analysis.
Interactive Vel Editor*
• When using the Input/Set velocity option with a value of 0, the stored values are set to 1.0 e-5. If hard zeros are required, you should first set a constant non-zero velocity, and then add the negative velocity value in a
Interpretational Mig. Vel. Analysis
• This module will fail with the message Abnormal termination Signal = 10if the input dataset is missing any CDP’s. (509261)
List/Restore from Tape
• The option to Restore 5.0 does not work. To restore 5.0 Archives, run the tar command from the UNIX command line. 5.0 Archive files are written with a ‘./’ prepended to the full file name. (500856)
• When restoring a dataset from a Line/Survey, you are prompted for the Former Area name. The parameter can be filled out, but is not used during the restore process. (501777)
• Upon completion of any Restore operation, the
job.output file should be reviewed for the occurrence of any UNIX errors. The restore job may continue to
completion, even though errors similar to the following may exist:
Unix error - broken pipe
ctar: Error reading file xxx/yyy/...
The dataset affected by the error can be restored in a rerun of the Restore operation, selecting the appropriate dataset. Individual files can also be restored by running the ctar executable from the command line. (502043) • The following error can be encountered when restoring a
ProMAX Release 5.1 archive:
Encountered checksum error on file xxx/yyy
work-around: Set Ignore checksum errors to Yes.
Warning messages are still printed for those files which encounter checksum errors, and the integrity of those files should be verified if possible. (502019)
• The Header Dump option does not work, failing with the error message:
No mode (-c, -x, or -t) was specified
There is no work-around for this error. (503124) • ProMAX looks in the original secondary storage
rather than using the secondary storage directories listed in the config_file. (507033)
• When restoring a new AREA, the user interface will not automatically refresh and show the new AREA. The work-around is to either add a new AREA or select the “config” button at the bottom of the user interface and toggle the “Sort Areas “option from yes to no. Either of these will cause the user interface to refresh and show the new name. (301664)
• Setting the parameter “Use primary storage for trace files = yes” does not prevent ProMAX from attempting to write to secondary file systems. (515425)
Make Database Basemap
• This process requires a ZMS license feature. If you do not have a current ZMS license at your site, we have included a demo ZMS feature to enter in your FLEXlm license file. This entry can be found in the file:
$PROMAX_HOME/etc/zms.license.
• If PD is not running, the program fails with the error: Could not open a PD connection. Error = 300000000
work-around: Start PD manually with
PROMAX_HOME/port/bin/start_pd or run another program that will start PD, such as VVE. (507356) • Linux Only: This module fails with a PD related error.
No work around at this time. (516196)
• The Zycor routines used by this module have a limit of 80 characters for file names. The error message is: Error submitting deck to ZMS Server
Work-around: Create short symbolic links to
$PROMAX_HOME and $PROMAX_DATA_HOME. (518724)
Marine Trace Decimation
• This module sets the TRC_TYPE value to be the same as the last trace decimated in the ensemble. If this happens to be something other than 1 it could result in traces being dropped from a dataset. The work-around is to use
Merge Database Files
• The following error results if one of the line names begins with a numeric value:
Error occurred in OPF routine: MERGE PROCESSOPF unable to initialize source area: xxx, line: yyy unable to perform merge
The problem can be avoided by renaming the line to start with an alphabetic character. (502233)
• You can experience problems when trying to merge database files in conjunction with a previous ProMAX 5.1 database. The work-around is to use Extract Database Files to create a database under the current version. (507234)
Migration Vel Analysis
• LINUX Only: Fails with the following error. (517578) Parameter ifx does not exist in the packet file! Quitting
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.
work-around:Create a new line. Place Extract Database Files in flow before NN Horizon Picking (TRC exists). • This module will not run on 3D un-stacked data.
(513180)
Noise QC Monitor
This process has been compiled for AIX systems only. (300405)
Normal Moveout Correction
• 3D Only: This module uses the CDP_X and Y coordinates of the first trace in the ensemble to
determine the interpolated velocity to use. If these values are inaccurate, or different from the rest of the traces in
• NMO correcting data using velocities output from 3D Dip Velocity Analysis yields a SIGBUS error on Solaris, a SIGSEGV error on IBM, and runs on SGI but produces bad results (traces with amplitudes of 0 or a constant number) (123666)
Work-Around: You have to use a statically linked
executable from ProMAX 6.2 with a 6.2
$PROMAX_HOME/port/misc/header.list and 6.2 menu’s.
Pad 3D Stack Volume
• Some users have reported that when padding by inline, zero fold inlines are not output. (512543)
• Putting Trace Header Math tools that generate negative ILINE_NO values after a Pad 3D Stack Volume corrupts the ILINE_NO trace header values. The work-around is to put a Disk Data Output after Pad 3D Stack Volume and a Disk Data Input before the Trace Header Math. (512950)
Pad Traces
• If you sort input traces with duplicate CDP’s existing within the primary sort order (Common Offset DMO binned data), Pad Traces followed by a Remove Padded Traces drops all but one of the duplicate CDP traces. If the Remove traces is included in Pad Traces, all duplicate CDP traces are dropped. (500689)
• The program does not function properly if you select the option to remove duplicate traces in a bin, and the last trace in an ensemble is a duplicate. (505508)
Parallel Max. Power Autostatics
If the number of inlines is not evenly divisible by the number of nodes this module fails with the message: (132520)
Bad start INLINE number
