ProMAX Seismic manual

ProMAX VSPUser Training Manual

copyright © 1999 by Landmark Graphics Corporation

Part No. 625321 Rev. B June 1999

Copyright © 1999 Landmark Graphics CorporationAll Rights Reserved Worldwide

This publication has been provided pursuant to an agreement containing restrictions on its use. Thepublication is also protected by Federal copyright law. No part of this publication may be copiedor distributed, transmitted, transcribed, stored in a retrieval system, or translated into any humanor 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:

Landmark Graphics Corporation15150 Memorial Drive, Houston, TX 77079, U.S.A.

Phone: 281-560-1000FAX: 281-560-1410

Trademark Notices

Landmark, OpenWorks, SeisWorks, ZAP!, PetroWorks, and StratWorks are registered trademarksof Landmark Graphics Corporation.

Pointing Dispatcher, Log Edit, Fast Track, SynTool, Contouring Assistant, TDQ, RAVE, 3DVI,SurfCube, SeisCube, VoxCube, Z-MAP Plus, ProMAX, ProMAX Prospector, ProMAX VSP,

MicroMAX, and Landmark Geo-dataWorks are trademarksof Landmark Graphics Corporation.

ORACLE is a registered trademark of Oracle Corporation.IBM is a registered trademark of International Business Machines, Inc.

AIMS is a trademark of GX Technology.Motif, OSF, and OSF/Motif are trademarks of Open Software Corporation.

UNIX is a registered trademark in the United States and other countries, licensed exclusivelythrough X/Open Company, Ltd.

SPARC and SPARCstation are registered trademarks of SPARC International.Solaris, Sun, and NFS are trademarks of SUN Microsystems.

X Window System is a registered trademark of X/Open Company, Ltd.SGI is a trademark of Silicon Graphics Incorporated.

All other brand or product names are trademarks or registered trademarks of their respectivecompanies or organizations.

Note

The information contained in this document is subject to change without notice and should not beconstrued as a commitment by Landmark Graphics Corporation. Landmark Graphics Corporationassumes 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

Landmark ProMAX VSP User Training Manual i

Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Agenda - Day 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i

Agenda Day 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Agenda Day 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

About The Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

How To Use The Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

ProMAX VSP System and Database Parameters . . . . . . . . . . 1-1

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

Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

ProMAX Data Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Program Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Ordered Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15

Parameter Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20

Disk Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24

Tape Datasets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28

Tape Catalog System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30

Flow Building and Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Contents

ii ProMAX VSP User Training Manual Landmark


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

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Building and Executing a Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Interactivity of Trace Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

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

Trace Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Create and Apply a Parameter Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Parameter Selection and Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1


Parameter Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

IF/ENDIF Conditional Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Interactive Spectral Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Real Dataset Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1


VSP Real Dataset Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Geometry Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

View Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Contents

Landmark ProMAX VSP User Training Manual iii


Display the Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Write Dataset To Disk in Your Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

VSP Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1


Assign VSP Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Quality Control Plots using the XDB database tool . . . . . . . . . . . . . . . . . . . . . 7-7

Load Geometry to the trace headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Keep Vertical Component Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1


Trap Vertical Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Output a file with vertical traces only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

First Break Picks on Vertical Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1


Pick First Breaks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

QC the First Breaks in the Database using XDB . . . . . . . . . . . . . . . . . . . . . . . . 9-4

VSP Velocity Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

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

Contents

iv ProMAX VSP User Training Manual Landmark

Generate Average Velocity vs. Depth and Smooth . . . . . . . . . . . . . . . . . . . . . 10-2

VSP True Amplitude Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1


True Amplitude Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Compute an RMS Velocity Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Test TAR Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

VSP Wave Field Separation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1


Flatten the Downgoing with F-B Picks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Flatten with F-B Picks and Event Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Compare Flattening Iterations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Wavefield Separation with Median Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

F-K Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13

Wavefield Separation with F-K Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

Wavefield Separation with Eigenvector (K-L) Filter . . . . . . . . . . . . . . . . . . 12-18

Wavefield Separation Comparison Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22

Save the Upgoing Energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24

Wavefield Separation to Keep Downgoing . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-26

Save the Downgoing Energy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28

QC plot of Separated Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30

Contents

Landmark ProMAX VSP User Training Manual v

VSP Deconvolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1


Picking the Decon Design Gate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Apply the mute for QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Deconvolution Filter Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Deconvolution Filter QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6

Deconvolution - Application to UpGoing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7

Spectral Analysis Before and After Decon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9

VSP Corridor Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1


Picking Corridor Mutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Apply the Corridor Mutes for QC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Produce the Corridor Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5

Splice the Corridor Stack into a Surface Stack. . . . . . . . . . . . . . . . . . . . . . . . . 14-8

Generate Intv-Dpth Velocity Function . . . . . . . . . . . . . . . . . . . . . . . 15-1


Compute Interval Velocity vs. Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

VSP CDP Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1


Contents

vi ProMAX VSP User Training Manual Landmark

VSP CDP Transform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

VSP Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1


VSP Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Display the VSP Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

VSP Corkscrew Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1


Assign VSP Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Quality Control Plots from the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8

Pre Vertical Stack Dataset Information . . . . . . . . . . . . . . . . . . . . . 19-1


VSP Prevertical Stack Dataset Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2

VSP Level Statics andVertical Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1


Plot the Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2

VSP Level Statics Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-5

Compute and Apply the Level Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7

Contents

Landmark ProMAX VSP User Training Manual vii

Vertically Stack Shots by Common Header Entry. . . . . . . . . . . . . . . . . . . . . 20-10

Compare Stacks With and Without Level Statics . . . . . . . . . . . . . . . . . . . . . 20-11

Synthetic Dataset Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-1


VSP Synthetic Dataset Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Level Stat and Vertical Stack for Multi Component / MultiLevel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-1


Plot the Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2

Determine Level Statics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-3

Vertically Stack Shots for Common Depth Levels . . . . . . . . . . . . . . . . . . . . . 22-7

Examine Headers for Common Header Entry . . . . . . . . . . . . . . . . . . . . . . . . . 22-9

Vertically Stack Shots by Common Header Entry. . . . . . . . . . . . . . . . . . . . . 22-10

Compare Stacks With and Without Level Statics . . . . . . . . . . . . . . . . . . . . . 22-11

3-Component Transform andFirst Break Picking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-1


3-Component Transform and First Arrival Picking. . . . . . . . . . . . . . . . . . . . . 23-2

Copying Picks from one Trace to the Others . . . . . . . . . . . . . . . . . . . . . . . . . . 23-4

QC the Copied Picks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6

Contents

viii ProMAX VSP User Training Manual Landmark

VSP 3-Component Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1


3 Component Hodogram Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-2

Example Hodogram Analysis Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-4

Example of Hodogram Output Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-7

Prepare Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-1


Preparing the Input Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25-2

Archival Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-1


SEG-Y Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-2

Tape Data Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-4

UNIX tar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-7

Archive to Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26-8

UNIX Workstation Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-1


Text Editors in ProMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-2

UNIX Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-5

Examples of UNIX Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27-15

Landmark ProMAX VSP User Training Manual i

Agenda

Agenda - Day 1

Introductions, Course Agenda

ProMAX User Interface Overview

Trace Display Functionality

• Exercises to familiarize ourselves with Trace Display

System Overview Discussion

• Discussion of the ProMAX system architecture

Parameter Testing

Viewing the Input Data

Geometry

• Building the geometry database for VSP data

Agenda-ii ProMAX VSP User Training Manual Landmark

Keep Vertical Traces

First Break Picking

Velocity Function Generation

Velocity Function Manipulation

True Amplitude Recovery Testing

True Amplitude Recovery

Wavefield Separation Testing

• Median Filter - FK Filter - Eigen Vector Filters

Landmark ProMAX VSP User Traiining Manual iii

Agenda Day 2

Isolate the Upgoing Energy

• After choosing the desired wavefield separation technique we will iso-late the upgoing energy

Isolate the Downgoing Energy

• After choosing the desired wavefield separation technique we will iso-late the upgoing energy

Deconvolution

• Source signature removal filter design and application

Corridor Stack

Splicing the Corridor Stack into a Surface Stack

VSP-CDP Transform

VSP Migration

Single channel vertical stack

• Preprocessing exercise for vertically stacking multiple shots at the samereceiver locations

Look at Synthetic Data

Level Statics

Level Summing (vertical stack)

Agenda-iv ProMAX VSP User Training Manual Landmark

Agenda Day 3

3-Component Transforms and first break picking

3-Component Hodogram Analysis

Dataset Preparation

VSP Modelling

Cross Well Tomography Demonstration

Archive Methods

Generation of CGM Plots

Landmark ProMAX VSP User Training Manual v

Preface

About The Manual

This manual is intended to accompany the instruction given during thestandard ProMAX VSP User Training course. Because of the power andflexibility of ProMAX VSP, it is unreasonable to attempt to cover allpossible features and applications in this manual. Instead, we try toprovide key examples and descriptions, using exercises which aredirected toward common uses of the system.

The manual is designed to be flexible for both you and the trainer.Trainers can choose which topics, and in what order to present materialto best meet your needs. You will find it easy to use the manual as areference document for identifying a topic of interest and movingdirectly into the associated exercise or reference.

vi ProMAX VSP User Training Manual Landmark

How To Use The Manual

This manual is divided into chapters that discuss the key aspects of theProMAX VSP system. In general, chapters conform to the followingoutline:

• Introduction: A brief discussion of the important points of the topicand exercise(s) contained within the topic.

• Topics Covered in Chapter: Brief list of skills or processes, in theorder that they are covered in the exercise.

• Topic Description: More detail about the individual skills orprocesses covered in the chapter.

• Exercise: Details pertaining to each skill in an exercise, along withdiagrams and explanations. Examples and diagrams will assist youduring the course by minimizing note taking requirements, andproviding guidance through specific exercises.

This format allows you to glance at the topic description to eitherquickly reference an implementation, or simply as a means of refreshingyour memory on a previously covered topic. If you need moreinformation, see the Exercise sections of each topic.

Landmark ProMAX VSP User Traiining Manual vii

Conventions

Mouse Button Help

This manual does not refer to using mouse buttons unless they arespecific to an operation. MB1 is used for most selections. The mousebuttons are numbered from left to right so:

MB1 refers to an operation using the left mouse button. MB2 is themiddle mouse button. MB3 is the right mouse button.

Actions that can be applied to any mouse button include:

• Click: Briefly depress the mouse button.

• Double Click: Quickly depress the mouse button twice.

• Shift-Click: Hold the shift key while depressing the mouse button.

• Drag: Hold down the mouse button while moving the mouse.

Mouse buttons will not work properly if either Caps Lock or Nums Lockare on.

Exercise Organization

Each exercise consists of a series of steps that will build a flow, helpwith parameter selection, execute the flow, and analyze the results.Many of the steps give a detailed explanation of how to correctly pickparameters or use the functionality of interactive processes.

The editing flow examples list key parameters for each process of theexercise. As you progress through the exercises, familiar parameterswill not always be listed in the flow example.

The exercises are organized such that your dataset is used throughoutthe training session. Carefully follow the instructor’s direction whenassigning geometry and checking the results of your flow. Animproperly generated dataset or database may cause a subsequentexercise to fail.

viii ProMAX VSP User Training Manual Landmark

Landmark ProMAX VSP User Training Manual 1-1

Chapter

ProMAX VSP System andDatabase Parameters

In this chapter we discuss some of the behind-the-scenes program operation, as well as basicProMAX framework. Understanding the ProMAX framework and its relationship to the UNIXdirectory structure can be useful. The ability to manipulate the various components of the linedatabase, such as ordered parameter files, from the User Interface is critical to smooth operationof the software.

Topics covered in this chapter:

❏ Directory Structure

❏ Program Execution

❏ Ordered Parameter Files

❏ Parameter Tables

❏ Disk Datasets

❏ Tape Datasets

1

Chapter 1: ProMAX VSP System and Database Parameters

1-2 ProMAX VSP User Training Manual Landmark

Directory Structure

/advance (or $PROMAX_HOME)

The directory structure begins at a subdirectory set by the$PROMAX_HOME environmental variable. This variable defaults to /advance, and is used in all the following examples. Set the$PROMAX_HOME environment variable to /my_disk/my_world/advance to have your Advance directory tree begin below the /my_disk/my_world subdirectory.

/advance/sys

/advance/sys is actually a symbolic link to subdirectories unique to agiven hardware platform, such as:

/advance/rs6000 for IBM RS6000 workstations,

/advance/sparc for Sun Microsystems Sparcstations running SunOS,

/advance/solaris for Sun Microsystems Sparcstations and Cray 6400workstations running Sun Solaris OS,

/advance/sgimips for Silicon Graphics Indigo workstations using the 32bit operating system and

/advance/sgimips4 for Silicon Graphics Indigo and Power Challengeworkstations using the 64 bit operating system.

This link facilitates a single file server containing executable programsand libraries for all machine types owned by a client. Machine specificexecutables are invoked from the UNIX command line, located in /advance/sys/bin.

Operating System specific executables and libraries, called fromProMAX, are located under /advance/sys/exe. These machine-dependent directories are named after machine type, not manufacturer,to permit accommodation of different architectures from the samevendor. Accommodating future hardware architectures will simplyinvolve addition of new subdirectories. Unlike menus, help andmiscellaneous files, a single set of executables is capable of running allAdvance products, provided the proper product specific licenseidentification number is in place.

Landmark ProMAX VSP User Traiining Manual 1-3


ProMAX Directory Structure

/sys

/port

/etc

/scratch

/queues

config_fileproductinstall.docpvmhostsqconfiglicense.dat

/data

/help

/menu

/misc

/plot

/lib

/bin

/exe

/promax3d

lib*.a

/promax

*.menuProcesses

/frame

/sdi

/3rd party software

super_exec.exe

*.exe

exec.exe

*.lok - Frame help*.help -ASCII help

*_stat_math*.rgb-colormapsProMax_defaults

$PROMAX_HOME

/area /line(or $PROMAX_DATA_HOME)

(default=/advance)

/promax3d

/promax

/promaxvsp

/promaxvsp

promaxpromax3d

promaxvsp



Third party software distributed by Advance will now be distributed ina subdirectory of /advance/sys/exe using the company’s name, thusavoiding conflicts where two vendors use identical file names. Forexample, SDI’s CGM Viewer software would be in /advance/sys/exe/sdi and Frame Technology’s FrameViewer would be in /advance/sys/exe/frame.



ProMAX Directory Structure

/sys

/port

/etc

/scratch

/queues

config_fileproductinstall.docpvmhostsqconfiglicense.dat

/data

/help

/menu

/misc

/plot

/lib

/bin

/exe

/promax3d

lib*.a

/promax

*.menuProcesses

/frame

/sdi/3rd party

super_exec.exe*.exe

exec.exe

*.lok - Frame help*.help -ASCII help

*_stat_math*.rgb-colormapsProMax_defaults

$PROMAX_HOME

/area /line(or $PROMAX_DATA_HOME)

(default=/advance)

/promax3d

/promax

/promaxvsp

/promaxvsp

promaxpromax3dpromaxvsp

software



/advance/port

Software that is portable across all platforms is grouped under a singlesubdirectory /advance/port. This includes menus and Processes (/advance/port/menu), helpfiles(/advance/port/help), miscellaneous files(/advance/port/misc). Under the menu and help subdirectories areadditional subdirectories for each ProMAX software product. Forinstance, under /advance/port/menu, you will find subdirectories forProMAX 2D (promax), ProMAX 3D (promax3d), and ProMAX VSP(promaxvsp). Menus for additional products are added as newsubdirectories under /advance/port/menu.

/advance/etc

Files unique to a particular machine are located in the /advance/etcsubdirectory. Examples of such files are the config_file, which containsperipheral setup information for all products running on a particularmachine, and the product file, which assigns unique pathnames forvarious products located on the machine.

/advance/scratch

The scratch area defaults to /advance/scratch. This location can beoverridden with the environmental variable,PROMAX_SCRATCH_HOME.

All ProMAX development tools are included within the followingsubdirectories: /advance/sys/lib, /advance/sys/obj, /advance/port/src, /advance/port/bin, /advance/port/include and /advance/port/man.

/advance/data (or $PROMAX_DATA_HOME)

The primary data partition defaults to /advance/data, with new areasbeing added as subdirectories beneath this subdirectory. This defaultlocation is specified using the entry:

— primary disk storage partition: /advance/data 20

in the /advance/etc/config_file. This location can also be set with theenvironmental variable $PROMAX_DATA_HOME.



ProMAX Data Directories

Each region identifies a collection of files and directories which can besummarized as the Area, Line, Parameter Tables, Flow, Trace Headers,and Ordered Parameter Files database.

/Data

/AreaDescNameProject

/LineDescName17968042TVEL31790267TGAT36247238TMUT12345678CIND12345678CMAP

/12345678HDR1HDR2TRC1

/Flow1

TRC2

DescName

job.output

/OPF.SINOPF60_SIN.GEOMETRY.ELEV

/OPF.SRF

A Flow subdirectoryTypeName

packet.job

and its files

Parameter Table files

Index and Map Dataset files

Dataset subdirectoryand Header and TraceDataset files

PROMAX_DATA_HOME

or

#s0_OPF60_SRF.GEOMETRY.ELEV

/OPF.SIN Databasesubdirectory anda non-spanned file

/OPF.SRF Databasesubdirectory and aspan file

Area subdirectoryand its files



Program Execution

User Interface ($PROMAX_HOME/sys/bin/promax)

Interaction with ProMAX is handled through the User Interface. As youcategorize your data into Areas and Lines, the User Interfaceautomatically creates the necessary UNIX subdirectories and providesan easy means of traversing this data structure.

However, the primary function of the User Interface is to create, modify,and execute processing flows. A flow is a sequence of processes that youperform on seismic data. Flows are built by selecting processes from alist, and then selecting parameters for each process. A typical flowcontains an input process, one or more data manipulation processes, anda display and/or output process. All information, needed to execute aflow, is held within a Packet File (packet.job) within each Flowsubdirectory. This Packet File provides the primary means ofcommunication between the User Interface and the Super Executiveprogram. See next section, Super Executive Program.

In addition, the User Interface provides utility functions for copying,deleting and archiving Areas, Lines, Flows, and seismic datasets;accessing and manipulating ordered database files and parameter tables;displaying processing histories for your flows; and providinginformation about currently running jobs. The User Interface is



primarily mouse-driven and provides point-and-click access to thefunctions.

Program Execution

Super Executive Program (super_exec.exe)

Execution of a flow is handled by the Super Executive, which islaunched as a separate task by the User Interface. The Super Executiveis a high level driver program that examines processes in your flow byreading packet.job and determines which executables to use. Themajority of the processes are subroutines linked together to form theExecutive. Since this is the processing kernel for ProMAX, many ofyour processing flows, although they contain several processes, arehandled by a single execution of the Executive. Several of the processes



are stand-alone programs. These processes cannot operate under thecontrol of the Executive, and handle their own data input and output bydirectly accessing external datasets. In these instances, the SuperExecutive is responsible for invoking the stand-alone programs and, ifnecessary, multiple calls to the Executive in the proper sequence.

The Packet File, packet.job, defines the processes and their type forexecution. The Super Executive concerns itself with only two types ofprocesses:

• Executive processes

• Stand-alone processes

Executive processes are actually subroutines operating in a pipeline,meaning they accept input data and write output data at the driver level.However, stand-alone processes cannot be executed within a pipeline,but rather must obtain input and/or produce output by directly accessingexternal datasets.

The Super Executive sequentially gathers all Executive-type processesuntil a stand-alone is encountered. At that point, the Packet Fileinformation for the Executive processes is passed to the Executiveroutine (exec.exe) for processing. Once this is completed, the SuperExecutive invokes the stand-alone program for processing, and thenanother group of Executive processes, or another stand-alone process.This continues until all processes in the flow have been completed.

Executive Program (exec.exe)

The Executive program is the primary processing executable forProMAX. The majority of the processes available under ProMAX arecontained in this one executable program.

The Executive features a pipeline architecture that allows multipleseismic processes to operate on the data before it is displayed or writtento a dataset. Special processes, known as input and output tools, handlethe tasks of reading and writing the seismic data, removing thisburdensome task from the individual processes. This results in processesthat are easier to develop and maintain.



The basic flow of data through the Executive pipeline is shown below:

Each individual process will not operate until it has accumulated thenecessary traces. Single trace processes will run on each trace as thetraces come down the pipe. Multi channel processes will wait until anentire ensemble is available. For example in the example flow the FK



filter will not run until one ensemble of traces has passed through theDDI and AGC. If we specify for the Trace Display to display 2ensembles, it will not make a display until two shots have beenprocessed through the DDI, AGC and FK filter. No additional traceswill be processed until Trace Display is instructed to release the tracesthat it has displayed and is holding in memory by clicking on the trafficlight icon or terminating its execution (but continuing the flow).

Note: All the processes shown are Executive processes and thus operatein the pipeline. An intermediate dataset and an additional input toolprocess is needed if a stand-alone process were included in this flow.

A pipeline process must accept seismic traces from the Executive,process them, and return the processed data to the Executive. The tablebelow describes the four types of processes defined for use in theExecutive.



AGC

F-K Filter

Decon

Disk DataInput

Disk Data

Disk Data Input, Tape DataInput and standalone toolsalways start new pipeswithin a single flow

One pipe must completesuccessfully before a newpipe will start processing

NMO

CDP Stack

Bandpass

Disk DataInput

Disk Data

Filter

Output

Output

Multiple Pipes in One Flow



Types of Executive Processes

The table below describes the four types of processes defined for use inthe Executive.

Stand-Alone Processes and Socket Tools

Some seismic processing tools are not well suited to a pipelinearchitecture. Typically, these are tools making multiple passes throughthe data or requiring self-directed input. These tools can be run inline ina ProMAX job flow and appear as ordinary tools, but in reality arelaunched as separate processes. The current version of ProMAX doesnot provide the ability to output datasets from a stand-alone process.Socket tools start a new process and then communicates with theExecutive via UNIX interprocess communications. Socket tools havethe singular advantage of being able to accept and output traces in anasynchronous manner.

Table 1: ProMAX Executive Process Types

Process Type Description

simple tools Accepts and returns a single seismic trace.

ensemble tools Accepts and returns a gather of seismic traces

complex tools Accepts and returns a variable number of seismic traces suchas, stack. This type of process actually controls the flow ofseismic data.

panel tools Accepts and returns overlapping panels of traces toaccommodate a group of traces too large to fit into memory.Overlapping panels are processed and then merged alongtheir seams.



Ordered Parameter Files

Click to jump to the section

This section discusses the following issues relating to the OrderedParameter Files database:

• Organization

• Database Structure

• File Naming Conventions

The Ordered Parameter Files database serves as a central repository ofinformation that you or the various tools can rapidly access.Collectively, the ordered database files store large classes of data,including acquisition parameters, geometry, statics and other surfaceconsistent information, and pointers between the source, receiver andCDP domains. The design of the Orders is tailored for seismic data, andprovides a compact format without duplication of information.

The Ordered Parameter Files database is primarily used to obtain a listof traces to process, such as traces for a shot or CDP. This list of tracesis then used to locate the index to actual trace data and headers in theMAP file of the dataset. Once determined, the index is used to extractthe trace and trace header data from their files.

Organization

The Ordered Parameter Files contain information applying to a line andits datasets. For this reason, there can be many datasets for a single setof Ordered Database Files.

Ordered Parameter Files, unique to a line, reside in the Area/Linesubdirectory. The Ordered Parameter Files database stores informationin structured categories, known as Orders, representing unique sets ofinformation. In each Order, there are N slots available for storage ofinformation, where N is the number of elements in the order, such as thenumber of sources, number of surface locations, or number of CDPs.Each slot contains various attributes in various formats for one



particular element of the Order. The Orders are organized as shown inthe table below.

OPF Matrices

The OPF database files can be considered to be matrices.

Each OPF is indexed against the OPF counter and there are varioussingle numbers per index. Note the relative size of the TRC OPF to theother OPF files. The TRC is by far the largest contributor to the size ofthe database on disk

Table 2: Organization of Ordered Parameter Files

LIN (Line) Contains constant line information, such as final datum, type ofunits, source type, total number of shots.

