and then run SEISBR again.

Cross-Platform Issues

1   There are some problems related to SGI backup/Solaris restore.  If these occur, either use the 'dd | cpio'
    route, or add a tape drive to an SGI on the network and try again.

2   Backups generated under Solaris cannot be restored under SunOS.

R98/R98+, SGI - on 6.5.1m/3m

-seisbr > Restore has a 4GB limit on space available during file system mapping operations.

-R98 Plus: seisbr > Restore does not come up with the correct available space for 18 GB disks when file system mapping needs to be performed. It displays  the following message:

Space available is less than space required! Please try again
seisbr displays space available as 4194303 kbs, which equals 4 GB
df -k reports space available as 13992478 kbyytes

Workarounds -Allocate more file systems for use from either local or NFS mounted disks. This is obviously painful in situations where you have a large project to restore, say,12 GB.

Note Def/Enh 49925 (IRIX64 specific)

If the "DISPLAY" was set ":0.0" or ":0.1", after issuing a "rsh" command the control never returns to the application.  seisbr hangs after deleting /tmp files, and ps/kill needs to be used to kill the application.  By inserting "hostname" explicitly to "DISPLAY" variable will solve the problem (done in R98+ startup script).

Three issues for a heads up (reported on call 141151), but not reproducible (R98+).

1 LDS_Solaris at the end will not work - seisbr won't come up - use LDS_Sol, despite what is written by owinstall.
2 device - must use /dev/rst (since it prefixes it with an n).
3 DLT devices give it a problem - error encountering short record .

Tape Device Configuration for the R98(+) Environment       (Contents)

PostStack Data Loader and SegyAnalyzer
In the R98 R98+ environment, tape device configuration has become a tricky issue for some clients.  This document should clear up some of the commonly asked questions about configuring tape devices for use with PostStack Data Loader and SEGY Analyzer.

Configuring tape devices is a job for the System Administrator.   This document is meant to give information on the files that are being looked at for each application.

The main difference in the tape drive configuration between PostStack and SEGY Analyzer is that PostStack references the device.txt file and SEGY Analyzer references the device.dat file.

SEGY Analyzer
The device.dat file can be located in your $OW_PMPATH directory for you own personal use, or the $OWHOME/conf directory for everyone to use.

If the device.dat file is not located in either of these directories, you may want to run the install script to set it up.  To run this script you can cd to $OWHOME/install and type OwInstallLDS.  You can also manually change the device.dat file by using a text editor to add or remove device names. 

The device.dat file should look similar to the following:
# logical:physical:type:capacity:attributes:machine:OS
DLT:/dev/rmt/0:LDS_8_MM:10000:LDS_RW:prowler:LDS_SOLARIS
8mm_1:/dev/rmt/1:LDS_8_MM:2000:LDS_RW:prowler:LDS_SOLARIS
8mm_aix:/dev/rmt/0:LDS_8_MM:2300:LDS_RW:xke:LDS_AIX
8mm_sun:/dev/rst/0:LDS_8_MM:5000:LDS_RW:nomad:LDS_SUNOS
8mm_sol:/dev/rmt/0:LDS_8_MM:2000:LDS_RW:troy:LDS_SOLARIS

The rmttape.dat file is used in conjunction with the device.dat when using a tape device from a remote machine. This file can be located in the host machine's $OWHOME/conf directory.

The rmttape.dat file points to the rmtspc.exe file on the remote machine.  The rmtspc.exe file should be located in the $OWHOME/GeoDataLoad/bin directory on the remote machine.

The rmttape.dat file should look similar to the following:

bentley:/big/sol_r98/GeoDataLoad/bin/rmtspc.exe
prowler:/big/sol_r98/GeoDataLoad/bin/rmtspc.exe
mirage:/mirage1/r98/GeoDataLoad/bin/rmtspc.exe
bugatti:/bugatti1/r98+/GeoDataLoad/bin/rmtspc.exe

NOTE : The fully qualified path to the rmtspc.exe file is required.

PostStack
The device.txt file can be located in your $HOME directory for your own personal use, or the $PSHOME/etc directory for everyone to use.

The device.txt file points to the fclient.exe on the local machine or the remote machine.  For in-depth instructions on installing the proper fclient.exe on the remote system, see the PostStack Family user Guide System Administration chapter.

To make changes to your device.txt file, you can use the configure option from The PostStack>Input Data> SEGY Parameters.  You can also use a text editor to open the device.txt file that you want to edit.

The device.txt file should look similar to the following:

tape1 /dev/rmt/1b scorpio simple 60 no scorpio:0.0 fclient.exe 60 no 0 0 0 0 4 scorpio /dev/lcmp0 scorpiob 1 0
tape2 /dev/rmt/1n scorpio simple 60 no scorpio:0.0 fclient.exe 60 no 0 0 0 0 4 scorpio /dev/lcmp0 scorpion 1 0
tape3 /dev/rmt/1bn scorpio simple 60 no scorpio:0.0 fclient.exe 60 no 0 0 0 0 4 scorpio /dev/lcmp0 scorpiobn 1 0

NOTE:  Be sure not to leave any lines or fields blank in the device.txt as this will crash the program.

Seismic Data Loading      (Contents)

SEGY Analyzer Common Issues

1. SEGY Analyzer is only reading the first file on my tape
   * Configure and select a tape device that includes the option 'b'
   Example: /dev/rmt/0b instead of /dev/rmt/0
2. Error opening file- Error Code 7
   * SEGY Analyzer is reading the  Format Code in the Binary Header Wrong
   * Change the Template from 'Defined in File' to actual Sample Format.
