PM-SS SPA v2

SeisSpace
Seismic Processing
and Analysis
Training Manual
Volume 2
copyright © 2010 by Landmark Graphics Corporation
Part No. 162383 D April 2010

© 2010 Halliburton
All Rights Reserved
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by
Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system,
or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or
disclosed to third parties without the express written permission of:
Halliburton | Landmark Software & Services

2107 CityWest Blvd, Building 2, Houston, Texas 77042-3051, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone:713-839-2000
FAX: 713-839-2015
Internet: www.halliburton.com/landmark
Trademark Notice
3D Drill View, 3D Drill View KM, 3D Surveillance, 3DFS, 3DView, Active Field Surveillance, Active Reservoir Surveillance, Adaptive Mesh
Refining, ADC, Advanced Data Transfer, Analysis Model Layering, ARIES, ARIES DecisionSuite, Asset Data Mining, Asset Decision Solutions,
Asset Development Center, Asset Development Centre, Asset Journal, Asset Performance, AssetConnect, AssetConnect Enterprise, AssetConnect
Enterprise Express, AssetConnect Expert, AssetDirector, AssetJournal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer,
AssetObserver, AssetObserver Advisor, AssetOptimizer, AssetPlanner, AssetPredictor, AssetSolver, AssetSolver Online, AssetView, AssetView
2D, AssetView 3D, BLITZPAK, CasingLife, CasingSeat, CDS Connect, Channel Trim, COMPASS, Contract Generation, Corporate Data Archiver,
Corporate Data Store, Crimson, Data Analyzer, DataManager, DataStar, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 3D
Drill View, DecisionSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace
Atomic Meshing, DecisionSpace Nexus, DecisionSpace Reservoir, DecisionSuite, Deeper Knowledge. Broader Understanding., Depth Team, Depth
Team Explorer, Depth Team Express, Depth Team Extreme, Depth Team Interpreter, DepthTeam, DepthTeam Explorer, DepthTeam Express,
DepthTeam Extreme, DepthTeam Interpreter, Design, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery
3D, Discovery Asset, Discovery Framebuilder, Discovery PowerStation, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth-
Model, Drillworks, Drillworks ConnectML, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDM
AutoSync, EDT, eLandmark, Engineer's Data Model, Engineer's Desktop, Engineer's Link, ESP, Event Similarity Prediction, ezFault, ezModel,
ezSurface, ezTracker, ezTracker2D, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, FZAP!, GeoAtlas, GeoDataLoad,
GeoGraphix, GeoGraphix Exploration System, GeoLink, Geometric Kernel, GeoProbe, GeoProbe GF DataServer, GeoSmith, GES, GES97,
GESXplorer, GMAplus, GMI Imager, Grid3D, GRIDGENR, H. Clean, Handheld Field Operator, HHFO, High Science Simplified, Horizon
Generation, I2 Enterprise, iDIMS, Infrastructure, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as a service), Landmark (as software),
Landmark Decision Center, Landmark Logo and Design, Landscape, Large Model, Lattix, LeaseMap, LogEdit, LogM, LogPrep, Magic Earth, Make
Great Decisions, MathPack, MDS Connect, MicroTopology, MIMIC, MIMIC+, Model Builder, NETool, Nexus (as a service), Nexus (as software),
Nexus View, Object MP, OpenBooks, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWire Client, OpenWire Server,
OpenWorks, OpenWorks Development Kit, OpenWorks Production, OpenWorks Well File, PAL, Parallel-VIP, Parametric Modeling, PetroBank,
PetroBank Explorer, PetroBank Master Data Store, PetroStor, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView,
Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, Power Interpretation, PowerCalculator, PowerExplorer,
PowerExplorer Connect, PowerGrid, PowerHub, PowerModel, PowerView, PrecisionTarget, Presgraf, PressWorks, PRIZM, Production, Production
Asset Manager, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D, ProMax 3D,
ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+, QUICKDIF,
Quickwell, Quickwell+, Quiklog, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset
Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-
time View, Reference Data Manager, Reservoir, Reservoir Framework Builder, RESev, ResMap, RTOC, SCAN, SeisCube, SeisMap, SeisModel,
SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks
PowerSection, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert,
SimDataStudio, SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, SmartFlow, smartSECTION, Spatializer, SpecDecomp, StrataAmp,
StrataMap, StrataModel, StrataSim, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SynTool,
System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team
Workspace, TERAS, T-Grid, The Engineer's DeskTop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, TracPlanner
Xpress, Trend Form Gridding, Trimmed Grid, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL,
VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Well Cost, Well H. Clean, Well Seismic Fusion,
Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellSolver, WellXchange, WOW, Xsection, You're in Control.
Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks, or service marks of Halliburton.
All other trademarks, service marks and product or service names are the trademarks or names of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by
Halliburton. Halliburton assumes no responsibility for any error that may appear in this manual. Some states or jurisdictions do not
allow disclaimer of expressed or implied warranties in certain transactions; therefore, this statement may not apply to you
Contents
ProMAX User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
ProMAX Menu Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Building a Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Flow Building and Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Build a Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Sort data by source number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Sort data by source and channel number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Sort data by CDP number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Display near offset section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Additional Geometry Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Geometry Core Path Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

How to Decide on the Primary Geometry Path . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Transferring the Database to Trace Headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Details of the Geometry Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Steps Performed by Inline Geom Header Load. . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Valid Trace Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Valid Trace Number Origin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Steps Performed By Extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Between Extraction and Geom Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Geometry Load Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Pre Geometry Database Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Pre Geometry Initialization flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Complete the Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Landmark SeisSpace Seismic Processing and Analysis i

Contents
Inline Geometry Header Load after Pre Initialization . . . . . . . . . . . . . . . . . . 2-13

Load Geometry to Trace Headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
ProMAX Marine 3D Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3D Marine Geometry from UKOOA Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Using the Marine 3D Geometry Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Determine Primary Azimuth for Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Cable Feather QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
CDP Binning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
QC the Calculated Grid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Interactive Grid QC and Alteration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Load Final Grid and Perform CDP Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Critical Parameters During CDP Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Receiver Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
QC the CDP Binned Data using a Fold Plot. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Finalize the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Assigning CDP Flex Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Inline and Crossline Overlap Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Inline and Crossline distance Weighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Azimuth Weighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Prime Line Weighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
QC Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Produce QC plots from the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
CDP Contribution and Null QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Expand Flex Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3D Land Swath Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
3D Land Swath Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Prepare the Line and run the Spreadsheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
ii SeisSpace Seismic Processing and Analysis Landmark

Contents
Receivers Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Sources Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Patterns Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Complete the Sources Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Trace Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Spread QC after Trace Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Automatic Bin Calculation and QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
QC the Calculated Grid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Complete CDP Binning using the Batch CDP Binning Tool . . . . . . . . . . . . . . 4-22
Archival Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
SEG-Y Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Tape Data Ouput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Archive Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
De-multiple Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Topics covered in this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Interactive Radon Analysis and Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Input Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Processing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Generate a synthetic CDP gather . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Run Interactive Radon/Tau-P Analysis on synthetic CDP gather . . . . . . . . . . . 6-6
Run Radon Filter on synthetic CDP gather. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Display "real" marine CDP gathers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Run Radon Analysis on marine CDP gathers . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Run Radon Filter on marine CDP gathers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
OPTIONAL: Test parabolic vs. hyperbolic transform . . . . . . . . . . . . . . . . . . . 6-20
Radon Velocity Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Generate a synthetic CDP gather and analyze moveout . . . . . . . . . . . . . . . . . . 6-21
Landmark SeisSpace Seismic Processing and Analysis iii

Contents
Interactive FK Analysis and Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24

Input Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
Run Interactive FK Analysis on synthetic CDP gather . . . . . . . . . . . . . . . . . . 6-26
Run FK Filter on synthetic CDP gather . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Plotting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Creating, Viewing, and Plotting a CGM+ File . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Creating a CGM+ Plotfile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Viewing and Plotting CGM+ plotfiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Using Unisec to create plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Create a UNISEC CGM+ Plot file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Plotting CGM+ plotfiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
First Break Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Interactive NN First Break Training/Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Interactive Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Batch Neural Network First Break Picking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Pick First Breaks for entire survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
First Break Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Coordinate-based Refraction Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Coordinate-based Refraction Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Apply Refraction Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Apply Refraction Statics to your data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
iv SeisSpace Seismic Processing and Analysis Landmark

Chapter 1
ProMAX User Interface
This chapter will get you started processing with ProMAX. You will learn how to set up a work
space with the ProMAX User Interface, and then build and execute data processing flows.
Topics covered in this chapter:
o ProMAX Menu Map

o Getting Started
o Building a Workspace
o Flow Building and Execution
o Data Sorting
Landmark ProMAX Seismic Processing and Analysis 1-1

Chapter 1: ProMAX User Interface
ProMAX Menu Map
1-2 ProMAX Seismic Processing and Analysis Landmark

Getting Started
ProMAX is built upon a three level organizational model referred to as

Area/Line/Flow. When entering ProMAX for the first time, you will
build your own Area/Line/Flow workspace. As you add your own Area,
you may want to name it with reference to a geographic area that
indicates where the data were collected, such as “Onshore Texas”, or use
your name, such as “daves area”. Line is a subdirectory of Area which
contains a list of 2D lines from an area, or the name of a 3D survey.
After choosing a line from the Line menu or adding a new line, the Flow
window will appear. Name your flows according to the processing
taking place, such as “brute stack”. For this course, we will also use a
number, for example "01: Display shots".
Look at the Menu Map figure on the previous page. This figure refers to
the menus we have just discussed, as well as other menus you will use
to access your datasets, database, and parameter tables.
Building a Workspace
In this exercise, you will build a workspace and look at some of the
functionality available within the user interface.
Initiating a ProMAX session is done in a variety of ways. Typically your

system administrator will create a start-up script or make a UNIX alias,
and set certain variables within your shell start-up script to make this
easy. You will use a start-up script that has already been built.
1. Type ./promax
A product name window appears, followed by the Area menu that

displays a list of all available Areas. Along the top of this window
you will find the version number of the User Interface, the machine
identification code, hostname, and license ID. The Areas are
described by a user specified name, and a UNIX name. The UNIX
name is a parsed version of the name you selected for the area.
Capital letters, most punctuation, and spaces are removed in the
parsing routine. This parsed name is the name of the actual UNIX
directory. Other information is also listed, such as owner, date and
the number of lines in each Area.

Available areas
Active Command Global Options
Area Menu
Exit Promax
Mouse Button Help Processing Queues
Window Job Notification
Configuration Options and Control
Area Menu
The black horizontal band below the menu displays mouse button
help. Mouse button help describes the possible actions at the current
location of the cursor, and gives brief parameter information during
the flow building process.
Below the mouse button help line are options to Exit ProMAX,
configure the queues and user interface, as well as check on the
status of jobs.
• Config: Brings up settings which control how lists of Areas,

Lines, Flows, Datasets, Parameter tables and Headers are sorted.
Also controls nice values for running flows, the number of
copies of flow output, where ProMAX UI restarts after exit and
popup behavior. Lastly, it allows you to specify the attributes
dsplayed for Areas and Lines.

• Option: Brings up settings for debugging, compression, use of

dataset headers for sorting, and locations of data, scratch space
and the configuration file.
• Queue: Allows user to control batch processing queues.
• Exit: Will exit the User Interface, prompts to save if there is an

unsaved flow.
• Notification: Gives information about jobs, and allows user to

check job status.
The list of options running across the top of this menu: Select, Add,
Delete, Rename, and Permission are called global options. To use
these, you must first select the command, then select the Area name
that you want the command to apply to. The Copy command works
differently by providing popup menus to choose an Area to copy
from.
2. Select Add from the Area Menu with MB1.
At this point you are building your work space. Adding an Area
creates a UNIX directory.
3. Before moving the mouse, enter an Area name
Use your name for the area name. For example, “Mary’s area”.
4. Press return, or move the mouse to register your selection.
You can control whether moving the mouse registers the selection,
or if you need to press return in the Config popup. Set the Popups
remain after mouse leaves option to yes or no.
The Line Menu appears with the same global options to choose from
as the Area Menu.

5. Add a Line using the same steps as you did for adding an Area.
Name the line “Intro Line”
Area Name
Global Options
Available Seismic Lines
Line Menu
Line Menu

The Flow window appears with the following new global options:
• Datasets: Lists all your datasets for that particular line.
• Database: Allows you to view your Ordered Parameter Files.
• Tables: Allows you to view various Parameter Table Menus.
• Product: Changes from ProMAX 2D to ProMAX 3D or VSP.
6. Add a Flow and name it “01: Display Shots”.
Access Access Access Change

Datasets Database Parameter Products
Tables
Available Flows
Flows Menu
Flow Menu

Flow Building and Execution
Now it is time to build a flow, and process data. In order to perform this
you will need to tell ProMAX which processes you want to invoke, as
well as provide specific details for each of these steps. Finally, there are
different options available for executing a flow.
Build a Flow
Upon completion of the previous exercise, you are in the ProMAX flow
building menu (see below). From here, you will construct flows by
choosing processes and selecting the necessary parameter information.
Once the flow is ready, you will execute it and view the results.
1. Look at the flow building menu.
Editable Flow
Parameter Specification
Available Processes
Edit Flow Menu

The screen is split into two sides: a list of processes on the right and
a blank tablet below the global options on the left. To build a flow,
you will select from the processes on the right and add them to the
blank tablet on the left.
2. Move your cursor into different areas of the display, such as into the
processes list, the blank tablet and the global options. Notice that
the mouse button help is sensitive to the current cursor location.
3. Global Options for flow editing:
• Add: This is the default. When highlighted in blue, a process can

be selected from the list of processes and added to the flow.
• Delete: When selected with MB1, the highlighted process is

removed from the flow. This process is actually stored in a new
kill buffer. Selecting Delete with MB2 appends a newly deleted
process to the existing kill buffer. MB3 is used to insert (paste)
the contents of this buffer into the current flow. The memory of
the buffer is maintained even after exiting a flow menu, so the
contents may be cut and pasted from one flow to another.
• Execute: When selected, the job is executed.
• There are two methods available to execute a flow using the

Trace Display process:
MB1 and MB2 will execute the flow interactively. The mouse button
help explaining the difference between MB1 and 2 does not apply to
the Trace Display process. Either button will allow the display to
immediately take over the monitor for display.
MB3 indicates Execute via Queue. This option enables the use of the
two types of batch queues. When using MB3, a new menu pops up
allowing the use of either the general batch queues or the small job
batch queues. In order for this option to work, your system
administrator must enable the queues whenProMAX 2D was
installed.
• View: Accesses the view (job.output) file. This file includes

important job information such as error statements.
• Exit: Leaves the edit flow menu, and returns you to the flow
listing menu.