TRC (Trace) Contains information varying by trace, such as FB Picks, trimstatics, source-receiver offsets.

SRF(Surface location)

Contains information varying by surface receiver location, suchas surface location x,y coordinates, surface location elevations,surface location statics, number of traces received at eachsurface location, and receiver fold.

SIN(Source Index #)

Contains information varying by source point, such as sourcex,y coordinates, source elevations, source uphole times, nearestsurface location to source, source statics.

CDP (CommonDepth Point)

Contains information varying by CDP location, such as CDP x,ycoordinates, CDP elevation, CDP fold, nearest surface location.

CHN (Channel) Contains information varying by channel number, such asChannel gain constants, channel statics

OFB(Offset Bin)

Contains information varying by offset bin number, such assurface consistent amplitude analysis. OFB is created whencertain processes are run, such as surface consistent amplitudeanalysis.

PAT (Pattern) Contains information describing the recording patterns.

Table 3: Additional Parameter Files for 3D

ILN (Inline) Contains information, constant within a 3D inline.(Number oftraces per line)

XLN (Crossline) Contains information constant within a 3D crossline. (Numberof traces per crossline)



OPF Maftrices

SIN (Sources) Database

SRF (Receivers) Database



Database Structure

The ProMAX database was restructured for the 6.0 release to handlelarge 3D land and marine surveys. The features of the new databasestructure are listed below:

Each order is contained within a subdirectory under Area and Line. Forexample, the TRC is in the subdirectory OPF.TRC.

There are two types of files contained in the OPF subdirectories:

• Parameter: Contain attribute values. There may be any number ofattribute files associated with an OPF.

• Index: Holds the list of parameters and their formats. There is onlyone index file in each OPF subdirectory. The exception to this is theLIN OPF. The LIN information is managed by just two files, oneindex and one parameter, named LIN.NDX and LIN.REC.

OPF files are of two types:

• Span: These files are denoted by the prefix, #s. Non-span files lackthis prefix. The TRC, CDP, SIN, and SRF OPF parameters are spanfiles. The first span for each parameter is always written to primarystorage. Span files are created in the secondary storage partitionslisted in the config_file as denoted with the OPF keyword. Spanfiles may be moved to any disk partition within the secondarystorage list for read purposes. Newly created spans are written inthe OPF denoted secondary storage partitions. All subsequent spansare written to the secondary storage partitions denoted by the OPFkeyword in a round robin fashion until the secondary storage is full.Then, subsequent spans are created in primary storage. Span filesize is currently fixed at 10 megabytes, or approximately 2.5million 4 byte values per span file.

• Non-span: All other OPFs are non-span.

Given the fact that each parameter is managed by a file, it may benecessary to increase the “maximum number of files open” limit onsome systems, specifically, SUN, Solaris and SGI. From the csh, thefollowing command increases the file limit to 255 files open, “limit de255”.

The geometry spreadsheet is a ProMAX database editor. Modifyinginformation within a spreadsheet editor and saving the changes willautomatically update the database.



There is no longer an import or export from the geometry database to theProMAX database files as was required prior to the 6.0 release.

Database append is allowed. Data can be added to the database via theOPF Extract tool or the geometry spreadsheet. This allows for thedatabase to be constructed incrementally as the data arrives.

There is improved network access to the database. Database I/O acrossthe network is optimized to an NFS default packet size of 4K. Alldatabase reads and writes are in 4K pages.

Existing and restored 5.X databases are automatically converted to the6.0 (and later) database format.

File Naming Conventions

Parameter file names consist of information type and parameter name,preceded by a prefix denoting the Order of the parameter.

For example, the x coordinate for a shot in the SIN has the followingname: #s0_OPF60_SIN.GEOMETRY.X_COORD. Where #s0_OPF60indicates a first span file for the parameter, _SIN denotes the Order,GEOMETRY describes the information type of the parameter, andX_COORD is the parameter name.

0. Index file names contain the three letter Order name. For example,the index file for the TRC is called OPF60_TRC.

Within each Order, there are often multiple attributes, with eachattribute being given a unique name.

NOTE:

The index file for each Order must remain in the primary storagepartition. Span parameter files may be moved and distributedanywhere within primary and secondary storage.



Parameter Tables

Parameter Tables are files used to store lists of information in a verygeneralized structure. To increase access speed and reduce storagerequirements, parameter tables are stored in binary format. They arestored in the Area/Line subdirectory along with seismic datasets, theOrdered Parameter Files database files (those not in separatedirectories), and Flow subdirectories.

Parameter Tables are often referred to as part of the database. Parametertables differ from the OPF database in OPF files contain many attributesthat are 1 number per something. Parameter tables contain more thanone number per something. For example a velocity function containsmultiple velocity-time pairs at 1 CDP.

Creating a Parameter Table

Parameter tables are typically created in three ways:

• Processes store parameters to a table for later use by otherprocesses.

• Parameter tables can be imported from ASCII files that werecreated by other software packages or hand-edited by you.

• Parameter tables can be created by hand using the Parameter TableEditor which is opened by the Create option on the parameter tablelist screen.

An example is the interactive picking of time gates within the TraceDisplay process. After seismic data is displayed on the screen, you pulldown the Picking Menu and choose the type of table to create. The endresult of your work is a parameter table. If you were to pick a top mute,you would generate a parameter table ending in TMUT. If you werepicking a time horizon, you would generate a table ending in THOR.These picks are stored in tabular format, where they can be edited, usedby other processes in later processing, or exported to ASCII files for useby other software packages.

Remember, you name and store the parameter tables in their specificArea/Line subdirectory. Therefore, you can inadvertently overwrite anexisting parameter table by editing a parameter table in a differentprocessing flow.



ASCII File Export to Parameter Table Editor

Export writes either ASCII or EBCDIC formatted files with fixedcolumnar data from a spreadsheet editor. In the following exercise, avelocity table is exported to an ASCII file.

Exercise1. In a flow-building window, add the Access Parameter Tables process

to a flow and view the parameter menu with MB2.

Find the line: VEL: RMS (stacking) velocity and click on Invalid.The list of parameter tables for RMS Velocity appear.

2. Click on Edit and select the name of the file to export.

A Parameter Table spreadsheet appears with CDP, TIME, andSEMB_VEL columns.

3. Click on File and select Export.

An ASCII File Export window appears with export information forquality control before actually creating the ASCII file.

4. Click on File.

A new window appears with the path to your working directory.

5. Enter a filename after the last / and click OK.

The window disappears and a dashed line appears in the ASCII FileExport window.

6. Click on Format.

An Export Definition Selection window appears.

7. Type in a selection name and click on OK.

The Column Export Definition window appears.

8. Fill the Column Export Definition with starting and ending columnnumbers, then click on Save.

When you fill in the start and end columns for a particular columndefinition, the contents of the column appear in the ASCII File



Export window. Be sure the column definitions are wide enough toaccommodate all the significant figures, as well as complete columntitles. If they are not, edit the Column Export Definition windowuntil the information is correct.

9. When the ASCII File Export window is correct, click on Apply.

An Apply Export window appears. You may choose to overwrite orappend new information to the ASCII file. You may also add a singleline description of your work that will be internal to the file.

10. Click on OK.

This creates the ASCII file in the directory you specified. You maynow Quit the Column Export Definition window, Cancel the ASCIIfile Export Window, and pull down the File menu in the ParameterTable window and exit this window and continue working.

ASCII File Import to a Parameter Table

File Import reads either ASCII or EBCDIC formatted files with fixed columnar data into thespreadsheet editor.

Exercise1. In a flow-building window, add the Access Parameter Tables process

and view the parameter menu with MB2.

Find the line: VEL: RMS (stacking) velocity and click on Invalid.The list of Parameter Files(tables) for RMS velocity appear.

2. Click on Create.

The cursor will move to the top of the table name column, enter anew velocity file name. After typing a name, press Return. AParameter Table spreadsheet appears with CDP, TIME, andVEL_RMS columns.

3. Click on File and choose Import.

Two new windows appear: ASCII/EBCDIC File Import and FileImport Selection. In the File Import Selection window, choose thepath to the file containing velocity information to import and clickon OK. The import information appears in the ASCII/EBCDIC FileImport window.



4. Click on Format in the ASCII/EBCDIC File Import window.

The Import Definition Selection window appears.

5. Type in a selection name and click on OK.

The Column Import Definition window appears.

6. Blank rows that will not be imported into the new velocity file.

To blank the rows, click MB1 in the first row to ignore and clickMB2 in the last row to ignore. Press Ctrl-d, the rows to ignore arelabeled Ignore Record for Import.

7. Fill the Column Import Definition window.

Begin filling the Column Import Definition window by choosing adefinition parameter by clicking on the parameter name. Theparameter box will be highlighted in white. Next, move the cursorinto the ASCII/EBCDIC File Import window to the values definingthe definition parameter. Hold down MB1 as you drag it from left toright across the import parameter values. The chosen columnsshould highlight in black in the ASCII/EBCDIC File Import windowand the Start Col and End Col boxes in the Column ImportDefinition window should contain the appropriate column numbers.Repeat this process with the other two parameters and save thedefinition.

8. When the Column Import Definition window is correct, click onApply in the ASCII/EBCDIC File Import window.

The Apply Import window appears. You may choose to overwrite orappend new information to the spreadsheet.

9. Click OK.

This fills in the spreadsheet with selected numbers. Also, the Importwindows disappear from the screen. You may now continue workingand apply these velocities to your data.



Disk Datasets

ProMAX uses a proprietary disk dataset format that is tailored forinteractive processing and random disk access. Disk dataset files canspan multiple filesystems, allowing for unlimited filesize datasets.

A typical set of files might look like this:

— /advance/data/usertutorials/landexample/12345678CIND/advance/data/usertutorials/landexample/12345678CMAP/advance/data/usertutorials/landexample/12345678/TRC1/advance/data/usertutorials/landexample/12345678/HDR1

These files are described in more detail in the table below.

Table 4: Composition of a Seismic Dataset

File Name Contents

Trace(...TRCx)

File containing actual sample values for data trace.

Trace Header(....HDRx)

File containing trace header entries corresponding to datasamples for traces in the trace file. This file may vary inlength, growing as new header entries are added. Keep traceheaders in a separate file so trace headers can be sortedwithout needing to skip past the seismic data samples.

Map(....CMAP)

File keeps track of trace locations. Given a particular tracenumber, it will find the sequential trace number within thedataset. This rapidly accesses traces during processing. Themap file is a separate file, as it may grow during processing.

Index(....CIND)

File has free-form format information relating to the entiredataset, including sample interval, number of samples pertrace, processing history, and names of trace header entries.This file may grow during processing.



Disk Dataset Components - Relative Sizes

Secondary Storage

In a default ProMAX configuration, all seismic dataset files reside on asingle disk partition. The location of this disk partition is set in the$PROMAX_HOME/etc/config_file with the entry:

— primary disk storage partition: /advance/promax/data 20

In addition to the actual trace data files, the primary storage partitionwill always contain your flow subdirectories, parameter tables, orderedparameter files, and various miscellaneous files. The ...CIND and...CMAP files which comprise an integral part of any seismic dataset arealways written to primary storage.

Since the primary storage file system is of finite size, ProMAX providesthe capability to have some of the disk datasets, such as the ...TRCx and...HDRx files, and some of the ordered parameter files span multipledisk partitions. Disk partitions other than the primary disk storagepartition are referred to as secondary storage.

All secondary storage disk partitions must be declared in the appropriate$PROMAX_HOME/etc/config_file. Samples entries are:

CIND

CMAP

HDRx

TRCx



secondary disk storage partition: /advance/promax/data2 20 TRC OPFsecondary disk storage partition: /advance/promax/data3 20 TRCsecondary disk storage partition: /advance/promax/data4 20 OPFsecondary disk storage partition: /advance/promax/data5 20

Refer to the ProMAX System Administration guide for a completedescription of the config_file entries for primary and secondary diskstorage.

Under the default configuration, the initial TRC1 and HDR1 files arewritten to the primary storage partition. It is possible to override thisbehavior by setting the appropriate parameter in Disk Data Output. If theparameter Skip primary disk partition? is set to Yes, then no TRC orHDR files will be written to the primary disk partition. This can beuseful as a means of maintaining space on the primary storage partition.(To make this the default situation for all users, have your ProMAXsystem administrator edit the diskwrite.menu file, setting the value forAlstore to ‘t’ instead of ‘nil’).

A typical set of data files might look like this:

— /advance/data/usertutorials/landexample/12345678CIND /advance/data/usertutorials/landexample/12345678CMAP /advance/data/usertutorials/landexample/12345678/TRC1 /advance/data/usertutorials/landexample/12345678/HDR1 /advance/data/usertutorials/landexample/12345678/TRC4 /advance/data/usertutorials/landexample/12345678/HDR4 /advance/data/usertutorials/landexample/12345678/TRC7 /advance/data/usertutorials/landexample/12345678/HDR7

/advance/data2/usertutorials/landexample/12345678/TRC2 /advance/data2/usertutorials/landexample/12345678/HDR2 /advance/data2/usertutorials/landexample/12345678/TRC5 /advance/data2/usertutorials/landexample/12345678/HDR5 /advance/data2/usertutorials/landexample/12345678/TRC8 /advance/data2/usertutorials/landexample/12345678/HDR8

/advance/data3/usertutorials/landexample/12345678/TRC3 /advance/data3/usertutorials/landexample/12345678/HDR3 /advance/data3/usertutorials/landexample/12345678/TRC6 /advance/data3/usertutorials/landexample/12345678/HDR6



Secondary storage is used in a “as listed and available” fashion. As anattempt to minimize data loss due to disk hardware failure, ProMAXtries to write a dataset to as few physical disks as possible. If the primarystorage partition is skipped by setting the appropriate parameter in DiskData Output, the CIND and CMAP files are still written to the primarystorage partition, but the TRCx or HDRx files will not be found there.



Tape Datasets

Tape datasets are stored in a proprietary format, similar to the diskdataset format, but incorporating required structures for tape input andoutput. Tape input/output operates either in conjunction with a tapecatalog system, or without reference to the tape catalog. The tapedevices used for the Tape Data Input, Tape Data Insert, and Tape DataOutput processes are declared in the ProMAX device configurationwindow. This allows access to tape drives anywhere on a network. Themachines that the tape drives are attached to do not need to be licensedfor ProMAX, but the fclient.exe program must be installed.

Tape Trace Datasets

A ProMAX tape dataset is similar to a disk dataset in that the index file(...CIND) and map file (...CMAP) still reside on disk in the Line/surveydatabase. Refer to the documentation in the Disk Datasets portion of thishelpfile for a discussion of these files. Having the index and map filesavailable on disk provides you with immediate access to informationabout the dataset, without needing to access any tapes. It also providesall the information necessary to access traces in a non-sequentialmanner.

Although the index and map files still reside on disk, copies of them arealso placed on tape(s), so that the tape(s) can serve as a self-containedunit(s). If the index and map files are removed from disk, or neverexisted, as in the case where a dataset is shipped to another site, the tapescan be read without them. However, access to datasets through the indexand map files residing solely on tape must be purely sequential.

Tape datasets are written by the Tape Data Output process, and can beread using the Tape Data Input or Tape Data Insert processes. Theseinput processes include the capability to input tapes by reel, ensemblenumber, or trace number. Refer to the relevant helpfile for a completedescription of the parameters used in these processes.

The use or non-use of the tape catalog in conjunction with the tape I/Oprocesses is determined by the tape catalog type entry in the appropriate$PROMAX_HOME/etc/config_file. Setting this variable to fullactivates catalog access, while an entry of none deactivates catalogaccess. An entry of external is used to indicate that an external tapecatalog, such as the Cray Reel Librarian, will be used. You can overridethe setting provided in the config_file by setting the environment



variable for BYPASS_CATALOG to ‘t’, in which case the catalog willnot be used. The actual tape devices to use for tape I/O must also appearas entries in the config_file, under the tape device: stanza.



Tape Catalog System

Tape Catalog Overview

The fundamental strategy of the tape catalog is that a group of tapes areintroduced or logged into the tape catalog, which then works inconjunction with the Tape Input, Tape Insert, and Tape Outputprocesses to provide access to those tapes from within the ProMAXsystem. Before being introduced to the catalog, an ANSI label is writtento each tape using the catalog utilities outlined below. The catalogsystem knows the label and status (initially SCRATCH) of every tape,and can monitor and validate the tape catalog resources accordingly. Forexample, when a request for an output dataset is made, the catalog candecide which tape to use, and can verify that the correct tape is mounted.When a dataset overflows a tape, the catalog can decide which tape touse next, and can again verify that the correct tape is mounted. When arequest for an input dataset is made, the catalog knows which tapesbelong to the dataset, and can verify that the correct tapes are mountedin the correct order.

Getting Started

The first step in using the Advance tape catalog is to create some labeledtapes.

The program $PROMAX_HOME/sys/bin/tcat is used for tape labelling,catalog creation and maintenance, and for listing current cataloginformation. The program is run from the UNIX command line.

The following steps are required to successfully access the tape catalog:

1. Label tapes

1. Read and Display tape labels

1. Add labeled tapes to a totally new catalog

Before adding the tapes to a new catalog, it is a good idea to visuallyinspect the contents of the label information file for duplicate or missingentries. The contents typically look like:

0 AAAAAA 0 1 41 AAAAAB 0 1 4



2 AAAAAC 0 1 43 AAAAAD 0 1 44 AAAAAE 0 1 4

The fields are: volume serial number (digital form), volume serialnumber (character form), tape rack slot number, site number, and mediatype, respectively. You can manually edit these fields.

1. Write a label information file from the existing catalog

1. Add labeled tapes (and datasets) to the existing catalog

1. Merge an additional catalog into the existing catalog

2. Delete a dataset from the catalog




Chapter

Flow Building and Execution

This chapter is designed to get you started processing with ProMAX.You will learn how to set up a work space with the ProMAX UserInterface and subsequently build and execute data processing flows.


❏ Getting Started

❏ Building and Executing a Flow

2

Chapter 2: Flow Building and Execution


ProMAX Menu Map



Getting Started

ProMAX is built upon a three level organizational model referred to asArea/Line/Flow. When entering ProMAX for the first time, you willbuild your own Area/Line/Flow workspace. As you add your own Area,you may want to name it with reference to a geographic area thatindicates where the data were collected, such as Onshore Texas, or useyour name, such as daves area. Line is a subdirectory of Area whichcontains a list of 2D lines from an area or a 3D survey name. Afterchoosing a line from the Line menu or adding a new line, the Flowwindow will appear. Name your flows according to the processingtaking place, such as brute stack.

Look at the Menu Map figure on the previous page. This figure refers toother menus you can use to access your datasets, database entries andparameter tables. These features will be discussed later.

ExerciseIn this exercise, you will build a workspace and look at some of theavailable options.

Initiating a ProMAX session can be done in a variety of ways. Typicallyyour system administrator will create a start-up script or make a UNIXalias, and set certain variables within your shell start-up script to makethis easy. This topic is discussed in the system overview chapter.

1. Type promax.

A product name window should pop up followed by the Areawindow. The window, as shown below displays a list of all availableAreas. Other information is listed, such as owner, date and UNIXname.



The black horizontal band below the menu is called mouse buttonhelps. Mouse button helps describe the possible actions at thecurrent location of the cursor.

Below the mouse button helps are options to Exit ProMAX,configure the queues and user interface, as well as check on thestatus of jobs. These options will be discussed at length later.

The list of options running across the top of this menu: Select, Add,Delete, Rename, and Permission are called global options. To usethese, you must first click on the option followed by clicking the lineon your screen with your Area name. The Copy option worksdifferently by providing popup menus to choose Areas not displayedin this window.

Global Commands

Configuration Options

Exit Promax

Job Notificationand Control

Mouse Button Help

Processing QueuesWindow

Area Menu



2. Click on Add from the Area Menu with MB1.

At this point you are building your work space. Adding an Areacreates a UNIX directory.

3. Before moving the mouse, enter an Area name

You can choose the area name.

4. Press return, or move the mouse to register your selection.

The Line Menu appears with the same global options to choose fromas the Area Menu. (Pressing return or moving the mouse to registera selection depends on whether the ‘Popups remain after mouseleaves’ option is toggled on or off. This option is listed under theConfiguration Options.)

Global Commands

Line Menu

Area Name

Active Command

Available Seismic Lines

Configuration Options

Exit Promax

Job Notificationand Control

Mouse Button Help

Processing QueuesWindow



5. Add a Line using the same steps as you did for adding an Area.

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.

• Product: Changes from ProMAX 2D to ProMAX 3D or VSP.

6. Add a Flow and name it Display Shots.

Global Commands

Change Products

Access DatabaseAccess Datasets

Active Command

Available Flows

Flows Menu



Building and Executing a Flow

Now it is time to process data. In order to perform this task, you willneed to tell ProMAX which processes you want to invoke as well asprovide specific details for each of these steps. Finally, there aredifferent options available for executing a flow.

ExerciseUpon completion of the previous exercise, you are in the ProMAX flowbuilding menu (see below). From here, you will construct your flows byordering processes and selecting the necessary parameter information.Once the flow is ready, you will execute it and look at the results.

1. Look at the flow building menu.



The screen is split into two sides: a list of processes on the right anda blank tablet below the global options on the left. You will selectfrom the processes on the right and add them to the left.

The list of available processes is very long. This list is ordered fromtop to bottom into a general processing sequence with I/O processesat the top and poststack migration tools further down on the list.There is a scroll bar to help you look at the list. There are alsooptions available to hide processes in the secondary or More list (usethe mouse button helps).

You can customize the list to have only the processes you use mostoften displayed.

2. Move your cursor into different areas of the display, such as into theprocesses list, the blank tablet and the various options.

The mouse button helps are sensitive to the current cursor location.

3. Global Options for flow editing are as follows.

• Add: This is the default. When highlighted in blue, a process canbe selected from either the list of processes or a text searchmenu.

• Delete: When selected with MB1, the highlighted process isremoved from the flow. This process is actually stored in a bufferand can be accessed by selecting Delete with MB3. SelectingDelete with MB2 appends a newly deleted process to the existingdelete buffer. MB3 is also used to paste the contents of this bufferinto the current flow. The memory of the buffer is maintainedeven after exiting a flow menu, so the contents may be pastedinto another flow.

• Execute: When selected, the job is executed.

There are two methods available to execute a flow using theTrace Display process:

MB1 and MB2 will Execute suppressing pause for display.These options allow the display to immediately take over themonitor when the job has finished running.

MB3 indicates Execute via Queue. This option enables the useof the two types of queues. When using MB3, a new menu popsup allowing the use of either the general batch queues or the



small job batch queues. In order for this option to work yoursystem administrator should have enabled the queues whenProMAX VSP was installed.

Note: When using Screen Display, the mouse button helps arecorrect and MB1 will Execute With Normal Wait on display.When this option is used, the Notification window first shows thejob has started and is then waiting for display. By clicking on theNotification window, a new Processing Jobs window appearswhere it waits for your response. Clicking on Wait for Display,prompts the display to come to the foreground of the monitor.This option is useful if you want to work on something else anddo not want to be interrupted by the display taking over themonitor.

• View: Accesses the view (job.output) file. This file includesimportant job information such as error statements.

• Exit: Brings you back to the menu listing of all your flows.

4. Move your cursor into the Data Input/Output portion of theprocesses list, and select the process SEG-Y Input with MB1.

You have just added your first process to a flow.

5. Move your cursor back into the processes list (but not on a categoryheading) and type “trace d” and press return.

This acts as a text search. Click on Trace Display to add it to the flow.

6. Parameterize the flow.

7. Select SEG-Y Input parameters.

Editing Flow: 00- Display data

Add Delete Execute View Exit

SEG-Y Input----------instructor provided

MAX traces per ensemble---------------------------------3

----Default all remaining parameters for this process----Trace Display

Number of ENSEMBLES/screen-----------------------10

----Default all remaining parameters for this process----



Click on SEG-Y Input with MB2 to bring up the parameter selectionwindow. Now you can select the parameters for this process.

To get a helpfile for a process, click on the red highlighted questionmark.

8. In the SEG-Y Input menu, select the dataset as directed by yourinstructor.

There are 3 traces per shot ensemble in this SEGY dataset.

All of the remaining parameters may be defaulted.

9. Select the Trace Display parameters.

For now, do not change any of the values except that we want todisplay 10 ensembles. We will discuss many of the other options inthe next chapter.

10. Run the flow by clicking on the global command, Execute.

Execution results in a trace display on the screen. Eight icons appearin a column to the left of the traces, and pulldown menus appearabove the traces.

11. Click on the page forward icon a few times and watch as we movefrom one group of shots to the next.

12. You may elect to change the primary annotation from Source toFFID using the VIEW/Trace Annotation pull down menu.

13. Click on File and then Exit/Stop flow in the pulldown menu.

This interrupts the job and brings you back to the flow builder.



Exercise- output a file to disk1. Using the same flow as before deactivate the Trace Display using

MB3 and add in a Disk Data Output at the end of the flow.

2. Add a dataset to the datasets list in the Disk Data Output menu.

We will use this dataset in the next few exercises instead of readingthe SEGY file again.

3. Execute the flow

4. When complete, go to the datasets list and press MB2 on the filename you just created.

You should see a summary print that shows that you have a data setwith 80 ensembles and 240 traces.

Exercise- Disk Data Input Sort Options5. Using the same flow toggle the SEG-Y Input inactive and add a

Disk Data Input to the Flow.



SEG-Y Input>Trace Display<Disk Data Output



>SEG-Y Input<Disk Data Input

Trace read option-------------------------------------------------Sort

Select primary trace header entry------------------------FFID

Sort order list for dataset--------------------------------1-80(2)/Trace Display

Primary trace LABELING header entry-----------------FFID>Disk Data Output<



6. Toggle the Trace Display active and the Disk Data Output inactiveusing MB3.

7. Select new Disk Data Input parameters.

Your first look at the executed job was all of the shots with allchannels. After clicking the Page Forward icon, you saw the next setof shots. What if you wanted to look at a every other shot? What ifyou only wanted to look at a single channel for each shot? Theseoptions, and many more, are available in Disk Data Input.

8. Click on the Get All for Trace Read Option.

This toggles to Sort and the menu will automatically add three newoptions:

• Select Primary trace header entry: Allows you to resort toanother domain, such as CDP, or remain in the same sort order,which sets you up for trace limiting.

• Select Secondary trace header entry: Same as above.

• Sort order for dataset: Allows you to restrict the amount of databrought into the flow, such as channels 1-60.

Let’s try one.

9. Set the Primary trace header entry to FFID (Field file ID number)

10. Click on Sort order for dataset.

An Emacs Widget Window appears for specifying input traces. Aformat and example are given at the bottom of this window. EmacsHelp is discussed later in the training class.

11. In the Widget Window delete existing values and type 1-80 (2) /.

12. Move your cursor out of the Widget Window.

13. Click on Execute.

You will see FFID’s 1- 19 by 2.

14. You may want to change the primary trace annotation again toFFID instead of SOURCE using the pull down menu.



15. Click on the Page Forward icon.

This will be Live Source Numbers 21-39 by 2.

When the last available data is displayed, the Page Forward trianglebecomes grayed out and is inactive. To exit this display, click on Fileand choose Exit/Stop Flow.

Lets make the exercise a little bit more complicated and try todisplay all the shots but only with channel 1.

16. Select the parameters for Disk Data Input. .

Choose CHAN from the popup menu for primary trace header entryand FFID for secondary.

17. Change the Sort order for dataset to 1:*.

This format specifies to build ensembles of recording channelnumber and have the traces within this ensemble ordered by FFID.Check the formats and examples for hints.

18. Execute the flow.

You will only see the trace from channel 1 for all the shots displayedas a single ensemble



>SEG-Y Input<Disk Data Input

Trace read option-------------------------------------------------Sort

Select primary trace header entry----------------------CHAN

Select secondary trace header entry-------------------FFID

Sort order list for dataset--------------------------------1:*/Trace Display

Primary trace LABELING header entry--------------CHAN

Secondary trace LABELING header entry-------------FFID

>Disk Data Output<



In this case you may elect to set the primary annotation to CHANand the secondary to FFID.

This is a typical sort type for VSP data.

19. Select to Exit/Stop the flow.


Chapter

Interactivity of Trace Display

Trace Display provides general trace display and analysis capabilities.In addition, it allows for interactive definition of parameter tables.Interaction with the data is accomplished using a series of icons andpulldown menus presented upon execution of a flow with TraceDisplay. Icon or menu choice allow you the ability to:

• Obtain information about the traces in the display window.

• Modify the presentation.

• Define processing parameter information.

Topics to be covered in this chapter:

❏ Trace Display

❏ Create and Apply a Parameter Table

3

Chapter 3: Interactivity of Trace Display


Trace Display

When you execute your job, the following display appears:

Trace Display Window

Menu BarIcon Bar

Mouse Help Data Display

Trace Header Plot

Active Icon



Icon Bar

The following is a brief description of the Trace Display icons, locatedalong the side border:

• Next ensemble: Show the next ensemble. When there is no moredata in the flow, the icon will turn gray and become inactive. InProMax, an ensemble is a collection of traces, such as a shot recordor CDP gather. Each ensemble is flagged with an end of ensemblemark in the trace header (END_ENS).

• Previous ensemble: Show the previous ensemble. When at thebeginning of the flow, this icon is gray and inactive.

• Rewind: Return to the first ensemble.

• Save Image: Save the current screen image. Annotation and pickedevents are saved with the trace data.

• Animation: Brings up the Animation dialog box to review the savedimages. This button is active only when there are at least two savedscreen images. You have the option to cycle through the selectedscreens at a chosen rate. These are just screen images, you cannotedit parameter files using the saved image.

• Paintbrush: Allows you to "paint" trace kills, reversals and mutesinteractively on the screen after they have been picked.

• Zoom Tool: Click and drag using MB1 to select an area to zoom. Ifyou release MB1 outside the window, the zoom operation iscanceled. If you just click MB1 without dragging, this tool willunzoom. You can use the zoom tool in the axis area to zoom in onedirection only.

• Velocity Tool: Displays linear or hyperbolic velocities. For a linearvelocity, click MB1 at one end of a waveform and drag the redvector out along the event. A velocity is displayed at the bottom ofthe screen. Use MB2 to display a hyperbolic velocity by anchoringthe cursor at the approximate zero offset position of the displayedshot or CDP. Drag the red line along the event and read the velocityat the bottom. New events can be measured with either velocityoption by reclicking the mouse on a new reflector and re-anchoring



the starting point. Velocities can be labeled by using MB3 on thecurrent velocity. Geometry must be assigned to successfully usethis icon.

• Header Tool: Displays detailed information about trace headers andtheir values for each individual trace. Click MB1 on any trace tocall up the header template. If the header template is in the way ofthe traces being viewed, you can move the template by dragging thewindow. To remove the template click on the header icon or on anyother icon.

• Annotation Tool: When active you can add, change, and delete textannotation in the trace and header plot areas. The pointer changes toa circle when it is over text annotation. You can move an annotationby clicking and dragging MB1, or add new annotation by clickingMB1 when the pointer is not over an existing annotation. When thepointer is over an existing annotation, click MB2 to delete the textor MB3 to edit the text or change its color.

Menu bar

File has five options available in a pulldown menu. You can save yourpicks, move to the next screen, make a hardcopy plot or exit TraceDisplay. You have two choices when you exit. You can exit and stop theflow, or you can exit and let the flow continue without Trace Display.

Note: Use caution when using the stop option. For example, you useDisk Data Input to read in ten ensembles with a Disk Data Output and aTrace Display. If you execute this flow and use the Exit/Stop Flowoption after clicking through the first five ensembles, then you willactually output five ensembles in the output dataset as opposed towriting out ten ensembles.

View has five options in a pulldown menu. You can control the tracedisplay, the trace scaling, and trace annotation parameters. You can alsochoose to plot a trace header above the trace display and edit the colormap used for color displays.



Animation saves screens, or displays previously saved screens in anyorder and different swap speeds.

Picking for Parameter Tables

Picking inputs values into one or more of the parameter tables. You canstore the primary and secondary header values into a kill trace or reversetrace table. You can pick any kind of mute, horizons, gates, orautostatics horizons. You can also edit database or header values.



For example, to create a parameter table file with a list of traces to kill,click on Picking and a menu of parameter table choices appears. Clickon Kill traces. Another window appears for selecting a previous killparameter file or creating a new file.

When you create a new file, another window appears listing traceheaders to choose from for a secondary key.



In this case, an appropriate key for killing traces would be CHAN,allowing selection of each individual trace within each shot record.Depending upon the parameter table you are using, the most appropriatesecondary header should appear at the top of the list.

At this time a Picking Tool icon will appear on the side of the TraceDisplay screen below the other icons.

• Picking Tool: This appears when one or more pick objects from thePicking menu are selected. A small window with the file name willappear on the right hand side of the screen. This means the file isopen and ready to be filled with the primary and secondary keyvalues of killed traces. When active, click on MB1 to pick a pointon a trace or click and drag to pick a range of traces. When themouse is over a picked point, the pointer shape changes into acircle. Click and drag using MB1 to move a picked point. Use MB2to click on a single point to delete it, or click and drag over a rangeof points to delete them. Click MB3 for additional picking options.Holding MB1 down and dragging it across several traces allows fora consecutive number of traces to be added. To select traces fromthe next shot use the Traffic light icon. The created Kill traces fileremains open and waiting for more traces to be added to the file.

To create a new parameter table such as a reverse traces file, use the Pickicon again and select Reverse traces from the menu. After creating a newfile with a new name, choose a secondary key of CHAN. The new filename appears in the small window on the right hand side of the screenbelow the kill traces file name. The kill traces file is no longerhighlighted, meaning that it is inactive and the reverse traces file ishighlighted. If you have chosen traces to kill and reverse on the screen,the active parameter file will have the chosen traces overplotted with ared line. The traces chosen for the inactive table(s) will be overplottedin blue. This helps you distinguish which file is active and which file isinactive. Traces are only added to the active file. Select or delete tracesin the same manner using the mouse button helps at the bottom. To goback to adding to the kill traces file, click on the kill file and use MB1to toggle that file to active. The reverse traces file table is no longerhighlighted in black and any reverse traces picked on the screen areoverplotted in blue.

Some parameters require a top and a bottom pick, such as a surgicalmute. Once you have picked the top of the mute zone, click MB3anywhere inside the trace portion of Trace Display. A new menuappears allowing you to pick an associated layer (New Layer). You canalso snap your pick to the nearest amplitude peak, trough or zerocrossing.



Miscellaneous time gates are parameter tables used for such proceduresas picking a window for a deconvolution operator design gate orwindows for time variant filtering or scaling. For this exercise pick adecon design gate with a secondary key of AOFFSET. Picking amiscellaneous time gate is also done in two steps. First, pick the top ofthe gate by selecting points to be connected with MB1. BecauseAOFFSET is the secondary key, the picks at the corresponding offset onthe opposite side of the shot will be displayed if you click MB3 in thedisplay field and choose Project from the popup menu. Then use MB3to select an associated layer for the bottom half of the gate. In order topick another time gate, below or overlapping the previous, continue touse MB3 to pick tops and bottoms. Time gates must always be picked inpairs, otherwise your job may fail. Each time gate pair is also shown inthe legend box.



Create and Apply a Parameter Table

Parameter tables are generated when you interactively define lists ortables of information. These files are stored in binary format and areintended for use in subsequent processing flows. Interactivity of TraceDisplay allows you to generate files, such as first break mutes, decondesign time gates, lists for zeroing or reversing traces in a record. Youmake a parameter selection while viewing the data.

ExerciseThis exercise describes the way to pick a top mute. Other parametertables may be picked in the same fashion. Trace kills, trace reversals andmiscellaneous time gates were discussed in the previous section.

1. Build this flow:

2. Read the file we created in the last exercise.

This file should exist in your own line.

3. Insert an Automatic Gain Control process for cosmetics.

4. Parameterize Trace Display to display 80 ensembles per screen.

This VSP data has 3 traces per shot and there are a total of 80 shotsin this project.

5. Set the primary annotation to be FFID instead of SOURCE.


Editing Flow: 01- Pick Parameter Tables


Disk Data InputAutomatic Gain ControlTrace Display

Number of ENSEMBLES(line segments)/screen--------80

Primary trace LABELING header entry-----------------FFID‘



The interactive Trace Display window appears.

7. Click the Picking pulldown menu and choose Pick Top Mute.

Since you have not previously created a top mute table, enter a newtable name called Top Mute. A select Secondary key windowappears.

8. For this dataset, select FFID for the trace header entry.

The mute times that you pick will be interpolated as a function ofFFID. This is a relatively unique relationship for VSP data thatdiffers from surface seismic.

9. Pick a mute.

Turn on the Picking tool icon and pick a top mute to remove theenergy above the first arrivals. Select only a few traces on the recordbecause points will be connected and interpolated as well asextrapolated.

Click MB3 in the display field and choose Project from the popupmenu to display the picks at the intermediate FFIDS that were notexplicitly picked.

NOTE: all of the traces at the same FFID will get "X"’ed as theproject interpolates the points.

You may also elect to press the "Paintbrush" icon and interactivelyapply the mute on the display.

10. Exit and Stop the flow.

To exit, click on File pulldown menu and select Exit/Stop Flow. Ifyou choose to exit, you are prompted to save or not save the workyou have completed. Save this mute so that we can re-apply it via theTrace Muting Process.



11. Edit your previous flow by inserting Trace Muting.

12. Click on Invalid to select the type of mute to apply (Top) and themute parameter file (Top Mute).

In ProMAX, each type of parameter table has its own separate list,such as mute tables, kill trace tables, velocity tables. When selectingthe mute parameter file, you are taken to a list of parameter files forMute Gates.


Notice the effect Trace Muting has on your data. Also, be aware thatthis effect is not permanent since you have not created a new diskdata file with Disk Data Output.

Editing Flow: Display Gathers


Disk Data InputTrace Muting

Type of Mute:------------------------------------------------------- Top

SELECT mute parameter file: --------Your mute file nameAutomatic Gain ControlTrace Display




Chapter

Parameter Selection and Analysis

ProMAX contains a suite of processing modules which provide the userwith convenient, yet flexible parameter testing and data analysiscapabilities. The modules developed to facilitate parameter selection arefound in the process list category called Flow Control. Parameter testingis broken down by type: manual and automatic. Manual parametertesting refers to the use of IF-ELSEIF-ENDIF conditional processingsequences to define a particular test scenario, whereas automaticparameter testing refers to using the Parameter Test module.


❏ Parameter Test

❏ IF/ENDIF Conditional Processing

❏ Interactive Spectral Analysis

4

Chapter 4: Parameter Selection and Analysis


Parameter Test

The Parameter Test process provides a mechanism for testing simplenumeric parameters by creating multiple copies of input traces andreplacing a key parameter in the next process in the flow with specifiedtest values. It automatically expands the processing flow, creating IFconditional branches for each test value. The output consists of copiesof the input data with a different test value applied to each copy.

Parameter Test creates two header words. The first is called REPEAT.This is the data copy number and is used to distinguish each of theidentical copies of input data. The second is called PARMTEST and isan ASCII string, uniquely interpreted by the Trace Display processes asa label for the traces.

ExerciseIn this exercise, you will use Parameter Test to compare shot gatherswith different AGC operator lengths.

1. Build the following flow:

2. Read the file that we wrote to your line after reading the SEGY file.

Sort the input to have a primary sort order of CHAN and a secondaryof FFID. Get channel 1 only for all FFID’s

Editing Flow: 02- Parameter Test Example


Disk Data Input


Select secondary trace header entry---------------------FFID

Sort order list for dataset -------------------CHAN:FFID 1:*/Parameter Test

Enter Parameter Values: ---------------------250|500|1000

Trace Grouping to Reproduce: ----------------------EnsembleAutomatic Gain Control

AGC operator length: ----------------------------------------99999Trace Display



3. Specify Parameter Test test values.

Type in a list of parameter values for AGC operator lengths, eachseparated by a vertical bar ( | ). To determine the format (real,integer, sequence) and a realistic range of test values, look at thedefault value in the AGC process, in this example the AGC operatorlength. (Try values of 250, 500 and 1000 ms.).

We will reproduce by ensembles.

4. Replace the AGC operator length default value with five nines(99999).

99999 is a flag telling Parameter Test which parameter you aretesting.

5. Use Trace Display to present the results from the test to the screen.

We will have 3 original ensembles each copied 4 times. This gives atotal of 12 ensembles.


After the Trace Display appears, you can use the zooming andscrolling capabilities to move through the ensembles.

7. Exit and Stop the flow.

8. Select View from the flow builder menu to look at the processesthat were executed in your flow.

Near the bottom of the job.output file is a listing of the executedprocesses as shown below. There are some additional processes inthe flow and Parameter Test is absent because Parameter Test is amacro, built from other processes.

DISKREAD2

REPEAT

FLOW_IF

AGC

THDRMATH

FLOW_ELSEIF



AGC

THDRMATH

FLOW_ELSEIF

AGC

THDRMATH

FLOW_ELSEIF

THDRMATH

FLOW_ENDIF

ST_TRACE_DISPLAY

In the next exercise we will build a flow similar to this manually tosee how these components communicate with one another.



IF/ENDIF Conditional Processing

Automatic parameter testing is not always an option. It can only be usedwhen the testing parameter is a simple numeric value, such as theautomatic gain control operator length, or a sequence of numerics, as inthe case of corner frequencies used to define a bandpass filter. Whenyour testing requires evaluating multi-level tests, or comparing non-numeric parameters, such as a fan filter option instead of a polygon filteroption in FK Filter, then manual testing must be used.

In order to manually test parameters you must:

• generate multiple copies of the data

• split or branch your processing stream so that each copy of the datamay be processed with different parameters.

One method of generating multiple data copies is to use the ReproduceTraces process. This process is included in the Parameter Test macro.

Reproduce Traces generates a specified total number of copies andappends a header word to each trace, allowing you to distinguishbetween the multiple versions of data. This header word is known asRepeated Data Copy Number or REPEAT for short. It is a numeric valuefrom 1-N, where N is the total number of generated copies. You shouldconsider placing Reproduce Traces after any processing which iscommon to all copies of the data, but prior to the processes you wish tocompare.

Splitting or branching the flow is a conceptual term for controlling theprocesses your dataset utilizes. In other words, you do not actually breakup any single flow into separate flows, rather utilize the capability of theIF, ELSEIF, and ENDIF processes to select and direct traces forprocessing. This is handled automatically by the Parameter Testprocess, as you saw if you looked at the View information when youexecuted the previous flow.

More specifically, each copy of the data is passed to a different process,or the same process with different parameter selection using a series ofIF, ELSEIF and ELSE processes in the flow. For example, if the datacopy number (REPEAT) is 1, then pass that copy of the data to the nextprocess. If the data copy number is 2, pass that copy to a differentprocess, and so on until all copies of the data have been passed to uniqueprocesses. The series of conditions is ended with ENDIF.



Finally, you may use a process called Trace Display Label to generate aheader word for posting a label on the display.

ExerciseIncorporate Reproduce Traces with IF and ENDIF to compareprocessed and unprocessed data. In this exercise, we will compare thefirst shot of the AGC dataset to a version with true amplitude recovery.It is always a good idea to have a control copy, the original input, forfurther comparison. This flow illustrates how to compare these threecopies.



Editing Flow: 03 - IF/ELSEIF Conditional


Disk Data Input



Sort order list for dataset -------------------CHAN:FFID 1:*/Reproduce Traces

Trace grouping to reproduce: ----------------------Ensembles

Total Number of datasets: ----------------------------------------3IF

SELECT Primary trace header word:-----------------Repeat

SPECIFY trace list:----------------------------------------------------1Automatic Gain ControlTrace Display Label:-------------- AGC

ELSEIF

SELECT Primary trace header word:-----------------Repeat

SPECIFY trace list:----------------------------------------------------2Trace EqualizationTrace Display Label:--------------- EQ

ELSETrace Display Label:-------- Original Input

ENDIFTrace Display



Sort the input to have a primary sort order of CHAN and a secondaryof FFID. Get channel 1 only for all FFID’s

3. In Reproduce Traces, enter 3 for the total number of datasets.

You will generate two additional copies, one ensemble (record) at atime.

4. Select Repeat for Select Primary trace header word in IF andELSEIF.

IF acts as the gate keeper, providing the mechanism for selecting orrestricting traces which will be passed into a particular branch of theflow. Header words are used (just as in Disk Data Input) to uniquelyidentify the traces to include or exclude in a particular branch.

In the first IF conditional, select REPEAT as the primary traceheader and 1 (copy number) as the trace list entry. Data copy 1 ispassed to AGC in this example. The ELSEIF condition passes thesecond data copy number (REPEAT=2) to Trace Equalization.

The ELSE process selects all traces, not previously selected with IFor ELSEIF. In our case, having selected two of the three copies ofdata for filtering, leaves only the third data copy (REPEAT=3) forthe ELSE branch. In this example, no additional processing isapplied to this copy. It is the control copy.

5. Use Trace Display Label to create labels for each copy.

Label the copies according to their unique processing. For example,label the first copy with AGC, the second with EQ and the final copywith Original Input.

6. Select to use a hand input design gate for the Trace Equalizationand use the default parameters.

7. Modify Trace Display to do each of the following in two differentexecutions:

• each copy on different screens and use screen swapping

• all records on same screen.



Interactive Spectral Analysis

Interactive Spectral Analysis computes and displays power, phase andF-X spectra estimates for interactively selected subsets of traces. Thesedisplays can be configured both interactively and from the ProMAXmenu.

There are three modes of data selection:

• Simple Selection: Analyzes only the displayed traces. During theinteractive session you may analyze new traces by choosing NextData from the Data menu.

• Single Subset Selection: Enables you to interactively select arectangular subset of the data for spectral displays. The spectraldisplays are automatically updated for each new rectangleselection.

• Multiple Subset Selection: Displays at least two windows: a DataSelection Window and one or more Spectral Analysis windows.Subsets for Spectral Analysis are chosen from the Data SelectionWindow, using the selection tool from the toolbox. A SpectralAnalysis window for the current selection is made by selectingSpectral Analysis from the Data Analysis menu. By default, theSpectral Analysis window updates itself for each new selection.You can freeze the subset in the Spectral Analysis window so that itdoes not update with new selections. This allows spectra fromdifferent subsets to be compared.

ExerciseIn this exercise you will run Interactive Spectral Analysis in the simplemode.



1. Build this flow.


Sort the input to have a primary sort order of CHAN and a secondaryof FFID. This yields only channel 1 for all FFID’s.

3. Select Interactive Spectral Analysis parameters.

Select the Simple mode and bring in traces by ensemble.

Select to process 1 ensemble per analysis location Also set theprimary annotation to Recording Channel Number and thesecondary annotation to FFID so that the traces do not overlay oneanother.


A Simple Spectral Analysis window appears, displaying your data inT-X, F-X representation, power and phase spectra. Now we will lookat the choices available across the top of the menu: File, Data,Options and Window.

5. Select View/Visibility and select Data window.

Editing Flow: interactive spectral analysis


Disk Data Input



Sort order list for dataset ------------------------------------ 1:*/Automatic Gain ControlInteractive Spectral Analysis

Data selection method?:------------------------------------Simple

Display data by traces or ensembles?:--------Ensembles

Number of ensembles per analysis location?:-------------1

Primary header for sorting and trace label?:-------CHAN

Secondary header for sorting and trace label?:-----FFID



There are many different displays that you can interactively turn onand off. Remember that you have control of your display when youare selecting parameters.

6. Select Options/PreFFT Time Window, and turn on the Boxcar.

You have a lot of control from within the interactive session tomodify your analysis.

7. Activate the Zoom icon to enlarge the trace data.

In this case, your F-X spectrum is zoomed as well.

8. From the File pull down select to Exit and Stop the flow.

Exercise1. Rerun the flow after changing to Single Subset mode.

2. Click on the Select Rectangular Region icon to window the data onthe leftmost (large) shot display.

3. Select a range of data from the left hand window over which to dothe analysis.

Use MB1 to start the rectangle and MB1 again to end the window.



Disk Data Input



Sort order list for dataset ------------------------------------ 1:*/Automatic Gain ControlInteractive Spectral Analysis

Data selection method?:-------------------------Single Subset

DIsplay data by traces or ensembles?:--------Ensembles

Number of ensembles per analysis location?:-------------1

Primary header for sorting and trace label?:-------CHAN

Secondary header for sorting and trace label?:-----FFID



Now the trace data in the top middle of the screen is the subset ofdata you just defined with the corresponding spectra also displayed.

4. Click on the Select Rectangular Region again.

5. Click MB2 inside the zoom window on the left data displaywindow to drag the box to another location and click MB2 again toredisplay the zoom window.

6. Try resizing the selection window with the other mouse buttonoptions.

7. From the File pulldown select to Exit and Stop the flow.



Exercise1. Rerun the flow after changing to the Multiple Subset mode.

Your 80 traces will appear in a window.

You may find that iconifying the ProMAX User Interface makes iteasier for you to manage the windows you create in this session.

2. Activate the Select Rectangular Region icon to window the data ondisplay.

Choose an analysis region by drawing a rectangle beginning andending with MB1 clicks.

3. Select Analysis Options and then Spectral Analysis.

This produces a Spectral Analysis window.

4. Choose another window on the data display.

This changes what is displayed in the Spectral Analysis window.

5. Select Data and Freeze selection from within the Spectral Analysiswindow.

6. Choose a new window on the data display and select AnalysisOptions and Spectral Analysis.

This will use your last rectangular region to create a second SpectralAnalysis window. This capability enables you to compare spectrafrom different windows.

7. From the File pulldown select to Exit and Stop the flow.



Disk Data InputAutomatic Gain ControlInteractive Spectral Analysis


Chapter

Real Dataset Information

Most of the exercises in this manual will use a real dataset. This datasethas already been vertically stacked so that there is only 1 shot for eachdepth position. The following information provides you with the neededinformation to build the geometry spreadsheet and database, and preparethe job flows in the exercises.


❏ VSP Real Dataset Geometry

5

Chapter 5: Real Dataset Information


VSP Real Dataset Geometry

Source type: Vibrator

Number of Sweeps per receiver location: 1

Number of Receivers: 1

Number of components: 3

• channel 1: vertical component

• channel 2: primary horizontal

• channel 3: secondary horizontal

Number of recording levels: 80

Depth of first record: 12100 ft.

Depth of last record: 8150 ft.

Depth increment: 50 ft.

Source offset from hole: 500 ft.

The bore hole is vertical with no deviation

Source elevation: 0 ft.

Datum elevation: 0 ft.

Assume the Kelly Bushing is also at 0 ft. for simplicity

Source is at station 1

Receivers are at stations 2-81



Geometry Diagram

12100 ft

8150 ft

recordinglevelincrement= 50 ft

surface elevationand Kelly Bushing elevation= 0 ft

source location500 ft east of thewell

each level has a three componentrecording tool

1

2

3




Chapter

View Input Data

This is our first look at the input data. There are 80 FFIDs, eachconsisting of 3 channels. Channel 1 is the vertical trace, channels 2 and3 are the two horizontal traces situated orthogonal to one another. Thetraces are approximately 3400 ms in length.


❏ Display the Input Data

❏ Write Dataset To Disk in Your Area

6

Chapter 6: View Input Data


Display the Input Data

ExerciseIn this exercise we will simply view the traces and look at the trace headers to familiarizeourselves with the data.

1. Build the following flow to look at the input data and trace headers:

2. You will read a SEGY file as described by the instructor.

Read all available traces. There are 3 traces per shot ensemble and80 ensembles.

3. Apply an AGC scaler for cosmetics.

4. Display the data and view the trace headers.

Set the Trace Display to plot 80 ensembles and annotate each FFIDand channel.

Which trace headers have values?

Editing Flow: display the input data


SEGY Input

Type of storage to use: ----------------------------- Disk Image

Enter DISK file path name: -----------------------------------------------------------------------/misc_files/vsp/vsp_segy

MAX traces per ensemble: ----------------------------------------3

Remap SEGY header values -----------------------------------NoAutomatic Gain ControlTrace Display

Number of ENSEMBLES /screen -----------------------------80

Primary trace LABELING ------------------------------------ FFID

Secondary trace LABELING ------------------------------- Chan



Write Dataset To Disk in Your Area

Exercise1. Expand the previous flow to write the dataset to disk in your own

area for future processing.

2. Write the file to disk in your own area.

3. Make sure you toggle the AGC and the Trace Display inactive.

4. After the flow is complete go to the datasets list and press MB2 onthe dataset name that you just created.

It should have 80 ensembles and a total of 240 traces.

Editing Flow: display the input data


SEGY Input

Type of storage to use: ----------------------------- Disk Image

Enter DISK file path name: -----------------------------------------------------------------------/misc_files/vsp/vsp_segy

MAX traces per ensemble: ----------------------------------------3Remap SEGY header values -----------------------------------No>Automatic Gain Control<>Trace Display<Disk Data Output

Output Dataset -------------------------------shots - input data




Chapter

VSP Geometry

VSP Geometry Assignment takes advantage of the simplicity of thespatial relationship between the source and receiver positions in VSPdata. This helps to minimize the input required to describe the geometry.

Some VSP data is very complex and incorporates a lot of variedinformation to describe the geometry. Some holes are deviated(crooked) and you may have inclination and azimuth information at allrecorded depth levels. In these cases you may also have two sets ofdepth information: log depth and vertical depth. The Spreadsheets havebeen written to handle all such information.

Our case is very simple, using a non-deviated hole.


❏ Assign VSP Geometry

❏ Quality Control Plots from the database

❏ Load Geometry to the trace headers

7

Chapter 7: VSP Geometry


Assign VSP Geometry

In this exercise you will describe the source and receiver coordinate anddepth information, define the field recording channel geometry, anddescribe the shot to receiver group relationships using the spreadsheets.

Exercise1. Build a flow to Assign VSP Geometry.


The following window will appear:

Fill in each of the Borehole, Patterns, and Sources spreadsheets inthis order.

The Borehole spreadsheet describes the X, Y and Z information ofthe borehole.

The Patterns spreadsheet describes how many channels wererecorded and the orientation of these channels.

The Sources spreadsheet describes the X, Y and Z information forall of the source locations and relates the recorded FFID informationwith a given source and spread reference position.

Editing Flow: Spreadsheet / Geometry


VSP Geometry Spreadsheet*



3. Open the Borehole spreadsheet by clicking on “Borehole” on themain menu.

In this case we have a straight, vertical borehole. The log depths arethe same as the elevations, except that they are all positive numbers.All x,y values will be defined at 0.0 and 0.0.

4. Define the borehole with two sets of X,Y, and Z coordinates.

5. Exit from the Borehole Spreadsheet.

6. Open the Patterns Spreadsheet by clicking on “Patterns” on themain menu.

There is only one pattern for this geometry.

The Grp Int column specifies the separation between the specifiedrecording channels in the borehole.

The Offset column specifies a shift to apply to the “chan from”channel relative to the depth listed in the sources spreadsheet.

In this case we have three channels all at the same depth. You willdefine the exact depth for the receivers for each shot.

7. Exit from the Patterns Spreadsheet.



8. Open the Sources Spreadsheet by clicking on “Sources” on themain window.

9. We have a total of 80 shots in this VSP, so the first thing to do isexpand the sources spreadsheet to 80 rows.

Mark the last card as a block with MB1 and MB2 and then use theedit pull down to insert the required number of cards.

10. Number the Sources and FFIDs starting at 1 and incrementing by 1.

11. All shots are at shot station number 1 and at an elevation of 0.0 ft.

12. X,Y values are defined at 500.0 and 0.0 respectively.

13. All shots use the same pattern (1) and have 3 channels.

14. The pattern reference depths start at 12100 and decrement by 50 ft.for each shot.

15. Exit from the Sources Spreadsheet

The next steps in the geometry definition process are to define thepseudo CDP binning and to finalize the database.

NOTE:

For documentation purposes, the columns have been re-ordered slightly. Alladditional columns are filled with 0.0



This is a 3 step process.

16. Open the Bin menu and select to Assign trace geometry by patterninformation.

17.

18. With the Assign option selected, click on the OK button.

You should see several window related to Assigning VSP geometrybased on patterns flash by fairly quickly. The last window will saythat the geometry has been successfully assigned.

19. Dismiss the Status window by clicking on OK.

20. Compute the Pseudo Common Depth points.

Bin starting at CDP 1, starting at 0.0 ft. and ending at 12100 ft.incrementing by 50 ft. per bin.

21. Click on the OK button.

Again you should see several window flash by ending with a windowindicating that the binning was completed successfully.

22. Dismiss this window by clicking on the OK button.

23. Finalize the database.



This step completes building the look up tables and other databasefinalization functions.

24. Select the Finalize Database option and click on the OK button.

You should see a window indicating that the VSP geometryfinalization has completed successfully.


26. Click on the Cancel button in the binning dialog box to dismiss thiswindow.



Quality Control Plots using the XDB database tool

2D plot of TRC vs. Receiver elevation and log depth

• used to check depth assigned to each trace

2D plot of SRF vs. elevation

• used to check depth assigned to each receiver station

2D plot of TRC vs. various other values

• used to check additional information for each trace



Load Geometry to the trace headers

Exercise1. Build the following flow to install the Geometry information into the

trace headers:

2. Input the file that we previously wrote to your own areas afterreading the SEGY data.

3. Select VSP Inline Geom Header Load parameters.

Since you did not use the Extract Database Files process you mustassign the geometry to the trace headers by referencing the FFID anddefault of recording channel.

You do not have valid trace numbers.

Editing Flow: load geometry to headers


Disk Data Input

Select dataset----------------------------------shots - input data

Trace Read Option--------------------------------------------Get AllVSP Inline Geom Header Load

Primary header to match database --------------------- FFID

Secondary header to match database ---------------- None

Match by valid trace number?---------------------------------No

Verbose Diagnostics?----------------------------------------------NoTrace Header Math

Select Mode ------------------------------- Fixed equation mode

Define trace header equation ------------- geo_comp=chanDisk Data Output

Output Dataset Filename-------------- “shots - with geom”

New, or Existing, File?------------------------------------------New

Record length to output--------------------------------------------0.

Trace sample format------------------------------------------16 bit

Skip primary disk Storage?-------------------------------------No



4. Create the GEO_COMP trace header word.

In Trace Header Math, create a trace header word calledGEO_COMP, which is equivalent to recording channel number. Formulti component VSP processing we need to be able to distinguishbetween the vertical and two horizontal components by a geophonecomponent header word.

Component 1 is the vertical trace. Component 2 is the primaryhorizontal and component 3 is the other horizontal. By conventionhorizontal 2 is 90 degrees clockwise from horizontal 1 looking fromthe top.

5. In Disk Data Output, output a new file.

Since there are no valid trace numbers, we cannot do trace headeronly processing in an overwrite mode.

Exercise

This exercise QCs the headers.

1. Build a new flow to re-read the data and plot it to check the newvalues in the trace headers

2. Input the traces with the new geometry and check the headers withthe Header Dump capabilities in Trace Display.

Plot 80 ensembles and annotate each FFID and every 12th receiverelevation.

Editing Flow: qc geometry load


Disk Data Input


Trace Read Option--------------------------------------------Get AllTrace Display

Number of ENSEMBLES per screen --------------- 80

Primary trace LABELING ------------------------------------ FFID

Secondary trace LABELING ----------------------- REC_ELEV

INCREMENT for Secondary annotation ------------------- 12



You should see the correct shot X value, and receiver elevationvalues.

.

NOTE:

The receiver depths go into receiver elevation not receiver depth.


Chapter

Keep Vertical Component Traces

Although most VSPs are recorded using multi-component instruments,in the majority of cases only the vertical component traces are actuallyused. In order to minimize our disk requirements, we only want to keepthe traces that we are actually going to process. In this exercise we willrun a job that will keep only the vertical traces for further processing.

We will keep the original data (with all 3 components) for some otherexercises later in the class.

A good question to ask here is:

“What is the best sort order to build the most efficient ensemble forfuture processing?”


❏ Create Vertical Component Dataset

8

Chapter 8: Keep Vertical Component Traces


Trap Vertical Traces

Exercise1. Build the following flow to keep only the vertical traces.

Sort the input data on CHAN/FFID and only keep channel 1 for allof the shots.

If we make an ensemble of only channel 1, then we can alwaysdefault the Trace Display to plot all traces in 1 ensemble instead ofhaving to change it to 80 and worry about ensemble gaps and displaylabel issues.

2. In Trace Length, limit the amount of data to be processed to 2000ms.

3. Display the resulting dataset and if satisfied, write the output todisk.

Editing Flow: 03 - trap vertical traces


Disk Data Input


Trace Read Option-------------------------------------------- SORT

Interactive Data Access ----------------------------------------- No

Select primary trace header ----------------------------- CHAN

Select secondary trace header ---------------------------- FFID

Select tertiary trace header ------------------------------ NONE

Sort order list for dataset ------------------------------------ 1:*/

Presort in memory or on disk? ------------------------ MemoryTrace Length

New trace length ----------------------------------------------- 2000>Disk Data Output<Trace Display

Number of ENSEMBLES per screen -------------------------- 1

Primary trace LABELING ---------------------------------- CHAN




Plot 1 ensemble. You also may want to change the annotation to beCHAN and then Receiver Elevation.

If you are successful, the Trace Display plot should look as follows:



Output a file with vertical traces only

1. Modify the flow to output a file that contains only the vertical traces.

Editing Flow: 03 - trap vertical traces


Disk Data Input


Trace Read Option-------------------------------------------- SORT

Interactive Data Access ----------------------------------------- No

Select primary trace header ----------------------------- CHAN

Select secondary trace header ---------------------------- FFID

Select tertiary trace header ------------------------------ NONE

Sort order list for dataset ------------------------------------ 1:*/

Presort in memory or on disk? ------------------------ MemoryTrace Length

New trace length ----------------------------------------------- 2000Disk Data Output

Output Dataset Filename------------ “vertical traces only”




Skip primary disk Storage?-------------------------------------No>Trace Display<


Chapter

First Break Picks on VerticalTraces

First Break times are an integral part of the processing of VSP data. Inthis exercise we will pick the first arrival times on the verticalcomponent traces for use in future processing steps.

In the processing of VSP data, first arrival times are used for a varietyof different purposes. These times are used to compute velocityfunctions which are then used by other processes. The first arrival timesare also used as flattening statics for wavefield separation. They are alsoused to convert the VSP data to two way travel time in preparation forCorridor Stack. With all of these uses in mind, it is apparent that the firstarrivals must be accurate.


❏ Pick First Breaks

9


Chapter 9: First Break Picks on Vertical Traces

Pick First Breaks

ExerciseIn this exercise, we will build a flow to display the vertical traces andpick the first arrivals.

1. Build the following flow:.

2. In Disk Data Input, input the previously created file containing thevertical trace.

This file is one ensemble of all traces from channel 1

3. In Trace Display, plot 1 ensemble.

You may also want to set the annotation heading to be CHAN on thefirst line and then plot every 12th receiver elevation on the second.

4. Execute the Flow.

5. Select the Picking pulldown menu, and choose to edit the firstarrivals in the database.

You will be prompted to select a type of attribute. You will writethese first break times to an attribute of type GEOMETRY in theTRC database called FB_PICK.

Editing Flow: pick first arrivals


Disk Data Input

Select dataset--------------------------------vertical traces only



Primary trace LABELING ---------------------------------- CHAN


INCREMENT for Secondary annotation ------------------- 12



6. The Pick editing icon on the left side of the plot will automaticallybe selected for you.

7. Pick the arrivals with the rubber-band and then snap to the desiredphase with MB3.

It is suggested to pick the first strong, continuous peak.

8. Edit any picks as you see fit.

9. Exit the program to save the picks to the database.



QC the First Breaks in the Database using XDB

1. Click on Database in the flow menu. From the resulting DBToolsdialog, click on the Database pulldown and select XDB DatabaseDisplay. Plot the first arrival times from the TRC database and editany bad picks.

Reposition any picks that appear out of line and then save the editedpicks back to the database. This is accomplished using the Database/Save buttons.

Be sure not to move the pick off of the selected trace.

2. If you want, you can re-execute the pick job and then replot theedited picks on the traces for further QC.


Chapter

VSP Velocity Functions

VSP datasets can provide additional velocity information to aid in theprocessing of surface seismic data and provide comparisons with welllog information. Additionally, some processes that can be applied toVSP data require some velocity information. VSP data provides a directmeasurement of average velocity as a function of depth.

The Velocity Manipulation process allows you to generate other typesof velocity fields from this average velocity function which in turnpermits you to generate VSP-CDP transforms and/or migrations of theVSP data.


❏ Generate Average Velocity vs. Depth

❏ QC using Velocity Viewer/Point Editor

❏ Velocity function manipulation

❏ Velocity function smoothing

10

Chapter 10: VSP Velocity Functions


Generate Average Velocity vs. Depth and Smooth

The first arrival times are a direct measure of travel time as a functionof source to receiver distance. This gives a direct measurement of theaverage velocity between the source and receiver.

Exercise1. Build the following flow to compute the average velocity:

2. Parameterize Vel Table From VSP.

Editing Flow: generate avg.velocity function


Vel Table From VSP*

Specify a datum elevation---------------------------------------- 0

Limit source-receiver horizontal offsets ------------------- No

Limit source elevations ------------------------------------------ No

Limit receiver elevations ---------------------------------------- No

Select output AVERAGE velocity file ----------------------------

----------------------------------- from raw first break pick times

Table overwrite options ---------- Overwrite existing table

Time pick Parameter ---------- TRC GEOMETRY FB_PICKVelocity Viewer / Point Editor*

Select the type of field you wish to edit ----------------

------------------------------------------- Average Velocity in Depth

Do you wish to edit an existing table --------------------- Yes

Select the input velocity database entry --------- ------------

----------------------------------- from raw first break pick times

Do you wish to specify the bounds of the field -------- No

Select output velocity database entry --------------------

------------------------------------------------------ smoothed version

Minimum depth (or time) of velocity field ------------------- 0

Maximum depth (or time) of velocity field ------------------ 0



Using a reference datum of 0 ft., generate an average velocity vs.depth velocity table. Do not impose any limits. Input the set of firstbreaks that was picked from the vertical traces and then edited fromthe database.

3. View the output function using Velocity Viewer/ Point Editor.

Select parameters to input the average velocity vs. depth tablecreated from the first arrivals, and output to a new velocity table thatis generated by smoothing the computed function over a depth rangeof 250 ft. (or 5 receiver levels).

In the interactive smoothing parameters, set to output a functionevery 1000 CDPs to ensure that only one function is output. Also setthe depth sampling interval to 50 ft. to match the original inputsampling interval. The CDP smoothing value can be defaulted andset the depth smoothing level to 250 ft.



The following diagram shows the difference between the original, orraw average velocity vs. the smoothed version.


Chapter

VSP True Amplitude Recovery

VSP data is similar to surface seismic data in that it also suffers fromamplitude loss due to spherical divergence and inelastic attenuation.However, one difference is that VSP data generally only travels half ofthe distance relative to surface data because the data we are interested inis recorded directly above the reflecting horizon. This difference iscompensated for in the True Amplitude Recovery process. Sphericaldivergence requires accurate first arrival times in the header and both thespherical divergence and inelastic attenuation corrections require avelocity function. Therefore, TAR cannot be applied until after the firstarrivals have been picked, loaded to the trace headers, and an RMSvelocity function has been generated.

As an alternative to spherical divergence and dB/sec gain recovery, youmay elect to test various time power curves.


❏ RMS Velocity Function generation

❏ True Amplitude recovery tests

❏ Application of True Amplitude Recovery correction.

11

Chapter 11: VSP True Amplitude Recovery


True Amplitude Recovery

In this exercise, you will test the True Amplitude Recovery process foran appropriate dB/sec correction combined with spherical divergence.The spherical divergence correction requires a velocity function whichis generated by converting your average velocity function into an RMSfunction.



Compute an RMS Velocity Function

1. Build the following flow.

Editing Flow: 06- compute RMS from AVG vel


Velocity Manipulation*

Type of velocity table to input ----- Average Vel in Depth

Get velocity table from database entry ------------------ Yes

Select input velocity database entry ---------------------------------------------------from raw first break pick times

Combine a second velocity table ---------------------------- No

Resample the input velocity table? ------------------------- No

Shift or stretch the input velocity table ------------------- No

Type of parameter table to output ----------------------------------------------------------------- Stacking (RMS) Velocity

Select output velocity database entry -------------------------------------------------------------------- from raw average

Spatially resample the velocity table ---------------------- No

Output a single average velocity table -------------------- No

Smooth velocity field --------------------------------------------- No

Vertically resample the output velocity table ----------- No

Adjust Output velocity by percentage --------------------- NoVelocity Viewer / Point Editor*


---------------------------------------------- Stacking (RMS) Velocity



------------------------------------------------------ from raw average



-------------------------------------------------------from raw average





2. Input the average velocity function that was computed from the firstarrival times before smoothing and convert it to an RMS function.You might want to name the output table “from raw average”.

3. Display the output function using the point editor.

4. Rerun the same flow using the smoothed average function that youcreated earlier. Convert it to an RMS function using the option:from smoothed average.

5. Compare the results and look at the values of the RMS function inthe Velocity table editor.




Select input velocity database entry ----------------------------------------------------------------------smoothed version

Select output velocity database entry ------------------------------------------------------------ from smoothed average

Velocity Viewer / Point Editor*


---------------------------------------------- from smoothed average


----------------------------------------------from smoothed average



If you zoom in around a single output point on either plot, you will seethat there are actually two points at each time knee separated by only acouple of ms.

From Raw Average ----------- From Smoothed Average

Comparison of RMS Velocity Functions



6. Edit the Velocity Manipulation* menu to vertically resample theoutput RMS from the smoothed average at a new sample interval of48 ms.

Input the smoothed average function and output a new table andview the results using the Point editor.





Select output velocity database entry -------------------------------------------------------- from smoothed average




Vertically resample the output table ----------------- Yes

Time step sizes for the output table ------------------- 48



---------------------------------------------- Stacking (RMS) Velocity






----------------------------------------------from smoothed average





Test TAR Parameters

1. Build a flow to test various dB/Sec corrections combined withspherical divergence.

2. Input the file with only the vertical traces and process all traces.

Editing Flow: 07 - true amp recovery (test)


Disk Data Input


Trace Read Option--------------------------------------------Get AllDatabase/Header Transfer

Direction of transfer -- Load TO trace headers FROM db

Number of parameters -------------------------------------------- 1

First database parameter --- TRC GEOMETRY FB_PICK

First header entry --------(FB_PICK) First break pick timeParameter Test

Enter parameter VALUES ----------------- 2|4|6|8|10|12

Trace grouping to reproduce ---------------------- EnsemblesVSP True Amplitude Recovery

Apply spherical divergence corrections ---------------- YES

Basis for spherical divergence -------------------------- 1/dist

Apply inelastic attenuation correction --------------------- No

Get TAR velocity from database ---------------------------- Yes

Should the vel be treated as space variable ------------ No

Select the velocity parameter table --------------------------------------------------------------- from smoothed average

Apply dB/sec correction --------------------------------------- Yes

dB/sec correction constant ------------------------------ 99999

Apply time raised to a power correction ------------------ No

APPLY or REMOVE ------------------------------------------- Apply

Maximum application time --------------------------------- 2000Trace Display




3. Transfer the first break times to the trace headers.

4. Produce a comparison of 2,4, 6, 8, 10 and 12 dB/Sec combined witha 1/dist spherical divergence correction.

Use the RMS velocity function that you generated from thesmoothed average and then resampled to every 48 ms.

5. Parameterize Trace Display for the test panels.

We are generating 6 panels plus the control panel, so we will have atotal of 7 ensembles.

We may also elect to set the minimum time of the display to 500msec instead of 0 for the comparison to avoid a lot of dead samplesat the top of the display.

Since we are looking for relative amplitude on these traces, we mayfind that using entire screen scaling will be a better choice thanindividual trace scaling.

6. Produce a second set of test panels varying the time power valuefrom 1.4 to 2.2 by .2 and turning off the SPHDIV and dB/seccorrections.

You must reset the dB/sec correction back to a single number otherthan 99999 and don’t forget to reset the number of ensembles todisplay in Trace Display if you are using this option.



7. After selecting a set of TAR parameters (suggested SPHDIV and 6dB/sec to 2000 ms), process the traces and output a new data filewith TAR applied.

Editing Flow: 07 - true amp recovery (test)


Disk Data Input


Trace Read Option--------------------------------------------Get AllDatabase/Header Transfer

Direction of transfer -- Load TO trace headers FROM db

Number of parameters -------------------------------------------- 1

First database parameter --- TRC GEOMETRY FB_PICK

First header entry --------(FB_PICK) First break pick time>Parameter Test<VSP True Amplitude Recovery

Final Selected ParametersTrace Display Label

Trace Label --------------------------- vertical traces with TARDisk Data Output

Output Dataset Filename-------- vertical traces with TAR




Skip primary disk Storage?-------------------------------------No




Chapter

VSP Wave Field Separation

Corridor Stacks, VSP-CDP transforms and/or migrations are the finalproducts from most VSP processing exercises. These products usuallyconsist of only upgoing reflected energy. The downgoing energy mustbe removed from the total wavefield to uncover the reflected energy. Itis also necessary to isolate the downgoing energy to aid in thedeconvolution process. There are three basic techniques available toseparate the downgoing and upgoing wavefields from the total wavefield. These are Median, FK and Eigenvector Filters.


❏ Flattening the downgoing using the first arrivals

❏ Wavefield Separation using a Median Filter

❏ Wavefield Separation using an F-K filter

❏ Wavefield Separation using an EigenVector Filter.

❏ Wavefield Separation Test Comparisons

❏ Saving the Upgoing to Disk

❏ Saving the Downgoing to Disk

12

Chapter 12: VSP Wave Field Separation


Flatten the Downgoing with F-B Picks

Wavefield separation requires flattening on the downgoing energy. Thisis accomplished by applying first arrival times as static values followedby some trim statics. Therefore, as a prerequisite to wavefieldseparation, first arrival times must be in the database and in the traceheaders.

Exercise1. Build the following flow to apply the first break pick times as a static

to flatten the down going energy.

2. Input the file containing only the vertical component traces after tarhas been applied and process all traces.

Remember that we transferred the first arrival times from thedatabase to the headers prior to applying True Amplitude Recovery.

3. Select Header Statics parameters.

Apply a positive 100 ms Bulk Shift to all the traces and Subtract thefirst arrival time from the trace header as a static.

Editing Flow: 08- wavefield separation


Disk Data Input

Select dataset-------------------------vertical traces with TAR

Trace Read Option--------------------------------------------Get AllHeader Statics

Bulk shift Static -------------------------------------------------- 100

What about previous statics ---- Add to previous statics

Apply how many static header entries --------------------- 1

First header word to apply --------------------------- FB_PICK

How to apply header statics ------------------------- SubtractApply Fractional StaticsTrace Display



4. In Apply Fractional Statics, apply the non-sample period portion ofthe static.

5. Plot the output traces on the screen and check to see that the firstarrivals are approximately flat at about 100 ms.

Set the maximum time of the display to 500 msec.



Flatten with F-B Picks and Event Alignment

Because the first arrival pick times can be somewhat contaminated bynoise, we can estimate trim statics via a cross correlation technique andapply them for additional flattening.

1. Expand the previous flow to add one iteration of event alignment.

2. Select Event Alignment in a Window parameters.

Editing Flow: 08- wavefield separation


Disk Data InputHeader StaticsApply Fractional Statics------------Event Alignment in Window

Maximum allowable static shift ----------------------------- 10

Allowable percentage of hard zeros ------------------------ 55

Method of building model trace ------------ Selective Stack

Ignore end of ensembles? ------------------------------------- Yes

Seek and report reversed traces ---------------------------- No

Accumulate statics in TOT_ALIN ---------------------------- No

Get analysis window parms from Database? --------- No

SELECT Primary header word ---------------------------- FFID

SELECT secondary header word ---------------------- NONE

SPECIFY window analysis parameters ------ 1:50-150/Header Statics

Bulk shift Static ------------------------------------------------------ 0



First header word to apply ------------------------------alinstat

How to apply header statics -------------------------------- AddApply Fractional Statics------------Trace Display



Use a 55 trace Selective Stack model, ignoring end of ensembleissues to estimate static shifts up to 10 ms on a Hand Input window100 ms wide centered on the first breaks [1:50-150/]. Use a primaryheader word of FFID with no secondary header.

3. Read the Event Alignment helpfile to find the name of the attributeto apply in Header Statics and also how to set the yes/no switch forAccumulate Statics in TOT_ALIN.

Set to No for this flow.

4. In Header Statics, ADD a user defined attribute called ALINSTATto any previous statics and apply any remaining fractional statics.

5. Plot the output traces on the screen and check to see that the firstarrivals are flatter than those from the previous exercise.



6. Expand the previous flow to add in a second iteration of eventalignment.

7. In Event Alignment in Window, use a 30 trace Selective Stackmodel, again Ignoring end of ensemble issues.

Use the same gate as the previous execution.

Make sure you properly set the yes/no switch for Accumulate Staticsin TOT_ALIN. Yes in this case.

8. Add the new ALINSTAT statics to any previous statics and applyany fractional remainder.

9. Plot the output traces on the screen and check to see that the firstarrivals are even flatter than those from the previous exercise.

Editing Flow: wavefield separation


Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Statics--------------Event Alignment in Window

Allowable percentage of hard zeros ------------------------ 30

Accumulate statics in TOT_ALIN ----------------------------YesHeader Statics

Bulk shift Static ------------------------------------------------------ 0



First header word to apply ------------------------------alinstat

How to apply header statics -------------------------------- AddApply Fractional Statics--------------Trace Display



Compare Flattening Iterations

1. COPY the previous flow to a new flow to compare all three datasets.

2. Using flow editing techniques, rearrange and expand the existingflow to generate the comparison displays of:

• First Arrivals only

• 1 loop of Event Alignment

• 2 loops of Event Alignment

Editing Flow: 09- compare flattening


Disk Data InputHeader StaticsApply Fractional StaticsReproduce TracesIF <REPEAT=1>

Trace Display LabelELSEIF <REPEAT=2>

Event Alignment in WindowHeader StaticsApply Fractional StaticsTrace Display Label

ELSEIF <REPEAT=3>Event Alignment in WindowHeader StaticsApply Fractional StaticEvent Alignment in WindowHeader StaticsApply Fractional StaticsTrace Display Label

ENDIFTrace Display

Specify Display END time ------------------------------------ 500



3. Display the results using Trace Display.

The three comparison displays should resemble the followingexamples:

You may find that setting the trace display to display 3 verticalpanels will help you do this comparison.



Wavefield Separation with Median Filter

The median filter has proven to be a very effective means of estimatingthe flattened event amplitudes by computing the median amplitude overa series of traces at constant time samples. If the input data is wellflattened and the waveforms are stable, then the median filter shouldperform well. Typically, the amplitudes of consistent events areestimated and then this component is subtracted from the input.



Exercise1. Expand the previous flow to do 2D spatial filtering to estimate and

subtract the downgoing energy.

2. In Parameter Test, test a series of different length median filters.



Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Statics---------------Parameter Test

Enter parameter VALUES ------ 3|5|7|9|11|13|15|19

Trace grouping to reproduce ---------------------- Ensembles2-D Spatial Filtering

Type of 2-D filter --------------------------- Simple 2-D Median

Number of SAMPLES for 2-D filter ---------------------------- 1

Number of TRACES for 2-D Filter ---------------------- 99999

Type of trace edge taper --------------------- Fold edge back

Application mode for 2-D filter ------------------ Subtraction

Minimum number of traces for subtraction ---------------- 3

Steer filters along a vertical dip? ---------------------------- No

Re-apply mutes after filtering ------------------------------- YesBandpass Filter

Default all parameters EXCEPT

Ormsby filter frequency values ------------- 8-12-100-125>Trace Display Label<---------------Trace Display

Number of ENSEMBLES per screen ------------------------ 10



Test values of 3 |5| 7 |9| 11 |13| 15 | 19 for the number of traces in thefilter.

3. In 2D Spatial Filtering, apply a Single Sample, Simple 2D MedianFilter to Subtract the downgoing energy from the total flattenedwavefield.

In the Minimum Number of traces for Subtraction parameter, use aminimum of 3 traces in the filter and fold live traces back over theedge to make sure that there are always enough traces for the filter.

4. Apply a fairly wide open zero phase Ormsby Band Pass filter tosuppress any adverse side effects of the median filter.

For this data at a 4 ms sample rate, apply a filter of 8-12-100-125.

5. Display the results using Trace Display.

You may find that setting the maximum time to display to 700 msprior to display may save you some time in the zooming process.

You may also find that setting the display to plot 5 horizontal panelswill be helpful.

You may also want to reset the Trace Display to do one vertical panelwith 1 ensemble per screen and use the screen swapping capabilitieswithin Trace Display to compare the different results.

6. After selecting the length of filter that works best, rerun the flow toQC the output section.

Toggle the Parameter Test inactive and input the proper filter length(11) in the 2D Spatial Filter process instead of the 99999 for theparm test.



7. Add a Trace Display Label after the Median Filter to annotate thesedata for future reference.

Upgoing Energy Separated by Median Filter



F-K Analysis

Using an F-K filter to separate the input data into various dipcomponents is another very effective means of separating the flatteneddowngoing energy from the dipping upgoing energy, thus separating theupgoing from the downgoing. We can plot the flattened data in the F-Kplane and estimate various fan filters and/or polygonal filters to isolateone of the dip components.

Using the Interactive F-K Analysis process, you can interactively testvarious reject and accept F-K polygons to keep the upgoing anddowngoing.



Exercise1. Expand the previous flow to add an F-K Analysis to pick the fan

filter, or polygon filters to apply.

Note: Toggle the median filter, bandpass filter, and Trace Displaysteps inactive.

2. Select F-K Analysis parameters.

There are 80 traces per panel and the traces are separated by 50 ft.Add a Parameter Table name for the FK-Polygon.

We may elect to use polygon editing or we may just measurevelocities to use a fan function in the F-K filter process.



Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Static>Parameter Test<>2-D Spatial Filtering<>Bandpass Filter<---------------F-K Analysis

DEFAULT all parameters EXCEPT

Panel width in traces -------------------------------------------- 80

Distance between input traces ------------------------------- 50

Select mute polygon table -- reject poly to keep upgoing

Mode of F-K filter windowing ------------------------- REJECT--------------->Trace Display<



3. Use the dx/dt tool to measure the apparent velocity of the up-goingenergy in flattened space on the F-K Analysis section.

The velocity should be about 6700 ft./sec.

4. Pick a positive and negative velocity cut to apply as a fan filter in F-K Filter.

Numbers like -4000 and + 20000 are good choices for a reject filterto keep the upgoing.

You may choose numbers like -20000 and +20000 as an accept filterto keep the downgoing.

Note: If you are working with polygons, be careful about how youset the Accept and Reject options.

5. Generate the Filtered Output panel to QC the polygon andparameters.



Wavefield Separation with F-K Filter

Experiment with different accept and reject fan filters and polygonslooking at the output in F-K Analysis and Trace Display.

1. Expand the previous flow to add an F-K Filter to estimate and rejectthe downgoing energy.

2. Input your velocities as a fan filter and/or try any picked polygonsto Reject the downgoing and keep only the upgoing. Use thedefaults for padding and tapering.



Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Static>Parameter Test<>2-D Spatial Filtering<>Bandpass Filter<---------------F-K Filter

Type of F-K filter ----------------------------- Arbitrary Polygon

Distance between input traces ------------------------------- 50

Panel Width on Traces ------------------------------------------ 80

Select mute parameter file - reject poly to keep upgoing

Mode of F-K filter operation --------------------------- REJECTF-K Analysis--------------->Trace Length<>Trace Display<



Suggested parameters are to use a fan filter of -4000 and + 20000 ft./sec in reject mode. With this velocity the K-space wrap parametershould be set to No. QC the output with F-K analysis.



Wavefield Separation with Eigenvector (K-L) Filter

An Eigenvector Filter essentially decomposes a group of traces into dipcomponents where the number of dip components is related to thenumber of traces in the transform. These dip components are accessedby selecting eigenvector percentages from 0 to 100 percent where thelow percentages are the flatter components. The option exists to eitherkeep the selected percentage or to subtract the selected percentage fromthe input.

Three sets of times are required depending on what options are selected:

• a design gate from which the dip component matrix weights arecomputed

• an application time gate

• an optional subtraction time gate.

In general the application and subtraction gates are the entire time rangeof the data. The design gates should be restricted to a good data zone.For VSP data, this is the area near the first arrivals.

When operating on data that has been flattened on the first arrivals, thelow percentage eigenvectors are the flattened downgoing energy and thehigh percentages are the dipping upgoing. In this exercise you willdesign the eigenvectors over a time window around the first arrivalsusing a fairly short spatial window and then subtract the low percentagevalues from the input to extract the upgoing energy.



Exercise1. Alter the existing flow to use the Eigenvector Filter to separate the

wavefields.

Parameters for Parameter Test and Eigenvector Filter are on the nextpage.....



Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Static>Parameter Test<>2D Spatial Filtering<>Bandpass Filter<>F-K Analysis<>F-K Filter<---------------Parameter TestEigenvector Filter---------------Trace Display



.

Note: Toggle the F-K filter and F-K Analysis inactive in the flow

1. Design a test of the Eigenvector filter over the first arrivals

Use a constant design window for all FFID’s from 0-500 ms andapply a filter over the entire time range (0-2000 ms). Also, subtractover the entire time range from 0-2000 ms. Test values of 3, 7, 11,15, and 19 for the trace window width and subtract the first 10percent of the Eigen images.



---------------Parameter Test

Enter parameter VALUES ------------------- 3|7|11|15|19

Trace grouping to reproduce ---------------------- EnsemblesEigenvector Filter

Mode ----------------------------- Subtract Eigenimage of Zone

Get matrix design gates from DATABASE --------------- No


SPECIFY design time gate ---------------------------- 1:0-500/

Get application gates from DATABASE ------------------- No


SPECIFY application gate -------------------------- 1:0-2000/

Get Subtraction gate from DATABASE -------------------- No


SPECIFY subtraction gate -------------------------- 1:0-2000/

Type of Computation ------------------------------------------ Real

Horizontal window width -------------------------------- 99999

Start percent of eigenimage range ---------------------------- 0

End percent of eigen image range -------------------------- 10

Re-apply trace mutes after filter --------------------------- Yes---------------Trace Display



2. You may want to test various panel widths, design gates, and Eigenimage percentage ranges.

Note that you cannot use the “Parameter Test” sequence to test thepercentage ranges.

3. Try various Trace Display configurations:

1) Each output ensemble individually and then swap the screens.

