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
Parameter Table Editor
• When you use CREATE to make a default table, values for NULL are 0.0 and 1000.0. Should be 1, otherwise when used in VVE module crashes with following error: (507752)
Warning occurred Message is:
Unexpected Z description, TIME. Changing to TimeAssertion failed: jy>=0, file /seg/71/advance/port/src/lib/agfc/tb3.c, line 447
The next sub-flow will not be executed due to errors Abnormal termination (/ProMAX/sys/exe mainWin.exe) Signal = 6 (Core file generated)
• 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
As we did before, check the zeh_plotfile script to make sure your NODENAME, PASSWORD, SCRDIR,
DAEMDIR, and PRGDIR are set correctly. Then simply copy this $ZEHHOME/config/zeh_plotfile script to your $PROMAX_HOME/port/bin directory. (you can rename the zeh_plotfile script that is in your
$PROMAX_HOME/port/bin directory to something else to preserve it first). If you are using OpenWorks, you can also copy the $ZEHHOME/config/zeh_plotfile script to the $OWHOME/hardcopy/bin directory. Make sure this script exists in your $ZPSPRG directory as well. You should then be able to successfully run Plot CGM+ Plotfiles* as long as your config_file file has your plotter device defined and cgmplot line filled out properly. (131309)
• SDI Only: This module is in-compatible with the latest version of SDI software. Work-around: submit plots from the SDI GUI. Contact [email protected] for a possible patch. (145361)
• The UNISEC Create CGM+ module does not put the VDC extents in the .cgmp file, since the .cgm file is metric the extents are not required by the rasterizing software. However Plot CGM+ Plotfiles is expecting them and fails.
Work-around: Submit plots via the plotting vendors GUI
(SDI,Zeh, Larson) (148249)
Post-Stack Inversion
• Does not check min and max frequency values for valid input. (508075)
• The threaded version of this module runs much slower than the non-threaded option. (515603)
Progressive Mute Analysis
• In 3D, if the mute table is picked on CDP ordered data it should be resolved before using this module. Otherwise the extrapolation is un-reliable. (507672)
Prestack Kirchhoff 3D Time Migration
• TMPDIR is being prepended to scratch directory path. If you have TMPDIR being set somewhere, you may find that TMPDIR will be used as your scratch directory
This can be verified by running UNIX Commands: show environmental variables in your flow. (513228)
work-around: In your config_file you may insert the
variable: merge temporary directories: psh in order to override what is being set by TMPDIR.
• SGI: Restart from checkpoint fails w/ signal 15 if you do not have a Disk Data Output in your flow. This seems to be random on different SGI machines. (513213)
• The downward statics are being applied in full but the upward static is about 1/2 of what it should be. A statically linked new executable is on the ftp site under. product/ProMAX/v2003.0/<platform>/exe
README_127776 and kirktime3d.exe_127776.Z (a compressed tar file) (127776)
Pre-Stack Kirchoff Time Migration
• This module will fail if you set antialiasing to yes and let it compute (0.0) trace spacing. Work around is to input a valid number. (508042)
• If you request specific offset planes and ask for every cdp to be output, the job fails with a SIGBUS error. The work around is to explicitly set the output bounds to remove the edge CDPs, or do a Get All in Disk Data Input. (702352)
• Linux Only: This tool fails with a socket accept error. Contact [email protected] for a possible patch. (147022)
Prestack Kirchhoff Depth Mig.
• AIX Only: This module fails with a segmentation fault message. (134149)
• AIX Only: This module fails with a segmentation fault message. (134149)
• If you are specifying output CDP increments greater than the input CDP increment, anti aliasing filters will be applied. With coarse output CDP spacings, the program will perceive almost all the dips except for the flat ones to be aliased, and therefore all your dips are filtered. We recommend an output CDP increment equal
Prestack Wave Equation Datuming
• This process requires the trace header SRF_SLOC. This header is not always defined for geometries described under the 6.0 release. Use Trace Header Math to set SRF_SLOC = REC_SLOC if required. (502110)
ProMAX 3D Viewer
• After changing data range, color or scaling parameters you are asked to reread the data volume. This second re- read is not normally required and the dialog box may be dismissed. (507806)
• It has been reported that sometimes if you have multiple “entities” on the screen, i.e. combinations of opacity and animation, when you change the parameters of the opacity cube all of the “entities” disappear and you have to reread to get them back. No other known work-around at this time. (507808)
• The environment variable TMPDIR is not recognized when creating CGM files. The temporary files always go to /var/tmp. If this directory is too small a possible work-around is to create a link pointing to a larger filesystem. Or set the environment variable TMPDIR prior to runing this module. (512924)
• The 3D Viewer in Promax will not run without an
OpenWorks license available. In 1998.6 it gave the same error, but then went ahead and started the viewer.
Contact [email protected] for a fix. (132103)
Pulse Test
• SGI Only: This module generates incorrect results on IRIX systems. The work-around is to use Interactive Spectral Analysis to view the amplitude and phase spectra. (510497)
Q Compensation
• This module behaves differently depending upon
whether you select the menu from the VSP interface or the 2D/3D interface. If you are applying Q
Compensation to normal seismic data, be sure that your flow is built from either the 2D or 3D interfaces.
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
It is not narrowed down to any specific type of model but instead is random. (513205)
Reflectivity/Synthetic Logs
• The option to add multiples/transmission losses to the synthetic traces is in error. The amplitudes are too low and the polarity is reversed. The work-around is to use either Finite Difference Modeling or Synthetic Trace Generation. (508201)
Refraction Statics
• Linux Only: When attempting to edit the GRM Depth Model using MB1 to select does not always
register.Cycling through the solutions may cause it to register. (130535)
• Linux Only: If you display traces while editing first break picks the position of the SIN may not be correct until you begin to move through the volume. (130534)
Refraction Statics Calculation
• If you choose to use refractor velocity option in the statics calculation, rather than user defined, then you must also calculate the depth model at the same time. Otherwise you may get extremely large statics output. (507822)
• If the sort order in the Sources spreadsheet if different from the Receiver Spreadsheet Refraction Statics will generate an incorrect depth model. The work-around is to sort the spreadsheets so that both are increasing in the same direction. (126886)
Resample Log
• This process may add zero samples to the bottom of the log. If required, a Trace Length process can be used to bypass these samples. (503923)
• There is a problem with Resample Log and Well Log Pad to Surface being in the same flow. (507238)
work-around:Run a Well Log Disk Data Output and Disk Data Input between the resample and the Pad to
surface.
SEG I/O General
• See also Tape Administration.
• When Input primary selection choice is not set to Input All, the process will read a maximum of 50,000 ensembles. (501900)
• Maximum data block size in bytes in the SEG read menus is now obsolete and will be ignored if set here. You now have to set that in your device.tts by using the variable MAXBLK="nnnn". (512672)
• The NREW (no rewind) parameter in the device.tts file is not being honored. Using NREW+NUNL may operate properly. (514411,515409)
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.
There is no known work-around at this time. Contact [email protected] to see if a patch is available. (509031)
• Although the problem of reading FFID values greater than 9999 has been addressed, there is still a problem in the menu that prevents sorting on FFID’s greater than 9999. (510983)
• When re-mapping headers the job.output will report 2 times the actual value of the byte location being re- mapped. (512469)
• ProMAX is unable to completely extract geometry
information from the Western version of RAPS 2000 Seg- D tapes. (513039)
• Menu: omit records of type: Docs specify that you should be able to type in a string like 1:5:10:14... however the emacs widget does not appear and you cannot type this type of string. (512037)
• Sercel 408 format: Source and receiver point and index number are not properly mapped from the SEG-D
header to ProMAX. (513969) The workaround it to remap them manually.
Main Header Mapping: S_LINE,Shot Line,2I,,,69/
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