4. Move your cursor into the Data Input/Output portion of the

processes list, and select the process “Disk Data Input” with MB1.
You have just added your first process to a flow.
The list of available processes is very long. It is ordered from top to

bottom in a general processing sequence with I/O processes at the
top and poststack migration tools further down on the list. There is a
scroll bar to help you view the list.
There are also options available to hide processes in the secondary,

or More list. By doing this, you can customize the list to only display
the processes you use most often.
5. In the Data Input / Output category, click MB1 on the word

“MORE”. Notice that a popup appears containing a list of
secondary processes.
6. Move the “SS Phoenix Output” process to the secondary list, and
make sure the procedure worked correctly by viewing the
secondary list again.
To move a processes to the secondary list, click MB3 on the process

name (notice the mouse button help). You can move a process from
the secondary to primary list with the same procedure.
There is also a text search to help you find specific processes.
7. Move your cursor back into the processes list (but not on a category
heading),type “gain” and press return. The following appears:
This acts as a text search, and displays all processes that contain the
word "gain." Add the process Automatic Gain Control by selecting
the process name with MB1.

8. Finish building the following flow by adding the “Trace Display”

process to your flow.
Editing Flow: 01: Display Shots
Add Delete Execute View Exit
Disk Data Input

Read data from other lines/surveys?: -----------------------------Yes
Select dataset: --------------------------------------Area: 2d-tutorials
----------------------------------Line: Wave Equation Multiple Reject
--------------------------------------------Dataset: Shots-w/ geometry
Trace Read Option: ---------------------------------------------Get All
Read the data multiple times?: ------------------------------------No
Process trace headers only?: --------------------------------------No
Override input data’s sample interval?: ------------------------No
Automatic Gain Control
Application mode: ------------------------------------------------Apply
Type of AGC scalar: --------------------------------------------MEAN
AGC operator length: --------------------------------------------1500
BASIS for scalar application: ------------------------------Centered
Exclude hard zeroes?: ----------------------------------------------Yes
Robust Scaling?: -----------------------------------------------------No
Trace Display
----Default all parameters for this process----
9. Select Disk Data Input parameters.
Select Disk Data Input with MB2 to bring up the parameter

selection window. To view the helpfile for a process, select the red
highlighted question mark.
10. Select Yes for the “Read data from other lines/surveys?” parameter.
For the introductory lessons we will read data from the tutorial line.
11. Select Invalid for the “Select dataset” parameter.
Follow the instructor’s directions for the exact path to the dataset.
After you select the dataset you will be returned to the flow editing
menu.

Default the rest of the parameters in this menu.
12. Select Automatic Gain Control with MB2.
You can now modify parameters for AGC. Select Apply for the
Application mode.
By clicking on the parameter, a popup menu appears for making a

selection from the menu. Help text appears for each of the associated
choices in the popup menu. Move your mouse out of the popup
window to retain the default.
13. Set the AGC operator length to 1500ms.
To change this value simply place your cursor on the old value, and
type in the number 1500.
This example is called a Type-In parameter. Type in a value to

replace the defaulted or existing value. The mouse help will always
read, “MB1 Enter, MB2 Edit”. Clicking MB1 will clear the default
and let you enter the new parameter. Clicking MB2 will let you edit
the existing default value.
14. Select Trace Display parameters.
For now, do not change any of the values. We will discuss many of
these options in the next chapter. At that point, you will have the
opportunity to test and explore the various options.

15. Run the flow by clicking on the global command Execute with
MB1 or MB2.
A new Trace Display window appears on the screen. Ten icons

appear in a column to the left of the traces, and pulldown menus
appear above the traces. There is a detailed discussion of these in the
next chapter.
Next
Screen
Icon
16. Select the Next Screen icon with MB1.
This takes you to the next shot. Repeat 2-3 times.
17. Select File Exit/Stop Flow.
This interrupts the job and brings you back to the flow editing menu.

Sorting
Your first look at the data was the first shot with all channels. After
clicking the Next Ensemble icon, you saw the next shot. What if you
wanted to look at every other shot? What if you only wanted to look at
channels 1 through 60? What if you wanted to sort the data to CDP and
then display. All these options and more are available in Disk Data
Input.
Sort data by source number

1. Edit your flow named “01: Display Shots”.
Disk Data Input

Read data from other lines/surveys?-------------------------------Yes
---------------------------------Line: Wave Equation Multiple Reject
---------------------------------Dataset: Shots-w/ geometry
Trace Read Option--------------------------------------------------Sort
Interactive Data Access?: ------------------------------------------No
Select primary trace header entry------------------------SOURCE
Select secondary trace header entry ----------------------- NONE
Sort order for dataset ----------------------------------------------1,3/
Presort in memory or on disk?: ----------------------------Memory
Read the data multiple times?: ------------------------------------No
Process trace headers only?: --------------------------------------No
Override input data’s sample interval?: ------------------------No
----Use the same parameters as before----
Trace Display
----Default all parameters for this process----
2. Open the Disk Data Input Menu and click where the menu reads
Get All for Trace Read Option.

This toggles the read option to Sort, and the menu will automatically
add several new options:
• Select Primary trace header entry: Allows you to specify a group

of ensembles or traces to read, or sort the data to a different
order. Virtually all sorting within ProMAX is done on input. This
allows a user to easily change domains without running a
separate, time consuming flow. An ensemble in ProMAX is any
logical grouping of traces, such as a shot record, or a CDP gather.
• Select Secondary trace header entry: Allows you to re-order, and

choose which traces you want to read within each ensemble.
• Sort order for dataset: Allows you to specify an order, or restrict

the amount of data brought read.
• Interactive Data Access: Allows you to move forward and

backward throught the data after it is displayed, as well as
change the values for primary and secondary sort order to jump
to a new location. Also allows you to select an ensemble to
display from the database.
3. Select SOURCE for the primary sort order, this will read in shot
ordered ensembles.
4. Leave the secondary sort set to NONE, this means that no sorting
of traces within ensembles will be performed.
5. Select Sort order for dataset.
An Emacs Widget Window appears for specifying input traces. A

format and example are given at the bottom of this window.
6. In the Widget Window delete the default values, and type 1, 3/.
This specifies that only SOURCE numbers 1 and 3 will be read into
the flow.
7. Move your cursor out of the Widget Window.
8. Select Execute.
The first shot displayed is Live Source Number 1.

9. Select the Next Screen icon.
This will be Live Source Number 3.
When the last source is displayed, the Next Screen icon becomes
inactive. To exit this display, select File Exit/Stop Flow.
Sort data by source and channel number

Lets make the exercise slightly more complicated, and display every
tenth shot, limiting the number of channels to 1-60.
1. Edit your previous flow.
Disk Data Input

----------------------------------Dataset: Shots-w/ geometry
Interactive Data Access?: ------------------------------------------No
Select primary trace header entry-------------------------SOURCE
Select secondary trace header entry ---------------------- CHAN
Sort order for dataset -------------------------------1-101(10):1-60/
Trace Display
2. Select CHAN for the secondary trace header entry. This will allow
you to sort each SOURCE ensemble by channel number, and also
limit the number of channels to be processed.
3. Change the Sort order for dataset to 1-101(10):1-60.
• 1-101 selects the SOURCE range to be processed.
• (10) selects every tenth SOURCE within the defined range.

• : separates the primary sort order from the secondary sort order.
• 1-60 selects the first 60 CHAN (channels) within each

SOURCE.
Note
If you only select a primary sort key, then only one range of values is allowed in the
sort order for dataset. If you select both a primary and a secondary sort key, then
two ranges of values, separated by a colon, are necessary in the sort order. This is a
common area for new ProMAX users to make mistakes.
4. Execute the flow.
You will see the first shot and all subsequent shots display with only
the first 60 channels.
5. Select the Next Screen icon to see additional shots.
6. Move your cursor into the trace display area. Notice that the mouse
button help gives a listing of the current CHAN and SOURCE.
Trace Display will always give you a listing of the values for the
current Secondary and Primary sort keys.
7. Select File Exit/Stop Flow when finished.
Sort data by CDP number

The dataset that we have been reading, is stored on disk in shot order.
Both of the previous exercises maintained the shot ordering, and
specified the shot gathers to be displayed. In this exercise you will
actually read in the data as CDP gathers. This uses the other side of
sorting, which is to actually change the type of ensemble being
processed.
Recall that the primary trace header entry specifies the type of ensemble
to build, and also the range of that ensemble to read. The secondary sort
key allows you to sort and select the traces within each ensemble.

Disk Data Input

---------------------------------Dataset: Shots-w/ geometry
Interactive Data Access?: -------------------------------------------No
Select primary trace header entry-------------------------------CDP
Select secondary trace header entry ----------------------OFFSET
Sort order for dataset ---------------------------------500-600(25):*/
Trace Display
2. Select CDP for the Primary trace header entry. This tells the
program to build CDP gathers from the input dataset.
3. Select OFFSET for the secondary trace header entry. This tells the
program to order the traces within each CDP gather by the OFFSET
header.
4. Set the sort order for dataset to 500-600(25):*/.
• 500-600(25) This select every 25th CDP between 500, and 600.
• * This is a wildcard that tells the program to read in all OFFSET

ranges.
6. Notice that we have now displayed a CDP gather, even though the
input dataset is stored on disk as shot gathers.
7. Move your cursor into the trace display area, and confirm that the
displayed gather has Primary and Secondary sorts of CDP and
OFFSET.
8. Select File Exit/Stop Flow when finished

Display near offset section

Using the sorting capabilities within Disk Data Input, you can easily
display a near offset section by selecting the first channel on each shot.
A near offset section will give you a broader overview of what the
geology for your line looks like.
Disk Data Input

----------------------------------Dataset: Shots-w/ geometry
Interactive Data Access?: -------------------------------------------No
Select primary trace header entry-----------------------------CHAN
Select secondary trace header entry ----------------------SOURCE
Sort order for dataset ----------------------------------------------*:*/
Trace Display
2. Change the primary trace header entry to CHAN (which is roughly

equivalent to offset).
3. Set the secondary trace header entry to SOURCE.
4. Set the sort order for dataset to *:*/. This will select all channels for
all shots starting with channel number 1.
5. Select File Exit/Stop Flow when finished.


Chapter 2
Additional Geometry Information
This chapter contains additional information on the geometry assignment processes.
o Geometry Core Path Overview

o Details of the Geometry Programs
o Pre-Geometry Database Initialization
o Inline Geometry Header Load after Pre-Initialization
o Geometry from Full Extraction

Chapter 2: Additional Geometry Information
Geometry Core Path Overview
How to Decide on the Primary Geometry Path

Vector Diagram
OPTIONS QUESTIONS
* Pre-Initialization
no * Does Shot and Receiver X, Y, and
station information exist in the
yes headers and do you want to use it?
no
* Full Extraction
no
* Do you want to minimize the
number of times that you have to
yes read the data?
* From Field Notes and Survey
no
yes * Do I have “Valid Trace Numbers”?
Table Diagram
Question Answer Option
Is shot and receiver station, Yes Full Extraction

and x,y information in the
headers; do you want to use
it? No Ask the next question
Do you want to minimize the Yes From Field Notes and Survey
number of times to read the
data?
No Partial Extraction

Transferring the Database to Trace Headers

When the database is completed, the information contained in it is
transferred to trace headers. The following question determines how to
match a trace in the data file to a trace in the database:
Question Answer Option
Was a Full or Partial No Inline Geom Header Load by

Extraction used to create the Chan and other trace header
database and a new output file words.
written?
Inline Geom Header Load by

Yes valid trace number.

Details of the Geometry Programs
In this section we will look in detail at the functions performed by the

main programs used in the geometry assignment process. The specific
processes that will be addressed are:
• Inline Geom Header Load
• Extract Database Files
• Geometry Header Preparation
Inline Geom Header Load is the main program used to assign geometry
values to individual trace headers from the OPF database files. One of
the main issues related to this geometry assignment procedure is to
define how a trace in a data file will be identified in the Trace Ordered
Parameter file. One of the options is to use a specific trace header word
called the "valid trace number". In order to utilize the "valid trace
number" we will have to spend some time discussing it’s origin and how
it can be used.
Another program that may be used in the geometry assignment

procedure is called Extract Database Files. We will see that this program
is one of the ways that the "valid trace number" can be generated by
running it in either the Partial or Full extraction modes.
Geometry Header Preparation is another program that may be selected

in the geometry assignment procedures. This program can be used for a
variety of different purposes. We will look specifically at how it can be
used when dealing with the problem of duplicate Field File
Identification Numbers.
Steps Performed by Inline Geom Header Load

• Inline Geom Header Load is the program that populates the trace
headers of an input data file with the geometry information stored
in the database.
• The outcome from running this program is to have a database and a

data file that "match".

• This means that every trace in the output data file exists in the
database and there is a one to one correspondence in all values in
the trace header to those in the database.
• After a successful, run each trace will also be assigned the "valid
trace number" if it was not pre-assigned using Extract Database
Files.
There are two major options in this program pertaining to how to

identify a trace in the input data file with a trace in the database. These
options are:
1. to read the "valid trace number" from the input trace header, or
2. to read the recording channel number (automatic) and 1 or 2 trace

header words that can uniquely identify this trace as having
originated from a unique shot (SIN) that exists in the shot database.
Once a trace in a data file has been identified in the Trace OPF, the
information in all of the OPF’s for that trace is copied to the trace
header.
Valid Trace Numbers

Before we proceed, let’s make sure that we understand the idea of the
"valid trace number". Understanding this will help us decide on the
"best" course of action for our data.
• The "valid trace number" is simply a ProMAX trace header word.

Every trace in the database is numbered from 1 to N, where N is the
total number of individual traces in the database.
• This is a unique number for each trace in the line or 3D project.
• A "valid trace number" combined with matching geometry is a flag

that will allow fast random access sorting of disk datasets.
• Every trace in the TRC database is assigned to a single SIN (shot),

SRF (receiver) and CDP. Every trace has an individual Shot to
Receiver Offset distance, an individual midpoint X and Y location
and many other values that are single numbers, that may, or may not
be different for every trace.
• Inline Geom Header Load matches the current trace being

processed to the database and then copies all of the trace dependent

values as well as the other order values to the trace header. The last
thing that happens is that the traces are "stamped" as matching the
database.
Valid Trace Number Origin

Where does the "valid trace number" trace header word come from?
Luckily, the answer to this is very simple.
• The Extract Database Files program writes this trace header word
after it reads and counts a trace that it is entering into the TRC
database. In this case the "valid trace number" is pre-assigned.
• If it is not pre-assigned, the Inline Geom Header Load process will

create it after it determines which trace in the database corresponds
to a trace in a data file.
The "valid trace number" is a unique number for every trace and is
stored in the trace header as TRACE_NO.
This trace header word continues to exist ONLY if you write a new trace
file after the extraction procedure.
A common question that arises concerns the decision to pre-assign the