2) All ensembles on the same screen.

Note that the Eigen Filter is very difficult to test because thepercentage to keep range varies as a function of the length of thefilter.



Wavefield Separation Comparison Test

Exercise1. Expand the previous flow to reproduce the traces and add IF -

ELSEIF - ENDIF statements around the various separationprograms.

2. Based on the value of the Repeat header word, apply all three typesof separation possibilities and compare the results using Trace



Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Statics>Parameter Test<Reproduce TracesIF

2D Spatial FilteringTrace Display LabelBandpass Filter

ELSEIFF-K Filter>F-K Analysis<Trace Display label

ELSEIFEigenvector FilterTrace Display Label

ENDIF>Trace Length<Trace Display



Display.

3. If desired, an AGC or other type of gain function may be applied.

4. Experiment with various display options to compare the resultsfrom the different separation techniques.

• Display each 80 trace ensemble on the screen independently andscroll through them.

• Display all three 80 trace ensembles on the screen at the same time.

• Display all three 80 trace ensembles on the screen in 3 vertical andthen 3 horizontal display panels.

5. Select the method that produces the best results.



Save the Upgoing Energy

Exercise1. Select the method that best isolates the upgoing and then remove the

flattening statics, and trim statics and save the upgoing data.



Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Statics>Reproduce Traces<>Parameter Test<>IF<>2D Spatial Filtering<>Trace Display Label<>Bandpass Filter<>ELSEIF<>F-K Analysis<F-K FilterTrace Display label>ELSEIF<>Eigenvector Filter<>Trace Display Label<>ENDIF<--------------Header StaticsDisk Data Output-------------->Trace Display<