3. Where are my Templates stored?
   $HOME
   $SEISUTILSHOME/dat
   $OWHOME/SeisUtils/dat

PostStack Data Loader Common Issues

1. PDL crashes as soon as I select my 2d project
   * Run bldsms to create the .sm files before bringing up PostStack
2. How can I save my histogram and run log?
   * Save PostStack session before running job
   * cd to project directory  and look for directory named for your session name
   * cd into *.sess/flow1/
   * The job.output file will contain the run log from the most recent run.
   * Rename this file and move to the project directory so that it will be included with any project back up

Batch Control Monitor (bcm) Common Issues

1. TDEVICE environmental variable
   * Tape Open Error  ihstat = 2
   * setenv TDEVICE  /dev/rmt/? before running the bcm job
2. SEIS_DPATH environmental variable
   * syntax error in format: (1000) error in format
   * set SEIS_DPATH to your $OWHOME/SeisUtils/dat directory in the lgcenv.cf file
3. LGC_MASTER environmental variable
   * setenv LGC_MASTER <yourmaster> before running bcm2d
   * -or- use  bcm2d -m <masterproject> when running bcm2d

General Upgrade Procedures      (Contents)

This is a general workflow for SeisWorks upgrading procedures.   This workflow assumes that the corresponding OpenWorks project has already been successfully upgraded.  It also assumes that the SeisWorks project has been successfully restored onto the system and is currently in R97 format.

General

• Confirm that you have manage permissions for the corresponding OW project.
• Backup your R98 OpenWorks projects BEFORE upgrading any navigation. That way, if you have problems during your nav upgrade, you can restore the OW project and start over.
• Build/rebuild/update your plist.dat in R98 .  The plist.dat - format has changed slightly in R98, so it must be rebuilt either by hand or through Seismic Project Create. Blank and "no well" entries for well databases are unacceptable (old format), so you can't just copy the old plist.dat into the R98 environment, without editing it. Also, you may have new names for the R98 OpenWorks well database projects associated with your seismic projects. The old time/date stamp is incorrect for Y2K applications. 
• There is a utility to upgrade the plist.dat called updowplst in $OWHOME/SeisUtils/bin.
• Update the dir.dat to reflect any changes in the R98 environment.

3D Projects

• Copy all 3d project directories for a the project to be upgraded into R98 environment.
• In Seismic Project Manager, open Project > Navigation Upgrade.
  Select Upgrade > 3D Projects.  Select the appropriate project and click OK.   This will upgrade the navigation data and will store it in the OpenWorks database in R98.  Once a the message "3D Upgrade Complete" appears, close Navigation Upgrade.

2D Projects

• Clean up the 2d project in R97 before you upgrade. 
• Run Contest2d and Master Proj Checker, available on isite.
• Backup the 5 .sm files in each working project.  These files are modified during upgrade and the ownerships are changed to the login account that upgraded the project. You may need to change the ownerships and/or permissions, so that other users can access these files. Also, if you need to "go back," you would have to re-modify the project to rebuild them correctly in R97 environment, or restore an R97 version of them.
  projectname.ln.sm
  projectname.lt.sm
  projectname.sp.sm
  projectname.st.sm
  projectname.lh.sm
• Copy all 2d project directories (working and master) for a particular project into R98 environment.
• Run NavChek in R98 environment.
• In Seismic Project Manager, open Project > Navigation Upgrade.
• Select Upgrade > Master Project. 
• highlight lines to upgrade
• Hit associate with survey
• create a new survey, ok
• load 2d lines
• When master proj has upgraded successfully, upgrade the working project.
• Select Upgrade > Working Project.  When the working project has upgraded successfully, close Navigation Upgrade.
• It may be necessary to run bldsms utility if there are problems with the working project .sm files.

Concepts to Remember

• The seismic trace data (2v2_glb) remains unchanged and is still stored in the appropriate master project directories.
• The horizon interpretation (hzd_glb and hzh_glb) ) remains unchanged and is still stored in the appropriate master project directories.
• Seismic Navigation information for all 2d and 3d projects will now be stored in the OpenWorks database.
• When you are in Navigation Upgrade, you will be accessing only the CURRENT well database project.Therefore, remember to upgrade only the 2d lines (Master Project) for the 2d projects that will use the CURRENT well database project.
• While in Navigation Upgrade, you can see lines from several Master Projects, not all of which should go into the CURRENT well database project.
• While in Navigation Upgrade, you will only see 3d projects and 2d working projects, listed from the plist.dat, that are associated with the current well database. To see other projects, you will have to change the current well database project.
• If you have 2d working projects that access the same Master Project and 2d lines, but different well database projects, you will have to upgrade the same seismic navigation information into each well different database project.
• You must have upgraded your OpenWorks (well database) project(s) BEFORE upgrading your associated 2d or 3d projects, since all of the navigation information is stored in the well database projects.
• You must have built/rebuilt/upgraded your plist.dat file before upgrading any Seismic projects. This is because the upgrade software looks at your plist.dat, and lists any projects (2d and/or 3d) associated with the current R98 OpenWorks project.
• You must upgrade the project-specific 2d Seismic Lines (Navigation) in the Master Project BEFORE upgrading your 2d working project.
• 2d or 3d SURVEYS should be created BEFORE you can upgrade the 2d working or 3d projects. The upgrade program will prompt you to create the survey, if you have not done so before.

TIPS:

• Although the documentation states that you can/should delete the 3 seismic navigation files (st_glb, lh_glb. And xy_glb) from the 2d Master Projects, you may want to keep these files, since there are some utilities (MasterProjectChecker, for example) which use them.