"valid trace number" using Extract Database Files or to rely on the
alternate header identification on the first read of the input data. You
may consider using Extract Database Files if there is sufficient
information in the trace headers that can be transferred to the database
which will save time and increase accuracy of the geometry definition
process. The extraction may be run in either the partial extraction or full
extraction modes depending on what information is available in the
trace headers of the input data.
Steps Performed By Extraction

The steps performed by the extraction options are:
Pre-Geometry Initialization (or partial extraction) which is sometimes

used when no receiver information exists in the incoming headers.
Partial Extraction counts each of the following:
• the number of traces encountered

• the number of shots encountered
• the number of traces per shot

and then
• writes the trace count number and SIN to the trace header
Full Extraction is used when you want to extract the shot and receiver
location and coordinate information from the incoming headers.
Full Extraction counts each of the following:
• the number of traces encountered

• the number of shots encountered
• the number of traces per shot
• the number of receivers encountered
• the number of traces per receiver
and then
• writes the trace count number and SIN to the trace header
IF you have run the extraction in either mode, AND written a new trace
data file, AND have not altered the number of traces in the database, you
now have “valid trace numbers” in the headers of the output data set
which you can use to map a trace in a data file to a trace in the database.
This mapping will be performed by Inline Geom Header Load after the
database is completed.
Between Extraction and Geom Load

After running Extract Database Files in either mode there are many
steps that need to be completed prior to running the Inline Geom Header
Load.
The extraction only partially populates the database. More work will
generally need to be done in the Spreadsheets to input the remaining
information.
After the Spreadsheets are complete, the next step would be to complete
the CDP binning procedures and then finalize the database.
With the database complete, you can continue with the next step of
loading the geometry information from the databases to the trace
headers. You may elect to address a trace by its "valid trace number"
assigned during the extraction or you may read a combination of trace
headers to identify the trace.

Geometry Load Procedures

For the first option, Inline Geom Header Load operates as follows:
1) it identifies the TRACE_NO of the incoming trace and finds that trace
in the TRC database.
2) it copies the appropriate TRC order values to the trace header and
then
3) finds the shot, receiver, cdp, inline, crossline, and offset bin for that
trace. The appropriate values from those orders are then copied to the
trace headers as well.
In the second option, Inline Geom Header Load does not know exactly
which TRACE_NO it is looking for. It does know which channel and
shot to look for based on the header word(s) that you selected. Given
that this mapping is unique, the program now knows which SIN and
CHAN to look for in the TRC database. Once the entry is found, the
TRACE_NO is copied to the headers and the steps outlined in the first
option are performed.
Again, the key to the second option is that you need to identify which
shot a trace came from by a "unique" combination of header words for
that shot.

Pre Geometry Database Initialization
Note: In general, this process is not recommended for medium to large

volume 3D projects.
To create a minimum set of entries in the SIN and TRC Ordered

Parameter files, based upon the information found in the trace headers
of the data passed through the flow, selecting Yes to the option for Pre-
Geometry Extraction. Basically this process counts how many traces,
different FFIDs, and recording channels were present for each input
FFID. Therefore, it can build the TRC and SIN ordered database files.
An SRF OPF could be created, and may or may not have any
information in it.
Partial Extraction Flow Chart
Disk Output - Pre-Init Path

O.B. UKOOA ASCII Field
Notes Data
UKOOA SEG-? Input

Import Spreadsheet
Manual
Input Import
Database
Import Seismic Data
Extract (ProMAX)
Database
Geometry Files
Spreadsheet
Builds TRC and SIN
Ordered Parameter OPF’s only Disk Data
Pre Geom Init = yes Output
Files
Marine Data Inline Geom

SSD correction Header Load Valid Trace
Numbers
Overwrite Seismic Data
Seismic Data Trace Headers
(ProMAX)
(ProMAX)

This option may be appropriate for relatively small datasets which only
have FFID and CHAN in the input trace headers. This option should be
used when reading the field data and writing the data to disk for the first
time. In so doing, information, such as FFID, number of shots, number
of channels are written to the database, and are then available when the
geometry is completed. Selecting this option will also stamp the output
dataset with “valid trace numbers”, which allows you to process with
trace headers only and overwrite the dataset with updated geometry
from the database files. This is an important concept for the Inline Geom
Header Load process.
In the following example, you will assume that only the FFID and
recording channel number exist in the incoming trace headers. This
information will be extracted, using the perform pre-geometry database
initialization option in Extract Database Files.

Pre Geometry Initialization flow

1. Make a new line called “from pre-initialization”.
2. Build the following flow:
Editing Flow: 01-Pre-Geom Initialization
SEGY Input
Type of storage to use: -------------------------------------------- Disk
Select disk file type: ----------------------------------------Disk Image
Enter DISK file path name: --------------------------------------------
---------------------------------/misc_files/2d/segy_0_value_headers
MAXIMUM traces per ensemble: ---------------------------------120
Remap SEGY header values: -------------------------------------- NO
Extract Database Files
Is this a 3D survey: ---------------------------------------------------No
Data Type: --------------------------------------------------------LAND
Source index method: ---------------------------------------------FFID
Receiver index method: ------------------------------------STATIONS
Mode of operation: --------------------------------------OVERWRITE
Pre-geometry extraction?: -----------------------------------------Yes
Disk Data Output
Output Dataset Filename: -------------------------”Shots-raw data”
New, or Existing, File?: -------------------------------------------New
Record length to output: ----------------------------------------------0.
Trace sample format: ---------------------------------------------16 bit
Skip primary disk Storage?: ----------------------------------------No
3. Enter the parameters for the SEGY-Input process:
Enter the full path name to the SEGY input dataset as described by
the instructor.
There are 120 traces per ensemble.
4. In Extract Database Files, select to identify which traces belong to

which shots and receivers as follows:

Sources: identify by FFID.
Receivers: identify by STATIONS.
5. In Extract Database Files, select Yes for the option Pre-geometry

extraction.
This initializes the SIN and TRC domains of the Ordered Parameter
Files, stamps the dataset with valid trace numbers, and allows for the
use of overwrite mode when performing the Inline Geom Header
Load step later.
6. In Disk Data Output, enter the name for a new output file, such as
“Shots-raw data”.
After the Flow Completes

8. Exit the flow building level and select Database from the global
command line.
9. Check the OPFs, verifying the number of records in the dataset, the
number of channels/record, and the FFID range.
The only OPF files that should exist are LIN, SIN, and TRC. If SRF
exists, this means that you identified traces for receivers by
coordinates. You will also find that the SRF OPF has 1 value in it.
Complete the Spreadsheet

In this sequence, the next steps would be to complete the Sources,
Receivers and Patterns Spreadsheets and perform the CDP binning.

Inline Geometry Header Load after Pre Initialization
In this sequence, we ran the Extract Database Files process in the pre-
initialization mode. Here, we will read the output data from the pre-
initialization step and identify a trace relative to its “valid trace number”
with respect to the database.
Load Geometry to Trace Headers

1. After you have run the 2D land Geometry Spreadsheet and finished
assigning geometry, build the following flow::
Editing Flow: 03-Load Geom to Headers and QC
Disk Data Input

Read data from other lines/surveys: -------------------------------No
Select Dataset: --------------------------------------”Shots-raw data”
Trace read option: ----------------------------------------------Get All
Read the data multiple times?: -------------------------------------No
Process trace headers only?: --------------------------------------Yes
Override input data’s sample interval: ----------------------------No
Inline Geom Header Load
Match by valid trace number?: ------------------------------------Yes
Drop traces with NULL CDP headers?: --------------------------No
Drop traces with NULL receiver headers?: ----------------------No
Verbose Diagnostics?: -----------------------------------------------No
Disk Data Output
Output Dataset Filename: -------------------------”Shots-raw data”
New, or Existing, File?: -------------------------------------Overwrite
Record length to output: ----------------------------------------------0.
Trace sample format: ---------------------------------------------16 bit
Skip primary disk Storage?: ----------------------------------------No
2. In Disk Data Input, enter your input shot dataset.
In this sequence, we only process the trace headers.

3. In Inline Geom Header Load, match the traces by their “valid trace
numbers”.
Since the traces were read and counted with Extract Database Files,
you have a “valid trace number” to identify a trace. You have binned
all traces; therefore, do not drop any traces. Unless you have a
problem, there is no need for verbose diagnostics.
4. In Disk Data Output, output to the same dataset as specified in Disk

Data Input.
We will use the overwrite option in conjunction with trace header

only processing in the Disk Data Input.
5. Execute this flow.
In the Extract Database Files path, the Inline Geom Header Load
process operates on a sequential trace basis, and includes a check to
verify that the current FFID and channel information described in the
OPFs matches the FFID and channel information found on each trace of
each ensemble. The Inline Geom Header Load process will fail if these
numbers do not correspond. You must then correct the situation by
changing the geometry found in the OPFs, or possibly by changing the
input dataset attributes.

Chapter 3
ProMAX Marine 3D Geometry
Geometry Assignment is designed to create the standard Ordered Parameter File directories,
OPFs, and load standard ProMAX geometry information into the trace headers. The sequence of
steps depends upon available information. This chapter serves as an example of how you could do
the geometry assignment sequence for marine 3D data. The Geometry Assignment Overview
section in the Online Help provides further details of the geometry assignment process.
o 3D Marine Geometry from UKOOA Data

Chapter 3: ProMAX Marine 3D Geometry
3D Marine Geometry from UKOOA Data
In this exercise, you will import a UKOOA file which is the standard
output from navigation processing. The file contains:
• coordinates for each shot location
• receiver coordinates for each trace of each shot.
You will load this single file to provide the SIN and TRC spreadsheets
with data. You will then continue with binning, using the Calc-Dim
option.
This marine 3D survey was collected using a single source / single cable
geometry.
Using the Marine 3D Geometry Spreadsheet

1. Make a new line, called “Appendix C: 3D Marine”.
Editing Flow: 01 - spreadsheet
3D Marine Geometry Spreadsheet
2. From the global commands select File UKOOA import
Enter the directory name as described by your instructor and then

click OK.
3. Choose the 3d_marine_ukooa file from the list.

4. From the Format pulldown menu, open a list of saved formats and
choose STANDARD UKOOA 90 Marine 3D.
Separate the windows.
5. Check the column definitions by clicking on the words in the

Parameter column.
Notice that there are two column definitions:
• One for the “R” cards
• one for the” S” and “V” cards
Also note that, if desired, the coordinates can be altered using the
Math Op and Op Value columns.

6. Choose to Apply the format and Overwrite all the data.
While the import is running, you will see a variety of Status windows.
Eventually you will see a “Successfully Completed” window.
7. Quit from each of the column definition windows and select the
File Exit from the main import window.
8. From the main menu click Setup and input the following
information:
• 25 m receiver station interval
• 25 m source station interval
• 50 m sail line (cross line) interval
• Set the azimuths to 0o for the shots and receivers (the correct
azimuth will be determined later).
9. Click on Ok
10. Generate a basemap of the project by opening the Sources

Spreadsheet and selecting View View All Basemap.

Determine Primary Azimuth for Binning

1. Use the “Double Fold” icon and MB3 to measure the azimuth of the
shot lines.
25 mt group int
25 mt shot int
50 mt line spacing
32 degree azimuth
You should measure a value of approximately 32 degrees East of

North.
2. Click Setup and enter 32 degrees for the Nominal Sail Line
Azimuth.

Cable Feather QC
Using the same Basemap you can generate a quick QC display showing
the cable feather for individual shots or for entire shot lines.
1. Click on the “Highlight Contributors to Trace Domain” icon and

then follow the mouse button helps to display the cables for the shots
2. Press MB1 on any shot and its cable will highlight.
3. Pres MB2 near a shot and all shots on the same shot line will
highlight.
4. Press Shift-MB2 to clear the screen.
5. Repeat as desired.
6. Exit from the XYGraph using File Exit Confirm.

CDP Binning
1. In the main menu, click Bin
2. In the Available Binning Options window, select Assign midpoints

by existing index number mappings in the TRC and click Ok.
Note:
You are assigning midpoints based on existing index number

mappings in the TRC. You loaded the x,y positions for each shot and
each receiver for each shot from the UKOOA file

3. Select Bin midpoints for the the Binning Type and click Ok to
open the bin definition window.
Grid Constants
calculated bins 32 degrees 12.5 by 50 meters
4. For the Bin space name, enter a grid name and set the following
grid constants:
Grid Azimuth = 32, dx=50, dy=12.5, offset bin increment=50 and

set the inlines to be parallel to the Y axis (parallel to azimuth).

5. Click the Calc Dim button.
A grid is automatically calculated to include all midpoints.The

origin of the grid is computed as well as the extents of the grid
parallel and perpendicular to the azimuth.
Calculated Values
6. Click OK to dismiss the notification window.
7. Click on the Save button to save the grid.

QC the Calculated Grid

1. Select “Define binning grid” from the main binning window and
click on Ok.
This will bring up a small map window.
2. Select Display Midpoint Control Points Black

(depending on the color of the background).

You should get the following display:.
Subsurface Point Scatter
3. Click on Grid Open and select the grid name that you saved
from the Calc Dim operation.
This step overlays the bin grid on your subsurface data.

Overlay the Grid and the Shot Locations
4. You may elect to add a Display of the shot locations by clicking on

the pull down menus Display Source Control
Points White
Interactive Grid QC and Alteration

1. You may elect to alter the grid by using any of the interactive grid
editing icons if desired.
You may choose to have one subsurface line for each surface sail
line. In this case you may elect to turn off the midpoint and shot plots
and redisplay the shots only in black.
Views Remove Shot based Posting of Position

Views Remove Midpoint based Posting of Position
Display Source Control Points Black
Grid Display
2. Here you may elect to Zoom in on an area and reposition the

proposed CDP binning grid so that the centers of the Grids follow
the sail lines and so that the shot locations coincide with a CDP bin
centers.
One CDP Line per Sail Line
3. You may find that you will want to delete one “inline” from the
calculated grid and you may need to adjust the inline extents by
redisplaying the Midpoint Control Points
Display Midpoint Control Points Black.

4. You may end up with a final CDP bin Grid similar to that shown in
the following diagram:
5. When satisfied with the CDP Grid make sure that you save it before
exiting from the XYgraph. Select Grid Save to and enter a
new grid name in the dialog box and press the OK button:

6. Exit from the XYGraph using File Exit Confirm
Load Final Grid and Perform CDP Binning

1. Return to the 3D Marine Midpoint Binning Window and LOAD the
final grid parameters to this menu.
3
1
2. Select the bin space name that was saved in the XYgraph session
3. Click on the OK Button.
Critical Parameters During CDP Binning