2. Suppose that the F-K Filter was selected as the best option to isolatethe upgoing energy.

3. Comment out all other processes and Add in a Header Statics toRemove the previous statics.

Set the number of header statics to apply to “0”.

4. Add in a Disk Data Output to save the upgoing energy in a file forlater processing.

Note: You may want to toggle the Trace Display inactive for thisexercise to ensure that all traces get processed.

If you leave the Trace Display turned on you will find that thedisplay is not very good because we have returned the data tooriginal recorded time but the display is set for the first 700 mseconly.



--------------Header Statics

Bulk shift static ------------------------------------------------------ 0

What about previous statics -- Remove previous statics


HOW to apply header statics ------------------------------- AddDisk Data Output

Output Dataset Filename------------------- isolated upgoing




Skip primary disk Storage?-------------------------------------No--------------



Wavefield Separation to Keep Downgoing

Exercise1. The same job can be used to determine the best approach to use to

separate the downgoing energy only.

Copy the Wavefield separation flow to a new flow to test the differenttechniques for isolating the downgoing data.

Editing Flow: 10 - test/keep downgoing


Disk Data InputHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsReproduce Traces>Parameter Test<IF

2D Spatial FilteringTrace Display LabelBandpass Filter

ELSEIFF-K Filter>F-K Analysis<Trace Display label