NEW FILES and ENV VARIABLES IN R98:

• owdir.dat - An ascii file which contains the directory paths to the OW_SYS_DATA and OW_PROJ_DATA directories, which store certain OpenWorks, SeisWorks, and TDQ project files. It is typically defined when software is loaded, can be customized for individual users. By default, located in the $OWHOME/conf dir, the location can be overridden by setting the OW_PMPATH or OWDIR_LOC variables. 
• OW_SYS_DATA - only one OW_SYS_DATA dir per owdir.dat file, this directory stores:
• Well symbols and  Lithology patterns - in the owsymbols subdir - (.LIP, .SYM, and .PRI files)
• Data loading formats (initially just the default formats, others can subsequently be added): -
• in the owioformats subdir - .wdl, ASCII LOADER (well data loader) formats and .all, CURVE LOADER (ascii log loader) formats
• in the owsdlformats subdir - .sdl, SEISMIC (2d navigation) DATA LOADER files
• OW_PROJ_DATA - directory which stores:
• .zgf files  -  graphics files, which now replace .cdf files, and are accessed by SeisWorks. Note that Zmap+ does NOT access this directory by default when looking for .zgf files.
• tdq models. The TDQ models are stored in an OW-PROJECTNAME/I3DV subdirectory and are named I3DVn, with "n" being an incremental number. If you have renamed your OpenWorks well database project, you will have to find and rename the OW-PROJECTNAME directory to match your R98 well database name. You may also have to define the path to that subdir in your owdir.dat file, or move the subdirectories to a path ALREADY defined in the owdir.dat.
  EXAMPLE: /data66/pb/OW_PROJ_DATA/COLT_R98/I3DV/I3DV20

Upgrade Issues     (Contents)

Common Issues
1. Upgrading the .cdf files to .zgf files
    * Mapping Overlay Manager
    * Script for batch upgrade of ALL .cdf files to .zgf files
2. Upgraded 3d project , now I get project initialization error
    * Check permissions on the project files (especially project.pds)  Make sure they are at least 666 and are owned by an R98 user
    * 3. When Upgrading my 3d project it said "3D Project Upgrade Complete".   But, above that line it said 3d project failed to load.
    * Check permissions on the .pds file
4. I created a new 3d project, but it shows up as an available project to upgrade.
    * This is because the 3d survey name is different than the 3d project name
5. How do I re-upgrade a 2d line?
    * Delete the line in Seismic Data Manager and go back into Navigation Upgrade

Well Display Troubleshooting     (Contents)

If wells will display in Mapview but will not display in Seisview ....Troubleshooting Checklist and other information:

1) Seismic View > Wells > Select > Displays Wells > Displayed Wells List

• Does you well appear on the displayed side of the list?  If not, move it to the displayed side of the list and see if you can force it to display.

2) Seismic View > Wells > Parameters > Criterion Distance

• Make sure that your criterion distance is set to a reasonable number for your data.

3) SeisWorks Main Menu > Defaults > Project Datum

• Make sure that your Project Datum is defined.

4) Time/Depth Table associated with well?  Is the time/depth table active?

• Make sure that you have a Time Depth Table associated with the well and that it has been labeled as active.

5) Seismic View  > Wells > Select > Time/Depth Tables.   Do a view/adjust and verify:

• KB Value,
• Project Datum is defined
• T/D table datum elevation is defined
• What is maximum display time?
• Are the first time and depth values set to zero
• Make sure there are no recumbent values in the Time Depth Table.
• Is the last point in the Time Depth Table equal to the Total Depth?

6)  Is the time/depth table loaded in milliseconds & TVD?

7) Well Data Manager - Well Header - check elevation, total depth, and make sure elevtype - is KB in full caps

8) Is this a deviated well and if so is there a position log loaded?

• last point in position log = to total depth in well master  (MD)?
• first line     xoffset 0 yoffset 0 tvd 0
• no recumbent values in the log.  (i.e. log values steadily increasing.)

Note:  Reloading of Position logs
1) if position log loaded with curve loader it will calculate MD on the fly
2) if position log loaded in WDM it will NOT calculate MD on the fly, must load x, y, TVD & MD

9) If you are using a well list, try selecting <All Wells> to rule out well list corruption.

10)  Try exporting the time/depth table back out to QC the data

• OW > Export > Well Data Export

SeisWorks Datums      (Contents)

DEFINITION:  A datum is an elevation from which vertical depth or time measurements are referenced.  (e.g.  29m above sea level)

• Datums should be treated as part of the data.  Changing a datum is just like changing data values in the database.
• Datums are NOT intended for setting a preferred reference point for display annotation.

TYPES OF DATUMS:

  Depth datums

• Well Datum
• Universal datum - M.S.L

  Time datums 

• SeisWorks Project Datum
• OpenWorks Time Grid Datum
• TDQ Volume Time Datum

Time/depth datums  -  Time/depth Table Datum

• Normally you should SET DATUMS EQUAL TO THE SEISWORKS PROJECT DATUM.

Data types referencing DEPTH datums

•   Well Datum (well logs, well picks, well faults)
•   Sea Level (OpenWorks depth grids, StratWorks profiles and surfaces)
•   SeisWorks project datum (horizons, faults, trace data)
•   OpenWorks Time Grid Datum (OpenWorks grids)
•   TDQ volume Time Datum (TDQ volumes)

Data types referencing TIME/DEPTH Datums

• Time/Depth Table datum (checkshot surveys, time/depth tables, synthetics)
• The same datum applies to both time and depth values in checkshot surveys and time/depth tables.
• The first point is always assumed to be (0,0) relative to the datum.