Even if you know that you are going to run the Flex Binning processes
prior to Velocity Analysis, Stack, DMO and Migration, it is CRITICAL
to get the conventional CDP binning and Offset Binning Parameters
correct.
The CDP Binning parameters, even after Flex Binning, still control how
many lines and cross lines exist for the project. The often overlooked

parameters pertaining to offset binning are extremely important in the

case of Flex Binning.
In the Flex Binning assignment one of the most critical parameters

pertains to the number of traces per offset bin that should contribute to
each CDP. Typically, this will be set to 1 in order to stabilize the offset
contribution to each CDP. If the original offset binning is not done
correctly, then there is no way to stabilize the Flex Binning output.
The Goal of the Offset Binning is to achieve one trace per CDP per
offset bin, the same requirement for DMO processing. For a typical
marine case you would specify the offset bin increment as twice the shot
interval. In this case the shot interval and the group interval are the same
at 25 meters.
25 mt group intv
3182 mt
x
near offset = 207
next offset = 232
207 mt
maximum offset = 3182 mt
first bin center = 219.5
minimum offset to bin = 194.5
maximum offset to bin > 3219.5
offset bin increment = 50
50 mt offset bin intv

3182 mt
x
first bin center = 219.5
minimum offset to bin = 194.5
maximum offset to bin > 3219.5
use 3300 ft offset bin increment = 50
Marine 3D Collection Geometry

CDP Binning Parameters for Marine 3D
In this case we will use offset bins that have bin centers at 50 meter
increments with a near offset bin center at 219.5 meters and a far offset
of 3300 meters.
You can use a display from the database to QC these parameters after
the final binning step. If you plot a 3D: XYgraph, from the TRC order
and plot OFFSET in X, CDP in Y and color code by OFB, you can see
the offset distributions on the CDP gathers. After some selective
zooming you can overlay the proposed offset binning grid for QC. You
may also find that using the “contrast.rgb” color table in the
$PROMAX_HOME/port/misc directory will be useful.

Zoom of Offset vs CDP plot with Offset Bins Overlay
You will also notice on this plot that in areas there are duplicate offsets
at given CDP’s thus making it impossible to reach the goal of 1 trace per
CDP per bin.
4. Make sure that the Inlines are specified to be parallel to the Y axis.

5. Click Apply and when the Binning is complete, click Cancel from
the Binning window.
Receiver Binning
1. For the Binning Type, select Bin receivers and click OK.
This step is completely optional. Run this step if you intend to run
any surface consistent processing like surface consistent
deconvolution or residual statics.
1
2
4 3
5
2. Load the information from the CDP grid as a starting point
3. Change the Y dimension of the receiver grid to match the group

interval of 25 meters
4. Enter a Bin space name such as “receiver grid 32 degrees 50 by 25

meters.”

5. Automatically compute the extents of the receiver grid by clicking

on the Calc Dim button
6. Perform the binning by clicking on the Apply button
A Binning receiver locations.... window appears.
7. Cancel from the Receiver binning window when the binning is

complete.

QC the CDP Binned Data using a Fold Plot

1. Select QC Midpoint Bin data, the Coordinate Space Fold display and
then select your bin grid from QC Bin Space, and click Ok.
Finalize the Database

1. Select Finalize Database, and click Ok.
2. When complete, Cancel from the Binning Menu.
3. Exit from the Spreadsheet menu using the File Exit pull down
menu.

Assigning CDP Flex Binning
Editing Flow: 02: Assign CDP flex binning
Assign CDP Flex Binning*

Crossline overlap factor ---------------------------------------------- 3
Inline overlap factor ---------------------------------------------------1
Maximum number of trace/offset bin---------------------------------1
Omit traces with zero weight --------------------------------------- No
Limit flex binning to subset of survey ----------------------------- No
Apply crossline distance weighting ------------------------------- Yes
Crossline distance weighting -----------------------------
------------------------0: 0-1, 25-0/1500: 0-1, 50-0/3175: 0-1, 75-0/
Apply inline distance weighting ----------------------------------- Yes
Inline distance weighting -------------------------------0: 0-1, 6.25-0
Apply azimuth weighting rule -------------------------------------- No
Apply prime line weighting rule----------------------------------------
Yes
Prime line weighting ------------------------ 0:1.0,0.1/1500:1.0,0.5/
Number of user defined rules ------------------------------------ None
Verbose printout? ---------------------------------------------------- No
2. Look at the parameters for the Assign Flex Binning Process.
Inline and Crossline Overlap Factors

The Inline and Crossline overlap factors define the total search radii
for all traces that may contribute to an output CDP.
The input values are in numbers of original CDP bins.

Crossline Overlap Factor = 2.0

Crossline Direction
Inline Overlap Factor = 0.8
Inline Direction
Inline and Crossline Overlap Factors
Typical values for these parameters would be 1 in the inline direction

and somewhere between 2 and 5 in the crossline direction. For our
case we will run with 3 in the crossline direction which means that
we will search the current line and 1 line on each side for
contributors.
3. We will allow 1 trace per offset bin.
4. Allow traces with zero weight to contribute.
This means that if, for some reason, the only trace that is available
for a particular offset bin in a CDP has a weight of zero, use it
anyway.
5. Do NOT limit the Flex Binning to a subset of the survey.
Process the entire project

Inline and Crossline distance Weighting

6. Parameterize the Crossline and Inline weighting entries.
Typically, these weighting functions will be offset variant. We will

generally want to keep the near traces from the original stack track
but we will generally need to change the weight function parameters
for the far offsets.
Inline Overlap = 1 Inline Bin Size=12.5

Crossline Overlap=3 Cross Line Bin Size=50
Near Intermediate Far

Offsets Offsets Offsets
1 1 1
inline
direction
25’
50’
75’
6.25’ 0 0 0
1 1 1
XLine --> offset: distance - weights
0: 0-1, 25-0 1500: 0-1, 50-0 3175: 0-1, 75-0
Inline --> offset: distance - weights
0: 0-1, 6.25-0
Inline and Xline Distance Weighting
Azimuth Weighting
7. The following is an example of how you could set the parameters
for the the Azimuth weighting entry. We won’t set them for this
exercise but the description is included for reference.

Again you may elect to vary the azimuth weights as a function of

offset where you would weight the traces with the prime sail line
azimuth higher than others. You may find that you will have to open
the weight range for the far offsets where feathering is greater.
Pass Azimuth 1
Pass Azimuth 2
Taper Length
Pass weight Linearly tapered weight Reject weight
Pass weight if Reciprocal Traces = ‘Yes’, otherwise reject weight
Lineraly tapered weight if Reciprocal Traces = ‘Yes’, otherwise reject weight
Azimuth Weighting Schematic
for our example you may use 3 different weighting schemes for
different offset, azimuths pairs:
0:30,34,1.0,0.0,1/ 1500:28,36,1.0,0.0,2/ 3175:22,42,1.0,0.0,3
This will give us +/- 2 degrees at the near offsets, +/- 4 degrees at the
mid offsets and +/- 10 degrees at the far offsets. Note also that we are
increasing the taper length from 1 to 3 degrees as the offset
increases.

Prime Line Weighting

8. Parameterize the Sail line weighting entry.
In the marine case we may elect to weight traces by a single sail line.
In this case all of the traces that contribute to the CDP line are
examined by their S_line trace header word. The sail line with the
highest number of contributors is the prime sail line and traces that
come from this sail line have the highest weight. You may elect to
put an offset variant weight function based on the dominant sail line
represented in the traces. In this example we will use an offset
variant weighting function that weights the sail line highly for the
near offsets and relaxes the weighting function toward the far
offsets:
0: 1.0, 0.1/ 3000: 1.0, 0.9
9. Set the number of user-defined rules to NONE.
you will have to cycle from ONE through FIVE back to NONE
10. Use the default of No to not request a verbose printout.
11. Execute the Flow.

QC Plots
The Assign CDP Flex Binning process writes a number of values to the
CDP Order Parameter (database) Files. You may elect to generate QC
plots using the 3D database QC capabilities.
The values that are available for QC are:
CDP: GEOMETRY: FLEXFOLD
The number of traces contributing to the CDP after flex binning. One of
the goals of flex binning is to provide uniform fold. The uniformity of
this value indicates how well the flex binning worked.
CDP: FLXBINQC: MINOFF
CDP: FLXBINQC: MAXOFF
If the short or long offsets are missing from a flex binned CDP, these
values can be too high or too low, respectively.
CDP: FLXBINQC: MEANOFF
CDP: FLXBINQC: RMEANOFF
These values can show if long or short offsets are missing. At CDPs
where the values are high, short offsets are missing. If the values are
low, long offsets are missing. The expected mean offset is half the sum
of the first offset bin center and the last offset bin center. Ideally,
RMEANOFF, the ratio of the mean to the expected mean, should be 1.
In our case we specified 50 as our near offset and 3225 as our far offset.
This yields a predicted mean of 1725 meters.
CDP: FLXBINQC: STDDOFF
CDP: FLXBINQC: RSTDDOFF
Tell where missing offsets are if the missing offsets happen to occur
such that the mean offset is unchanged. The ratio of standard deviation
to expected standard deviation will be 1 for an even offset distribution.
If the ratio is less than 1, short and/or long offsets are missing. If it is
greater than 1, middle offsets are missing.
CDP: FLXBINQC: MEANAZTH

Indicates how well the Apply azimuth weighting rule accomplished

your goals.
Produce QC plots from the database

1. Open the XDB Database Display and generate the following pairs of
displays:
• 3D: XYGRAPH: CDP: Xcoord, Ycoord, FOLD

• 3D: XYGRAPH: CDP: Xcoord, Ycoord, FLEXFOLD
• 3D: XYGRAPH: CDP: Xcoord, Ycoord, MINOFF

• 3D: XYGRAPH: CDP: Xcoord, Ycoord, MAXOFF
• 3D: XYGRAPH: CDP: Xcoord, Ycoord, MEANOFF

• 3D: XYGRAPH: CDP: Xcoord, Ycoord, RMEANOFF
• 3D: XYGRAPH: CDP: Xcoord, Ycoord, STDDOFF

• 3D: XYGRAPH: CDP: Xcoord, Ycoord, RSTDDOFF
and also:
• 3D: XYGRAPH: CDP: Xcoord, Ycoord, MEANAZTH
Notice that using the recommended parameters we have done a good job
of stabilizing the fold and offset distributions of all of the CDP’s.
CDP Contribution and Null QC

There is one more set of QC plots that you might find useful. We already
know that we have good offset distribution and fold but we don’t know
how many traces we have used more than once and how many we have
thrown away.
2. From the XDB Database Display, generate 2D (simple) plots of the

FLEXCDP#1, #2 and #3 attributes from the Trace database.
Any trace that is NULL for FLEXCDP#1 did not contribute to any
CDP. Non NULL CDP’s in #2 and #3 contributed to more than 1
CDP.

3. Exit XDB Database Display and DBTools.

Expand Flex Binning
Expand Flex Binning performs the second step of replicating or deleting

traces per the bin assignments. This tool should be run before imaging
processes like stack, DMO, prestack migration, AVO analysis, or
velocity analysis.
This tool accepts traces in any sort order and makes a copy of each input
trace for each CDP bin to which it contributes. The tool finds the list of
CDPs the trace contributes to by querying the TRC database parameter
FLEXCDPS. If the trace contributes to no bins, it will be deleted. The
tool simply reproduces one trace at a time, therefore, if the input data are
CDP sorted, they would no longer be sorted on output from this tool.
If a trace contributes to a CDP and its midpoint does not lie within the
boundaries of the CDP bin, the trace’s source and receiver coordinates
will be adjusted so that the trace’s adjusted midpoint lies at the same
relative position in the new CDP as it did in it’s original bin. The tool
does this so that 3D DMO will apply the trace to its new bin rather than
just increasing its effect in the old bin.
shot and receiver

locations after
flex binning
X
o
O
X original shot and
receiver locations
o
O
We do not actually have any trace data for this example so we cannot
run this.


Chapter 4
3D Land Swath Geometry
Geometry Assignment is designed to create the standard Ordered Parameter File directories,
OPFs, and load standard ProMAX geometry information into the trace headers. The sequence of
steps depends upon available information.
This chapter serves as an example of how to input the geometry for a swath geometry. The main
items of interest here are the ways to handle the spreads rolling on and off the ends of the swaths
and how to handle the cable roll between the swaths. The Geometry Assignment Overview
section in the Online Help provides further details of the geometry assignment process.
o 3D Land Swath Geometry

Chapter 4: 3D Land Swath Geometry
3D Land Swath Geometry
In this exercise you will look at another Land 3D example, a more

standard swath shoot.
153-154
Receivers 1001-1154
Receivers 2001-2154
shots 10001 -
10153
shots 50001-
50153
1 Receivers 8001-8154
Note the numbering sequence as described on the basemap. In this case

we have single station numbers that can be divided into line and station
numbers. We will choose this option in order to make the pattern
management easier. For the cable stations we will divide the 1001 - 1154

stations into line 1 stations 1 - 154. The remaining receiver lines will be
handled similarly. We will also divide the shot stations 10001-10153
into line 10 stations 1 - 153. The remaining shot lines will be handled
similarly as well.
This exercise will present a couple of logistical problems in how to

handle survey files and also how to roll the spread on and off at the end
of the swaths using a single pattern definition per swath.
440’
110’
110’
Project Geometry Constants

Prepare the Line and run the Spreadsheet

1. Make a new line, called “AppendixD: 3D Land Swath”
Editing Flow: 01 - Spreadsheet
3D Land Geometry Spreadsheet
4. Click the Setup pull down and enter the project constants:
• Nominal Receiver Station Interval = 110 ft.
• Nominal Source Station Interval = 110 ft. (or 155)
• Nominal Crossline Separation = 440 ft.
• Base Source Station co-ordinates upon a match (Required)

between source and receiver station numbers = Yes
• This project was recorded using a surface source
• The coordinate system is in feet
5. Click OK.

Receivers Spreadsheet
1. Open the Receivers Spreadsheet using the File Import pull
down open the ASCII file import window.
2. Select the “3d_5swath_recs” file from the directory that your

instructor describes for you.
3. Using the Format pull down enter an new columnar format

description such as “5 swath receivers”
4. In the Column Import Definition window click on the word

“Station” in the parameter column and then paint the 3 columns that
we will use as the station numbers.

Note:
We are splitting the station number into two numbers, one for the line
and the remaining for the station along the line.
5. Select the remaining column definitions for Line, and the X and Y
coordinates.
Filter the file and remove unwanted comment cards

6. Click on the Filter button and then respond to the window asking
you to delete any card that does not match the columnar format that
was defined.