ELSEIFEigenvector FilterTrace Display Label

ENDIF>Header Statics<>Disk Data Output<Trace Display



2. In 2D Spatial Filtering, select to run in Normal mode, theEigenvector Filter to Output the eigenvector filtered zone, and theF-K filter to run in an Accept mode.

Note: You may want to change the fan filter velocities for thisexercise. Values of -20000 to 20000 ft./sec in an accept mode arereasonable.

3. Repeat the various comparison displays and select the methodwhich gives the desired results.

• Display 3 vertical panels limiting the time on each panel to 1100ms.

• Display 3 ensembles on one screen to 2000 ms.



Save the Downgoing Energy

Exercise1. Select one of the separation techniques and leave the flattening

statics applied. Save the downgoing data to disk.

2. Comment out all other processes.

Editing Flow: test/keep downgoing


Disk Data InputDatabase/Header TransferHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional StaticsEvent Alignment in WindowHeader StaticsApply Fractional Statics>Reproduce Traces<>IF<>2-D Spatial Filtering<>Trace Display Label<>Bandpass Filter<>ELSEIF<>F-K Analysis<>F-K Filter<>Trace Display label<>ELSEIF<Eigenvector FilterTrace Display Label>ENDIF<Disk Data Output-------------->Trace Display<



3. Change the dataset name in Disk Data Output to save the downgoing energy for later processing.

4. In this case, also make sure that the Header Statics process istoggled inactive.

Why do we leave the statics applied to the downgoing data?



QC plot of Separated Data

Exercise1. Reread the input, the isolated upgoing data file and the isolated

downgoing data files and plot them together on the screen.

In the Disk Data Input and Insert processes, get three input files: theoriginal input, the separated upgoing with statics removed, and theseparated downgoing with the statics still applied.

2. In Trace Display, select to plot three ensembles.

3. Plot the first break picks on the traces.

They should plot at about the start of the reflection data on theupgoing.

Note: This is meaningless on the downgoing.

Editing Flow: QC Wavefield Separation


Disk Data Input

Select dataset-------------------------vertical traces with TAR

Trace Read Option--------------------------------------------Get AllDisk Data Insert

Select dataset------------------------------------isolated upgoing


Select dataset-------------------------------isolated downgoing




Chapter

VSP Deconvolution

Deconvolution of VSP data involves the generation of an inverse filterdesigned to compress an input wavelet to a zero phase wavelet. Theinput wavelet is commonly extracted from the separated downgoingenergy. A filter is designed to compress this energy into a zero-phasewavelet centered on the first arrival time. This filter is then applied tothe upgoing data to remove the source signature from the reflectionenergy and output a zero phase wavelet at the actual time of thereflection generation interface.

Some design gate determination is commonly performed to isolate thewavelet from which the inverse filter is designed. This design gategenerally starts at zero time, envelopes the first arrivals and progressesin time for a couple of hundred milliseconds. The maximum time of thegate typically comes immediately after the last consistent reverberationof the first arrival.


❏ Picking a design gate

❏ Designing the inverse filter on the downgoing data

❏ Applying the filter to the down-going for Quality Control

❏ Applying the filter to the upgoing data

13

Chapter 13: VSP Deconvolution


Picking the Decon Design Gate

Exercise1. Build a flow to plot the downgoing data and pick a design gate.

2. Input the separated, flattened downgoing data.

3. All of the Trace Display parameters may be defaulted.

4. Using the Pick pulldown menu, select to pick a Bottom Mute to beapplied prior to inverse filter design.

When prompted for a header entry to use for the mute function,select FFID as the header entry over which to vary the mute starttimes. Set the bottom mute to start at about 400 ms.

5. Exit the program to save the mute parameter table.

Editing Flow: 12 - VSP Decon


Disk Data Input





Apply the mute for QC

Exercise1. Expand the previous flow to apply the mute for QC.

2. Apply the mute that was just picked as a Bottom Mute.

3. Display the result.

Editing Flow: 12 - VSP Decon


Disk Data Input


Trace Read Option--------------------------------------------Get AllTrace Muting

Reapply previous mutes --------------------------------------- NO

Mute time reference ---------------------------------------- Time 0

Type of mute -------------------------------------------------- bottom

ending ramp --------------------------------------------------------- 30

EXTRAPOLATE mute times --------------------------------- YES

get mute file from the database ---------------------------- Yes

Select mute parameter file -- decon design bottom muteTrace Display



Deconvolution Filter Design

Exercise1. Build a flow to design the decon filter traces.

2. Input the separated, flattened downgoing data and apply the bottommute to limit the design gate.

3. Select Filter Generation parameters.

After applying a Hanning Window taper over 100% of the inputwavelets (zero percent flat), design and output to disk 1000 msinverse filters where time zero on the input trace is 100 ms and use3% white noise.

4. Plot the output from Filter Generation.

The plotted traces are the actual filters to be applied.

Editing Flow: 12 - VSP decon


Disk Data InputTrace MutingFilter Generation

Filter type ------------------------------------------------------ Inverse

Type of operator ------------------------------------ Time Domain

Percent additive noise factor ------------------------------------ 3

Trace length for the filter trace --------------------------- 1000

Time on input trace representing time zero ----------- 100

Apply taper to input wavelet AND output -------------- Yes

Taper type --------------------------------------------------- Hanning

Percent flat for time window ramping ----------------------- 0

Output filter or filtered wavelet -------------------------- Filter

Spectral plot --------------------------------------------------------- No

Write filter trace to disk ---------------------------------------- Yes

Output dataset name ------------------------------ decon filtersTrace Display



5. In Filter Generation, output the filter traces to a disk file.

Where did the 100 ms in the filter generation come from?



Deconvolution Filter QC

Exercise1. Expand the previous flow to apply the filters and QC the results on

the down going data.

2. Input the separated, flattened downgoing data.

3. Select VSP Deconvolution parameters.

Apply filters that have been mixed over 5 FFIDs and exclude 1 filtertrace on each end. Make sure that the zero reference time of the filteris correct. This should be set to 500 ms. which is the center time ofthe filter traces.

4. Add a label for display