Checkshot Survey vs. Time/Depth Table

•   Both are represented the same way in the database as Time/Depth pairs.  The only difference is a flag.
•   In general, checkshot surveys are loaded directly, while time/depth tables  are calculated.  

 TERMS sometimes associated with datums:

Replacement Velocity - velocity calculated from (0,0) to first pair in the time/depth table

Well Shift - a time value added to or subtracted from time values in the time/depth table

Datum correction - a calculated correction made by applications before combining data objects referencing different datums.  Depending on domain, this may involve a simple shift, or an extrapolation of the replacement velocity.

A LITTLE HISTORY

• OW curve loader (pre V4.1.3) -  checkshot datum defaulted to KB.  Usually not the case for time values
• SynTool (pre V3.0) - defaulted output Time/Depth table datum to KB
• SeisWorks (pre V3.4.2) - used a different method to calculate replacement velocity.  There were bugs in synthetic stretch/squeeze.

REFERENCE:  UserNet, June 1998     

RULES OF THUMB:

1. Remember that checkshot surveys and Time/Depth table have a single datum for times and depth, and start at (0,0).
2. Set all elective time datums equal to the SeisWorks Project Datum.
3. In SeisWorks Merge, set datums of all projects to same value.
4. Try to set SeisWorks Project Datum above all important data points.
5. Don't change a datum in order to change the display annotation reference.    It won't work!
6. Don't change a datum to accommodate data misties or busts.   It may work, but you'll regret it!
7. Don't ignore them.  Sooner or later you'll wish you hadn't.

REMEMBER:  SeisWorks project datums are NOT part of the OpenWorks project.

Faultmanager      (Contents)

* Program: faultmanager version 1.1 
* Purpose: To provide easy access to fault management for OpenWorks 4.X and 5.X oracle databases
* * Syntax: Execute this program from an xterm:         

Intoduction

ALWAYS PERFORM A DATABASE BACKUP PRIOR TO USE IN ORDER TO INSURE A SAFE RECOVERY SHOULD A PROBLEM OR UNEXPECTED RESULT OCCUR.

• You must have MANAGER authority to use any of the delete or update options provide.  Those with INTERPRET or BROWSE database  privileges may only do options 1 - 9 and CK which do queries, only.
• Not entering information at any prompt is like cancelling the option.
• Options specified by uppercase characters (ex. DID) can be entered using either all uppercase  or all lowercase characters.
• All listings generated by the scripts in faultmanager are automatically written to the faultmanager.log file in your current directory. Use the command "tail -f faultmanager.log" in a separate window so you can scroll back through previous queries as necessary.
• This script should not be modified in any way.  If a related operation is required, such request should be made directly to Landmark Graphics Corporation.
• This program is for use with OpenWorks 4.X or 5.X projects, only.
• If you have additional SQL scripts that could be of value to others, please send them to barb@lgc.com for examination and possible inclusion in the next revision.

Summary of Command Menu:

STARTUP

1. List/Select Projects:
Lists OpenWorks projects for which the current  user has provileges and allows you to select the project to work with. 

2. Project Fault summary:
Provides a count for fault related items in the database and a summary of Fault Segment Ownership. These counts can give an idea of expected performance and management issues   associated with this project.   An example follows:

  Interpretation Type                                                  Number
  ------------------------------------------                             ----------
  Faults                                                                      18
  StratWorks Profiles (CrossSection)                   3
  StratWorks Polygons (MapView)                        0
  StratWorks Centre Line Sets (MapView)           0
  SeisWorks Fault Planes                                       18
  SeisWorks Fault Segments                                 80
  SeisWorks Assigned Segments                        58
  SeisWorks Unassigned Segments                    22
  SeisWorks Duplicated Segments                      0
  SeisWorks Fault Heaves                                      0

  Summary of Fault Segment Ownership for COLT:

                                         Segments
  SeisWorks Project        Interpreter       Owned
  ------------------------ ----------- -----------
  colt                   LGC                  30
                           ROC                  43
                                       ----------
    &nbssp;                                          73

QUERIES

3. Fault id's:
provides a list of Fault Name, Fault ID, and Interpreter.

4. Spread of fault data:
asks for a range of Fault ID's then gives you a count of items in each fault related table.   Example: for Fault ID's from 4 through 5:
   #vid in geom_polyline_vec                          9
   #geom_polyline_id in geom_polyline                 9
   #fault_segment_id in fault_heave                   0
   #fault_segment_id in fault_segment                 9
   #fault_plane_id in flt_seg_assignment              9
   #vid in fault_control_pointset_vec                 0
   ...and lots more...

5. Duplicated fault segments:
gives a count of duplicate fault segments.
Note: If you get a count of 265 duplicate segments, this means that you have 265 segments that have AT LEAST ONE duplicate segment. This query makes no differentiation between assigned and unassigned segments or whether the duplicated segments are assigned to different faults. In Release v1.1 more information concerning duplicate fault segments is given.  The information includes the number of duplicate fault segments, the Min and Max X and Y coordinates of the fault segment, the Min and Max Z value of the fault segment, the fault id, the fault name, and the fault segment id:

Number of duplicated fault segments in COLTOW_41:  29
Duplicate Segments with 9 points and extents of:
   Min X:       2188.77  Min Y:       12369.11  Min Z:     584
   Max X:      14481.53  Max Y:       12369.11  Max Z:    3996

   Fault ID Fault Name                       Segment ID
----------- ------------------------------ -----------
    &nbbsp;     2 main hb                                 182
         42 main1hb                                1115