7. When the filtering is complete you should get a “Filtering

Complete” window and there should be a card at the top of the file
that says “Ignore Record for Import”
8. Click on the OK button to dismiss the window.
9. Select to Apply the format and Overwrite the values with the new
import values.
10. Click on OK and the receivers spreadsheet should become

populated with the selected values.

Sources Spreadsheet
1. Open the Sources Spreadsheet by clicking on the word Sources in
the main spreadsheet menu window.
2. Select the File Import pulldown menus and select the

“3d_5swath_shots” file from the same directory where you found
the receivers file.
3. Using the Format pull down enter an new columnar format

description such as “5 swath shots”
4. In the Column Import Definition window click on the word

“Source” in the parameter column and then paint the entire source
station number columns that we will use as the source numbers.
Note:
We are splitting the station number into two numbers, one for the line
and the remaining for the station along the line.

5. Click on the word “Line” in the parameter column and then paint
the first two columns as the line number. (include a blank before the
first column).
6. Complete the column definitions for the Station and X and Y

coordinates.
7. Click on “Filter” to Ignore any unwanted cards.
8. Apply the format and Overwrite the values in the database. The
Sources spreadsheet should now be populated with the selected
information.

9. Generate a Basemap from either the Sources or Receivers

spreadsheet using the View View All Basemap pull down
menu.
10. Use the Cross Domain Contribution (Double Fold) icon MB3
function to measure the Azimuth of the cable lines. You should
measure approximately 25 degrees.

Reopen the Setup window by clicking the Setup button from the main
menu and input 25 degrees for the nominal azimuth.
Note:
In this mode the assignment mode is set to use the method of

matching pattern number in the SIN and PAT spreadsheets.
This is correct since we did not import patterns and did not run an
extraction. In this case we will have to specify patterns in the Patterns
Spreadsheet.
Patterns Spreadsheet
As an example we will define a pattern that is typical for a swath
shooting geometry. We will define a basic bi-symmetric split geometry
where we will have for any given shot 4 live cables and 60 traces on each
cable. The shots will be between the center two cables and between
traces 30 and 31 on each cable. There will be no gap in the split spread.
1. Open the Patterns Spreadsheet by clicking on the word Patterns in

the main spreadsheet menu window.
Two windows will appear.
2. In the smaller window specify that there are a maximum of 240

traces per shot and that the number of traces per shot varies.
3. Click OK in the smaller window to dismiss it.
4. We can now specify the first pattern. Since we are using a line/
station relationship we will need a separate pattern for each swath.

For the First pattern mark a block of 4 cards and then fill the
columns as shown in the next diagram.
• Fill Pattern starting at 1 and increment of 0

• Fill Min Chan starting at 1 and increment by 60
• Fill Max/Gap Chan starting at 60 and increment by 60
• Fill Chan Inc starting at 1 and increment by 0
• Fill Rcvr Line starting at 1 and increment by 1
• Fill Recr MinChan starting at 1 and increment by 0
• Fill Rcvr MaxChan starting at 60 and increment by 0
• Fill Rcvr Inc starting at 1 and increment by 0
5. Copy this pattern 4 times (one time for each remaining

swathmaking a total of 5 swaths). Use the Edit Copy pull
down to copy the pattern to a new one.

6. Next change the receiver lines to match the pattern numbers on a

per swath basis. The first swath patterns will use receiver lines 1-4,
the second 2-5, the third 3-6, etc.
The Patterns Spreadsheet should be as follows:
7. Exit from the Patterns Spreadsheet using the File Exit pull
down
Complete the Sources Spreadsheet

Now that the patterns have been defined we can assign each shot to use
the appropriate pattern and then “SHIFT” the pattern for each shot.
1. Return to the Sources Spreadsheet.
2. You may elect to reorder the columns of the spreadsheet so that the
pattern and pattern shift cards appears near the Line and Station
columns for convenience. Use the Setup Order pull down and
then click on the column headers in the order you want the to
appear. Use MB2 on the last column heading of interest.

3. For all of the shots in the first swath (on line 10) we will use pattern
number 1 and then we will shift the pattern by -29 for the first shot
and increment the pattern shift by 1 for each shot. The last shot in
the first swath should be 123.
4. For all the shots on the second swath (on line 20) use pattern
number 2 and shift the first shot by -29 and increment the pattern
shift by 1. Similarily, complete the pattern number and pattern shift
entries for all shots in all 5 swaths using multiple Find and Fill
operations.
5. When complete exit from the Sources spreadsheet using the

File Exit pull down.
Trace Assignment
This exercise illustrates CDP binning procedures. For this example we
will automatically compute a CDP grid based on some initial known
values and then apply the grid using the batch CDP Binning* process.
1. In the main menu, click Bin.
A submenu appears with options for Assigning the traces to

midpoints, defining the bin grid, binning the data, quality controlling
the binning, and finalizing the database.
2. Select to Assign midpoints by using “Matching pattern number in

the SIN and PAT spreadsheets”, and click Ok.
In this case the Assignment step is performing the following

calculations:

• Computes the SIN and SRF for each trace and populates the
TRC OPF
• Computes the Shot to Receiver Offset (Distance)
• Computes the Midpoint coordinate between the shot and

receiver.
• Computes the Shot to Receiver Azimuth.
An Assignment Warning window will pop up warning that some or

all of the data in the Trace spreadsheet will be overwritten. Click
Proceed.
A number of progress windows will flash on the screen as this step

runs. A final Status window should notify you that you Successfully
completed geometry assignment. Click Ok.
If this step fails, you have an error in your spreadsheets somewhere.

Checck your job.output listing for the cause of the error. Problems
are ususally related to the spread and/or pattern definitions.

Spread QC after Trace Assignment

1. Open the Receiver Spreadsheet and generate a basemap using the
View View All Basemap pull down menu.
2. Use the Cross Domain Contribution (Double Fold) icon MB1 and
MB2 functions to view which receivers have been defined to be live
for each shot and also to see which shots contribute to each receiver.
You should observe a symmetric split spread of four cables
centered on the nearest shot that rolls on and off the spread at the
ends of the swath.

3. Exit from the XYgraph and the Spreadsheet using the

File Exit Confirm and File Abort pull down menus
respectively.
Automatic Bin Calculation and QC

1. Select to “Bin midpoints” and click on OK. You should get the
following window:
2. Set the Azimuth=25, Grid Size in X = 55, Grid size in Y=55, Bin
Space Name=Calculated grid 25 degrees 55 by 55, Offset Bin
Increment=110 and select to set the Inlines to be parallel to grid Y

axis, which is parallel to the defined azimuth. In our case, this is

parallel to the cable.
3. Click on the “Calc Dim” Button
The Calc Dim operation computes the origin of the grid and the
Maximum X and Y dimensions.
4. Save the grid definition by clicking on SAVE.

5. Click on Cancel to exit this window.
QC the Calculated Grid

1. Select “Define binning grid” from the main binning window and
click on Ok.
This will bring up a small map window.
2. Select Display Midpoint Control Points Black

(depending on the color of the background).
You should get the following plot:

Mid-point Scattergram for CDP Binning
3. Click on Grid Open and select the grid name that you saved
from the Calc Dim operation.
This step overlays the bin grid on your subsurface data.

Because of the density of the display a zoom will help show and QC
the results.
Grid Overlay for QC
You may elect to alter the grid by using any of the interactive grid
editing icons if desired. (There should be no need to alter the grid)
4. Exit from the XYGraph using File Exit Confirm
5. Close the 3D Binning and QC window by clicking on the Cancel

Button.

6.Select File Exit from the main spreadsheet menu to exit the
Geometry Spreadsheet.
Complete CDP Binning using the Batch CDP Binning Tool

This exercise completes the CDP binning and database finalization
steps.
1. Build and execute the following flow:
Editing Flow: 02 - CDP Binning
CDP Binning*
Binned Space Name ------- “your grid”
This process will perform the CDP binning and Finalization steps in
a batch job instead of interactively using the spreadsheet.
2. Once the Binning is complete you can generate the QC plots using
the Database/Get and 3D options within XDB.

Chapter 5
Archival Methods
Archiving your data protects your work from system failure and may allow you to bring data into
other software packages. It is also useful for freeing up disk space and preserving flows. In this
chapter, we will discuss the archiving methods that can be run from inside the ProMAX User
Interface.
o SEG-Y Output
o Tape Data Output
o Archive Wizard

Chapter 5: Archival Methods
SEG-Y Output
ProMAX offers a variety of industry standard and individual company

output formats. Of these, SEG-Y is the most commonly used. This
process can write out industry standard SEG-Y tapes as well as
frequently requested non-standard variations of SEG-Y and IEEE
format. SEG-Y Output is a good choice for archiving a dataset that will
later be loaded to a third party software package. This process will
successfully archive data spanning over multiple disks. One downfall to
this archival method is that it will not automatically map all the
ProMAX trace headers. However, SEG-Y Output provides you the
capability of manually mapping these non-standard trace headers.
In this exercise, you will write a SEG-Y formatted tape, mapping some
of the non-standard SEG-Y headers. We will check to make sure the
headers were mapped correctly by using SEG-Y Input and Trace
Display.
1. Build the following flow, SEG-Y Output in Your Name Project,

Salt 3D - extraction Subproject:
2. Disk Data Input parameters.
Select to read just the first two shots from your "03 Shots - with
geometry" dataset.
We are limiting the dataset size for efficiency and to save disk space..

3. SEG-Y Output parameters.
Select Disk for type of storage--we will be using a Disk file instead
of Tape. Enter the DISK file path name according to your
instructor’s directions. Select Yes to Remap SEG-Y headers. Use
the default remapping values to map the header values for sou_sloc
and srf_sloc.
The SEG-Y format reserves bytes 181-240 for optional use. The
*_sloc trace headers are important to ProMAX so we typically write
them to the extended headers. These header values must be present
in order to automatically rebuild the database files with the Extract
Database Files process..
5. Once the job is complete, edit your flow to QC the traces and
headers written to the disk image file.
6. SEG-Y Input parameters.
Select Disk for type of storage and the same path and filename you
used for SEG-Y Output. Choose to remap headers, and use the
defaults for sou_sloc and srf_sloc.
8. Use the Header tool icon in Trace Display to QC the headers.
The extended header values should be preserved (sou_sloc and

srf_sloc).

Tape Data Ouput
Tape Data Output writes seismic traces to tape in ProMAX format. This
process is ideal for archiving a dataset to be used later in ProMAX since
it automatically preserves all trace headers, the CIND, and CMAP files.
Like SEG-Y Output, Tape Data Output will archive datasets spanning
multiple disks.
While we will not complete an exercise using Tape Data Output, you
should be aware of its benefits for archiving data.

Archive Wizard
The SEG output formats and ProMAX Tape Output only operate on
seismic trace files. Starting with the 5000.0 release SeisSpace offers
a process called the Archive Wizard which writes entire Areas or
Lines to tape. the Tape Wizard offer the ability to span tape volumes
and utilizes SeisSpace and JavaSeis secondary storage system.
The Archive Wizard also checks for available disk space before
writing files. You have the option to skip trace data files when you
archive or restore data. .
The following demonstrates the use of the Archive Wizard. Follow

your instructor’s directions on which areas or lines can be archived
and which tape device to use. (In this training class we will archive
to and from a disk file, not a tape device.)
This procedure archives everything necessary to move your data and

all associated processing to another machine. This includes all of
the database, tables, flows and if requested datasets.
The easiest way to learn this is to go to the Help pulldown menu at

the top of the Navigator and choose the Content and Index option.
Go to the SeisSpace Users Guide and choose Archive and Restore
on the second page of the index.
There is a thorough discussion and examples in the help file.
Once we have worked through the help file, we will step through an
archive and restore using our 2D Marine line.


Chapter 6
De-multiple Techniques
In order to produce the best time migration as well as to gain the maximum benefit from prestack
depth migration, careful preparation of the prestack time data is required. Multiple removal is
especially important and something that can be addressed early in the time processing sequence.
This will ensure a more accurate time image and a more accurate estimation of interval velocities
from pre-stack depth migrated data.
Topics covered in this chapter
o Radon Analysis and Filter

o Radon Velocity Filter
o F-K Multiple Attenuation

Chapter 6: De-multiple Techniques
Interactive Radon Analysis and Filtering
Interactive Radon/Tau-P Analysis and Radon Filter transform seismic

data into a domain where multiples and primaries are readily
distinguishable and can be separated. This separation allows multiple
energy to be easily removed prior to transforming the data back into T-
X domain.
Interactive Radon/Tau-P Analysis and Radon Filter model input data

using the Radon transform. The Radon transform models the original
data along a range of lines, parabolas, or hyperbolas. For multiple
attenuation, the parabolic transform is used since multiples after NMO
correction with primary velocities most closely approximate parabolas
rather than hyperbolas. In Radon Analysis, the modeled data is
displayed in time-moveout space, and primaries and multiples appear as
points rather than lines. Multiples can therefore be easily separated from
NMO corrected primary energy. Once separated, the modeled multiple
energy can then be subtracted from the input data with Radon Filter.
Since multiples and primaries are completely separated in Radon space,

this filter is still effective when primaries and multiples are co-incident
at near offsets in T-X domain. However, since separation of multiples
from primaries is based on event curvature, Radon Filtering should only
be run on gathers that carry no structural information (CDP gathers).
Input Data Requirements

• CDP gathers (with most complete processing applied).
• NMO corrected at primary velocity.
• Greater than 30 ms moveout difference between NMO corrected

primary and multiple.
• Can be used with irregular geometries (asymmetric cable).
Processing Requirements
• Number of modeling parabolas used in the Radon transform should
be calculated using 2 parabolas/Hz, at the maximum frequency of
the data, over the total delta-t range at a reference offset.

• The "minimum and maximum P-values" define the delta-t range at

a reference offset.
Generate a synthetic CDP gather

In this exercise, you will generate a synthetic CDP gather with multiples
and NMO corrected primaries. You will generate a 60 trace CDP gather
(50 ft. trace spacing) with the following events:
Primary 1: time = 800, velocity=3000
Multiple 1: time = 1000, velocity = 1500
Primary 2: time = 1500, velocity = 3000
Multiple 2: time = 1500, velocity = 1500

1. Create the following a flow called Radon 01: Analyze input in the
"Your Name" Project - 2D Marine Line SubProject:
2. In Synthetic Trc Generation, the zero offset times and the velocities
for the events to model are specified in the EMACS widget window
under "Define ORMSBY synthetic seismic events".
Designate the wavelet type as 2, which is a reflector (1 indicates a

refractor). A description of the other parameters is given in the

section below the parameters. You can type the information or you
can use File -> Import->../misc_files/Radon01.txt.
3. In Normal Moveout Correction, say No to "Get velocities from the