Is the peak of the zero phase wavelet at the correct time?



Disk Data Input>Trace Muting<>Filter Generation<VSP Deconvolution

Dataset where filters are stored -------------- decon filters

Mode of mixing filters -------------------------------------- Mixing

Select header on which to match traces -------------- FFID

Bin Radius ------------------------------------------------------------- 5

Exclude filters at edge of image ----------------------------- No

Time of input filter that represents zero time --------- 500

Reapply mutes after deconvolution ----------------------- YesTrace Display Label

Trace Label ----------------------------- downgoing - decon QCTrace Display



Deconvolution - Application to UpGoing

Once the filter traces have been generated and checked, they can beapplied to the upgoing data to produce a zero phase wavelet at the timeof the reflection events.

Exercise1. Build a flow to apply the decon filters to the upgoing data.

2. Input the separated upgoing data at original recorded time.



>Disk Data Input<Disk Data Input


Trace Read Option--------------------------------------------Get All>Trace Muting<>Filter Generation<VSP DeconvolutionTrace Display Label

Trace Label --------------------------------- upgoing with deconDisk Data Output

Output Dataset Filename---------------upgoing with decon



Trace sample format------------------------------------------16 bitSkip primary disk Storage?-------------------------------------NoDisk Data Input



Select dataset-------------------------------upgoing with decon





3. In VSP Deconvolution, apply the filters that were previouslygenerated.

Mix the filters over 5 FFIDs and exclude 1 filter trace on each end.Make sure that the zero reference time of the filter is correct. Thisshould be set to 500 ms or the center of the filter traces.

4. In Trace Display Label, label this data as being upgoing energywith decon applied.

5. In Disk Data Output, write the deconvolved data to disk.

6. Read the before and after decon files in a Disk Data Input andcompare them with Trace Display.



Spectral Analysis Before and After Decon

Once the deconvolution has been applied we can generate a comparisonspectral analysis of the data before and after decon.

Exercise1. Expand the previous flow to read two files from disk and then do a

spectral analysis on each.

Run a Multiple Subset analysis on one ensemble at a time. UseRecording Channel and FFID as the primary and secondaryannotation levels.

Editing Flow: 13 - spectral analysis


Disk Data Input




Trace Read Option--------------------------------------------Get AllInteractive Spectral Analysis

Data Selection method ---------------------- Multiple subsets

Freeze the selected subset ----------------------------------- Yes

Display data by traces or ensembles --------- Ensembles

Number of ensembles per analysis location -------------- 1

Number of ensembles between analysis locs ------------ 1

Primary header for sorting and label ----------------- CHAN

Secondary header for sorting and label ----- REC_ELEV

Default all remaining parameters--------------------------------




Chapter

VSP Corridor Stack

The Corridor stack is one of the common final products from VSP dataprocessing for zero (or near) offset surveys. This stack can be tied tosurface seismic stack sections to help the processors and interpretersidentify key geologic horizons at known depths to events seen on theseismic section. The corridor stack can also be used to help the drillerspredict what is coming up deeper in the borehole by what is called“looking ahead of the bit”.

There is scope for discussion about how the processing sequence for thecorridor stack is put together. We will first present the sequence usingthe prepared ProMAX macros for simplicity and then we can discussvariations on the processing sequence.


❏ Picking Corridor Mutes

❏ Apply the Corridor Mutes for QC

❏ Produce the Corridor Stack

❏ Splice the Corridor Stack into a Surface Stack

14

Chapter 14: VSP Corridor Stack


Picking Corridor Mutes

Two mutes are required to define the top and bottom of the corridor.

Exercise1. Build a flow to pick the top and bottom mute to define the corridor

to stack.

2. In Disk Data Input, input the deconvolved upgoing data file.

3. Use Trace Display to plot the trace.

You may find that adjusting the minimum and maximum displaytime will help you position your mutes.

4. From the picking pulldown menu, select to define a top mute.

Define the mute to set the Top of the corridor.

When prompted, select FFID as the header entry over which to varythe mute start times.

Note: This mute should be about the same time as the first arrivals.

5. From the picking pulldown menu, select to define a bottom mute.

Define the mute to set the Bottom of the corridor. It is normal tomake the corridor about 100 ms wide.

Editing Flow: corridor stack


Disk Data Input

Select dataset------------------------isolated upgoing - decon

Trace read option---------------------------------------------Get AllTrace Display



Apply the Corridor Mutes for QC

As a second check of the mutes, apply the mutes to the data and displaythe result.

Exercise1. Expand the existing flow to add in two Trace Muting processes.

2. In Disk Data Input, input the deconvolved upgoing data file.

3. In Trace Muting, apply the Top and Bottom mutes.

Editing Flow: corridor stack


Disk Data Input---------Trace Muting

Re-apply previous mutes-----------------------------------------No

Mute time reference------------------------------------------Time 0

TYPE of mute--------------------------------------------------------Top

Starting ramp--------------------------------------------30.

EXTRAPOLATE mute times?----------------------------------Yes

Get mute file from the DATABASE?-------------------------Yes

SELECT mute parameter file-----corridor stack top muteTrace Muting

Re-apply previous mutes-----------------------------------------No

Mute time reference------------------------------------------Time 0

TYPE of mute---------------------------------------------------Bottom

Starting ramp--------------------------------------------30.

EXTRAPOLATE mute times?-----------------------Yes

Get mute file from the DATABASE?-------------------------Yes

SELECT mute parameter file---------------------------------------------------------------------corridor stack bottom mute

---------Trace Display



Do not forget that one is a Top mute and the other is a Bottom mute.

4. Display the result with Trace Display.



Produce the Corridor Stack

In this exercise you will use the VSP Corridor Stack macro to apply themutes and the first arrival times as a positive static. This will shift thedata to two way time. You will then stack the traces. This stack trace willbe copied a number of times to produce the final Corridor Stack dataset.

Exercise1. Expand the existing flow to add in the processes associated with

VSP Corridor Stack and optional enhancement programs.

Parameters for One Way NMO and VSP Corridor Stack are on thenext page.

Editing Flow: 14 -corridor stack


Disk Data Input <GET ALL>>Trace Muting<>Trace Muting<>Trace Display<---------One Way Normal Moveout CorrectionVSP Corridor StackTrace Display LabelDisk Data OutputAutomatic Gain ControlBandpass FilterTrace Display



.

2. Comment out the two trace mutes since they are applied in theCorridor Stack Macro. Also comment out the Screen Display.

MB3 will toggle the processes inactive.

Editing Flow: 14 -corridor stack


One Way Normal Moveout Correction

CDP number for velocity--------------------------------------------1

Direction for NMO application----------------------FORWARD

Stretch mute percentage-----------------------------30.

Apply any remaining static during NMO?----------------Yes

Get velocities from the database?---------------------------Yes

Select velocity parameter file----from smoothed averageVSP Corridor Stack

Ramp time for top mute (ms)-----------------------------------30.

EXTRAPOLATE top mute times?-----------------------------Yes

Get top mute file from the DATABASE---------------------Yes

Select top mute parameter file---corridor stack top mute

Ramp time for bottom mute (ms)-----------------------------30.

EXTRAPOLATE bottom mute times?-----------------------Yes

Get bottom mute file from the DATABASE?--------------Yes

Select bottom mute parameter file--------------------------------------------------------------corridor stack bottom mute

Bulk shift static-------------------------------------------------- -900

What about previous statics?----Add to previous statics

Apply how many static header entries?---------------------1

First header word to apply-----------First break pick time

Header statics application mode---------------------------Add

Method for trace summing----------------------------------Mean

Root power scalar for stack normalization---------------0.5

Number of copies------------------------------------------------------5



3. Apply the One Way NMO correction using the RMS velocityfunction that was generated earlier for the Spherical DivergenceCorrection.

Use the resampled RMS from the smoothed average.

4. In VSP Corridor Stack, apply the Top and Bottom mutes and addthe first arrival times from the header as a static.

Make 5 copies of a mean stack trace. For display purposes, apply abulk shift static correction of -900 ms.

5. Write the Corridor Stack traces to a disk dataset.

6. If desired, add in the AGC and/or Bandpass Filter before and/orafter stack to help with the cosmetic appearance of the stack traces.

7. Add a new Trace Display to plot the corridor stack.



Splice the Corridor Stack into a Surface Stack

One of the main purposes for generating VSP data is to produce thecorridor stack. This stack is a direct measurement of geologic reflectiontimes and depths at the borehole. By tieing the VSP Corridor Stack tosurface seismic, interpreters can identify seismic reflections againstknown geologic interfaces in the borehole. In this exercise you willsplice the corridor stack into a surface seismic stack.

Exercise1. Build the following flow:

2. In Disk Data Input, input the Final Stack file.

3. In Trace Label, add a label called Stack.

4. In Splice Datasets, splice in the Corridor Stack at CDP Bin Number820 and pad with 3 dead traces.

5. Apply a bandpass filter and amplitude scaler (AGC) for cosmeticpurposes.

Editing Flow: splice corr stk into stack


Disk Data InputTrace Display LabelSplice Datasets

Select a trace data file to be spliced --------------------------------------------------- your area - your line corr stack

Primary header word ------------------------------------------ CDP

Input a primary header value ------------------------------ 820

Secondary header word ----------------------------------- NONE

Number of dead padding traces ------------------------------- 3Bandpass Filter

Default all parametersAutomatic Gain Control

Default all parametersTrace Display



6. Plot the combined display with Trace Display

Note: The stack and VSP are from completely different areas.

When the corridor stack was generated, a time shift is applied toapproximately tie the stack and the corridor stack.




Chapter

Generate Intv-Dpth VelocityFunction

Two products from VSP data processing require an Interval Velocity vs.Depth velocity function. These are the VSP-CDP transform and the VSPMigration.

In this exercise, we will build INTV-DPTH velocity fields from theaverage velocity functions that we derived from the first arrival timesbefore and after smoothing. Some additional editing will be required toensure that the velocity field spans the entire desired depth image areafor the VSP migration.


❏ Compute Interval Velocity vs. Depth

❏ QC of the function using the Velocity Viewer/Point Editor

15

Chapter 15: Generate Intv-Dpth Velocity Function


Compute Interval Velocity vs. Depth

The average velocity vs. depth function in itself is not very useful butwe can convert this function to an interval velocity vs. depth function forfuture processing. As you will see, typically some smoothing must occurwhile generating the interval velocity function.




2. Input the average velocity function computed from the first arrivaltimes and output an interval velocity vs. depth function.

3. View the output intv-dpth function.

Editing Flow: 16- generate intv-dpth function



Type of velocity table to input ----- Average Vel in Depth

Get velocity table from database entry ------------------ Yes

Select input velocity database entry ---------------------------------------------------from raw first break pick times

Combine a second velocity table ---------------------------- No

Resample the input velocity table? ------------------------- No

Shift or stretch the input velocity table -------------------- No

Type of parameter table to output ---------------------------------------------------------------------- Interval Vel in Depth

Select output velocity database entry -------------------------------------------------------------------- from raw average




Vertically resample the output velocity table ----------- No



---------------------------------------------Interval Vel in Depth



------------------------------------------------------ from raw average



-------------------------------------------------------from raw average





We will not do any editing, so you can output to the same table asyou are reading from.

Are there any problems with this interval velocity function?

Exercise1. Expand the flow to generate a new interval velocity vs. depth

function from the smoothed average velocity vs. depth function.

2. Input the smoothed average velocity function computed from thefirst arrival times and output a new intv-depth table.

3. View the output table for QC.

Editing Flow: 16- generate intv-depth function


>Velocity Manipulation*<>Velocity Viewer/Point Editor*<Velocity Manipulation*




Time step sizes for the output table ------------------- 48Velocity Viewer / Point Editor*







You may elect to run each of these simultaneously for comparison.

------- from raw avg ------- from smoothed avg -----

Note: There are two points very close together on both functions soyou can elect to resample the function in Velocity Manipulationprior to output.



ExerciseOne of the requirements for the VSP migration is that the velocity fieldspan the entire range of the output image area. Since we may want toimage events recorded below the bottom of the well, we must expand thevelocity field in depth to cover the proposed image area. We will alsoresample the output intv-depth function to the original sample period of50 ft.

1. Edit the existing flow.

2. Input the smoothed average velocity function computed from thefirst arrival times and output a new intv-depth table.

3. In Velocity Manipulation, resample the output function to a depthincrement of 50 ft.

4. View the output table for QC.

Specify an output maximum depth of 15000 ft.

Editing Flow: 16- generate intv-depth function


>Velocity Manipulation*<>Velocity Viewer/Point Editor*<Velocity Manipulation*




Time step sizes for the output table ------------------- 50Velocity Viewer / Point Editor*





Minimum depth (or time) of vel field -------------------------- 0

Maximum depth (or time) of vel field ----------------- 15000



5. Remember to go into edit mode and you may elect to edit thevelocity function in preparation for migration.

Edit the smoothed version and output a Velocity Function for VSP-CDP transform and Migration.




Chapter

VSP CDP Transform

For VSP surveys where the source is offset from the well location, astandard final product is the VSP to CDP transform. The VSP to CDPtransform is a high spatial and temporal resolution seismic section thatallows you to image reflection events near the borehole in the directiontoward the shot location. This may help identify faults and/or theattitude of dipping reflected events.


❏ Generation of the VSP CDP transform

16

Chapter 16: VSP CDP Transform


VSP CDP Transform

Exercise1. Build a flow to generate the VSP-CDP transform.

2. In Disk Data Input, input the upgoing data with decon applied.

3. Select the VSP/CDP Transform parameters.

Editing Flow: 17 - VSP-CDP transform


Disk Data Input


Trace Read Option--------------------------------------------Get AllVSP/CDP Transform

Horizontal binning interval -------------------------------------- 5

CDP at which to extract vel function --------------------- 100

Specify trace length of output trace in msec -------- 3000

Select how velocity is to be specified ------------ Database

Select a velocity file ---------------- from smoothed average

Ray trace interval ------------------------------------------------- 20

Datum elevation ----------------------------------------------------- 0

Allowable percentage of moveout stretch ---------------- 50Trace Display Label

Trace Label --------------------------------- VSP-CDP transformDisk Data Output

Output Dataset Filename-------------VSP - CDP transform




Skip primary disk Storage?-------------------------------------NoTrace Display

Primary trace LABELING header ----------------------- NONE

Secondary trace LABELING header ---------------- RBIN_X



Use the interval velocity function that was created from thesmoothed average function and edited. Build a trace every 5 ft. to 3sec, and ray trace every 20 ft.

4. Use Trace Label to label the traces as the VSP-CDP transform. InDisk Data Output, output the file.

5. Plot the output traces using Trace Display.

Plot 1 ensemble.

You will probably want to make the display window smaller in orderto see the traces more clearly.

6. Look at the headers of the traces and find the new header word thatyou can use to best annotate above the traces

Exercise1. Expand the existing flow to redisplay the VSP-CDP transform.

2. In Disk Data Input, input the VSP-CDP transform.

3. Apply a bandpass filter and AGC for cosmetic appearance.

4. Display the traces using Trace Display.

Editing Flow: VSP-CDP transform


>Disk Data Input<>VSP/CDP Transform<>Trace Display Label<>Disk Data Output<Disk Data Input


Trace Read Option--------------------------------------------Get AllBandpass Filter

Default all parametersAutomatic Gain Control

Default all parametersTrace Display



Plot the traces by annotating the RBIN_X header word above thetraces. This will plot a value representing the distance from theborehole above the traces.

Note: This is a user-defined attribute.

You may want to enhance the appearance of the transform byapplying a trace mix and/or adjusting the scaling and/or bandpassfilter parameters.


Chapter

VSP Migration

For VSP surveys where the source is offset from the well location, it ispossible to migrate the recorded data. The migration produces a highspatial resolution seismic section that allows you to image reflectionevents in the vicinity of the bore-hole looking in then plane defined bythe well bore and the shot location. Unlike the VSP-CDP transform, themigration can look on the opposite side of the borehole. This may helpidentify faults and/or the attitude of dipping reflected events.

The migration differs from the VSP-CDP transform in that the transformis a simple mapping function that takes a point on a shot to receiver traceand maps that point to a single reflection point in the subsurface. Themigration operation is similar to that for surface seismic data, where itattempts to place a data point at all locations from which it could haveoriginated. The migration can be a time consuming process dependingon the size of the output image area, the selected algorithm and the sizeof the dataset.


❏ VSP Migration

17

Chapter 17: VSP Migration


VSP Migration

Exercise1. Build the following flow to migrate the VSP data:

2. In Disk Data Input, input the upgoing data with decon applied.

3. Select the following VSP Kirchhoff Mig. parameters:

4. In Trace Label, label the traces as the migration. In Disk DataOutput, output the file to disk.

Editing Flow: VSP migration


Disk Data Input <GET ALL>VSP Kirchhoff MigrationTrace Display LabelDisk Data Output



Display the VSP Migration

Exercise1. Expand the flow to reread the migrated data and add an AGC prior

to display.

2. In Disk Data Input, input the migration file.

3. Scale the data to improve its cosmetic appearance.

Use a value of about 2000 ft. for the AGC gate length.

4. In Trace Display, plot the migrated data and annotate CDP numberabove the traces.

Editing Flow:


>Disk Data Input< <GET ALL>>Trace Header Math<>VSP Kirchhoff Migration<>Trace Display Label<>Disk Data Output<-------------------Disk Data InputAutomatic Gain Control-------------------Trace Display




Chapter

VSP Corkscrew Geometry

VSP Geometry can as simple as a straight borehole or it may becomemore complex when working with deviated boreholes. In this exercisewe will look at a synthetic VSP which was recorded in a borehole thatresembles a corkscrew.


❏ Assign VSP Geometry

❏ Quality Control Plots from the database

18

Chapter 18: VSP Corkscrew Geometry


Assign VSP Geometry

In this exercise you will describe the source and receiver coordinate anddepth information, define the field recording channel geometry, anddescribe the shot to receiver group relationships using the spreadsheets.

Exercise1. Build a flow to Assign VSP Geometry.


The following window will appear:

Fill in each of the Borehole, Patterns, and Sources spreadsheets inthis order.

The Borehole spreadsheet describes the X, Y and Z information ofthe borehole.

The Patterns spreadsheet describes how many channels wererecorded and the orientation of these channels.

The Sources spreadsheet describes the X, Y and Z information forall of the source locations and relates the recorded FFID informationwith a given source and spread reference position.

Editing Flow: Spreadsheet / Geometry


VSP Geometry Spreadsheet*



Synthetic Corkscrew VSP Geometry Diagram

1000 11001070.71

929.

92

929.92

1000

1100

1100

X-Coordinate

Y-C

oord

inat

e100

1050,1050

100 on the surface

1000logdepthdifference

995trueverticaldepthdifference

1-3

4-6

7-9

10-12

13-15

50

maximum log depth of 7000 ft



3. Open the Borehole spreadsheet by clicking on “Borehole” on themain menu.

In this case we have a curved borehole. We have 8 control points.The log depths differ from the elevations.

4. Define the borehole with six sets of X,Y, and Z coordinates.

5. Exit from the Borehole Spreadsheet.

6. Open the Patterns Spreadsheet by clicking on “Patterns” on themain menu.

There is only one pattern for this geometry.

The Grp Int column specifies the separation between the specifiedrecording channels in the borehole.

The Offset column specifies a shift to apply to the “chan from”channel relative to the depth listed in the sources spreadsheet.

In this case we have fifteen channels with a set of three at the samedepth. We will simulate a 5 level multi component tool where theindividual levels are 50 apart. You will define the exact depth for thefirst receiver for each shot.



7. Exit from the Patterns Spreadsheet.

8. Open the Sources Spreadsheet by clicking on “Sources” on themain window.

9. We have a total of 28 shots in this VSP, so the first thing to do isexpand the sources spreadsheet to 28 rows.

Mark the last card as a block with MB1 and MB2 and then use theedit pull down to insert the required number of cards.

10. Number the Sources and FFIDs starting at 1 and incrementing by 1.

11. All shots are at shot station number 1 and at an elevation of 0.0 ft.

12. X,Y values are defined at 1050.0 and 1050.0 respectively.

13. All shots use the same pattern (1) and each has 15 channels.

14. The pattern reference depths start at 6800 and decrement by 250 ft.for each shot.

Note: For documentation purposes, the columns have been re-ordered slightly. All additional columns are filled with 0.0.

15. Exit from the Sources Spreadsheet

The next steps in the geometry definition process are to define thepseudo CDP binning and to finalize the database.

This is a 3 step process.



16. Open the Bin menu and select to Assign trace geometry by patterninformation.

17. With the Assign option selected, click on the OK button.

You should see several windows related to Assigning VSP geometrybased on patterns flash by fairly quickly. The last window will saythat the geometry has been successfully assigned.


19. Compute the Pseudo Common Depth points.

Bin starting at CDP 1, starting at 0.0 ft. and ending at 7000 ft.incrementing by 50 ft. per bin.



20. Click on the OK button.

Again you should see several windows flash by ending with awindow indicating that the binning was completed successfully.

21. Dismiss this window by clicking on the OK button.

22. Finalize the database.

This step completes building the look up tables and other databasefinalization functions.

23. Select the Finalize Database option and click on the OK button.

You should see a window indicating that the VSP geometryfinalization has completed successfully.


25. Click on the Cancel button in the binning dialog box to dismiss thiswindow.



Quality Control Plots from the database

2D plot of TRC vs. Receiver elevation and log depth

• used to check depth assigned to each trace

2D plot of SRF vs. elevation

• used to check depth assigned to each receiver station

2D plot of TRC vs. various other values

• used to check additional information for each trace

From the Traces Spreadsheet generate a pointcloud of log depth vsX and Y.


Chapter

Pre Vertical Stack DatasetInformation

A dataset was generated to illustrate some of the capabilities ofProMAX VSP. This dataset will be used for an exercise to demonstratevertically stacking multiple shots where the receiver(s) were at commondepth positions.


❏ VSP Pre Vertical Stack Dataset Geometry

19

Chapter 19: Pre Vertical Stack Dataset Information


VSP Prevertical Stack Dataset Geometry

Source type: surface


Number of Receivers / receiver string: 1


• Channel 1: vertical component first receiver


Depth of first record: 12100 ft.

Depth of last record: 8150 ft.

Depth increment: 50

Source offset from hole: N/A

The bore hole is vertical with no deviation






Landmark ProMAX 3D User Training Manual 20-1

Chapter

VSP Level Statics andVertical Stack

When collecting VSP data, it is common to acquire multiple recordswith the sources and receivers at the same location. This helps attenuaterandom noise and builds up the signal to noise ratio of the data. Eachtime the source and recording system are activated, there can be smalltime differences in the records relative to one another. In order tooptimize the vertical stack of these records, these time differences canbe measured, normalized and applied prior to vertically stacking therecords.

There are some fairly complex issues associated with these processessuch as:

• What information is available in the incoming trace headers?

• What information do I have on observers notes?

• What are the best primary and secondary sort orders for pickinganalysis time gates?

• Do I need to do some trace header manipulation to build specialensembles?

• How many traces and recording levels per shot do I have per shotrecord?


❏ Plot the Traces

❏ VSP Level Statics Parameters

❏ Compute and Apply the Level Statics

❏ Vertically Stack Shots by Common Header Entry

20

Chapter 20: VSP Level Statics and Vertical Stack

20-2 ProMAX 3D User Training Manual Landmark

Plot the Traces

In this exercise you will plot the synthetic data to familiarize yourselfwith it.

Exercise1. Build a flow to plot the input data.

2. In Disk Data Input, input the prevertical stack traces file.

3. Use Trace Display to plot 400 ensembles.

There are 80 levels and 5 sweeps per level. Each trace is a separateshot ensemble.

Because each trace is a separate ensemble, we will want to set thegap between ensembles to “0” for the display.

Notice that there are 5 traces per depth level and these traces differslightly due to variations in random noise on each trace.

4. Look at the trace headers and see what values exist and are commonfor all traces at the same depth level.

There are two header words that can be used to identify all traces atthe same depth level, these are:

• Receiver Elevation

• SHT_GRP