6. Fault Plane query:
provides a list for ALL fault planes that displays Fault ID, Plane ID, Interpreter, Fault Name, Fault Type, Segment Count, Status of Geometry, Vertex Count, Triangle Count, Control Point Count.

7. Fault Segment query:
provides a list for ALL fault segments that displays SeisWorks Project, Source 3D Survey or 2D Line, Segment ID, Interpreted On, Number of Points, Assigned??, Segment Domain, Interpreter.

8. Fault Heave query:
      Horizon Name          Segment Id Inter                          Coordinates
-------------------------- ---------- ----- ----------------------------------------------------
aa_min_green_interpolated         104 BAB    Downthrown x, y, z:  622192.94, 5763043.00, 1844.00
                                            Upthrown    x, y, z:  622097.38, 5763253.50, 1730.29
                                  105 BAB   Downthrown x, y, z:  624628.31, 5759847.50, 1550.14
                                            Upthrown    x, y, z:  624508.69, 5759955.50, 1428.81
                                  106 BAB   Downthrown x, y, z:  623907.94, 5759378.50, 1808.80
                                            Upthrown    x, y, z:  623870.56, 5759461.00, 1707.38
cc_min_pink_Zap                    129 BAB   Downthrown x, y, z:  622741.94, 5761887.00, 1833.42
                                            Upthrown    x, y, z:  622741.75, 5761887.50, 1833.42

9. SeisWorks fault ownerships:
provides the following list for ALL fault planes:    Fault
Fault ID  Owner Fault Name               Assignment Status
--------- ----- ----------- ---------------------------------------------------
        1       bigblue      Plane 1 (owned by ROC) has 12 segments assigned that are OWNED by ROC
        4 ROC   purple       Plane 4 (owned by ROC) has 8 segments assigned that are OWNED by ROC
        4 ROC   purple       Plane 4 (owned by ROC) has 1 segments assigned that are OWNED by LGC)
       15 LGC   apurple      Plane 15 (owned by LGC) has 2 segments assigned that are OWNED by LGC

DELETIONS

DID    Faults by fault_id: asks if you want to see the fault id list first, then prompts for an inclusive range of id's to be deleted.
DUS  Unassigned segments: Deletes ALL unassigned segments.
DFS   Delete Faults by segment: Will delete the fault segment one at a time by fault segment id and if the segment affected is assigned to a fault it will flag the triangulation of that fault as out of date.
DSW  All SeisWorks fault data: Deletes ALL SeisWorks fault data. If other dependent data exist, fault_names will NOT be deleted.
DST  All StratWorks fault data: Deletes ALL StratWorks fault data.  If other dependent data exist, fault_names will NOT be deleted.
DA!  All OpenWorks project fault data: Deletes ALL fault data from the OpenWorks project.

DUPLICATE SEGMENTS
*************************
Duplicate segment deletion makes no differentiation between assigned and unassigned segments or whether the duplicated segments are assigned to different faults.
*************************
DDL  Delete latest: Makes a single pass through the database and  deletes the latest (last loaded) duplicate of a segment.      Other duplicates may still exist.
DDE  Delete earliest: Makes a single pass through the database and deletes the earliest (first loaded) duplicate of a segment.      Other duplicates may still exist.
DAL  Delete All latest duplicates: Makes multiple passes through the database and deletes the latest duplicate segment until there are no duplicate segments left.
DAE  Delete All earliest duplicates: Makes multiple passes through the database and deletes the earliest duplicate segment until there are no duplicate segments left.

UPDATES

FN     Rename a fault
OID    Fault ownership by fault_id: Provides the ability to change the interpreter for the plane, heaves, and segments associated with specified a fault_id or range of ids. 
OFN  Fault ownership by fault_name: Provides the ability to change the interpreter for the plane, heaves, and segments associated with specified fault_name.  
UN     Unassign all segments of a fault: specified by fault_id. 
SWP  Change SeisWorks survey for segments: Provides the abililty to change the SeisWorks survey name from project_one to project_two  for all segments assigned to project_one.

SANITY-CHECK

CK   SeisWorks fault data check: lists dangling references for faults, fault planes, and fault segments, and will also check for duplicate fault segments, and fault segments with >64 points.
DR   SeisWorks fault data clean-up: removes dangling references. 

*******************************************************************************
***On large fault databases, DR takes a long time and consumes 100% of CPU. We suggest that you run this overnight.***
********************************************************************************
DT   Delete Tuning Statistics: Results of "Project Tuning" may degrade performance. This script will delete the statistical information  from the fault vector tables.

0    EXIT

Fault Manager Menu

F A U L T   M A N A G E R   v 1.1
=======================================
Current OpenWorks Server: owprowler733
Current OpenWorks Project: not_defined
User's Project Privileges: not_defined

      STARTUP                           List/Select Projects  1
      -------                                Project Fault summary  2

      QUERIES                                                 Fault id's  3
      -------                                      Spread of fault data  4
                                          Duplicated fault segments  5
                                                          Fault Plane query  6
                                                   Fault Segment query  7
                                                        Fault Heave query  8
                                      SeisWorks fault ownerships  9

      DELETIONS                            Faults by fault_id  DID
      ---------                             Unassigned segments  DUS
                                Segments by fault_segment_id  DFS
                                          All SeisWorks fault data  DSW
                                           All StratWorks fault data  DST
                               All OpenWorks project fault data  DA!

      DUPLICATE SEGMENTS            Delete latest  DDL
      ------------------                              Delete earliest  DDE
                                     Delete All latest duplicates  DAL
                                  Delete All earliest duplicates  DAE

      UPDATES                                 Rename a fault  FN
      -------                        Fault ownership by fault_id  OID
                                Fault ownership by fault_name  OFN
                              Unassign all segments of a fault  UN
                        Change SeisWorks survey for seg.s SWP

      SANITY-CHECK      SeisWorks fault data check  CK
      ------------                 SeisWorks fault data clean-up  DR
                                                 Delete Tuning Statistics  DT

      EXIT ...................................................................................0