database?" and hand enter the primary velocity (3000 meters/sec).
Since the velocity is a constant you only need to enter it once at
time 0.0.
4. In Trace Display set SCALAR to 3.0 so that amplitudes before and

after filtering can be compared. Change the labeling to CDP and
Offset.

Synthetic CDP gather NMO corrected at Primary Velocity
Make a note of the following items:
• the maximum amount of residual moveout (in ms) on the

multiples.
• the offset at the maximum residual moveout (this is usually the

maximum offset).
You will need this information in the next exercise.
Run Interactive Radon/Tau-P Analysis on synthetic CDP gather

In this exercise, you will run Radon Analysis on the same synthetic
gather that you displayed in the previous exercise.
Radon Analysis models the input gather using the Radon transform.
Since multiples after NMO correction with primary velocities most
closely approximate parabolas rather than hyperbolas, the parabolic
transform is used for multiple attenuation. In Interactive Radon/Tau-P
Analysis, the modeled data is displayed in time-moveout space, and

primaries and multiples appear as points rather than lines. Multiples can
therefore be easily separated from NMO corrected primary energy. You
will pick a top mute in the time-moveout display that "mutes" the
multiples.
You will use the maximum residual moveout and the offset noted in the
previous exercise to set parameters in Radon Analysis.
1. Copy Radon 01: Analyze input to Radon 02: Radon analysis flow
and edit as follows:
2. We have to add the Trace Header Math to add the Aoffset header
and Inline Sort to CDP/Aoffset since Interactive Radon/Tau-P
requires the data be sorted by CDP/Aoffset.
3. In Radon Analysis, the Number of P-values refers to the number of

parabolas the Radon transform should use to model the input data.
In order to calculate this value, you need to specify 4 other menu

parameters first:

• Minimum P-value of interest (ms)

• Maximum P-value of interest (ms)
• Maximum frequency of interest
• Reference offset for delta moveout
The minimum and maximum P-values define a delta-time range at a

reference offset. The reference offset is usually the maximum offset.
on the gather.
For every zero-offset sample of input data, Radon transform will

model all offsets of the input along a fan of parabolic curves. The
width of this fan is specified by the delta-t range at the reference
offset. Therefore, the delta-t range is the positive (overcorrection)
and negative (undercorrection) residual moveout range necessary to
encompass all possible instances of primary and multiple for a given
zero-offset time. If you noted 150 ms as the maximum residual
moveout of your multiples at the maximum offset in the previous
exercise, then set the maximum P-value to something larger than 150
ms. In this case, 250 ms was used. If you noted that the NMO
corrected primaries are overcorrected by a certain amount, then set
the minimum P-value to some larger negative value than the amount
of overcorrection. In this case, -100 ms was used.
The minimum and maximum P-values of -100 ms and 250 ms define

a total delta-t range of 350 ms.
The reference offset for delta moveout is the maximum offset, 1200
meters.
The maximum frequency of the data is 50 Hz.
You can now calculate the total number of P-values or parabolas to

sufficiently model the input data. One recommendation is to use 2
parabolas/cycle or 2 parabolas/Hz.
If the input data has a maximum frequency of 50 Hz:
2 parabolas/cycle * 50 cycles/second = 100 parabolas/second
If the total delta-t = 300 ms:
100 parabolas/1000 ms * 300 ms = 30 parabolas
Therefore, the maximum number of P-values for this data should be

30. However, since Interactive Radon/Tau-P cannot set the number

of traces/ensemble to less than the incoming ensembles, set the

number of P-values to 60.
5. Once the display appears, select View Scaling

Optins .Tau-P Panel.
6. Set the Gain to .1 and click OK.
Locate MOVEOUT=0, this will be the location of your primaries.
Interactive Radon Analysis display of synthetic CDP gather
Note that the primaries (at 800 ms and 1500 ms zero-offset times)
appear along MOVEOUT=0. The multiples (at 1000 ms and 1500
ms zero-offset times) appear at their respective residual moveout
values.
7. In the Radon Analysis display, pick a top mute that passes between
the primaries and the multiples.

This mute is usually picked at a minimum of 20-50 ms MOVEOUT,

since Radon Filtering is most effective on data with RMO of 30 ms
or more.
Use the Paintbrush icon to QC your mute. Your Radon display

should only display the primaries.
Once you have saved the mute, we will use it in Radon Filter to apply
the filter in a batch mode and output a dataset with Radon Filter
applied.
Top Mute to mute off Multiples
However, the closer the mute lies to the primary, the more the
primary amplitudes will be affected. Move the mute so that is not
as close to the primaries. Use the Paint brush to reapply the mute.
There should be a subtle change in the amplitude of the primaries as
the mute is moved either closer or farther from the primaries.
8. Select File Save Picks and File Exit/Stop Flow.

Run Radon Filter on synthetic CDP gather

In this exercise, you will run 3 versions of Radon Filter: one to output
the modeled data only, and 2 more to output 2 versions of filtered data.
The filtered output is the input data minus the modeled multiples. You
will also display the original input gather for comparison.
1. Copy the previous flow to make the following flow, Radon 03:
Radon Filter:
2. In Radon Filter, use exactly the same P-value and offset parameters
that you used in the Interactive Radon/tau-P Analysis.
In the first Radon Filter, choose to "Pass the modeled data" and do
not mute the data in the radon domain. This will output the fully
modeled data, including both primaries and multiples.
In the second Radon Filter, choose to "Modeled" and Top mute the
data in the radon domain. This will remove the multiples from the

input data. In the third Radon Filter choose "Subtract". This will
remove the primaries from the input data
First and Second Radon Filter

.

Compare the filtered primary amplitudes of both filtered outputs to

the original amplitudes. Note that the closer the mute was to the
primaries in Radon space, the more the primary amplitudes are
affected. Also compare the effectiveness of the multiple removal on
both filtered outputs.
Synthetic CDP and output from Radon Filters

Display "real" marine CDP gathers

Now that you are familiar with what to look for on your input data and
how to parameterize Radon Analysis and Filter, apply the same
technique to real marine data.
In this exercise, you will display NMO corrected CDP gathers and
estimate the amount of differential moveout at the maximum offset.
1. Open the following flow, Radon 04: Marine CDPs:
2. Read the Shots with decon by CDP and Aoffset, CDPs 100-
600(100). Set Trace Display to plot 6 ensembles

Marine CDP gathers NMO corrected with Primary velocities
Make note of:
• the maximum offset.

• the amount of residual moveout on the multiples at the
maximum offset..
• the zero offset times of key multiples and primaries.
4. Exit the Trace Display flow.
Run Radon Analysis on marine CDP gathers

In this exercise, parameterize Radon Analysis, generate the display, and
pick a top mute. Note the following background information and hints:
• This data was filtered to 5-65 Hz.
• Enter the delta-t range (P-value range) sufficient to include the

slowest multiples.

• Calculate the number of P-values based on the maximum

frequency: 2 parabolas/cycle * 60 cycles/second = 120 parabolas/
second.
• If you use -50 and +350 as the delta-t range, then: 120 parabolas/
1000 ms * 400 ms = 48 parabolas.
• Input 2000 meters as the reference offset.
1. Edit your Radon 04: marine CDPs flow:
3. When the Interactive Tau-P/Radon Analysis display appears, adjust

the display parameters to enhance the visibility of the multiples.
Select View Scaling Options Tau-P Panel. Change

Scaling to Conventional and Individual, change Gain to 0.7. Click on
OK.

Radon Analysis of marine CDP gathers
4. Pick a Top Mute that will remove the multiples from this display.
Click on the PaintBrush icon to remove the multiples in the display.
Move to the next CDP.
Because the multiple energy in this dataset is so strong, it is likely

that the primary velocities used to NMO correct the data are
somewhat in error. Since slower velocities exhibit greater moveout,

any error in the velocities will produce greater residual moveout on

the shallow primaries than on the deeper primaries.
5. Select File Save Picks and File Exit/Stop Flow.
Run Radon Filter on marine CDP gathers

Use the Radon Analysis parameters and your top mute file in Radon
Filter.

1. Copy flow 10: Final Stack to Radon 05: Stack with Radon:
2. In the Radon Filter, make sure the parameters exactly match the
parameters you used in Interactive Radon/Tau-P Analysis.
1. Create a new flow, Radon 06: Compare stacks:

2. Input the Final Stack and Final Stack with Radon in Disk Data
Input and Insert, using After. Put 2 Panels in Trace Display and
Zoom up to a similar time frame as the display below.
Radon Filtered Stack Comparison
3. You may want to go back to Radon Analysis, re-pick a more severe

top mute and then re-run this flow to see the effect.
OPTIONAL: Test parabolic vs. hyperbolic transform

This exercise will test the number of gates used and parabolic vs.
hyperbolic Radon transform.
At shallow times, multiples corrected with primary velocity

approximate parabolas. At deeper times, multiples corrected with
primary velocity approximate hyperbolas.

Radon Velocity Filter
Radon Velocity Filter is a special version of Radon Filter. It utilizes the

same principles as Radon Filter, but does not require Interactive Radon/
Tau-P Analysis or picking a top mute in Radon space. Input data
requirements remain the same: CDP gathers NMO corrected at primary
velocities. Radon Velocity Filter can provide NMO capability within
the program. Required filter parameters are:
• a number of P-values necessary to model the input data,

• a reference offset, and
• a velocity percentage above and below the primary velocities. Data
inside this range of velocities will be considered primaries; data
outside this range will be considered multiples.
The program will automatically mute the data in Radon space at 10 %

above and below the primary velocity range specified. While initial
visual analysis of the CDP gathers is still necessary, Radon Velocity
Filter may be easier to test and implement in some data cases.
Generate a synthetic CDP gather and analyze moveout

In this exercise, you will generate the same synthetic gather as you did
for Radon Filter. You will generate an uncorrected and an NMO
corrected version. In Trace Display, you will use the dx/dt tool on the
uncorrected gather to get a range of velocities above and below the
primary velocity within which you want to preserve data. This velocity
range will then be used to calculate a +/- velocity percentage range
outside of which data will be filtered by Radon Velocity Filter. On the
NMO corrected gather, you will determine the number of P-values.
1. Copy the flow Radon 03: Radon Filter to Radon 07: Radon Vel
Filter:
2. Replace the first Radon Filter with Radon Velocity Filter. Change
the Trace Display label.


Synthetic CDP with NMO correction at Primary Velocities
4. You can still see some multiple energy using the Radon Velocity
Filter. You can rerun the flow with a tighter velocity percentage to
see the change in the amplitudes.
5. Exit this Trace Display.
6. In Radon Velocity Filter, note that a delta-t range (P-value range) or

a mute file are not requested.
Note also that NMO can be performed within Radon Velocity Filter.
Therefore, your input gathers do not need to have NMO already
applied.

Interactive FK Analysis and Filtering
Interactive FK Analysis and FK Filter transform seismic data into athe

FK domain where multiples, primaries and other seismic events are
readily distinguishable and can be separated. This separation allows
multiple energy or ground roll to be easily removed prior to
transforming the data back into T-X domain.
FK requires that the input traces be equally spaced. Also, since events
that arrive at the same time with the same slope will overlap, FK Filter
is not as effective in removing multiples as Radon Filter on the near
traces.
We will use a synthetic example to show how to design and use an FK

filter.
Input Data Requirements

• Shot or CDP gathers (we will use CDP gathers).
• NMO corrected at primary velocity.
• Traces equally sampled in the spacial domain.

1. .Copy the flow called Radon 01: Analyze input to FK 01: Analyze
input:
2. The Synthetic Trc Generation is changed so that the traces are now
40 meters apart and the first offset is -1200 meters making a split
spread CDP.
3. Additive Noise and Spikes is used to add ground roll to the

synthetic.
4. The CDP has NMO applied to make it more obvious where the
primaries will be (along the k=0 axis).

Run Interactive FK Analysis on synthetic CDP gather

1. Copy the FK 01: Analyze input to FK 02: FK Analysis:
2. Set the FK Analysis panel width to 60, set the trace spacing to 40.0
meters and set the Starting Display configuration to TX-FK.
Define a new mute polygon to store the mute we will design. This
mute will remove the ground roll from the CDP record.

4. Click on the Picking Icon and design a polygon to surround the

ground roll. You may want to zoom the FK display first.
5. Design the polygon around the ground roll.

Synthetic CDP gather NMO corrected - FK Analysis with Polygon
6. Click on the FilterResponse -> Filtered Output to see the data

with the FK Filter applied.
Synthetic CDP gather NMO corrected - FK Analysis with Polygon Applied

7. Once you have the polygon you want, Exit -> Stop the flow and
save your polygon.
Run FK Filter on synthetic CDP gather

1. Copy FK 02: FK Analysis to FK 03: FK filter:
2. Change the first parameter from Fan Filters to Aribrary Polygon.

Set the correct values in FK Filter.
3. Change Trace Display to display 2 ensembles and set the scaling to

Entire Screen and a Scalar value to .2

Synthetic CDP gather NMO corrected - with and without FK Filter

Chapter 7
Plotting
This chapter discusses creating and plotting a CGM+ plot file.We will assume that you have the
proper software and licenses for viewing and plotting CGM+ plotfiles. Two different methods will
be covered for creating plots. The first is a quick and easy method to create plots, the second is an
optional, more robust method.
o Creating a CGM+ file

o Viewing, and Plotting a CGM+ File

Chapter 7: Plotting
Creating, Viewing, and Plotting a CGM+ File
The first step in creating a final plot is to input your data into the Create
CGM+ Plotfile process. The menu for this process is split into three
sections (see figure). In the top section you will change some of the
global parameters for the plot. These include CDP range for a stack
section, units and font sizes. You can also choose your plot direction,
depending on how you input the leftmost and rightmost CDPs.
Top
Section
Middle
Section
Bottom
Section
Creating CGM+ plotfile
Near the end of the top section, you select a specific submenu to view.
This option controls a set of dynamic submenus which are selected one
at a time. Once you are familiar with the process, the normal sequence
would be to start by selecting the first option, Traces/Plots/Posts/
Graphs, and work your way down the list of submenus. When you select
a different submenu to view, the lower two sections of the menu change
allowing you fill in the appropriate selections.

Chapter 7: Plotting
Creating a CGM+ Plotfile

1. Copy the 2D tutorial line to a new area for your use following the
instructions given below.
Note that this step may not be necessary if you have already copied
the tutorial line during a previous exercise.
1. Create a new Area for 2D lines, using your name in the description
i.e. Bob’s 2d area. In the new area, copy the the “tutor2d - watson
rise” line from the 2D tutorials area. Name the new line anything you
want.
2. Run the flows, 01b - load geom to headers, 04 - compute elevation