If these header words did not already exist, how could you buildthem?

Editing Flow: level statics - vertical stack


Disk Data Input <GET ALL>Trace Display

Landmark ProMAX 3D User Traiining Manual 20-3


ExerciseIn this exercise, we will pick the level statics correlation time gate.

1. Edit the flow to toggle the VSP level Statics process inactive..

The parameter table we need to pick will be a miscellaneous timegate which has certain requirements.

We need to think about how we should sort the input data forpresentation to Trace Display and how to determine the secondarysort order for the parameter table itself.

We want a table that has constant values for all traces with the samereceiver elevation, but varies linearly between receivers. We willpick a miscellaneous time gate where we will pick times andinterpolate the times as a function of receiver elevation.

What is the best ensemble to build? There are actually two choiceshere.

• We could combine all of the traces into one ensemble and thenpick the times as a function of receiver elevation

• We could make ensembles of all traces of common receiverelevation and also interpolate the times a function of receiverelevation.

2. In Disk Data Input, sort the input with a primary sort key of CHANand a secondary of REC_ELEV.

This will combine all traces into one ensemble with the tracesordered as a function of the receiver elevation.

3. Pick a miscellaneous time gate with a secondary key of “rec_elev”and select times on the first trace and last trace about 50 ms beforethe first arrivals.

4. Using MB3, Project the pick times to all of the other traces.

Editing Flow: level statics- vertical stack


Disk Data Input <SORT>Trace Display



You should see that all traces recorded at the same receiver elevationhave the same time.

5. Add a New Layer using MB3 to this table.

Pick the bottom time of the correlation gate about 100 ms below thetop time.

6. Use MB3 to Project the times to the other traces.

Exit the Trace Display program and save the table to disk.



VSP Level Statics Parameters

In this exercise we will estimate and apply normalized time shifts torectify any small shot to shot time variations in the data.

Exercise1. Expand the flow to add the VSP level Statics process:

2. Shots will be identified by their FFIDs, that is all traces with thesame FFID belong to the same shot.

There are two methods for identifying groups of shots to be operatedon as groups:

• By hand listing the respective FFIDs

• By reading all traces with a common header word

In our case we have two header words to choose from, the ReceiverElevation and the SHT_GRP. We will use the SHT_GRP headerword for this exercise.

There are a maximum of 5 shots in a group.

3. The maximum separation between groups of SHT_GRP must be setto a value less than 1.

4. Analyze the vertical Recording Channel Number from each shot[channel 1].

5. You can expect a maximum static shift of about 5 ms.



Disk Data Input <GET ALL>--------------------VSP Level Statics--------------------Trace Display



6. Select to use the analysis window picked in the previous exercise.



Compute and Apply the Level Statics

In this exercise we will run the VSP Level Statics process to estimate thetime shifts and then apply the normalized time shifts using HeaderStatics and Apply Fractional Statics. Actually on this data, there are notime shifts, just random noise variation, so the values we get will be verysmall.

Exercise1. Expand the flow to add the Header Statics, Apply Fractional Statics

and the Trace Display:

2. In VSP Level Statics, select the time gate that was previouslypicked.

3. In Header Statics, add the value in trace header word LVL_SHFT asa static.

4. Complete the static shift using the Apply Fractional Statics process

5. Add a label to the headers and display the results.

6. You may want to produce a Header Plot of the LVL_SHFT values.



Disk Data Input <GET ALL>--------------------VSP Level StaticsHeader StaticsApply Fractional StaticsTrace Display Label--------------------Trace Display



ExerciseWith a little rearranging we can produce a comparison plot to look at thedata before and after the level statics application.

1. Expand the flow to compare the traces before and after level staticsapplication.

2. Add the Reproduce Traces and IF-ELSEIF-ENDIF processes.

3. Add the Inline Sort to resort the data by Repeat number and FFIDfor display.

There are 400 traces per ensemble and a total of 800 traces in the sortbuffer.

4. In the Trace Display select to plot 1 ensemble per screen and plot 2vertical panels.

You may also select to generate a header plot of the LVL_SHFTheader values.



Disk Data Input <GET ALL>Reproduce Traces <2 copies ALL DATA>IF <REPEAT=1>

VSP Level StaticsHeader StaticsApply Fractional StaticsTrace Display Label <input>

ELSEIF <REPEAT=2>Trace Display Label

ENDIFInline Sort <REPEAT:FFID>Trace Display



Comparison of with and without level statics including a header plotof the Level Statics Values for a subset of the data.



Vertically Stack Shots by Common Header Entry

Exercise1. Rearrange the flow to vertically stack based on a common header

entry.

2. Toggle the Comparison processes inactive.

3. Add VSP Level Sum after the statics application.

In VSP Level Sum, select to identify shot groups by header wordSHT_GRP.

There will be a maximum of 5 shots in a group.

4. Plot the results.

You should have 80 traces. (80 ensembles)

You can do an Inline Sort prior to the Trace Display with a primaryensemble of CHAN and secondary sort of FFID and then you willhave a single ensemble for the Trace Display.



Disk Data Input <GET ALL>>Reproduce Traces<>IF<VSP Level StaticsHeader StaticsApply Fractional StaticsVSP Level SummingTrace Display Label>ELSEIF<>Trace Display Label<>ENDIF<>In-line Sort<Trace Display



Compare Stacks With and Without Level Statics

Exercise1. Rearrange the flow to compare a vertical stack with and without the

level sum.

2. Using the screen swapping in Trace Display, compare the resultswith and without the level summing.

Display 1 ensemble per screen and then set the window size andzoom parameters. Save one screen and then go to the next. Save itand compare the two plots.

The differences in this example will be minimal.

3. You may also try to use two vertical (or horizontal) panels and plotboth results simultaneously.



Disk Data Input <GET ALL>Reproduce TracesIF

VSP Level StaticsHeader StaticsApply Fractional StaticsVSP Level SummingTrace Display Label <level stat>

ELSEIFVSP Level SummingTrace Display Label





Chapter

Synthetic Dataset Information

A synthetic dataset was generated to illustrate some of the capabilitiesof ProMAX VSP. This dataset will be used for a couple of exercisesshowing some ways of compensating for shot to shot time variations andalso to demonstrate vertically stacking multiple shots where thereceiver(s) were at common depth positions. This data set shows a multilevel / multi component example.


❏ VSP Synthetic Dataset Geometry

21

Chapter 21: Synthetic Dataset Information


VSP Synthetic Dataset Geometry

Source type: surface


Number of Receivers / receiver string: 2


• channel 1: vertical component first receiver

• channel 2: one horizontal component first receiver

• channel 3: second horizontal component first receiver

• channel 4: vertical component second receiver

• channel 5: one horizontal component second receiver

• channel 6: second horizontal component second receiver


Depth of first record: 1200 - 1100 ft.

Depth of last record: 1000 - 900 ft.

Depth increment: 100

Source offset from hole: N/A

The borehole is vertical with no deviation







Chapter

Level Stat and Vertical Stack forMulti Component / Multi Level

When collecting VSP data, it is common to acquire multiple recordswith the sources and receivers at the same location. This helps attenuaterandom noise and build up the signal to noise ratio of the data. Each timethe source and recording system are activated, there can be very smalltime differences in the records relative to one another. In order tooptimize the vertical stack of these records, these time differences canbe measured, normalized, and applied prior to vertically stacking therecords.

In this set of exercises we will use a synthetic dataset simulating theMulti Component - Multi Level situation.


❏ Determine Level Statics

❏ Vertically Stack Shots for Common Depth Levels

❏ Examine Headers for Common Header Entry

22

Chapter 22: Level Stat and Vertical Stack for Multi Component / Multi Level


Plot the Traces

In this exercise we will simply view the traces and look at the traceheaders to familiarize ourselves with the data.

Exercise1. Build the following flow to plot the input data:

2. In Disk Data Input, input the synthetic shot record dataset.

This dataset can be found in the VSP tutorials area.

3. In Trace Display, plot 10 ensembles.

4. Estimate the time of the first arrivals for each set of shots.

In the next exercise we will need some time gate information.

At approximately what time are the first arrivals on this dataset foreach set of 5 shots?

• Shots 1-5 __________

• Shots 6-10 _________

Editing Flow: level statics


Disk Data Input

Select dataset------------------------------Synthetic input data

Trace read option---------------------------------------------Get AllTrace Display

Specify display END time-------------------------------400

Number of ensembles(line segments)/screen------------10



Determine Level Statics

In this exercise we will estimate and apply normalized time shifts torectify any small shot to shot time variations in the data.

Exercise1. Expand the flow to compute and apply level_statics.

2. Select VSP Level Statics parameters.

Shots will be identified by their FFIDs and instead of grouping themby a header word, you will hand input the common shot groups. Thefirst five are one group and the second five are another group. Thereare a maximum of 5 shots in a group.

Analyze the two vertical traces from each shot. [traces (1 and 4)]You can expect a maximum static shift of about 5 ms. Use a handinput window about 100 ms wide centered at the approximate time



Disk Data Input

Select dataset------------------------------Synthetic input dataVSP Level Statics

Shot header name:----------------------------------------------FFID

How will shot groups be identified?:-----------Hand input

Shot grouping:---------------------------------------------1,5/6,10/

Analysis receivers:------------------------------------------------1,4

Maximum static shift (in ms):-------------------------------------5

Basis for analysis window:-----------------------Hand input

Select primary header word:--------------------------------FFID

Specify window analysis parameters:-------------------------

1:100-200/5:100-200/6:50-150/10:50-150/Header Statics

First header word to apply:--------------------------LVL_SHFTApply Fractional StaticsTrace Display



of the first arrivals. This analysis window will be constant for thefirst 5 FFIDs and change to a new constant for the second 5.

1:100-200/5:100-200/6:50-150/10:50-150

3. Read the VSP Level Statics helpfile to determine the name of theHeader Attribute to apply as a static in Header Statics.

4. After applying the LVL_SHFT statics using the Headers, apply thefractional remainder with Apply Fractional Statics.

ExerciseWith a little rearranging we can produce a comparison plot to look at thedata before and after the level statics application.



1. Modify the flow to compare the traces before and after level staticsapplication.

2. Add Reproduce Traces and IF-ELSEIF-ENDIF.



Disk Data Input

Select dataset------------------------------Synthetic input dataReproduce Traces

Total number of datasets------------------------------------------2IF

SELECT Primary trace header word:-------------REPEATED

SPECITY trace list:----------------------------------------------------1Trace Display Label

Trace label--------------------------------------------Original InputELSEIF

Trace selection MODE:-------------------------------------Include

SELECT Primary trace header word:-----------REPEATED

SPECIFY trace list:----------------------------------------------------2VSP Level StaticsHeader StaticsApply Fractional StaticsTrace Display Label

Trace label------------------------------------------------w/hdr statENDIFIn-line Sort

Select new PRIMARY sort key:----------------------- REPEAT

Select new SECONDARY sort key:------------------------FFID

Max. traces per output ensemble:----------------------------60

Number of traces in buffer:------------------------------------120Ensemble Redefine

Mode of application:-------------------------------------Sequence

Max traces per output ensemble:-------------------------------6Trace Display

Number of ensembles(line segments)/screen------------10



3. In Inline Sort, resort the data by Repeat number and FFID fordisplay.

We have a total of 60 traces per ensemble and a total of 120 traces inthe sort buffer.

4. Split the Repeat ensembles back into individual shot ensemblesusing Ensemble Redefine.

We will take each sequence of 6 consecutive traces as one outputensemble.

5. In Trace Display, plot 10 ensembles per screen and use the screenswap functionality to compare the data before and after level staticadjustment.



Vertically Stack Shots for Common Depth Levels

After the level statics have been computed and applied, the traces can bevertically stacked for common shot and receiver locations.

Exercise1. Modify the previous flow to vertically stack shots by hand input shot

groups for common receiver depth levels.

2. Select VSP Level Summing parameters.

In this exercise, individual shot records will be identified by theirFFID. We will sum common channels for Hand Input sets of shotswhere the first 5 FFIDs are grouped together and then the second 5.

3. Add a Trace Display Label.

Editing Flow: vertical stack


Disk Data Input <GET ALL>>Reproduce Traces<>IF<>Trace Display Label<>ELSEIF<VSP Level StaticsHeader StaticsApply Fractional Statics>Trace Display Label<>ENDIF<>In-line Sort<VSP Level Summing

Shot header name:----------------------------------------------FFID

Header name for secondary key:-----------------------CHAN

How will shot groups be identified?:-----------Hand input

Shot grouping:---------------------------------------------1,5/6,10/Trace Display Label <vert stack>Trace Display



4. In Trace Display, plot the result.

You should now have only 12 traces, 3 traces for each depth level.Use the Header Dump icon to look at a few trace headers.



Examine Headers for Common Header Entry

Plot the original input data and examine the trace headers.

Exercise1. Rearrange the flow to input the data and plot it via Trace Display.

2. Plot the traces using Trace Display.

Examine the headers to see if there is a header word that is commonto all traces in a group of shots that should be vertically stackedtogether.

In this case there is a header entry called SHT_GRP. We can use thisheader entry in VSP Level Summing as an alternative to handinputting the shot groups.



Disk Data Input <GET ALL>>Reproduce Traces<>IF<>Trace Display Label<>ELSEIF<>VSP Level Statics<>Header Statics<>Apply Fractional Statics<>Trace Display Label<>ENDIF<>In-line Sort<>VSP Level Summing<>Trace Display Label<Trace Display



Vertically Stack Shots by Common Header Entry

Exercise1. Rearrange the flow to vertically stack based on a common header

entry.

2. Toggle the level statics, static application and level summingprocesses back to active.

3. Review the parameters of VSP level summing.

In the VSP Level Summing process, select to identify shot groups byheader word SHT_GRP. Plot the results. Again you should have 12traces, 3 from each depth level.



Disk Data Input <GET ALL>>Reproduce Traces<>IF<>Trace Display Label<>ELSEIF<VSP Level StaticsHeader StaticsApply Fractional Statics>Trace Display Label<>ENDIF<>In-line Sort<VSP Level SummingTrace Display Label <summed by header>Trace Display



Compare Stacks With and Without Level Statics

Exercise1. Copy the flow and rearrange it to compare a vertical stack with and

without the level sum.

2. Using the screen swapping in Trace Display, compare the resultswith and without the level summing.

Display 1 ensemble per screen and then set the window size andzoom parameters. Save one screen and then go to the next. Save itand compare the two plots.

There are some very subtle differences.

Editing Flow: compare level statics


Disk Data Input <GET ALL>Reproduce TracesIF

VSP Level SummingTrace Display Label <No level stat>

ELSEIFVSP Level StaticsHeader StaticsApply Fractional StaticsVSP Level SummingTrace Display Label <level stat>





Chapter

3-Component Transform andFirst Break Picking

In some cases it may be advantageous to generate a trace that representsthe total power of all three component traces in order to help in the firstbreak picking process. Here we will generate a trace that is the RMSamplitude of the three component traces and look at a couple of differenttechniques for picking the first arrivals.


❏ 3 Component Transform to generate an RMS amplitude trace andFirst arrival picking

❏ Setting the first arrival times identical on all three components

❏ QC the copied picks

23

Chapter 23: 3-Component Transform and First Break Picking


3-Component Transform and First Arrival Picking

In this exercise you will input the three component traces and recomputenew traces based on the amplitudes of all three inputs.

Exercise1. Build a flow to construct an RMS trace and display the results.

2. In Disk Data Input, read the real data with the correct geometry inthe headers.

This file still has 3 traces per shot and has a primary sort order ofFFID.

3. Select 3-Component Transform parameters.

Editing Flow: three component transform


Disk Data Input

Trace read option:--------------------------------------------Get All3-Component Transforms

Header word for selecting replacement trace:-----Geophone component (x,y,z)

Value of replacement trace header ---------------------------2

Select 3-component transform to apply:------------------Sum Squares Stack

Maximum time to calculate transform (ms):----------1500In Line Sort

Select new PRIMARY sort key:------------------------Geophone component (x,y,z)

Select new SECONDARY sort key:------------------------FFID

Maximum traces per output ensemble:--------------------80

Number of traces in buffer:----------------------------240Trace Display

Number of ENSEMBLES(line segments)/screen:---------1

Number of display panels:--------------------------------3

Trace Orientation:---------------------------------------Horizontal



Replace header entry geophone component (x,y,z) number 2 andprocess to 1500 ms using a sum squares stack.

4. Sort the data with a primary sort of Geophone Component (x,y,z)and secondary of FFID.

There are 80 traces per ensemble and a total of 240 traces in the sortbuffer.

5. In Trace Display, display the three component traces.

Use 1 ensemble per screen and 3 horizontal panels.

You may also want to try 3 vertical panels.

6. Identify the first arrivals on the display of the RMS trace.

7. Create a new First Break entry of the type GEOMETRY in thedatabase using the Picking pulldown menu.

Select to edit database values (first breaks) and give these FB Picksa name that describes them as being picks from the RMS trace.

8. After “rubber-banding” the first arrivals on one of the panels, snapthem to the nearest peak.

Notice that each panel is picked completely independently from theothers. In this case only pick the one panel that contains the RMStrace.

9. Compare the picks by plotting them from the database.

We should have two sets of first break picks in the TRC database.The picks from the vertical traces that we picked earlier and thesenew picks from the RMS traces.



Copying Picks from one Trace to the Others

For 3-Component rotation and/or Hodogram Analysis, it is required thatall traces at a common receiver position have the same first arrival time.This exercise will demonstrate how this can be accomplished given onegood first arrival per receiver depth level.

Exercise1. Build a flow to copy the time pick from 1 component to the other

components.

2. In the first Disk Data Input, read the file with all three traces pershot with the geometry installed in the headers.

3. In Database/Header Transfer, move the database resident first breakpick that was picked from the single vertical trace to the fb_pickword in the trace header.

This is the first break pick that was picked earlier on the verticaltraces only and then edited in the database.

Editing Flow: copy first break picks


Disk Data Input <GET ALL>Database/Header TransferAssign Common Ensemble ValueDatabase/Header TransferDisk Data Output



4. In Assign Common Ensemble Value, copy the first break pick timefrom channel 1 to the other 2 channels of each shot.

5. Transfer the copied first break times from the trace header back tothe database.

Each trace has a first arrival time in the trace header, but there is noattribute in the database that has a first break time for all traces thatis correct. For future reference it would be advisable to make a copyof the copied arrival times in the database.

6. Write the output data to a new file.



QC the Copied Picks

As a final QC of the copied picks, plot them over the traces to see if allthree traces at a receiver depth level are constant.

Exercise1. Display the picks in the database.

Exit from the flow. Click on the global Database button.

Use the Database display tool to graph the various picks andcompare the results.

2. Expand the flow to reread the new data file and plot the first breaks.

3. Toggle all of the previous processes inactive.

4. In Disk Data Input, read in the file that was written in the previousexercise that has the copied picks in the header.

5. In Trace Display, plot the traces

Plot 80 ensembles.


7. Overlay the picks from the headers and/or the database on thetraces.

Editing Flow: copy first break picks


>Disk Data Input<>Database/Header Transfer<>Assign Common Ensemble Value<>Database/Header Transfer<>Disk Data Output<----------------------Disk Data InputTrace Display



Use the Picking pulldown menu to select the first breaks from thetrace headers, or the database.

All three traces per FFID should have the same pick time. Check thevalues by using the header dump facility.




Chapter

VSP 3-Component Orientation

Most modern down-hole seismic recording tools consist of one or moresets of geophones in a string. Each of these sets is typically a group ofthree geophones, (occasionally you may find four component tools). Forthe three component tool there will be one vertical geophone and twohorizontal geophones which are oriented perpendicular to one another.Sometimes, in processing, the energy recorded on the horizontal phonesis of interest. This data may contain a lot of shear wave energy whichcan yield valuable information if this is the goal. Quite often, thishorizontally recorded energy is ignored and only the vertical traces areused in processing.

In this chapter we will look at the interactive Hodogram Analysis 3component orientation process which can be used to build newhorizontal traces from the recorded traces that represent what are calledtransverse and radial components. These correspond to the traces thatwould have been recorded had the horizontal phones been perpendicularand parallel, to the line defined by the shot and receiver positions on thesurface. Additionally, given the vertical and oriented (radial) horizontaltraces, two new traces can be built representing the maximum andmedium traces where the maximum trace is that which would have beenrecorded had one geophone been aligned pointing directly toward thesource position.

Once the geophone orientation is known, additional processing of theoriented horizontal traces is possible for both p and shear wave energy.


❏ 3 Component Hodogram Analysis

24

Chapter 24: VSP 3-Component Orientation


3 Component Hodogram Analysis

ExerciseIn this exercise we will work with the two horizontal traces and buildtwo new horizontal traces: one Radial and one Transverse. Watch thepolarity of the output (watch the vertical orientation plot as well) inorder to get the output traces all the correct polarity.

1. Build a flow to compute the radial and transverse traces from twohorizontally recorded input traces of unknown orientation.

2. In Disk Data Input, read the traces with constant first arrival timesfor each trace at each receiver level in the headers.

3. Apply a bandpass filter.

Default values are ok. In general you would not want to apply anytrace by trace amplitude corrections for this process.

4. Select Hodogram Analysis parameters.

Editing Flow: 3 comp hodogram analysis


Disk Data Input <GET ALL>Bandpass FilterHodogram AnalysisDisk Data Output



Plot the first arrival times, and use the arrival times as a basis for theanalysis window. Do not output the analysis window to a time gatefile. Write the orientation values to the trace headers.

5. Write the output data to disk.

6. Execute the Flow.

You should see a display similar to the following after zooming inaround the first arrivals.



Example Hodogram Analysis Plot

The Hodogram plot has three basic sections:

• the trace data area

• the horizontal hodogram

• the vertical hodogram

Example Hodogram Analysis Product Display

OriginalVertical andTwoHorizontal

OriginalVertical andRadial andTransverseHorizontalTraces

Traces

OrientedVertical,Transverse VerticalandTransverse HorizontalTraces

Hodogram of Two HorizontalTraces

Hodogramof OrientedHorizontaland OriginalVertical



1. Click on the Hodogram editing icon.

This enables us to alter the orientation angle that the programcomputed automatically if desired. Normally we will only want towatch the polarity of the oriented traces and we may need to rotatethe trace by 180 degrees to get the proper polarity.

2. Look at the second and third trace of the middle trace display.

The second trace should be maximized at the same polarity as thefirst trace and the third trace should be minimized.

3. Press MB2 in the top hodogram window to rotate the orientedtraces by 180 degrees to change it’s polarity.

Change it back again with another MB2 Click. This trace has thecorrect polarity.

4. Press MB2 in the bottom hodogram window to rotate the orientedvertical trace by 180 degrees.

After rotation this trace now has the proper orientation.

5. Fine tune the orientation to minimize the third trace on the secondset of traces and the second trace on the third set of traces by usingMB1 and rotating the orientation axes.

In general you will find that the fine tuning is not required.

6. Press the Next Screen icon to go to the next set of three traces forthe next depth level.

Repeat the orientation procedures where the goal is to:

• 1) maximize the second trace on the second panel of traces at thesame polarity as the original vertical trace

• 2) maximize the first trace on the third panel of traces at the samepolarity as the original vertical trace.

7. Continue until all 80 levels have been oriented.



8. Expand the flow to display the output data.

9. Read the file that was just created.

You will want to sort the input with a primary ensemble sort order ofhodo_typ and sort the traces within these ensembles to increase byFFID.

10. You may want to experiment with different display options.

A best first guess would be to use Trace Display and plot 5ensembles.

You may also want to try 1 ensemble per screen and 5 horizontalpanels.

Editing Flow: 3 comp hodogram analysis


>Disk Data Input<>Bandpass Filter<>Hodogram Analysis<>Disk Data Output<Disk Data Input <hodo_typ,ffid>

Select primary trace header entry------------------hodo_typ

Select secondary trace header entry---------------------FFIDTrace Display



Example of Hodogram Output Trace Data

Given three input traces, there will be 5 output traces

• the original vertical traces

• the oriented (radial) horizontal traces