2D Continuity Test (Contest2d)     (Contents)

Introduction: contest2d is a SeisWorks 2D utility which performs sanity checking on several files in a 2d Master project (does not look at the working project).  The files include the line headers, horizon data files, and the seismic (2v2) files in the master project.  It is a nice "hands off" utility which runs and generates an error file.  It can take some time to run on large 2d master projects, so starting it during lunch or at the end of the day may be advised.  The error messages are diagnostic, but cryptic, and are explained below.

Error Messages from the contest2d program:

"error from inglct ier = x"
Explanation: There was a problem initializing the Master Project. Error code ier = 1 indicates an environment variable problem, check the value for LGC_MASTER.

"error from setprj ier = x "
Explanation: There was an error with the project or the project name.  Check that the LGC_MASTER env variable was set properly, and that the filesystems where the master project exists are properly specified in the dir.dat (or OW_DDF) file.

"error from locdef ier = x "
Explanation: No line headers (linename_.lh_glb) could be found in the master project.

Error Messages within the Error File:

"trace min = ZERO DANGER linename"
Explanation:  The minimum trace value in the line header was zero which is not allowed in SeisWorks 2D.  Note: 2D Seismic Basemaps will not show a zero for minimum trace number.  Instead use glincat -m mast_proj to display the minimum trace from the line header.  2D Seismic basemaps CAN be used to edit the line header to a number other than zero (just type over and say OK).  Remember that you will have to change to max value also to reflect the total number of traces loaded (if you change 0 to 1 for the min, add 1 to the max trace value as well).

"trace min is greater than trace max linename"
Explanation: The minimum trace number was greater than the max trace number in the line header (linename___.lh_glb) file.

"WARNING trace min equals trace max linename"
Explanation: The minimum trace number was equal to the max trace number in the line header (linename___.lh_glb) file.              

"error on opening linename___.lh_glb"
Explanation: There was a problem opening the line header file.  This could indicate a corrupted line header.

"error on opening linename___.xy_glb"
Explanation: check for missing linename___.xy_glb file or permissions problems.

"error on opening linename___.st_glb"
Explanation: check for missing linename___.st_glb file or permissions problems.

"error on opening read/write linename__horizonname__.hzd"
Explanation: the horizon data file did not exist, could not be found, or has a file permission problem. 

"hzd internal size mismatch with line header linename___.lh_glb"
"hzd mintrc = xxxx maxtrc = xxxx"
Explanation: the min and max trace values in the hzd file do not match the min and max trace values in the line header (lh_glb) file This is usually caused when a line is reloaded.   An incorrect byte count will cause horizon corruption.