statics, 04a - pre processing, and 06 - initial stack to create a stack
dataset for use in this plotting exercise.
3. Build the following flow to create a CGM+ file of the initial stack..
Editing Flow: 32 - Plotting
Disk Data Input

Select dataset---------------------------------------------Stack - Initial
Trace read option: ----------------------------------------------Get All
Bandpass Filter
Ormsby filter frequency values: ---------------------------3-6-60-70
AGC operator length: --------------------------------------------500
Create CGM+ Plotfile
Plot File Name: -----------------------------------------------cgmplot
-----Edit the remaining parameters as described below-----
>Create CGM+ Montage SDI<
>Plot CGM+ Plotfiles*<
4. In Disk Data Input, input the initial stack.
5. Select reasonable parameters for the Bandpass filter and AGC.
6. Default the parameters in the top section of the Create CGM+

Plotfile menu.

Chapter 7: Plotting
7. Select Traces/Plots/Posts/Graphs as submenu to view.
This option allows you to set the parameters for the trace data, as
well as display plots of database entries, and trace headers above and
below the trace data.
The bottom portion of this menu is dependent on what is defined by

the Component List in the middle section of the menu. At this point
the View and >Primary Trace Data< are highlighted.
8. Select parameters in the bottom section of the menu to define your

display.
Type in 24 for trace spacing, 2.5 for time scale, and default the
remaining parameters.
9. Label the CDP numbers below (after) the trace data.
Select the Add After option in the middle section of the menu. The
bottom section disappears, the Add After and Primary Trace data are
highlighted, and a menu to choose Component Type appears.
A component type of Post will label traces at a user specified

interval, Plot will place a symbol at each value, and Graph will
connect values with a continuous line.
10. Select Post for Component type, and CDP from the list of Attribute
types that appears.

Chapter 7: Plotting
A submenu in the bottom section appears. You can make

modifications to how the CDPs will be displayed. For CDP’s to
annotate, select 25-10000(25).
11. Post the stacking velocities above (before) the trace data.
Click on Primary Trace Data in the middle section, then select Insert
Before.
12. Select Post for Component type, and Vel for attribute type.
A submenu appears in the bottom section where you can specify

parameters for display of the velocities.
Click on Invalid to select a velocity function from the database.
Select Yes to Post interval velocity.
13. From Submenu to view in the top section, select Title Box Text.
This controls the side label’s title text and font sizes.

Chapter 7: Plotting
Select an item in the Titlebox Item List. You can change this item on
the Editable Title Item Text line.
14. From Submenu to view in the top section, select Field Parameter
Text.
This menu allows you to input field data information.
15. Select Date Recorded on the Editable Field Text line to edit the
field data.
Type in values in the Emacs window, or read in a file by typing the

path and file name on first line of the Emacs window, and pressing
Ctrl-r.
16. From Submenu to view in the top section, select Processing

Sequence Text.
You can input your own processing sequence, or create one out of
the ProMAX processing history information.
17. Select Processing Sequence Options and choose “Create Processing

Sequence in CGM+ History View Session” from the popup
window.
If you had previously saved a side label in the Dataset History

Viewer, you could select Get Processing Sequence saved in Dataset
History View Session. Side label are stored in the label_sequence.txt
file in the Area/Line directory.

Chapter 7: Plotting
19. Create side label during execution.
Edit flow selected in Flow Chart

Processing
Flow Chart
Current Side Label
The CGM+ History View Session window is split up into three

sections. The section to the right is a chart of your processing flows.
The upper left section is where you may choose whether specific
processes and parameters within a flow will reside in your side label.
The lower left section displays the current side label.
By default, the side label is nearly built. You can use MB2 or MB3
to select a flow box in the right hand section in order to toggle it in/
out to your side label. Use the mouse button helps to guide you.
ProMAX has default parameters for each process that are

automatically included in the side label. If you prefer to add or
remove certain of these parameters, click on the flow box in
question. This displays the flow in upper left corner of the screen

Chapter 7: Plotting
where you can toggle parameters black to include them in the side
label and toggle them gray to exclude. Use the mouse button helps.
20. Once you have the information you want included in the processing
history, click on Label Save (side label is stored in the
label_sequence.txt file in the Area/Line/Flow directory) and then
Exit.
21. Edit the side label you have just saved.
Select Processing Sequence text for submenu to view, then select

Get Processing Sequence saved in CGM+ History View Session in
Processing Sequence Options.
Select the line labeled Processing Sequence Text to modify the side
label. Edit the side label that you saved in the history viewer. You
may want to remove the flow names, blank lines, etc.
This creates the plotfile, and names it cgmplot.cgm, or whatever you

entered for the Plot File Name.
Viewing and Plotting CGM+ plotfiles

You will generally want to view your CGM file on screen, before
plotting to paper. This exercise describes how to do this using software
from SDI. You may have different software at your office.
1. Edit the flow to view your plot prior to plotting:
Editing Flow: 10: Plotting
>Disk Data Input<

>Bandpass Filter<
>Automatic Gain Control<
>Create CGM+ Plotfile<
Create CGM+ Montage SDI
Plot File Name ------------------------------------------------cgmplot
>Plot CGM+ Plotfiles*<
2. Toggle all processes inactive except Create CGM+ Montage SDI.

Chapter 7: Plotting
3. Enter your plot file name.
4. Execute flow
View your CGM+ file using the scroll bars, and Zoom option.
5. Plot your CGM+ file:
>Disk Data Input

>Create CGM+ Plotfile
>View CGM+ Plotfile SDI<
>Create CGM+ Montage SDI<
Plot CGM+ Plotfiles*
Plot File Name --------------------------------------------------cgmplot
Plot Software to Use: -----------------------------------------------SDI
Use new or old SDI version?: ----------------------------------Server
Interactive or batch plotting?: ----------------------------interactive
Delete cgm file after plotting?--------------------------------------yes
6. Enter your plot file name.

Chapter 7: Plotting
Using Unisec to create plots
1. Build the following flow. You may want to copy the previous flow to
save time..
Editing Flow: 32a: Unisec Plotting
Disk Data Input

Select dataset:---------------------------------------------stack - initial
Trace read option:-----------------------------------------------Get All
Bandpass Filter
Ormsby filter frequency values:----------------------------3-6-60-70
AGC operator length:-----------------------------------------------500
Disk Data Output
Output Dataset Filename:-------------------------stack - for plotting
Build Unisec Parmfile*
Edit Existing .par file?:-----------------------------------------------No
UNISEC Template filename :----------------Instructor will Provide
(&PROMAX_HOME/port/misc/unisec/stack1.par*)
Parameter File name:------------------------------------------cgmplot
Spatial Domain of Plot:--------------------------------------------CDP
Leftmost CDP:--------------------------------------------------------775
Rightmost CDP:------------------------------------------------------989
Domain annotation interval:-----------------------------------------25
Plotting Units:----------------------------------------------------Inches
Trace space (traces/plot unit):---------------------------------------24
Time Scale (plot units / sec)-----------------------------------------2.5
Edit the UNISEC parameter file?:----------------------------------No
----See next page for remaining parameters----
>UNISEC Create CGM+*<

Chapter 7: Plotting
2. Click REPLACE on the Editable Field Text line.
This opens an Emacs widgit where acquisition parameters may be

entered. Enter appropriate information . Move the cursor out of the
widgit box to close.
3. Click Add After and then your line name in the Titlebox Item List.
Two new lines appear. On the Editable Title Item Text line, enter My
Test Plot. The new plot title is appended to the Titlebox Item Text.
4. Default the remaining parameters.
Create a UNISEC CGM+ Plot file

The UNISEC Create CGM+* standalone process allows you to add
additional information to your plot file and view the plot prior to
generating a hard copy. Velocity analysis can be added to the display
and database values such as elevations or trace fold can be graphed on
the section. A comprehensive processing history can also be generated
and added to the side label in this step.

Chapter 7: Plotting
1. Build the following flow to create a CGM+ file of your stack and
interactively view the results before plotting.
>Build Unisec Parmfile*<

UNISEC Create CGM+*
UNISEC parameter filename:--------------------------------cgmplot
Display processing history?:-------------------------------------None
Get velocities form the database?:--------------------------------Yes
Select Velocity parameter file:---------------Single Brute Function
Edit the UNISEC parameter file?:---------------------------------Yes
Prefered editor----------------------------------------------------emacs
SELECT Seismic dataset:-------------------------stack - for plotting
Trace read option:---------------------------------------------get all
Remap SEGY trace header values for seismic?:-------Yes
Header value to label/profile:-----------------------TR_FOLD
Is there a color overlay dataset?:-----------------------------No
Change trace length?:---------------------------------------------No
Resample input data for display?:---------------------------No
Load trace header values form database?:------------Yes
Number of parameters:---------------------------------------------2
1st database parameter:----------CDP GEOMETRY FOLD
1st header entry:------------------------------------------TR_FOLD
2nd database parameter:-----SIN GEOMETRY SOURCE
2nd header entry:-------------------------------------------------SIN
Headers to profile:----------------------------------------TR_FOLD
Choose profile extents to set:-------------------------TR_FOLD
---Default Minimum and Maximum values to annotate--
Headers to label:---------------------------------------------------SIN
Annotation interval:------------------------------------------------50
View the CGM plotfile interactively?:----------------------Yes
Location of CGM+ Viewer:-----------Instructor will provide
---- Default the remaining parameters----

Chapter 7: Plotting
The resulting display allows you to check the contents of the

section’s side label and placement of velocity and display
information before you create a plot.
Plotting CGM+ plotfiles.

1. Edit the flow to generate your plo:t.
>Build Unisec Parmfile*<

>UNISEC Create CGM+*<
Plot CGM+ Plotfiles*
Plot File Name:------------------------------------------------cgmplot
Plot Software to use:-------------------------------------------Larson
Select active plotter-----------------------------------------plotter1
Plotter host name------------------------------sparky.denver.lgc.com
Delete cgm file after plotting-------------------------------------yes
2. Toggle all processes inactive except Plot CGM+ Plotfiles.
3. Enter your plot file name and select the plotter and host.
4. Execute flow

Chapter 7: Plotting

Chapter 8
First Break Picking
Artificial neural networks have had excellent results solving pattern recognition problems. First
break picking, trace editing, and reversed trace selection, typically tedious processing steps, are
all pattern recognition problems and lend themselves to the application of neural networks.
For First-break picking and trace editing, ProMAX uses a Cascade-Correlation Learning
Architecture. Advantages of this algorithm include decreased network learning time and the
ability to incrementally add to an existing network. The neural network compares various
attributes of the correct pick to other possible picks within a window. The network recognizes the
ability of an attribute to predict the correct pick and accordingly weights the network connection
to that attribute.
This tutorial flow is divided into 3 parts. The first part is for training the neural network, the
second part is for batch picking all shots. The third part is using the other picking module in
SeisSpace, FB Picking.
o Interactive Neural Network (NN) First Break Training/Picking

o Batch Neural Network (NN) First Break Picking
o First Break Picking

Chapter 8: First Break Picking
Interactive NN First Break Training/Picking
The first break picker in Trace Display gives you the opportunity to
interactively create and train a neural network to pick first breaks. You
will manually pick some first breaks and use these picks to train a neural
network. The neural network will then try to pick first breaks on selected
shots, and you can QC these picks using Trace Display.
Prepare a 2D line for nn picking.
NOTE:
The NN First Break Picker menu in Trace Display only appears if geometry is
defined, and your dataset matches the database. You can check if geometry matches
the database via MB3-> Properties on the dataset in the Dataset listing in the
Navigator.
Interactive Training
1. Go to “Your Name” Project and Salt 3D - extraction Subproject.
Create a new flow 08c - FB picking.
2. Input shots (SIN) 100-2000(300) with Interactive Data Access set

to YES, use the kill traces from flow 08 - Preprocessing that
removes the bad shots (not the ones that use Trace Statistics). Do
not apply Trace Muting.

3. Execute the flow to begin the NN sequence.
Run Trace Display
“Train” the Neural Network

Trace Display -> FirstBreakPicker ->
Set Neural Network Parameters
Create Training Dataset
Create a new time gate parameter file
Pick or edit a set of good picks to store in “FB Training Data”
Pick or edit the time gate centered on the “FB Training Data”
Neural Net Training
Create a new NN weight table (e.g., “fb_weight”)
or, if continuing “Training”,
Use the existing NN weight table
Use Neural Network to make FB picks

Trace Display -> FirstBreakPicker ->
Neural Net Recall -> One time Recall
Create a new OPF parameter file (e.g., “test nn picks”)
Trace Display ->

FirstBreakPicker ->
NO
Purge Neural Net Are the NN picks good?
Delete (MB2) “test nn picks”
YES
Do you want to continue to YES Go to

next
“Train” the Neural Network? gather
NO
Use Neural Network to pick every shot
Interactive NN FB picking Batch NN FB picking

Trace Display -> FirstBreakPicker -> Exit Trace Display
Neural Net Recall -> Continuous Recall Run NN First Break Picker
Run Trace Display
QC and Edit the NN FB picks on every shot

4. Zoom in on SIN 100
5. From the main Trace Display menu bar, select

FirstBreakPicker Set Neural Network Parameters. The
following menu will appear.
Select the pick polarity and the signal/noise gate length. The neural
network works well with peaks and a gate length of 100 ms. Select
OK to accept these parameters. The neural network itself, however,
may key off of instantaneous phase/frequency, amplitude before or
after the first break, or any other pattern it can recognize.

6. From the main menu bar, select FirstBreakPicker Create

Training Data set. Create a new gate “nn gate”. Take Aoffset as the
secondary key for interpolationl.
The Picking tool icon appears on the left side of the display. There
will be two entries in the Pick Layers box: “FB Training Data” and
the “nn gate.”
7. Select the “nn gate” table from the Pick Layers window, and
edit the top of the gate. Click MB3 -> New Layer to pick the
bottom of the gate. Move through the rest of the shots to make sure
the gate surrounds the first breaks. Edit the top and bottom of the
gate as necessary. If you have IDA set to Yes, you can move back
and forth to check/edit nn-gate.
Do not make a pick on every trace, as the gate is interpolated

between picks. The network tries to follow the slope of the top gate
when picking first breaks, so it is necessary that the top gate closely
follows the trend of the first breaks. Usually picking about 25ms
above the first break, at timing line intersection works quite well.
The gate should contain at least three to five peaks.

8. Click on FB Training Data in the Pick Layer window and

manually pick the first breaks using MB1.
Pick first breaks on 20-30 traces. Because training is interactive you

can incrementally train the network. This means you do not need
many picks to begin training, as more picks can be added in future
training runs. More picks means longer training time.
Use MB3 to select the Snap to peak option.

9. After picking, select FirstBreakPicker Neural Net

Training...
A First Break NN Training window appears, including a list of First