• the transverse horizontal traces

• the oriented (maximum) vertical traces

• the orthogonal to maximum (medium) traces

--- 1 ---------------- 2 ----------------- 3 -------------- 4 ------------------5 ----




Chapter

Prepare Input Data

There was a minor limitation with the tutorial dataset whereby in theoriginal file, all of the shot records had the same FFID and the geophonecomponent header word was not set. In order to process these data, wehad to assign different FFID numbers to each record and set thegeophone component value.

Additional header words were also zeroed so that you could follow theheader updates as the processing progressed.


❏ Preparing the Input Data

25

Chapter 25: Prepare Input Data


Preparing the Input Data

This is an exercise in trace header manipulation. There may be caseswhere you may want to alter trace headers before starting to process adataset. Here is one example.

Exercise1. Build a flow to look at the trace headers.

2. In Disk Data Input, read a file from another area.

This dataset can be found in:

• Area: VSP tutorials

• Line: VSP tutorials

• Data File: Wtexas_VSP

3. In Trace Display, plot the data and view the trace headers to identifythe header values that may need to be altered prior to the start ofprocessing.

Since we have no idea how this data is organized, use all defaults forTrace Display except specify to plot 100 ensembles. This will helpyou identify what an ensemble is and then how to deal with the data.

4. Derive an equation to use to assign the FFIDs from 1 to 80. Alsonote that the Geophone (x,y,z) header word does not exist and mustbe set equal to the channel number.

Editing Flow: prepare input data


Disk Data Input <Get All>Trace Display



Exercise1. Expand the previous flow to rebuild the trace headers and write the

file to your own line directory.

2. In the first Trace Header Math, compute FFID=(12100-CDP)/50+1.

3. In the second Trace Header Math, compute GEO_COMP=chan.

4. In the remaining Trace Header Math processes, set SOU_X=0.0,REC_ELEV=0.0, CDP=0, TR_FOLD=0.0, and LINE_NO=0 oneat a time.

Note: Some are integer others are floating point.

5. Sort the data back to FFID/CHAN.

There are 3 traces per FFID ensemble and a total of 240 traces in thedataset.

6. Check the output headers using Trace display.

7. In Disk Data Output, write the data to disk when satisfied that thedata is OK.

Editing Flow:


Disk Data Input <Get All>Trace Header MathTrace Header MathTrace Header MathTrace Header MathTrace Header MathTrace Header MathTrace Header MathIn-line Sort>Disk Data Output<Trace Display




Chapter

Archival Methods

Archiving your data protects your work from system failure and mayallow you to bring data into other software packages. The archivingmethods can be run from both inside and outside the ProMAX UserInterface. In this chapter, we will discuss options for archiving yourdata.


❏ SEG-Y Output

❏ Tape Data Output

❏ UNIX tar

❏ Archive to Tape

26

Chapter 26: Archival Methods


SEG-Y Output

ProMAX offers a variety of industry standard and individual companyoutput formats. Of these, SEG-Y is the most common. This process canwrite out industry standard SEG-Y tapes as well as frequently requestednon-standard variations of SEG-Y and IEEE format. SEG-Y Output is agood choice for archiving a dataset that will later be loaded to a thirdparty software package. This process will successfully archive dataspanning over multiple disks. One downfall to this archival method isthat it will not automatically map all the ProMAX trace headers.However, SEG-Y Output provides you the capability of mapping thesenon-standard trace headers.

ExerciseIn this exercise, you will write a SEG-Y formatted tape, mapping somenon-standard SEG-Y headers. We will check to make sure the headerswere mapped correctly by using SEG-Y Input and Screen Display.Depending on the availability of a tape drive on the system, this exercisemay be modified to write a SEG-Y disk image.


2. Select Disk Data Input parameters. Select two shots from your RawShots with Geometry dataset.

Limit the dataset size for efficiency.

3. Select SEG-Y Output parameters.

Editing Flow: SEG-Y Output


Disk Data InputSEG-Y Output

Remap SEGY header values: Yes

Use defaults for remapping.>SEG-Y Input<>Trace Display<



Enter the tape drive device name. Select Yes to Remap SEG-Yheaders. Map the defaulted header values, sou_sloc, rec_sloc, andcdp_sloc.

The SEG-Y format reserves bytes 181-240 for optional use. The*_sloc trace headers are important to ProMAX so we typically writethem to the extended headers. These header values must be presentin order to automatically rebuild the database files with the ExtractDatabase Files process.

4. Put tape in tape drive.


6. Once the job is completed, build the following flow to QC theheaders.

7. Select SEG-Y Input parameters.

Make sure the formats are consistent with those specified in SEG-Youtput.

8. Select Yes to Remap SEGY headers. This loads the extendedheaders that you mapped with SEG-Y output.


10. Click on the Header icon in Trace Display to QC the headers.

The extended header values should be preserved (rec_sloc andsou_sloc).

Editing Flow: SEG-Y Out


>Disk Data Input<>SEG-Y Output<SEG-Y Input

Remap SEGY header values: Yes

Use defaults for remapping.Trace Display



Tape Data Output

Tape Data Output writes seismic traces to tape in ProMAX format. Thisprocess is ideal for archiving a dataset to use later since it automaticallypreserves all trace headers, the CIND and the CMAP file. Like SEG-Youtput, Tape Data Output will archive datasets spanning multiple disks.

ExerciseIn this exercise, you will view trace headers in the dataset, write aProMAX formatted tape and read the tape back in to make sure theheaders are preserved.

1. Exit out of ProMAX by selecting the Exit at the bottom of the UserInterface.

2. Set the environment variable BYPASS_CATALOG = t in yourProMAX start-up script or your .cshrc file, by including the linesetenv BYPASS_CATALOG t (for the c shell).

This will deactivate the tape cataloging system. Information aboutthis system is located in the helpfile index under seismic datasets andtape datasets.

3. If you set the environment variable in your .cshrc file, type source.cshrc.

This will reinitialize your .cshrc file.

4. Type promax.


Editing Flow: Tape Data Output


Disk Data Input>Tape Data Output<>Tape Data Input<Trace Display



6. Select Disk Data Input parameters. Select two shots from your RawShots with Geometry dataset.

Limit the dataset size for efficiency.


8. Click on the Header icon in Trace Display to view the trace headers.

9. Exit out of Trace Display

10. Toggle off Trace Display and toggle on Tape Data Output usingMB3.

11. Select Tape Data Output parameters. Enter an output file name andtape drive device path name.

The Pre-geometry Database Initialization option is the same onefound in Disk Data Output. This initializes the database, creating theTRC, SIN, and CHN ordered database files. Since we alreadyapplied our geometry, leave the question defaulted to No.

12. Put tape in tape drive.


Choose to continue when the popup menu appears.

14. Enter your datasets menu and click MB2 on your tape dataset.

You can view your tape dataset filename under the same menu asyour disk dataset. Click MB2 to see information about your dataset.Your new tape dataset will have a Media type of Tape.



Disk Data InputTape Data Output>Tape Data Input<>Trace Display<



15. Build the following flow to QC the headers:

16. Select Tape Data Input parameters. Select your tape dataset createdin Tape Data Output, and specify the tape device path name.



18. Click on the Header icon in Trace Display to QC the headers.

You should see that all of your header values are preserved.



>Disk Data Input<>Tape Data Output<Tape Data InputTrace Display



UNIX tar

The UNIX tar command is handy for archiving files, such as datasets,flows, and OPFs residing on one disk such as your primary disk datastorage.

Exercise1. Put a tape in the tape drive.

2. In an X-window, change directories to your line directory using thecd command.

3. Type ls.

This lists all the files in your line directory

4. Select the flow that you want to archive.

5. Type tar -cvf /dev/(tape drive device name;rmt0) ./(flowname).

This command copies your flow directory and the files containedunderneath that directory to tape.

6. When files are copied, type tar -tvf /dev/ (tape drive devicename) at the prompt.

This command types the files contained on your tape to screen. Thisstep should always be done when you are using tar to archive files tomake sure the archive worked. You can also redirect the output to afile by typing:

tar -tvf /dev/(tape drive device name) > (file namewith tape list)

If you wanted to place archived files back to disk, you would typethe following command:

tar -xvf /dev/(tape drive device name) ./(flowname).

The x in -xvf indicates that you want to extract data.



Archive to Tape

The UNIX tar command was discussed in the previous section.Although this works fine in many situations, ProMAX also includes aninline archive program, Archive to Tape (sometimes referred to as ctar),designed specifically for seismic datasets. The program ctar has someadvantages over the UNIX tar commands such as the ability to span tapevolumes on all platforms, flexible use of ProMAX’s secondary storagefor seismic trace datasets and checking for available disk space beforewriting files during restore operations. Also, you may use thisfunctionality in conjunction with the Advance Tape Catalog.

The related process, List/Restore from Tape reads ProMAX archivetapes and restores the data to disk.

ExerciseIn this exercise, you will archive your ProMAX Area to tape, list thetape contents and restore your Area back to disk.

1. Add an Area/Line called archive/archive with permissions of 775 or777.

You may not need to do this in the classroom or, for that matter, atyour workplace if this Area/Line has already been created.

The purpose of creating this new Area/Line is to prevent you fromarchiving a line by executing a flow from within the line to bearchived.


3. Select Archive to Tape parameters.

4. Click on Invalid to select an Area.

Editing Flow: ARCHIVE


Archive to Tape>List/Restore from Tape<



5. Click on Invalid to select a tape drive device path.




8. Select List/Restore from Tape parameters.

Select Simple List for Type of operation.

9. Select Catalog is Bypassed for Select Archive.

10. Click on Invalid to select a tape drive device path.


Choose to continue when the popup menu appears. Verify that yourArea exists on the archive tape by looking at your job.output file.

12. From the ProMAX user interface, delete the Area you just archived.

You can remove the files from within the process after archiving.

13. Select Restore to Change Type of operation.


Choose to continue when the popup menu appears. If you view yourjob.output file, you will see that the files were written to disk.

15. Exit out of ProMAX using the Exit button at the bottom and thenget back into ProMAX by typing promax.

16. Verify that your Area is restored.

Editing Flow: ARCHIVE


>Archive to Tape<List/Restore from Tape




Chapter

UNIX Workstation Basics

This chapter serves as a quick reference to you for some basicworkstation operations.


❏ Text Editors in ProMAX

❏ UNIX Commands

❏ Examples of UNIX Commands

27

Chapter 27: UNIX Workstation Basics


Text Editors in ProMAX

There are three text editors used with ProMAX:

• Emacs Editor

• Emacs Editor Widget

• Emacs View Widget

The Emacs Editor is a general-purpose, full-function editor. It can beoperated outside of ProMAX or in the processes: Config File Edit andthe Emacs Editor process. To start the Emacs editor outside of ProMAX,exit ProMAX and type emacs filename at the UNIX prompt.

The Emacs Editor Widget is a subset of the full-function editor and isused within ProMAX when a single line editor is insufficient but a full-function editor is unnecessary. It supports cursor movement commandsand a small set of editing commands.

The Emacs View Widget is similar to Emacs Widget in cursormovement, but does not allow any modification of text. The EmacsView Widget only displays text. It is used by ProMAX to view help filesand the flow execution output listings (view job.output).

Since all the editors listed above are variations on the Emacs Editor, theyoperate similarly. Of course, the View Widget, which does not actuallymodify text, has no need for editing commands. Since the Editor Widgetis a subset of the full Emacs Editor, it does not have all the commandsin the Emacs Editor (Search and Replace, for example).

Note: The implementation of the editors is slightly different for each ofthe ProMAX supported hardware platforms. One reason for thedifferences is the fact that the keyboards are not the same on eachplatform. The main difference is the designation of the Meta key. Thisis the diamond key on either side of the space bar on the keyboard ofSUN SPARCstations, Compose Character key on DECstations and theAlt key on IBM RS/6000 workstations. In the following instructions,replace the Meta key with the equivalent key stroke depending on yourplatform.



Cursor movement:Use the 4 cursor arrow keys

Point the mouse cursor and click button 1

Ctrl-A Move the cursor to the beginning of the current line

Ctrl-E Move the cursor to the end of the current line

Ctrl-V Scroll the screen forward (down) one screen

”Meta”-V Scroll the screen backward (up) one screen

“Meta”-Shift-<Jump to the beginning of the file

“Meta”-Shift-> Jump to the end of the file

Ctrl-S Search forward for a string; (start entering ‘string’)

Ctrl-R Search backward for a string; (start entering ‘string’)

Editing:All keyboard entry is in insert mode

Delete key Delete one character to the left of the cursor (“Backspace”for DEC)

Ctrl-D Delete one character to the right of the cursor

Ctrl-K Kill to the end of the line (from the cursor)

Ctrl-Y Yank back the contents of the kill buffer (created by Ctrl-K orCtrl-W); “cut and paste”; (can move the cursor first)

“Meta”-X, then type “repl s” Search and replace; (follow prompts)

Ctrl-X, Ctrl-W Write new Emacs file; (enter path & filename)

Ctrl-X, Ctrl-S Save current Emacs file

Ctrl-X, Ctrl-F Find another Emacs file

Ctrl-X, I Insert a file at current cursor location

Ctrl-X, Ctrl-C Exit Emacs



Exiting Emacs:Ctrl-X, Ctrl-C; (then respond Y or N to saving)



UNIX Commands

Alphabetical summary of general purpose UNIX commands used inconjunction with ProMAX.

catConcatenate and Display Files

UNIX$ cat [options] [files]

Option:

-n print output line numbers with each line

cdChange Directory

$ cd [directory]

chmodChange Access Modes

$ chmod [options] mode names

Option:

-r recursively change directory tree

Mode can be numeric or symbolic

The symbolic case is of the form [agou][+-=][rstwx] where:

a group, other and user, access permissions

g group access permissions

o other access permissions

u user access permissions

+ add the permission to current status of files

- remove the permission from status of files



= set the permission of files to specified value

r read permission

s set owner -ID or group -ID on execution (usable only with g or u)

t save text mode

w write permission

x execute permission

cpcopy files

$ cp [options] file 1 file 2

make a copy of file 1 named file 2

$ cp [options] files directory

make copies of specified files in directory

Options:

-i prompt user before overwriting file

-p copies have same modification times and modes as source files

-r recursive copy of directory (with subdirectories)

dfReport Free Block Count

$ df [options][filesys][file]

Options:

-i print number of modes free and in use

files df reports on file system containing files

filesys is a list of device names or mounted directory names to report(default = all mounted)



duSummarize Disk Usage

$ du [options][names]

Options:

-a generate entry for each file

-s only display a grand total summary (default is entry for eachdirectory)

names directory names or filenames

grepSearch File for Pattern

$ grep [options]expr [files]

stdin read if no files specified

Options:

-b precede line with block number

-c print count of matching lines only

-e expr useful if the expr start with a -

-i ignore case of letters in search

-l print only names of files with matching lines

-n print line numbers

-s print error messages only

-v print non-matching lines

-w search for expression as a word

expr expression or pattern



killTerminate Process

$ kill -l

list signal names

$ kill [signal]process-ids

Options:

signal send signal instead of terminate

0 for process-id implies all processes resulting from current login

lnMake Links to File

$ ln [option] file1 file2

make a link to file1 named file2

$ ln [option] files directory

make links of specified files in directory

$ ln [option] pathname

make link with same name in current directory

Option:

-s make symbolic link (hard link default)

loginSign On to System

$ login [option][user]

login as user, logout if no user specified

lsList Contents of Directories

$ ls [options][names]



names can be files of directories

current working directory used if no name specified

Options:

-1 print listing of one entry per line

-a list all entries (including ones starting with.)

-d list only name (not contents) of directory

-l long list (mode, links, owner, size, mod. time)

-r reverse sort order

-R recursively print subdirectories

-s print file size in kilobytes

manPrint Manual Entries

$ man -k keywords

print 1 line synopsis for each section containing keywords

$ man -f files

print 1 line synopsis for sections related to files

$ man [options][section] cmds

print manual sections for each cmd specified

Options:

- pipe output through more (default on terminals)

-M path to search for entries (/usr/man/default)

-t troff output to raster device

path list of directories to search, separated by colons section Arabicsection number, followed by optional letter signifying type of command



dirCreate Specified Directories

$ mkdir directories

moreView file by Screenful or by Line

$ more [options][files]

Options:

-c redraw page one line at a time

-d prompt after each screenful

-f count by newlines instead of screen lines

-l treat formfeed (L) as ordinary character

-n window size (default set with stty)

+n start viewing file at line n

-s reduce multiple blank lines to one

-u suppress terminal underlining or enhancing

+/pat start two lines before line containing pat

Enter h when more pauses for interactive options

mvMove Files (See CP)

$ mv [options] file1 file2

rename (or move) file1 file2

$ mv [options] files directory

rename (or move) specified files to directory



Options:

- following arguments are filenames

-f force overwriting of existing files

-i interactive mode

psReport Process Status

$ ps [keys][-t list][process-id]

Keys:

a print all processes involving terminals

c print internally stored command name

e print both environment and arguments

g print all processes

k use/vmcore in place of /dev/kmem and /dev/mem for debugging llong listing

n process number (must be last key)

s add size of kernel stack of process to output

tn list processes associated with terminals; n is terminal number(must be last key)

u include fields of interest to user

U update namelist database (for speed)

v print virtual memory statistics

w 132 column output format

ww arbitrarily wide output

x include processes with no terminal



pwdPrint Working Directory Name

$ pwd

rcpCopy Files Between Machines

$ rcp [option] file1 file2

copy file1 file2

$ [options] files directory

copy files to specified directory

Options:

-p copies have same modification times and modes as source files

-r recursive copy of directories

rloginLogin on Remote Terminal

$ [rlogin] remote [options]

Options:

-8 allow 8 bit data path

-ec specify new escape character c

-l user user is login name on remote system

-L run remote session in litout mode

remote remote host system

rlogin is optional if /usr/hosts in search path

rmRemove Files

$ rm [options] files



Options:

- treat all following arguments as filenames

-i ask for confirmation before each delete

-r recursively delete directories

rmdirRemove Empty Directories (See RM)

$ rmdir directories

suBecome Another User (Set User)

$ su [options][user]

user defaults to root

Options:

- act like full login

-f if csh, don’t execute .cshrc

tarTape file Archiver

$ tar [key][option][files]

stdin read if no files specified

Keys: format: letter [modifiers]

Function Letters:

c create new tape and record files

t tell when files found, all entries if no files

x extract files, entire tape if no files



Function Modifiers:

0...9 specify which tape drive to use (0 default)

b next arg is blocking factor (20 default, 20 max)

B force I/O blocking at 20 blocks per record

f arch arch is the file to be used for input/output to archives (if-thenstdin read)

h follow symbolic links

l complain if all file links not found

m update file modification times

v verbose mode

w wait for confirmation after reporting filename (y causes action tobe performed)

Option:

-C dir change directory to dir

whoWho is on the System

$ who [file][am i]

Arguments:

file read instead of /etc/utmp for login information

am i output who you are logged in as

whoamiPrint Effective User-Id

$ whoami

works even if you have become another user with su.



Examples of UNIX Commands

Most of the following commands apply to Berkeley UNIX. Some of thecommands will be different or even unavailable, depending on whichshell you are using. The following examples refer to the C shell, and donot necessarily work with the Bourne or Korn shells.

alias promax /advance/sys/bin/promax&

The alias command is used to substitute a short, convenient commandin place of a longer command. In this case, promax is the new (alias)command. From this point on, typing promax will be equivalent totyping the full /advance/sys/bin/promax&.

Note: This alias will only be effective until you log out. If you want it tobe available each time you log in, place this line in your .cshrc file. Thisis a C shell command.

cp -r /advance/data/offshore .

cp is the copy command. The -r tells the system that you want to copyrecursively (useful for copying directories trees). The directory fromwhich you are copying in this case is /advance/data/offshore. Note thefinal ., which denotes the target directory. The single . means the currentdirectory. Be careful about how you specify the target directory. If youtold the system to copy the files to a directory offshore and this directoryalready exists, then the files will end up in offshore/offshore.

df

df shows the amount of free space on all the currently mounted filesystems, including remotely mounted file systems. The listing will showyou which of the file systems are remotely mounted. It is possible tospecify one file system and see the amount of free space in only that filesystem. If you do not specify a file system, then df will default toshowing all the mounted file systems. There are many other options fordf which you may find useful.

du -s offshore

The du command summarizes disk usage. It can show disk usage file byfile. When the -s option is given, only a grand total summary of disk



usage is produced. Specifying offshore requests a disk usage report forthat directory.

grep -i STAT elev_stat_math | grep -i CDP

grep is the search command. This command will search for the lineswithin the file elev_stat_math which contain the string STAT. The -icauses the search to ignore upper or lower case differences. Without thisoption, it would look for STAT exactly, in upper case. The | or piperedirects the output from the search into another grep command. Thisagain performs a case-insensitive search for CDP. Because the outputfrom the first search contains only lines with the string STAT, the resultof the piped search will contain only lines with both STAT and CDP.

grep STAT header.list static_hdrs

This grep will search the file header.list for lines containing the stringsource in upper case letters only, and then will direct the output of thesearch to a file called static_hdrs.

kill -9 2367

The kill command will stop a current process by sending a signal. Theprocess number in this case is number 2367, which was found by usingthe ps command. There are many modifiers for this command, but onewhich you should know is the -9. This makes it impossible for theprocess to ignore the signal.

You might use this when a process is locked up and there is no other wayto stop it.

ln -s /advance/data2/oswork offshore

The ln command means link. The -s denotes a symbolic link. This canbe used to link files on different file systems. A normal link, sometimesknown as a hard link, specified as ln without the -s, cannot link betweenfile systems.

This symbolic link will cause the directory /advance/data2/oswork toappear in the current directory under the name offshore. It is not a newdirectory, or a copy of the oswork directory in /advance/data2. Whenyou access a file in your directory called offshore, you are actuallyaccessing the original file in the directory /advance/data2/oswork.



Therefore any changes made in offshore will be made to in /advance/data2/os work.

You should be aware that certain commands act differently whenapplied to a linked file. For example, if you delete the linked file usingrm applied to the linked file in your directory, only the link is removed.The original file is intact. But if you copy the linked file with cp appliedto the file in your directory, the system will make a copy of the originalfile.

ps -ax

The ps (process status) command shows all of the processes currentlyrunning on the system. The -a tells the system to display all processesexcept process group leaders and processes not started from terminals.The x shows processes without control terminals. If you do not specifythe x, then you may not see the process for which you are looking. The-ax on Berkeley UNIX changes to -elf on System V UNIX. The lprovides a long form of the listing, -f provides a full listing of theprocesses, and -e asks for every process on the system.

rcp -r neptune:/usr/disk2/offshore .

rcp is the remote copy command. The -r, as with the cp command, is therecursive form of copy. It will copy the /usr/disk2/offshore directory andits subdirectories from the named server. The destination directory is .,the current working directory.

rmdir offshore

The rmdir command removes directories. In this example the rmdircommand will remove the directory offshore. rmdir will only remove anempty directory. If you still have entries in the directory, this commandwill fail. You can check the contents of the directory, to see if it containsfiles you meant to keep. Or you can use the rm -r command, at your ownrisk.

tar c /advance/data/offshore

The tar command (tape archive) is used for moving files to or from tape.The c means create, so a new tape will be created. The directory to becopied to tape is /advance/data/offshore. To copy more directories totape, just list them after the first directory, separated by spaces. x inplace of the c will extract files from the tape and copy them to the disk.



tar x with no files listed will read everything off the tape. tar x followedby a file name, directory or path will only read the data if it exists on thetape. This is a safe way to get back a specific dataset from the tape. Thev option is verbose, so that you can see what the process is doing.Otherwise, like most UNIX processes, it is silent. You may wish toinvestigate cpio as a more versatile alternative to tar.

tar c ./offshore

This tar command copies to tape the directory offshore and the fileswhich belong to the directory offshore. The ./ preceding ‘offshore’indicates that offshore is a subdirectory of the current working directory.It is generally best to use relative path names (rather than full pathnames) when you are using tar.

Documents

ProMAX Seismic manual