"file size error linename___horizonname___.hzd_glb"
"file size should be xxxx based on line header"
"file size is xxxx"
Explanation: the size of the hzd file in bytes should be =
((#traces from line header x 4 ) + 64)   This mismatch is usually caused when a line is reloaded.   An incorrect byte count will cause horizon corruption.

"error from locnxt ier = x"
Explanation: One of the Seismic file extents for the 2v2_glb files could not be found.   ier = 3 file not found.  Check dir.dat (or OW_DDF) for incorrect filesystems.

"error on opening read/write name0x.2v2_glb"
Explanation: Seismic file could not be opened.  Possible permission problem.

"dm3dop error = x   ,  name0x.2v2_glb"
Explanation: Seismic file could not be opened properly, error codes are:

                           1 = DSXRD/DSXWRT error on FCREC or trace index area
                           2 = File not a valid 3D seismic data file
                           3 = The max disc space requirement for the file being created exceeds the amount
                               of space currently available (MODE +2)
                           4 = Minimum X,Y, or Time coordinate must exceed -32767
     &nnbsp;                     5 = MODE argument must be 1,-1,2,-2, or 3
                           6 = File opened in input or output(prep) mode does not exist
                           7 = File opened in input mode exists but contains no data
                           8 = Invalid file name specification
                           9 = File opened in output mode exists but contains no data; file must be deleted
                          10 = Call to DSXBLK failed
                          11 = Permission denied on an existing file
                          12 = Failed to lock a file for write
                          13 = Not a DST version 2 or 3 file
                          14 = Attempt to write trace longer than 32767 bytes
                          -1 = Same as IERR=3 (see MODE argument)
                   (100+IER) = DSXOPN error codes  0 through 27. Definitions (with 100 prefix)

                               100 = normal return
                               101 = file did not exist and was created
                               102 = file did not exist and could not be created
                               103 = first extent did not exist; MODE='read'
                               104 = all logical units are allocated
                               105 = invalid file specification
                               106 = create access denied
                               107 = invalid mode
                               108 = file existed and MODE='create'
                               113 = no space available; MODE=8
                               114 = no extents available
                               116 = expected extent did not exist
                               117 = structure error
                               118 = invalid mode (from                               
                               119 = duplicate extent found
                               120 = no space available on SYSDR; MODE=9
                               121 = one or more extents existed beyond range 1...NXT.
                               122 = DST version is not IVCUR (from DSXADX)
                               123 = extent 1 is write protected (from DSXADX)
                               124 = last extent is write protected (from DSXADX)
                               125 = open permission denied on file
                               126 = file could not be locked (not opened)
                               127 = invalid version number (.NOT. 2 or 3)

                   (200+IER) = DSXRD read error on the file control record.

Continuity Test for R98 and R98+

Download the new version of 2d continuity test (contest2d in R98/R98+) from isite.  The new executable of 2d continuity test is on isite in the following directory location:/landmark/products/SeisUtils/R98/contest2d

This version of 2d continuity test(contest2d for R98) fixes the following problem, see defect# 68966:
Running 2d continuity test (original which came with CD) yields erroneous results regarding file size mismatches, not consistent or true results...replace with this new executable.  This is a Fix for miscalculations during integrity checking using 2d continuity test.

more README_contest2d
This directory contains versions of "contest2d".
contest2d checks the validity of seismic trace files, and horizon files compared to the number of traces on the matching seismic lines. These trace numbers are read from the seismic navigation data stored in the OpenWorks data base. This utility replaces the R98 version found in $SEISUTILSHOME/bin

Copy the appropriate contest2d image (sgi, ibm, sol) to your $SEISUTILSHOME/bin directory, and unompress the file using the command   "uncompress contest2d_???.Z" Change the file name to "contest2d", add execute permissions to the file  with the command "chmod +x contest2d"

To use, you must first set the environmental variable LGC_MASTER to the  appropriate master, or global area as defined in your plist.dat file. Typing "contest2d" with a return will show the proper syntax of this command line
executable.

2D Horizon Management      (Contents)

How To Handle Changes To X Y Information On A 2D Line

SUMMARY

2D Lines are often loaded with the wrong xy information.   Because 2d horizon data is sensitive to any changes, corruption can occur if this situation is not handled properly.  What is the proper workflow to use in order to preserve all horizon interpretation on a line when x and y information is changed?

WORKFLOW

1.  Backup your master project using seisbr.   A backup of the master project is necessary because when navigation data is changed for a line, it  will impact ALL horizons on that line whether or not they currently reside in a working project. 

2.  From a unix xterm, list all horizons which are connected to the line to be changed.   This can be done using the command ls -al /p*/lgc_master/G89A-1027*.hzd_glb , where p* represents a string that will catch all of the directories specified in your dir.dat, lgc_master represents your master project directory, and G89A-1027 represents the line that will be modified.

3.  Using SeisWorks > Map View > Horizons > Global Manager > Project Horizon Add, add all of these horizons to your working project.   This step is necessary because we cannot export horizons unless they are in a working project.

4.  Using Horizon Import/Export (Hie) export these horizons in line - trace format.**     Hie will export only 8 horizons at a time.  To do this, use a format file similar to the following:

LINEID  1    4  2
                    SHOTPT 5   11  2
TRACE 12  17  2
Z1       19  25  2
Z2        27  33  2
Z3        35  41  2
Z4        43  49  2
Z5        51  57  2
Z6        59  64  2
Z7        66  72  2
Z8        74  80  2

- Make a note of the horizons included in each ascii file.
- You can use the mltexp2d utility to export more than 8 horizons at a time. ***

5.  Check your ascii files to ensure that the horizon data exported correctly.

6.  Move all of the .hzd_glb files for the horizons which will be effected out of the master directory and into a temporary directory.

7.  Using OW > Data > Export > Seismic Data Export, export the navigation data for the line that youwill be changing.   Use the export_all format to export necessary information.   Check the ascii file to ensure that the navigation data has been exported correctly.

8.  In Seismic Data Manager, make the proper changes to your x and y values.  Save your changes.

9.  Using 2d Project Modify, save the new line to the 2d working project.

10. Import your horizon ascii files back into the working project using Hie. Use the same format that you used to export the horizons.  Use mltimp2d to import the horizons if you used mltexp2d to export the horizons.***

11. In SeisWorks, check that the horizons imported correctly. 

12. Using SeisWorks > Map View > Horizons > Global Manager > Project Horizon Remove to remove any horizons that you do not wish to include in   your working project.

**DO NOT MAKE CHANGES TO THE MIN/MAX TRACE AND THE XY AT THE SAME TIME.  THIS REQUIRES A DIFFERENT WORKFLOW, WHICH IS DOCUMENTED BELOW.

How To Handle Changes To The Minimum Or Maximum Trace Value Of A 2D Line

SUMMARY

2D Lines are often extended when additional data is acquired.   Because horizon data is directly linked
to the trace numbers, corruption can occur if this situation is not handled properly.   What is the proper
workflow to use in order to preserve all horizon interpretation on a line when the minimum or maximum
trace number is changed?

WORKFLOW

1.  Backup your master project using seisbr.   A backup of the master project is necessary because when navigation data is changed for a line, it  will impact ALL horizons on that line whether or not they currently reside in a working project. 

2.  From a unix xterm, list all horizons which are connected to the line to be changed.   This can be done using the command ls -al /p*/lgc_master/G89A-1027*.hzd_glb , where p* represents a string that will catch all of the directories specified in your dir.dat, lgc_master represents your master project directory, and G89A-1027 represents the line that will be modified.

3.  Using SeisWorks > Map View > Horizons > Global Manager > Project Horizon Add, add all of these horizons to your working project. This step is necessary because we cannot export horizons unless they are in a working project.

4.  Using Horizon Import/Export (Hie) export these horizons in x, y, z format.**    Hie will export only 8 horizons at a time.  To do this, use a format file similar to the following:  Make a note of the horizons included in each ascii file.   You can use the mltexp2d utility to export more than 8 horizons at a time.***

                LINEID   1   4  2
X       5  12  2
Y      13  18  2
Z1     19  25  2
Z2     27  33  2
Z3     35  41  2
Z4     43  49  2
Z5     51  57  2
Z6    59  64  2
Z7     66  72  2
Z8     74  80  2

5.  Check your ascii files to ensure that the horizon data exported correctly.

6.  Move all of the .hzd_glb files for the horizons which will be effected out of the master directory and into a temporary directory.

7.  Using OW > Data > Export > Seismic Data Export, export the navigation data for the line that youwill be changing. Use the export_all format to export necessary information.   Check the ascii file to ensure that the navigation data has been exported correctly.

8.  In Seismic Data Manager, make the proper changes to your minimum or maximum trace.  Save your changes.

9.  Using 2d Project Modify, save the new line (with the trace changes) to the 2d working project.

10. Import your horizon ascii files back into the working project using Hie.  Use the same format that you used to export the horizons.  Use mltimp2d to import the horizons if you used mltexp2d to export  the horizons.***

11. In SeisWorks, check that the horizons imported correctly.  You may need to change the XY Tolerance for Import in Hie if the horizons were not completely restored.

12. Using SeisWorks > Map View > Horizons > Global Manager > Project Horizon Remove to remove any horizons that you do not wish to include in   your working project. 

How To Handle Changes To The Minimum Or Maximum Trace Value And X Y Information At The Same Time

SUMMARY

2D Lines are often extended when additional data is acquired.   They may also have incorrect x y information loaded.  Because horizon data is directly linked to the trace numbers, corruption can occur if this situation is not handled properly.  What is the proper workflow to use in order to preserve all horizon interpretation on a line when the minimum or maximum trace number and the xy information needs to be changed?

ADDITIONAL INFORMATION

This task cannot be done with one simple workflow.  Because we are changing two major components of the 2d navigation data, the workflow is a bit intense.  Basically, you cannot make these two major changes in one attempt and also preserve all of the horizon data. 

To correctly achieve this feat, you must go through both the minimum-maximum trace workflow AND the x y workflow separately.

WORKFLOW

1. Go through the ' HOW TO HANDLE CHANGES TO X Y INFORMATION ON A 2D LINE' workflow above.

2. Go through the ' HOW TO HANDLE CHANGES TO THE MINIMUM OR MAXIMUM TRACE VALUES ON A 2D LINE' workflow. (InfoDoc 4694)

***NOTE: mltexp2d and mltimp2d are utilities that will import/export more than 8 horizons at a time.  These utilities can be found on the Landmark FTP Site in the /landmark/products/SeisUtils/mltihrz.

Troubleshooting ZAP!     (Contents)

1. Check ownership and permissions on horizons (*.hzd), project directories, and the *.pds file.

2. Exit SeisWorks and rebuild the horizon index file.
* delete the *hrz_cat file
* open HrzUtil scan for NaN
* rebuild horizon index file

3. Check for duplicate horizons.
* check in the *.err file
* check the project directories for duplicate zz####.hzd files (3D)

4. Evaluate the amount of used disk space.
* Type the following in an x-term:  df  -k
* We recommend not exceeding 94% use.

5. Open the dir.dat file to make sure that all directories are specified as "global" and that one directory is specified as the "sys" directory.

6. Confirm that the cube volume (*.cd) being used does not exceed 80% of the available swap space.
* to check swap space, use the following command:  swap  -s

7. Try a new SeisWorks session.  Many time the Zap process gets hung.  Opening a new session will reinitialize Zap.

8. Verify that 8-bit data is being used.  Zap can only handle 8-bit data.

9. Check for horizon files (*.hzd) with a file size of zero.
* if found, delete the horizon with a file size of zero
* rebuild the horizon index file ( see #2 above)

10.  If user can access Zap but can't intialize cube volume, check the s3d.err file for an error message that says: No Zap license available. 
* Someone must exit Zap before another user can access the license.

11.  If using a zone control map with exclusive zones, confirm that all the seed points DO NOT reside within the zones of exclusivity.

12. If Zap fails with the following message, remove excess semaphores:
* err msg:  No space left on device.  gpdAPI::Cannot sync init.  Failed to initialize gpd.
* reboot to remove excess semaphores.

Appendix A - Project Files     (Contents)

Zap!, Batch Zap!, & SeisCube Files

Seismic Cube Data

Seismic Cube Session Files

Display Data

ZAP! Data

Batch ZAP Data

Merged Project Files Written to Base Project Directory

Faults

Horizon Data

Interpretation Map Data

Project Control Files

Display - Color Files

Display - Panel Files

Merge Session Files

Data Import/Export

Plotting & Pictures

Obsolete Files You Can Delete After Successfully Upgrading to SeisWorks 1998

Obsolete Color File

Obsolete Culture Data Files

Obsolete Fault Data Files

Obsolete Well Data Files (created by utility "disoda")

Obsolete SurfCube Session Files

Obsolete Display Data Files

Scratch Files You Can Delete Between Sessions

User-created Files You Can Delete
Landmark recommends that you back up your seismic project to tape (using Backup/Restore) before you delete any of these files.

2D and 3D Project Files

Seismic Data

Faults

Horizon Data

Interpretation Map Data

  Project Control Files

2D Mistie Data

Seismic Balance Data

Display - Animation Files

Display - Color Files

Display - Panel Files

Session Files

Data Loading

Data Import/Export

FastTrack

2D Seismic Map Files

StratAmp Files

Plotting & Pictures

Miscellaneous Files

2D Master Project Files: Sorted by Type of 2D Data

Seismic Data

Horizon Data

FTP Password

Have a Nice Day and Enjoy you Life