Break Weight Tables. Create a new table “wt1” and select OK. The
network will be trained using your picks. While the network is
training, the cursor will change from an arrow to a wristwatch. When
the cursor changes back to an arrow, training is complete.
10. From the menu bar, select FirstBreakPicker Neural Net

Recall One Time Recall.
The One time Recall option applies the neural network to the
currently displayed gather. A First Break NN Recall window
appears.

You will be prompted to either choose an Ordered Parameter

File(OPF) from the list, or create a new OPF for storing picks.
Create a new OPF called NN training picks for the name,

enter 3000 for the offset to start picking, and default all other
parameters. Select OK. The Neural Network is applied to the current
gather display. The results of the picking are displayed.
11. If the picks are bad, modify your FB Training Data and retrain the
network. It works better if you pick on both slopes of the first
breaks.The picks are usually off at the near offsets, but we will not
use the near offsets for refraction statics in this case.
To modify training picks, click on the Picking tool icon. Your new
table of picks appears in the Pick Layers window. Remove the table
from the list and activate the FB Training Data. Modify or add to
these training picks, select First Break NN Training, and use the
same weight table. Iterate through steps 6, 7, and 8 until you are
satisfied with the results. If you still cannot get satisfactory results,
try purging the Neural Network (FirstBreakPicker
PurgeNeuralNet) and starting over.
12. Set Neural Net Recall to Continuous and click the Next ensemble
icon to go to the next shot.
You can retrain if necessary, or if you think the picks are close
enough, select File Exit/Stop Flow, and choose to save edits
before exiting.
The weight table, and time gates are saved and can be used in the
batch NN First Break Picker process to pick the entire dataset.

Batch Neural Network First Break Picking
This step uses the neural network weight matrix to pick first breaks on
all shots. In the case of first-break picking, neural network picks are
stored in the ordered database and can be accessed for various uses
including refraction static analysis.
Pick First Breaks for entire survey

In the previous exercise, we interactively created and saved a fb_weight
matrix file, and a time gate. Now we will use these as input to the NN
First Break Picker to pick all shots in batch mode.
1. Alter the existing flow as follows:

2. In Disk Data Input, input your entire dataset.
Some preprocessing may be necessary, such as trace edits, filtering,

scaling. Preprocessing is the same as input to the interactive NN
First Break Pick Training.
3. Select NN First Break Picker parameters.
Data dependent parameter selections are based on testing or

experience. Parameters are consistent with those for the interactive
NN FB Pick Training.
Input the fb_weight matrix wt1 file.
You must specify a starting offset for the picker. Specify an offset
with good S/N and no shingling of refractors. For this data, an offset
value of about 3000 ft. is good.
5. Once the picker is completed, QC your picks.
Edit the same flow, and toggle “NN First Break Picker” inactive, and
“Trace Display” active, and execute the flow. From the menu bar in
the Trace Display window, select Picking Edit Database
Values (first breaks)... Select NN_PICK as the Infotype, and
PICK0001 (the 12345678 picks are from the interactive picker)
from the OPF File Selector, and use the same name to save edits.
Don’t spend too much time editing picks here. The easiest way to
view and edit your picks is to use the first break editing capabilities
of the Refraction Statics process in the next chapter. Also do not
worry about zero picks on the dead traces.
For this dataset, the NN Picker does not work as well as the First
Break Picking module. We will use that picker next.

First Break Picking
1. Alter the existing flow (08c - FB Picking) as follows:
2. Set Disk Data Input to Get All.
3. The First Break Picker is a batch module. We will use our nn-gate
for the gate and default all the other parameters. It turns out, even
though this data was acquired with a surface source that the
DYNAMITE option works better.

5. Alter the flow to display your picks in Trace Display.
To view your picks, in Trace Display, go to Picking -> Edit Database

Values (first breaks) -> TRC -> F_B_PICKS -> PICK0000
These picks are better than the NN picks and will be used in the
Refraction Statics Chapter.

Chapter 9
Coordinate-based Refraction Statics
This section covers the steps for calculating and applying refraction statics. First break picks are
required as input into this process.
The refraction statics processes expects R_STATIC and S_STATIC to be present in the database.
Once these attributes are in the database the refraction statics processes can fill them in with more
accurate static values than simple elevation static calculations. The recommended method to
create R_STATIC and S_STATIC database entries is to run the process Datum Statics
Calculation*, before running the refraction statics processes.
o Refraction Statics Calculation - coordinate based

o Apply Refraction Statics
o Stack with Refraction Statics

Chapter 9: Coordinate-based Refraction Statics
Coordinate-based Refraction Statics
ProMAX provides a coordinate-based refraction statics algorithm that

computes refractor velocities and delay times, a near-surface depth/
velocity model and travel-time corrections to the final datum from
offset and first break information. There is also an option to edit first
break pick files automatically. All of the preceding attributes are
written to the database. Multiple layer models can be created, and
refractor velocities and depths and velocities will be computed for each
layer. There are many advantages to using this technique:
• Very robust for noisy first break picks.

• Works independent of shooting geometry.
• First break picks are not required for every shot.
The main disadvantages are that there is not a graphical interface for
editing. The source and receiver static solutions are applied to the data
in a future step, Apply Refraction Statics.
NOTE:
First break times must be picked and written to the database prior
to this exercise. Please refer to the Neural Network First Break Picking
exercise earlier in this manual.
As a part of this exercise you will see that there are two ways to enter
the refractor offset ranges. These are:
• Manually.
• By picking a Pick Top Mute in Trace Display.
In this exercise you will use first-break pick times to calculate a near-
surface model and travel-time corrections. This process calculates shot
and receiver refraction statics to shift to the final datum and updates the
database. Results of this exercise will be used by Datum Statics Apply
in the next exercise.
1. IOpen the “Your Name” Project and Salt 3D - extraction

Subproject.

2. Create the flow 08d- Refraction statics as below:

3. Select Refraction Statics Calculation* parameters.
Select the first break time to use for the statics decomposition. These
time picks will be in the TRC OPF and will normally be of the type
F_B_PICK. Select the PICK0000 file created by First Break
Picking. Enter the number of layers to model, in this case use one
layer. The identification number will be 1 for the first run through the
process. The shooting geometry is 3D .
There are 5 steps to Refraction Statics Calculation* described in

the menu. They may all be turned on for refraction statics
computation or you may select to run one option at a time and view
the output in the database.

4. INPUT V0 and REFRACTOR OFFSET.
In this exercise we’ll input V0 and compute uphole times and

manually type in the refractor OFFSET range.
Three database entries are created in the SIN OPF:
SIN REFR_OFF OFFPSS11 ---Near positive offset of refractor.
SIN REFR_OFF OFFPSE11 ---Far positive offset of refractor.
SIN REFR_OFF OFFNGS11 ---Near negative offset of refractor.
SIN REFR_OFF OFFNGE11 ---Far negative offset of refractor.
SIN VELOCITY V0INIT11 ----Weathering Velocity.
These database attributes may be edited. The V0INIT11 is written

over each time you rerun the module. If you want to make a
permanent change, edit the uphole times.
5. Set the V0 values to 3500 ft/second for the “weathering layer”.
6. Set the refractor offsets to 1900-8000 feet. The picks on traces with
this offset range will be used to calculate the refraction statics.

7. COMPUTE REFRACTOR VELOCITIES.
With this subheading turned on a refractor velocity is calculated

based on the first break times and the offset range from the previous
step. Although you can smooth the velocity model in the menu, you
may wish to look at your model in the database before smoothing.
You could then either smooth in the database (Good to see
immediate results of smoothing), or define a smoother in the menu.
There is an option to edit the first break picks automatically by

setting a deviation from the median velocity described by the offsets.
If any picks deviate more than the selected amount they will be
killed, and set to NULL in a new first break picks database file TRC
F_B_PICK FBPEDITX, where X is the run identification number.
Only the good picks will be included in this file. Remember to
examine this edited file.
Set the Length of INITIAL velocity smoother to 11
Set the Edit First Break times (median Velocity)? to Yes and the
value to 15%
Three database entries are created.
CDP VELOCITY VCINIT11 -- CDP velocity for 1st refractor.
SIN VELOCITY VSINIT11 ----Source velocity for 1st refractor.
TRC F_B_PICK FBPEDIT1 ----Edited first break pick file.
These database attributes may be edited.
You can view these database entries using DBTools -> View -> 2D
MATRIX

CDP VELOCITY VCINIT11 with 11 point box smoother
COMPUTE DELAY TIMES.
Once CDP velocity is available, delay times for shots and receivers
may be computed. This is done by iteration, starting with source
delay time estimates, followed by receiver delay time estimates, and
(optionally) finalized by CDP velocity updating. Values are not
computed for any SIN, SRF or CDP that does not meet the minimum
fold (menu parameter) criterion. Once the decomposition is
complete for each refractor, these missing values are interpolated
based on X and Y.
Three database entries are created.
SIN DELAYTIM SDELAY11----Source Delay times.
SRF DELAYTIM RDELAY11--- Receiver delay times.
CDP VELOCITY VCFIN011---- Final CDP velocities.

8.
9. COMPUTE REFRACTOR DEPTH MODEL.
The depth model stage inputs delay times and refractor velocities in
CDP, interpolates refractor velocity into SIN and SRF, computes a
depth model for sources and another for receivers. Optionally, the
first refractor depth in SRF may be projected into CDP, smoothed,
projected back into SRF, V0 recomputed in SRF based on the
smoothed depths, new V0 projected from SRF to SIN, and finally
SIN and SRF depth models computed.
Six database entries are created.
SIN REFDEPTH SDEP_011---Source Refractor Depth.
SIN VELOCITY VSFIN011 -- Final Source velocity for 1st

refractor.
SIN VELOCITY V0FIN011 ---Final Weathering Velocity.
SRF REFDEPTH RDEP_011--Receiver Refractor Depth.

SRF VELOCITY VRFIN011- - Final Receiver velocity for 1st

refractor.
SRF VELOCITY V0FIN011 ---Final Weathering Velocity.
SRF VELOCITY VRFIN011

10. COMPUTE SOURCE AND RECEIVER STATICS.
The statics computation stage inputs refractor velocities and

refractor depths, computes source and receiver depths to the FINAL
datum of 800 feet and outputs static values. We have the choice of
inputting a constant velocity or the bottom refractor velocity. For
this exercise choose the refractor velocity.
Two database entries are created.
SRF GEOMETRY RSTAT00X --- Receiver statics.
SIN GEOMETRY SSTAT00X ----Source statics.
SRF GEOMETRY RSTAT001

Apply Refraction Statics
The Datum Statics Apply program uses refraction statics computed by

the Refraction Statics* or Refraction Statics Calculation* processes,
along with elevations from the database to compute NMO_STAT and
FNL_STAT. As with the previous methods, these header entries are
updated and the integer multiple of a sample period portion of
NMO_STAT is applied to the trace and the remainder is written to
NA_STAT to be applied later. If the option to process to a final datum
is selected, C_STATIC is set to zero. Recall: NMO_STAT = S_STATIC
+ R_STATIC + C_STATIC. Therefore, C_STATIC is zero,
NMO_STAT becomes the static shifting traces to the final datum, and
FNL_STAT is zero because your data will already be at the final datum.
It is important to note that the Datum Statics Apply process first checks
to see if other statics have been applied to the traces by an earlier
processing step. If statics are applied, Datum Statics Apply first removes
these statics returning the traces to their original recorded time
reference. Also, if previous statics contained any hand statics or shot
delay corrections, these statics are also removed and should be
reapplied.
The refraction statics to be applied must be calculated prior to running

Datum Statics Apply. Datum Statics Apply is generally executed in a
processing flow prior to velocity analysis. This process updates the
statics trace headers and applies the shifts to each trace.

Apply Refraction Statics to your data.

1. Copy the existing flow 10 - Initial stack to 10a - Refraction statics
stack:

2. Set the Datum Statics Apply parameters
NOTE:
We do not have to recalculate the datum statics (...C_STATIC...) unless you want to
change the smoother of N_DATUM, the datum elevation, or the replacement
velocity. Datum Statics Apply will back out the elevation statics before it applies
the refraction statics.
3. Apply the “imported from ascii” in NMO
4. Apply the “post NMO mute’ in Trace Muting.
5. Add a Trace Display Label.
6. Add a new output dataset 10a Stack - refraction
8. Build a flow to display gathers with refraction statics applied and

use the Header icon to check updated statics header entries.
9. Edit and execute flow 15 - Volume Comparison. Compare the

initial stack to the stack with refraction statics.


PM-SS SPA v2

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

PM-SS SPA v2

Hochgeladen von

Copyright:

Verfügbare Formate

SeisSpace

copyright © 2010 by Landmark Graphics Corporation

Part No. 162383 D April 2010

Halliburton | Landmark Software & Services

ProMAX Menu Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Flow Building and Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Additional Geometry Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Geometry Core Path Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Details of the Geometry Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Pre Geometry Database Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Landmark SeisSpace Seismic Processing and Analysis i

Inline Geometry Header Load after Pre Initialization . . . . . . . . . . . . . . . . . . 2-13

ProMAX Marine 3D Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3D Marine Geometry from UKOOA Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Assigning CDP Flex Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Expand Flex Binning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

3D Land Swath Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

3D Land Swath Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ii SeisSpace Seismic Processing and Analysis Landmark

Receivers Spreadsheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Archival Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

SEG-Y Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Tape Data Ouput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Archive Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

De-multiple Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Interactive Radon Analysis and Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Radon Velocity Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Landmark SeisSpace Seismic Processing and Analysis iii

Interactive FK Analysis and Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24

Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Creating, Viewing, and Plotting a CGM+ File . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Using Unisec to create plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

First Break Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Interactive NN First Break Training/Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Batch Neural Network First Break Picking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

First Break Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Coordinate-based Refraction Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Topics covered in this chapter: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Coordinate-based Refraction Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Apply Refraction Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

iv SeisSpace Seismic Processing and Analysis Landmark

Topics covered in this chapter:

o ProMAX Menu Map

Landmark ProMAX Seismic Processing and Analysis 1-1

ProMAX Menu Map

1-2 ProMAX Seismic Processing and Analysis Landmark

ProMAX is built upon a three level organizational model referred to as

Initiating a ProMAX session is done in a variety of ways. Typically your

A product name window appears, followed by the Area menu that

Landmark ProMAX Seismic Processing and Analysis 1-3

• Config: Brings up settings which control how lists of Areas,

1-4 ProMAX Seismic Processing and Analysis Landmark

• Option: Brings up settings for debugging, compression, use of

• Queue: Allows user to control batch processing queues.

• Exit: Will exit the User Interface, prompts to save if there is an

• Notification: Gives information about jobs, and allows user to

2. Select Add from the Area Menu with MB1.

3. Before moving the mouse, enter an Area name