SeisUP PDF

SeisUP Applications Manual
Table of Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Introduction to the SeisUP administrative and programming tools
SeisUP Configuration Files .
.
.
.
.
.
.
.
.
.
Dataset Naming Convention
.
.
.
.
.
.
.
.
.
DIRECTORY TREE .
.
.
.
.
.
.
.
.
.
.
SeisUP Files Stored in User Home Directories
.
.
.
.
.
LICENSE_INSTALL .
.
.
.
.
.
.
.
.
.
.
SEISUP_LMGRD_INSTALL .
.
.
.
.
.
.
.
.
CHKDSET
.
.
.
.
.
.
.
.
.
.
.
.
.
CHKLINKS .
.
.
.
.
.
.
.
.
.
.
.
.
CLEANUP_RUN_LOGS .
.
.
.
.
.
.
.
.
.
DSET_FILES .
.
.
.
.
.
.
.
.
.
.
.
.
DSKINV .
.
.
.
.
.
.
.
.
.
.
.
.
.
DUMP_JOB_CACHE .
.
.
.
.
.
.
.
.
.
.
JM_MULTICAST_MONITOR .
.
.
.
.
.
.
.
.
PROJECT_DATA .
.
.
.
.
.
.
.
.
.
.
.
SEISUPD_ADMIN
.
.
.
.
.
.
.
.
.
.
.
SEISUPD_CTL
.
.
.
.
.
.
.
.
.
.
.
.
SEISUPD_INSTALL .
.
.
.
.
.
.
.
.
.
.
SEISUPD_LOG_MON .
.
.
.
.
.
.
.
.
.
.
SELECT_PLOTTING_SUBSYSTEM .
.
.
.
.
.
.
SET_HELP_VIEWER .
.
.
.
.
.
.
.
.
.
.
TAPEINIT
.
.
.
.
.
.
.
.
.
.
.
.
.
TAPESERV .
.
.
.
.
.
.
.
.
.
.
.
.
CLUSTER_COMMAND .
.
.
.
.
.
.
.
.
.
NODE_NAMES .
.
.
.
.
.
.
.
.
.
.
.
CLUSTER_DIST .
.
.
.
.
.
.
.
.
.
.
.
CLUSTER_HOST_ENTRIES .
.
.
.
.
.
.
.
.
CLUSTER_NODE_ENTRIES .
.
.
.
.
.
.
.
.
CLUSTER_POWEROFF .
.
.
.
.
.
.
.
.
.
CLUSTER_REBOOT .
.
.
.
.
.
.
.
.
.
.
DIST_CLUSTER_PROGRAM .
.
.
.
.
.
.
.
.
RKILL.PL
.
.
.
.
.
.
.
.
.
.
.
.
.
RUTIL
.
.
.
.
.
.
.
.
.
.
.
.
.
.
COMPACT .
.
.
.
.
.
.
.
.
.
.
.
.
CONFIG_SEISUP_SCRIPT
.
.
.
.
.
.
.
.
.
CONVFLOW6_7 .
.
.
.
.
.
.
.
.
.
.
.
DB_DUMP
.
.
.
.
.
.
.
.
.
.
.
.
.
DBU .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
DUMP_FLOW
.
.
.
.
.
.
.
.
.
.
.
.
DUMP_ID .
.
.
.
.
.
.
.
.
.
.
.
.
.
GOODBAD .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
2
4
7
11
12
14
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
LOCKUP
.
.
.
.
.
.
REBUILD .
.
.
.
.
.
SEGMENTATION FAULT .
.
BUGREPORTS .
.
.
.
.
PROGRAMMING .
.
.
.
CAT_UPDATE Wrapper .
.
.
CATOUT
.
.
.
.
.
.
EXEC_DEBUG .
.
.
.
.
LS_HORIZONS .
.
.
.
.
LST_NODES
.
.
.
.
.
MODGEN .
.
.
.
.
.
PLOT_LOGOS .
.
.
.
.
PVM_HOSTS
.
.
.
.
.
LST_NODES
.
.
.
.
.
SeisUP Data Manager
.
.
.
SeisUP Filesystems Manager .
.
Options menu
.
.
.
.
.
SeisUP Tape Devices Manager
.
Introduction to the SeisUP system .
Using the flow editor .
.
.
.
Parts of the flow editor
.
.
.
Opening an existing flow .
.
.
Saving a flow .
.
.
.
.
.
Deleting a line
.
.
.
.
.
Quitting the flow editor .
.
.
Selecting icons
.
.
.
.
.
Inserting modules
.
.
.
.
Editing flows and icons .
.
.
Copying parts of a line to another line
Grouping icons .
.
.
.
.
Ungrouping icons .
.
.
.
.
Connecting modules .
.
.
.
Disconnecting modules
.
.
.
Query the connections of a node .
Releasing data sets
.
.
.
.
Seismic data inventory program .
Using Motif .
.
.
.
.
.
Lists .
.
.
.
.
.
.
.
Scroll bars .
.
.
.
.
.
Push button .
.
.
.
.
.
Check boxes and Radio buttons .
Text Input Field .
.
.
.
.
Using pull-down menus .
.
.
File selection box .
.
.
.
.
Managing Windows .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
52
.
53
.
54
.
55
.
56
.
57
.
58
.
59
.
60
.
61
.
62
.
63
.
64
.
65
.
66
.
73
.
75
.
77
.
80
.
82
.
83
.
84
.
85
.
86
.
87
.
88
.
89
.
90
.
92
.
93
.
94
.
95
.
96
.
97
.
98
.
99
.
101
.
102
.
103
.
104
.
105
.
106
.
107
.
108
.
109
.
Creating a flow .
.
.
.
.
.
.
.
.
File menu
.
.
.
.
.
.
.
.
.
.
Creating an input data set .
.
.
.
.
.
.
Using the execution type ahead buffer .
.
.
.
Edit tape attributes for tape .
.
.
.
.
.
Adding modules .
.
.
.
.
.
.
.
.
Using the module librarian
.
.
.
.
.
.
Setting module parameters
.
.
.
.
.
.
Using the flow pop-up menu .
.
.
.
.
.
Executing modules
.
.
.
.
.
.
.
.
Module types .
.
.
.
.
.
.
.
.
.
Selecting the Current Host
.
.
.
.
.
.
Execute menu
.
.
.
.
.
.
.
.
.
Flow editor menus
.
.
.
.
.
.
.
.
Edit menu
.
.
.
.
.
.
.
.
.
.
Find menu .
.
.
.
.
.
.
.
.
.
Module menu
.
.
.
.
.
.
.
.
.
Tools menu .
.
.
.
.
.
.
.
.
.
Glossary .
.
.
.
.
.
.
.
.
.
.
Geosp Using the matrix editor .
.
.
.
.
.
Geosp Parts of the matrix editor .
.
.
.
.
Geosp Matrix Editor File Menu .
.
.
.
.
Geosp Matrix Editor Edit Menu .
.
.
.
.
Geosp Tools Menu
.
.
.
.
.
.
.
.
Geosp Moving the current cell .
.
.
.
.
.
Geosp Selecting cells .
.
.
.
.
.
.
.
Geosp Cut, Copy, and Paste .
.
.
.
.
.
Geosp Moving Cell Values
.
.
.
.
.
.
Geosp Entering or updating values in a spreadsheet
Geosp Filling Cell Values .
.
.
.
.
.
.
Geosp Interpolating Cell Values .
.
.
.
.
Geosp Arithmetic Operations .
.
.
.
.
.
Geosp Sorting cell values .
.
.
.
.
.
.
Geosp Inserting Rows .
.
.
.
.
.
.
.
Geosp Deleting Rows .
.
.
.
.
.
.
.
Geosp Clearing Cell Values .
.
.
.
.
.
Geosp Creating a new spreadsheet .
.
.
.
.
Geosp Saving a spreadsheet .
.
.
.
.
.
Geosp Deleting a spreadsheet .
.
.
.
.
.
Geosp Navigating through spreadsheets
.
.
.
Geosp Go to Sheet
.
.
.
.
.
.
.
.
Geosp Importing matrix files .
.
.
.
.
.
Geosp Exporting matrix files .
.
.
.
.
.
Geosp Picking spreadsheets to export .
.
.
.
Geosp Quitting the Matrix Editor .
.
.
.
.
iii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
112
.
113
.
114
.
115
.
116
.
117
.
118
.
119
.
121
.
123
.
125
.
126
.
127
.
128
.
129
.
130
.
131
.
132
.
135
.
136
.
138
.
139
.
140
.
141
.
142
.
143
.
144
.
145
.
146
.
147
.
148
.
149
.
150
.
151
.
152
.
153
.
154
.
155
.
156
.
157
.
158
.
159
.
161
.
162
.
163
.
Geosp Matrix Editor Menus .

.
.
.
.
SeisUP - History Viewer - Help Documentation .
SeisUP -Job Monitor- Help Documentation .
.
SeisUP Job Server Administration Manual .
.
SeisUP Licensing Manual .
.
.
.
.
.
SeisUP Plotting Subsystem
.
.
.
.
.
SeisUP Reference Manual .
.
.
.
.
.
SeisUP Reference Manual: ADAPTDCN Module
SeisUP Reference Manual: ADDHDR Module .
SeisUP Reference Manual: AHCVEL Module .
SeisUP Reference Manual: AMPCOR Module .
SeisUP Reference Manual: AMPSTAT Module .
SeisUP Reference Manual: ASCREAD Module .
SeisUP Reference Manual: AUTC Module .
.
SeisUP Reference Manual: AUTOREV Module
SeisUP Reference Manual: AVOA Module .
.
SeisUP Reference Manual: AVOCROSS Module
SeisUP Reference Manual: AVOSCALE Module
SeisUP Reference Manual: AZIMVTRY Module
SeisUP Reference Manual: BINLINE Module .
SeisUP Reference Manual: BINREAD Module .
SeisUP Reference Manual: BLIP Module .
.
SeisUP Reference Manual: BSSE Module .
.
SeisUP Reference Manual: CAZM Module .
.
SeisUP Reference Manual: CCPBIN Module .
SeisUP Reference Manual: CENSUSDB Module
SeisUP Reference Manual: CHKNAN Module .
SeisUP Reference Manual: CLIP Module .
.
SeisUP Reference Manual: CLUSTEST Module
SeisUP Reference Manual: CMPLINE Module .
SeisUP Reference Manual: CNSGEOM Module
SeisUP Reference Manual: COFF Module .
.
SeisUP Reference Manual: COHFILT Module .
SeisUP Reference Manual: COMREAD Module
SeisUP Reference Manual: COMWRITE Module
SeisUP Reference Manual: CONV Module .
.
SeisUP Reference Manual: CROSSTIE Module
SeisUP Reference Manual: CUT3D Module
.
SeisUP Reference Manual: CVA2D Module
.
SeisUP Reference Manual: CVA3D Module
.
SeisUP Reference Manual: CVA3DHTI Module
SeisUP Reference Manual: CVFB Module .
.
SeisUP Reference Manual: CVGMA Module .
SeisUP Reference Manual: DBHDR Module
.
SeisUP Reference Manual: DBINQ Module
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
164
.
165
.
170
.
177
.
189
.
212
.
216
.
222
.
225
.
226
.
227
.
233
.
236
.
237
.
240
.
243
.
253
.
266
.
268
.
270
.
272
.
275
.
277
.
279
.
284
.
287
.
288
.
289
.
290
.
292
.
294
.
299
.
303
.
306
.
307
.
310
.
313
.
314
.
316
.
321
.
327
.
331
.
332
.
333
.
337
.
SeisUP Reference Manual: DBMERGE Module

SeisUP Reference Manual: DCBIAS Module .
SeisUP Reference Manual: DECON Module
.
SeisUP Reference Manual: DELHORZ Module
SeisUP Reference Manual: DELTAXY Module .
SeisUP Reference Manual: DEMUX Module .
SeisUP Reference Manual: DEPTH Module
.
SeisUP Reference Manual: DESPIKE Module .
SeisUP Reference Manual: DICE Module .
.
SeisUP Reference Manual: DICE3D Module .
SeisUP Reference Manual: DIPMOD Module .
SeisUP Reference Manual: DISINTG Module .
SeisUP Reference Manual: DISPLAY Module .
SeisUP Reference Manual: DLIST Module .
.
SeisUP Reference Manual: DMO3D Module
.
SeisUP Reference Manual: DMODIST Module .
SeisUP Reference Manual: DMOG Module
.
SeisUP Reference Manual: DMOS Module .
.
SeisUP Reference Manual: DNG1 Module .
.
SeisUP Reference Manual: DNG2 Module .
.
SeisUP Reference Manual: DTYPE Module
.
SeisUP Reference Manual: ELASTICP Module
SeisUP Reference Manual: ELETOFLT Module
SeisUP Reference Manual: ENDIF Module .
.
SeisUP Reference Manual: ENSBAL Module .
SeisUP Reference Manual: ENSCLN Module .
SeisUP Reference Manual: ENSDCN1 Module .
SeisUP Reference Manual: ENSDCN2 Module .
SeisUP Reference Manual: ENSFFT Module .
SeisUP Reference Manual: ENSMATH Module
SeisUP Reference Manual: ENSSCALE Module
SeisUP Reference Manual: EQDIST Module .
SeisUP Reference Manual: EQDMO Module .
SeisUP Reference Manual: EXPHORZ Module .
SeisUP Reference Manual: EXTRACT Module .
SeisUP Reference Manual: FAKE3D2 Module .
SeisUP Reference Manual: FBPBO2D Module .
SeisUP Reference Manual: FBPICKMC Module
SeisUP Reference Manual: FCVFB Module
.
SeisUP Reference Manual: FDAF Module .
.
SeisUP Reference Manual: FDMIG2D Module .
SeisUP Reference Manual: FDMIG3D Module .
SeisUP Reference Manual: FDUMP Module
.
SeisUP Reference Manual: FILTER Module .
SeisUP Reference Manual: FKFILT Module .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
338
.
340
.
341
.
348
.
349
.
352
.
358
.
359
.
360
.
363
.
366
.
368
.
369
.
393
.
395
.
401
.
403
.
407
.
411
.
415
.
416
.
417
.
421
.
423
.
425
.
428
.
430
.
436
.
438
.
440
.
442
.
447
.
450
.
455
.
457
.
459
.
461
.
464
.
468
.
470
.
474
.
477
.
485
.
487
.
490
.
SeisUP Reference Manual: FKINT Module .

.
SeisUP Reference Manual: FKKFILT Module .
SeisUP Reference Manual: FKMIG Module
.
SeisUP Reference Manual: FKMOD Module .
SeisUP Reference Manual: FKMRC Module .
SeisUP Reference Manual: FKPLOT Module .
SeisUP Reference Manual: FLAT Module .
.
SeisUP Reference Manual: FLEX Module .
.
SeisUP Reference Manual: FLEXBIN Module .
SeisUP Reference Manual: FOLD Module .
.
SeisUP Reference Manual: FORTHPIK Module
SeisUP Reference Manual: FRACDET Module .
SeisUP Reference Manual: FREQTUNE Module
SeisUP Reference Manual: FRFSTPRP Module
SeisUP Reference Manual: FXDN Module .
.
SeisUP Reference Manual: FXYDMIG Module .
SeisUP Reference Manual: FXYDN Module
.
SeisUP Reference Manual: FXYMIG Module .
SeisUP Reference Manual: FXYMIGEX Module
SeisUP Reference Manual: FXYMIGR Module .
SeisUP Reference Manual: GAIN Module .
.
SeisUP Reference Manual: GAMLSEIS Module
SeisUP Reference Manual: GCHG2D Module .
SeisUP Reference Manual: GEOM Module .
.
SeisUP Reference Manual: GEOMCK Module .
SeisUP Reference Manual: GEOMEXT Module
SeisUP Reference Manual: GEOMVIEW Module
SeisUP Reference Manual: GEOVEL Module .
SeisUP Reference Manual: GEOVEL3C Module
SeisUP Reference Manual: GNATTR Module .
SeisUP Reference Manual: GNPLOT Module .
SeisUP Reference Manual: GRNMTN Module .
SeisUP Reference Manual: GRVA Module .
.
SeisUP Reference Manual: GVLPICK Module .
SeisUP Reference Manual: GVLPRINT Module
SeisUP Reference Manual: HAMPSON Module
SeisUP Reference Manual: HDRDUMP Module
SeisUP Reference Manual: HDRINTP Module .
SeisUP Reference Manual: HDRSTK Module .
SeisUP Reference Manual: HILBERT Module .
SeisUP Reference Manual: HIP Module
.
.
SeisUP Reference Manual: HMTH Module .
.
SeisUP Reference Manual: HORIZON Module .
SeisUP Reference Manual: HORZIMP Module .
SeisUP Reference Manual: HSUM Module .
.
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
494
.
496
.
502
.
508
.
514
.
517
.
519
.
521
.
523
.
526
.
529
.
534
.
539
.
543
.
545
.
547
.
551
.
553
.
557
.
558
.
559
.
561
.
572
.
575
.
579
.
582
.
586
.
589
.
595
.
599
.
602
.
604
.
608
.
617
.
622
.
625
.
627
.
630
.
634
.
639
.
640
.
641
.
642
.
644
.
647
.
SeisUP Reference Manual: IDLINBIN Module .

SeisUP Reference Manual: IDRENUM Module .
SeisUP Reference Manual: IF Module .
.
.
SeisUP Reference Manual: IMPHORZ Module .
SeisUP Reference Manual: IMPLS3D Module .
SeisUP Reference Manual: INTGRT Module .
SeisUP Reference Manual: INVEL Module .
.
SeisUP Reference Manual: INVERSN Module .
SeisUP Reference Manual: ISOV Module .
.
SeisUP Reference Manual: IVEP Module .
.
SeisUP Reference Manual: KAPTURE Module .
SeisUP Reference Manual: KFIL Module .
.
SeisUP Reference Manual: KTMIG Module
.
SeisUP Reference Manual: LAME Module .
.
SeisUP Reference Manual: LAP Module .
.
SeisUP Reference Manual: LCKF Module .
.
SeisUP Reference Manual: LENGTH Module .
SeisUP Reference Manual: LENGTH2 Module .
SeisUP Reference Manual: LINE3D Module
.
SeisUP Reference Manual: LINENAME Module
SeisUP Reference Manual: LINSUB Module .
SeisUP Reference Manual: LOGREAD Module
SeisUP Reference Manual: LRADON Module .
SeisUP Reference Manual: MAPCON Module .
SeisUP Reference Manual: MARINE Module .
SeisUP Reference Manual: MATCH Module .
SeisUP Reference Manual: MATCH2 Module .
SeisUP Reference Manual: MATCON Module .
SeisUP Reference Manual: MCADPDCN Module
SeisUP Reference Manual: MGEOM Module .
SeisUP Reference Manual: MGRIDP1 Module .
SeisUP Reference Manual: MIDGEOM Module
SeisUP Reference Manual: MIX3D Module
.
SeisUP Reference Manual: MIXD3D Module .
SeisUP Reference Manual: MNMXAMP Module
SeisUP Reference Manual: MONOSUB Module
SeisUP Reference Manual: MPAS Module .
.
SeisUP Reference Manual: MSOURCE Module
SeisUP Reference Manual: MSTATION Module
SeisUP Reference Manual: MULP Module .
.
SeisUP Reference Manual: MUTE Module .
.
SeisUP Reference Manual: MVREC Module .
SeisUP Reference Manual: NMO3D Module
.
SeisUP Reference Manual: NMOA Module .
.
SeisUP Reference Manual: NMOR Module .
.
vii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
648
.
649
.
651
.
652
.
655
.
657
.
659
.
660
.
667
.
670
.
680
.
682
.
685
.
702
.
704
.
707
.
710
.
711
.
713
.
716
.
718
.
722
.
724
.
736
.
738
.
740
.
742
.
744
.
745
.
750
.
754
.
756
.
757
.
761
.
770
.
771
.
773
.
780
.
783
.
788
.
793
.
798
.
799
.
801
.
803
.
SeisUP Reference Manual: NOISE Module .

.
SeisUP Reference Manual: NOISEDIT Module .
SeisUP Reference Manual: NOPERMIT Module
SeisUP Reference Manual: NOTCH Module
.
SeisUP Reference Manual: NSUB Module .
.
SeisUP Reference Manual: NTEXT Module
.
SeisUP Reference Manual: OFFSCALE Module
SeisUP Reference Manual: OMIT Module .
.
SeisUP Reference Manual: OPTDCN1 Module .
SeisUP Reference Manual: OPTDCN2 Module .
SeisUP Reference Manual: OPTDCNPL Module
SeisUP Reference Manual: OPTMUTE Module
SeisUP Reference Manual: PAD3D Module
.
SeisUP Reference Manual: PICKSHIF Module .
SeisUP Reference Manual: PILOT Module .
.
SeisUP Reference Manual: PILOT2 Module
.
SeisUP Reference Manual: PKMIG Module
.
SeisUP Reference Manual: PLOT Module .
.
SeisUP Reference Manual: PMNORM Module .
SeisUP Reference Manual: POLINT Module .
SeisUP Reference Manual: POWER Module .
SeisUP Reference Manual: PSI3D Module .
.
SeisUP Reference Manual: PSMIG2D Module .
SeisUP Reference Manual: PSMIG3D Module .
SeisUP Reference Manual: PSUTIL Module
.
SeisUP Reference Manual: PTHROW Module .
SeisUP Reference Manual: PTSLICE Module .
SeisUP Reference Manual: PWAVO Module .
SeisUP Reference Manual: QC3D Module .
.
SeisUP Reference Manual: QCMUTE Module .
SeisUP Reference Manual: QCOMP Module .
SeisUP Reference Manual: QCVEL Module
.
SeisUP Reference Manual: QCVIEW Module .
SeisUP Reference Manual: QDERIVE Module .
SeisUP Reference Manual: QFILTER Module .
SeisUP Reference Manual: RADON Module
.
SeisUP Reference Manual: RADON1 Module .
SeisUP Reference Manual: RADONC Module .
SeisUP Reference Manual: RAS1 Module .
.
.
.
SeisUP Reference Manual: RAS3D1 Module .
SeisUP Reference Manual: RAS3D2 Module .
.
SeisUP Reference Manual: RDMO Module .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
813
.
814
.
817
.
821
.
825
.
826
.
828
.
830
.
832
.
838
.
840
.
845
.
847
.
848
.
849
.
852
.
854
.
856
.
883
.
884
.
886
.
888
.
892
.
899
.
908
.
910
.
913
.
915
.
927
.
929
.
931
.
935
.
938
.
954
.
958
.
962
.
969
.
982
.
995
.
997
.
998
.
999
.
1002
.
1004
.
1006
.
SeisUP Reference Manual: READ Module .

.
SeisUP Reference Manual: REFST Module
.
SeisUP Reference Manual: REFSTPRP Module
SeisUP Reference Manual: REGRID Module .
SeisUP Reference Manual: SOURCE Module .
SeisUP Reference Manual: REPEAT Module .
SeisUP Reference Manual: RESAMP Module .
SeisUP Reference Manual: RESID1 Module
.
SeisUP Reference Manual: RESID2 Module
.
SeisUP Reference Manual: RESMERGE Module
SeisUP Reference Manual: RFMT Module .
.
SeisUP Reference Manual: RFS1 Module .
.
SeisUP Reference Manual: RLIV Module .
.
SeisUP Reference Manual: RMHDR Module .
SeisUP Reference Manual: RNDCLN Module .
SeisUP Reference Manual: ROTATE Module .
SeisUP Reference Manual: ROTATE2C Module
SeisUP Reference Manual: ROTATE4C Module
SeisUP Reference Manual: RSIM Module .
.
SeisUP Reference Manual: RT3D Module .
.
SeisUP Reference Manual: RWSUM Module .
SeisUP Reference Manual: RZERO Module
.
SeisUP Reference Manual: SCALE Module
.
SeisUP Reference Manual: SCAT Module .
.
SeisUP Reference Manual: SCDCN1 Module .
SeisUP Reference Manual: SCDECON1 Module
SeisUP Reference Manual: SCDECON2 Module
SeisUP Reference Manual: SCPHD1 Module .
SeisUP Reference Manual: SEG2 Module .
.
SeisUP Reference Manual: SEGP1 Module .
.
SeisUP Reference Manual: SEGYREAD Module
SeisUP Reference Manual: SEGYWRIT Module
SeisUP Reference Manual: SELECT Module .
SeisUP Reference Manual: SGN1 Module .
.
.
.
SeisUP Reference Manual: SGNE1 Module
.
SeisUP Reference Manual: SGNE2 Module
.
SeisUP Reference Manual: SLICE Module .
.
SeisUP Reference Manual: SMIG Module .
.
SeisUP Reference Manual: SMIGSAVE Module
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ix
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1010
.
1015
.
1026
.
1028
.
1030
.
1035
.
1037
.
1038
.
1047
.
1056
.
1057
.
1064
.
1071
.
1075
.
1076
.
1078
.
1080
.
1086
.
1094
.
1095
.
1096
.
1097
.
1098
.
1101
.
1103
.
1106
.
1108
.
1109
.
1120
.
1124
.
1127
.
1129
.
1130
.
1133
.
1135
.
1144
.
1149
.
1151
.
1153
.
1158
.
1160
.
1163
.
1165
.
1166
.
1173
.
SeisUP Reference Manual: SMOOTH Module .

SeisUP Reference Manual: SMTHANG Module
SeisUP Reference Manual: SMVSLICE Module
SeisUP Reference Manual: SNR Module .
.
SeisUP Reference Manual: SORT Module .
.
SeisUP Reference Manual: SOURCE Module .
SeisUP Reference Manual: SPER Module .
.
SeisUP Reference Manual: SPIKEDIT Module .
SeisUP Reference Manual: SPRSKID Module .
SeisUP Reference Manual: SPS Module
.
.
SeisUP Reference Manual: SQUEEZE Module .
SeisUP Reference Manual: SRINTERP Module
SeisUP Reference Manual: SSDECON Module .
SeisUP Reference Manual: SSMP Module .
.
SeisUP Reference Manual: STACK Module
.
SeisUP Reference Manual: STACK3D Module .
SeisUP Reference Manual: STATIC Module .
SeisUP Reference Manual: STATINTP Module
SeisUP Reference Manual: STATION Module .
SeisUP Reference Manual: STKSNR Module .
SeisUP Reference Manual: STRETCH Module .
SeisUP Reference Manual: STRM Module .
.
SeisUP Reference Manual: STTINTP Module .
SeisUP Reference Manual: SUBSEGY Module .
SeisUP Reference Manual: SURFWAVE Module
SeisUP Reference Manual: SURMAT Module .
SeisUP Reference Manual: SWAP Module .
.
SeisUP Reference Manual: SYNDIP Module .
SeisUP Reference Manual: SYNTH Module
.
SeisUP Reference Manual: TAUF Module .
.
SeisUP Reference Manual: TAUPDMO Module
SeisUP Reference Manual: TCOPY Module
.
SeisUP Reference Manual: TDAF Module .
.
SeisUP Reference Manual: TDUMP Module
.
SeisUP Reference Manual: TFDNOISE Module
SeisUP Reference Manual: TOVG0 Module
.
SeisUP Reference Manual: TRACECAL Module
SeisUP Reference Manual: TRACECMB Module
SeisUP Reference Manual: TRACEFFT Module
SeisUP Reference Manual: TRANSPOS Module
SeisUP Reference Manual: TRCPLOT Module .
SeisUP Reference Manual: TRCREM Module .
SeisUP Reference Manual: TRIMCMP Module
SeisUP Reference Manual: TRIP Module .
.
SeisUP Reference Manual: TRIP5D Module
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1174
.
1177
.
1178
.
1182
.
1184
.
1186
.
1191
.
1194
.
1197
.
1198
.
1202
.
1203
.
1206
.
1211
.
1213
.
1215
.
1217
.
1230
.
1232
.
1238
.
1240
.
1241
.
1243
.
1245
.
1247
.
1249
.
1251
.
1253
.
1256
.
1258
.
1262
.
1266
.
1267
.
1270
.
1279
.
1285
.
1287
.
1294
.
1298
.
1300
.
1302
.
1308
.
1310
.
1315
.
1317
.
SeisUP Reference Manual: TVEQ Module .

.
SeisUP Reference Manual: TVMULT Module .
SeisUP Reference Manual: TVSA Module .
.
SeisUP Reference Manual: TVSAC Module
.
SeisUP Reference Manual: TVSE Module .
.
SeisUP Reference Manual: TVSEC Module
.
SeisUP Reference Manual: TVTRIM Module .
SeisUP Reference Manual: TVZD Module .
.
SeisUP Reference Manual: UKOOA Module .
SeisUP Reference Manual: UNDUPE Module .
SeisUP Reference Manual: UNSCALE Module .
SeisUP Reference Manual: VA3C Module .
.
SeisUP Reference Manual: VCOR Module .
.
SeisUP Reference Manual: VELCONV Module
SeisUP Reference Manual: VELSMTH Module
SeisUP Reference Manual: VEXTRACT Module
SeisUP Reference Manual: VIBMIN Module .
SeisUP Reference Manual: VIEWER3D Module
SeisUP Reference Manual: VIMPEXP Module .
SeisUP Reference Manual: VIP Module
.
.
SeisUP Reference Manual: VIPINV Module
.
SeisUP Reference Manual: VIPMATH Module .
SeisUP Reference Manual: VORMED Module .
SeisUP Reference Manual: VORONOI Module .
SeisUP Reference Manual: VORSCL Module .
SeisUP Reference Manual: VSLICE Module .
SeisUP Reference Manual: VSUM Module .
.
SeisUP Reference Manual: WAVELET Module
SeisUP Reference Manual: WAVEMULT Module
SeisUP Reference Manual: WRITE Module
.
SeisUP Reference Manual: WTNRC Module .
SeisUP Reference Manual: XAVA Module .
.
SeisUP Reference Manual: XEQU Module .
.
SeisUP Reference Manual: XYGEOM Module .
SeisUP Reference Manual: XYMAP Module .
SeisUP Reference Manual: ZAVO Module .
.
ASCII data type .
.
.
.
.
.
.
.
BIN data type
.
.
.
.
.
.
.
.
CGM data type .
.
.
.
.
.
.
.
CMAP data type .
.
.
.
.
.
.
.
COMPRESS data type
.
.
.
.
.
.
DGN1 data type .
.
.
.
.
.
.
.
DNS1 data type .
.
.
.
.
.
.
.
ENSDCN data type .
.
.
.
.
.
.
FDMIG data type
.
.
.
.
.
.
.
xi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1324
.
1327
.
1331
.
1333
.
1336
.
1339
.
1342
.
1344
.
1348
.
1351
.
1359
.
1361
.
1363
.
1365
.
1368
.
1370
.
1371
.
1373
.
1374
.
1377
.
1381
.
1383
.
1384
.
1386
.
1389
.
1390
.
1395
.
1398
.
1401
.
1404
.
1408
.
1411
.
1416
.
1418
.
1420
.
1424
.
1439
.
1440
.
1441
.
1442
.
1443
.
1444
.
1445
.
1446
.
1447
.
FXYDSV data type .

.
FXYMIG data type .
.
FXYSAV data type .
.
GCI Data Type .
.
.
GVL data type .
.
.
KTMIG data type
.
.
LAS data type
.
.
.
OPTDCN data type .
.
PSM data type .
.
.
RAS1 data type .
.
.
RAS3D1 data type
.
.
REG data type .
.
.
RFMT data type .
.
.
RFS1 data type .
.
.
SCDCN1 data type .
.
SCDCN2 data type .
.
SCDECON1 data type
.
SCPHD1 data type .
.
SCPHD2 data type .
.
SEG-Y data type .
.
.
SGN1 data type .
.
.
SGNE1 data type .
.
.
SMIG data type .
.
.
Matrix 3DDIR .
.
.
Matrix 3DREFDEF .
.
Matrix 4THNMO
.
.
Matrix AFS1B .
.
.
Matrix AMPSTAT .
.
Matrix AMPWIN
.
.
Matrix APERTURE .
.
Matrix AUTC
.
.
.
Matrix AVGVEL .
.
.
Matrix AVOC
.
.
.
Matrix CMPDATUM .
.
Matrix COFFOFF
.
.
Dialog COLORSURFDEF
Matrix CONVFREQ .
.
Matrix CONVFREQ1
.
Matrix CONVTIM .
.
Matrix CONVTIME .
.
Matrix CVAETAS
.
.
Matrix CVAVELS
.
.
Matrix DBFOLD .
.
.
Matrix DBFOLDOFF .
.
Matrix DECON .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1448
.
1449
.
1450
.
1451
.
1458
.
1459
.
1460
.
1461
.
1462
.
1463
.
1464
.
1465
.
1466
.
1467
.
1468
.
1469
.
1470
.
1471
.
1472
.
1473
.
1478
.
1479
.
1480
.
1481
.
1484
.
1488
.
1490
.
1492
.
1494
.
1495
.
1497
.
1498
.
1500
.
1501
.
1502
.
1503
.
1506
.
1507
.
1509
.
1510
.
1511
.
1512
.
1513
.
1514
.
1516
.
Matrix DFORM .
.
Matrix DICE .
.
.
Matrix DIPMODEL .
Matrix DISTOFF .
.
Matrix DMUX .
.
Matrix DNGBINS
.
Matrix DSETLIST .
Matrix DUMPLIST .
Matrix ENSWIN .
.
Matrix ETANMO
.
Matrix EVEL
.
.
Matrix EXTRACT .
Matrix FILEFREQ .
Matrix FILES
.
.
Matrix FILTER .
.
Matrix FILTERB
.
Matrix FKFAN .
.
Matrix FKFANV .
.
Matrix FKPOLY .
.
Matrix FKPOLYV .
Matrix FLEX
.
.
Matrix FLEXOVP
.
Matrix FXYFREQ
.
Matrix GAIN
.
.
Matrix GCIHDREXT .
Matrix GDELAY .
.
Matrix GEOMCK
.
Matrix GVLAWIN .
Matrix GVLPREF
.
Matrix HMTH .
.
Matrix HORIZON
.
Matrix HORIZON3D .
Matrix INTVEL .
.
Matrix IREFVEL
.
Matrix ISOVBINS
.
Matrix ISOVHORS .
Matrix ISOVLINS
.
Matrix ISOVTIMS .
Matrix KFIL .
.
.
Matrix LASHEADER
Matrix LCKF
.
.
Matrix LINAME .
.
Matrix LINES
.
.
Matrix LMOVEL
.
Matrix MARINEGEOM
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xiii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1518
.
1521
.
1523
.
1525
.
1526
.
1528
.
1530
.
1531
.
1532
.
1533
.
1535
.
1537
.
1541
.
1542
.
1543
.
1545
.
1547
.
1549
.
1551
.
1553
.
1555
.
1556
.
1558
.
1560
.
1562
.
1563
.
1565
.
1567
.
1569
.
1572
.
1576
.
1577
.
1579
.
1581
.
1583
.
1585
.
1586
.
1588
.
1590
.
1592
.
1593
.
1595
.
1597
.
1598
.
1600
.
Matrix MATCH .
.
.
Matrix MATCH2 .
.
.
Matrix MIDPOINT .
.
Matrix MIX3DWGT .
.
Matrix MPISNODES .
.
Matrix MULPPER .
.
Matrix MUTE
.
.
.
Matrix MUTECONT .
.
Matrix MXLINE3D .
.
Matrix MXLINE3DXY .
Matrix NMOMUTE .
.
Matrix NOTCHFIL .
.
Matrix OFFBDIST .
.
Matrix OMIT
.
.
.
Matrix OPTDCN .
.
.
Matrix OPTDCNP1 .
.
Matrix PATREC .
.
.
Matrix PATTERN
.
.
Matrix PATTERNM .
.
Matrix PLOTENTRY
.
Matrix PLOTLIST .
.
Matrix PLOTLT .
.
.
Matrix PLOTLTCUS .
.
Matrix PLOTNOTETEXT
Matrix PLOTPRF
.
.
Matrix PLOTSINGLE
.
Matrix PLOTSPMX .
.
Matrix PLOTSYMBOLS .
Matrix PLOTTIC
.
.
Matrix PLOTTRIP .
.
Matrix PSMQC .
.
.
Matrix PSROTANG .
.
Matrix PSROTANG1 .
.
Matrix QCOMPF
.
.
Matrix QCOMPS
.
.
Matrix QCOMPV
.
.
Matrix QCVELWIN .
.
Matrix QMATRIX .
.
Matrix QVALUES
.
.
Matrix RADON .
.
.
Matrix RADON1 .
.
.
Matrix RAS2GEO
.
.
Matrix RAS2SRC
.
.
Matrix RECMASK .
.
Matrix RECVGEOM .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xiv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1603
.
1604
.
1606
.
1607
.
1610
.
1611
.
1613
.
1615
.
1617
.
1619
.
1621
.
1623
.
1625
.
1626
.
1629
.
1632
.
1634
.
1636
.
1638
.
1640
.
1641
.
1642
.
1644
.
1646
.
1647
.
1649
.
1650
.
1651
.
1653
.
1654
.
1655
.
1656
.
1657
.
1659
.
1661
.
1663
.
1665
.
1666
.
1668
.
1670
.
1672
.
1674
.
1675
.
1676
.
1677
.
Matrix REELS .
.
Matrix REGIONS
.
Matrix REGIONST .
Matrix RFMT
.
.
Matrix RFMTSEGD .
Matrix RMOD .
.
Matrix RMSFCSN
.
Matrix RMSSSPN
.
Matrix RMSV3C .
.
Matrix RMSVEL .
.
Matrix SCDCN1 .
.
Matrix SCDECON1 .
Matrix SCLDB .
.
Matrix SCLSCL .
.
Matrix SCLWIN .
.
Matrix SDELAY .
.
Matrix SEGYEBC
.
Matrix SEGYLINES .
Matrix SEGYREMAP
Matrix SGN1 .
.
.
Matrix SGN2 .
.
.
Matrix SGNE
.
.
Matrix SMOOTHHORZ
Matrix SNR .
.
.
Matrix SOURCE .
.
Matrix SOURCE2
.
Matrix SOURCEM .
Matrix SRCDXOFF .
Matrix SRCDXOFF2 .
Matrix SRCMXLST .
Matrix SRCRECREC
Matrix SRCRECREC2
Matrix SRCRECSPD .
Matrix SRCRECSPD2
Matrix SRCRECXY .
Matrix SRCRECXY2 .
Matrix SRCXYREC .
Matrix SRCXYREC2 .
Matrix SRCXYSPD .
Matrix SRCXYSPD2 .
Matrix SRGMUTE .
Matrix SSDEC .
.
Matrix STAELEV
.
Matrix STATGEO
.
Matrix STATION
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1681
.
1682
.
1684
.
1686
.
1688
.
1690
.
1691
.
1693
.
1695
.
1697
.
1699
.
1701
.
1703
.
1704
.
1705
.
1707
.
1709
.
1710
.
1711
.
1713
.
1715
.
1717
.
1719
.
1721
.
1722
.
1724
.
1727
.
1730
.
1734
.
1739
.
1740
.
1743
.
1747
.
1750
.
1754
.
1757
.
1761
.
1764
.
1768
.
1771
.
1775
.
1777
.
1778
.
1780
.
1782
.
Matrix STATSEQ
.
Matrix STATSRC
.
Matrix SURFACE
.
Matrix SURFDEF
.
Matrix SURFSMOOTH
Matrix SVSHTSHIFT
Matrix SYNDIFF .
.
Matrix SYNDIPOA .
Matrix SYNDIPS .
.
Matrix TARGET .
.
Matrix TAUF
.
.
Matrix TRCPLOT_CMT
Matrix TRCPLOT_GAP
Matrix TSVP .
.
.
Matrix TVDIP .
.
Matrix TVSMOOTH .
Matrix TVTVZD .
.
Matrix TVTVZDC .
Matrix TVTVZDD .
Matrix TVZD
.
.
Matrix USRFCSN
.
Matrix USRMBIN
.
Matrix USRSBIN .
.
Matrix USRSGEN
.
Matrix V0
.
.
.
Matrix VA3CDIP
.
Matrix VABINS2D .
Matrix VABINS3D .
Matrix VPVSDEN
.
Matrix VS2VP2 .
.
Matrix VSUM
.
.
Matrix VVSPER .
.
Matrix WEIGHTS
.
Matrix WINDOWS2 .
Matrix X_T .
.
.
Matrix XTTAPER
.
Matrix XYDIP .
.
Release Notes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xvi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1784
.
1786
.
1788
.
1790
.
1792
.
1794
.
1795
.
1797
.
1799
.
1802
.
1804
.
1806
.
1807
.
1808
.
1810
.
1812
.
1814
.
1816
.
1818
.
1820
.
1822
.
1823
.
1824
.
1825
.
1826
.
1827
.
1828
.
1830
.
1832
.
1834
.
1835
.
1838
.
1840
.
1841
.
1844
.
1845
.
1847
.
1849
.
Documentation >
SeisUP
2013 Help Documentation
Applications and Administration

Reference
Modules
Data Types
Matrices
SDK Programming Manual (PDF format)
SDK Reference Manual (PDF format)
Release Notes
Copyright 2013 GeoCenter LP
Documentation > SeisUP Applications Manual >
SeisUP
Applications Manual
Administration
Lots of useful information for optimal SeisUP usage. Includes descriptions for SeisUP admin scripts, a
number of "General Usage" tips, troubleshooting and third party development.
DataManager
The DataManager application provides a through and organized view of the data known to SeisUP. Along
with viewing the data sets for any SeisUP project, other features include setting up the output filesystems
list, tape definitions file and the ability to archive/restore projects.
Flow Editor (Geodraw)
An introduction to SeisUP: starting a SeisUP session, building processing flows and running jobs.
Matrix Editor (Geosp)
An introduction to the multidimensional spreadsheet program used within SeisUP to manipulate
dimensional vector information such as geometry and velocities.
HistoryViewer
Complete documentation on viewing the processing history of a SeisUP data set using the HistoryViewer
program.
JobMonitor
Complete documentation on viewing the status all running SeisUP jobs using the JobMonitor program.
Also describes how the user may interact with running jobs.
JobServer (seisupd)
An introduction and administrative information regarding SeisUPs job server which is responsible for
spawning processes that represent the work-flows submitted by users via the FlowEditor.
License Server / Licensing Scheme
A discussion of the license scheme and administration of the license management subsystem.
Plotting
This document describes how to setup SeisUPs interface with 3rd Party plotting software to produce hard
copies.
SeisUP has undergone some significant changes in function. Many will not be visible to the normal user
but administrators and programmers need to be aware of what has changed. This release incorporates the
new administrative functions as well as new modules. This document discusses both old and new versions.
Overview
The SeisUP administrative tools are grouped by function. Most tools can be used by anyone, some require
root access.
General information
Administrative configuration files.
Dataset naming conventions.
The directory structure was changed for the 2005 release.
Files stored in user home directories.
Installation and License issues

SeisUP is changing its licensing code from an internal system to Flexlm in order to provide additional
flexibility.
Installation of SeisUP is relatively easy. Documentation is on the SeisUP CD. The main issues are
where to put the executables and where to put the seismic data. As a general rule, do not put seismic
data on the same device as the OS. Also try to keep the SeisUP usr directory off of the device with
the OS as well.
The new license_install script is very similar to the old version. Several options have been removed
because the SDI functions have also moved to Flexlm.
This link is a discussion of the new Flexlm licensing.
Flexlm licensing installation
General purpose
The backuparea script allows the user to save a copy of the flows and optionally the data for an area
to disk or tape. The option to save to a file is new. NOTE The tape drive is assumed to be locally
attached.
Search for "orphaned" datasets with the new chkdset script.
This is a replacement for the old fixdsets function. chklinks
The listing files names and locations will change. The cleanup_run_logs script moves and renames
the listing files to the new location.
Get a list of the actual locations of datasets with the dset_files script. This has been partly absorbed
by the dskinv function.
A catch all program for disk space reports - dskinv.
This new script, dump_job_cache, provides a fast way to see what jobs are running in a line without
having to have a graphic connection to the machine.
Use fixdsets to update dataset locations when data has been moved to another location.
This new script allows the user to watch job activity as jobs enter and leave the job queue.
jm_multicast_monitor
This new script scans an area for live datasets and optionally tars them to a file. project_data
The restorearea script allows the user to bring an area and its data back from storage.
This is a utility to send commands to the new SeisUP daemon. seisupd_admin
This is a script to stop, start or restart the new daemon. seisupd_ctl
This is a script to install the new daemon. seisupd_install
This provides a way to follow the SeisUP job log without having to have a graphical interface.
seisupd_log_mon
This new script presents a list of available plot streams and allows the user to changes settings.
select_plotting_subsystem
This new script updates the help browser default. set_help_viewer
This function sets the reel number on a tape. - tapeinit - Tapes normally do not come with serial
numbers set. The tape library can be used to verify tapes are accessed in the correct order.
This function allows a tape drive on a remote machine to be accessed by a SeisUP job. The tape
configuration file must contain the full path to this executable on the remote machine. If it is not running,
the job will attempt to start it. tapeserv
Cluster tools
These are new functions to maintain a cluster.
To send the same command to several cluster nodes use cluster command.
Use cluster dist to copy files to a list of nodes. A new provision allows each cluster node to have local
copies of executables to reduce bandwidth demands at job startup.
A function to generate entries for the /etc/hosts file. cluster host_entries
A function to generate node lists. cluster node_entries
A function to turn off cluster nodes. cluster_poweroff
A function to reboot cluster nodes. cluster_reboot
A wrapper for cluster_dist. dist_cluster_program
Kill a users jobs on a node with rkill.pl.
A GUI wrapper for rkill.pl rutil.
Plotting
A discussion of the new plotting control functions.
Troubleshooting and other odd tools

If something breaks.
Use the compact command to free space form DB files. This has largely been replaced with the dbu
command.
Use the config_seisup_script to change the $QEDTOP referenced in the seisup script.
Previous releases used a different structure for the flow files. The convflow6_7 function will update
the flow.
The db_dump function can dump the contents of a DB file.
The work horse of DB utilities is the dbu command. It combines several functions and is more
tolerant of corrupted DB files.
Use dump_flow to get a list of all nodes and node IDs in a flow file.
The dump_id command reports the most recently run node and job ID.
The goodbad command does a quick check of a DB file. It reports if it can read all entries. If it can,
the DB file is good.
SeisUP can sometimes lockup. The steps to take if this happens are here.
The rebuild command has mostly been replaced by the dbu command.
The dreaded segfault.
If all else fails a good bug report can speed up fixes considerably.
Development tools
These are for writing your own modules.
The build system has been updated between releases, the programming manual has not yet been updated.
The changes are fairly minor.
There are two programming manuals. One describes the needed files and the other describes available
functions.
The new cat_update script updates the SeisUP.cat file in $QEDTOP/lib/db/cat. Previously a third
party application had its own .cat file in the same directory.
Use the catout to get a list of modules on the system.
The new exec_debug script is evoked when a job is run in debug mode. To run jobs in debug mode
you must first start seisup with the debug flag:
seisup nw
In order to get a list of SURFACE horizons for a parameter list, use the ls_horizons function in the
modules .pdb file.
In order to get a list of nodes for a parameter list use the lst_nodes function in the moduless .pdb file.
The new modgen script will build a skeleton C module.
In order to get a list of plot logos for a parameter list use the plot_logos function in the modules .pdb
file.
In order to get a list of pvm hosts for a parameter list use the pvm_hosts function in the modules .pdb
file
In order to get a list of color maps for a parameter list use the sup_cmaps function in the modules
.pdb file
SeisUP Configuration Files

SeisUP Installation Directory
bin/
glp
etc/
seisup.csh
filesystems
tape_devices
io.conf
seisupd.conf
exec.conf
matrix.conf
horizon.conf
lib/
qedhosts
pvmhosts
qedtapes
nodes/*
logo/default.wdf
Also see:
Plotting
glp
This script is executed whenever the user selects print in the help viewer or when displaying the
execution status. The provided script simply uses the "lp" command on the resident system. You may
need to modify the script to accommodate your printing subsystem.
seisup.csh
This file can be read in your .cshrc file to properly initialize your environment for SeisUP. For
example, if SeisUProotDirectory above is /seisup and you are on a Sun, add the following to the end
of you .cshrc file: source /seisup/etc/seisup.csh
filesystems
This file will list directories or file systems available for creating disk data sets via the disk manager.
Previous versions of SeisUP may have suggested placing "local" or "remote" after the path of the
filesystem. That format is no longer supported. Each line in this file must be either a comment (the
line starts with the # character) or a path to a filesystem. The disk manager will attempt to distribute
disk files among different file systems using a disk selection method defined in the io.conf file
(description below). All data sets will be written to the filesystems listed in this file, except when the
user explicitly sets up an alternative filesystems list for a SeisUP project using the "Filesystems"
option from the "Options" menu in the Flow Editor program.
If all of the file systems fill up, the disk manager will attempt to communicate with the user to request
if the job should abort, or continue after the user releases some disk space.
This file may be modified manually or by using the Data Filesystems Manager option accessed from
the Data Manager applications File menu.
tape_devices
This file defines the list of available tape drives. The job server does not automatically add the list of
local tape devices to this file, instead the user may repopulate the list using the "Discover Tapes"
button from the Tape Devices Manager Dialog within the Data Manager application. The reason this
functionality has been removed from the job server was so that the new job server may remain
independent of other parts of SeisUP. This file may be edited manually or via the Tape Devices
Manager option accessible from the Data Managers File menu.
io.conf
This configuration file has been added to improve disk usage. By modifying the io.conf file the user
can set a free space requirement on disk selection so that disks with very little free space will not be
written to. The user may also set the disk selection algorithm to random, based on available space, or
number of processes using the disk. Please read the comments in the io.conf file for a more detailed
explanation of possible I/O configurations.
seisupd.conf
This new configuration file defines parameters for the job server, seisupd. After any modifications
the job server will need to be restarted. The default network parameters may be changed should they
conflict with your network.
exec.conf
This file will contain parameters to be used when running jobs in SeisUP. For instance:
MAX_ENSEMBLE
The maximum number of traces per ensemble to hold in memory if not

stacked data.
MAX_ENSEMBLE_STACKThe maximum number of traces per ensemble to hold memory for stacked
data
matrix.conf
This file will define names of matrix types are to be saved to the processing history file in the internal
SeisUP formatted data sets.
horizon.conf
This file will define colors to be used for interpreted horizons.
qedhosts
This file will define the hosts available for executing jobs. Each host listed here should have the job
server running. In previous versions this file held the license keys. That is no longer the case, license
files are now stored in the SeisUProotDirectory/etc/ directory.
pvmhosts
This file will define the hosts available for parallel execution when spawning off child processes.
qedtapes
This file will define the range of tape numbers for tape media types available at this site.
nodes/*
This directory will define the hosts available for non-PVM parallel execution when spawning off
child processes or multi-threaded applications. An example module that uses this is KTMIG. A file
named default must always exist. The default file contains the default host list. The Systems
Administrator can create various combinations of host lists in this directory. A user can select a host
list file from the module parameter menu over which to run his application on. An example usage on
an SMP machine named godzilla with 16 CPUs and a Linux cluster of 128 nodes with dual CPUs
could contain one entry in the default file as follows:
godzilla cpu=16
A second file could be named cluster would contain one entry for each of the 128 cluster nodes,
named node1, node2, ..., as follows:
node1 sys=linux cpu=2
node2 sys=linux cpu=2
...
...
The user would then be able to select to run the parallel job either on the SMP machine or the cluster
via the parameter menu for the module.
logo/default.wdf
This file is an X-window dump file of the logo to be displayed by the PLOT module for the default
logo. Other logos are located in the same directory. The file extension .wdf is an alias for .xwd which
a number of image manipulation programs can output. GIMP and Image Magic are both free and can
produce this format. Client logos should have the total number of colors reduced to < 10 colors.
Copyright 2013, GeoCenter LP. All rights reserved. SeisUP is a registered trademark of GeoCenter LP.
10
Dataset Naming Convention

Data Directories
SeisUPs naming convention for disk datasets in the data directories is:
Area.Line.Dataset.type.[number]
Dataset is limited to 8 characters for display reasons.

Type can be something like GCId, GCIm, GCIz, SEGY, CGM, ... Number is usually a 1 if present. If a
dataset has been split, Number will be 2, 3, ... This only happens if a data directory has run out of space
and the data is sent to another disk.
SeisUPs internal data format is named GCI. A GCI dataset has at least three parts. The GCId dataset is
the actual data. The GCIm dataset is a map file used to speed up access to the data. The GCIz dataset,
which is not strictly required, is a mostly ASCII history file that contains the processing flow and
parameters. Any of the three can be split among data directories.
NOTE Putting punctuation in an area, line or dataset name is generally a bad idea. Periods (.) and spaces
can cause many problems. Underscores (_) are permitted.
SeisUP Usr Directories

There are a number of files under the SeisUP usr directory which contains the area / line files. The biggest
by far are the files named DB. They contain geometry and other information. The flow file contains the
modules and connections. Datasets are controlled by the .cleanup files. Job listings are either .lst or .runlog
files.
11
DIRECTORY TREE
All directories listed here are rooted at $QEDTOP - the highest level SeisUP directory. $QSYS is the
system type, i.e. linux, sun, sgi, hp or nt. It is possible to have multiple installations for different
architectures sharing a $QEDTOP. It is not possible to have different versions of SeisUP installed in the
same $QEDTOP but it is possible to have them on the same machine.
The current directory structure is as follows.
Documentation
Documentation/Applications
Documentation/Applications/Administratium
Tool help files.
Documentation/Applications/DataManager
Datamanager help.
Documentation/Applications/Geoall
Color table help.
Documentation/Applications/Geodraw
Flow editor help.
Documentation/Applications/Geosp
Matrix help.
Documentation/Applications/HistoryViewer
Historyviewer help.
Documentation/Applications/JobMonitor
Jobmonitor help.
Documentation/Applications/JobServer
Jobserver help.
Documentation/Applications/LicenseServer
License help.
Documentation/Applications/Plotting
Plotting help.
Documentation/Reference
Documentation/Reference/DataTypes
Data type help.
Documentation/Reference/Matricies
Matrix help.
Documentation/Reference/Modules
Module help.
Documentation/Reference/ReleaseNotes
Release notes.
bin
bin/${QSYS}
Various mostly command line tools.
bin/${QSYS}/admin
Administrative tools.
bin/${QSYS}/devel
Development tools.
bin/${QSYS}/list_gen
List generating tools.
bin/${QSYS}/plotting
Plotting scripts.
bin/${QSYS}/sdi
SDI executables. These may not be present.
etc
Configuration files.
include
Include files for programming.
install
Installation scripts.
lib
lib/app-defaults
X window display files.
lib/cmaps
Color maps.
lib/db/cat
Catalog files.
lib/db/ldb
Parameter list files.
lib/db/mdb
Module definition files.
lib/db/pdb
Module parameter files.
lib/db/xdb
Matrix definition files.
lib/${QSYS}
Library files and third party executables.
lib/log
Log files for the license server.
lib/logo
Plot logos.
lib/nodes
Node definition files.
lib/txt
Display icons.
sdi
Tape database.
sys
sys/GeoSeis
sys/GeoSeis/bin/${QSYS} SeisUP executables.
sys/GeoSeis/segy
Global DB file.
tmp
12
usr
usr/area
usr/area/line
usr/area/line/run_logs
Area DB file.
Line DB, flow and cleanup files.
listing files.
Some files are not located under $QEDTOP. These are:

/var/run/seisupd.pid
/var/log/seisupd.log
The process ID of the SeisUP daemon.

The message log for the SeisUP daemon.
The directory structure for SeisUP 2004 and prior was as follows.
bin
bin/${QSYS}
bin/${QSYS}/sdi
devp
include
install
java
jm/[machine_name]
lib
lib/app-defaults
lib/cmaps
lib/db/cat
lib/db/ldb
lib/db/mdb
lib/db/pdb
lib/db/xdb
lib/hlp
lib/${QSYS}
lib/logo
lib/nodes
lib/txt
sdi
sys
sys/GeoSeis
sys/GeoSeis/bin/${QSYS}
sys/GeoSeis/hlp
sys/GeoSeis/hlp/dt
sys/GeoSeis/hlp/mod
sys/GeoSeis/hlp/mx
sys/GeoSeis/hlp/release
sys/GeoSeis/lib
sys/GeoSeis/segy
tmp
usr
usr/area
usr/area/line
Various mostly command line tools.

SDI executables.
Programming manuals and examples.
Include files for programming.
Installation scripts.
Java libraries for instrument tests.
Jobserver, start and stop scripts, log files.
X window display files.
Color maps.
Catalog files.
Parameter list files.
Module definition files.
Module parameter files.
Matrix definition files.
System help files.
Library files and third party executables.
Plot logos.
Node definition files.
Display icons.
Tape database.
SeisUP executables.
Data type help files.
Module help files.
Matrix help files.
Release notes.
Libraries.
Global DB file.
Area DB file.
Line DB, flow, cleanup and listing files.
The seisup.csh file, located in bin/${QSYS}, when "sourced" from a csh shell, will set several
environmental variables and update the PATH variable.
13
SeisUP Files Stored in User Home Directories

Files
.compression
.flexlmrc
.qedgeometry
.qt/
.seisup/
selected_plotter
last_project
projects/
gradients/
.SeisUPdisplay
.seisupenv
.compression
Users default values for GCI data compression is stored in this file.
.flexlmrc
Technically this is not solely a SeisUP file, it may be used by any software which uses FlexLM for
license management. Its purpose is to store license file locations.
.qedgeometry
Stores the size, screen position and default icon size used in the last SeisUP session.
.qt/
This directory contains preferences files for QT applications. Several SeisUP utility applications,
such as the JobMonitor and DataManager, fall in this category. If youve used the JobMonitor, for
instance, then you should have a file ~/.qt/jobmonitorrc.
.seisup/
selected_plotter
Stores which plotter, from the plotters list, is the users default.
14
last_project
Stores the last saved SeisUP project. New SeisUP sessions will open in this project.
projects/
Under this directory a session_history file is stored for every SeisUP project the user has
actively worked in. Each session_history file simply stores the location in the flow where the
user last saved the project. Thus, the next time a user goes back into a saved flow the area should
be familiar.
gradients/
User defined colormaps created in module IVEP are stored in this directory.
.SeisUPdisplay
Stores the customized list of headers used in the Header Dump option accessible from DISPLAYs
Tools menu.
.seisupenv
No use for this file found. Perhaps it is still around for legacy code.
15
LICENSE_INSTALL
This script must be run as root. It allows the SeisUP and SDI CGMLIB licenses to be updated / installed.
./license_install
Respond with
seisup -lib
-quit
--
one of the following:

Install SeisUP license
Install CGM creation license
Quitlicense_install
Only the first letter of each option is required. You will be asked if you have a license ready. If you
respond "NO", information will be output that is needed to generate the license. If you respond "YES",
you will be asked for the license.
Linux systems do not require a separate CGMLIB license.
16
SEISUP_LMGRD_INSTALL
Installs the SeisUP license manager daemon onto a host system. To uninstall seisup_lmgrd from a system
pass the --uninstall option to the installer. This is called during installation. The only use of this script
otherwise is to remove SeisUP.
seisup_lmgrd_install [--uninstall] [seisup-directory]
--uninstall
- removes seisup_lmgrd
seisup-directory - defaults to $QEDTOP
17
CHKDSET
This function checks the data directories for datasets that do not have a corresponding .cleanup file in the
$QEDTOP/usr directory. If an "orphan" dataset is found, you will be asked if you want to delete it.
NOTE If your system has multiple QEDTOPs with independent usr directories, chkdset can report
datasets without .cleanup files that actually have files in another QEDTOP if you do not check for all
QEDTOPs at once.
chkdset [altQEDTOP1] [altQEDTOP2] [...]
altQEDTOPn
Additional QEDTOP to check.
18
CHKLINKS
Usage: chklinks [ -ufld ] [ QEDTOP= ] [ AREA= ] [ LINE= ] filesystem
The chklinks script takes the path to a filesystem that contains SeisUP dataset files. For each SeisUP
dataset file in the target filesystem, chklinks will go to the area/line directory and check that the .cleanup
for the dataset file references the correct path to the file.
For example, if you had a GCI dataset named Geom, whose GCId file was located at the path
/mnt/seisup_data/Area.Line.Geom.GCId.1 chklinks will report if the file
${QEDTOP}/usr/Area/Line/Geom.GCId.cleanup references the dataset file at a different path (say,
/export/seisup_data/Area.Line.Geom.GCId.1).
One scenario that may result in out-of-date .cleanup files is when dataset files are moved from one
filesystem to another, or if you rename a filesystem. In these situation, run chklinks first to generate a
report of what .cleanup files require updating, and then use the -u flag to cause chklinks to update the
.cleanup files so that they contain the correct path to their dataset file.
chklinks operates using the value of the QEDTOP environment variable. If QEDTOP is not set, then
chklinks will exit with an error. You may specify an alternate QEDTOP without changing your
environment variable using the command line argument QEDTOP=. For example, chklinks
QEDTOP=/seisup_alt /mnt/data will check the files in /mnt/data against the .cleanup files for the areas and
lines contained in QEDTOP /seisup_alt.
You may restrict the scope of chklinks to a specific area or line by specifying the command line argument
AREA= and LINE=, respectively. Alternatively, you may set the environment variables QEDAREA or
QEDLINE to the area and line you wish to restrict chklinks search to.
-u
-f
-l
-d
QEDTOP=
AREA=
LINE=
Update links in cleanup files

Force update without requiring interactive confirmation
List files for which cleanup files could not be found,
if any
Print formatted output suitable for parsing
Alternate QEDTOP to search for .cleanup files
Area name to restrict scope of chklinks
Line name to restrict scope of chklinks
NOTE: Punctuation in area, line or dataset names can throw this and several other utilities off. Do NOT
use periods (.) or spaces in any name.
19
CLEANUP_RUN_LOGS
Copies .lst files for a project into the same run_logs directory that SeisUP writes run logs to. This program
must be run from the project (line) directory itself.
The older versions of SeisUP put the job listings in files named number.lst in the line directory. The
current version puts the listings in the run_logs directory under the line directory as files named
job_number.runlog. In both cases number is negative for batch jobs. Having a file name with a leading "-"
causes some problems searching the listings.
NOTE Use of this script will prevent older versions of SeisUP finding the job listings (execution status).
The current version first checks the run_logs directory for the job listing and if it does not find one, looks
for a .lst file.
There is no inverse version of this script.
20
DSET_FILES
Produce a list of actual datasets from .cleanup files.
dset_files <.cleanup file>
dset_files <area> <line> <dataset>
dset_files <area> <line> <dataset> <type>
area line dataset
type
area name
line name
- dataset
- type of dataset, i.e. GCId, GCIm, GCIz
The first version must be run from the directory with the .cleanup file. The last two require the QEDTOP
and QSYS environment variables be set and can be run from any directory.
21
DSKINV
A somewhat catch all program for disk space reports.
dskinv
Available commands:
1. end
2. help
3. query
<file>
4. scratch
maxspace
5. space
6. files
Quit
Produce this display
Query datasets
Produce a summary space utilization output by area.
If <file> is specified, individual dataset information
is saved to the file, otherwise it is output with
the summary information.
Scratch datasets
Delete datasets by area, line and dataset.
Hidden and not very useful parameter
List data directories.
Show disk space
Report free space in the data directories SeisUP
can write to.
Show actual files for dataset
Input a command
The options can be specified on the command line as well as from the prompt. Options can be specified by
number or name.
dskinv 5
dskinv space
dskinv 6 <area> <line> <dataset>
The most used options are space, files and query.
22
DUMP_JOB_CACHE
This program opens the seisupd job cache located at the path specified in the first argument and prints
descriptions of each job contained in the cache.
dump_job_cache [-c] cache_file
-c
- prints summary only
cache_file - normally named job_cache
dump_job_cache -c job_cache
5 jobs in job_cache
dump_job_cache job_cache
JMJobRef (100074b0) = {
Owner: qamar:user (uid = 513, gid = 20)
Display: atlas.geocenter.lan:0
Exec. Host: godzilla
Exec. Name: jobexec
Process ID: 510589
State: JMStateExitSuccess
SeisUP Dir: /mnt/gz4/seisup-pro
Area: Sanchez-Dummy
Line: mergemap
Flow File: /mnt/gz4/seisup-pro/usr/Sanchez-Dummy/mergemap/flow
Run Log: /mnt/gz4/seisup-pro/usr/Sanchez-Dummy/mergemap/run_logs/job_1412.r
unlog
Node ID: 2014
Job ID: 1412
Submit Time: Fri Oct 7 09:05:41 2005
Start Time: Fri Oct 7 09:05:41 2005
End Time: Fri Oct 7 09:06:21 2005
}
.
.
.
23
JM_MULTICAST_MONITOR
This function allows the user to watch SeisUP job submissions. The level of detail is greater than the
seisupd_log_mon provides.
24
PROJECT_DATA
Given an area name, this script will scan the area directory located in the SeisUP installation for all
cleanup files, parse the cleanup files, and return paths to the datasets for the project.
project_data [-a archive_file] area_name [line_name]
-a archive_file All datasets found will be tarred into archive_file.
25
SEISUPD_ADMIN
Send commands to the SeisUP daemon seisupd.
seisupd_admin
seisupd Administration Commands:
restart
Restart Network Services
stop
Stop Network Services
start
Start Network Services
flush
Flush Job Queues
reset
Reset Job Queues
killall
Kill All Jobs
shutdown
Shutdown
ssd
Scheduled Shutdown
quit
Quit seisupd_admin
26
SEISUPD_CTL
This is a wrapper script around /[etc|sbin]/init.d/seisupd start/stop/restart. It must be run as root.
27
SEISUPD_INSTALL
Installs the seisupd job server onto a host system.
To uninstall seisupd from a system pass the --uninstall option to the installer.
28
SEISUPD_LOG_MON
Run a tail -f on the SeisUP job log. A ^C stops the tail.
29
SELECT_PLOTTING_SUBSYSTEM
Presents the user with a list of available plotting subsystems. The user makes a selection from this list and
the script will update the necessary links to enable the old_subsys subsystem.
30
SET_HELP_VIEWER
Searches the users path for a web browser and adds it to the SeisUP script.
31
TAPEINIT
Set the reel number for a tape.
tapeinit reeln unit
reeln The reel number to set into the tape.
unit The unit number where the tape is loaded.
32
TAPESERV
This program is the SeisUP remote tape server. It is a standalone program that runs on remote machines to
serve as a remote tape server. See the tape_devices file in $QEDTOP/etc. Field 6 in this file is the path to
the tapeserv executable on the remote machine. If tapeserv is not running on the remote machine SeisUP
will attempt to start it using this path. There are no arguments.
33
CLUSTER_COMMAND
This script allows the same command to be sent to one or more nodes. It assumes the cluster nodes are
named sequentially like:
darwin001
darwin002
.
.
.
darwin100
Arguments:
1: cluster node base name
2: starting node number
3: ending node number
4: command to execute
Example:
cluster_command darwin 1 30 "/sbin/shutdown -h now"
As shown in the example, multiple argument commands should be enclosed in quotes.

See the node_names script.
34
NODE_NAMES
This minimally useful script takes as its arguments a base node name, a starting node number, and an
ending node number. From this it will print out formatted node host names.
node_names darwin 1 5
darwin001
darwin002
darwin003
darwin004
darwin005
35
CLUSTER_DIST
This script will copy a file to a list of cluster nodes using the rsh command. If the cluster is NOT using the
cluster.conf file in $QEDTOP/etc to keep local copies of the executables on the node, there is no purpose
using this script.
For example:
cluster_dist darwin 1 10 /etc/hosts /etc
copies the file /etc/hosts into the directory /etc on
cluster nodes darwin001 through darwin010.
Arguments:
1: Base hostname
2: Starting node number
3: Ending node number
4: Local file
5: Remote destination
An example of a cluster.conf file is:

InstallPath /opt/seisup
RemoteUser cluster
This cluster has local copies of the executables and a "cluster user" so every user does not have to have an
ID on each node.
36
CLUSTER_HOST_ENTRIES
This script will create entries for the /etc/hosts file for cluster nodes designated in the command
arguments. The entries are printed to standard output which can be used by the user as he wishes. This
script takes the following arguments:
1:
2:
3:
4:
starting IP address
cluster node base hostname
starting node number
ending node number
For example, consider the following invocation and its output:

% cluster_host_entries 10.0.0.50 darwin 1 5
10.0.0.51
darwin001
10.0.0.52
darwin002
10.0.0.53
darwin003
10.0.0.54
darwin004
10.0.0.55
darwin005
37
CLUSTER_NODE_ENTRIES
This script will generate and output to stdout host entries for SeisUP cluster node lists. See the
$QEDTOP/lib/nodes directory. The output format is as follows:
basenameXXX sys=QSYS ncpu=N
Arguments:
1: Base hostname
4: SeisUP platform identifier (i.e. linux, darwin-ppc)
The default is the environmental variable $QSYS.
5: Number of CPUs (2 default)
38
CLUSTER_POWEROFF
Sends a shutdown command to the specified nodes.
Arguments:
1: Base hostname
39
CLUSTER_REBOOT
This script is used to send a reboot command to each of the specified nodes.
Arguments:
1: Base hostname
40
DIST_CLUSTER_PROGRAM
This script uses the cluster_dist script and the $QEDTOP/etc/cluster.conf file to send executables to local
copies on cluster nodes.
Usage: dist_cluster_program program_name cluster_name start_node_num end_node_num
41
RKILL.PL
Kill a users jobs on a cluster node.
rkill.pl <user> <machine> [program]
program
If specified, kill this program. Otherwise kill everything

owned by user.
42
RUTIL
Cluster maintenance utility.
This utility allows the user to kill jobs on multiple nodes or remove temporary files on the nodes. The
utility presents selectable node lists.
Currently no released modules leave temporary files on the cluster nodes. This will change soon.
43
COMPACT
The COMPACT utility compresses a DB file. This function has largely been replaced by the dbu
commands copy option which is a bit more tolerant of corrupted DB files.
compact srcfile dstfile errfile
srcfile - full path to the DB file to be compressed
dstfile - output DB file
errfile - file for error handling - not human readable
If the utility completes successfully, move dstfile over srcfile. Delete errfile in any event.
44
CONFIG_SEISUP_SCRIPT
You will probably never need this script. It edits the seisup script to point to another location.
45
CONVFLOW6_7
Convert an old version flow file to a new version file. Any flow file created since 1996 should not need
this function.
convflow6_7 <flowfile> <version>
46
DB_DUMP
Dump the contents of a DB file in hex and ASCII.
db_dump <filename> [ MANUAL | SEQ ]
MANUAL allows the user to step through the output. SEQ, which dumps everything, is the default
db_dump DB MANUAL
Dump Utility for C-Index/II version 4.0D
(c) Copyright Trio Systems 1983-1989
Enter node to dump or H=header, F=fwrd node, R=rev node, P=print, X=exit
L=lock file, U=unlock file (Status: Unlocked) H
Header Dump
----------Wordorder =
1x
Root =
1225
Levels =
4
Next Node =
13945
Next Rec =
1
End of File =
13949
Free Nodes =
-1
Delete Count = 0
Record Count = 0
Custom Info Len = 0
Index Type Codes
1: 0
2: 0
3: 0
4: 0
5: 0
6: 0
7: 0
8: 0
9: 0 10: 0
11: 0 12: 0 13: 0 14: 0 15: 0 16: 0 17: 0 18: 0 19: 0 20: 2
Enter node to dump or H=header, F=fwrd node, R=rev node, P=print, X=exit
L=lock file, U=unlock file (Status: Unlocked)
47
DBU
DBU is a database utility program. This should be run in the directory where the database file is located.
dbu
Available
create
open
close
list
dump
load
delete
copy
commands:
<database>
<database>
<index> [fname]
<index> <keyname> [fname]
<index> <keyname> <fname>
<index> <keyname> [rec]
<new_database>
help
end
Create a database
Open a database
Close current database
List keys for given index
Dump contents of key
load fname contents into key
Delete key
Copy the current database
to new_database. NOTE The
default database is the
global database.
Produce this display
Quit dbu
<index>: P - PDB; M - MDB; X - MatrixDB; L - ListDB

C - CATEGORY; D - Development Category.
OR
<index>: # - # is a number from 0 - 15.
Input a command
The DB file must be opened or created before anything is done to it. The most common use of dbu is to
copy / compress a possibly corrupted DB file to a new file. The new file is then moved over the old DB
file.
48
DUMP_FLOW
Lists all Node Names and Node IDs in a flow file. This must be run in the line directory.
dump_flow flow
49
DUMP_ID
Lists the most recently run Node ID, Job ID and Batch Job ID for a flow file.
dump_id flow
Node ID:
7
Job ID:
1475
Batch Job ID: 401
50
GOODBAD
Database file structure check tool.
goodbad <filename>
goodbad DB
Goodbad C-Index/II File Integrity Checker
(c) Copyright Trio Systems, 1986-1989
version 4.0D
Testing: DB
File tests as good.
This will fail with a message "Error opening file" if the file is in use. Errors in the DB entries are printed
out.
51
LOCKUP
For reasons that are seldom clear, the SeisUP flow editor sometimes locks up. The usual suspects list
includes corrupted DB, .ID, .JMlog, .history and JMtable files. If you get a reasonable clue as to how these
get corrupted other than a system crash, please pass it on to GeoCenter so we can address it.
The .ID, .JMlog and .history files all reside in the line directory; $QEDTOP/usr/<area>/<line>. If no one
has the flow open, these files can be deleted safely.
Suspect DB files can be checked with the goodbad command. Corrupted DB files are treated by using the
dbu command to copy the contents to another file. The new file should be moved over the existing DB
file. DB files reside in both the area and line directories. The one in the line directory is generally much
larger and the most likely one to be corrupted.
The JMtable file resides in $QEDTOP/jm/<machine_name>. The job server must be stopped to delete this
file.
52
REBUILD
Database rebuild utility. This has largely been replaced by the dbu copy command which is a bit more
tolerant of corrupted database files.
rebuild oldfile newfile errfile
oldfile - input file - normally named DB
newfile - output file
errfile - error file - not human readable
If the utility completes successfully, replace oldfile with newfile. Delete errfile.
53
SEGMENTATION FAULT
Segmentation faults and bus errors are related. Both are related to memory overflows. Segmentation faults
occur when memory is accessed outside of an arrays bounds. A bus error occurs when memory is
accessed outside the jobs work space.
The primary suspect in any abort related to a segmentation fault or bus error is a parameter with a default
of "get from database" and the value is not in the database. What is returned from a query for a missing
value is a NULL. This translates to a very large number that, if used, will overflow any array.
Most modules that query the database have override parameters for the values. A few still do not and as
such can not run with an incomplete (or inaccurate) database.
54
BUGREPORTS
When you have a problem that defies solution, a good bug report can speed the solution up considerably.
GeoCenter has an email and web based bug reporting system <feedback@geocenter.com> and
<http://cadence.geocenter.com/fogbugz>. Unfortunately the spammers found the web based system and
after 4000+ (> 10 times the number of actual) bug reports to see if we were interested in Viagra, etc. the
web based system was changed to forbid anonymous entries. This could be changed in the future if we can
get the spam filter to work.
Error messages displayed in the window where SeisUP was started, the relevant parts of the job listing
(parameters and error messages) and screen shots of displays can help. Some aborts also create core files.
These are normally found in the line directory.
The care and feeding steps of core files is as follows:
cd to the directory with the core file.
file core
This will report the executable name.

The core file may be named core.[number].
gdb executable core
Gdb is a debugger.
An alternative is dbx.
where
This will report the function calling

tree at the point of the abort. Capture
this tree.
quit
After the call tree is captured, the core file is of no more use and can be deleted. It is generally not
practical to send the core file to GeoCenter.
55
PROGRAMMING
There are two .pdf files to help with programming your own modules. They are:
Programmers Manual
Reference Manual
56
CAT_UPDATE
This script is a wrapper for catout to update the SeisUP.cat file.
57
CATOUT
SYNOPSIS
Print to stdout a list of modules organized by category along with brief descriptions of each module. The
build system makes use of an option to output an alternate format to regenerate the SeisUP module
catalog.
DESCRIPTION
This script prints a list of modules installed in SeisUP organized by category, with a short description
following each modules name. The script discovers which modules are installed in SeisUP by scanning
the contents of $QEDTOP/lib/db/mdb. This directory contains an .mdb file for each installed module,
which provides information about the module such as which category it belongs to.
catout optionally accepts an -f command-line option, which produces an alternate output format. This
alternate output format is the same format as a module catalog file, which are installed in
$QEDTOP/lib/db/cat. The catalog files installed in this directory are scanned by geodraw at startup to
populate the module librarian dialog. The build system relies on this alternate output format capability to
regenerate the main SeisUP module catalog: $QEDTOP/lib/db/cat/SeisUP.cat. Whenever a new module is
registered with the system by make db, the build system executes the following command to generate
SeisUP.cat:
$(QEDSRC)/make/bin/catout -f > $(QEDTOP)/lib/db/cat/$(CATALOG).cat
Prior to the incorporation of this script into the build system the module catalog was opened directly by
the dbu program. dbu read in the catalog and attempted to update it by finding the correct category for the
module being installed, and adding the module name in. However, the program was plagued by bugs such
as category names being left behind after the last module had been removed from the category.
This script is copied to $QEDTOP/bin/$QSYS/admin by the src/util/scripts Makefile. It is provided as a
utility to SeisUP users. Included also is a wrapper script for updating the main SeisUP catalog in the same
way that the build system does. This script is also found in $QEDTOP/bin/$QSYS/admin, and is named
cat_update. It is simply used to sync up SeisUP.cat with the contents of the mdb directory, which may be
necessary when distributing patches to clients.
NOTES
The ability of this script to function depends entirely on each modules .mdb file containing the module
category name. Before changing the build system to regenerate SeisUP.cat using this script, the category
name of a module was specified in the modules Makefile under the CATNAME build variable. This is no
longer necessary. At the same time I modified the .mdb file of every module in the system and committed
those changes to CVS. We must ensure that new modules put the category name in the correct place. The
mdb syntax checker (chk_mdb_syntax) will look for this and abort if the category is not specified. If the
category name is not present in the mdb file, then the module will be put in the "OTHER" category.
58
EXEC_DEBUG
This script can be modified to suit the host system to invoke a debugger to run a job executive in. This
script is executed by seisupd when a job has the debug flag set.
The sole argument to this script is the path to the executable to debug. While the stock script is
implemented as Bourne shell script, you are free to use whatever script interpreter you like.
59
LS_HORIZONS
Output a list of SURFACE matrices for an <area>/<line>. This is used by the parameter display code.
ls_horizons area line
60
LST_NODES
Output a list of cluster node files from $QEDTOP/lib/nodes. This is used by the parameter files to get a
custom list for user selection.
61
MODGEN
This script will generate the skeletal C code for a SeisUP queue processing module.
modgen module_name
The following files are generated (where "module" is replaced with the name of your module):
ex_module.c
pp_module.c
module.h
module.pdb
module.mdb
Makefile
You should be able to build the skeletal module into the system using build command make new db
install.
62
PLOT_LOGOS
Output a list of logo files from $QEDTOP/lib/logo. This is used by the parameter files to get a custom list
for user selection.
63
PVM_HOSTS
Output a list of host machines available to run PVM jobs on from $QEDTOP/lib/pvmhosts. This is used
by the parameter files to get a custom list for user selection.
64
LST_NODES
Output a list of color files from $QEDTOP/lib/cmaps. This is used by the parameter files to get a custom
list for user selection.
65
SeisUP Data Manager

Getting Started
The Application Main Window
The Menu Bar
The Status Bar
The Filesystems Manager
The Tape Devices Manager
The Backup Areas Window
The Restore Areas Window
Shortcut Keystroke Commands
Troubleshooting
Getting Started
This application provides a through and organized view of the data known to SeisUP, as well as methods
to delete, archive and restore that data. The Data Manager may be opened from SeisUPs "Tools" menu or
from the command line. If opened from SeisUP, the Data Manager will display datasets pertaining to the
current project.

The layout of the Data Managers main window should be familiar to many users as it is common to other
popular file management applications. Along the left side is the directory tree of SeisUPs "usr" directory
(see figure 1) and on the right are the contents of any selected subdirectory (see figure 2).
Figure 1: SeisUPs "usr" Directory Tree.
The directory tree has only three levels: the root "usr" directory, the "areas" folders in the second level and
the "lines" folders in the third level. To view the datasets located in an entire area click on its folder. This
will also cause the directory tree to expand, revealing its line subfolders. To view the datasets located in an
66
single line within an area, click the "directory expander" icon located just left of the area folder icon.
Then, click the line folder for which you wish to view the contents. Whenever an area folder is expanded,
the database file size residing in its line folders will be shown in the "DB Size" column to the right the line
name. To the right of the expanded area folder will be the summation of database sizes in its line folders.
Figure 2: Datasets Table for the Selected Area Folder.
The dataset table on the right side of the main window contains four static columns: dataset name, type,
area and line, as well as other columns the user added using the Columns option.
The Menu Bar

The Data Manager has four top level menu items: File, View, Dataset and Help...
The File drop down menu has eight options...
File -> Manage Data Filesystems...
This option will open the Data Filesystems Manager window. From this window the user may tell SeisUP
which filesystems dataset should be stored to. For more information see the Data Filesystems Manager
section of this document.
File -> Manage Tape Devices...
This option will open the Tape Devices Manager window. From this window the user may enter
information about remote tape devices so they are known to SeisUP. For more information see the Tape
Devices Manager section of this document.
File -> Backup Selected Areas...
This option will open the Backup Areas window. From this window the user can create a tar archive of the
selected area folders. For more information see the Backup Areas section of this document.
File -> Restore Areas...
This option will open the Restore Areas window. From the window the user can restore an archive created
from the Backup Areas window. For more information see the Restore Areas section of this document.
67
File -> Open Backup/Restore Log...

Selecting this option will open, in a separate window, the $QEDTOP/lib/log/archive_log file. This text file
contains information about previous backups and restores, such as archive name, archive time/date, file
path or tape drive, the area names archived or restored, etc.. The user should view this log if he or she is
uncertain if an archive has already been made of an area, and if so where is that archived stored. On tape
or on disk? How long ago was the archive made?
File -> Get Info...
The Get Info option will display the name, type, size, path, last modified date, and status for any selected
dataset in a separate window, titled "Dataset Properties" (see figure 3). The user may click on the "More
Information" at the bottom of the window to view the size (in bytes), last access date, user ID, user name,
group ID, group name, file permissions, area and line information for the selected dataset. Additionally,
for GCI datasets the Dataset Properties window will show a "Files" section listing the file paths and sizes
for the GCId, GCIm, GCIh and GCIz component files.
A nice feature of the Dataset Properties window is that it will automatically update its contents if the user
selects a different dataset from the dataset table in the main application window. Thus, instead of the user
opening a Dataset Properties window for a dataset, then closing that window before opening another, the
user can simply leave a single Dataset Properties window open while selecting which ever dataset he or
she is interesting in viewing at that moment and the Dataset Properties window will automatically update
itself.
68
Figure 3: The Dataset Properties Window.
File -> Preferences...

At the moment there are only two preferences which may be set. If the user is interested in viewing the
actual size of the GCI datasets shown in the datasets table the first preference box should be checked. If
unchecked the size column will report the size of only the GCI file (usually 256 bytes) instead of the
summation of each of the four GCI component files. If the second preference box is checked the number
of datasets being displayed in the datasets table is shown in the left side of the status bar, as well as the
summation of the size column in the table. Notice that, the summation of the size column shown in the
status bar is dependent on whether or not the first preference box is checked.
File -> Quit
Terminates the application. The user preferences are stored.
The View drop down menu has a single option...
View -> Columns...
Selecting this option will bring up a list columns from which the user can add or remove from the datasets
table in the main window. The user can choose to include the following columns in the datasets table: size
(formatted for readability), size (in bytes), date of last modification, date of last access, user ID, user
name, group ID, group name, path and permissions.
The Dataset drop down menu has a three options...
Dataset -> Delete
Deletes the selected datasets.
Dataset -> View Raw Data...
Selecting this option will display the raw data of the selected dataset in both hexadecimal and ASCII
formats.
Dataset -> History Viewer...
This option is only for use with GCI datasets. Selecting this option will display the processing history for
the selected dataset using the History Viewer application.
The Help drop down menu has a two options...
Help -> About...
Displays general information about the application.
Help -> Help...
Displays this document.
The Status Bar. See figure 4.

The status bar seen along the bottom edge of the applications main window has three sections. The left
side contains statistics about the currently selected area. In the middle is a progress bar used when
populating the datasets table. Finally, on the right is a combo box containing a list of columns and an input
field. The user may filter the rows of the datasets table based on the input given. For example, if the user
69
wishes to view only SEGY datasets he or she should select "Type" from the columns combo box and type
"SEGY" in the input field.
Figure 4: The Status Bar.
The Backup Areas Window

From this window the user may create a tar archive of the SeisUP area folders selected from the main
windows directory tree. Typically, users create archives to free space or transport area folders on one
machine running SeisUP to another machine. First, choose whether to backup up to a tape or disk. If
youre backing up to a tape, then enter that tapes drive number in the text field, otherwise choose a file
name, including path, for the tar archive. If you wish to backup the datasets associated with the selected
areas then click the box labeled "Backup datasets". If you are backing up to a low density tape click the
final box. The example Backup Areas window shown below is setup to create an archive named
"dallasArea.tar", saved to filesystem "/mnt/volume1". Once, the "Backup" button is clicked archiving will
begin and a window will be displayed to show the status.
Figure 5: A Backup Areas Example.
The Restore Areas Window

From this window the user may restore data archived using the Backup Areas option. First choose whether
the archived data is stored on tape or disk. If youre restoring from tape, put that tapes drive number in
the text field. If youre restoring from disk, type in the file name with path to the archive file. If you wish
to restore datasets contained in the archive click the box labeled "Restore datasets" and then choose a
filesystem from the table. The datasets in the archive will be restored to the selected filesystem. Finally, if
you wish test the restoring process and view its progress without writing any information to disk, then
click the box labeled "Display only". Once the "Restore" button is clicked a status window will appear
showing the progress of the restore. The example Restore Areas Window shown below is setup to restore
an archive named "dallasArea.tar", stored on filesystem "/mnt/volume1" with the datasets being restored
to filesystem "/seisup_data".
70
Figure 6: A Restore Areas Example.
Shortcut keystroke commands:

Manage Data Filesystems... ctrl+f
Manage Tape Devices... ctrl+t
Backup Selected Areas... ctrl+b
Restore Areas... ctrl+r
Open Backup/Restore Log... ctrl+l
Get Info... ctrl+i
Preferences... ctrl+p
Quit ctrl+q
Columns... ctrl+c
Delete... ctrl+x
View Raw Data... ctrl+d
View History... ctrl+y
About... ctrl+a
Help... ctrl+h
Troubleshooting
Problem: Opening folders takes too long.
Solution: If you are looking for datasets in a specific line then navigate to the line folder by clicking the
"directory expander" icon located just left of the area folder icon. Then, click the line folder for which you
wish to view the contents. This will reduce the number of datasets the Data Manager must load. The user
may also turn of the preferences which calculate GCI dataset file size and cumulative project size
71
statistics.
Problem: After filtering the dataset table, if I try to sort the results, the table refreshes back to the original
list of datasets.
Solution: This is a known problem for the Data Manager and hopefully will be resolved in a future
version. However, the user can get the desired results by sorting the table first, then filtering it.
72
Filesystems Manager
Back to the Data Manager Documentation
The filesystems manager allows the user to control where SeisUP stores data. All data sets will be written
out to the filesystems list shown here unless a user has setup a project specific filesystems list using the
Filesystems.. option, found in SeisUPs "Options" menu. A filesystem maybe an entire disk, for example
/mnt/volume1, or just a directory on a disk, such as /mnt/hill1/data as seen in figure 1. Displayed in the
window is a list of filesystems along with their available space and used space statistics. The user may add
or removed a filesystem using the plus and minus buttons below the filesystem list. If the user wants to
temporarily stop SeisUP from writing new datasets to a filesystem he or she may simply uncheck the box
next to its path. In other words, once the user has "unchecked" a filesystem SeisUP will not choose that
path to write new datasets out to. When a filesystem is "unchecked" its row in the filesystems list is grayed
out. Also, when a filesystem has reached ninety-eight percent capacity its row in the filesystems list
becomes red. The list of filesystems are stored as a text file at $QEDTOP/etc/filesystems (older versions
of SeisUP stored the filesystems list in the file $QEDTOP/jm/$HOSTNAME/disks.dat).
Figure 1: The Filesystems Manager Window.
The filesystems manager also provides functionality to make sure the data stored on a particular volume is
available to SeisUP. SeisUP uses "cleanup" files to keep track of where a dataset is actually stored. These
cleanup files are stored in the $QEDTOP/usr directory. When a user clicks the "check links" button the
application will search for three types of problems that can lead to data files on the filesystem not being
available to SeisUP: data files that are not linked in their SeisUP cleanup files, data files that have no
corresponding cleanup file, and data files that do not appear to be in a SeisUP recognizable format. This
search may take awhile to produce results, depending on the number of files on the filesystem, size of the
filesystem, and access speed. When complete the filesystems manager window will expand to display the
results of the search as well as a few more buttons (see figure 2).
73
Figure 2: Expanded Window Showing the Results of the "Check Links" Search.
The check links search will display three types of improperly linked datasets. To fix the problem where
"Data files not linked to their cleanup file" the user can select those data files from the list and click the
"update links" button. Datasets listed under the "Data files without a cleanup file" node should be deleted
if no longer needed, or left alone if another installation of SeisUP is linking that dataset. Files listed under
the "Files not recognized by SeisUP" can be deleted or ignored. Finally, the print button will produce a
hard copy of the files listed.
Note: It may not be practical to perform this search on very large filesystems( > 1000 Gigabytes ). Use the
"chklinks" script, found under $QEDTOP/bin/$QSYS/admin, it allows the user to restrict the search to a
specific area or line.
74
Options menu
Use the Options menu to perform the following operations:
Icon size.
Change the size of flow editor icons:
Selecting this will change the window geometry for the module librarian, the work area, the other
dialogs and fonts. When the flow editor is restarted, the same window size and location will be used.
The current grid size is also changed.
Small:
By default the size of flow editor is large. If you want to change the size of flow editor to small,
select icon size from the option menu and select small. A warning message will popup, that it will
restart the application do you want to proceed. Press Yes to change the size or press No to cancel the
action.
Large:
If the size of flow editor icons is small, and you want to change it back to large. Select icon size from
the option menu and select large. A warning message will popup, that it will restart the application
do you want to proceed. Press Yes to change the size or press No to cancel the action.
Edit mode
Mode when adding modules (Cascading):
Manual
Manually add modules
Automatic
Automatically add modules (Cascading):
Rightward
Auto. add towards the right side
Downward
Auto. add towards the bottom
Preferences
User preferences (Cascading):
Save configuration
Selecting this will save the window geometry for the module librarian, the work area, and the dialog
to open a line. When the flow editor is restarted, the same window size and location will be used. The
current grid size is also saved.
Default compression
Select this option for setting the default values for GCI data compression, if no option is selected , the
default value is set to none.
4:1:
Selecting this will set the default value for data compression as 4:1 for GCI data types.
2:1:
Selecting this will set the default value for data compression as 2:1 for GCI data types.
75
None:
Selecting this will set the default value for data compression as none for GCI data types.
Filesystems...
Select this option to setup a list of data set output locations specific to this project. Typically, all
SeisUP projects use a default list of filesystems which can be setup in the DataManager application
via the Filesystems Manager option. Be aware that overriding the default filesystems list in the
project will effect all users of that project. When this is the case, the message "* Override Output
Defaults *" will be shown in SeisUPs title bar. The alternative filesystems list will be used until a
user selects the "Use defaults" button.
See also the following topics:
Flow editor menus
76
Tape Devices Manager

Back to the Data Manager Documentation
The Tape Devices Manager shows the currently defined tape devices. Local tape devices can be found
automatically by using the "Discover Tapes" button, while remote tape devices will need to be added by
the user. When doing tape jobs in SeisUP, the user can specify a remote tape machine to read/write
seismic data over the network. All modules that read and write tape have been upgraded to be able to
perform I/O remotely over a network. On the remote side all that is needed is the tape server process to
perform the actual I/O. SeisUP need not be loaded on the tape server. See the remote tape server category
below for more information on installation and usage.
Figure 1: Tape Devices Table.
To add a tape device click the "plus" button below the table. A new row will be inserted into the table
which will need to be filled in with the appropriate information. Use the "minus" button to remove
unwanted tape devices. After you have edited the tape devices list, use the "Save" button to store your
changes. The Data Manager saves the tape devices list to a text file, $QEDTOP/etc/tape_devices
(previous versions of SeisUP saved this text file in $QEDTOP/jm/$HOSTNAME/tapes.dat).
The Unit # is critical information and is associated with the device name on the host computer. For
example, a Unix device "rmt0" built in the "dev" directory will have a unit number = 0. Another example:
A Windows NT device tape1 will have unit number = 1.
The Unit Name may be edited to whatever you feel best describes the tape device, however blank spaces
are not allowed in the description. Example: Exabyte-8505, describes a Exabyte tape drive model 8505.
The Host Name is also critical. This name must be the network name associated with a remote computer.
Examples: jupiter, jupiter.geocenter.com, 38.153.51.101. The program will allow IP address instead of a
device name. This way you do not have to edit the host tables on a machine to communicate with a tape
device on a remote machine. All tape devices attached to the local computer must have the unit name
"local".
The Sleep column is for stacker type tape devices. Enter the amount of time to sleep, in seconds, between
tape changes in the stacker.
The Timeout column is for socket communications to a remote machine. If the host machine cannot
connect to the remote machine within the time out period, then the job is aborted. Enter the time-out
period in seconds.
77
The Program Name column contains the tape server program name including path. This field is used
when the tape server is currently not running on a remote machine. The host machine will attempt to start
the tape server using this program. If you do not want SeisUP to attempt to start the tape server enter
"none" as the program name. Do not leave the program name column blank.
The Type column is used to define whether the tape device is normal, a stacker or robotic. Type = 0 for a
regular tape device, 1 for a stacker and 2 for robotic.
The Density column should be filled in as 0 for low density tapes and 1 for high density tapes.
The Remote Tape Server

All SeisUP processes that use tape have been upgrade for remote tape access. On the remote machine, a
tape server program will be started to perform the I/O. The tape server program must be installed on the
remote machine prior to using this method. SeisUP does not have to be loaded on the remote machine, just
the tape server program, "tapeserv". Windows NT users must also install the Nutcracker software. All the
above software will be located on the SeisUP CD-ROM.
Please observe the following to install and use the remote tape server:
Install: If SeisUP is not installed on the remote machine, copy the
$QEDTOP/jm/$HOSTNAME/tapeserv executable to the tape server host. Please be careful to select
the correct binary for the remote machine (i.e. load the Sun binary on Sun workstations). The
tapeserv executable for other platforms is also available on the SeisUP CD-ROM. Windows NT users
must also install the Nutcracker software located on the SeisUP CD-ROM.
Run: The tapeserv program can be started in either of the two following ways...
1) The first option is to start the tapeserv manually or have it start automatically at system
startup as follows. Type, "tapeserv &" at the directory where the tapeserv program is loaded. On
UNIX machines, the tapeserv program will automatically be started using the rshd daemon.
The user must have rlogin privileges without entering a password. Windows NT users must
install a win32 version of the rshd daemon for automatic startup. Otherwise start the tapeserv
manually before trying to access remote tapes.
2) The second option is to have SeisUP attempt to start the remote tapeserv when a job needs to
use a tape device on that host. To allow this, make sure the remote tape device has an entry in
the Tape Devices Table (seen in figure 1) and the host name and program name fields are filled
in correctly. SeisUP will use that information to start the remote tapeserv when a job tries to
access a tape device on that host.
Use: When starting a remote tape job via SeisUP, use the Job Monitor to respond to tape handling
commands. Within the Job Monitor, select the "Reply to Message" option from the "Job" menu. A
dialog box will appear (see figure 2 below). When the question appears asking for a tape unit number,
please select the correct unit number corresponding to the correct host name from the list that is
provided. Users who manually enter the tape information must now enter the unit number followed
by a space, then the host name. Example: 131 godzilla, where 131 is the tape unit number and
godzilla is the remote host name.
78
Figure 2: Job Monitors Reply Dialog.
79
Introduction
SeisUP is a system that will create flows that comprise a series of software tools (called modules) and data
sets. After connecting a series of modules to a data set, the modules can be run interactively or in batch.
The flows reside in a hierarchical structure consisting of areas and lines. A flow represents the entire
history performed to a particular line within an area.
SeisUP consists of four main components:
1. A flow editor, which is a work area to create and modify flows. The flow editor also will be used to
execute flows.
2. A seismic data inventory package, which is a tape management system.
3. A job server, which responsible for the execution of flows in a networked environment.
4. A matrix editor, which is a multi-dimensional spreadsheet program for editing dimensional vectors
such as geometry and velocities.
This article will describe the use of SeisUP. It assumes the reader is familiar with X-windows and Motif.
Starting SeisUP
At the command line type:
seisup
This will start the flow editor and it will open the last flow that was saved when SeisUP was quit. If this is
the first time to start the flow editor for a particular user, it will request the user to open a line.
A dialog window will also appear that will indicate the version and copyright notice for SeisUP. To
remove the window, click the left mouse button anywhere in the window or select Close from the window
menu.
Opening your first flow

A Dialog with a title of Open a line will appear. This dialog consists of two lists. On the left is a list of
areas and on the right is list of the lines within the area selected from the left. If you have permission to
open another users flow (See your system administrator), then select the area and line you wish to open.
Otherwise you will need to create a new area and line. The current area and line will be displayed in the
flow editors window title bar.
Create an input data set if one does not already exist and start attaching modules from the module
librarian. When the flow contains the desired list of modules, modify the parameters, and execute the flow.
See also:
80
Flow Editor Menus

Available application modules
Available matrices
SeisUP Datatypes
Job Monitor
Data Manager
History Viewer
Administrative Tools
glossary
81
Using the flow editor

In the flow editor you create a flow which will be composed of a series of icons. The icons can represent
either a data set, module, or group. A data set represents a physical medium that contains data and is
attached to input and output modules. A module will perform some operation to the data and send the
results to the next module. A group is an icon that represents a series of modules and data sets. The flow
editor is an environment in which flows can be built and executed. A single flow will contain all of the
modules and data sets for a particular line within a particular area.
The flow editor also supports work groups where multiple people can edit the same flow at the same time.
Modules added, moved, removed, etc. will be reflected on the same flows that are simultaneously opened.
See the following topics:
Introduction
Creating a flow
Opening an existing flow
Saving a flow
Deleting a line
Quitting the flow editor
Selecting icons
Adding modules
Inserting modules
Creating an input data set
Editing flows and icons
Grouping icons
Ungrouping icons
Connecting modules
Query connections
Releasing data sets
Executing modules
Flow editor menus
82

The flow editor consists of a large working area below the menu bar that can be scrolled around in which
flows can be built. To the right of the working area is an icon bar that provides a short-cut to menu
functions in the menu bar (See Flow editor menus).
The module librarian is a dialog that will display the available modules within a set of categories, usually
the module librarian is located to the left of the working area.
An icon in the working area consist of the following:
1. A title, which contains the module, data set, or group name.
2. A status signal in the top right corner, that represents the status of the module or data set (See Status
signal).
3. A signal below the status signal to indicate if a note is attached to the icon.
4. A picture representing that module or data set. If the icon is a data set, the picture will be either a disk
or stack of tapes. If the icon is a module, the picture will be an image drawn to represent that module.
If an image doesnt exist for the module, the default picture will be displayed which is a picture of the
word SeisUP.
5. Stubs on the top and/or bottom of the icon representing available channel connections to other
modules or data
83

To open an existing flow, select Open a line from the File menu or click the
menu icon. A dialog
will appear that will have a title of Open a line. Select the area and then select the line within the area.
Click on OK to open the flow. The flow editor will position the flow (scroll bars) at the same position
when the flow was last saved. If the flow is owned by another user and you do not have write access
privileges, the flow editor will display a dialog that informs you that the current flow is opened for view
mode only and you will not be able to modify the flow.
Creating a flow
Saving a flow
Deleting a line
84
Saving a flow
To save a flow, select Save from the File menu or click the
flow is also saved.
Creating a flow
Deleting a line
85
menu icon. When you execute a flow the
Deleting a line
To delete a line (flow), select Delete lines from the File menu or click the
menu icon. A dialog will
appear that will have a title of Delete line. Select the area and then select the line within the area to delete.
Click on OK to delete the line. Another dialog will appear that will request if you are sure, click Yes.
When you are through deleting lines click Cancel on the Delete line dialog. If you are deleting a line and
it is the current flow, the flow editor will request that you open another line and the dialog title will change
to Open a line (See Opening an existing flow).
Deleting an area
To delete an area, delete all of the lines within the area
Creating a flow
Saving a flow
86
Quitting the flow editor

To quit the flow editor, select Quit from the File menu or click the
menu icon. If the flow was
modified and not saved, the flow editor will ask if you wish to save the flow.
87
Selecting icons
Before you can execute or perform an editing operation such as cut, copy, or move, on icons (data set and
module), you must select them.
To select an icon, click on the icon with the left mouse button.
The icon will become highlighted.
To deselect an icon, clicking the left mouse button with the cursor in an empty area of the flow work area
or click the Ctrl key and the left mouse button on an already selected icon.
To select all of the icons currently in the flow editor, select Select all from the Edit menu.
To select multiple icons, press the mouse in an empty space next to the first icon you wish to select. Drag
the mouse towards the last icon you wish to select. An outline of a rectangle will appear. When you
release the left mouse button, all icons falling within the rectangle outline will be selected.
You can also select multiple icons by holding down the Ctrl key and click on each icon in turn.
Use the Ctrl key while dragging the mouse to add or delete more icons from the selection.
88
Inserting modules
To insert a module between two connected modules:
1. Make sure the module librarian is displayed and the edit mode (See edit mode under Options menu)
is automatic.
2. Select two icons in the flow that you wish to insert between.
3. Click the middle button on the module in the module librarian that you wish to insert into the flow.
Adding modules
89

You can copy, cut, duplicate, group, and move single modules or groups of icons by using the flow editor
menus but first the icon(s) must be selected.
To move icons, press the left mouse button on one of the selected icons and drag the mouse to the desired
location. As you move the mouse, an outline of the icons will be drawn. Release the mouse button to
invoke the move operation.
To copy icons to the paste buffer, select Copy from the Edit menu or click the
menu icon. You
cannot copy data sets to the paste buffer because data sets must be unique within a line.
To cut icons to the paste buffer, select Cut from the Edit menu or click the
set will cause the data set to be released (see Releasing a data set).
menu icon. Cutting a data
To paste icons from the paste buffer to the work area, select Paste from the Edit menu or click the
menu icon. Then move the mouse to the working area. You will see an outline of the icons in the paste
buffer. Move the outline to the desired location by moving the mouse and then click the left mouse button.
To duplicate modules with connections intact, select Duplicate from the Edit menu or click the
icon.
To copy icons to another line or lines, select Line copy from the Edit menu or click the
(See Copying parts of a line to another line).
menu
menu icon
To undo a previous operation, select Undo from the Edit menu or click the
menu icon. To be able to
perform undo, you must click undo immediately after the undesired function. For example, if you cut an
icon and want to undo the operation, do not click the mouse anywhere but on the undo function, otherwise
the icon will be lost.
To group a series of icons into a single icon, select Group from the Edit menu or click the
(See Grouping icons).
To ungroup a group icon, select Ungroup from the Edit menu or click the
Ungrouping icons).
90
menu icon (See
menu icon

Connecting modules
91

To copy some icons to another line or lines, select the icons you wish to copy, then select Line copy from
the Edit menu or press the
menu icon. The line copy will copy all of the parameters, matrix files,
and notes associated with each icon. Those matrices where there exists matrices with same names of the
same types in the target area/line will not be copied. If the user does want to overwrite them, go to the
target line, delete those matrices and then do Line Copy, Physical data sets will not be copied so the data
sets will be shown as not existing. When line copy is selected, a dialog will be displayed with a title of
Line Copy.
To use the line copy dialog:
1. Select the areas from the Areas to select list that you wish to copy to. The flow editor will then
display a list of the all of the lines within each of the areas you selected in the Pick lines for copy list.
2. Select the lines from the Pick lines for copy list that you wish to copy to. Click on an already selected
item to remove it from the selection list. Click the All button to select all of the lines in the list.
3. Click the OK button to start the copying process. This could take a while depending on how many
icons you wish to copy and how many lines you are copying to and the size of the matrices to be
copied.
92
Grouping icons
To group a series of icons to a single icon, select the icons you wish to group, then select Group from the
Edit menu or click the
menu icon. A group will allow you to tidy up your work space. But at present
you cannot execute a group. You must first ungroup the group and then execute. After Group is selected:
1. A dialog will be displayed with a title of Grouping and will request for a group name. Click the left
mouse button in the text field and type in a name.
2. Click the OK button.
3. Move the mouse to the working area. You will see an outline of the group icon.
4. Move the outline to the desired location by moving the pointer and then click the left mouse button.
93
Ungrouping icons
To ungroup a group icon into a series of icons, select the group icon you wish to ungroup, then select
Ungroup from the Edit menu or click the
menu icon.
After Ungroup is selected:

1. Move the mouse to the working area. You will see an outline of the icons within the group.
94
Connecting modules
To manually connect modules that are already in the flow:
1. Press the right mouse button over the module that contains the output channel that you wish to
connect from.
2. Select Connect ... from the pop-up menu.
3. If the module contains multiple output channels, a dialog will appear that will request you to select
which channel you will be connecting from. Click the OK button after you have selected the
appropriate channel.
4. The pointer will change from a hand to an arrow going downwards.
5. Click the left mouse button on the module that contains the input channel that you wish to connect to.
6. If the module contains multiple input channels of the same data type, a dialog will appear that will
request you to select which channel you will be connecting to. Click the OK button after you have
selected the appropriate channel.
7. The connection will be drawn and the pointer will change back to a hand.
8. To connect more than one existing module, hold Ctrl key and click with the Middle button on every
module you wish to connect.
To cancel a connection request click the left mouse button in an empty area in the work area.
95
To manually disconnect modules that are already in the flow:
1. Press the right mouse button over one of the modules that you wish to disconnect from.
2. Select Disconnect from the pop-up menu.
3. If the module contains multiple channels, a dialog will appear that will request you to select which
channel you will be disconnecting from. Click the OK button after you have selected the appropriate
channel.
4. The pointer will change from a hand to arrows going vertically and horizontally.
5. Click the left mouse button on the other module that you wish to disconnect to.
6. If the module contains multiple channels, a dialog will appear that will request you to select which
channel you will be disconnecting to. Click the OK button after you have selected the appropriate
channel.
7. The connection will be cleared and the pointer will change back to a hand.
8. To disconnect more than one existing module, hold Ctrl key and click with the Middle button on
every module you wish to disconnect.
To cancel a disconnection request click the left mouse button in an empty area in the work area.
Connecting modules
96
Query the connections of a node

When a flow becomes large and clustered, it may be necessary to know the actual connections of a node
that linking in or out through which channels. There are two ways to check the connections:
1. Move the mouse pointer to the node queried and press the right mouse button to bring up the popup
menu. Pick Show Connections and release the button. Then a dialog will appear showing detailed
connection information about that node.
or
1. Move the mouse pointer to the node queried. Press the Shift Key and keep it down while pressing left
mouse button, then the links of the node will be highlighted. Release the button will be back to
normal. Although this is a convenient way to query the connections, to know accurately, the user may
need the first method.
Using the Flow editor
Connecting modules
97
Releasing data sets

Data sets that have allocated a file on disk or some magnetic tapes will have the status light on the icon a
green color.
To release (free storage space) a data set:
1.
2.
3.
4.
Press the right mouse button over the data set that you wish release.
Select Release from the pop-up menu.
A dialog will appear that will request if you are sure. Click on Yes.
The status light on the icon will turn to gray meaning that the data set does not exist.
Data sets can also be released by cutting the icon from the working area (see Editing flows and icons)
98
Seismic Data Inventory program

The Seismic Data Inventory (SDI) program is responsible for management of the tape libraries. Please
note that this has no connection to the Systems Development Incorporateds CGM viewing and plotting
programs. Disk management is maintained by the DataManager application.
SDI is started by typing sdinv in a console window.
Library management
To manage a tape library, create a user named sdi. This user can scratch any users tapes. Normally only
the user that assigned the tape can release the tape. The user sdi can also create a new tape database.
A new database can be created as follows:
1. Make sure that the directory filesystem/sdi exists where filesystem is the directory where SeisUP(R)is
installed. If not, perform the following:
1. Sign on a root.
2. Type mkdir filesystem/sdi
3. Type chmod 777 filesystem/sdi
4. Type cp filesystem/install/files/SDItapes filesystem/sdi
5. Type chmod 777 filesystem/sdi/SDItapes
Commands
The following are available commands for SDI:
1. add - Add tapes to the library. SDI will request for the starting and ending tape numbers to add.
SeisUP(R) determines different tape media types by the tape number. Each SeisUP(R)installation
may customize the different media types and tape number ranges for each media type in the file
filesystem/lib/qedtapes where filesystem is the directory where SeisUP(R) is installed This file is also
used in the flow editor when creating tape data sets. The following is the default qedtapes definition:
9track: Tape numbers 1-19999
8mm: Tape numbers 20000-29999
3480: Tape numbers 30000-39999
dlt: Tape numbers 40000-49999
2. assign - Assign tapes from the library. SDI will ask for the area name, user name, line name, data set
name, media type, and number of tapes to assign. SDI will check to see if the data set already exists
in the database under the area and line specified. If it exists, SDI will ask if you wish to append the
tape(s) to the existing data set. After assigning the tapes, SDI will print the assigned tapes to the
console. If a log is set, the reel numbers will also be printed to the log.
3. change - Change information given a reel number. SDI will request for a single tape number and
allow you to change most of the fields associated with the tape.
4. delete - Delete reel numbers.
5. end - Quit the SDI program.
99
6. help - Produce a summary of the available commands.

7. log fname - Print tapes that are allocated to a log file. fname should be the name of the log file.
Example: log sdi.log.
8. query - Query database by data sets. This option allows you to query the database by specifying wild
card specifications of the area, line, and data set. For wild card specifications a * must trail any name.
For example Tri* or *. The information displayed can conform to the following levels:
1. Areas (0): Show for each area the count of the tapes assigned.
2. Lines (1): Show for each area and line the count of the tapes assigned.
3. Data sets (2): Show for each area, line, and data set the assign date and the count of the tapes
assigned.
4. Ordinals (3): Show for each area, line, data set, and ordinal (tape) the assign date, reel number,
and the count of the tapes assigned.
9. rquery - Query database by reel numbers. SDI will ask for the first and last reel number to query for.
Information will be displayed for every tape between the first and last.
10. scratch - Scratch tapes by data sets. This option allows you to scratch data sets by specifying wild
card specifications of the area, line, and data set. For wild card specifications a * must trail any name.
For example Tri* or *. SDI will report to you the number of matching data sets and optionally print
the information for each data set. SDI will then confirm whether or not you wish to scratch the
selected data sets.
11. rscratch - Scratch tapes by reel number. SDI will ask you for a single reel number, print information
on the reel, and confirm whether or not you wish to scratch the reel.
12. slist - Produce a scratch tape list. SDI will ask for the media type, print the number of available tapes,
and optionally print the reel numbers that are available to assign.
13. export fname - Copy all records to an ASCII file.
The following commands require root or sdi user access.
create - Create a new tape library.
convert - Modify the tape library to allow use between systems.
import fname - Copy all records from an ASCII file.
100
Using Motif
Motif is a windowing environment that runs on top of X-Windows. Programs that are written under Motif
follow a particular style of appearance and behavior. A common style allows you to easily use a wide
variety of Motif style applications.
The Motif environment consists of the following:
1. Motif widgets: Widgets are graphical objects or controls that allow you to interact with the
application program. Some of the common controls are:
1. Lists
2. Scroll bars
3. Push buttons
4. Check boxes and radio buttons
5. Text input fields
6. Menus
7. File selection box
2. Motif window manager: The window manager helps you manage the windows on your screen. The
window manager provides functions such as open, closing, and moving a window. The window
manager is the one responsible for the three-dimensional frame around each window.
101
Lists
Items from a list may be chosen by a list box or a Motif option list. A list box is a rectangular area
showing the available list items. If the list is larger than the list box, scroll bars will appear along the right
and bottom edges of the window. When an item is selected, it is highlighted and may show up in a
selection just below the list. Items may be selected by pointing to the item in the list and click the left
mouse button or the up and down cursor keys to highlight the item you want.
An option list is a one line rectangle that will show only the currently selected item in the list. The
rectangle will be beveled upwards and have bar graphic on the right hand side. For example:
To select another item within an option list press the left mouse button on the list and a list will appear.
Drag the mouse to the desired selection and release the mouse button.
102
Scroll bars
Motif scroll bars allow you to control what portion of a larger object is displayed within a window. Scroll
bars have an arrow at each end and a rectangular slider in the middle. The slider represents the current
relative position within a window. The following are ways to move the slider:
1. Position the mouse over an arrow button and press the left button to scroll one item in that direction.
Hold the mouse down to move multiple times. For text applications, this will move one line at time.
2. Press the left mouse button on the slider, drag the pointer, release the button at the desired position.
Some windows will scroll the window as the mouse is being dragged, otherwise the window will
scroll when the mouse is released.
3. Click the left mouse button in the area between the arrows and the scroll bar to move a page at a time.
The direction of the paging will move in the direction of the mouse relative to the scrollbar.
103
Push Button
A Motif push button is a rectangular area that causes an immediate action. Push buttons are beveled
upwards and can display either text or an icon. To press a push button, point to it and then click the left
button.
104
Check Boxes and Radio Buttons

When an application has a finite list of options or settings, they are often presented as a list of toggle
buttons. Like a light switch, a toggle button can be on or off. A group of Motif toggle buttons may be
presented as follows:
1. Check boxes
are used for a group of settings that can be set in any
combination. Check boxes are usually displayed as small square buttons. The graphic indicator is
usually a raised square to indicate an on state or a pressed square to indicate an off state.
2. Radio buttons are used to group related settings that allow only one selection at a time. Radio buttons
are usually displayed as small diamond-shaped buttons. The graphic indicator is usually a filled
diamond to indicate an on state or an empty diamond to indicate an off state.
To select a check box(s) or a radio button, click the left mouse button on the desired option.
105
Text Input Field

Motif text input fields are used to display and enter text. The text may be either a single line or multiple
lines.
Some applications may display more than one input field at a time, so you may have to first select a field
before you enter text into it. To select an input field, point to it and then click the left button. An I-shaped
cursor will begin blinking in the box. This cursor marks your typing position.
While typing in a text input field, use the Backspace and Delete keys to delete unwanted characters. Use
the cursor keys to move the cursor to a different position.
The mouse can be used to move the cursor position by positioning the mouse at the desired location and
clicking the left mouse button. Text may selected by dragging the left mouse button over the desired text.
A text selection can be extended by dragging the right mouse button.
Clicking the middle button copies the current selection to the insertion cursor.
Text can also be deleted with the mouse by selecting the text to delete and then typing a character to
replace it.
106
Using pull-down menus

Motif pull-down menus are commonly accessed from a menu bar across the top of a window (just below
the title bar). Each word in the menu bar represents a pull-down menu. The menus are used to access
commonly used functions.
A function from the pull-down menu may be chosen by either of the following methods:
1. Point to the menu you want to display. Press and hold the left mouse button and drag the pointer to
highlight the desired function. Then release the button.
2. Point to the menu you want to display. Click the left mouse button once to display the menu then
point to the desired function, and click again. If you do not want to select one of the functions from
the menu, press the left mouse button again but outside of the menu space.
Cascade menus
Cascade menus (submenus), will provide additional options on pull-down menus. The cascade menus are
indicated by an arrow next to primary window selection.
To select a cascade menu, hold the left mouse button, drag the pointer to the selection that has the arrow in
it, move the pointer to the right to the submenus, and release the button on the desired option.
Menu Short Cuts

In addition to mouse selection of a menu, the following allow you to quickly select a menu option:
1. An accelerator key is a key on your keyboard that the application has assigned to directly execute a
function in a menu. Accelerators are listed in the menu next to the function name. You can use
accelerators to execute menu functions without displaying the menu.
2. A mnemonic is a key that allows you to select a menu or a menu item without using the mouse by
typing significant within a menu. Mnemonics are indicated as underlined characters in the menu.
Mnemonics on the menu bar may be activated by typing ALT and the mnemonic at the same time.
The Esc button will cancel menu selection. You can also select a menu item by using the cursor keys
to highlight to the desired function, and then press Enter.
107
File Selection Box
The Motif file selection box is used to cross through directories, view the file names and sub directories in
them, and selects a file. The file selection box contains four main areas:
1. Filter: A text input field for displaying and editing a pattern. When you click on the Filter button or
press Return after modifying the pattern, all the files that match the pattern are displayed in the files
list.
2. Directories list: Displays the directories in the filter. Selecting a directory in the directories list with
the left mouse button will display the files from that directory in the files list and enters the name of
the directory in the selection field.
3. Files list: Displays the files in the file filter. Selecting a file in the files list with the left mouse button
enters the name of the file in the selection field.
4. Selection field: A text input field for displaying and editing a file name
108
Managing Windows
The following document will describe how to manage windows under the Motif window manager.
Window Terminology
Window Menu
Dash in the top left corner of the window.
Title bar
Top portion of the window containing the title.
Minimize button
Little dot to the left of the Maximize button at the top right corner of the window.
Maximize button
Big square at the top right corner of the window.
Mouse Button Terminology

Click
Press and release a button without moving the pointer.
Double-click
Click a button twice in rapid succession.
Drag
Press and hold a button while moving the pointer.
Moving a Window
To move a window from one location to another:
1. Position the pointer within the title bar of the window.
2. Press down the left mouse button and drag the pointer. As the pointer moves, the outline of the
window will appear.
3. Release the mouse button when the window is in the desired location.
Alternate method: Drag on the Window Menu, release on Move, position the window outline, and click a
mouse button.
Resizing a Window
To resize a window:
1. Determine the direction to resize the window. The corners allow resize in a diagonal direction, while
the sides allow resize in the corresponding horizontal or vertical direction.
2. Position the pointer on the window corner or the side you want to resize.
3. Press down the left mouse button and drag the pointer. As the pointer moves, the outline of the
window will appear.
4. Release the mouse button when the window is resized to the desired size.
109
Alternate method: Drag on the Window Menu, release on Size, position the window outline, and click a
mouse button.
Raising a Window
To raise a window above the rest:
1. Position the pointer within the title bar of the window or on a window border.
2. Click the left mouse button.
Lowering a Window
To place a window on the bottom of the window stack:
1. Position the pointer anywhere within the window you wish to lower.
2. Press Alt and the left mouse button at the same time.
Alternate method: Drag on the Window Menu and release on Lower.
Maximizing a Window
To enlarge the window to the maximum dimensions of the screen:
1. Click the left mouse button on the Maximize button in the window you want to maximize.
Alternate method: Drag on the Window Menu and release on Maximize.
Restore a Maximized Window

To restore a window that was maximized:
1. Click the left mouse button on the Maximize button in the window you want to restore.
Alternate method: Drag on the Window Menu and release on Restore.
Iconify a Window
To convert a window into an icon:
1. Click the left mouse button on the Minimize button in the window you want to minimize.
Alternate method: Drag on the Window Menu and release on Minimize.
110
Deiconify a Window
To convert a icon into a window:
1. Click the left mouse button on the icon you want to deiconify.
Alternate method: Drag the Window Menu with the right mouse button and release on Restore.
Moving an icon
To move an icon from one location to another:
1. Press the left mouse button and Drag the pointer on the icon you want to move. The outline of the
icon will appear.
2. Release the mouse button when the icon is in the desired location.
Close a Window
To close a window:
1. Double-click on the Window Menu for the window that you desire to close.
Alternate method: Drag the Window Menu and release on Close.
Quitting X-windows
1. Quit any running applications. This avoids the possible loss of data due to improperly stopping a
program.
2. Drag the right mouse button in the root section of the screen and release on logout.
111
Creating a flow
To create a new flow, select New line from the File menu or click the
menu icon. A dialog will
appear that will have a title of Create new line. If you wish to create a line (flow) under an existing area,
select the area. Otherwise, type in a new area in the text field below the Area list. Then type in a new line
in the text field below the Line list. Click on OK to create the flow. An empty flow will be displayed and
the new area and line will be displayed on the flow editors title bar. If a new area is being created, another
dialog will appear that will have a title of New project initialize.
This dialog will request for the following area level parameters:
1.
2.
3.
4.
Type of Survey: 2-D or 3-D

Measurement units: Feet or Meters
Prospect name: This is an optional text field.
Prospect location: This is an optional text field.
Click on OK when the parameters are set.

Saving a flow
Deleting a line
112
File menu
Use the File menu to perform the following operations:
Module librarian
Opens the module librarian if you have closed it.
Open a line
Open an existing line.
New line
Create a new line.
Save
Save current line.
Backup area
Backup area(s).
Restore area
Restore area(s).
Delete lines
Delete lines.
Import Dataset
Create an input data set.
Project Info
Displays project survey type, measurement units, prospect name and prospect location.
Select Plotter...
Brings up the plotter selection window.
Print Preview...
Previews the selected CGM data set.
Print
Submits selected CGM data set for plotting.
Quit
Close flow editor.
See also the following related topics:
Flow editor menus
113
Creating an input data set

If you need to add a module that requires an input data set and you have no data sets to connect to as in the
case with a new flow, select Pick data set in the File menu or click the
displayed that will request for data set parameters as follows:
menu icon. A dialog will be
1. Data set name: Move the mouse to the dialog and click on the Data set name text field and enter a
data set name. The data set name must be unique within the flow.
2. Data Type: Select the data type from the available choices.
3. Data store media: Select either Disk, High density tape, or Low density tape as the data sets physical
medium.
4. If the data store medium is tape, you may choose tape type and pick reel information. If you choose
Yes for Need reel info ?, you must edit the matrix to define the reel names for the data set.
5. If the tape drive you are reading from is a tape stacker, select yes for the tape stacker question. For
tape stackers, the tape handling routine will eject the tape currently being read, wait 60 seconds for
the next tape to be mounted and then request for another tape unit number. You may use the
execution type ahead buffer to input multiple tapes in the tape stacker.
6. If the data store medium is disk, you will need to enter a filename via the File selection box.
7. Click OK to add the data set to the flow. The icon will be placed in the upper left hand corner of the
flow window.
Tape attribute edit
114
Using the execution type ahead buffer

For jobs that require operator intervention, such as tape input and tape output, the traditional method of
responding to questions is through the job monitor. But if you know what the questions are going to be
ahead of time, then the execution type ahead buffer may be used. The execution type ahead buffer is a text
field where each line will correspond to a returned message to the task. To set a message in the execution
type ahead buffer:
1. Place the mouse over a module within a job that is currently running or waiting for later execution.
2. Press the right mouse button and select Exec Type Ahead from the pop-up menu.
3. A dialog will appear that will have a title of the assigned job id along with Execution Type Ahead.
Select a type ahead queue for the responses to go to. The type ahead queues can correspond to any
data set within the current execution run or All for any response. If data set handler cannot find any
type ahead responses for its data set type ahead queue, it will attempt to get responses from the All
queue if any exist.
4. Press the left mouse button in the text area and enter the messages to send to the task one line at a
time. The # character in the far left side will be interpreted as a comment and will not be passed back
to the task requesting a response.
5. Click the OK button to set into the buffer the contents of the text field. Click the Cancel button to
remove the dialog. Click the Delete button to clear the type ahead.
115
Edit tape attributes for tape

If the storage medium of the data set is tape you can change some of its attributes: tape density, tape type,
compression, and reel info matrix. If you want change more, you have to cut this data set node and create a
new data set node with the attributes you want.
1. Select either High density tape or Low density tape as the data sets physical medium.
2. If the data type for this data set is SeisUP internal format, you may choose the compression type as
none for no compression, 2:1 for 16 bit per sample, or 3:1 for 1 byte per sample. The compression is
a lossy method using floating point scalars every so many samples.
3. To set the reel number reel information for the tape handler. Select Yes for Need reel info ?, you must
edit the matrix to define the list of tape names for the data set.
4. If the tape drive you are reading from or writing to is a tape stacker, select yes for the tape stacker
question. For tape stackers, the tape handling routine will eject the tape currently being read or
written, wait 60 seconds for the next tape to be mounted and then request for another tape unit
number. You may use the execution type ahead buffer to input multiple tapes in the tape stacker.
116
Adding modules
To add a module to the flow, first make sure the module librarian is displayed. If the edit mode (See edit
mode under Options menu) is manual:
1. Click the left button on the module in the module librarian that you wish to add to the flow.
2. Move the mouse to the working area. You will see an outline of the module icon.
To add modules if the edit mode is automatic:
1. Select an icon in the flow that you wish to connect to. You must select only one icon and it cannot be
a group icon.
2. Click the left button on the module in the module librarian that you wish to add to the flow. The new
module will now become highlighted and more modules or data sets can be added. If the module
being added contains an output data set as the first output channel, the flow editor will display a
dialog with a title of dataset. Move the mouse to the dialog and click on the Data set name text field
and enter a data set name. The data set name must be unique within the flow. If the data type supports
both tape and disk, the dialog will also display a Data Source. Select either Disk or Tape. Click the
left mouse button on OK to add the data set to the module. The data set will now be highlighted. If
the module contains an output data set channel and an output channel that can be connected to the
next module and you wish to add another module to this module, move the data set to the side and
select the module.
The flow editor will make sure that when adding modules that the data type matches, otherwise, the flow
editor will complain.
If the module being added contains no input channels or contains only optional input channels, the flow
editor will place the module in the vicinity of the selected module. If no module is selected, the flow editor
will place the module near the top left hand corner.
See also Inserting modules.
117

The module librarian is a dialog used to add modules to the flow. If the module librarian is not on the
screen, select Module librarian from the File menu or click the
menu icon. To see the available
modules within a category, click the left mouse button on a category item. To see the module descriptions
within a category click the Description button at the bottom of the dialog. Click the Search button to
interactively find a module by name. Click the Dismiss button with the left mouse button to close the
dialog.
Selecting icons
Adding modules
Inserting modules
Available application modules
118

Module parameters can be of the following types:
1.
2.
3.
4.
5.
6.
7.
Integer
Float: Single precision floating pointer number
Double: Double precision floating pointer number
String: Character string
Single list: An option list to select a single item
Multiple list: Multiple selections via radio buttons
Matrix: Matrix files via the matrix editor
Parameters that contain no value mean that those parameters are required. Parameters that are enclosed
within double quotes mean that the program will compute a default and the string within the quotes should
indicate a description of the default.
The parameter selection is a rule based system whereby parameters that depend upon other parameters will
be displayed. For example, If one of the parameters is an option list of yes or no, and you select yes,
parameters that depend upon a yes selection will appear, parameters that depend upon a no selection will
disappear. Parameters cannot be modified while the module is being executed.
To modify the parameters for a particular module:
1. Press the right mouse button over the module that you wish modify parameters for.
2. Select Parameter from the pop-up menu.
3. A parameter dialog will appear with a title of the module name.
The parameter dialog is composed of the following parts:
1. In the top section, the left hand side will contain a short description for the module and a Module help
button to display the help file for the current module. The right hand side will contain three buttons.
Click the Cancel button to cancel any parameter changes. Click the OK button to set the parameters
into the module. Press the Help button to display this help file.
2. Below the top section will contain each of the parameters where each parameter is displayed row at a
time. Each parameter will contain a description, a place to modify the parameter and a series of
buttons. The following are a description of the buttons:
Button with a dot on it: This button will be displayed next to any parameter that is of matrix
type.
If a parameter is modified, the buttons OK and Cancel will be displayed. OK will validate the
parameter. while Cancel will restore the parameter to the value before it was modified. Pressing
the Enter key will also validate the parameter unless the parameter is of matrix type.
A Reset button will be displayed on the right hang side. If clicked, the parameter will return to
the system default.
119
Matrix parameters
To modify a matrix parameter, either enter the name in the text field and press enter to edit the matrix, or
click the dot button next to the text field. When the dot button is clicked, a dialog will appear that will
display a list of matrixs with the same matrix type. For example all of the RMS velocities. To select a
matrix within the dialog:
Select a matrix from the existing matrixs list if you want a matrix that was made previously.
or
Click the left mouse button on the text field and type in a new matrix name.
or
Select a existing matrix from the list and click the Copy button. This will cause a dialog to appear
that will contain the title Matrix copy and will ask you for a name to copy to. Click the left mouse
button on the text field and type in a matrix name. Then click the OK button. This will copy the
contents the existing matrix to a new one so that you can make changes to the new one. Select the
copied matrix from the list of existing matrixs.
To edit a selected matrix, click the Edit button.
To place the current selection in the parameter text field and not edit the selection, click the OK button.
To delete the current selection, click the Delete button. A dialog will appear that will request if you are
sure.
Using the matrix editor.
120
Using the flow pop-up menu

When the mouse is placed over an icon in the working area and the right mouse button is pressed, a
pop-up menu of available options are displayed. For data sets the following will be displayed:
Connect
Connect the data set to a module input channel
Disconnect
Disconnect the data set from a module
Show Connections
Display status of current connections
View Comments
Create or modify a note associated with this data set.
If the data set has allocated some disk space or tapes, the following will also be displayed:
Release
Release the physical medium (Free the storage space).
If the data set store medium is tape or a disk in SeisUP internal format, the following will also be
displayed:
Edit attributes
Edit and change the attributes: compression, tape density, tape type, reel info.
History Viewer
Displays the the history of a dataset.
For CGM data types the following will also be displayed:
View
View the CGM data set with the CGM previewer
Hard copy
Produce a hard copy from the CGM data set
For modules the following will be displayed:
Parameter
Modify module parameters
Connect...
Connect a module or a data set to another modules input channel
Disconnect
Disconnect the module from a data set or another module. This will not be displayed if the
module is in for execution.
Show Connections
Display status of current channel connections
View Comments
Create or modify a note associated with this module
121
Module Documentation
Display the help file for this module
Execution Status
Display the execution log
Job Progress
For running jobs, display the execution time, each module in the flow and the primary and
secondary ID values last processed by each module.
If the module is currently executing or is waiting for execution, the following will also be displayed:
Exec Type Ahead
Create or modify operator messages that will be sent to the task at a later time
1. Flow editor menus
122
Executing modules
To execute a module or a series of modules:
1. Make sure that all required connections and parameters are set.
2. Select all of the modules that you wish to execute. If you are executing a queue of modules (see
Module types), you must select all of the modules in the queue. That is from the input module, like
SEGYREAD, to last module you wish to execute. If you have multiple data sets connected to the
same channel number, you must also select the data sets. All modules selected for execution must be
connected together by either module to module connections or through data sets. For example, you
cannot execute multiple stand-alone modules that have no data sets connecting them. You must
execute them one after another.
3. Select the host you wish to run the module(s) on. In a multi-host environment, you can select which
computer (host) you wish the program to run on. Each flow has a current host defined for it. The
current host remains in effect until you change it or open another flow that has a different current
host. When you create a line the current host is set to the current host within the currently opened
line. If no line is currently open, the host you signed on to will be used.
4. Execute the modules(s). To run the modules immediately, select Submit Interactive Job from the
Execute menu or click the
menu icon. To add the module(s) to a batch queue for later execution
select Submit Batch Job from the Execute menu or click the
menu icon.
When a module actually starts executing, the status signal will turn yellow. If the module is waiting for
execution at a later time, the status signal will be orange.
When running multiple modules that are connected by a data set, the module writing to the data set must
be finished writing to it before the module reading it can be run. Therefore, the status lights for the
modules connected to the data set will be orange and will be executed after the first set of modules are
finished.
Each time a set of modules are executed, the flow editor assigns a job id to it. A runlog file will be created
for that set of modules (job) and will contain the start date and time, the host id, a list of modules running,
possible module parameter errors, and module print information. At the end of each set of modules that are
executed, a section will be displayed that will list the ending date and time, the CPU elapsed time in
seconds (usr) and the elapsed time for system related functions like read and write (sys). The runlog file
may be viewed by moving the mouse to any module within the job, pressing the right mouse button, and
then selecting Execution status from the pop-up menu.
If an error occurs within the job or the job aborts, the status signal will turn red. For a successful
execution, the status signal will turn green. If a set of modules ran successfully within the job and a later
set of modules aborted, the aborted modules signal will turn red and subsequent sets of modules within the
job will turn to a plain color.
123
Once module(s) are executing or are in queue for execution, you cannot modify the parameters, remove
the module, connect the module, or disconnect the module. You can however move and copy the module.
Batch jobs
If a batch job is submitted and there are no other batch jobs within the line the job will run immediately.
To place more jobs in that queue execute them using the Submit Batch Job icon, or from the Execute
menu. A user may create another batch queue by executing a job with the Submit New Head Batch Job
option, also in the Execute menu. Any subsequent batch jobs will run after the previously submitted job in
its queue finishes. If a batch job aborts, the status signal will turn red, and any subsequently submitted
batch jobs will have a plain signal.
User defined batch jobs

More complex job dependencies can be setup using the Submit User Defined Batch Job... option or click
menu icon.
the
In this case the user has two options. The default is to define one of the jobs currently running or in queue
as the prerequisite job for which the submitted job must wait. The other option is to schedule the job to run
at a later time, perhaps when fewer users are on the system. To do so first click the Schedule job to start in
button, then enter the amount of time the job should wait before executing.
Job monitor
124
Module types
The following module types can be within a flow.
1. Stand alone: Stand alone modules cannot send and receive data to and from other modules.
2. Queue: A queue is a series of modules that begins with an input module and usually ends with an
output module. Currently all queue modules pass GCI format ensembles between modules, but the
number of traces passed is limited by a system defined value. An example of an ensemble would be
shot records, CMP gathers, or 3-D lines.
Executing modules
125
Selecting the current host

The current host is defined as the computer that you wish your modules to run on. To change the current
host:
1. Select Set Execution Host from the Execute menu or press the
menu icon.
2. A dialog will appear with a title of Select Job Server. A list of available hosts will be displayed. Press
the left mouse button on the host you wish to change subsequent module execution to.
3. Press the OK button to apply the selection and remove the dialog. Press the Cancel button to keep
the original current host and remove the dialog.
126
Execute menu
Use the Execute menu to perform the following operations:
Submit Interactive Job
Run selected modules interactively.
Submit Batch Job
Run selected modules in batch.
Submit New Head Batch Job
Submit the modules as the first job in a new job queue.
Submit User Defined Batch Job...
Submit the job to execute after a user specified job.
Submit Dry Run Job
Run only the preprocessing phase of the job (skip the execution phase). Submitting the job as a "Dry
Run" may be used to check parameters.
Abort Job
Abort job associated with the selected modules.
Set Execution Host...
Select the current host to run jobs on.
Set Display...
Change the display environment.
Flow editor menus
127
Flow editor menus

The following menus are available from the menu bar from within the flow editor:
File
Functions to open, close, and create flows
Edit
Functions to perform to icons within the
Find
Search the flow for data sets, modules, or jobs.
Execute
Functions to control execution of modules
Module
View runlog or connections for the selected module.
Options
Functions to control user preferences
Tools
Utilities programs
Within the working area, the flow editor pop-up menu controls module and data set functions such as
connecting, disconnect, and selecting parameters.
128
Edit menu
Use the edit menu to perform the following operations:
Cut
Cut current selection to paste buffer
Copy
Copy current selection to paste buffer
Line copy
Copy current selection to other lines
Duplicate
Duplicate modules with connections intact
Paste
Paste icons from the paste buffer to the flow
Undo
Undo previous operation
Select all
Select all icons in the flow
Group
Group a series of icons to a single icon
Ungroup
Ungroup a group icon into a series of icons
Flow editor menus
129
Find menu
Use the find menu to perform the following operations:
Find Module...
Locate a specified module
Find Dataset...
Select and locate a data set
Find Last Job
Locate the last interactive job executed
Find Last Batch Job
Locate the last batch job executed
Find Job...
Locate modules by a given jobid
Flow editor menus
130
Module menu
Use the module menu to perform the following operations:
Show Runlog...
View the execution status for the job associated with the selected module(s).
Show Connections...
Display the connections for the selected module.
Flow editor menus
131
Tools menu
Use the Utility menu to perform the following operations:
Data Manager
Start the DataManager program in a window.
Job Monitor
Start the job monitor program in a window.
Cluster Maintenance
This is a simple utility for killing remote processes and cleaning up temporary files on a set of clusters.
Line Notepad.
Line notepad always pops up when the user opens any Area/Line. In case user wants to reopen the
notepad to edit or view the note, this tools menu is used.
132
Run flow diagnostic.

This tool menu is used only if a flow file gets corrupted. If there are any corrupted nodes in the flow,
select this option to fix the flow file. A dialog will popup as below:
Click Fix button to fix the corrupted nodes. If no corrupted nodes found, a warning message is shown as
below:
You can click Yes button to force the fix flow. A copy of original flow is saved in the Area/Line.
Note:
User should reopen (Area/Line) after fixing the flow file.
133
Flow editor menus
134
Glossary
Data type
The format of the data accessed by the modules.
Dialog
A window that will reside on top of the application until closed.
Flow editor
Work area for creating and modifying flows
Icon
A graphical object to represent a module or data set within a flow. Icons can also exist within the
X-windows root window that represent executing tasks.
Input channel
The part of a module through which data is received from a previous module or from a data set.
Job
A series of modules in for execution.
Job monitor
A utility to view the job status of a particular host machine.
Matrix editor
An editor for creating and modifying spreadsheets that have dimensions attached to them.
Module librarian
Lists categories of modules available for use.
Module
Performs an algorithmic function on the data passing through it.
Output channel
The part of a modules through which data is passed on to the next module or written to a data set.
Parameter
Options available to modules. Parameters can be of type integer, single precision floating point
(float), double precision floating point (double), and character strings (string).
Spreadsheet
A series of vectors displayed side by side with a corresponding row number.
Vector
An array of numbers or characters. Vectors can be of type integer, single precision floating point,
double precision floating point, or character strings.
Widgets
Buttons, menus, and text fields for changing parameters.
135
Using the matrix editor

The matrix editor is a multi-dimensional spreadsheet program for editing dimensional vector such as
geometry and velocities. The matrix editor shares some basic features with regular spreadsheet software
such as Excel. It is powerful yet very easy to learn and use. The matrix editor has been written under the
idea of being user-friendly. The various warning dialogs will tell the user what you should do or what is
wrong.
The matrix editor may be invoked from within the flow editor by editing module parameters and
modifying a matrix parameter.
The matrix editor works according to the definition of the matrix, like how many dimension variables
there are, its type, and the maximum number of spreadsheets for each dimension, and so on. Vectors
(columns) are also defined in like manner. The user can look at the matrix definition through the help on
matrix definition.
Terms
Current Cell
The area where a row and a column cross is known as a cell. There is only one cell that will receive
keyboard input at any time. This active cell is called the Current Cell. It is always highlighted and is
the starting point for block operations. If the highlighted block contains more than one cell the one
located at the corner of top left is the Current Cell. Use arrow keys or left mouse button to change the
Current Cell.
Block and Paste
A Block is a highlighted area. Use the left mouse button to make a block and make the Current Cell.
A paste buffer is provided for Cut, Copy, and Paste blocks.
The matrix editor works according to the definition of the matrix, like how many dimension variables
there are, its type, and maximum number of spreadsheet on each dimension, and so on. So is the case for
vectors. The user can look at the definition through the help on matrix definition.
Introduction
Parts of the matrix editor
Moving the current cell
Selecting cells
Entering or updating values in a spreadsheet
Creating a new spreadsheet
Saving a spreadsheet
Deleting a spreadsheet
Navigating through spreadsheets
Importing matrix files
Exporting matrix files
Quitting the matrix editor
136
Matrix editor menus
137

The matrix editor consists of the following parts:
1. A menu bar, featuring File, Edit, Tools, and Help.
2. An icon bar on the right hand side, providing a short-cut to the functions in the menu bar.
3. A text entry field located at the top left corner below the menu bar that is used to display or edit the
current cell value.
4. Dimension text entry fields and arrow buttons located at the top right corner below the menu bar to
enter dimension variables. The arrow buttons allow dimension navigation.
5. A work sheet located below the current cell field and the dimension fields, is the working area for
user to edit.
6. A horizontal and a vertical scroll bars to scroll through the work sheet.
7. At the top of each column (vector), a title will be displayed and a default. If there is no default then
that column requires an entry for each row defined. Defaults that are enclosed within double quotes
means that the program reading this matrix will compute a default and the string within the quotes
should indicate a description of the default.
138
File Menu
New Sheet
Create a new spreadsheet.
Save
Save the current spreadsheet.
Import ASCII...
Import an ASCII matrix file.
Export ASCII...
Export to an ASCII file.
Quit Matrix Editor
Quit the Matrix Editor
Matrix editor menus
139
Edit Menu
Use the Edit menu to perform the following operations:
Cut
Cut current selection to paste buffer
Copy
Copy current selection to paste buffer
Paste
Paste from the paste buffer to the spreadsheet.
Clear
Clear selected cells.
Move...
Move current selection to another location.
Clear Sheet
Clear the contents of the current spreadsheet.
Go to Sheet...
Go to a specified spreadsheet
Delete Sheet...
Delete the current spreadsheet
Fill
Fill a column.
Synchronous Fill...
Fill several columns at the same time with the same pattern as that of the base column.
Insert Rows...
Insert rows
Delete Rows...
Delete rows
Go to Row...
Go to a user specified row
Find...
Find the first cell containing a specified value.
Column Width...
Set the width for the currently selected column.
Matrix editor menus
140
Tools Menu
Use the Tools menu to perform the following operations:
Arithmetic
Perform arithmetic on selected values.
Add...
Subtract...
Multiply...
Divide...
Dimension Arithmetic
Perform arithmetic on dimension values.
Add...
Subtract...
Multiply...
Divide...
Sort
Sort a column of values according to the matrix type definition.
Synchronous Sort
Sort several columns at once.
Interpolate
Interpolate values in a column.
Smooth...
Take the running average of a column of values.
Merge Matrices...
Merge the currently opened matrix with another matrix of the same type.
Matrix Editor menus
141

The following functions allow you to move the current cell:
1. Press the cursor keys.
2. On option, scroll through the spreadsheet with the scroll bar or press the page down/page up keys.
Click the left mouse button on the desired cell.
3. Press the Home key to place the current cell at the top left row and column.
4. Press the End key to place the current cell at the bottom right row and column.
5. Press the tab key to place the current cell at the column. When the current cell is at the far right
column, pressing the tab key will result in the current cell being placed at the first column on the next
row.
6. Select Go to Row... from the Edit menu or click the
menu icon. A dialog with a title of Go to
row will appear and will ask for the row number to go to. Click the left mouse button in the text entry
field and enter the row number.
Selecting cells
142
Selecting cells
Before you can perform editing operations such as cut, copy, or move, on cells, you must select them.
To select a cell, click the left mouse button on the desired cell.
To select a range of cells, press the left mouse button on the top left cell to select and drag the mouse. As
the mouse is being dragged the cells selected will become inverse video. Release the mouse button on the
bottom right cell to select.
To extend a block, click the right mouse button on the new bottom right cell to select. You can also press
and drag the right mouse button as described above for a range of cells.
143
Cut, Copy, and Paste

To cut or copy to the paste buffer you must first select a cell or a block of cells.
To cut the cells in a block to the paste buffer, select Cut from the Edit menu or click the
icon.
To copy the cells in a block to the paste buffer, select Copy from the Edit menu or click the
icon.
toolbar
toolbar
To paste the contents of the paste buffer to the spreadsheet, select a starting cell to place the paste buffer
and select Paste from the Edit menu or click the
toolbar icon. Because the paste buffer will remain
intact after a paste action, the paste action can be done repeatedly even between spreadsheets within the
same matrix.
144
Moving Cell Values

To move a block of cell values:
1. Select the range of cells that you wish to move.
2. Select Move... from the Edit menu.
3. Click the left mouse button at the cell corresponding to the desired location for the top left corner of
the selected block of cells.
You can also move cell values by performing a cut and paste operation.
See also the following topic:
145

The following are ways to enter or update a value in a spreadsheet:
1. Type into Current Cell directly. Select a cell to edit and use the keyboard to type in a value for the
current cell. Press the return key or press a cursor keys to store the cell value.
2. Edit in the Text Entry Field. Select a cell to edit. The contents of the current cell will be displayed in
the text entry field. Move the mouse on the top of the text entry field and edit the value. Press the
return key to store the cell value.
3. Cut, Copy and Paste cells
4. Move cell values
5. Fill a Vector
6. Interpolate a vector
7. Arithmetic operations
8. Importing external files
9. Sort a vector
10. Insert rows
11. Deleting rows
12. Erase cell values
Selecting cells
146
Filling Cell Values

To fill a vector with a value or increment a value within a vector, select a cell or a range of cell values to
fill. Select Fill... from the Edit menu or click the
toolbar icon. A dialog will appear with a title of
Fill vector. In the dialog there are three text entry fields as follows:
Initial value
The intended value at the current cell, the default value is that of the current cell.
Step value
The interval value between consecutive cells. The default value is one.
Total rows
The total number of rows to fill. The default is the number of rows selected in the block.
To modify the fields, click the left mouse button in the text field that you wish to modify. Press the OK
button to proceed.
147
Interpolating Cell Values

To interpolate empty cells between defined cells, select a range of cells to interpolate and select
Interpolate from the Tools menu or click the
to vectors of type String.
toolbar icon. The interpolate function does not apply

148
Arithmetic Operations
Arithmetic operations (Add, Subtract, Multiply, and Divide) allow the cells in a highlighted block of a
non-string type vector to be updated by an identical value simultaneously.
To do a Arithmetic operation, select a range of cells to perform to an arithmetic operation to and select the
desired function from the cascaded menu on the Arithmetic item in the Tools menu or click the desired
toolbar icon.
A dialog will appear that will request for a value to perform the arithmetic operation with. Press the left
mouse button in the text entry field and enter the value. Press the OK button to proceed.
149
Sorting cell values

To sort a column and move the corresponding columns:
1. Select a range of cells in the column that you want to base your sort order on. The matrix editor will
only sort the selected rows.
2. Select Sort from the Tools menu or click the
toolbar icon.
3. If the column selected to sort on has a rule that requires increasing order, the sort will be increasing.
If the column selected requires decreasing order, the sort will be decreasing. If the column is neither
increasing nor decreasing, the matrix editor will ask via a dialog if the sort should be in increasing or
decreasing order.
See also the following topic:
150
Inserting Rows
To insert a series of rows:
1. Select the row that will follow the inserted rows.
2. Select Insert Rows... from the Edit menu or click the [IMAGE] toolbar icon.
3. A dialog with a title of Insert rows will appear and ask you for the number of rows to insert. Click the
left mouse button in the text entry field and enter the number of rows you wish to insert. Click the
OK button to proceed.
151
Deleting rows
To delete a series of rows:
1. Select the rows that you wish to delete.
2. Select Delete Rows... from the Edit menu or click the
toolbar icon.
3. A dialog with a title of Delete rows will appear and ask you for the number of rows to delete. The
number of rows highlighted will be the default. If you wish to change the default, click the left mouse
button in the text entry field and enter the number of rows starting from the top left corner of the
selected block of cells that you wish to delete. Click the OK button to proceed.
152
Clearing Cell Values

To clear cell values:
1. Select the cells whose contents you wish to clear.
2. Select Clear from the Edit menu or click the
toolbar icon.

153
Creating a new spreadsheet

To create a new spreadsheet, select New Sheet from the File menu or click the
toolbar icon. If some
changes have been made to the current spreadsheet, a question dialog will pop up to ask whether to save
the changes or discard them. Press the Yes button to save. Press the No button to discard the changes. A
fresh spreadsheet will be the current spreadsheet.
154
Saving a spreadsheet
Select Save from the File menu or click the
toolbar icon. If the spreadsheet cannot be saved, a dialog
will pop up to tell you why. Follow the warnings to make corrections and save again.

155
Deleting a spreadsheet
To delete the currently opened spreadsheet, select Delete Sheet... from the Edit menu or click the
menu icon. A dialog will appear any ask if you are sure. Press the Yes button to delete the spreadsheet and
open the closest spreadsheet or press the No button to cancel the request.
156
Navigating though spreadsheets

If the matrix has dimension variables, a dimension value entry field and a pair of arrow buttons will be
created for each dimension. There are two approaches available for the user to navigate between
spreadsheets within the editing matrix.
One approach is to press the up arrow button to navigate to the next spreadsheet in that dimension and
press the down arrow button to navigate to the previous spreadsheet in that direction. When multiple
dimension variables are involved, the matrix editor will go to the closest spreadsheet in that direction
within a forty-five degree angle.
The other approach is to select the Go to Sheet menu item.
157
Go to Sheet
To go to a specific spreadsheet, select Go to Sheet... in the Edit menu or press the
toolbar icon. A
dialog will appear that will allow the user to navigate through all existent spreadsheets. Select a
spreadsheet to go to and then press the OK button in the dialog. Each item in the scrolled list consists of
dimension values sequentially, separated by + sign.
158
Importing matrix files

To import a matrix from an ASCII file:
1. Select Import ASCII... from the File menu or click the

toolbar icon.
2. A dialog title Import from ASCII file will appear. Select the file from the file selection box. Click the
OK button to proceed.
Export matrix files
Import dialog interaction

At this stage of the import session, the file is read in and ready for import. The import dialog shows
control buttons and the contents of the file.
There are two groups of ASCII files: SeisUP formatted file generated by means of export of the SeisUP
matrix of the same type; Any other ASCII files fall into the second group. (Please note that the first group
requires the same type, that means the definitions of dimensions and vectors are the same.)
1. For the file belonging to the first group, a quick import is provided. Press the button All.
2. The second group covers all ASCII files. Arbitrary import can be done.
Arbitrary import
The basic operation is to copy a block to the spreadsheet. The block will be copied as the data from the
Current Cell and downwards. The data are interpreted according to the type of the current column of the
spreadsheet.
The selection of the block is a little different from that of the spreadsheet.
Press the left button will start a new block, and subsequent release will pick the new block.
Click the middle button inside the block will extend the block downwards to the last line of the showing
file.
Press and release the right button will resize the block from the initial point to the point where the right
button releases.
The following are functions for the buttons available in the import dialog:
159
Go
Copy block to the spreadsheet. The Current Cell is the first row for copy.
Match
Abstract the file according to the highlighted block of the spreadsheet. When doing this the user has
to pick a block as the comparison key. Attention should be paid here that if multiple rows matched
the same key, only the row closest to the end of import file counts.
All
To import a SeisUP formatted file
Dismiss
To finish the import session.
160
Exporting matrix files

To export a matrix in SeisUP format to an ASCII file:
1. Select Export ASCII... from the File menu or click the

toolbar icon. A dialog title of Export to
ASCII file will appear.
2. Enter a file name to export to via the file selection box. Click the OK button to proceed.
3. If multiple spreadsheets exist, an additional dialog will appear to allow you to selectively pick which
spreadsheets to pick.
Import matrix files
161
Picking spreadsheets to export

This is the next step after Export matrix, it provides the user with the options to export the whole or partial
matrix.
1. The highlighted list items are the spreadsheets to export. Use the left mouse button to select/deselect
spreadsheets. The default is to export all spreadsheets of the matrix. Clicking the Clear button will
deselect all items.
2. Click the OK button to proceed to export the selected spreadsheets.
162
Quitting the Matrix Editor

To quit the matrix editor, select Quit Matrix Editor from the File menu or click the
toolbar icon. If
some changes have been made to the current spreadsheet, a question dialog will pop up to ask whether to
save the changes or discard them. Press the Yes button to save. Press the No button to discard the changes.
163
Matrix Editor Menus

The following menus are available from the menu bar from within the Matrix Editor:
File
Functions to create, save, and delete spreadsheets.
Edit
Functions to perform on cells and sheets that are selected within the spreadsheet.
Tools
Functions to perform advanced operations on matrix contents.
164
SeisUP History Viewer

Getting Started
The Menu Bar
The Status Bar
Getting Started.
This program allows the user to view the processing history of a SeisUP dataset using a tree structure. The
tree has four levels: root, processing, module, and parameter. The tree can be expanded or contracted by
clicking the left mouse button on the node icon, seen as an arrow. Alternatively, double clicking any
where along a row will do the same, as well as using the arrow keys located on the keyboard. Use the up
and down arrows to navigate through the expanded nodes or use the left and right arrows to contract or
expand the currently selected node.
The History Viewer is activated by pressing the right mouse button on a dataset icon inside the SeisUP
Flow editor. A list will pop-up that displays several options, including the History Viewer. Click the left
mouse button on the History Viewer option and the program will start executing.
The Application Main Window. See figure 1.

The tree can be expanded or contracted by clicking the node icon with the left mouse button or using the
arrow keys as mentioned above. The icon is just to the left of the node information text. When the program
initially starts up, the root and process levels are visible. To expand a process node, click the icon at the
process to want to expand. If you now click the same icon again, it will contract.
165
Figure 1: A snapshot of the History Viewer.
The viewer has four levels...

The first level is the root level and displays the dataset name. For example Dataset: vibmin as shown in
figure 1. This level controls the processing level nodes.
The second level is the processing nodes . A processing level is defined by a read and then write of a
dataset that contains processing history. Typically, this represents a SeisUP processing run from a READ
to WRITE. The processing nodes control the module level nodes. The processes are listed first to last in
the tree as in the first job run on a child dataset to the last job on this dataset. The processing nodes will be
displayed in blue for easy viewing. On the line will be Queue which represents a SeisUP queued
processing run. The line may also show StandAlone which represents a SeisUP standalone process. The
rest of the line will show the time and date when the process was run, the host computer on which the job
was run, and the process id (pid) of the job. If a processing node is selected, by clicking on its row or by
scrolling to it with the keyboard arrow keys, all of the module names used during that processing run will
be displayed in the status bar, located at the bottom of the application.
The third level is the module nodes. This level shows all the modules that were used during that
processing run. Each module line shows the SeisUP name of the model. If a module node is selected a
brief description of that module will be displayed in the status bar. The module nodes control the
parameter nodes, which are the menu parameters for this module. The module line may also show datasets
that were input or output to this module. Such as: datasets: field:in wavelet:out as shown in figure 1. The
:in depicts an input connection to the module while :out depicts an output connection to the module.
166
The last and final level is the parameter nodes. This level shows all the menu parameters for this module
and the values that the user selected for each parameter. The values will be aligned on the right side of the
window. Alternating menu parameters rows will have a slight different background color so it is easy to
line up the menu parameter with its assigned value.
The Menu Bar. See figure 2.
Figure 2: The menu bar.
The history viewer has three top level menu items...

The File drop down menu has four options...
File -> Save as...
This option allows the user to save the entire history file as text. The text is formatted so that processing
jobs are easily distinguishable from one another. The key command shortcut to activate this option is
ctrl+s.
File -> Print All...
This option will allow the user to print the entire history file. Activating this option will display the usual
Printer Setup window which will allow the user to select different printers, print the history information
to a postscript file, or make several copies. The key command shortcut to activate this option is ctrl+p.
File -> Print Open...

This option allows the user to print only the history information which is expanded in the application. The
nodes that are collapsed ( not visible ) will not be sent to the printer. The user has control over which
information get sent to the printer by just selecting what text is expanded and what text is collapsed. The
text will be formatted so that levels of the tree structure are represented. As with the Print All option, a
separate window will be displayed which will help the user select their printing options. The key
command shortcut to activate this option is ctrl+o.
File -> Exit

This option terminates the History Viewer application. The key command shortcut to activate this option
is ctrl+q.
167
The View drop down menu has only two options...

View-> Expand All
The user can expand the whole tree by activating this option. This is a convenient method to expand the
whole processing history. The key command shortcut to activate this option is ctrl+down arrow.
View-> Collapse All
The user can collapse the tree down the the job processing level by activating this option. This is a
convenient method to collapse the whole processing history. The key command shortcut to activate this
option is ctrl+right arrow.
The Help drop down menu has two options...
Help-> About
This option displays the about box which provides the user with general information about the application.
The key command shortcut to activate this option is ctrl+a.
Help-> Help
The Help option displays this document. The key command shortcut to activate this option is ctrl+h.
The Status Bar. See figure 3.

The status bar is located at the very bottom of the application window and contains two fields. The text
displayed on the right side will not change throughout the execution of the program. The dataset name and
the number of processing jobs pertaining to that dataset will be shown in that right side field. On the left
side however, the text displayed will change with respect to the currently selected node. If a job processing
row is selected a list of the module names used during that processing run will be displayed. Alternatively,
if a module name is selected a brief description of that module will be displayed. For example (from figure
3), the status bar is showing the description of the module whos name is UNDUPE.
Figure 3: The status bar.

Save As... ctrl+s
Print All... ctrl+p
Print Open... ctrl+o
Exit... ctrl+q
Expand All... ctrl+down arrow
168
Collapse All... ctrl+right arrow

About... ctrl+a
Help... ctrl+h
169
SeisUP Job Monitor

Getting Started
The Hosts Window
The Menu Bar and Toolbar
Replying to Jobs
TroubleShooting
Getting Started.
When the Job Monitor application starts the user will typically be prompted with the Hosts Window (see
figure 1). Here the user will choose a host for which the application will view and interact with resident
jobs. The Job Monitor application will display the jobs currently running, or recently exited on the host.
The user may kill, suspend, or even set the priority for a running job, as well as view its run log.
Suspended jobs may be resumed, and jobs waiting for user input may be responded to. At any time the
user may switch the active host to view jobs running on a different machine.
The Hosts Window.

The Hosts Window contains a list of hosts for which a user may want to monitor job activity. Once a user
has selected a host from the list, the connect button is used to trigger the host switch. Host names may be
added or removed by using the "plus" and "minus" buttons respectively. A default host may be set so that
the application will start without asking the user to choose a host. However, this option must be selected in
the applications preferences.
170
Figure 1: The Hosts Window.
The Application Main Window.

The Main Window contains a list of jobs which are currently active on the host, or were recently killed but
have not yet been removed. Although the user may choose from 16 possible columns to display, there are
5 important columns that may not be removed:
Project: The area and line from which the job was started.
Owner: The user that most recently changed the the jobs execution state.
JobID: Value used to identify the job. Interactive jobs will have positive numbers, while batch jobs will
have negative numbers.
ProcessID: Another value used to identify the job, this one provided by the operating system.
State: Short description of the jobs current state.
Two other columns of note are the "Message" column, used to display any outstanding messages or
questions from the job, and the "Prerequisite JobID" column. The user is encouraged to add and remove
columns based on what job information is most important to them. To do this click on the "View" menu
button, then select "Options", or use the keyboard shortcut ctrl+o.
171
Figure 2: The Main Window.
The Menu Bar and Toolbar.
Figure 3: The Menu Bar And Toolbar.
The Job Monitor application has a menu bar and a toolbar containing important options. If an option is not
available for the currently selected job it will appear vague (see the Resume and Clear icons in figures
2 and 3).
The Job Monitor has four top level menu items...
The File drop down menu has five options...
File -> Hosts...
This option opens the Hosts Window seen in figure 1 and described above.
172
File -> Manual Reply...

This option should rarely be used. In the case that a job has lost communication with the job server
(maybe because the job server was rebooted) use this option to send a reply message. Because the job is
"lost" the user will need to get all of the job information from the "execution status log" via the flow
editor. To create a reply message the user will need the Job ID, Process ID, Host, Area and Line associated
with the "lost" job. All of this information, along with the actual question from the job that needs to be
answered should be in the execution status log.
File -> Get Info...
This option will display a complete listing of the information the application has for the selected job. That
information includes: Job ID, Process ID, Prerequisite Job ID, Project, State, Priority, Start Time, End
Time, Executable Name, Executable Host, SeisUP Directory, User Name, User ID, Group Name, Group
ID, and Message.
File -> Preferences...
This option will bring up the preferences window where the user may customize some of the applications
functionality.
File -> Quit
Terminates the application.
The View drop down menu has six options...
View -> Job Server Log...
This option will display the job servers log file in a separate window.
View -> Run Log...
This option will display the currently selected jobs run log file in a separate window. This file usually
contains detailed information about the jobs execution history.
View -> Clear Job
This option removes the selected job from the list. Only exited jobs may be removed.
View -> Clear All
This option will remove every exited job from the list.
View -> Only My Jobs
This option will remove all the jobs that do not belong to the current user from the list.
View -> Options...
This option allows the user to choose which columns are displayed in the applications main window.
The Job drop down menu has five options...
Job -> Reply to Message...
When a job requires operator intervention, the job will request for a response to a question, displayed in
the "Message" column, via any running job monitors. This option allows the user to respond to the job.
See the Replying to Jobs section of document for more information.
Job -> Set Priority...
Use this option to change the priority of the selected job. Typically when a job starts it is given the
maximum priority(0). The user may lower that priority to a minimum(20) so other, more important, jobs
will have access to system resources.
Job -> Kill
173
This option will stop the selected job and the job listing will be updated accordingly.
Job -> Suspend
This option will suspend the selected running job and the job listing will be updated accordingly.
Job -> Resume
This option will resume the selected suspended job and update the job listing accordingly.
The Help drop down menu has two options...
Help-> About
This option displays the about box which provides the user with general information about the application.
Help-> Help
This option displays this document.
Replying to Jobs
This function is used to reply to jobs waiting for a response. It also displays common responses as well as
tape drives installed on the system. In figure 4 below Job 1747 is ready to mount an input tape for I/O and
is asking for a unit number and host name. The reply field is filled in as, "124 godzilla". Once the user hits
the "Reply" button Job 1747 will receive the answer message and proceed.
174
Figure 4: The Reply to Message Window.
The following are the explanations of the response messages:

1. (a/c) abort/continue
2. (a/c/n) abort/continue/next
3. (s/c/a) same/continue/abort
4. (y/n) yes/no
5. (s/a) same/abort
6. (p/s/n/a/q) previous/same/next/abort/quit
7. (p/s/n/c/a/i) previous/same/next/continue/abort/ignore
8. (p/s/n/c/a) previous/same/next/continue/abort
For 3-D data, if the shot matrix name is in the header and GEOM cannot find the name in the database the
following message will appear at the jobmonitor:
1. Cannot find LINE: #### ID: #### CHAN: ### in db, reply (q/a/st/sl/line) The allowable responses are
as follows:
2. q Stop sending data to the next process and quit the program.
3. a Abort immediately.
4. st Skip the trace.
5. sl Skip the line.
6. line Enter the shot matrix name in the geometry db in place of "line". For example to respond with the
line "100", simply respond with "100" not "line 100".

Preferences... ctrl+f
Quit ctrl+q
Options... ctrl+o
Only My Jobs ctrl+shift+m
Job Server Log... ctrl+l
Run Log... ctrl+v
Clear Job ctrl+x
Clear All ctrl+a
Reply to Message... ctrl+m
Manual Reply... ctrl+e
Set Priority... ctrl+p
Kill ctrl+k
Suspend ctrl+s
Resume ctrl+r
Job Info... ctrl+i
About... ctrl+a
Job Monitor Help... ctrl+h
175
TroubleShooting
General Tips:
For the Job Monitor application to run properly it must be monitoring a host running the SeisUP Job
Server.
Copyright 2013, GeoCenter LP. All rights reserved. SeisUP is a registered trademark of
GeoCenter LP.
176
Documentation > Applications > seisupd >
SeisUP Job Server Administration Manual

Contents
Overview
Running seisupd
Server Status Reports
Files
Environment Variables
Signals
Configuring seisupd
Command-line Utilities
Troubleshooting
Appendix A: Changes from jmserv
Overview
SeisUP is a multi-tiered system where a number of programs and applications collaborate to configure,
execute, and manage processing jobs. The three primary components of SeisUP are the Flow Editor
(geodraw), the job server (seisupd), and the job executive (jobexec). The Flow Editor is the main user
interface in which users design and parameterize processing workflows. From the Flow Editor users
submit workflows to the job server as job execution requests. Upon receipt of job requests the job server
spawns instances of the job executive, which contains that actual processing subroutines represented by
the workflow.
Before executing jobs seisupd checks that a license is available to run the job, and if the job has any
prerequisite jobs that must complete before running (batch submission mode). If a job cant be run for
some reason, such as resource availability, then seisupd will put it into a queue. As jobs exit and resources
become available, job requests are taken from the submission queue and executed.
One of the most critical functions of the job server is to monitor the status of job processes that it spawned.
In the Unix vernacular the job server is called the parent process, and each job is referred to as a child
process. As children processes finish executing and exit the parent is notified of the exit status of each
those children. When a job exits the job server takes the exit status of the job and relays it to all instances
of the Flow Editor as a job status notification. A job status notification contains identifying information
for the job, its exit status, and timestamps for the jobs submission, execution, and completion times.
For those interested in technical details, job requests are sent to the job server using TCP/IP. The job
server has a socket that is listening for these TCP/IP job requests on port number 7755. Job status
notifications use a different communications channel. They are transmitted as UDP packets to a multicast
group. Mulitcasting is a low-overhead technique for sending out information to anyone who is interested
in receiving the information. When the Flow Editor starts it joins this multicast group and listens for job
notifications. The beauty of mulitcasting is that any number of job servers can send notifications to the
177
multicast group, and any number of applications can join the multicast group to receive these notifications.
All of this transpires without the job server knowing anything about the listening Flow Editors, and
vice-versa.
One application we havent mentioned yet is the JobMonitor. This is a graphical application that gives the
user a view on the inner workings of the job server. The main user interface is a table of all jobs under
management by the monitored job server. Users can view job run logs and information about the job such
as the owner, submission time, process ID, and more. The JobMonitor receives updates on jobs through
the same mechanism as the Flow Editor, that is by joining the job status notification multicast group.
In addition to inspecting jobs users can manage jobs through the JobMonitor. Using the JobMonitor
interface you can send management requests to the job server to abort jobs, suspend and resume execution
of running jobs, and change the execution priority of running jobs. For more information on the
JobMonitor see the JobMonitor documentation.
Sending Feedback
If you experience problems with seisupd, or wish to send feature suggestions or other general feedback,
please contact us at feedback@geocenter.com.
Running seisupd
The job server control script can be found at /etc/init.d/seisupd. To execute this script you must be logged
in as the root user. The script has a number of commands to control seisupd:
start
This will start seisupd if it is not already running.
stop
Stop a running instance of seisupd by sending the process a TERM signal (15).
restart
Stop a running instance of seisupd and then start it again.
status
Send an USR1 signal to the job server process, causing it to dump a status report to its log file. See
the section Server Status Reports for more information.
debug
This starts seisupd in a GDB session for debugging. If you would like to use a debugger other than
GDB, you will have to edit the /etc/init.d/seisupd script.
Stopping and Restarting seisupd

The job servers responsibility is to spawn job executive processes in response to job submissions from the
main SeisUP user interface. All jobs started by seisupd are child processes to the job server process. This
relationship allows seisupd to receive signals when child jobs exit that are relayed as job status
notifications to the Flow Editor. The Flow Editor in turn updates modules status indicators in response to
job notifications broadcast by the job server.
178
If seisupd is stopped then any jobs that were started by that instance of seisupd are orphaned, since their
parent no longer exists. This presents a problem since there is now no way to communicate information
about the exit status of an orphaned job to the Flow Editor, and the status lights of the job modules will
only display the last known status of the job. Starting a new job server will not solve this problem because
a process can not claim orphaned children as its own children. Note that a jobs run log will always show
the correct status for a job regardless of the state of the jobs managing job server. This poses a
complication to users if an administrator wishes to restart a job server since restarting the job server will
disable the primary means of communicating job state to a user.
To solve this problem when seisupd is instructed to terminate (either by using the kill -TERM
command, or through any of the seisupd control scripts) it goes into a scheduled shutdown state. In this
state the job server will continue to run until all of its child jobs have exited. This provides the needed
communications channel so that the Flow Editor interface can continue to faithfully show the state of
running jobs. Once the last child job has exited seisupd will automatically exit.
The thing to note about how scheduled shutdown works is that while the job server is still running and
managing its children, all of its network services have been stopped. This means that it is no longer
available for receiving new job submissions. If a user attempts to submit a job he will be notified that no
job server is running. However, because all of the server sockets have been closed in this state, a new job
server can be started to take over the role of receiving new job submissions. In effect, two instances of
seisupd will be running side-by-side: the first exists solely to catch the exit status of its children and send
the notification out, while the second exists to allow new job submissions.
If you desire to stop an instance of seisupd altogether, you can send an interrupt signal using the command
kill -INT. This will cause the job server to gracefully exit. If all else fails, you can shutdown seisupd
using kill -9, which will stop it dead in its tracks. Note that if you stop seisupd using either of these
methods the Flow Editor will not receive completion notifications for jobs that were running at the time
you killed the job server.
If you do find yourself in the situation where you know a job has completed (because the run log says so)
but the status lights show otherwise you can select the flow and use the Execute->Abort Job command
from the Flow Editor.
Server Status Reports

seisupd can dump a status report to its log by sending it a USR1 signal. This can be done by using the
status command in the seisupd init script, or by using the kill program, as shown here:
% kill -USR1 cat /var/run/seisupd.pid
Dumping the status to the message log produces output like the following:
******************************************************
*
Job Server Status Report
*
******************************************************
Thu Dec 9 15:53:17 2004
Server has been up 10 days, 04:14
3 jobs running
0 interactive jobs waiting to run
179
0 batch jobs waiting to run

Job Statistics
------------------------------------------------------Submitted: 261 (20)
Rejected: 0 (0)
Executed: 178 (10)
Exited normally: 3 (0)
Exited abnormally: 15 (0)
Aborted by signal: 157 (12)
Job Terminations by Signal
------------------------------------------------------9 (Killed): 2
11 (Segmentation Fault): 2
15 (Terminated): 153
Messages Waiting for Responses

------------------------------------------------------test/3D/1339: jobexec running
test/3D/1: jobexec running
test/3D/4: jobexec running
Every status report starts out with a timestamp of when the report was generated, and a report of the
current uptime for the server. In the top section we get a summary report of the number of jobs that are
being managed by the job server. We see the number of running jobs, as well as the number of interactive
and batch jobs waiting in queue. Next we see some historical job information that shows how many jobs
have been submitted and executed. We also see a breakdown of how jobs completed: whether they exited
successfully, unsuccessfully, or otherwise failed. The numbers in parentheses show the change since the
last status report. For example, in the example above we see that 20 jobs have been submitted since the
last time we dumped a status report.
Next we see a breakdown of job terminations by signal. In the example nine jobs were terminated with a
KILL signal (which are explicitly sent to processes by a user using the kill command), two jobs failed as a
result of a segmentation violation (SEGV), and 153 exited as a result of a TERM signal. Note that signal 15
is the default signal of the kill command, and it is also the mechanism used to terminate running jobs when
the user uses the job abort command in the Flow Editor. This explains the high number of signal 15
terminations.
The last part of the status report is a list of execution messages that are awaiting responses from users.
Many jobs will send messages to the job server that are broadcast to listening job monitors for users to
observe and respond to. Common execution messages include messages about tape changes and tape I/O
errors. If a message is unanswered, you will see it listed in the status report in this section. See the
JobMonitor Users Guide for more information.
180
Using telnet to Check the Server

telnet can be used to quickly check the status of an instance of seisupd. The following example shows
how we check to see if seisupd is running on the host named southpark:
% telnet southpark 7754
Trying 192.168.254.198...
Connected to southpark.
Escape character is ^].
seisupd v1.0 (Thu Mar 17 14:26:16 CST 2005)
Connection closed by foreign host.
Files
seisupd works with and creates a number of files during the course of execution. In this section we will
describe which files belong to seisupd, and what their function is. Many files exist within the SeisUP
directory structure, and theyre path is specified relative to the root of the SeisUP installation, represented
by the environment variable $QEDTOP.
In this section we will describe the function of the following files:
/etc/init.d/seisupd
/var/spool/seisupd_job_cache
$QEDTOP/usr/Area/Line/job_cache
/tmp/seisupd-{exec-pid}
/tmp/seisupd
/etc/init.d/seisupd
This is the seisupd init script used to start and stop the job server. The commands of this script are
discussed above in the section Running seisupd.
When SeisUP is installed links are created by the installer various runtime configuration directories to this
init script. On Linux platforms and Mac OS X the runtime configuration links are created by the chkconfig
utility, which is invoked by the installer as:
chkconfig --add seisupd
For more information see the chkconfig Unix man page.

On IRIX and Solaris the seisupd installer creates the following links to /etc/init.d/seisupd:
/etc/rc0.d/K02seisupd
/etc/rc2.d/S99seisupd
181
$QEDTOP/etc/seisupd.conf
This is the configuration file for the seisupd daemon. In it you will find a number of directives for
customizing and tuning the behavior of seisupd. For more information see the section Configuring
seisupd.
This is the seisupd execution log where all messages are output. The job server outputs information about
jobs as they are submitted, queued, executed, and completed. Any server errors are output to this log as
well. Each log entry has a time stamp and a severity. The severity is one of the following, beginning with
the most critical:
FATAL
WARNING
NOTICE
USR1
DEBUG
TRACE
By default seisupd outputs messages that are at the USR1 level or higher. You can configure seisupd to
output fewer or more messages by setting the SEISUP_LOG_LEVEL environment variable in the seisupd
startup script found in /etc/init.d/seisupd. For example, to have debugging information output to the log,
add the following line to /etc/init.d/seisupd:
SEISUP_LOG_LEVEL=DEBUG
export SEISUP_LOG_LEVEL
You should be careful not to set the log level below USR1, as most seisupd logging about job activity and
status occurs at the USR1 level.
This file contains the process ID of the current seisupd instance. When the server daemon launches it
checks to see if this file exists. If the pid file does exist seisupd exits under the assumption that the file
represents an already-running instance of seisupd. In other words, seisupd is setup to run one and only one
instance of itself. If you find that seisupd wont start and you know there isnt an instance already running,
check to make sure that this file isnt present and blocking startup.
/var/spool/seisupd_job_cache
This is the global job cache. The job cache is a binary file that contains job data structures for each of the
jobs currently being managed by the job server. This includes jobs that are waiting in queue and executing.
When a job exits its corresponding data structure is removed from the global job cache and added to the
project job cache, which is described below.
182
The command-line utility dump_job_cache can be used to print the contents of a job cache file. This
program is found in the directory $QEDTOP/bin/$QSYS/admin.
$QEDTOP/usr/Area/Line/job_cache
This file is the project job cache, which exists for each project. This cache contains the binary data
structures for each job that was run in the project. The Flow Editor uses this cache to update the status
information of modules in the job flow user interface. It is deleted by the flow editor when a project is
opened.
The command-line utility dump_job_cache can be used to print the contents of a job cache file. This
program is found in the directory $QEDTOP/bin/$QSYS/admin.
/tmp/seisupd-{exec-pid}
This is a temporary local Unix domain socket created by running job executives that are sending execution
messages to the job server.
/tmp/seisupd
This is a local Unix domain socket that seisupd opens for the local messaging service. seisupd listens on
this socket for messages from job executives.
Environment Variables
QEDTOP
This is the standard SeisUP environment variable that specifies the base directory of the active SeisUP
installation.
QSYS
This is the SeisUP platform identifier which is set by the seisupd init script. You should not ever need to
change this.
SEISUP_LOG_LEVEL
This sets the level of logging for the server, which allows you to control the amount of information output
by seisupd. See the description of /var/log/seisupd.log for more information.
SEISUPD_DEBUG
Defining this environment variable has the same effect as specifying the -debug command-line option.
This prevents seisupd from daemonizing itself at startup, and causes all messages to be printed to stdout
instead of the server log.
183
SEISUPD_CONF_PATH
This environment variable is used to specify an alternate job server configuration files. The default
location is $QEDTOP/etc/seisupd.conf. An alternate configuration file can also be specified using the
-conf command-line option.
Signals
seisupd implements special handlers for a number of standard signals, which are documented in this
section. Any of these signals can be sent to the seisupd process using the kill command. If you are not the
owner of the job server process, then you must be the superuser to send a signal to seisupd.
SIGTERM
The SIGTERM signal is used to initiate a scheduled shutdown of seisupd. When seisupd is put into
the scheduled shutdown state all seisupd network services are stopped, but the process does not
terminate until all of the jobs under control of the seisupd process terminate. For more information
see the section Running seisupd.
SIGINT
Sending a SIGINT (interrupt) signal to seisupd will cause the job server to shutdown and exit
gracefully. Unlike SIGTERM, SIGINT will shutdown seisupd immediately without waiting for
managed jobs to exit.
SIGHUP
Sending a HUP signal will cause seisupd to reread the configuration file and restart all networking
services. This involves closing all listening sockets, and then reopening them as if seisupd were being
restarted.
SIGUSR1
When seisup receives a USR1 signal it will dump a status report to the server log. See Server Status
Reports above for more information.
SIGUSR2
This causes seisupd to enable or disable its administrative IPC service. This allows a user to use the
seisupd_admin command-line utility to perform administrative tasks. When seisupd is launched, the
administrative IPC service is disabled. Sending a SIGUSR2 will enable it. Sending this signal when
the service is running will stop the service. For more information about what you can do with the
administration service, see the section on seisupd_admin.
Configuring seisupd
Many properties of the job server can be configured through the seisupd configuration file located at
$QEDTOP/etc/seisupd.conf. Parameters are specified by directives that specify key-value pairs which are
separated by white space. The key is the parameter name, and the value is the setting for the parameter.
This section documents the directive keys that are recognized by seisupd.
GlobalJobCache
This is the location of the global job cache file, specified as an absolute path. The default is
/var/spool/seisupd_job_cache.
184
Listen
This is the address on which the seisupd job management service binds to and listens for new job
submissions and server requests. By default seisupd binds to all addresses on the host.
LogFile
This is the path to the seisupd log file. The default value of this setting is /var/log/seisupd.log.
MaxBatchExecJobs
This is the maximum number of batch jobs that may concurrently execute.
MaxInteractiveExecJobs
This is the maximum number of interactive jobs that may concurrently execute.
MessageResendPeriod
This is the number of seconds seisupd waits before rebroadcasting an executive message that has not
received a response.
MulticastAddress
This is the IP address that seisupd sends multicast job and message notifications out on. The default
value is 7757.
MulticastPort
This is the port number that seisupd sends multicast job and message notifications out on. The default
value is 7757.
PidFile
This is the path to the process ID file that contains the process ID of the current seisupd instance. You
should not need to change this, but if you do be sure to update /etc/init.d/seisupd to point to the new
location of the PID file.
Port
This is the port on which the seisupd job management service binds to and listens for new job
submissions and server requests.
Using Alternate Configurations

seisupd provides two mechanisms for specifying alternate configuration files. This is useful if you want to
run two unique job server instances. You can specify an alternate configuration using the -conf
command-line option when starting seisupd. You can also specify the path to a configuration file by
setting the SEISUPD_CONF_PATH environment variable. If a path is specified in
SEISUPD_CONF_PATH and in the -conf command-line option, the path specified on the command-line
will override the environment variable.
Included in the SeisUP installation are a number of command-line utilities that can be used to monitor the
status of seisupd and obtain other types of information. In this section the following utilities are described:
dump_job_cache
seisupd_ctl
seisupd_install
185
dump_job_cache
This program will print the contents of a job cache file to standard output. seisupd maintains two types of
job caches: the project cache and the global cache. The locations of these cache files is described above.
The command if found in $QEDTOP/bin/$QSYS/admin. The only argument it takes is the path to the job
cache to dump. The following is an example of its usage, as well as what you can expect to see in the
output:
% cd $QEDTOP/usr/test/3D
% dump_job_cache job_cache
JMJobRef (0x1800a00) = {
User: mike:staff (uid = 516, gid = 20)
Display: southpark.local:0.0
Exec. Host: southpark
Exec. Name: jobexec-test
Process ID: 7503
State: JMStateExitSuccess
SeisUP Dir: /opt/seisup
Area: test
Line: 3D
Flow File: /opt/seisup/usr/test/3D/flow
Run Log: /opt/seisup/usr/test/3D/run_logs/job_1323.runlog
Node ID: 1523
Job ID: 1323 (Interactive execution mode)
Submit Time: Thu Dec 9 23:53:53 2004
Start Time: Thu Dec 9 23:53:53 2004
End Time: Thu Dec 9 23:54:03 2004
}
This example shows only a single job in the project cache for project test/3D. JMJobRef
(0x1800a00) in the first line refers to the internal data structure type and address in memory for the job
data structure. The other fields display information about the job such as the process ID, state, and time
stamps for when the job was submitted, executed, and when it exited. For each job in a cache
dump_job_cache produces a similar listing.
This program, found in $QEDTOP/bin/$QSYS/admin, does nothing more than monitor the seisupd
multicast group for job status notifications and exec notifications. When a notification is received it is
printed to standard output. To stop monitoring press Ctrl-C.
seisupd_ctl
This script is a wrapper around /etc/init.d/seisupd. It takes the same commands as described in the section
Running seisupd.
186
seisupd_install
This is the seisupd installer, which is invoked by the main SeisUP installer during installation. You should
not ever need to use this script. It does, however, have a feature that may be of interest to some users. You
can use this script to uninstall seisupd from a system, which involves deleting all seisupd initialization
files described in the section Files. To invoke the uninstaller, simply pass the --uninstall
command-line options:
% seisupd_install --uninstall
Note that you must have superuser privileges to execute this script.
Troubleshooting
seisupd reports that it is running when in fact it isnt.
When starting seisupd you may get a message similar to the following:
% seisupd_ctl start
seisupd already running! PID: 25183
If you receive this error message when you know that seisupd is not running, delete the file
/var/run/seisupd.pid. This file can get left behind when seisupd does not shut down cleanly. You can
check for a running instance of the job server using the following command, substituting in the process ID
reported in the error message:
% ps -ef | grep 25183
Appendix A: Changes from jmserv

Prior to SeisUP 2005 jmserv was the name of the job server. seisupd, which is a reimplementation of the
job server, replace jmserv. jmserv was supported by a number of data and configuration files within the
SeisUP installation directory in the directory QEDTOP/jm. SeisUP 2005 no longer requires the directory
to exist, and as a result files and programs previously found in that directory have been moved and
renamed to other locations. In this section we document where to find these new files.
187
SeisUP system configuration files and management tools: before and after SeisUP 2005 (all paths are
relative to $QEDTOP).
Before SeisUP 2005
SeisUP 2005 and Later
Description
/jm/hostname/jmserv
/bin/$QSYS/seisupd
The SeisUP job server executable. plotting
/jm/hostname/tapeserv
/bin/$QSYS/tapeserv
The SeisUP tape server executable.
/jm/hostname/disks.dat
/etc/filesystems
This file contains the paths to filesystems

used by SeisUP for data storage.
/jm/hostname/tapes.dat
/etc/tape_devices
Tape device database that contains

information about tape devices available
to SeisUP applications.
/jm/hostname/startjm,
stopjm
/bin/$QSYS/admin/seisupd_ctl
The seisupd_ctl script is a one-stop shop

for starting, stopping and restarting the
seisupd job server. It is actually a wrapper
around the startup script found in
/etc/init.d/seisupd.
/jm/hostname/JMlog
The job server log file.
188
SeisUP Licensing Guide

Contents
Overview
Features
One vs. Many Licensed Machines
Running lmgrd
Files
Troubleshooting
Appendix A: License Categories
Overview
Beginning with the release in 2005, SeisUP will use a popular third party software package provided by
Macrovision Corporation to implement license security. This software allows for a greater range of
licensing flexibility. Now SeisUP may be installed to run only a portion of the several hundred modules in
its processing library, or be restricted by the number of concurrently running jobs.
The major difference between the licensing scheme of this version of SeisUP and versions pre 2005 is that
the burden of severing licenses has been moved out of SeisUP and into FlexNETs license server manager:
lmgrd which is located in the SeisUP installation at $QEDTOP/bin/$QSYS/admin/lmgrd. The license
server manager along with the license vendor daemon: seisup comprise the license server system. Please
be careful not to confuse the license vendor daemon, located at $QEDTOP/bin/$QSYS/admin/seisup
with the seisup script used to start the flow editor, located at $QEDTOP/bin/$QSYS/seisup.
The FlexNET licensing software used by SeisUP is highly configurable, so after reading about the default
installation below the FlexNET licensing End User Guide should be used as a more in-depth reference.
Sending Feedback
If you experience problems with SeisUPs licensing system, or wish to send feature suggestions or other
general feedback, please contact us at feedback@geocenter.com.
Features
All installations of SeisUP will have a license to run a set of "core" modules, however many of the
modules in SeisUP belong to a specific license category. For instance, to run the modules KTMIG or
DMO3D a "timemigration" license is required.
A SeisUP license may be purchased to restrict the number of SeisUP jobs concurrently running on the host
machine. In this case the license server manager will keep track of how many jobs are running, when the
maximum is reached no more jobs can be started on that machine until one or more finish.
189
Several modules in SeisUP can spawn many executables to be run in parallel on a cluster or SMP
machine. These modules require cluster node licenses. For each child process spawned by the master job a
request will be made for a cluster node license. This request will only be successful if the requesting node
already has a license checked out or the license server has a cluster node license available (i.e. they are not
all checked out). It is also required that the requesting node have the correct number of CPUs, meaning a
machine with eight CPUs will fail to receive a cluster node license if all you have are licenses for nodes
with 2 CPUs.
One vs. Many Licensed Machines

If you are licensed to run SeisUP on more than one machine the license scheme will define one as the
alpha host, while the others will be considered non-alpha. The license file on the alpha host,
$QEDTOP/etc/seisuplocal.lic, will contain licenses for all of the hosts (and clusters), while this file on the
non-alpha hosts will contain license information for itself only. In addition each non-alpha host will
contain a copy of the alpha machines license file at $QEDTOP/etc/seisupalpha.lic.
Each host will run the license server, however during normal execution all license requests are handled by
license server on the alpha host. If the license sever on the alpha host goes down each non-alpha machine
will rely on its local license server. Notice that all requests for cluster node licenses will fail because they
are served only by the alpha host.
Running lmgrd
The license manager control script can be found at /etc/init.d/seisup_lmgrd. During the installation process
this file should have been modified to set the QEDTOP and the lmgrd_user variables. The script will start
the license manager under the user name defined by lmgrd_user. FlexNET strongly recommends the
lmgrd_user running the license manager not be a superuser. However, you should be logged in as the root
user when running the seisup_lmgrd script with the following commands:
start
This will start lmgrd if it is not already running. A status file is created at
$QEDTOP/lib/log/lmgrdboot.log which should record any problems during the startup. If the
following is displayed in the terminal during execution of the start command it can be ignored,
"nohup: appending output to nohup.out". A license server log is also created to record the on going
status of licenses served by that instance of lmgrd, located at $QEDTOP/lib/log/licensedaemon.log.
stop
Stop a running instance of lmgrd.
restart
Stop a running instance of lmgrd and then start it again.
status
Display the status of the license server and the licenses it is currently serving.
190
Files
lmgrd works with and creates a number of files during the course of execution. In this section we will
describe which files belong to lmgrd, and what their function is. Many files exist within the SeisUP
directory structure, and their path is specified relative to the root of the SeisUP installation, represented by
the environment variable $QEDTOP.
In this section we will describe the function of the following files:
/etc/init.d/seisup_lmgrd
$QEDTOP/lib/log/lmgrdboot.log
$QEDTOP/lib/log/licensedaemon.log
$QEDTOP/bin/$QSYS/admin/lmutil
$QEDTOP/etc/seisuplocal.lic
$QEDTOP/etc/seisupalpha.lic
$QEDTOP/bin/$QSYS/admin/seisup
/etc/init.d/seisup_lmgrd
This is the lmgrd init script used to start and stop the license manager. The commands of this script are
discussed above in the section Running lmgrd.
When SeisUP is installed links are created by the installer in various runtime configuration directories to
this init script. On Linux platforms and Mac OS X the runtime configuration links are created by the
chkconfig utility, which is invoked by the installer as:
chkconfig --add seisup_lmgrd
For more information see the chkconfig Unix man page.

On IRIX and Solaris the lmgrd installer creates the following links to /etc/init.d/seisup_lmgrd:
/etc/rc0.d/K02seisup_lmgrd
/etc/rc2.d/S99seisup_lmgrd
NOTE: On HP the seisup_lmgrd script as well as the above links are placed within the /sbin directory.
$QEDTOP/lib/log/lmgrdboot.log
This log file records any status output from the startup of the license manager.
$QEDTOP/lib/log/licensedaemon.log
This log file records the on going status of the license manager including the status of currently checked
out licenses as well as reports of failed license requests.
191
$QEDTOP/bin/$QSYS/admin/lmutil
This executable is used by the license manager init script to stop, restart and show the status of the license
manager.
$QEDTOP/etc/seisuplocal.lic
The contents of this file defines what licenses should be made available by the license server running on
the local machine.
$QEDTOP/etc/seisupalpha.lic
The contents of this file defines what licenses are available for every machine on the network running
SeisUP. Typically, this file will not exist on the alpha host.
$QEDTOP/bin/$QSYS/admin/seisup
This is the license vendor daemon that along with the license server manager, lmgrd, comprise the license
server system. Essentially, the license vendor daemon, seisup, communicates the SeisUP specific license
information to the universal license server manager, lmgrd. Because the license server manager is
universal you may run only one instance of lmgrd to server several different license vendor daemons (see
FlexNETs End User Guide for configuration options).
Troubleshooting
You are getting an error message saying the license sever is down.
First make sure the license server manager,lmgrd, and the license vendor daemon, seisup are running
without error or warning. Use the following command to make sure lmgrd and seisup are running:
% ps -ef | grep seisuplocal.lic
If either the license server manager or license vendor daemon are not running use the lmgrd control script
to start them. If the control script fails to start then view the lmgrd boot log located at
$QEDTOP/lib/log/lmgrdboot.log. If any errors appear in the log, consider resolving them using the
Licensing End User Guide as a reference.
You are getting an error message saying you could not obtain a license
for a certain feature.
There are several reasons a user may get this error. Gathering information about the error is important so
look in the license server managers log file at $QEDTOP/lib/log/licensedaemon.log. Remember that if you
have multiple machines running SeisUP, the alpha machine should be serving licenses to the others so
look in the licensedaemon.log file on the alpha machine. Please make sure you have the license to run all
of the modules in the flow you attempting to submit as a job. View the license category chart below to find
192
out if the modules you are running require a special license. If so, look at your SeisUP license files for the
matching license features. For instance if you are running a flow including the KTMIG module you should
make sure your license file on the execution machine contain lines similar to these:
FEATURE timemigration seisup 2005.0 permanent uncounted \
HOSTID="XXXXXXX" SIGN="XXXX XXXX XXXX XXXX XXXX"
You may also be denied a license if all of the licenses for a particular feature are checked out. For
instance, you may have a license to run ten jobs concurrently on a machine but your colleagues are already
doing so, then your job will be the eleventh and thus be denied a license. The same may happen for cluster
node licenses.
If you feel you are being denied a license that should be available contact the GeoCenter support staff with
as much of the information about the error as possible: actual error message, licensedaemon.log file,
modules in flow that failed, license file, etc. Or if the error message is descriptive you may feel it can be
fixed by modifying one of the license server systems configuration files. Use FlexNETs End User Guide
for assistance, but remember never modify the actual license files (those ending in .lic).
Appendix A: License Categories

A 3D license is required for running jobs in 3D areas. The compression license is for writing out wavelet
compressed data. Pre-stack systems require the pstack license. The following table shows which modules
in the SeisUP processing library belong to which license category. Modules have a primary and secondary
category which may be the same. Modules not listed here should be considered part of the core and field
categories. Field systems use the field category, this is mostly a subset of the core category. A number of
modules listed here have not been released yet and may never be. The list compiled here is subject to
change without notice.
Module Name
Primary Category
Secondary Category
adaptdcn
core
core
addhdr
core
core
ahcvel
core
core
ampcor
core
core
ampstat
core
field
animod
core
core
apdlms
core
core
ascread
core
core
193
autc
core
field
autorev
core
core
avoa
avo
avo
avoazim
avo
avo
avocross
avo
avo
avopore
avo
avo
avoscale
avo
avo
azimvtry
core
core
binline
core
core
binread
core
core
blip
core
core
bsse
core
core
cazm
core
core
ccpbin
multicomponent
field
censusdb
core
core
chknan
core
core
clip
core
core
clustest
core
core
cmpintp
core
core
cmpline
core
core
cnsgeom
core
core
coff
core
core
194
cohfilt
core
core
comread
core
core
comwrite
core
core
conv
core
field
crosstie
core
core
cut3d
core
field
cva2d
core
field
cva3d
core
field
cva3dhti
core
field
cvfb
core
core
cvgma
core
core
dbhdr
core
core
dbing
core
field
dbmerge
core
core
dcbias
core
field
decon
core
field
delhorz
core
core
deltaxy
core
core
demux
core
field
depth
timemigration
timemigration
despike
core
core
dice
core
core
195
dice3d
core
core
dipmod
core
core
disintg
core
core
display
core
field
dlist
core
field
dmo3d
timemigration
timemigration
dmodist
timemigration
timemigration
dmog
timemigration
timemigration
dmos
timemigration
timemigration
dng1
timemigration
timemigration
dng2
timemigration
timemigration
drtoy
avo
avo
dtype
multicomponent
multicomponent
elasticp
avo
avo
eletoflt
core
core
endif
core
core
ensbal
core
core
enscln
core
core
ensdcn1
core
core
ensdcn2
core
core
ensfft
core
core
ensmath
core
core
196
ensscale
core
core
eqdist
core
core
eqdmo
timemigration
timemigration
exphorz
core
core
extract
core
field
fake3d2
core
core
fbpbo2d
core
field
fbpickmc
core
field
fcvfb
core
core
fdaf
core
field
fdmig2d
timemigration
timemigration
fdmig3d
timemigration
timemigration
fdump
core
field
ffwmig3d
timemigration
timemigration
filter
core
field
fkfilt
core
field
fkint
core
core
fkkfilt
core
core
fkmig
timemigration
field
fkmod
core
core
fkmrc
core
core
fkplot
core
core
197
fkpocs
core
core
flat
core
core
flex
core
core
flexbin
core
core
fold
core
field
forthpik
core
core
fracdet
multicomponent
multicomponent
freqtune
core
core
frfstprp
core
field
fxdn
core
field
fxydmig
timemigration
timemigration
fxydn
core
core
fxymig
timemigration
timemigration
fxymigex
timemigration
timemigration
fxymigr
timemigration
timemigration
gain
core
field
gamlseis
gamlseis
gamlseis
gavel
avo
avo
gchg2d
core
core
geom
core
field
geomck
core
field
geomext
core
field
198
geomview
core
core
geovel
core
field
geovel3c
core
core
glirpt
core
core
gnattr
core
core
gnplot
core
core
grnmtn
core
core
grva
core
core
gvlpick
core
field
gvlprint
core
core
hampson
core
core
hdrdump
core
field
hdrintp
core
core
hdrstk
core
field
hilbert
core
core
hip
core
core
hmth
core
field
horizon
core
field
horzimp
core
core
hsum
core
core
icomp
core
core
idlinbin
core
core
199
idrenum
core
field
if
core
core
imphorz
core
core
impls3d
core
core
interp
core
core
intgrt
core
core
invel
core
core
inversn
core
core
isov
core
field
ivep
core
core
kapture
core
core
kdmig
timemigration
timemigration
kfil
core
core
ktmig
timemigration
timemigration
ktvel
timemigration
timemigration
lame
avo
avo
lap
core
core
lckf
core
core
length
core
field
length2
core
core
line3d
core
core
linename
core
field
200
linetie
core
core
linsub
core
core
logread
core
core
lradon
core
core
mapcon
core
core
marine
core
core
match
core
core
match2
core
core
matcon
core
core
mbinmap
timemigration
timemigration
mcadpdcn
core
core
mgeom
core
core
mgridp1
core
core
midgeom
core
core
mix3d
core
core
mixd3d
core
core
mnmxamp
core
field
mpas
core
field
mpasext
core
core
mpdpool
core
core
monosub
core
core
msource
pstack
pstack
201
mstation
core
core
mulp
core
field
mute
core
field
mvrec
core
field
netread
core
core
netwrite
core
core
nmo3d
core
core
nmoa
core
field
nmor
core
field
noise
core
field
noisedit
core
core
nopermit
core
core
notch
core
field
nsub
core
field
ntext
core
core
offscale
core
core
omit
core
field
optdcn1
core
core
optdcn2
core
core
optdcnpl
core
core
optmute
core
core
pad3d
core
core
202
pickshif
core
core
pilot
core
core
pilot2
core
core
pkmig
core
core
plot
core
field
pmnorm
core
core
polint
core
core
power
core
core
preint
timemigration
timemigration
psi3d
timemigration
timemigration
psmig2d
timemigration
timemigration
psmig3d
timemigration
timemigration
psutil
multicomponent
multicomponent
pthrow
core
core
ptslice
core
core
pwavo
core
core
qc3d
core
field
qcmute
core
core
qcomp
core
core
qcvel
core
core
qcview
core
field
qderive
core
core
203
qfilter
core
core
rad02
core
core
radon
core
core
radon1
core
core
radonc
core
core
ras1
core
core
ras2
core
core
ras3
core
core
ras3d1
core
core
ras3d2
core
core
ras4
core
core
rdmo
timemigration
timemigration
read
core
field
redomx
core
core
refst
core
field
refstprp
core
field
regread
core
core
regrid
core
core
regwrite
core
core
reloc
core
core
repeat
core
core
resamp
core
core
204
resid1
core
field
resid2
core
field
resmerge
core
field
rfmt
core
field
rfs1
core
core
rliv
core
core
rmhdr
core
core
rndcln
core
core
rnmo
core
core
rot3d3c
multicomponent
multicomponent
rotate
multicomponent
multicomponent
rotate2c
core
core
rotate4c
core
core
rsim
core
core
rt3d
core
field
rtml
timemigration
timemigration
rva
core
core
rwsum
core
core
rzero
core
field
scale
core
field
scat
core
field
scdcn1
core
field
205
scdcn2
core
field
scdcn3
core
field
scdecon1
core
field
scdecon2
core
field
scphd1
core
core
scphd2
core
core
scphd3
core
core
seg2
core
core
segp1
core
field
segyread
core
field
segywrit
core
field
select
core
field
sfnmo
core
core
sgn1
core
field
sgn2
core
field
sgn3
core
field
sgne1
core
core
sgne2
core
core
slice
timemigration
timemigration
smig
timemigration
timemigration
smigsave
timemigration
timemigration
smooth
core
core
206
smthang
multicomponent
multicomponent
smvslice
core
core
snr
core
core
sort
core
field
source
pstack
pstack
sper
core
field
spikedit
core
field
spromig
timemigration
timemigration
sprskid
core
core
sps
core
field
squeeze
multicomponent
multicomponent
srinterp
core
core
srme1
core
core
ssdecon
core
core
ssmp
core
field
stack
core
field
stack3d
core
core
static
core
field
statintp
core
core
station
core
field
stksnr
core
core
stretch
core
core
207
strm
core
field
sttintp
core
core
subsegy
core
core
surfwave
core
field
surmat
core
core
swap
core
field
syndip
core
core
synth
core
core
tauf
core
core
taupdmo
timemigration
timemigration
tcopy
core
core
tdaf
core
core
tdump
core
field
tfdnoise
core
field
tomostat
core
core
tomova
timemigration
timemigration
tomovint
core
core
tovg0
core
core
tprt
core
core
tracecal
core
core
tracecmb
core
core
tracefft
core
core
208
transpos
core
core
travtomo
core
core
trcplot
core
field
trcrem
core
core
trimcmp
core
core
trip
core
core
trip5d
core
core
ttgci
timemigration
timemigration
tvaaa
core
core
tveq
core
field
tvmult
core
core
tvsa
core
core
tvsac
core
core
tvse
core
core
tvsec
core
core
tvtrim
core
core
tvzd
core
field
ukooa
core
field
undupe
core
field
unscale
core
field
va3c
core
core
vcor
core
field
209
velconv
core
core
velhorz
core
core
velsmth
timemigration
timemigration
vextract
core
core
vibmim
core
field
viewer3d
core
core
vimpexp
core
core
vip
core
field
vipinv
core
core
vipmath
core
core
vormed
core
core
voronoi
core
core
vorscl
core
core
vslice
core
core
vsum
core
core
wavelet
core
core
wavemult
core
core
write
core
field
wtnrc
core
core
xava
avo
avo
xequ
core
core
xygeom
pstack
pstack
210
xymap
core
field
zavo
core
core
211
SeisUP Plotting Subsystem

Contents
Introduction
Interface Scripts
Sending Feedback
Introduction
SeisUP 2005 introduced an entirely new plotting subsystem that provides many advantages over the
plotting subsystem that existed in SeisUP prior to the 2005 release. The new plotting system provides a
number of simple scripts that are invoked by the Flow Editor to handle actions requested by the user for
previewing a plot or submitting a plot job. SeisUP includes integration scripts for interfacing with
PrintMaster from SDI, as well as the legacy SeisUP plotting system. Users can customize these scripts to
allow SeisUP to interface with plotting software from any vendor.
The information contained in this manual pertains to software provided with SeisUP 2005 and later.
Interface Scripts
The plotting system scripts and configuration files are located in the directory
$QEDTOP/bin/$QSYS/plotting. This directory contains subdirectories that represent individual
subsystems. For example, the sdi subdirectory contains implementations of the plotting scripts to interface
with PrintMaster.
In plotting/ directory there are also links to three scripts and a configuration file. These are links to files
within the subdirectory that represents the plotting system you wish to interface SeisUP with. The files are
described as follows:
seisup_plotter_list
This script will return a list of plotters that SeisUP can use for plotting.
seisup_plot_preview
This script is used to launch a CGM viewer application.
seisup_plot_submit
This script is used to submit a plot job.
plotting.conf
This file contains information describing the active plotting subsystem.
Each of these files is described in more detail in the following sections.
212
seisupd_plotter_list
This script prints a list of plotters to stdout that are available to SeisUP for plotting. No command-line
arguments are required for this script, and the output contains one plotter per line. The Flow Editor
invokes this script in response to the user selecting File->Select Plotter.... The output of the script is
presented to the user in the Select Plotter dialog.
The following is an example of the output generated by this script when run from the command line:
% ./seisup_plotter_list
"DesignJet - HP DesignJet 650C 300dpi"
"Versatec - OYO GS636 400 400dpi"
This output is displayed in the plot selection dialog when invoked from the Flow Editor, as shown here:
seisup_plot_preview
The Flow Editor invokes this script in response to the File->Print Preview... command, or the View
action in a CGM datasets contextual menu. The Flow Editor passes a single command-line argument to
this script, which is the absolute path to the CGM file to be displayed.
The following example shows an implementation of this script that brings up the PrintMaster plot submit
and preview dialog:
#!/bin/sh
/opt/sdi/pm_server/bin/sdiSubmit.sh -f $1 &
213
Note the ampersand at the end of the command. If the preview application is not put into the background
the Flow Editor interface will be frozen as long as the preview application is open. Again, $1 refers to the
first command-line argument to the script, which is the path to the CGM file being opened.
seisup_plot_submit
This script submits a CGM file to the vendor plotting software to be output. seisup_plot_submit is invoked
by the Flow Editor when the user selects the File->Print command or Hard Copy command from the
contextual menu for a CGM dataset module. When invoked this script is passed two arguments: the path
to the CGM file to plot, and an index indicating which plotter to use. The plotter index is the line number
from the output of seisup_plotter_list, starting with 1. Thus, in the following example:
% ./seisup_plotter_list
"DesignJet - HP DesignJet 650C 300dpi"
"Versatec - OYO GS636 400 400dpi"
index 1 refers to the plotter named DesignJet, and index 2 refers to the plotter named Versatec.
This is an example implementation of seisup_plot_submit that submits a plot to PrintMaster:
#!/bin/sh
#
# seisup_plot_submit
#
# This script will submit a plot job to an SDI PrintMaster
# plot server. The script is passed the following arguments:
#
#
$1 - path to file to plot
#
$2 - Index of plotter in list returned by seisup_plotter_list
#
(starting with 1)
#
sdi_bin=$QEDTOP/bin/$QSYS/plotting/sdi
host_info=cat $QEDTOP/etc/plot_host
if [ -z "$host_info" ]; then
echo "Could not find valid plotting host in $QEDTOP/etc/plot_host"
exit 1
fi
host=echo $host_info | awk { print $1 }
port=echo $host_info | awk { print $2 }
if [ -z "$port" ]; then
port=6050
fi
dev_info=$sdi_bin/ntserv_access $host $port plotters | sed -n "${2}p"
plotter=echo $dev_info | awk -F: { print $1 }
pm_host=echo $dev_info | awk -F: { print $2 }
pm_port=echo $dev_info | awk -F: { print $4 }
$sdi_bin/sdi_pm -r $pm_host -O $pm_port -p "$plotter" $1 > /dev/null
214
Youll notice that we refer to a configuration file located at $QEDTOP/etc/plot_host. This file simply
contains the hostname and port number of the PrintMaster service. When writing scripts for another
vendors software you may use this file to store the hostname and port number of that vendors plot server.
plotting.conf
seisup_plot
select_plotting_subsystem
Sending Feedback
If you experience problems with plotting in SeisUP, or wish to send feature suggestions or other general
feedback, please contact us at feedback@geocenter.com.
If you would like support for another vendors software added to SeisUP, or have yourself developed
scripts to interface with a particular vendors software that you would like included in the next SeisUP
release, please let us know by sending feedback through the previously mentioned channel.
215
Documentation > SeisUP Reference Manual >
SeisUP Reference Manual

Modules
ADAPTDCN
ADDHDR
AHCVEL
AMPCOR
AMPSTAT
ASCREAD
AUTC
AUTOREV
AVOA
AVOCROSS
AVOSCALE
AZIMVTRY
BINLINE
BINREAD
BLIP
BSSE
CAZM
CCPBIN
CENSUSDB
CHKNAN
CLIP
CLUSTEST
CMPLINE
CNSGEOM
COFF
COHFILT
COMREAD
COMWRITE
CONV
CROSSTIE
CUT3D
CVA2D
CVA3D
CVA3DHTI
CVFB
CVGMA
DBHDR
DBINQ
DBMERGE
DCBIAS
DECON
DELHORZ
DELTAXY
DEMUX
DEPTH
DESPIKE
DICE
DICE3D
DIPMOD
DISINTG
DISPLAY
DLIST
DMO3D
DMODIST
DMOG
DMOS
DNG1
DNG2
DTYPE
ELASTICP
ELETOFLT
ENDIF
ENSBAL
ENSCLN
ENSDCN1
ENSDCN2
ENSFFT
ENSMATH
ENSSCALE
EQDIST
EQDMO
EXPHORZ
EXTRACT
FAKE3D2
FBPBO2D
FBPICKMC
FCVFB
FDAF
FDMIG2D
FDMIG3D
FDUMP
FILTER
FKFILT
FKINT
FKKFILT
FKMIG
FKMOD
FKMRC
FKPLOT
FLAT
FLEX
FLEXBIN
216
FOLD
FORTHPIK
FRACDET
FREQTUNE
FRFSTPRP
FXDN
FXYDMIG
FXYDN
FXYMIG
FXYMIGEX
FXYMIGR
GAIN
GAMLSEIS
GCHG2D
GEOM
GEOMCK
GEOMEXT
GEOMVIEW
GEOVEL
GEOVEL3C
GNATTR
GNPLOT
GRNMTN
GRVA
GVLPICK
GVLPRINT
HAMPSON
HDRDUMP
HDRINTP
HDRSTK
HILBERT
HIP
HMTH
HORIZON
HORZIMP
HSUM
IDLINBIN
IDRENUM
IF
IMPHORZ
IMPLS3D
INTGRT
INVEL
INVERSN
ISOV
IVEP
KAPTURE
KFIL
KTMIG
LAME
LAP
LCKF
LENGTH
LENGTH2
LINE3D
LINENAME
LINSUB
LOGREAD
LRADON
MAPCON
MARINE
MATCH
MATCH2
MATCON
MCADPDCN
MGEOM
MGRIDP1
MIDGEOM
MIX3D
MIXD3D
MNMXAMP
MONOSUB
MPAS
MSOURCE
MSTATION
MULP
MUTE
MVREC
NMO3D
NMOA
NMOR
NOISE
NOISEDIT
NOPERMIT
NOTCH
NSUB
NTEXT
OFFSCALE
OMIT
OPTDCN1
OPTDCN2
OPTDCNPL
OPTMUTE
PAD3D
PICKSHIF
PILOT
PILOT2
PKMIG
PLOT
PMNORM
POLINT
POWER
PSI3D
PSMIG2D
PSMIG3D
PSUTIL
PTHROW
PTSLICE
PWAVO
QC3D
QCMUTE
QCOMP
217
QCVEL
QCVIEW
QDERIVE
QFILTER
RADON
RADON1
RADONC
RAS1
RAS2
RAS3
RAS3D1
RAS3D2
RAS4
RDMO
READ
REFST
REFSTPRP
REGRID
RELOC
REPEAT
RESAMP
RESID1
RESID2
RESMERGE
RFMT
RFS1
RLIV
RMHDR
RNDCLN
ROTATE
ROTATE2C
ROTATE4C
RSIM
RT3D
RWSUM
RZERO
SCALE
SCAT
SCDCN1
SCDCN2
SCDCN3
SCDECON1
SCDECON2
SCPHD1
SCPHD2
SCPHD3
SEG2
SEGP1
SEGYREAD
SEGYWRIT
SELECT
SGN1
SGN2
SGN3
SGNE1
SGNE2
SLICE
SMIG
SMIGSAVE
SMOOTH
SMTHANG
SMVSLICE
SNR
SORT
SOURCE
SPER
SPIKEDIT
SPRSKID
SPS
SQUEEZE
SRINTERP
SSDECON
SSMP
STACK
STACK3D
STATIC
STATINTP
STATION
STKSNR
STRETCH
STRM
STTINTP
SUBSEGY
SURFWAVE
SURMAT
SWAP
SYNDIP
SYNTH
TAUF
TAUPDMO
TCOPY
TDAF
TDUMP
TFDNOISE
TOVG0
TRACECAL
TRACECMB
TRACEFFT
TRANSPOS
TRCPLOT
TRCREM
TRIMCMP
TRIP
TRIP5D
TVEQ
TVMULT
TVSA
TVSAC
TVSE
TVSEC
TVTRIM
TVZD
218
UKOOA
UNDUPE
UNSCALE
VA3C
VCOR
VELCONV
VELSMTH
VEXTRACT
VIBMIN
VIEWER3D
VIMPEXP
VIP
VIPINV
VIPMATH
VORMED
VORONOI
VORSCL
VSLICE
VSUM
WAVELET
WAVEMULT
WRITE
WTNRC
XAVA
XEQU
XYGEOM
XYMAP
ZAVO
ASCII
BIN
CGM
CMAP
COMPRESS
DNG1
DNS1
ENSDCN
FDMIG
FXYDSV
FXYMIG
FXYSAV
GCI
GVL
KTMIG
LAS
OPTDCN
PSM
RAS1
RAS3D1
REG
RFMT
RFS1
SCDCN1
SCDCN2
SCDECON1
SCPHD1
SCPHD2
SEGY
SGN1
SGNE1
SMIG
Data Types
Matrices
3DDIR
3DREFDEF
4THNMO
AFS1B
AMPSTAT
AMPWIN
APERTURE
AUTC
AVGVEL
AVOC
CMPDATUM
COFFOFF
COLORSURFDEF
CONVFREQ
CONVFREQ1
CONVTIM
CONVTIME
CVAETAS
CVAVELS
DBFOLD
DBFOLDOFF
DECON
DFORM
DICE
DIPMODEL
DISTOFF
DMUX
DNGBINS
DSETLIST
DUMPLIST
ENSWIN
ETANMO
219
EVEL
EXTRACT
FILEFREQ
FILES
FILTER
FILTERB
FKFAN
FKFANV
FKPOLY
FKPOLYV
FLEX
FLEXOVP
FXYFREQ
GAIN
GCIHDREXT
GDELAY
GEOMCK
GVLAWIN
GVLPREF
HMTH
HORIZON
HORIZON3D
INTVEL
IREFVEL
ISOVBINS
ISOVHORS
ISOVLINS
ISOVTIMS
KFIL
LASHEADER
LCKF
LINAME
LINES
LMOVEL
MARINEGEOM
MATCH
MATCH2
MIDPOINT
MIX3DWGT
MPISNODES
MULPPER
MUTE
MUTECONT
MXLINE3D
MXLINE3DXY
NMOMUTE
NOTCHFIL
OFFBDIST
OMIT
OPTDCN
OPTDCNP1
PATREC
PATTERN
PATTERNM
PLOTENTRY
PLOTLIST
PLOTLT
PLOTLTCUS
PLOTNOTETEXT
PLOTPRF
PLOTSINGLE
PLOTSPMX
PLOTSYMBOLS
PLOTTIC
PLOTTRIP
PSMQC
PSROTANG
PSROTANG1
QCOMPF
QCOMPS
QCOMPV
QCVELWIN
QMATRIX
QVALUES
RADON
RADON1
RAS2GEO
RAS2SRC
RECMASK
RECVGEOM
REELS
REGIONS
REGIONST
RFMT
RFMTSEGD
RMOD
RMSFCSN
RMSSSPN
RMSV3C
RMSVEL
SCDCN1
SCDECON1
SCLDB
SCLSCL
SCLWIN
SDELAY
SEGYEBC
SEGYLINES
SEGYREMAP
SGN1
SGN2
SGNE
SMOOTHHORZ
SNR
SOURCE
SOURCE2
SOURCEM
SRCDXOFF
SRCDXOFF2
SRCMXLST
SRCRECREC
SRCRECREC2
220
SRCRECSPD
SRCRECSPD2
SRCRECXY
SRCRECXY2
SRCXYREC
SRCXYREC2
SRCXYSPD
SRCXYSPD2
SRGMUTE
SSDEC
STAELEV
STATGEO
STATION
STATSEQ
STATSRC
SURFACE
SURFDEF
SURFSMOOTH
SVSHTSHIFT
SYNDIFF
SYNDIPOA
SYNDIPS
TARGET
TAUF
TRCPLOT_CMT
TRCPLOT_GAP
TSVP
TVDIP
TVSMOOTH
TVTVZD
TVTVZDC
TVTVZDD
TVZD
USRFCSN
USRMBIN
USRSBIN
USRSGEN
V0
VA3CDIP
VABINS2D
VABINS3D
VPVSDEN
VS2VP2
VSUM
VVSPER
WEIGHTS
WINDOWS2
X_T
XTTAPER
XYDIP
221
ADAPTDCN
Module Description
Input Channels
Output Channels
Parameters
Module Description
The Adaptive Deconvolution method is based upon the use of a simple adaptive algorithm which allows
continuous updating of the deconvolution operator as the seismic trace is processed. Adaptive
deconvolution is effective at collapsing refraction, water-bottom, and peg-leg multiples. It is also effective
at removing coherent noise like ground-roll. This deconvolution is susceptible to noise and refraction
energy, you might want to design upper mutes to cut this information before applying this deconvolution.
Adaptive deconvolution is a time-varying deconvolution method for processing seismic data. The adaptive
algorithm has it roots in the communications field, where it is used to improve the signal-to-noise ratio of
the data. Adaptive deconvolution is effective at collapsing multiples and coherent noise energies. The
technique is based on the use of a continuously adaptive linear prediction operator in which the operator
coefficients are updated using a adaptive algorithm. New coefficients are computed for each data sample
in the seismic record so as to minimize the mean-square error criterion.
The adaptive deconvolution method uses a Maximum Entropy (Burg) solution. The user specifies the rate
at which the prediction filter coefficients adapt, 1.0 is the suggested starting point. The author suggests
that you subtract in increments of 0.05 until results indicate no further refinement. In all cases, low
adaptation rates will show little spectral whitening and high rates may become unstable.
An operator length must be chosen so that the length encompasses the entire length of the wavelet. A
prediction gap may be entered so that specific multiples can be collapsed. The prediction gap length
dictates the multiples to be attenuated. The program allows the use of the water bottom time taken from
the trace header to attenuate water bottom multiples.
Application time gates can be selected so that only specific times of the data may be deconvolved.
Typically, you will try to select mutes just above or below the refraction energy. If you want to attenuate
refraction multiples, then choose gate times above the refraction energy. If the refraction energy is
changing the operator such that the data below is not being deconvolved properly, then choose time gates
just below the refraction energy.
References
L. J. Griffths, F. R. Smolka, L. D. Trembly, Adaptive Deconvolution: A New Technique for Processing
Time-Varying Seismic Data, Geophysics 42, 1977, pp. 742-759.
222
Cowan, C.F.N., and Grand, P.M., 1985, Adaptive Filters; Prentice-Hall Book Co.
Hale, D., Widrow, B., and Stearns, S.D., 1985, Adaptive Signal Processing; Prentice-Hall Book Co.
Input Channels
1. Input: Required connection from previous process GCI data type
Output Channels
1. Dataset for CGM plot: Optional connection to disk file
Parameters
Decon operator length (ms)
Select a operator length in milliseconds that will encompass the length of the wavelet.
Prediction gap (ms)

Enter a prediction gap in milliseconds to attenuate specific multiples.
Adaptation rate
Enter the adaptation rate. The default is 1.0. You might want to increase/decrease adaptation rates of 0.05
from the starting point. Most of the time, you will decrease from the default value.
Application time gates for decon?

Select to enter the start/stop time from the menu or to get the start/stop times from a matrix file.
Application time gate start (ms)

Enter the time in milliseconds to begin applying the deconvolution.
Application time gate end (ms)

Enter the time in milliseconds to end applying the deconvolution.
223
Primary header key

Options: NONE, CDPN, DIST, FCSN, FSPN, MBIN, MLIN, MSBN, MSLN, OIDN,
RSBN, RSLN, SDPN, SGEN, SBIN, SLIN, SSBN, SSLN, SSPN, TIM1, TIM2,
TLSN
Secondary header key

TLSN
Application time gates

Matrix Type: WINDOWS2
Header to add to gate start time

Options: NONE, TIM1, TIM2
Header to add to gate end time

Restore amplitude?
Low frequency (Hz)
High frequency (Hz)
224
ADDHDR
Module Description
Input Channels
Output Channels
Parameters
Module Description
The ADDHDR module is used to define addition fields in GCI trace headers. The standard GCI trace
header is comprised of 87 32-bit header fields. This module can be used to add any number of fields,
which may be typed integer or floating point. The module is parameterized in a header extension matrix in
which each row defines a new field. A field is defined by a field name and a type. The default type is
integer.
Known Issues
Using the READ module to read in multiple datasets with extended headers will fail when attempting
to open the second dataset.
To fix this problem, use the RMHDR module to get rid of the extended headers and try again.
Input Channels
1. Input: Required connection from input process GCI data type
Output Channels
1. Output: Optional connection to next process GCI data type
Parameters
Header Extension Matrix
Matrix Type: GCIHDREXT
This is the matrix used to define additional header fields. Each row of the matrix defines a new field, and a
field is defined by a name and a type. The type may be either integer or floating point, integer being the
default.
225
AHCVEL
Module Description
Parameters
Module Description
Converts RMS velocities to Amerada Hess format.
Parameters
Input velocities
Matrix Type: RMSVEL
Output file name
226
AMPCOR
Module Description
This module corrects pre-stack amplitudes for various non-geologic effects, such as, geometric
divergence, absorption (Q), source and receiver arrays, emergence angle (for land data only),and
anomalous transmission losses. These corrections would particularly be important for AVO analysis. All
pre-existing gains, however, should be removed from the gather data, prior to running this module. The
module AMPCOR should be followed by surface-consistent amplitude corrections using modules, SGN1,
SGN2, and SGN3. Optionally, this program can also remove previously applied amplitude correction
factors.
The module AMPCOR also has options to equalize the RMS amplitude of each CDP gather to a specified
level. It can estimate corrections for zero-offset only, which would be suitable to correct post-stack
amplitudes for any of the above causes. Optionally, it also builds Vp-Vs-Density model using the RMS
velocity function, Vp-Vs and Vp-density relationships. It then computes transmission coefficients at these
interfaces for all offset distances in a CDP gather. It then corrects the trace amplitudes for anomalous
transmission coefficients at the overlying layers. For land data, it computes the ray emergence angle at a
geophone using the RMS velocity function, and then corrects the amplitude as if it would be vertically
incident on the geophone.
This module also produces statistics, such as the minimum, maximum, and average value, of each
component of amplitude corrections, in the execution status file. By processing a few gathers, statistics of
amplitude corrections thus obtained could be useful in two ways. First, it can help in judging the
sensitivity of the input parameters in computing these corrections. (Highly sensitive parameters need to be
input as accurately as possible.) Second, it can help in deciding which amplitude correction factors are
significant, and which are not so significant. To process a large number of gathers by this module, this
decision can save a lot of computation time.
References
Newman, P., 1973 Divergence Effects in a Layered Earth by P. Newman, Geophysics, P. 481-487.
Input Channels
1. Input
Required
Connect from other process only
GCI data type
227
Output Channels
1. Output
Required
Connect to other process only
GCI data type
Parameters
Apply or remove amplitude correction?
Normally, the program will apply, by default, all or specific amplitude corrections that have been chosen.
The Remove option is the opposite of Apply option - it will remove the correction factors from the
data.
Options: Apply, Remove
Starting CMP Bin for amplitude correction

Final CMP Bin for amplitude correction
Marine or Land data?
If a land data set is input, the module will correct the amplitudes for emergence angle at a geophone. For
marine data, this correction is not necessary as the data are recorded by pressure-sensitive hydrophones.
Emergence angle correction is done within the geometric divergence compensation.
Options: Marine, Land
Are data moveout corrected?

Length(velocity) Units: Feet(feet/sec) or Meters(Meters/sec)?
Options: Feet(Feet/Sec), Meters(Meters/Sec)
Normalize ensemble RMS amplitude?

Optionally, the module can normalize the RMS amplitude of each CDP ensemble to a specified level (see
below).
228
RMS reference amplitude

If the normalization option for ensemble RMS amplitude is chosen (see above), this is the level to which
the RMS amplitude would be normalized. The default is the RMS amplitude level of the first CDP
ensemble processed.
Reference frequency for amplitude correction

Normally, it should be the peak frequency of the seismic pulse.
Compute zero-offset correction only?

The user has a option to correct amplitudes based on zero-offset effect only. This option is particularly
useful for post-stack data, when amplitudes need to be corrected for any particular effect (see below).
Apply all amplitude corrections?

The user has an option to correct amplitudes for all or individual effects specified below. If you choose
yes here, you do not need to choose individual corrections, except selecting parameters for these
corrections.
Compute geometric divergence correction?

These are the corrections for spherical divergence loss in a layered earth. Note that corrections for
emergence angles in land data are done within this option. RMS velocity function, and surface-layer
velocity (see below) are required for computing these corrections.
Compute absorption (Q) amplitude correction?

This module computes only amplitude corrections due to a Q model. For phase corrections, the user must
use the QCOMP module. One needs to specify the Q model through a Q matrix (see below). To build this
Q matrix, one can estimate Q values within a time window, using the QDERIVE module.
Q-Matrix
Required for Q correction of amplitudes (not phases). For phase correction, use the QCOMP module. As
mentioned above, Q-values for this matrix could be estimated using the module, QDERIVE.
Matrix Type: QMATRIX
Compute source array correction?

One requires this correction, particularly if the source array length is longer than 30 meters. Computation
of these corrections uses an assumption of a linear array. Although the source array actually could be
spread over an area, linear array assumption would be adequate if the nearest geophone is about 1000 feet
away.
229
Length of source array (m or ft)

Note that the unit of the array length should be the same as the UNIT parameter chosen above.
How many sources in the array?

Note that this number should be based on the assumption of a linear array.
Compute receiver array correction?

One requires this correction, particularly if the receiver array length is longer than 30 meters. Computation
of these corrections uses an assumption of a linear array.
Length of receiver array (m or ft)

Note that the unit of the array length should be the same as the UNIT parameter chosen above.
How many receivers in the array?

Note that this number should be based on the assumption of a linear array.
Compute hard/soft streak transmission correction?

Normally, in wave theory, transmission losses in amplitudes would be compensated by amplitude gain
through generation of interbed multiples. However, when there are anomalous transmission losses caused
by the presence of hard or soft streaks, such as carbonate or coal layers, these losses need to be
compensated.
Tolerance Limit for transmission coefficient correction

The anomalous transmission coefficients are defined by this parameter and the next parameter. Computed
transmission coefficients would be considered anomalous, if they fall outside 1.0 +/- tolerance limits. If
ray parameter,p = 0. is chosen for selecting the anomalous interfaces, which is the default for the next
parameter, then we recommend using 0.1 as the tolerance limit. For other P-values, this limit should be
increased to, say, 0.3. Otherwise, a large number of interfaces may be selected as anomalous, which would
cause a large computation time for transmission loss correction.
Factor to multiply the maximum p-value

The maximum ray parameter value, p is given by 1./VTOP, where VTOP is the P-wave velocity of the
surface layer. If one chooses here the factor to be zero, which is the default, then p=0 (that is, the
normal-incident ray) is used as the basis for selecting anomalous interfaces. An appropriate value for the
tolerance limit (say, 0.1 for p=0) also needs to be chosen (see above). On the hand, if one selects 1.0 as the
factor here, and 0.3 or less for the tolerance limit above, then a larger number of interfaces would be
selected as anomalous. This increase would cause a significant delay in the output of the transmission
corrections. Note that the interfaces where critical angles are almost reached, are considered anomalous
230
here as the transmission coefficients fall sharply at these interfaces.
Value for b-coefficient in the relationship: Vs=b*Vp+c

To compute elastic reflection coefficients, this module generates shear-wave velocities (Vs) from P-wave
interval velocities using a linear relationship:
Vs = b * Vp + c.
The default for b-coefficient in this relationship is based on the work by Castagna et al.
Value for c-coefficient in the relationship: Vs=b*Vp+c

To compute elastic reflection coefficients, this module generates shear-wave velocities (Vs) from P-wave
interval velocities using a linear relationship:
Vs = b * Vp + c.
The default for c-coefficient in this relationship is based on the work by Castagna et al.
Value for a-coefficient in the relationship: Density = a*Vp**b

To compute elastic reflection coefficients, this module generates densities from P-wave interval velocities
using a power-law relationship:
Density = a * Vp ** b.
The default for a-coefficient in this relationship is based on the work by Gardner.
Value for b-coefficient in the relationship: Density = a*Vp**b

To compute elastic reflection coefficients, this module generates densities from P-wave interval velocities
using a power-law relationship:
Density = a * Vp ** b.
The default for b-coefficient in this relationship is based on the work by Gardner.
RMS velocities
Required for geometric divergence correction, Q correction, emergence angle correction etc.
Matrix Type: RMSVEL
231
Top-layer P-Wave Velocity

The top-layer P-wave velocity is required for geometric divergence correction, emergence angle correction
(for land data), and transmission correction. The default for the top-layer velocity is 4950 feet/sec (or,
1509 meters/sec) for marine data, and 6000 feet/sec (or, 1829 meters/sec) for land data.
232
AMPSTAT
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module has been donated to the SeisUP community by El Paso Production Company.
AMPSTAT calculates statistics for a user-specified grouping of traces. The group may consist of a single
trace, an ensemble, a panel of traces, or an entire dataset. AMPSTAT calculates the absolute mean and
median, the RMS value, and finds the minimum and maximum amplitudes for each trace group.
Each trace grouping may be further sub-divided into time windows, by specifying a series of start and stop
times in a matrix.
AMPSTAT can print the amplitude statistics in the standard output of the job, or can save the statistics in a
matrix, or both.
AMPSTAT can divide each trace groups amplitudes into a user-specified number of bins.
AMPSTAT can also store the RMS value, the mean, or the median of each trace or ensemble in the TIM1
or the TIM2 trace headers of each trace.
Input Channels
Output Channels
Parameters
Use time windows for Summary Groups?
Choose Yes to calculate statistics over one or more time windows. The windows are specified in matrix.
233
Analysis windows matrix name

Accessed if Use time windows for Summary Groups? is Yes.
Specify the name of a matrix file to contain starting and ending times for statistics calculations. For each
window, enter a start time in milliseconds, in column 1 of the matrix, and an end time in column 2.
Matrix Type: AMPWIN
Summary group
This parameter determines the number of traces used for each statistic calculation.
Options: All, Ensemble, Trace, NONE, Panel
Panel size in traces

Accessed if Summary group equal Panel.
Enter the number of traces per panel. Panels cannot span ensemble boundaries. If the number of traces per
ensemble is not a multiple of the panel size, the last panel of each ensemble will be Adjusted accordingly.
For example, if panel size is 10, and ensemble size is 38, the panels will be of size 10, 10, 10, and 8.
Summary group increment

It is not necessary to calculate statistics for every group in a dataset. Specify an increment of "n" to
analyze every "nth" group. If Summary group is Panel, then all the panels in every "nth" ensemble will be
analyzed.
Amplitude statistics output

Choose what type of output to produce. Print means that the statistics are in the Execution Status file for
the job.
Options: Print, Matrix, Both
Amplitude statistics output matrix

Accessed if Amplitude statistics output equal Matrix or Both.
Specify a matrix name.
Matrix Type: AMPSTAT
234
Distribution group
If you want to produce amplitude-binning information for plotting, choose a group type other than NONE.
Options: Ensemble, Trace, NONE
Number of distribution bins

Enter the number of bins into which amplitudes are to be divided.
Distribution group increment

It is not necessary to bin every group in a dataset. Specify an increment of "n" to bin every "nth" group.
Amplitude stat to store in TIM1 trace header

Choose from NONE, RMS-Trace, RMS-Ens, Mean-Trace, Mean_Ens, Median-Trace, or Median-Ens to
store statistics in each TIM1 trace header.
Options: NONE, RMS-Trace, RMS-Ens, Mean-Trace, Mean-Ens,
Median-Trace, Median-Ens
Amplitude stat to store in TIM2 trace header

Choose from NONE, RMS-Trace, RMS-Ens, Mean-Trace, Mean_Ens, Median-Trace, or Median-Ens to
store statistics in each TIM2 trace header.
Options: NONE, RMS-Trace, RMS-Ens, Mean-Trace, Mean-Ens,
Median-Trace, Median-Ens
235
ASCREAD
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use ASCREAD to read an ASCII formatted tape to an ASCII formatted disk file. This file then can be
read by programs such as UKOOA.
Input Channels
1. Input: Required ASCII data type.
Output Channels
1. Output: Required connection to dataset ASCII data type.
Parameters
Output record length
This is the number of bytes per line.
Perform EBCDIC to ASCII conversion?

Number of EOFs to skip
Number of records to skip
Maximum number of records to output
236
AUTC
Module Description
Input Channels
Output Channels
Parameters
Module Description
AUTC creates autocorrelations with the given parameters. The autocorrelations are output to the next
process.
Input Channels
Output Channels
Parameters
Append autocorrelation to the input data?
Select Yes to append the autocorrelation to the end of each input trace.
Reference mean for the autocorrelation

Increasing this value will boost the amplitudes of the autocorrelation functions. If 0.0 is coded,
autocorrelation functions are not normalized.
Application mode
Select Single Trace to apply deconvolution on a trace by trace basis. Select Ensemble to apply an
operator that is derived by an average of the autocorrelation over the entire ensemble. Select Running
Window to apply an operator to a single trace that is derived by an average of the autocorrelations from
neighboring traces.
237
Options: Ensemble, Single Trace, Running Window
Number of traces in the running window

If the Application mode is Running Window, enter the number of neighboring traces to used to compute
an average autocorrelation from. This number will be forced to a lower odd number.
Trimmed mean(%)
Required if Application mode? = Ensemble or Running Window. A composite trace is built from the
autocorrelations to be used to compute a deconvolution operator. When trim = 0, the average value of a
time slice through the ensembles autocorrelations is used to build the composite trace. When trim = 100,
the median value of the time slice is used. In between, the out lying values are dropped.
Time variant?
Autocorrelation length(ms)
Required if Time variant? = No.
Space variant design windows?

Start design time(ms)

Required if Space variant design windows? = No.
End design time(ms)

Primary header key

Required if Time variant? = Yes or Space variant design windows? = Yes.
TLSN

238
TLSN
Deconvolution operators
Required if Time variant? = Yes.
Matrix Type: AUTC
Design times
Header to add to design start time

Header to add to design end time

239
AUTOREV
Module Description
The AUTOREV module will automatically detect reverse polarity traces. The data must be in CMP order
and NMO applied, brute stack quality data should be sufficient. A window may be applied to the trace to
limit the analysis to a specific time zone. The percentage of reverse flagged common receivers may be
specified to control which traces are considered reversed polarity.
The traces within the CMP gather are cross-correlated against the stacked trace. The stacked trace is the
stacked sum of all the traces within the CMP gather. The maximum magnitude is selected for the
cross-correlated data and the correlation coefficient (quality) is computed. If the quality is negative, then
the trace is flagged as reversed.
Geometry must be assigned for this dataset before this module can be run.
The CMP gather NMO corrections do not have to be exact. Typically, a brute stack type NMO application
should be sufficient.
The number of positive and negative correlation coefficients are tracked for each common receiver. The
user can specify what percentage of the common receivers must have negative correlation coefficients to
actually be considered as a reverse polarity trace.
The module will allow one time gate to be specified so that the data analyzed to limited to a specific zone.
If you are using the time and space variant matrix, only the first time gate is used.
The module allows the user to specify how many non-zero samples must be in the time window for that
trace to be considered valid. If a trace has too many zero values, then it is ignored in the analysis.
Input Channels
1. input
Required
GCI data type
Output Channels
1. output
Required
GCI data type
240
Parameters
Number of common receivers flagged negative (%)
Specify the percentage of common receivers that must have negative correlation coefficients for a trace to
be considered reversed in polarity. The number of positive and negative correlation coefficients are
tracked for each common receiver.
Example: A common receiver had 100 traces assigned to it. 60 traces had a negative correlation
coefficient, while 40 trace had a positive correlation coefficient. Traces that have this common receiver
number will be flagged as negative as long as this parameter is 60%.
Number of non-zero samples in window to be valid (%)

Specify the number of samples in the trace that must be valid before this trace is used in the analysis. This
value is expressed in the percent of live (non-zero) values within the trace.
Time and space variant time gates?

Specify if you are using a matrix with time/space variant pairs or you are using a single start/stop time.
Time gate start (ms)

Specify the start time in milliseconds for the time gate to use in the analysis. This option will appear if a
time gate matrix was not chosen.
Time gate end (ms)

Specify the end time in milliseconds for the time gate to use in the analysis. This option will appear if a
Primary header key

If you have chosen to use a time/space variant matrix, enter the primary header key for the matrix values.
TLSN

If you have chosen to use a time/space variant matrix, enter the secondary header key for the matrix
values.
241
TLSN
Time gates matrix name

Enter the name of the time/space variant windows file. This must be a pre-existing matrix, that contains
secondary key, start time, and end time values. Only the first time gate is used. Any additional defined
gates for a trace are ignored.

If the trace header has a start time in it, you can use it to adjust the trace in start time. See GCI trace header
word 84 (TIM1).

If the trace header has a end time in it, you can use it to adjust the trace in end time. See GCI trace header
word 85 (TIM2).
242
AVOA
Module Description
AVOA performs Amplitude-versus-Offset (AVO) analysis by extracting AVO attribute stacks. This
analysis can give indications of lithology and pore content. Two methods to compute the attributes are
supported: Linear regression, and Geostack. Eleven different attribute types can be created.
Input data must be CMP or common-bin sorted gathers with NMO applied. Coherent and random noise
will degrade the AVO analysis. Noise can be reduced on the CMP gathers by angle and offset-mixed
super-gathers as well as offset-consistent amplitude corrections. The attribute analysis is done across
iso-time samples or gated time intervals.
The program AVOA computes the various attributes to facilitate amplitude-versus-offset studies. For each
common reflection point, an amplitude-versus-incident-angle curve can be plotted, but it is difficult to
draw any useful information from this kind of curve because noise always exists. However, under the
assumption of a small change in elastic parameters, it has been proven that the reflection coefficient varies
linearly with the square of the sine of the incident angle (Shuey, 1985).
This module will also accept angle of incidence gathers from module XAVA. The center angle for each
angle group that is stored in DIST header word is used to compare with the min/max angles specified in
this module. Center angles outside of this range will be rejected.
Linear regression (least squares) analysis is used to get a best-fit straight line of amplitude verses square
sine of the incident angle. A sample from each trace in the gather is used in the best-fit line analysis. The
Intercept (P) and the Gradient (G) are taken from the straight-line equation:
Y = G * X + P
The intercept (P) of the line from the best-fit analysis is called the pseudo P-wave reflection coefficient at
zero-offset. The gradient, G, indicates the variation of the amplitude with offset. The gradient can be
plotted as gradient stack section (Denham, 1985). By combining the intercept, P, and the gradient, G, other
attribute sections, such as pseudo S-wave section, pseudo Poissons ratio section, hydrocarbon-indicator
section and fluid factor section, can be obtained. Each attribute represents a different aspect of the offset
dependent reflectivity. A combination of all the attributes is recommended for a comprehensive AVO
study.
When using the normal linear regression best-fit straight-line technique, a correlation coefficient and a
randomness statistic section can be built. You can also set a minimum threshold correlation coefficient to
reject best-fit analysis at samples that dont meet the threshold. The correlation coefficient and
randomness sections can later be used to weight the other attribute stacks.
The Geostack option is uses a weighted stacking technique. It outputs the P-Wave velocity reflectivity
(Rp) into the intercept (P) field and the S-Wave velocity reflectivity (Rs) into the gradient (G) field. It also
outputs the sum of the Rp for the trace window as the correlation coefficient and the sum of the Rs as the
statistics. This option computes the Gradient from the P and S wave reflectivity series as:
243
G = Rp - 2 * Rs
Even though the Gradient is not output when using this option, it is used to compute the remaining
attributes.
The AVO attribute analysis is done across same-time sample values or within stack polarity defined gates.
A common problem with AVO attributes stacks is residual NMO on the CMP gathers because of
imperfect velocity analysis. To compensate, amplitudes may be selected within polarity gates, thereby
relieving the requirement of exact NMO application. Polarity gates are computed using a stack of the CMP
gather. The amplitudes in the gate are used to compute a maximum value. The maximum value for each
trace in the gather is used in the best-fit analysis. The output values are blocked as constant values over
each polarity gate.
RMS and interval velocities are needed to compute the sine square of the incidence angle. They are also
used in computing the fluid factor section. The RMS velocities can be provided either as a spreadsheet
matrix or in a VIP file. The velocity function should be smoothed before the attributes are computed to
reduce noise. An option is included to perform smoothing. If the velocities are coming from a VIP file,
then it is recommended to smooth the velocities in the VIP program and not in AVOA.
The AVO attribute analysis may be performed in time gates. Two methods for time gates are included:
spatial varying or non-spatial varying. The non-spatial varying method asks for a start and end time for
performing the analysis. These times are used across the entire survey. The spatial varying method asks
for a times file that was previously built. This module only uses the first start and end time at an analysis
location within the file. If the file contains additional start and end at a location, they will be ignored.
Header values TIM1 and TIM2 may also be used to center a time window about a horizon.
The user can specify the mud rock line slope and intercept used for the Fluid Factor stack trace. Castagna
defines the typical mud-line slope to be 1.16 and the intercept to be 1360. However, experience has shown
that this value varies by geology. The Vs/Vp equation is:
244
Vs/Vp = (1./mud slope) - (mud intercept/mud slope)/Vp
This is then used to compute the fluid factor:

For the Least-Squares option:
FF = (8/5)*P-mud slope*(Vs/Vp) *(0.5*(P-G)) from Castagna, 1993.
For the Geostack option:
FF = P-mud slope*(Vs/Vp)*S from Castagna, 1993.
where: P=P-wave trace, G=Gradient trace, S=S-wave trace.
A specific request was to allow more flexibility in the Poissons Ration stack trace. You can now define a
weighted Poissons Ratio to be:
PR = a * P + b * G
The user can specify the weights in the menu. If you choose to do the default Poissons Ratio then this
equation is used:
PR = (P+G)*4/3
AVO attribute sections built by this module include:

1. Pseudo P-wave (Intercept) stack (P):
This is the intercept in the amplitude versus the square of the sine of the incidence angle. The pseudo
P-wave section displays the zero-offset P-wave velocity reflectivity series. Conventional CMP stack
smears the amplitudes at different incident angles. The pseudo P-wave section is a better representation to
the zero-offset reflection coefficient than the CMP stack section. Therefore, it is more suitable for P-wave
impedance inversion. The interpretation of a P-wave stack is similar to that of a conventional CMP stack.
If the Geostack option is used, then this value is the P-wave velocity reflectivity series. The algorithm
requires a shear velocity, which is computed from the P velocity using Castagnas mud rock equation. A
valid mud rock line slope and intercept should be entered into the menu.
2. Gradient (Slope) stack (G) for least squares method:
Pseudo S-wave stack for geo-stack method:
This is the gradient (slope) in the amplitude versus the square of the sine of the incident angle. A large
positive gradient indicates that the amplitude increases with offset. It may indicate the existence of gas
sand.
If the Geostack option is used, then this value is the S-wave velocity reflectivity series. The algorithm
requires a shear velocity, which is computed from the P velocity using Castagnas mud rock equation. A
valid Mud rock line slope and intercept should be entered into the menu.
245
3. Restricted gradient stack (sign(P) * G):

This stack is the sign of the pseudo P-wave times the gradient section. The restricted gradient stack will
show a positive anomaly when the absolute amplitude increases with offset. Plotting only the positive
quantities can enhance the indications of the potential presence of gas.
4. Pseudo Poissons-ratio stack ((P+G)*4/3):
This stack is four thirds of the pseudo P-wave section plus the gradient section. This is approximately the
Poissons ratio under the assumption that P-wave travels 1.732 times faster than S-wave. The Poissons
ratio stack has a similar appearance to that of a stacked seismic section. High Poissons ratio is suggestive
of gas sand in a sand-shale sequence.
5. Pseudo S-wave stack (1/2)*(P-G)
The pseudo S-wave section displays the zero-offset S-wave velocity reflectivity series but with the P-wave
travel time
6. Potential Hydrocarbon-indicator stack (P*G):
This is the product of the pseudo P-wave section and the gradient section. The potential
hydrocarbon-indicator stack is similar to the restricted gradient stack in interpretation; a large positive
anomaly often indicates the presence of gas in a sand-shale sequence.
7. Restricted P-wave stack (P*Sign(G)):
This is the sign of the gradient times the pseudo P-wave section. This section displays an anomaly when
the absolute amplitude increases with offset.
8. Correlation coefficient or Intercept weights:
When the AVO computation method is least squares then this section displays the correlation coefficient
of the least squares fit. The correlation coefficient has an absolute value range of 0.0 to 1.0, with 1.0
indicating a perfect fit of the points to a least squares straight line. If the computation method is geo-stack,
then this section displays the intercept weights.
9. Statistics or Gradient weights:
When the AVO computation is least squares then this section displays the randomness statistics. Large
absolute values of the statistic (greater than 3) indicate that the data does not trend in a straight line so a
straight line fit is not appropriate. If the computation method is geo-stack, then this section displays the
gradient weights.
10. Fluid factor:
The fluid factor is computed using Castagnas mud rock equation. Gardners relationship is used to
determine the density. A deviation of the intercept and gradient from a regional trend will show up as a
fluid factor anomaly.
246
11. (Far - Near) * Far

A new option in this module is to output a (Far Near) * Far (FNXF) amplitude trace. The near value is the
amplitude on the nearest offset in the CMP that still has a valid (non-zero) sample. The far value is the
amplitude on the farthest offset in the CMP that still has a valid (non-zero) sample.
The following attributes are available:
Option Description
Equation
------ ---------------------------- -------1
P-wave stack (Intercept)
Gradient stack (Slope)
Restricted gradient stack
Sign(P) * G
Pseudo Poissons-ratio stack (P+G)*4/3
Pseudo S-wave stack
(P-G)/2
Potential Hydrocarbon stack
P*G
Restricted P-wave stack
P*Sign(G)
Correlation coefficient or Intercept weights
Statistics or Gradient weights
10
Fluid factor
11
(Far-Near)*Far
247
AVOA outputs the AVO stacks side-by-side. The corresponding option number will be placed in the
location of offset (DIST) in the header. Module EXTRACT or SELECT can be used to separate the
different attribute stacks.
References
Goodway, B., Chen, T., Downton, J., Improved AVO fluid detection and lithology discrimination using
Lame petrophysical parameters from P and S inversions.
Denham, L., Palmeria, R. and Farrel, R., 1985, The zero-offset stack: Presented at the 55th SEG annual
International meeting, Washington, D.C.
Shuey, R. T., 1985, A simplification of the Zoepritz equations: Geophysics, 50,609-614.
Castagna, J.P., Batzle, M.L., and Eastwood R.L., 1985, Relationships between compressional-wave and
shear-wave velocities in clastic silicate rocks.
Smith, G.C., and Gidlow, P.M., 1987, Weighted stacking for rock property estimation and detection of
gas: Geophysical Prospecting, 35, 993-1014.
Castagna, J.P., and Backus M.M., 1993, Offset-Dependent Reflectivity - Theory and Practice of AVO
Analysis. Investigations in Geophysics No. 8.
Todd, C., 1986, Isolation, display, and interpretation of offset dependent phenomena in seismic reflection
data using offset depth ratio partial stacks: M.S. thesis, University of Texas at Austin
248
Jan L. Fatti, George C. Smith, Peter J. Vail, Peter J. Strauss, and Philip R. Levitt, 1994, Detection of gas in
sandstone reservoirs using AVO analysis: A 3-D case history using the Geostack Technique.
Fred Hilterman, 2001, Seismic Amplitude Interpretation, 2001 SEG Short Course Notes
Input Channels
1. Seismic input
Required
GCI data type
2. VIP velocity database
Optional
Connect from disk file only
SEGY data type
GCI data type
Output Channels
1. Attribute stacks
Required
GCI data type
Parameters
Attribute stack output options:
Options: P-wave (Intercept), Gradient stack (Slope), Restricted
gradient, Pseudo Poissons-ratio, Pseudo S-wave, Potential
Hydrocarbon, Restricted P-wave, Correlation coefficient, Statistics,
Fluid factor, (Far-Near)*Far
Method for AVO amplitude fit:

The AVO analysis can be computed at each sample or within polarity gates. The polarity gate is
determined by a stack of the CMP gather traces. The gate being samples within the same polarity cycle.
The amplitude used for each trace is the maximum found using interpolation. The amplitudes are blocked
as constant values within the gate times.
Options: At each sample, Polarity gate
249
Method for AVO attribute computations:

The best-fit line computation is performed using a least squares linear fit or the weighted stacking
Geostack method.
Options: Least squares linear fit, Geostack
Least squares method:

Method for AVO attribute computation: = least squares.
Options: Least Squares, Robust Least Squares
Minimum acceptable correlation coefficient:

Method for AVO attribute computation: = least squares. When using the least squares linear fit method, a
minimum correlation coefficient can be specified. The correlation coefficient is a statistical measurement
of the fit of the data to the best-fit straight line. The correlation coefficient can range from 0.0 to 1.0, with
0.0 being a poor fit and 1.0 being a good fit. Computed correlation coefficients that fall below this
minimum value will result in the attributes at that sample being zeroed. A value of 0.0 results in no editing
of the attribute values. A value of 0.5 will result in strong editing of the attribute values.
Maximum incident angle (deg.):

The maximum angle for a linear fit of an AVO curve of reflection amplitude versus sin(theta)**2 is 25
degrees (Shuey, 1985). However, AVOA renders this as a parameter at the users discretion. AVOA will
mute the data that has an angle of incidence greater than this maximum angle.
Minimum incident angle (deg.):

Seismic data at less than 3 degrees tends to be noisy and of poor quality. AVOA renders this as a
parameter at the users discretion. AVOA will mute the data that has an angle of incidence that is less than
this minimum angle.
Space variant start and end times?

The user may select space variant or non-spatial variant start and stop times. The space variant times are
entered through a window file or a spreadsheet. The non-spatial variant times are constant throughout the
survey.
Start time (ms.)

Space variant start and stop times? = No. Enter the start time in milliseconds. The attribute stack
computations will start at this time.
250
End time (ms.)

Space variant start and stop times? = No. Enter the end time in milliseconds. The attribute stack
computations will end at this time.
Start and stop times

Space variant start and stop times? = Yes. This parameter appears if space variant start and stop times are
selected. The user can select a windows file or use the spreadsheet to enter start and stop times. Only one
start and stop time is allowed by CMP location. If the file contains additional times per CMP location,
they will be ignored.
Header to add to start time

The user may have previously selected a start and stop time and placed them into the trace header. These
header values may be retrieved and used as a bulk shift of the start and stop times.
Header to add to end time

RMS velocities:
This parameter specifies the velocity functions to use for the survey. The user may select a VIP file that
was previously built or may enter the time-velocity pairs in a spreadsheet. The velocities enter should be
the RMS velocities. The module will compute the interval velocities from the RMS velocities.
Matrix Type: RMSVEL
Velocity smoothing filter length (ms):

A time domain running average filter can be applied to smooth the velocity function. If the velocities are
in a VIP file then smoothing should be applied in the VIP program, but it can be applied here. The filter
length should be entered in milli-seconds.
251
Mudrock line slope (Geostack and fluid factor only)

Enter the mudrock line slope to be used in the fluid factor computation. The fluid factor is computed from
the mudrock line trend from Castagna (1993) and Hilterman (2001). This value is used for the fluid factor
trace only.
Vs/Vp = 1. mud slope-(mud intercept/mud slope)/Vp
dF = dVp/Vpa - mud slope(Vs/Vp)(dVs/Vsa)
Mudrock line intercept (Geostack and fluid factor only)

Enter the mudrock line intercept to be used in the fluid factor computation. The fluid factor is computed
from the mudrock line trend from Castagna (1993) and Hilterman (2001). This value is used for the fluid
factor trace only.
Vs/Vp = 1./mud slope - (mud intercept/mud slope)/Vp
dF = dVp/Vpa - mud slope(Vs/Vp)(dVs/Vsa)
Weighted Poissons Ratio? (Poissons Ratio only)

Select YES to compute a weighted Poissons Ratio:
PR = a * P + b * G.
The weight parameters will appear below. If you select NO then the normal Poissons Ratio is computed:
4/3 * (P + G).
This parameter is used for the Poissons Ratio trace only.
P-Wave weight
Enter the scalar (a) to apply to the P-Wave (P) in the equation:
PR = a * P + b * G.
Gradient weight
Enter the scalar (b) to apply to the Gradient (G) in the equation:
PR = a * P + b * G.
252
AVOCROSS
Module Description
Input Channels
Output Channels
Parameters
Module Description
AVOCROSS performs cross plotting of two different traces. The output from the modules is a stack trace
of the cross-plotted values. The module will accept AVOA attribute traces built by the module AVOA.
The module will also cross-plot traces from CMP gathers. An option is to produce a CGM plot of the
cross-plotted values within a given window of time.
A new option is to output a stabilized Intercept and Gradient. The filtering technique will reduce the noise
in the AVO gradient. Time windowed AVO analysis and hodogram technology, are utilized to compute a
new gradient trace that has reduced noise.
If the geometry database is not loaded for a run of this module then the parameter Maximum number of
bins per line: must be entered. The number of bins must be greater that the maximum number of bins per
line in the survey.
Input data to this module may be:
1. Attribute stacks computed by the AVOA module.
2. CMP gathers.
3. CMP X-BIN gathers.
The module will output eight different cross-plotted values:
1. Fluid, this is the fluid factor plot that was originally output. This is referred to as the Strength in the
literature.
2. Hodogram, product of the Strength and the Polarization Angle Difference.
3. Product of the Amplitude and the Polarization Angle Difference.
4. Polarization Angle Difference only.
5. Trend intercept from least squares computation.
6. Trend slope from least squares computation.
7. Stabilized Intercept
8. Stabilized Gradient
AVOCROSS now outputs multiple attributes in one run of the program. Through the menu, select the
attributes to output by highlighting the button next to the attribute. The attributes will be interleaved into
the output dataset. You will have to use the SELECT module to separate out specific attributes. Each
attribute has a specific value stored in the DIST header word.
253
DIST header = 21 Fluid

DIST header = 22 Hodogram
DIST header = 23 Amplitude * Polarization Angle
DIST header = 24 Polarization Angle
DIST header = 25 Intercept of the trend angle
DIST header = 26 Slope of the trend angle
DIST header = 27 Stabilized Intercept
DIST header = 28 Stabilized Gradient
When cross-plotting the AVOA attribute traces, the user selects which attributes to cross-plot. Any AVOA
attribute can be selected for either the horizontal or vertical axis of the cross-plot.
When cross-plotting CMP gathers, the user has the option to select the cross-plot traces by number. By
default, the module will cross-plot the first and the last traces in the ensemble. The trace number is
sequential starting from 1. The user also can enter the label for the horizontal and vertical axis in the CGM
plot.
AVOCROSS performs least-squares straight line fit or an alpha-trim mean fit to the data within a window.
The fit is performed within a time window specified by the user. A trend angle and intercept values are
computed for the fit. In the case of the alpha-trim mean, the intercept is always zero. The default is to use
the alpha-trim mean. When cross-plotting Vs/Vp or Intercept/Gradient (from AVOA), the computed
straight line should pass through the zero point. The alpha-trim mean option allows the user to control how
many anomalous points are removed from the computation before computing the trend angle. This is
useful in areas of gas, where the data points are anomalous; these points should not affect the trend angle
computation.
To get a good fit of the trend of the data, the analysis takes place in a time window using a mini-volume of
the input data. The use can select how many traces to use in the in-line and cross-line direction for the
trend analysis. Typically, you want to use a large amount of traces to establish a good trend line. A trend
angle and intercept are computed for each window and applied at the window center. All other samples are
interpolated between window centers. This causes the trend angle and intercept to slowly vary in time.
254
255
A popular AVO cross-plot is the Fluid factor (Strength) attribute computed using the P-wave (intercept) as
the horizontal attribute and the Gradient (slope) as the vertical attribute. The points of the trace when
entering or leaving the gas sand will show a marked deviation from the best-fit line when compared to the
surrounding (trend) points.
The module will output the trend intercept and trend slope from the least squares computation. The slope
angle is interpolated at each sample using the computed valued from the window centers.
Several new output plots have been added. A better approach for designing AVO indicators is to compute
an AVO Hodogram. In the Hodogram approach, the AVO particle motion is polarized along the axis trend
for non-anomalous events, and is polarized at angles different from the trend angle for anomalous events.
The hodogram incorporates the various effects of wave propagation and processing. In particular, the
polarization angle can be used to directly identify AVO anomalies.
256
The polarization angle is computed for every sample using a sliding time window of about to 1
wavelength long. The user enters the length of the wavelet in milliseconds. Typically, this can be the
dominant frequency of the data in the window of interest. This angle is compared to the trend angle, which
uses a much larger window in time and encompasses many surrounding traces.
The polarization angle difference is computed as:
Polar Angle Difference = Polar Angle - Trend Angle.
The module will output the Hodogram, which is the product of the strength * polarization angle
difference. Another output is the product Amplitude * polarization angle difference. The amplitude is the
distance from zero crossing to the sample being evaluated. The module will also output the polarization
angle difference in degrees.
A new option is to output the stabilized intercept and stabilized gradient. This filtering technique can
reduce the noise in the AVO gradient while leaving the intercept most unaltered. The input gradient should
be on the vertical axis and the input intercept on the horizontal axis. The trend angle is computed. The
intercept/gradient pairs are rotated clock-wise by the trend angle. The polarization angle is computed using
least squares from the rotated data. The gradient value is re-computed using the best-fit line from the
polarization least squares. Given the intercept value, the new gradient is selected along the best-fit line.
The new intercept/gradient pairs are rotated back the original position. The intercept/gradient are output if
the options are selected. See the reference below.
The user has the option to make CGM plots of the cross-plotted data. The plots will look similar the above
graph. The blue dots will represent the cross-plotted values within the window for the current trace (trace
samples). The red dots will represent the cross-plotted values of the surrounding traces (volume samples).
The surrounding traces are represented by the values chosen for the mini-volume.
References
Castagna, J.P., Swan, H.W., Foster, D.J., Framework for AVO gradient and intercept interpretation, 1998,
Geophysics, 63, 948-956
Keho, T.H., The AVO hodogram: Using the polarization to identify anomalies. SEG 2000 Expanded
Abstracts.
Castagna, J.P., Mahob, P.N., The use of polarization attributes to identify anomalies: AVO hodograms.
SEG/San Antonio 2001 Expanded Abstracts.
D.N. Whitcombe, M. Dyce, Stabilizing the AVO Gradient, SEG 74 th International Exposition October
2004.
TYPE
Queue
257
Input Channels
1. Previous process: Required connection from previous process - GCI data type.
Output Channels
1. Output: Required connection to next process - GCI data type.
2. Dataset for CGM plot: Required connection to dataset - CGM data type.
Parameters
Data input type:
Select the type of input data that we are going to cross-plot. If you select the AVOA attributes then the
program expects the input to be the output from AVOA. If CMP gathers is selected, then the program
expects the input to be CMP gather data. It will take the first and last trace of the CMP to perform the
analysis.
AVOA attributes to use as the horizontal values in the least squares best-fit line.
Default .....:AVOA Attribute Stacks
Name ........:atype
Type ........:Option list of single pick
Options .....:
AVOA Attribute Stacks
CMP Gathers
Horizontal axis attribute:

Select the AVOA attributes to use as the horizontal values in the least squares best-fit line.
Default .....:P-Wave (Intercept)
Name ........:ahopt
Options .....:
P-Wave (Intercept)
Gradient (Slope) or S-Wave (Geostack)
Restricted Gradient
Pseudo Poissons-Ratio
Pseudo S-Wave
Potential Hydrocarbon
Restricted P-Wave
258
Correlation Coefficient
Statistics
Fluid Factor
Vertical axis attribute:

Select the AVOA attributes to use as the vertical values in the least squares best-fit line.
Default .....:Gradient (Slope) or S-Wave (Geostack)
Name ........:avopt
Options .....:
P-Wave (Intercept)
Gradient (Slope) or S-Wave (Geostack)
Restricted Gradient
Pseudo Poissons-Ratio
Pseudo S-Wave
Potential Hydrocarbon
Restricted P-Wave
Correlation Coefficient
Statistics
Fluid Factor
Horizontal axis trace number

If the CMP gather input type was selected then enter the trace index number to use for the horizontal axis.
The default is to use the First Trace in the ensemble. The index number starts at 1 and increments
sequentially until the end of the ensemble. Example: User selects 1 for the horizontal axis and 10 for the
vertical axis. The module will then cross-plot the 1 trace in the ensemble against the 10 trace in the
ensemble.
Default .....:"First trace"
Name ........:hopt
Type ........:Integer
Min .........:1
Max .........:
Label for horizontal axis

If the CMP gather input type was selected then enter the label for the horizontal axis. This string will be
placed on the horizontal axis of the CGM plot.
Default .....:First Trace
Name ........:hlab
Type ........:String
259
Vertical axis trace number

If the CMP gather input type was selected then enter the trace index number to use for the vertical axis.
The default is to use the Last Trace in the ensemble. The index number starts at 1 and increments
sequentially until the end of the ensemble. Example: User selects 1 for the horizontal axis and 10 for the
vertical axis. The module will then cross-plot the 1st trace in the ensemble against the 10th trace in the
ensemble.
Default .....:"Last trace"
Name ........:vopt
Min .........:1
Max .........:
Label for vertical axis

If the CMP gather input type was selected then enter the label for the vertical axis. This string will be
placed on the vertical axis of the CGM plot.
Default .....:Last Trace
Name ........:vlab
Data output options:

The module will output six types of data as stacked sections. Any number of attributes can be output to the
dataset. The attributes will be interleaved into the output file. Use the SELECT module to output a specific
attribute. Use the DIST header word to retrieve a specific attribute (see list above).
The Fluid option is the default and is what the module output originally as the fluid factor. The Fluid is
referred to as the strength in the literature. Three new outputs have been added using the polarization angle
difference. The Hodogram is the product of the strength * polarization angle. Another output is the
product of the amplitude * polarization angle. The Polarization Angle only is measure in degrees.
Default .....:Fluid
Name ........:aout
Type ........:Option list of multiple pick
Options .....:
Fluid
Hodogram
Amplitude*Polarization Angle
Polarization Angle only
Trend Intercept
Trend Slope
Stabilized Intercept
Stabilized Gradient
260
Cross-plot fitting method:

Select the method to perform a straight line fit. The alpha-trim mean method computes a trend angle and
an intercept of 0,0. The alpha-trim mean method allows you to remove the upper and lower means using a
percentage. This should allow anomalous values to be removed before computing the angle . The least
squares method computes a trend angle and intercept to best fit the data.
Default .....:Alpha-Trim Mean
Name ........:lstsq
Options .....:
Standard Least Squares
Alpha-Trim Mean
Trimmed mean (%):

Select the percent of data points to be removed before the median computation. The upper and lower
percentage of mean points is removed. The mean is computed for each data point. The values are then
sorted from lower to upper. Then the percentage of upper and lower points is removed before the median
value is computed. If you select 100 percent, the median value of the data points is selected. If you select
10 percent, the lower 10 percent are removed and the upper 10 percent of the mean values are removed.
Default .....:10
Name ........:trim
Min .........:0
Max .........:100
Wavelet length (ms)

The wavelet length is entered in milliseconds. The size of the time window to compute the polarization
angle should be to 1 wave period. Typically, this can be the dominant frequency of the data in the
window of interest.
Default .....:35
Name ........:wave
Min .........:1
Max .........:
Start time (ms)

Specify the start time in milliseconds to begin the computation. This parameter and the end time below
constitute the length of the trace that is used for the analysis.
261
Default .....:0
Name ........:dstrt
Min .........:0
Max .........:
End time (ms)

Specify the end time in milliseconds to stop the computation. This parameter and the start time above
constitute the length of the trace that is used for the analysis.
Default .....:"Record length"
Name ........:dend
Min .........:0
Max .........:
Maximum number of bins per line

Enter the maximum number of bins for any line that will be encountered. The default is to get this value
from the database. The only time that you might want to change this value, is if you are cross-plotting
some data that was not built within this line. The module needs the geometry built for this line to get
information. If you import data without performing geometry, you will have to set this value.
Example: You get a SEGY file from an external source that you want to cross-plot, but you have not built
a database for this. In this case, you must enter the maximum number of bins per line for the module to
work properly.
Default .....:"Get From DB"
Name ........:nbin
Min .........:1
Max .........:
Window length to use for best-fit line computation (ms)

The best-fit line computation can be limited to a window of the data. The trace is broken into window
lengths and the computation is performed in each window starting at the start time and ending at the end
time.
Default .....:500
Name ........:window
Min .........:0
Max .........:
262
Window overlap (%)

A window overlap will smooth changes at the window boundaries. The default is to overlap the windows
at 10%. The values in the overlap zone will be averaged.
Default .....:10
Name ........:overl
Min .........:0
Max .........:100
Computed value measured from the

The computed values is the distance from the best fit line to the actual sample value. This value can be
measured in the perpendicular, vertical or horizontal sense. Please see the above explanation for the
measurement of this value.
Default .....:Perpendicular
Name ........:ameas
Options .....:
Perpendicular
Vertical
Horizontal
Inline bins to include in best-fit volume analysis (odd number)

A mini-volume of data may be included in the least squares computation. This should increase the
reliability of the computation. Bin traces surrounding the current bin being computed are included in the
least squares computation. This value must be an odd number (i.e. 1,3,5,7). Enter the number of
surrounding bins to include in an in-line direction.
Default .....:5
Name ........:iline
Min .........:1
Max .........:
Cross-line bins to include in best-fit volume analysis (odd number)

A mini-volume of data may be included in the least squares computation. This should increase the
reliability of the computation. Bin traces surrounding the current bin being computed are included in the
least squares computation. This value must be an odd number (i.e. 1,3,5,7). Enter the number of
surrounding bins to include in a cross-line direction.
263
Default .....:5
Name ........:cline
Min .........:1
Max .........:
Generate QC plots?
Select YES to generate QC plots. The plot will be an XY graph of the horizontal and vertical variables.
The best-fit line will be drawn through the points. The trace samples will be blue circles and the other
mini-volume points will be red X.
Default .....:No
Name ........:plot
Options .....:
Yes
No
Plot line, cmp, time:

Use the matrix editor to enter the plot line, cmp, and times. Enter the line number and the CMP number
and then up to 10 times (milliseconds) per analysis location.
Default .....:
Name ........:name
Type ........:Matrix
Matrix type .:AVOC
Horizontal width of plot (in.):

The horizontal width of the plot in inches. The plot can be shrunk or zoomed but the best resolution will
be at the selected plot size.
Default .....:8.0
Name ........:hwidth
Type ........:Float
Min .........:0.
Max .........:9.
Vertical width of plot (in.):

The vertical width of the plot in inches. The plot can be shrunk or zoomed but the best resolution will be at
the selected plot size.
264
Default .....:6.0
Name ........:vwidth
Type ........:Float
Min .........:0.
Max .........:7.
Maximum plot value:

On default the module will locate the maximum amplitude of the data for the plot maximums. The user
may select a different maximum plot value here.
Default .....:"Computed"
Name ........:val
Type ........:Float
Min .........:
Max .........:
AUTHOR
Created on Jun 8, 2005 by Steve Jensen
265
AVOSCALE
Module Description
Input Channels
Output Channels
Parameters
Module Description
AVOSCALE corrects seismic data for the slowly varying AVO background behavior. An angle and time
dependent scalar is applied for each seismic data sample.
For each seismic data sample, a Vs (shear velocity) is computed using the input interval velocity (Vp) and
Castagnas mudrock relation:
Vp = Vs * k + c (velocities in meters)
Some common k and c values:

c = 1360 m/s k = 1.16 in-situ mineralogy.
c = 1064 m/s k = 1.24 sandstone
c = 1126 m/s k = 1.30 shale
The module allows the user to change the mudrock intercept (c) and the mudrock slope (k). This will
allow an accurate scalar to be computed for different rock types.
The module requires a RMS velocity matrix to be input. The RMS velocity matrix is converted to interval
velocity and interpolated over the survey. This gives the input Vp values used to compute the Vs value at
each sample.
We start with Shueys equation to compute the reflection coefficient:
R(angle) = A + B * sin^2(angle)
Castagnas mudrock equation allows us to compute the Vs using Vp, mudrock slope and the mudrock
intercept.
Vs = [ Vp - 1360 ] / 1.16
Using the above relations we can compute the following:

A = 5/8 * (delta-Vp / Vp )
B = 4/5 * A * [ 1 - 8k*(Vs/Vp) - (Vs/Vp)**2 ]
Scalar = B * sin^2(angle) + 1
266
This gives an angle dependent and time dependent (through Vp) background AVO behavior. If we use
Vs/Vp = 0.5, then the result would be:
R(angle) = A * [ 1 - 2.16 * sin^2(angle) ]
References
JP Castagna, ML Batzle, RL Eastwood, "Relationships between compressional-wave and shear-wave
velocities in clastic silicate rocks", Geophysics vol. 50, No. 4, p571-581
JP Castagna, ML Batzle, TK Kan, "Rock Physics - The link between rock properties and AVO response",
Offset-Dependent Reflectivity - Theory and practice of AVO analysis.
Input Channels
1. Input: Required connection from previous process GCI data type.
Output Channels
1. Output: Required connection to next process GCI data type.
Parameters
Mudrock line slope
Specify the mudrock line slope. This slope is used to compute the Vs (shear velocity) using the input Vp
(interval velocity and Castagnas mudrock equation:
Vp = intercept + slope * Vs
Mudrock line intercept (m/s)

Specify the mudrock line intercept in meters/second. The intercept is used to compute the Vs (shear
velocity) using the input Vp (interval velocity) and Castagnas mudrock equation.
RMS velocities:
Specify the RMS velocity matrix to use as the Vp (interval velocity) information. The RMS velocity
matrix is converted to interval velocity and interpolated over the whole survey.
Matrix Type: RMSVEL
267
AZIMVTRY
AZIMVTRY - HTI LMO trials.
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module AZIMVTRY computes a semblance cube for refraction arrival azimuthal velocity analysis. The
linear moveout correction velocity is given by
where V slow is the slow LMO velocity, V fast is the fast LMO velocity, s is the azimuth of the slow
velocity axis and &#981 is the source-receiver azimuth. The axes of the output cube are V slow in
HDR(41), V fast in HDR(42) and s is time. Sequential indexes for V slow and V fast are in HDR(43) and
HDR(44). The module prints values to use in module DISPLAY to show the proper azimuth values on the
time axis.
Input Channels
Output Channels
Parameters
268
Number of fast velocity trials

Must be an odd number.
Number of slow velocity trials

Must be an odd number.
Fast velocity trial reference

Slow velocity trial reference
Fast velocity trial increment
Slow velocity trial increment
Azimuth trial increment
Semblance window length (ms)
Semblance window center time after LMO (ms)
Length of scale window (ms)
Limit by offset
Offset pass minimum
Required if Limit by offset equals Yes.
Offset pass maximum

Required if Limit by offset equals Yes.
269
BINLINE
Module Description
Input Channels
Output Channels
Parameters
Module Description
BINLINE re-locates original midpoints to be within the CMP cloud for 2D crooked lines. The output is a
matrix of CMP bin locations to be used in module STATION.
Parameters
Number of shots to smooth over
Smoothed shot locations are initially used to determine the CMP cloud center. The smoother removes the
high frequency changes in the shot line locations. Some experimentation may be required for best results.
The default value of 5 shots may be too small for weakly crooked lines.
Output midpoint matrix

Module STATION has the option of inputting CMP coordinates from a matrix to use in geometry
computations. The output of BINLINE will be in this matrix.
Matrix Type: MIDPOINT
Pick the type of output CMP line

Three options are available for CMP output location control. The first, "Between source and receiver",
mimic the CMPLINE output. The second, "Through the midaxis", adjusts the initial midpoint locations
estimates to be through the centroid of the CMP cloud. The last option, "Maximize fold", adjust the CMP
locations so as to maximize fold for each output CMP. This last option may be the preferred one so as to
avoid zero fold CMPs.
Options: Between source and first channel, Through the midaxis,
Maximize fold
Do you want the CMP points to be uniformly distributed?

This options locates the output CMPs equally spaced.
270
Distance Between consecutive CMPs

Desired output CMP spacing.
Memory Pad
Extra memory for extending arrays.
271
BINREAD
Module Description
Input Channels
Output Channels
Parameters
Module Description
BINREAD is a module that be used to input multi-dimensional binary formatted data to SeisUP. For
instance, this module can used to read RSF or SEP formatted data sets from the Madagascar or SEPlib
formats.
Parameters
Directory name
Enter the whole path to the directory containing the binary file you wish to import.
File name
Enter the file name of the file you wish to import.
Data type
Select the input binary data format.
Options: Float, Integer, Complex
Drop single valued axis from sort keys?

By option, BINREAD can drop any axis that has only one element. This can be useful when trying to view
a data set with the module DISPLAY.
Axis 1 number.
Axis 2 number.
272
Axis 3 number.
Axis 4 number.
Axis 5 number.
Enter the number of elements for the respective axis. For Madagascar data sets this is the n1, n2, ... value.
Axis 2 origin
Axis 3 origin
Axis 4 origin
Axis 5 origin
Enter the axis origin. For Madagascar data sets this is the o2, o3, ... value. For the fastest axis (1), the
origin is always set at zero to conform to SeisUP standards.
Axis 1 increment
Axis 2 increment
Axis 3 increment
Axis 4 increment
Axis 5 increment
Enter the axis increment. For instance, if the axis is of MBIN type, enter the MBIN ordinal increment. For
Madagascar data sets this is the i1, i2, ... value.
Axis 1 label
Axis 2 label
Axis 3 label
273
Axis 4 label
Axis 5 label
Enter the axis label that describes the particular axis.
Options: Not used, Time, Depth, CDPN, DIST, DMODIST, FCSN, FSPN,
MBIN, MLIN, MSBN, MSLN, OIDN, RSBN, RSLN, SDPN, SGEN, SBIN, SLIN,
SSBN, SSLN, SSPN, TIM1, TIM2, TLSN
274
BLIP
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module can be used to overlay some sort of attribute over a seismic section. For instance a user
should be able to overlay elevations that have been converted to time on top of the seismic section. This
module will create a blip or event with a user specified amplitude and duration at the time specified in the
trace header word defined.
Input Channels
Output Channels
Parameters
Get blip time(ms) from header
Options: none, CDPN, DIST, FCSN, FSPN, MBIN, MLIN, MSBN, MSLN, OIDN,
TLSN, other
Blip time header index

Required if Get blip time(ms) from header equal other.
Length of the blip(ms)
275
Amplitude of the blip
276
BSSE
Module Description
Input Channels
Output Channels
Parameters
Module Description
BSSE extracts signal from background random noise on pre-NMOed ensembles using rigid hyperbolic
beams. An event of a shot record will follow a flat trajectory at near offsets and a steep trajectory at far
offsets making a search for a best fit hyperbola over different velocities necessary (for every sample).
When that best fit is found, a new output sample is computed from weighting samples on either side of the
output sample. Best results are obtained after application of Refraction (Datum) and auto statics.
Input Channels
Output Channels
Parameters
Beam stack option
The hyperbolic fit may be evaluated with two possible stacking options If the data has no spikes or large
noise bursts the Standard option is preferred. However, if the data is highly contaminated with large noise
features the Diversity option may give a better result.
Options: Standard, Diversity
Diversity beam height (samples)

Used if Beam stack option is Diversity. The Diversity option computes a stack over a hyperbolic window
(beam). The best height of the beam will be frequency dependent. Typically 5 samples for high frequency
(dynamite) data and more for low frequency events.
277
Minimum Velocity
To match the curvature of events at high source-geophone offsets a velocity as low as 5000 ft/sec (1500
m/s) may be needed in marine work. This minimum velocity is usually higher in land data.
Maximum Velocity
To match the event curvature at near offsets a high velocity is needed. Values such as 20000 ft/s or higher
may be needed.
Velocity Increment
The velocity scan to find the best fit will increment by this value. Typically somewhere between 50 to 200
will suffice.
Beam width (traces)

This value specifies the beam width for hyperbolic match. A minimum value would be 5. The greater this
value, the stronger the signal cleanup.
Weight option
There are two sample weight options to construct the output sample from the input samples on the best
beam. The exponential option weights surrounding samples by e raised to a negative power inversely
proportional to distance separation squared. This means that the original sample of interest gets the most
weight. The Equal option computes a standard average stack of surrounding samples. This will result in a
stronger signal cleanup.
Options: Exponential, Equal
Include negatively curved beams

Specifying YES for this parameter will include hyperbolic fit measurement of convex and concave
hyperbolas. This is necessary to match event trajectory in complex structure datasets.
Number of threads
The more threads used (up to the number of CPUs) the faster the execution.
278
CAZM
Module Description
Input Channels
Output Channels
Parameters
Module Description
CAZM is a module for common-azimuth processing. It can group the input traces into different
common-offset and common-azimuth bins. The offset is the distance between the source and receiver
while the azimuth is the angle between them. To be able to create offset and azimuth bins, this program
will need parameters for spacing. Figure 1 is a 2-D stacking diagram chart showing the meaning off the
offset interval. Figure 2 is a polar plot that shows both the meaning of both offset and azimuth. The polar
plot also shows how by default CAZM will map azimuths using reciprocity from the lower half of the
circle to the upper half. Using reciprocity will allow more traces to be grouped into a common-offset bin
and represent all traces with fewer azimuth bins. Offset bin center values will be placed in trace header
DMODIST and azimuth bin center values will be placed in trace header BINAZIM.
Figure 1. 2-D stacking diagram showing the meaning of an offset interval
279
Figure 2. Polar plot showing azimuth around the circumference of the plot. The radial circles represent
offset boundaries. In this example three offset vectors are shown. The green vector is an example whereby
using reciprocity allows one to map to the upper half of the azimuths by shifting the azimuth by 180
degrees as is shown by the purple version of it.
CAZM has multiple options to bin offset as follows:
1. Fixed increment: With this option, evenly spaced offset bins are defined by a minimum, maximum
and common offset increment. In Figure 2. above the offset increment is an example of a fixed
increment.
2. Fixed area: Notice in Figure 2 the area defined by
, where r are different offset
boundaries, that the area increases as offset increases. Using this option allows the offset increment to
increase by a square root function. See Figure 3 for an example of Fixed Area. Be forewarned though
the fold that most surveys within offset bands will increase with a square root function till you reach
a certain dominate offset then quickly die out. In this case do not use the absolute maximum offset an
instead use the dominate offset and then using this as a guide create a user specified one mentioned
below.
3. User specified: Variable or custom spaced offset bins are created by defining a matrix of start and
end offset values for each offset bin. Currently overlapping bins are not allowed.
4. Optimal: Choosing this option will not actually bin the offsets but rather create a "User specified"
matrix for another run. This matrix is created by collecting all offsets over the survey, sorting them,
then creating equal fold for each offset by evenly dividing the offsets by the user specified number of
desired optimal offset bins.
280
Figure 3. Example of equal area. Notice the area between each offset band has equal area.
Q.C Plots
CAZM has the following Q.C. plots:
1. Auxiliary output set: If this output channel is connected, CAZM will output a fold data set whereby
the time axis is azimuth and the horizontal or trace ensemble axis is the offset cell center. Ideally one
should input this data into a Rose diagram plot program but for quick check one an display this with
the DISPLAY module.
2. Ascii job status: The execution status will contain the following:
1. Histogram showing the fold count for each azimuth bin. The count is over all offsets but within
each azimuth bin.
2. Histogram showing the fold count for each offset bin. The count is over all azimuths but within
each offset bin.
3. Offset bin widths. This plot is only shown at the end of the job and only when using Optimal
offset binning.
Input Channels
281
Output Channels
1. Next process: Optional connection to next process GCI data type.
2. Offset/azimuth fold: Optional connection to dataset GCI data type. This data set will contain the
fold for each common-offset (horizontal or ensemble axis) and common-azimuth (vertical or time
axis)
Parameters
Offset increment method
Select the desired binning method for offsets. See above for a description.
Options: Fixed increment, Fixed area, User specified, Optimal
Minimum offset bin

Enter the minimum offset boundary bin value.
Maximum offset bin

Enter the maximum offset boundary bin value.
Offset increment
Enter the fixed offset increment between offset bin centers. This parameter is only available for the Fixed
increment binning method.
Number of offset bins

Enter the number of desired offset bins. This parameter is only available for the Fixed area and Optimal
binning methods.
Offset bins
When using the User specified binning method, enter a matrix containing the minimum and maximum
offset boundary value for each offset bin. Currently CAZM does not support overlapping offset bins.
Matrix Type: COFFOFF
282
Output optimal offset bins

Enter an output matrix name for CAZM to output the calculated optimal offset bin values.
Minimum azimuth bin

Enter the minimum azimuth boundary azimuth bin value.
Maximum azimuth bin

Enter the maximum azimuth boundary azimuth bin value.
Azimuth increment
Enter the fixed azimuth increment between azimuth bin centers.
Use reciprocity?
Select Yes to use reciprocity and attempt to map azimuths outside the minimum and maximum above to
within them using plus or minus 180 degrees addition. Also see example above.
Verbose print-out?
Select Yes for more detailed print-out in the execution status.
283
CCPBIN
Module Description
Input Channels
Output Channels
Parameters
Module Description
Theory
Seismic reflection data traces are normally "binned" according to their common reflection points assuming
a flat earth model. The term CDP suggests this model. For common PP reflection data, the source-receiver
mid-point, or CMP, is the usual bin location. However, for PS reflection data, the proper CDP point, or
reflection location, is the point at which the down-going P-wave energy reflects and converts to up-going
S-wave energy. This is referred to as the "CCP" or Common Conversion Point. The actual location of this
point is dependent upon the Vp/Vs ratio of the entire overburden column above the converting layer. The
actual CCP moves laterally between source and receiver as the depth and Vp/Vs ratio changes. For the
generation of brute stacks and computation of simple automatic residual statics, the asymptotic
approximation to the true CCP can be used. Module CCPBIN computes this asymptotic conversion point,
Xc = rg / (1 + g),
where Xc is the distance from the shot location to the point directly above the conversion point, r is the
total source-receiver offset distance and g is the average Vp/Vs value down to the reflector of interest.
This approximation is more accurate for small offset/depth ratios. The approximation can potentially
introduce artifacts into the PS stacked section. Imaging of PS data sets can be more properly accomplished
using a PSTM algorithm which allows the use of separate velocity fields for source and receiver travel
paths, P-waves and S-wave respectively. A more accurate image may be obtained using a full PSDM
algorithm which also supports dual velocity field migration.
284
CCPBIN computes the relative asymptotic conversion point given the source and receiver x and y
coordinates and the coded Vp/Vs ratio. The MBIN, MLIN, MCX, MCY, SDPN, and EC for the bin closest
to the actual computed conversion point is placed in the trace header of the output trace. No modification
is made to the data base. Module STATION must have been run prior to CCPBIN to create the bin grid. It
should be noted that the coverage geometry for PS data is rather different from PP data coverage. The
coverage point moves toward the receiver location. Care should be taken in designing a grid to use for the
CCP binned data set. The same bin grid will not be optimal for both PP and PS data for the same surface
recording geometry.
References
Fromm, G., Krey, Th.. and Wiest, B. 1985. Static and dynamic corrections. In:Seismic Shear Waves, G.
Dohr ed.), 191-225. Handbook of Geophysical Exploration, Vol. 15b. Geophysical Press.
Tessmer, G. and Behle, A., 1988, Common reflection point data-stacking technique for converted waves;
Geophys. Prosp., 36, 671-688.
Input Channels
285
Output Channels
Parameters
Vp/Vs value for binning
Enter the Vp/Vs ratio that is to be used in binning the data. If no measurement of Vp/Vs is available, a
value of 2.0 is usually a reasonable first guess.
Modified on 29 May, 2003 by John Stevens.
286
CENSUSDB
Export attributes to CENSUS formatted ASCII file.
Module Description
Module Description
The CENSUS formatted ASCII file created by this module will written into your home directory.
287
CHKNAN
Module Description
Input Channels
Output Channels
Parameters
Module Description
CHKNAN will filter out NaNQ and NaNS floating point numbers from the data. NaNQ and NaNS
floating point numbers are Not a Numbers that usually result from a programming problem such as a
divide by zero or a floating point overflow. If you detect a NaNQ or NaNS floating point number and you
can detect that the number was created by a SeisUP(tm) module, please call GeoCenter Inc. so that we can
fix the problem. If a NaNQ or NaNS is in your data the following can result:
1. The trace will look like a dead trace but flagged as a live trace.
2. A multi-trace process such as KFIL will spread NaNs to neighboring traces.
3. Any mathematical operation to a NaN will result in a NaN.
Input Channels
Output Channels
Parameters
Print NANQ samples?
If Some is selected, only the first NANQ detected on any trace will be printed.
Options: All, Some, None
288
CLIP
Module Description
Input Channels
Output Channels
Parameters
Module Description
CLIP will replace an amplitude that exceeds a user specified amplitude with a user specified value.
Input Channels
Output Channels
Parameters
Amplitude Threshold level
Clipped amplitude level
Clip window start time (ms.)
Clip window end time (ms.)
289
CLUSTEST
Module Description
Parameters
Module Description
This module will run tests on clustered parallel machines. Tests run include memory, tcp/ip socket, math,
and thread tests. All test information is written to the status file.
The node list resides in the QEDTOP/lib/nodes/<name> file. This is the standard way that GeoCenter
cluster modules operate. The user has to build this file with the node names. The user may specify a subset
of these nodes using a MPISNODE matrix. A typical node file might look like this:
Colorado1 sys=linux cpu=1
Colorado2 sys=linux cpu=1
The first column is the machine name. The name must be the same name you would use for logging into
that machine. The second column is the system type and points the software to the correct directory to find
binaries. The third column is the number of cpus for each node.
The user specifies how much memory to allocate on the head and each node. The memory is then fully
written to and read back to check for errors. At the start of the memory test, the module computes the
physical and available memory for each node and displays the results.
The module does a data transfer test on each node. This involves sending a megabyte of data to each node
and then testing the contents of the data for errors. The node then sends the data back to the master where
the data is tested again for errors. During this time threads are fired up depending on the number of cpus
specified in the menu. The whole data transfer test is timed so the user can see if any nodes have some
type of network delay problem.
Parameters
Number of Nodes in the Cluster
Specify the number of nodes to run in this cluster test. The node names are taken from the
QEDTOP/lib/nodes/<name> file.
Number of Processors on each Node of the Cluster

If each node has more than one cpu, please specify the number of cpus for each node. A thread test will be
done on each cpu.
290
Compute node list

Specify the QEDTOP/lib/nodes/<name> file that we are using to get node names.
Custom sub-node list

Specify a subset of the node list if you want to run on specific nodes.
Matrix Type: MPISNODES
Max. available memory on Master Node (MB)

Specify the amount of memory to allocate on the master node for the memory test in megabytes. At the
start of the memory test, the module will find out the amount of physical and available memory on the
machine.
Max. available memory on each Compute Node (MB)

Specify the amount of memory to allocate on each node for the memory test in megabytes. At the start of
the memory test, the module will find out the amount of physical and available memory on the machine.
291
CMPLINE
NAME
CMPLINE - Derive CMP crooked line coordinates
DESCRIPTION
This module was designed to help marine data with severe feathering. It can also be used on 2-D land data.
TYPE
Stand alone
INPUT CHANNELS
None
OUTPUT CHANNELS
None
PARAMETERS
Number of shots to smooth over
Default .....:5
Name ........:nsmooth
Min .........:0
Max .........:
Output midpoint matrix

Default .....:
Name ........:Mname
Matrix type .:MIDPOINT
292
Is the acquisition from a streamer?

Default .....:Yes
Name ........:streamer
Options .....:
Yes
No
AUTHOR
Created on Oct 5, 2004 by David Dunbar
293
CNSGEOM
Module Description
Input Channels
Output Channels
Parameters
Module Description
CNSGEOM can be used to apply geometry to trace headers from the CENSUS database. Currently
CNSGEOM will read QCGT version 401 formatted files. When creating the QCGT file use the following
options:
1. The coordinates should not be moved to the bin center.
2. Output good traces only.
3. Output prime and flex traces.
Input Channels
Output Channels
Parameters
3-D restart?
Select "Yes" if you are adding more lines to the database.
Directory for the QCGT files

This directory must be the full path name for the location of the QCGT file(s).
Receiver trace header(s) for matching

This is the trace header to use for matching the receiver number in the QCGT file and trace being read. If
RSBN & RSLN is selected, the RSLN (receiver station line number) shifted left and combined with the
RSBN (receiver station bin number). In addition, the combined number is truncated to the right most
seven digits. For example, RSBN 1234 and RSLN 4321 will combine to the number 211234. The number
294
is truncated because CENSUS can only store significant digits for the receiver number.
Options: RSBN & RSLN, FCSN
Number of traces per shot record

Required if 3-D restart? = No.
Index in QCGT for shot elevation

If an attribute in the QCGT file for the shot elevation is available, enter the attribute index starting from
on. If not supplied, the default for the source spreadsheet will be used.
Index in QCGT for shot uphole time

If an attribute in the QCGT file for the shot uphole time is available, enter the attribute index starting from
on. If not supplied, the default for the source spreadsheet will be used.
Index in QCGT for shot depth

If an attribute in the QCGT file for the shot depth is available, enter the attribute index starting from on. If
not supplied, the default for the source spreadsheet will be used.
Index in QCGT for geophone elevation

If an attribute in the QCGT file for the geophone elevation is available, enter the attribute index starting
from on. If not supplied, the default for the station spreadsheet will be used.
Maximum number of flex traces per shot

This is the number extra traces created per shot due to flexible binning.
Line name in trace header?

Line name
Required if Line name in trace header? = No or 3-D restart? = No. This is the line name in the CENSUS
database. If the line name is in the trace header, this parameter is required to get area parameters.
Use Census midpoint grid?

Select Yes to use the overlay midpoint grid defined in the QCGT file. Select No to enter a user defined
midpoint grid.
295
Azimuth angle for grids

Enter the survey angle in degrees. This angle is used to rotate the coordinates so that a horizontal grid may
be established. The azimuth angle is the angle of the survey from the X-axis (from east to north). A
positive angle will rotate the survey clockwise. Proper rotation will result in less computations and fewer
bins.
Inline midpoint interval

Enter the midpoint interval in feet or meters along the X-axis after rotation of the survey.
Crossline midpoint interval

Enter the midpoint interval in feet or meters along the Y-axis after rotation of the survey.
Midpoint X coordinate origin

A default origin will be calculated from the minimum midpoint X and Y coordinates in the survey.
Midpoint Y coordinate origin

Inline midpoint number at the origin
This will be the first midpoint bin number.
Crossline midpoint number at the origin

This will be the first midpoint line number.
Number of inline midpoint numbers

The default will be to calculate the number of midpoint bins from the maximum midpoint X and Y
coordinates.
Number of crossline midpoint numbers

Receiver specification by
Choose Grid to overlay a receiver grid over the survey. Coordinates to specify the actual coordinates for
live receiver. Usually Grid is chosen for a marine survey while Coordinates are usually used when a
SEG-P1 file is available.
Options: Grid, Coordinates
296
Stations
This matrix will define the coordinates for every live receiver in the survey. If you depend on the final
receiver coordinates from the QCGT file, enter pre-planned coordinates for all possible receivers.
Matrix Type: STATION
Average inline receiver interval

Average crossline receiver interval
Print receivers?
Select Yes to print the X , Y, elevation, geophone interval, change in elevation, and azimuth from the
previous receiver. This option can only be used if the coordinates are specified in the station matrix.
Update station file with Census coords.?

If the receivers are specified by coordinates, select Yes to update the station spreadsheet with the
coordinates read from the QCGT file. If an update occurs, CNSGEOM will print out a line in the
execution listing to indicate the receiver coordinate has changed.
Inline receiver interval

Enter the receiver interval in feet or meters along the X-axis after rotation of the survey. Required if 3-D
restart? = No.
Crossline receiver interval

Enter the receiver interval in feet or meters along the Y-axis after rotation of the survey. Required if 3-D
restart? = No.
Receiver X coordinate origin

A default origin will be calculated from the minimum receiver X and Y coordinates in the survey.
Receiver Y coordinate origin

297
Receiver number at the X origin

This will be the first receiver bin number. Required if 3-D restart? = No.
Receiver number at the Y origin

This will be the first receiver line number. Required if 3-D restart? = No.
Number of inline receiver stations

The default will be to calculate the number of receiver bins from the maximum midpoint X and Y
coordinates. Required if 3-D restart? = No.
Number of crossline receiver stations

298
COFF
common-offsets
Module Description
Input Channels
Output Channels
Parameters
Module Description
COFF is a module for common-offset processing. It can group the input traces into different
common-offset bins. The bin offsets are defined by the parameters:
1. Evenly spaced offset bins defined by the parameters Minimum common-offset, Maximum
common-offset, Common-offset increment, and Common-offset bin width. As the common-offset bin
width can be larger than the offset increment, the same input trace can be grouped into different
common-offset bins.
2. Variable or custom spaced offset bins defined by the parameter Offsets bins. The user must build a
matrix of start and end offset values for each offset bin. The offset bin may overlap adjacent offset
bins to allow the same input trace to be grouped into different offset bins.
Header word DMODIST is used to store the bin offset value. If all the other parameters are defaulted, this
module is similar to DMODIST except that an input trace can be duplicated to the output if the
common-offset bin width is larger than the offset increment. The empty common-offset bin can be filled
with a seismic trace which is either borrowed from the nearest neighbor or created by the NMO stack, so
299
that there is no hole on the common-offset section. Caution must be used to do so, since it may copy the
same trace many times or create wrong header information.
If parameter Apply partial stack is turned on, COFF will stack the traces grouped into the same
common-offset bin. The bin offset is assigned to header word DIST and the source and receiver
coordinates are adjusted accordingly. The number of traces summed is stored to header word FOLD. The
rest of the header values will be the average values of all the traces in the partial stack. The NMO
correction should always be applied before the partial stack. If the inverse NMO correction is applied after
the partial stack, this procedure performs NMO regularization on prestack data. The partial stacked data
can not be sorted back to common-shot or common-receiver. Any surface-consistent processing should be
run or applied before the partial stack. If parameter Group common-offset traces into azimuth sectors is
Yes, the partial stack will only sum the traces in the same azimuth sector. The reciprocal traces are treated
equally in the partial stack so the azimuth varies only from -90 degrees to 90 degrees after the partial
stack.
COFF is also a module for pre-migration scaling. If parameter Apply pre-migration normalization is Yes,
the output data will be normalized by the stacking fold of the common-offset bin. Pre-migration
normalization should always be applied on NMO-corrected data.
Any traces that are borrowed or copied will have the trace header FOLD set to one. The trace header word
OIDN will be set to zero. This can be used for example to provide an even distribution of traces within an
offset for pre-stack migration and then after migration remove all borrowed or copied data.
Input Channels
1. GCI seismic traces: Required connection from previous process GCI data type.
Output Channels
1. GCI seismic traces: Required connection to next process GCI data type.
Parameters
Use fixed offset increment?
Enter No if a custom offset increment is desired.
Minimum common-offset (distance units)

This parameter will be the middle of the first offset bin.
300
Maximum common-offset (distance units)

Common-offset increment (distance units)
Common-offset bin width (distance units)
This parameter will allow traces to be grouped into multiple adjacent offset bins. The default for this
parameter should be used unless there is a significant non-uniform distribution of offsets. A
Common-offset bin width (distance units): that is too small can result in too few live traces being output.
One that is too large can smear the data. In the following figure the common offset bins have been offset
for clarity.
Offset groups
If custom offset bin ranges are desired, enter the start and end offset values for each offset bin. Start and
end offset values are allowed to overlap adjacent offset bins if it is desired to copy the trace to adjacent
offset bins. An example use for this parameter is for 3-D land surveys where one desires to have a greater
offset bin interval for the short offsets and a smaller offset interval on the long offsets. If you are not using
a fixed offset interval then data should be sorted by DMODIST, MLIN, and MBIN prior to running
DMO3D, KTMIG or any other module that uses the trace header word DMODIST. Otherwise these
modules require a fixed offset interval.
301
Expected maximum fold after COFF

Enter the CMP fold expected after running COFF. This parameter is only used if a custom offset bin
matrix is entered. The default value if the offset ranges do not overlap is the maximum number of traces
per ensemble of the input dataset plus the number of offset ranges. If the offset ranges overlap at all the
default is twice the maximum number of traces per ensemble of the input dataset. Neither of these defaults
are fool proof.
Fill in empty offset bins with

If None is selected, the offset bin will be left empty. If Nearest Neighbor is selected the nearest valid
offset bin will be copied to the empty bin. If NMO Stack is selected, the CMP gather should be NMO
corrected and a stack of the CMP gather will be used to copy to the empty bin. All copied traces will retain
the original coordinates and source to receiver offset except that the FOLD will be set to one, OIDN will
be set to zero and the DMODIST header word will be set to the offset bin value. For programs such as
DMO3D, the trace will be pre-stack partially migrated using the DIST header word but will be binned into
the DMODIST offset. After DMO3D is run in this case, the DIST header word will be set to the
DMODIST value. However the NMO mute will not be recomputed. In this case the user should reapply
the NMO mute.
Options: None, Nearest Neighbor, NMO Stack
Maximum neighbor delta (% bin width)

If the parameter Fill in empty offset bins with is Nearest Neighbor, this is the maximum number of
adjacent offsets bins to search for a trace to borrow. The parameter is expressed as percent of the offset bin
width. The default will allow for any offset bin to be used.
Apply pre-migration normalization?

If this is Yes, the output data will be normalized by the stacking fold of the common-offset bin.
Pre-migration normalization should always be applied on NMO-corrected data.
Apply partial stack?

Group common-offset traces into azimuth sectors?
Azimuth increment (degrees)
Starting azimuth (degrees)
302
COHFILT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Coherency filtering improves the coherency of events in an ensemble. Coherency weighting is the ratio of
the signal power to the signal-plus-noise power over the frequencies of interest.
This modules attempts to improve the coherency of events by weighting the frequencies of interest using
the ratio of signal power versus signal-plus-noise power. The signal power is the magnitude of the
complex sums of consecutive cross-power correlations over a range of traces. The signal-plus-noise power
is the magnitude of the complex sums of consecutive auto-power correlations over a range of traces. The
input traces are filtered with the averaged ratio of cross-power/auto-power in the frequency domain.
The user must specify the lowest and highest frequencies of interest. This is typically accomplished by
looking at the amplitude and phase spectra of an ensemble and then choosing the frequencies of interest.
The user also selects the length of the auto and cross correlation windows. The correlations are averaged
over a specified trace range. This averaged ratio is then applied to the center trace during filtering.
The correlations are computed over a time gate. The user must select a time gate on the seismic data in
which to perform the correlations. Typically, you would select a time gate over the seismic events of
interest. The gates should be at least twice as big as the correlation window length; otherwise the program
will abort.
Input Channels
Output Channels
Parameters
303
Lowest frequency of interest (hz)

Select the minimum frequency for filtering. The coherency weighting of frequencies below this value will
be zeroed.
Highest Frequency of interest (hz)

Select the maximum frequency for filtering. The coherency weighting of frequencies above this value will
be zeroed.
Auto and cross correlation window length(ms)

Power estimates are made from the auto and cross correlations over this length in milliseconds. If this
length is longer than the smallest time gate, then the program will abort.
Number of traces in power estimate window (0=all)

Enter the number of traces over which to average the auto and cross correlations. The program will then
apply the averaged coherency weighting to the center trace. Entering a value of 0 means that all the
traces in the ensemble are used for the average.
Power estimate time gates?

Selected the option for time gate values. The time gates are used to design the auto and cross correlation
values. The user can enter one start and stop time gate for the entire dataset. Or enter the gates into a
matrix so that time variant gates can be applied. If the smallest time gate is less than the correlation
window length, then this program will abort.
Time gate start (ms)

Enter a start time in milliseconds for computing the correlations.
Time gate end (ms)

Enter a stop time in milliseconds for computing the correlations.
Primary header key

Select the primary header key that corresponds to the primary key of the WINDOW2 matrix file.
TLSN
304

Select the secondary header key that corresponds to the secondary key of the WINDOW2 matrix file.
TLSN
Time gates matrix


You can optionally add time to the start time of the window using this header key.

You can optionally add time to the end time of the window using this header key.
Restore mute?
The user can optionally restore the mute that is applied to each trace.
305
COMREAD
Module Description
Perform seismic data de-compression using discreet wavelet packet transforms. This module will read the
compressed ensembles/traces that were written to disk file using module COMWRITE.
See the COMWRITE module help for more detailed information on the compression methods.
Queue
Input Channels
1. Compressed Input
Required
COMPRESS data type
Output Channels
1. Output
Required
GCI data type
Copyright (c) 2013 GeoCenter LP. All rights reserved. SeisUP is a registered trademark of GeoCenter LP.
306
COMWRITE
Module Description
Perform seismic data compression using discreet wavelet packet transforms on seismic ensembles or
single trace compression. The compression can be performed based upon a compression ratio or by
acceptable RMS error. The compressed data is written to a disk file and may be read using the
COMREAD module.
The 2-D (wavelet) compression method is performed on an ensemble basis. After getting an ensemble, the
data is compressed using discreet wavelet transforms and Huffman encoding. The 1-D (block)
compression method is performed on single traces. The 1-D method will not compress as much as the 2-D
method for the same RMS error.
Clean seismic data will tend to compress more with less error than noisy data. The author has found that
10:1 compression on shots and 20:1 compression on stacks can be reasonable.
The compression can be performed by stating the compression ratio. The ratio is, compressed size:original
size. Example: 20:1, will compress the seismic data 20 times the original size. The compression ratio is
computed by experimenting with the first ensemble found using different RMS values. It is tested up to 20
times before a final compression ratio is used. The actual compression of the data may be different than
the user requested. If the first ensemble ( first trace for 1-D compression) of the data is not representative
of the full dataset, then this method should not be used.
Stating the minimum acceptable RMS error between the original data and the compressed data can also
perform the compression. A larger RMS error will result in a greater compression at the expense of more
error introduced into the data.
The compressed file will have a SeisUP extension as COMPRESS. The COMPRESS file is the stored data
and headers. The COMPRESSz file is the history of the processing up to the current time.
Input Channels
1. Input
Required
GCI data type
307
Output Channels
1. Compressed Output
Required
Connect to disk file only
COMPRESS data type
2. Next Process
Optional
GCI data type
Parameters
Compression method
Select to use 2-D (wavelet) or 1-D (blocked) compression. The 2-D method is performed on ensembles of
data while the 1-D method is performed on single traces. The 2-D method will compress greater than the
blocked method using the same RMS value.
Default .....:2-D
Name ........:comp
Options .....:
2-D
1-D
Specify compression as ratio?

Specify to compress using a compression ratio or a RMS value. The ratio method will experiment with the
first ensemble (wavelet) or trace (blocked) until a suitable RMS value is found or up to 20 tests. If the first
ensemble/trace is not representative of the full dataset, then the RMS value should be used.
Default .....:No
Name ........:spec
Options .....:
Yes
No
308
Compression ratio (??:1):

Select the compression ratio. Example 20:1, would compress the data down 20 times the original size. 5:1
would compress the data 5 times the original size. This method runs tests on the first ensemble/trace to
find the best RMS value that will compress the data to the stated ratio. You should not use this method if
the first ensemble/trace does not represent the dataset.
Default .....:10.0
Name ........:comp
Type ........:Float
Min .........:2.0
Max .........:500.0
Acceptable RMS error (%)

Enter the minimum acceptable RMS error in percent. The RMS error is measured between the original
data and the compressed data. A larger value will result in more compression but at the expense of noisy
or missing data.
Default .....:0.01
Name ........:crms
Type ........:Float
Min .........:0.000001
Max .........:500.0
Copyright 2013 GeoCenter LP. All rights reserved. SeisUP is a registered trademark of GeoCenter LP.
309
CONV
Module Description
Input Channels
Output Channels
Parameters
Module Description
CONV will convolve data with a given wavelet or its inverse. Optionally, up to 5 wavelets and application
gates may be specified for the frequency input option. Each gate must be at least 100 ms in length and
gates must be separated in time by at least 100 ms from surrounding gates.
Input Channels
Output Channels
Parameters
Filter input domain
Options: Frequency, Time
Time-space variant?
Required if Filter domain = Frequency
Options: Yes, No
Filter to apply
Required if Filter domain = Frequency and Time-space variant =NO.
Matrix Type: CONVFREQ
310
Primary key
Required if Filter domain = Frequency and Time-space variant = Yes.
TLSN, Other
Primary key index

Required if Primary header key = Other
Secondary key
Required if Filter domain = Frequency and Time-space variant = Yes.
TLSN, Other
Secondary key index

Required if Secondary header key = Other
Number of filters per location

Required if Filter domain = Frequency and Time-space variant =YES.
Time-space variant filter to apply

Required if Filter domain = Frequency and Time-space variant = YES.
Matrix Type: CONVFREQ1
Filter to apply
Required if Filter domain = Time.
Matrix Type: CONVTIM
Amplitudes specified in DB?

311
Corrections to apply
Options: Amplitude & Phase, Phase only
Additive pre-whitener (%)

When computing the inverse or the phase only spectrum, enter the percent value of additive white noise
used to stabilize the calculation.
Convolve with the inverse of the filter?

Transform pad percent
Pad FFT length by this value to avoid circular convolution effects.
Set MUTEND header to first non-zero sample on input.

Options: Yes, No
This does not mute the trace. It just updates the header word.
312
CROSSTIE
Module Description
Input Channels
Output Channels
Parameters
Module Description
CROSSTIE checks crossing points on two SeisUP data sets. Data set 1 is from a previous process. Data
set 2 is from a GCI data file. The two data sets must have the same sampling rate and same number of
samples. The program uses MCX, MCY to compute the minimum distance from each CMP location on
two datasets. The results are printed on execution status.
The program can output traces from both data sets near crossing point, if an optional connection to next
process provided.
Input Channels
1. Seismic input: Required connection from previous process GCI data type.
2. Second data set: Required GCI data type.
Output Channels
1. Traces near the crossing point: Optional connection to next process GCI data type.
Parameters
The maximum distance of two closest points
Number of traces near the crossing point from either line to display
313
CUT3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
CUT3D will create time slices from 3-D seismic data. Output from CUT3D will be seismic traces where
the samples will correspond to midpoint lines and each trace will correspond to midpoint bins. The
following header values will be set:
Sample rate:
# Samples:
DIST
MBIN
MLIN
1000 us.
# of midpoint lines
Time (ms.) for time slice
Midpoint bin number
Midpoint line number for sample one.
When displaying time slices with DISPLAY program, the vertical axis annotation will start from zero.
Since most 3-D surveys do not start with line number zero, you will need to add the first line number,
usually one, to the annotated number.
The unused header word (81) is used to pass the time slice increment to the next module. The header word
(81) is used by the DISPLAY program only to view the previous time slice. Note: If Reverse MLIN order
parameter is Yes, and header words (77) and (81) are over written by some other module, then display
module will not display the data as expected.
Input Channels
Output Channels
Parameters
314
First time slice (ms.)

Last time slice (ms.)
Increment between time slices (ms.)
Minimum midpoint bin number
Maximum midpoint bin number
Minimum midpoint line number
Maximum midpoint line number
Select MLIN order?
If Yes option is selected, cut3d uses unused header word (77) to pass a flag for the data order to the next
module.
315
CVA2D
Module Description
Input Channels
Output Channels
Parameters
Module Description
CVA2D is a program used to generate velocity analysis information for further processing or output.
Therefore, output could be velocity stacks (output through a primary or secondary node) or coherency
information and gathers for further processing via interactive analysis such as GEOVEL. A stretch mute
can optionally be applied to the data to mute distortions due to excessive stretching of the data.
Input may be in any sort order, bearing in mind that the first parameter defaults to CMP sorted input data
and could become quite large if input data is in another order. Note that coherency measurements in
semblance or energy (power) may be selected.
A delta-offset term defines the tolerance for the common offset gather generated by the program. The
"header to add to mute" is as defined by program HORIZON as TIM1 or TIM2. The mute, velocity
analysis increment, and analysis location information are as user-defined multi-dimensional matrices.
Optionally, a user-defined AGC is applied before and/or after NMO/stack application.
Start time and stop time allow "horizon-based" analysis. The number of points in the coherence window is
roughly the dominant period of the data.
For velocity stacks a sequential velocity analysis number is put into GCI header word number 87. The
GCI header VELO will contain the constant velocity used for constant velocity stacks and variable
velocity index for variable velocity stack To display the constant velocity stacks with the DISPLAY
program set the following parameters in the module SEGYREAD or READ:
Input
Index
Index
Index
Max #
sort order
to primary header word
to secondary header word
to ensemble header word
traces per ensemble
Other
66
87
78
Max # traces in analysis
A stretch mute can optionally be applied to the data. The default is no stretch mute or 0 to be
compatible with older versions of this program. The author recommends that a stretch mute be applied to
the data with a default of 30%. Any data point whose sample interval is altered by a percentage greater
than the specified value will be muted. The stretching of waveforms is an undesirable but unavoidable
artifact of the normal moveout process. At shallow times and the far offsets, data will become so stretched
out that it will degrade the stack and distort the frequency content of the shallow data.
316
The program will also detect and mute traces where a combination of velocities and offsets causes the data
to crossover. This phenomenon usually happens if there are significant rapid decreases in the rate of
change of velocity resulting in imaginary interval velocities. This can cause damaging artifacts on the
stacked section if the data is moved out according to the velocity field with no sample crossover muting.
Input Channels
Output Channels
1. Geovel dataset: Optional connection to dataset GVL data type.
2. Velocity stacks : Optional connection to next process GCI data type.
Parameters
Number of midpoints to hold
Use converted wave NMO equation
Select Yes to apply a shifted hyperbolic normal moveout equation that can be applied to converted wave
data. Select No to apply the standard normal moveout equation.
Output analysis options

Options: Velocity stacks, Coherency, Gathers
Coherency type
Options: Semblance, Energy
Type of velocity stacks

Options: Constant, Variable
Reference variable velocity stack

If producing velocity stacks enter the matrix name to be used for the central variable velocity stack.
CVA2D will use triangulation to interpolate the function at each analysis location if multiple velocities are
input.
317
Matrix Type: RMSVEL
Percentage of reference VVS

If producing velocity stacks, enter the matrix name containing percentage function(s) to apply to the
reference velocity to determine the minimum and maximum variable velocity stacks. CVA2D will use
triangulation to interpolate the function at each analysis location if multiple percentage functions are input.
Matrix Type: VVSPER
Number of variable velocity stacks

If producing velocity stacks enter the number of variable velocity stacks you wish to calculate.
Minimum offset for gather

Required if Output analysis options: = Coherency or Gathers. This is the center of the first offset group.
Maximum offset for gather

Required if Output analysis options: = Coherency or Gathers. This is an offset within the last offset
group.
Output offset increment for gather

Required if Output analysis options: = Coherency or Gathers.
Header to add to mutes

Primary mute header key

TLSN
Secondary mute header key

TLSN
318
Mutes
Matrix Type: NMOMUTE
Apply NMO stretch mute?

Select Yes to apply a stretch mute to the data during NMO.
Stretch mute percentage (%)

Enter the amount of percentage stretch for the output traces after NMO has been applied. The author
recommends starting at 30 for 30% stretch muting.
Velocities
Matrix Type: CVAVELS
Analysis locations
Matrix Type: VABINS2D
Minimum CMP fold

If the fold within the CMP gather after summing common offsets is less than the value entered here, the
velocity analysis will not be output. If an analysis is dropped due to low fold, a warning message will be
printed to the execution status.
Pre-NMO AGC window length (ms)

Post-stack AGC window length (ms)
AGC pre-suppression level (%)
Required if Pre-NMO AGC window length (ms) 0 or Post-stack AGC window length (ms) 0.
AGC Reference mean

Stack Normalization technique

Options: square root of fold, fold plus next parm
319
# to add to fold before divide

Required if Stack normalization technique = fold plus next parm.
Ending time (ms)

Apply mute
Options: Before NMO, After NMO
# points in coherency window
320
CVA3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
CVA3D is a program used to generate velocity analysis information for further processing or output.
Therefore, output could be velocity stacks (output through a primary or secondary node) or coherency
information and gathers for further processing via interactive analysis such as GEOVEL or IVEP. A
stretch mute can optional be applied to the data to mute distortions due to excessive stretching of the data.
Input may be in any sort order, bearing in mind that the first parameter defaults to CMP sorted input data
and could become quite large if input data is in another order. Note that coherency measurements in
semblance or energy (power) may be selected.
A delta-offset term defines the tolerance for the common offset gather generated by the program. The
"header to add to mute" is as defined by program HORIZON as TIM1 or TIM2. The mute, velocity
analysis increment, and analysis location information are as user-defined multi-dimensional matrices.
Optionally, a user-defined AGC is applied before and/or after NMO/stack application.
Start time and stop time allow "horizon-based" analysis. The number of points in the coherence window is
roughly the dominant period of the data.
For velocity stacks a sequential velocity analysis number is put into GCI header word number 87. The
GCI header VELO will contain the constant velocity used for constant velocity stacks and variable
velocity index for variable velocity stack To display the constant velocity stacks with the DISPLAY
program set the following parameters in the module SEGYREAD or READ:
Input
Index
Index
Index
Max #
sort order
to primary header word
to secondary header word
to ensemble header word
traces per ensemble
Other
66
87
78
Max # traces in analysis
compatible with older version of this program. The author recommends that a stretch mute be applied to
321
A new option is added for outputting GCI format dataset which is required by interactive analysis module
IVEP. Fourth order(Eta) NMO can be used for velocity analysis. Constant Etas are defined in matrix
CVAETAS. To reduce computation time, reference guide function and fairway can be used. The option of
variable velocity stacks is not supported for GCI dataset.
In case of constant velocity stack, header 71 is set to 1.
In case of coherency information, header 71 is set to 2.
In case of gathers, header 71 is set to 3.
Constant velocity information is saved in header 78.
Constant Eta(multiplied by 1000) information is saved in header 52.
Either GCI or GVL dataset can be outputted, but not both in one job. In addition, parameter "Output
dataset format" needs to be selected correctly.
Input Channels
Output Channels
1. GEOVEL dataset: Optional connection to dataset GVL data type.
2. IVEP dataset: Optional connection to dataset GCI data type.
3. Velocity stacks : Optional connection to next process GCI data type.
Parameters
Number of midpoint lines to hold
Use converted wave NMO equation
322
Output analysis options

Options: Velocity stacks, Coherency, Gathers
Coherency type
Type of velocity stacks

Options: Constant, Variable
Reference variable velocity stack

If producing velocity stacks enter the matrix name to be used for the central variable velocity stack.
CVA3D will use triangulation to interpolate the function at each analysis location if multiple velocities are
input.
Matrix Type: RMSVEL
Percentage of reference VVS

If producing velocity stacks, enter the matrix name containing percentage function(s) to apply to the
reference velocity to determine the minimum and maximum variable velocity stacks. CVA3D will use
triangulation to interpolate the function at each analysis location if multiple percentage functions are input.
Matrix Type: VSPER
Number of variable velocity stacks

If producing velocity stacks enter the number of variable velocity stacks you wish to calculate.

Required if Output analysis options: = Gathers. This is the center of the first offset group.

Required if Output analysis options: = Gathers. This is an offset within the last offset group.
Output offset interval for gather

Required if Output analysis options: = Gathers.
323


TLSN

TLSN
Mutes


Velocities
Use 4th order(eta) NMO equation?

Select Yes to use 4th order(eta) NMO equation.
Import an ETANMO matrix?

ETANMO matrix name
324
Constant Etas
If using 4th order(eta) NMO equation, enter the constant Eta values you wish to calculate.
Matrix Type: CVAETAS
Use reference guide function and fairway?

Select Yes to use reference guide function and fairway to reduce computation time. Coherency
information is only calculated within fairway
Reference variable velocity

If using reference guide function and fairway, enter the matrix name to be used for the reference guide
function. CVA3D will use triangulation to interpolate the function at each analysis location if multiple
velocities are input.
Matrix Type: RMSVEL
Percentage of reference velocity

If using reference guide function and fairway, enter the matrix name containing percentage function(s) to
apply to the reference velocity to determine the minimum and maximum variable velocities. CVA3D will
use triangulation to interpolate the function at each analysis location if multiple percentage functions are
input.
Matrix Type: VSPER
Analysis locations
Minimum CMP fold

If the fold within the CMP gather after summing common offsets is less than the value entered here, the
velocity analysis will not be output. If an analysis is dropped due to low fold, a warning message will be
printed to the execution status.

Post-stack AGC window length (ms)
325

AGC Reference mean



Required if Stack Normalization technique = fold plus next parm.
Ending time (ms)

Apply mute

Output dataset format
Options: GVL(GEOVEL dataset),GCI(IVEP dataset),NONE
326
CVA3DHTI
Module Description
Input Channels
Output Channels
Parameters
Module Description
CVA3DHTI generates HTI velocity analysis information. Output is coherency (i.e. semblance) gathers.
These gathers may be interpreted using IVEP.
Input may be in any sort order. However, CMP order is recommended to avoid storage problems.
The Offset Interval defines the offset range for offset scaling. The mute, velocity analysis values, and
analysis location information are input by multi-dimensional matrices. AGC may be applied before
coherency computation. A stretch mute may be applied after NMO correction prior to coherency
computation.
There are two independent variables in velocity analysis; time and velocity. In HTI velocity analysis there
are four independent variables; time, Vslow, Vfast and the Vslow axis orientation (s). The axis
orientation is fixed and the two velocities varied creating a three dimensional data set. In the NMO
equation
with the V nmo velocity given by
Coherency output data header 71 value is set to 3. Header 78 (VELO) contains Vslow, header 52 contains
Vfast and headers 67 and 66 contain MLIN and MBIN.
327
Input Channels
Output Channels
1. IVEP dataset: Required connection to dataset GCI data type.
2. Velocity stacks : Optional connection to next process GCI data type. --NOT YET
IMPLEMENTED--
Parameters
Number of midpoint lines to hold
Coherency type
Offset scaling
Options: Yes, No

This is the center of the first offset group.

This is the center of the last offset group.
Output offset interval for gather

Required if Offset scaling = Yes.

328

TLSN

TLSN
Mutes


Enter the amount of percentage stretch for the output traces after NMO has been applied.
Velocities
Vslow azimuth
Enter the azimuth of the Vslow axis.
Analysis locations
Minimum CMP fold

If the fold within the an analysis location is less than the coded value, the velocity analysis will not be
performed. If an analysis is dropped due to low fold, a warning message will be printed to the runlog.
329

AGC Reference mean
Ending time (ms)
Apply mute
330
CVFB
Module Description
Parameters
Module Description
CVFB can output an external file so that other refraction statics programs can use the picks in the first
break matrix generated by the DISPLAY or RFS1 modules. Geometry must have been defined.
Parameters
Output format
Options: Green Mountain, Hampson-Russell
Picks
Matrix Type: AFS1B
Output file name

Enter the file name to place the results. If an absolute path is not entered, the file will be placed relative to
your home directory.
Rotate coordinates by grid azimuth?

Maximum offset
Enter the maximum offset to output. Any picks that exceed this offset will be dropped.
Maximum time (ms.)

Enter the maximum pick time to output. Any picks that exceed this value will be dropped.
331
CVGMA
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use this module to convert between the SeisUP SEG-Y format to the GMA modified SEG-Y format.
Input Channels
1. Input: Required SEGY data type.
Output Channels
1. Output: Required SEGY data type.
Parameters
Convert
When converting from SEG-Y to GMA, the file will be placed in your home directory with the extension
of .SGY appended to the data set name.
Options: SEGY->GMA, GMA->SEGY
332
DBHDR
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module DBHDR will transfer attributes between the geometry database and the trace headers. Attributes
that are transferred from the trace header to the database can then be viewed with the module QCVIEW.
Input Channels
Output Channels
1. Next process: Required connection to next process GCI data type.
Parameters
Direction
Options: Header to DB, DB to Header
Trace header
This is the trace header field that will be transferred into the database.
Trace header index

This is the trace header index that will be transferred into the database if the trace header parameteris
Other.
Order
This is the sort order within the database to retrieve or place attributes in the database. The option
Channelshould be used for attributes needed for every trace. The Channel attribute corresponds to the
channel number (FCSN) within the shot.
333
Options: Shot, Channel, Receiver, Midpoint
Shot class attribute

Input the attribute class when the Orderparameter is Shot.
Options: User, Amplitude
Channel class attribute

Input the attribute class when the Orderparameter is Channel.
Options: User, Amplitude
Midpoint class attribute

Input the attribute class when the Orderparameter is Midpoint.
Options: User, Fold, Datum
Shot amplitude attribute

Input the attribute name when the Shot classparameter is Amplitude.
Matrix Type: RMSSSPN
Channel amplitude attribute

Input the attribute name when the Channel classparameter is Amplitude.
Matrix Type: RMSFCSN
Shot user attribute

Input the attribute name when the Shot classparameter is User.
Matrix Type: USRSBIN
Channel user attribute

Input the attribute name when the Channel classparameter is User.
Matrix Type: USRFCSN
334
Receiver user attribute

Input the attribute name when the Orderparameter is Receiver.
Matrix Type: USRSGEN
Fold type
Select Pre-stack to manipulate the fold within common offsets. Select Post-stack to manipulate the fold
after CMP stack.
Options: Pre-stack, Post-stack
Midpoint fold attribute

Input the attribute name when the Midpoint classparameter is Fold and the parameter Fold type: is
Post-stack.
Matrix Type: DBFOLD
Pre-stack midpoint fold attribute

Input the attribute name when the Midpoint classparameter is Fold and the parameter Fold type: is
Pre-stack.
Matrix Type: DBFOLDOFF</A>
Midpoint datum attribute

Input the attribute name when the Midpoint classparameter is Datum.
Matrix Type: CMPDATUM
Midpoint user attribute

Input the attribute name when the Midpoint classparameter is User.
Matrix Type: USRMBIN
Channel first break attribute

Input the attribute name when the Channel classparameter is First break.
335
Add to existing attribute?

If you want to append, insert, or replace attributes in the database select YES. Otherwise select NO to
delete any existing attribute with the specified name.
Create a new trace header field?

If the you are transferring attributes from the database to the trace header select Yes to create an extended
trace header index. Any extended trace headers will only be retained when outputting in the SeisUP
internal format by using for example, the WRITEmodule.
New trace header field name

Enter the trace header name to be associated a new extended trace header. The name is limited to 15
characters. If the name already exists, the previously defined header will be used.
Trace header index

When you are not creating a new header field, enter the trace header index to place the database attribute
into. See the SeisUP internal trace specification.
Force trace header to be a floating point number?

This parameter is required when you are transferring attributes from the database to the trace header. Most
modules within SeisUP will only support integer trace headers. Unless a module within SeisUP specifies
that it supports floating point trace headers or if this is required for an external application, select No.
When selecting No, any fractional numbers within the database are rounded to the nearest integer number.
When selecting Yes, the attribute will be in IEEE floating point format.
336
DBINQ
Module Description
Parameters
Module Description
Use this module to dump information from the DB file.
Parameters
None
337
DBMERGE
Module Description
Parameters
Module Description
DBMERGE will merge first break matrices into another. This allows several users to pick first breaks on
different parts of a survey and merge them together. From two to four matrices can be merged in one job.
Parameters
Number of channels per matrix
This allows the database value to be overridden.
Merged first break matrix

The matrix to be merged into. Duplicate SLIN/SBIN spreadsheets will be silently overwritten.
NOTE The module will still run if this matrix is a pre-existing matrix. This is NOT a good idea.
Matrix Type: AFS1B
Input first break matrix

A matrix to be merged in. This parameter is required.
Matrix Type: AFS1B

Another matrix to be merged in. This parameter is required.
Matrix Type: AFS1B

Another matrix to be merged in. This parameter is optional.
Matrix Type: AFS1B
338

Another matrix to be merged in. This parameter is optional.
Matrix Type: AFS1B
339
DCBIAS
Module Description
Input Channels
Output Channels
Parameters
Module Description
DCBIAS will remove DC bias by calculating the mean value of all the samples in the trace and then
subtracting the mean value from the whole trace. With the time-variant option, DCBIAS will subtract the
running window mean from the trace.
Input Channels
Output Channels
Parameters
Time variant?
Window length (ms).
340
DECON
Module Description
Input Channels
Output Channels
Parameters
Module Description
Performs Weiner-Levinson or Maximum Entropy deconvolution on a trace by trace or multi-trace basis.
The Weiner-Levinson option can be applied as spiking or predictive deconvolution. Up to five different
operators may be specified. The deconvolution operators can be band-limited for improved operator
stability.
Seismic data can be considered as the convolution of the source signal with the instruments, geophones,
and earth response. The earth response can give undesirable effects like reverberations, multiples, and
ghosts. The objective of deconvolution is to estimate the responses and then apply inverse filters to
remove them.
The module allows for Wiener-Levinson Spiking or Predictive deconvolution. If Predictive decon is
chosen then the gap must be entered. A decon operator length must be chosen for the Wiener-Levinson
algorithm.
If Spiking deconvolution is selected, an option is provided to perform minimum phase, zero phase, and
phase only deconvolution. The Wiener-Levinson filter used to deconvolve the data is minimum phase, so
by default, if minimum phase is chosen, then a normal deconvolution is performed. You can optionally
convert the Wiener-Levinson filter to zero phase and then perform the deconvolution. The last option is to
perform zero phase (only) deconvolution (i.e. do not apply the amplitude). Zero phase only deconvolution
will have to be followed up the another zero phase type deconvolution to apply the amplitude correction.
The Maximum Entropy spiking filter is designed using a least squares minimization of the forward and
reverse prediction errors and Levinson recursion. This type of deconvolution is also referred to as the Burg
technique.
If Weiner-Levinson deconvolution is chosen, you can perform this on an ensemble or running window
basis. To reduce the amount of noise in the autocorrelation for ensemble deconvolution, DECON performs
as follows:
SUM A(i) FROM i = 1+R/2 TO N-R/2
-------------------------------N-R
341
Where:
A(i) are common autocorrelation time samples distributed
about the median value.
N
is the number of autocorrelations.
is the number of autocorrelations outside the

median to reject. (F5 * N / 100)
Application times are interpreted as follows:

Ramp
Ramp
|<->|
|<->|
___________
|
|
___________
|\ /|
Op. #1
| X |
__________________
|\ /|
Op. #2
| X |
|
Op. #3
|...
|___________|/ \|___________|/ \|__________________|

^
End1
^
Start2
^
End2
Start3
End3
When performing deconvolution, overall amplitudes may decrease. When "Restore Amplitude" is
requested, a scalar is derived by computing the ratio of the energy of the filtered input application window
over the filtered deconvolved application window. If this is not requested, scaling is unity.
A band-limited version of the estimated input wavelet can be deconvolved with the data. Typically, the
low/high frequencies chosen for band-limited deconvolution should be the original frequencies of the
input wavelet. Due to improved operator stability when using the band-limited option, the user can lower
or remove the pre-whitening percent. There are several reasons why band-limited deconvolution is more
desirable than a normal spiking or predictive deconvolution. Because of additive noise and band-limited
sources such as Vibroseis, ideal spiking deconvolution is never achieved. In addition, two low frequency
problems are responsible for large errors in the low frequency portion of the deconvolution operators. One,
the low frequency part of the wavelet is attenuated by the earth thereby not satisfy the white reflectivity
assumption of deconvolution. Two, it is difficult to achieve accurate estimates of the low frequency part of
the input wavelet. Band-limited deconvolution is achieved by computing a bandpass filter then while in
the frequency domain, the amplitude portion (real part) of the spectrum is inverted (1/amplitude). The
phase portion (imaginary part) is zero or minimum depended on the user selection. Typically, if the input
data is minimum phase, then this filter should be minimum phase. The Inverse band filter is then
convolved with the windowed input trace during the operator design phase of the program.
A Hanning window can be applied to the windowed input trace to prevent ringing of the autocorrelation
function due to abrupt truncation of the data. This ringing is know as Gibbs phenomenon
342
References
Robinson, E.A., 1967, Multichannel Time Series Analysis with Digital Computer Program, Holden-Day.
Robinson,E.A., Trietel, S., 1980, Geophysical Signal Analysis, Prentice-Hall, Inc.
Burg, J.P., 1972, The Relationship Between Maximum Entropy Spectra and Maximum Likelihood
Spectra, Geophysics, Vol. 37, pp 375-376.
Burg, J.P., 1975, Maximum Entropy Spectral Analysis, Ph.D. Thesis, Stanford University.
Input Channels
Output Channels
2. Cgm: Optional connection to dataset CGM data type.
Parameters
Type of deconvolution
Select to use Wiener-Levinson Spiking or Predictive deconvolution or Maximum Entropy deconvolution.
If Predictive is chosen then the gap parameter must also be entered.
Options: Wiener-Levinson Spiking Deconvolution, Wiener-Levinson
Predictive Deconvolution, Maximum Entropy Spiking Deconvolution
Application mode
If Wiener-Levinson deconvolution is selected, select Single Trace to apply deconvolution on a
trace-by-trace basis. Select Ensemble to apply an operator that is derived by an average of the
autocorrelation over the entire ensemble. Select Running Window to apply an operator to a single trace
that is derived by an average of the autocorrelations from neighboring traces.
Minimum offset
Required if Application mode is Ensemble.
343
Maximum offset
Required if Application mode is Ensemble.
Number of traces in the running window

If the Application mode is Running Window, enter the number of neighboring traces to used to compute
an average autocorrelation from. This number will be forced to a lower odd number.
Trimmed mean(%)
Required if the Application mode is Yes. A composite trace is built from the autocorrelations to be used to
compute a deconvolution operator. When trim = 0, the average value of a time slice through the
ensembles autocorrelations is used to build the composite trace. When trim = 100, the median value of the
time slice is used. In between, the out lying values are dropped.
Time variant?
Prewhitening (%)
Prediction gap (ms)


Start design time (ms)

End design time (ms)

344
Primary header key

TLSN

TLSN
Matrix Type: DECON
Application times
Design times


345
Decon operator phase

You can chose to perform minimum phase decon, which is the default. This option will apply the
minimum phase and amplitude of the Wiener-Levinson filter. The zero-phase option will convert the
Wiener-Levinson filter to zero phase and then apply amplitude and phase. The phase only option will
convert the Wiener-Levinson filter to zero phase and then apply the phase only portion.
Options: Minimum-phase, Zero-phase, Phase only
Band-limited deconvolution?
Choose whether to perform band-limited deconvolution. If selected, the four corner frequency of the band
pass filter must be chosen. In band-limited deconvolution, and band pass filter is designed and the
amplitude spectra is inverted:
new amp spectra = 1 / old amp spectra.
The inverse band filter is then convolved with the windowed input trace during the operator design phase
of the program.
Filter phase
Select whether the band-limited filter is minimum or zero phase. Typically, if the data is minimum phase
then this filter should be minimum phase also.
Options: Minimum-phase, Zero-phase
Low cut frequency (Hz)

Enter the low cut frequency in Hertz. Frequency below this value are zeroed out for the band pass filter.
Low pass frequency (Hz)

Enter the low pass frequency in Hertz. This is the lowest frequency that will be passed at normal
amplitude. Frequencies between this value and the low cut value are tapered to zero.
High pass frequency (Hz)

Enter the high pass frequency in Hertz. This is the highest frequency that will be passed at normal
amplitude. Frequencies between this value and the high cut value are tapered to zero.
High cut frequency (Hz)

Enter the high cut frequency in Hertz. Frequency above this value are zeroed out for the band pass filter.
346
Apply Hanning window to input traces?

The input trace can have a Hanning window applied to the ends. The length is half the decon operator
length at each end of the input trace. A Hanning window prevents ringing of the data due to abrupt
truncation when applying a window to the input trace. The Hanning window will prevent what is know as
the Gibbs Effect.
Restore amplitude?
Low frequency (Hz)
Required if Restore amplitude? = Yes.
High frequency (Hz)

347
DELHORZ
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use DELHORZ to delete interpreted horizons from the database.
Parameters
Horizon to delete
Select the horizon name that you wish to delete.
348
DELTAXY
DELTAXY - Computes source and/or geophone location errors.
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module DELTAXY computes shot or receiver location repositioning trials using refraction arrivals. The
shot or receiver is repeatedly placed at new locations based on the movement parameters coded. At each
location, the refraction arrivals are linear moveout corrected using the trial location to compute the offset
distance. The semblance is then computed for the entire ensemble over the window specified. Each output
sample is the semblance from one location trial. Each trace contains all trials with the same delta x. The
delta y axis is time. The sample rate is set to delta y. Traces used in the computation may be limited by
shot/receiver offset and azimuth. The number of input traces used is stored in header word 79 (FOLD).
The analyses can be viewed using READ/DISPLAY by reading the output data set by the secondary
header key and using header word 70 (containing delta x values) for the ensemble key. Setting DISPLAY
parameters as noted in the runlog will produce correct time axis annotation.
Input Channels
Output Channels
Parameters
Trial Coordinate
Options: Shot, Receiver
349
Number of X trials
The number of trials in the x coordinate.
Number of Y trials
The number of trials in the y coordinate.
X trial increment
The increment in the x coordinate direction.
Y trial increment
The increment in the y coordinate direction.
Semblance window length

The length of the semblance computation window.
Semblance window center time after LMO

The center time of the semblance computation window after linear moveout correction correction.
Azimuth variable velocity

Options: YES, NO
Vslow azimuth
Azimuth of the slow principle propagation axis.
Vslow
The slow velocity used for linear moveout correction.
Vfast
The fast velocity used for linear moveout correction.
LMO correctional velocity

The velocity used for linear moveout correction.
350
Length of scale window

The data are scaled by the average absolute value in this window centered about the moveout time
computed.
Limit by azimuth
Options: YES, NO
Azimuth pass center

The azimuth pass band center.
Azimuth pass width

The azimuth pass band width. The center and width define a cone about the center and the center -180.
Limit by offset
Options: YES, NO
Offset pass minimum

The minimum value of the absolute value of the shot/receiver offset to process.
Offset pass maximum

The maximum value of the absolute value of the shot/receiver offset to process.
351
DEMUX
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use this module to demultiplex seismic field data (without amplitude recovery) from tape. DEMUX allow
the user to define the seismic field format in one of two ways:
1. By specifying each item necessary to define the field format (i.e., ID type, bytes/scan, bytes/sample,
bytes/sync, sync code, sub-multiplex gain flag, data channels, auxiliary channels and gain channels).
2. By specifying a common format name and the number of data channels DEMUX will default the
parameters as follows:
Format
SEGA
SEGB
SEGB
SEGB
SEGB
SEGB
SEGB
SEGB
SEGC
SEGC
SEGC
GOEL
SEGD
SEGD
SEGD
Data
48
24
36
48
60
96
120
240
24
48
96
96
120
240
240
Aux.
14
5
5
5
5
5
5
5
7
15
31
3
7
7
24
ID type
0f0f0f0f
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
ffff0000
GAIN
18
1
1
1
1
1
1
1
0
0
0
0
1
1
0
B/SCN
128
74
104
134
164
254
314
614
128
256
512
400
318
618
536
B/SMP
2
2
2
2
2
2
2
2
4
4
4
4
2
2
2
B/SYC
3
4
4
4
4
4
4
4
4
4
4
4
4
4
4
Sync
ffffff00
01010101
01010101
01010101
01010101
01010101
01010101
01010101
ffffff00
ffffff00
ffffff00
ffffff00
ffffff01
ffffff01
ffffff01
Subm
Yes
No
No
No
No
No
No
No
No
No
No
No
No
No
No
FPSEGA
24
integer
integer
integer
integer
integer
integer
integer
integer
float
float
float
float
SEGD(15)
SEGD(15)
SEGD(44)
Where:
Format
Format name.
DATA
The number of data channels per shot.
AUX.
The number auxiliary channels per shot.
ID type
The ID type.
GAIN
The binary gain or IFP recovery flag
B/SCN
The number of bytes per scan.
B/SMP
The number of bytes per sample.
B/SYC ,
The number of bytes per sync.
352
0f0f0f0f
18
64
ffffff00
Yes
integer
Sync
The sync code.
Subm
The sub-multiplex gain.
FP
The floating point data flag.
The number of channels per scan my be computed as the number of bytes per sync divided by the number
of bytes per sample. If there is a sub-multiplex gain, subtract one from the numerator before the divide.
NOTE: The sync code and sub-multiplex gain are not considered as channels by DEMUX.
Hardware Requirements
DEMUX needs to be able to read long block records (greater than 64K bytes). The following is required
for each platform:
Solaris
No changes are needed.
Irix (Silicon Graphics)
Currently only Qualstar 34XX supported. Contact GeoCenter regarding adding 9-track tape devices
to SeisUP.
AIX (IBM)
The existing 9-track device driver will work, but the maximum DMA transfer parameter for the SCSI
controller must be increased. Issue the command chdev -l scsi0 -a dbmw=0x902000 -P as root.
Where scsi0 is the name of the SCSI controller connected to your tape drives. Reboot the operating
system after issuing the above command. The maximum record size is 8MB.
HPUX
No changes are needed.
When using the Qualstar 34XX tape device on the SGI, IBM, or HP system, the tape device will block
long records into 64K byte chunks so that a special long block driver is not needed. Make sure that the
parameter Data Blocked? is set to Yes.
References
Society of Exploration Geophysicists, Digital Tape Standards.
Northwood, E.J., Weisinger, R.C., and Bradley, J.J., Recommended standards for digital tape formats:
Geophysics, V. 32, p. 1073-1084.
Meiners, E.P., Lenz, L.L., Dalby, A.E., and Hornsby, J.M., Recommended standards for digital tape
formats: Geophysics, V. 37,p. 36-44
Barry, K.M., Cavers, D.A., and Kneal, C.W., Recommended standards for digital tape formats:
Geophysics, V. 40, p. 344-352
353
SEG Subcommittee on Field Tape Standards, Recommended standards for digital tape formats-SEG-D,
REVISION 1: Geophysics, V. 59,p. 668-684
Input Channels
1. Input: Required RFMT data type.
Output Channels
1. Output: Required SEGY data type.
Parameters
Number of records to demultiplex
The default is demultiplex all of the records in the input data set.
Output record length (ms.)

Input sample rate
Select the input sample rate in microseconds.
Options: 1000, 2000, 4000, 8000
Data blocked?
Select Yes if the shot record is split into multiple blocks
Memory to allocate for field record (MB.)

This parameter should be larger than the maximum record size in the input data set.
Format name
Options: User defined, SEGA, SEGB, SEGC, GOEL, SEGD
354
SEGD format
If the Format name is SEGD, enter the type of SEGD data. This value is in byte 4 of the general header.
Options: 15, 44
Number of data channels per shot

ID type
The ID mask (in hex) represents the first four bytes of the header block. Each BCD (binary coded decimal)
digit of the ID is indicated by the letter f.
Options: xf0f0f000, xfff00000, xffff0000, x0f0f0f00,
xffffff00, x0f0f0f0f
Byte displacement to the early gain

If the format name is SEGA, this parameter is for the binary gain recovery. Enter the byte displacement to
the early gain in the header block. If the displacement is entered as a positive value, the gain is computed
from the early gain in conjunction with the up/down and gain change bits. If the displacement is entered as
a negative value, the gain is computed from the sub-multiplex gain in conjunction with the up/down and
gain change bits.
Binary gain or IFP recovery flag

If the format name is User, enter zero if there is no binary gain or IFP recovery. Enter a zero for SEGC
formats. If non-zero, there are two cases:
1. IFP recovery. Enter the number of data channels per four gain bits. E.g., code as 1 for SEGB,
SEGD(15), DFS IV or DFS V .
2. Binary gain recovery (SEGA type formats). Enter the byte displacement to the early gain in the
header block. If the displacement is entered as a positive value, the gain is computed from the early
gain in conjunction with the up/down and gain change bits. If the displacement is entered as a
negative value, the gain is computed from the sub-multiplex gain in conjunction with the up/down
and gain change bits
Bytes per scan

If the format name is User, enter the number of bytes per scan.
355
Bytes per sample

If the format name is User, enter the number of bytes peer sample
Options: 2, 4
Bytes per sync

If the format name is User, enter the number of bytes per sync.
Options: 2, 3, 4
Sync code
Sub-multiplex gain?
Select NO unless the format is SEGA, DFS III, EPR, SUMMIT VI, SN328, PDR89.
Header size in bytes

Separate header?
Select Yes if the header block and the data block are separate records. Select No if the header block and
the data block are one continuous record.
Floating point data flag

Options: integer, floating point, SEGD(15), SEGD(44)
Data channels
If the format name is User, enter the channel numbers corresponding to the data channels.
Matrix Type: DMUX
Gain channels
If the format name is User, enter the channel numbers corresponding to the gain channels.
Matrix Type: DMUX
356
Auxiliary channels
If the format name is User, enter the channel numbers corresponding to the auxiliary channels
Matrix Type: DMUX
Output channels
Enter the channel numbers that you wish to output. The row number will correspond to the output channel
number. The value in the row is the input channel number. The default is to output data channels only
numbered from one to the number of data channels per shot.
Matrix Type: DMUX
357
DEPTH
Module Description
Input Channels
Output Channels
Parameters
Module Description
DEPTH will convert a 2-D or 3-D stack section to a depth section. DEPTH will convert from time to
depth along vertical rays using a velocity model created by the module VIP. When plotting depth sections,
specify the IPS (inches per second) as the number of inches per one thousand (1000) feet or meters. One
should also remember that DEPTH is essentially a resampling process so that the Nyquist frequency will
change.
* NOTE *
DEPTH requires the input data set to be a velocity-depth model from module VIP. Users should select the
options to compute AVERAGE velocities and be DEPTH oriented.
Input Channels
1. GCI data from previous process: Required connection from previous process GCI data type.
2. VIP velocity dataset: Required connection from dataset SEGY data type. OR GCI data type.
Output Channels
Parameters
Depth step (feet or meters)
Maximum depth
358
DESPIKE
Module Description
Input Channels
Output Channels
Parameters
Module Description
DESPIKE applies a running median filter to the absolute value of the samples. Samples that exceed the
median by Spike threshold (db). are flagged as spikes and replaced by a cubic spline fit derived from the
adjacent live samples.
DESPIKE should be run prior to any deconvolution or filtering. First breaks should generally be picked
prior to DESPIKE. It tends to flag first arrival peaks as spikes, but generally replaces them with values
that are reasonably close to the original.
Input Channels
Output Channels
Parameters
Spike threshold (db).
The lower this value is, the more samples will be flagged as spikes.
# consecutive samples that can be a spike.

This parameter and the number of samples per trace are the main determining factors for CPU time.
Debug level
Options: None, Traces with spikes, Changed values, Values used, Way
too much
359
DICE
Module Description
Input Channels
Output Channels
Parameters
Module Description
DICE will perform time variant signal enhancement by extracting the signal along the dominant dip
direction and then summing the signal with the original trace. The dominant dip direction is measured by
finding the maximum coherency along a range of dips from neighboring traces at each sample. If the
maximum coherency is less than a user specified threshold level, no signal will be extracted. After signal
extraction, the coherency is measured between the signal and the original trace at each sample. The
coherency is then used to calculate a weight to apply to the signal trace before summing with the original
trace.
DICE uses the ensemble header word (see GCI) to determine the distance away from the trace being
enhanced. This header word should be a sequential index like SDPN, MBIN, MLIN, FCSN, or CDPN.
DICE will drop dead and auxiliary traces.
Input Channels
Output Channels
Parameters
Number of neighboring traces to use
This is the number of neighboring traces to use to determine the dominant dip. DICE will force this
number to a higher odd number.
360
Number of points in the coherency time window

Coherency estimates will be calculated over a this symmetrical window.
Minimum dip in Ms. per trace

The Ms. per trace should be measured over the input data.
Maximum dip in Ms. per trace

Dip increment in Ms. per trace
This is the dip increment in Ms. per trace between the minimum and maximum dip defined above. DICE
will determine the coherency at each dip increment.
Minimum coherency threshold level

Force DICE to use the turbo version?
If the dip increment is a multiple of the sample rate(ms) divided by 10 then DICE will use a faster version
at the expense of using more memory. For example, if the sample rate is 4ms. and if you roughly
measured a 1.7ms/trace dip increment then the dip increment should be 1.6 (4*4/10) or 2.0 (5*4/10). By
choosing Yes to this parameter, DICE will use the turbo version at the expense of a slight interpolation
error.
Output
Options: Signal, Signal & Original, Coherency
Use custom coherency-weight table?

Required if Output: = Signal & Original.
Coherency(1) for weight(1)

Required if Use custom coherency-weight table? = No. This is the coherency between the signal and the
original trace. A coherence of -1 means the traces are exactly opposite. A coherence of 1 means the traces
are exactly the same. Weights will held constant below this coherency.
Weight(1) to apply at coherency(1)

Required if Use custom coherency-weight table? = No. This weight will be applied to the signal prior to
summing with the original data at the coherency defined in the previous parameter. DICE will linearly
interpolate weights between defined coherencies.
361

Required if Use custom coherency-weight table? = No. Weights will held constant above this coherency.

Required if Use custom coherency-weight table? = No.
Coherency-weight matrix
Required if Use custom coherency-weight table? = Yes.
Matrix Type: DICE
Normalize stack back?

Required if Output: = Signal & Original. If "Yes" is chosen, after summing the signal trace with the
original trace, the output trace will be normalized.
362
DICE3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
DICE3D will perform time variant signal enhancement to 3-D stacks. DICE3D will extract the signal
along the dominant dip within a plain and then sum the signal with the original trace. The dominant dip
direction is measured by finding the maximum coherency along a range of dips from neighboring traces at
each sample. If the maximum coherency is less than a user specified threshold level, no signal will be
extracted. After signal extraction, the coherency is measured between the signal and the original trace at
each sample. The coherency is then used to calculate a weight to apply to the signal trace before summing
with the original trace. For Q.C., the user can output additional data sets such as the maximum signal,
coherency, dip, or azimuth. Header word 71 will be set to 1, 2, 3 or 4 in the signal, coherency, dip, or
azimuth data sets.
DICE3D will drop dead and auxiliary traces.
Input Channels
Output Channels
1.
2.
3.
4.
5.
Signal+original: Required connection to next process GCI data type.

Signal: Optional GCI data type.
Coherency: Optional GCI data type.
Dip: Optional GCI data type.
Azimuth: Required GCI data type.
Parameters
Number of traces within an ensemble to use
This is the number of neighboring traces within an ensemble to use to determine the dominant dip.
DICE3D will force this number to a higher odd number. If the input data is X-bin stack sorted, this is the
number of MBIN traces to use.
363
Number of ensembles to use

This is the number of neighboring traces between ensembles to use to determine the dominant dip.
DICE3D will force this number to a higher odd number. If the input data is X-bin stack sorted, this is the
number of MLIN traces to use.

Minimum dip within an ensemble (Ms/trace)

Maximum dip within an ensemble (Ms/trace)

Dip increment within an ensemble (Ms/trace)
This is the dip increment in Ms. per trace between the minimum and maximum dip defined above.
DICE3D will determine the coherency at each dip increment.
Minimum dip between ensembles (Ms/trace)

Maximum dip between ensembles (Ms/trace)
Dip increment between ensembles (Ms/trace)
DICE3D will determine the coherency at each dip increment.

Use the turbo version?
The turbo version is faster, uses more memory and has a slight interpolation error. It is appropriate if the
dip increment is a multiple of the sample rate(ms) divided by 10. For example: if the sample rate is 4ms.
and if you roughly measured a 1.7ms/trace dip increment then the dip increment should be 1.6 (4*4/10) or
2.0 (5*4/10).
Minimum trace number within an ensemble

This and the next parameter are used to allocate space. The default assumes the ensemble key for the input
data is MBIN. The numbers input should reflect the range of the ensemble key.
364
Maximum trace number within an ensemble

This and the previous parameter are used to allocate space. The default assumes the ensemble key for the
input data is MBIN. The numbers input should reflect the range of the ensemble key.


summing with the original data at the coherency defined in the previous parameter. DICE3D will linearly


Matrix Type: DICE

If "Yes" is chosen, after summing the signal trace with the original trace, the output trace will be
normalized.
365
DIPMOD
Module Description
Input Channels
Output Channels
Parameters
Module Description
DIPMOD processes ensembles of traces containing dip, azimuth and coherency data (as data sets signal,
coherency, dip, or azimuth output by DICE3D). A header word (DICE3D uses header word 71) is used to
define each data set. Data input to DIPMOD should be sorted in ensembles containing all three traces from
a given analysis location (such as MLIN and MBIN). The header word and header values to define each
attribute may be specified.
The output from DIPMOD consists of two dip traces and a "switch" trace. The dip traces are computed
from the input dip and azimuth traces. They are the X and Y dip components in samples. The X dip
component is in the zero azimuth direction. Note that this is relative to the input azimuth trace values,
NOT the SeisUP header (word 82) azimuth values. Also note that if DICE3D is used to compute the input
traces, the zero azimuth dip is oriented in increasing secondary header direction (as input to DICE3D) and
its sense is Cartesian (increasing counter clockwise).
The "switch" trace will be "1" or"0" depending on coded threshold values, the input trace values and the
action parameter. The action parameter chooses between setting the switch trace or nulling the dip traces.
The switch is 1 (or the dips are zero) if the coherency is greater than a coded threshold and the dip is less
than a coded threshold. Either threshold may be ignored.
Header DIST is set to 5, 6 and 7 for the dip X component, dip Y component and "switch" respectively.
Input Channels
Output Channels
Parameters
366
Header Containing Component ID

TLSN, other
Header ID Index for Component ID

Required if Header Containing Component ID is Other.
Signal Component ID
Coherency Component ID
Dip Component ID
Azimuth Component ID
Coherence Threshold
Dip Threshold
Coded in MS.
Action if threshold fails

Options: Zero "Switch", Zero "Dip"
367
DISINTG
Module Description
Input Channels
Output Channels
Parameters
Module Description
DISINTG is equivalent to a 90 degree phase-shift filter. It is actually the derivative of the input trace.
Input Channels
Output Channels
Parameters
None
368
DISPLAY
Module Description
Input Channels
Output Channels
Parameters
Module Description
DISPLAY is an interactive program that will display seismic data. The DISPLAY window consists of a
large area below the menu bar that will display seismic data. The area can be scrolled around if the display
cannot fit within the window. The window title will show the display number within the queue sequence
(if multiple DISPLAY modules are in the queue). To the right of the seismic display is the menu icon bar.
The menu icons can be used instead of using the menus. If you opened a picking function from the Pick
menu icons will appear to the left of the seismic display. Multiple picking functions can be opened. The
current picking function can be selected by pressing the appropriate pick icon.
Within the seismic data display window, the seismic data will be annotated at the top of the section with
the current ensemble header key word (See GCI data type). Below the seismic data will be certain trace
header values that correspond to either the mouse position when the data is displayed or while the left
mouse button is being dragged across the data display. The values displayed at the bottom are:
1.
2.
3.
4.
The time in milliseconds or the depth.

The trace header value for the primary header key word if one exists (see GCI data type).
The trace header value for the secondary header key word if one exists (see GCI data type).
If the data is pre-stack, then the following will be displayed:
Sequential shotpoint number (SSPN)
Sequential geophone number (SGEN)
Source to receiver distance (DIST)
Field channel sequence number (FCSN)
If the data is post-stack, then the following will be displayed:

Field shotpoint number (FSPN)
Selecting an area
Before you can zoom, perform a header dump, or perform auto scaling you must select the area to perform
the operation on. To select an area:
1. Press the left mouse button on the first trace you want to select.
2. Drag the mouse. You will see the trace header values displayed at the bottom of the seismic display.
An outline of a rectangle will also be displayed.
3. Release the mouse button on the last trace that you want to select. The outline will remain, showing
the traces and samples selected.
369
In the new version of DISPLAY (SeisUP 2003) it is possible to highlight multiple regions at the same
time. To select additional regions hold down the Shift key while dragging as described above. You will
see that when two or more selections are present, each selection rectangle will be tagged in the upper
left-hand corner with a unique number. This number is used to associate spectral analysis plots with each
selection in the Spectral Analysis tool.
When multiple selections are present, any operation that works with one selection rectangle (i.e. Zoom,
Header Dump, or Auto Scaling) will use the most recently added selection region. That is, if I have three
selection rectangles drawn in the display, the Header Dump will display the header information for the
traces contained within the selection rectangle labeled "3".s
Animation and comparison

DISPLAY will allow you to save previously displayed images in the X-windows server and then animate
the images over a selected window. To save the previous images, change the parameter Save an image for
every DISPLAY? to Yes when for example performing a filter test where a DISPLAY is connected to
every FILTER module. Or change the parameterNumber of images to saveto some number of images to
save when a single DISPLAY module is being executed.
To display the previously displayed image, select an area to view and press the
pressing the recall icon to switch back and forth between the two images.
menu icon. Keep
Other images can be manipulated with the animation dialog. To show the animation dialog, select Animate
from the file menu or press the
menu icon. The following icons can be used:
Show the first image or frame.
Animate the frames in reverse order .
Step to the previous frame.
Continuously cycle through frames when reverse or forward animation is selected if this button is
pressed in. If this button is out, animation will stop when the last frame is reached.
Step to the next frame.
370
Animate the frames in forward order.
Show the last frame.

Use the Frame slider to manually cycle or select a frame and use the Speed slider to adjust the number of
frames per second for animation.
To compare say the first and fourth frame:
1. Show the first frame by using the step icons or the Frame slider.
2. Show the fourth frame by using the Frame slider.
3. Press the Recall icon repeatedly.
To perform a filter or decon test:
1.
2.
3.
4.
Set up a flow with say a FILTER module:

Make sure the parameter Save an image for every DISPLAY? is set to Yes.
Modify the parameters for each FILTER.
Select all of the modules and execute them.
5. Press the
icon until the window title for DISPLAY is Display # of # is displayed, where # is
the number of FILTERs. In this case three.
6. Select an area in the seismic display to compare or animate.
7. Press the
icon and interact with the dialog to animate or compare different filters.
371
Changing the plotting scale

To change the scale of the plot you can change the inches per second or the traces per inch parameters.
You can also change the scale by performing the following operation:
1. Press the middle mouse button in the seismic display.
2. Drag the mouse. You will see the trace annotation turn to red. The width of the plot can be changed
by moving the mouse to the left or right. The height of the plot can be changed by moving the mouse
up or down.
3. Release the mouse button. The seismic data will be redrawn at the new scale.
Viewing the next ensemble

To view the next ensemble, select Next from the File menu or press the
change to an hour glass while retrieving the next ensemble.
menu icon. The pointer will
Viewing a user selected ensemble

To view a user selected ensemble, select Seek ensemble from the Filemenu or press the
menu icon.
To use this option, the input module must be the READ module. In addition, you cannot use the default
Read sequential sort order. When you use this option, DISPLAY will request the READ module to read
the user specified ensemble number. You cannot change the sort order between the READ module and the
DISPLAY module. The user should be aware that if the data from DISPLAY is passed to the next module
and this option is selected, duplicate and/or missing data could result in the output data.
Zooming
To zoom an area, select an area to zoom and select Zoom from the File menu or press the
menu
icon. A dialog window will appear that will zoom the selected window by two times. The scroll bars in the
zoom window will allow you to navigate through the ensemble. As you move the scroll bars, the selected
area in the main display will reflect the location of the data within the zoomed window. To increase or
decrease the zoom factor, resize the window. If you proceed to the next ensemble, the zoom window will
redisplay the selected area. To close the zoom window, selectClose from the window menu.
Trace dump
To perform a trace dump, select an area to perform a trace dump to and select Trace dump from the File
menu A dialog window will appear that will display the trace sample values, the time or depth, and a line
printer style plot. Press the Close button at the bottom of the window to close the trace dump window.
372
Header dump
To perform a header dump, select an area to perform a header dump to and select Header dump from the
File menu or press the
menu icon. A dialog window will appear that will display certain header
values. Press the Close button at the bottom of the window to close the header dump window. To
customize the header dump listing press the Customize button and the following will appear:
The following functions can be used to customize the header dump display:
Properties: Change the field width and data type for the selected trace header. The data type can be
Integer, Float, Coordinates, or ASCII. If Coordinates is selected, the scale value in the trace header
will be applied to the header value and displayed as a floating point number. The trace headers SX,
SY, GX, GY, MCX, and MCY all default to a 9 digit width and Coordinates as the data type. The
trace header LINE defaults to a 8 wide ASCII data type.
Delete: Delete the selected trace header from the header dump listing.
Add: Add a trace header to display in the header dump listing. A dialog will appear with a list
containing all possible trace header words. Select a trace header and then press the OK button to add
a trace header to the header dump listing. Optionally a user can enter a header word index or header
word name in the text field.
Shift Up: Shift the selected trace header up (left in the listing).
Shift Down: Shift the selected trace header down (right in the listing).
Close: Close the customize dialog.
Help: Display this help file.
Auto scale
To automatically compute the gain factor to apply to the data, select an area to calculate the average RMS
amplitude from and select Auto-scale from the File menu or press the
373
menu icon. The data will be
displayed with the new gain value. For non-amplitude data like RMS velocities or Hilbert transform
attributes, DISPLAY will calculate the gain and bias from the minimum and maximum values.
Fourier spectra
To display the Fourier spectra, select an area and select Spectrum from the File menu or press the
menu icon. Only the traces and samples selected within the selected area will be used for the Fourier
transform. For multiple traces, the Fourier spectra for each trace will be averaged. After the Fourier
transform is performed, a display will appear that contains two plots. The top plot is the unwrapped phase
in degrees versus frequency in Hz. plot. The bottom plot is the amplitude versus frequency in Hz. plot.
File menu
Next
View the next ensemble
Seek ensemble
View a user selected ensemble
Recall
Show previous displayed image or frame
Animate
Show animation dialog
Zoom
Zoom the selected area
Header dump
Header dump the selected area
Trace dump
Trace dump the selected area
Auto-scale
Automatically compute the gain factor to apply to the data
Spectrum
Display the Fourier spectra
Change parameters
Change display parameters
Refresh
Force a redisplay of the traces.
Edit color
Show the color editor dialog
Print ...
Print the trace display
Quit
Quit the current set of modules.
374
View menu
Use the View menu to perform the following operations:
Apply Linear Moveout
Use this option to apply linear moveout to the input data.
Set LMO Velocity
Use this option to set LMO velocity.
Set Gain
Use this option to set the amount of gain in db to apply to the display. You can also use the Plus or
Minus key to increase or decrease the the amount of gain in db.
Automatic Gain
This option is used to set the amount of gain in db automatically.
Show Timing Lines
Use this option to display the timing lines.
Overlay Group Elevation (EG)
Use this option to Overlay Group Elevation.
Overlay Static (STAT)
Use this option to set Overlay Static (STAT)
Overlay Trace Header
Use this option to display a specific trace header graph.
Set Overlay Scale
Use this option to set the scale.
Show Colors
This option is available only in color mode. Use this option to edit color scheme, load the colors, save
the colors, and to delete the color schemes.
Tools menu
Use the Tools menu to perform the following operations:
Header dump
See the documentation above for header dump.
Trace dump
See the documentation above for trace dump.
Spectral Analysis
See the documentation above for Fourier spectra.
Display Header...
Graph any number of header values for the currently displayed traces in a separate window. Use the
Select header... option from the File menu to determine which headers are graphed or redefine the
scale on which they are plotted. The header graph is automatically updated when the trace display
changes.
Display Amplitude...
The user can graph (RMS or Average) amplitude of selected data in a separate window. The
amplitude graph does not automatically follow the users selection.
375
Zooming
See the documentation above for zoom.
Trace Rendering Benchmark
This option for trace rendering benchmark.
Pick menu
Use the Pick menu to perform the following operations:
Open
Open a picking function.
Close
Close the current picking function.
Parameters
Change parameters for the current picking function.
Circulate
Circulate the current picking function. With pick functions such as time windows where there are
multiple start and end gates, Circulate can be used to switch the another gate. If the current gate is the
last one, selecting Circulate will make the first gate the current one.
Open menu within the pick menu

When opening a pick function, a parameter dialog will appear requesting parameters. A pick icon will also
be displayed to the left of the seismic display that will represent the picking function. Use the open menu
to open the following picking functions:
First breaks
First Breaks Database
This option is used to pick the first breaks.
Shot Statics Database
When this option is selected, the picks are based on SSPN ( Sequential Shot Number ), and
saved in the STATSRC matrix.
Receiver Statics Database
When this option is selected, the picks are based on SGEN ( Sequential Gephone Number ), and
saved in the STATGEO matrix.
Refractor model
Pick a refractor model for picking first breaks with this module or with module RFS1.
Gain curves
Pick gain curves for module GAIN.
Kill traces
Pick trace kills for module OMIT.
376
Reverse polarity
Pick polarity reversals for module OMIT.
Horizon
Pick a horizon for module HORIZON.
Mute
NMO mute
Trace mute
Surgical mute
Windows
Pick time or depth window gates for modules such as DECON, FILTER, and SGN1.
F-K analysis
Pick polygons for module FKFILT.
Geometry
View and/or modify the shot location.
First break picking

When picking first breaks, the picked time can be optionally modified to the nearest peak or trough. With
automatic picking, the first break will be predicted using the previously picked common geophone and the
refractor model, then the pick can be modified to the nearest peak or trough. The refractor model by
default is calculated using the refractor velocity. For finer control of the refractor model or to pick an
offset variant refractor model, you can interactively pick a refractor model. The following mouse functions
are allowed with the first break picker:
Button 1
Pick the current trace and any traces to the left of the current trace.
Button 2
Pick only the current trace.
Button 3
Pick the current trace and any traces to the right of the current trace.
Shift-Button 1
Pick the traces along a line created by pressing shift and the left mouse button on the first trace for
the line, dragging the mouse to the last trace, and releasing the mouse. The pick will be modified to
the nearest peak or trough.
Ctrl-Button 1
Pick the current trace at the mouse position or pick the traces along a line created by pressing shift
and the left mouse button on the first trace for the line, dragging the mouse to the last trace, and
releasing the mouse. Picks will not be modified to the nearest peak or trough.
Ctrl-Button 3
Delete the pick for this trace. If you keep the mouse down and drag the mouse across adjacent traces,
the picks for those traces will also be deleted.
377
The following parameters are used for picking first breaks:

1. Pick matrix: Enter the matrix name to contain the first break picks.
2. Pick type: Enter the type of pick adjustment to use after the initial pick is make. Select Peak to
adjust the pick to the nearest peak. Select Trough to adjust the pick to the nearest trough. Select
None to not adjust the initial pick.
3. Refractor Velocity: Enter the first break refractor velocity.
4. Refractor Model: Enter the custom refractor model that is used to predict the initial first break pick.
The default is to compute the refractor model using the first break velocity.
5. Use total static header?: Select Yes to add the value in the trace header total static location to the
pick times. To improve the appearance of the data for first break picking the user may wish to apply
field statics. Statics should only be applied to help first break picking. Make sure other statics are not
applied prior to applying the Refractor Statics.
6. Search for maximum energy? Select Yes to search for the maximum energy within a window using
a stabilized power ratio algorithm.
7. First break energy envelope width (ms) Enter the average width of the energy envelope in
milliseconds of a typical first break signal. The energy envelope can also be called the refraction
train. A typical refraction train is 120 ms. to 500 ms in length. This parameter is used only if
searching for the maximum energy.
8. Power ratio stabilization factor Enter a percentage of the power of the entire trace to add to the
trailing window. This factor will help stabilize the leading-to-trailing power ratio. The suggested
range is 0% to 40%. This parameter is the most critical value to change when attempting to get the
picker to work properly. If the pick is lower in time than intended, then decrease the stabilizer. If
there are many false picks, then increase the stabilizer. This parameter is used only if searching for
the maximum energy.
9. Pick window (ms.) Enter the length of the pick window in milliseconds. The first break pick should
reside within this window. The leading and trailing window envelope entered above is added to this
value. This determines the analysis window for automatic first break picking. This parameter is used
only if searching for the maximum energy.
Picking a refractor model

To pick a refractor model for first break picking with the DISPLAY or RFS1 module, select Refractor
model from the Pick-Open menu A red line will represent the interpolated refractor model. Times will be
extrapolated for offsets picked before the first pick and after the last pick. Picked points will be drawn
with a red X.
The following mouse functions are allowed when picking mute functions:
Button 1
Add or insert a pick at the current trace.
Button 2
Delete the pick closest to the current trace.
378
Button 3
Move the pick closest to the current trace to the current trace.
Gain curve picking

To pick gain curves for module GAIN, select Gain curves from the Pick-Open menu. A parameter dialog
will appear to request parameters. After the parameters are picked another window will appear on the right
hand side of the screen with a window title of Gain analysis. The top portion of the window is reserved for
the computed gain curve. At the bottom of the window are two buttons as follows:
Close
Will close the matrix file and the gain analysis window.
Analyze
Will perform a gain analysis over the selected traces in the seismic display window.
When a gain analysis is performed the gain curve is calculated as follows:
1. Compute an average gain curve from each trace by computing the instantaneous amplitude.
2. Compute the log base 2 gain curve.
3. Smooth the gain curve using the smoothing window size.
If there are any existing gain functions within the selected area, the picks for that gain function will be
displayed. For traces that match existing gain functions, a blue V will be displayed on top of the trace. If
there are no existing gain functions within the selected area, the primary and secondary id is taken from
the middle trace.
The following mouse functions are allowed within the gain analysis:
Button 1
Pick the gain value at the current mouse location.
Button 2
Delete the last time pick.
The Primary and Secondary ids within the parameter dialog should correspond to the sort order of the
data when multiple gain functions are to be picked. If you change the primary and secondary ids, make
sure you also change the ids in the parameters for the GAIN module.
Picking trace kills

To pick trace kills for the module OMIT, select Kill traces from the Pick-Open menu. Traces that are
selected for trace kill will have a red line drawn through the baseline from the start time to the end time.
Traces selected for trace kill will passed to the next process as a dead trace. The following mouse
functions are allowed when picking trace kills:
379
Button 1
Kill the current trace.
Button 3
UN-kill the current trace.
Ctrl-Button 1
Kill any trace at the current mouse location while the mouse button is depressed.
Ctrl-Button 3
UN-kill any trace at the current mouse location while the mouse button is depressed.
Picking polarity reversals

To pick polarity reversals for the module OMIT, select Reverse polarity from the Pick-Open menu. Traces
that are selected for polarity reversal will have a red line drawn through the baseline from the start time to
the end time. DISPLAY will reverse the polarity and redisplay any trace selected for polarity reversal.
Traces selected for polarity reversal will passed to the next process with the polarity reversed. The
following mouse functions are allowed when picking polarity reversals:
Button 1
Reverse the polarity for the current trace.
Button 3
Restore the polarity for the current trace.
Ctrl-Button 1
Reverse the polarity for any trace at the current mouse location while the mouse button is depressed.
Ctrl-Button 3
Restore the polarity for any trace at the current mouse location while the mouse button is depressed.
Picking horizons
To pick horizons for the module HORIZON, select Horizon from the Pick-Open menu. A blue line will
represent the interpolated horizon from all horizons in the matrix. A red line will represent a horizon at the
current primary id location (See Primary & Secondary ids below). Picked points will be drawn with a red
X. The following mouse functions are allowed when picking horizons:
Button 1
Button 2
Button 3
380
Picking mutes
Picking normal moveout mutes:
To pick normal moveout mutes, select Mute->NMO mute from the Pick-Open menu. A blue line will
represent the interpolated mute between mute functions. A red line will represent a mute function at
the current primary id location (See Primary & Secondary ids below). Picked points will be drawn
with a red X.
Optionally the trace headers TIM1 or TIM2 may be subtracted from the picked times prior to creating
the NMO mute matrix. In this case, make sure you select the same TIM1 or TIM2 trace header entry
when applying the NMO mute matrix with for example the NMOR module.
The following mouse functions are allowed when picking mute functions:
Button 1
Button 2
Button 3
Picking trace mutes:
To pick trace mutes, select Mute->Trace mute from the Pick-Open menu. A blue line will represent
the interpolated mute between mute functions. A red line will represent a mute function at the current
primary id location (See Primary & Secondary ids below). Picked mute points will be drawn with a
red X. A line will be drawn to represent start time, and end time for picks. The current line can be
selected by selecting Circulate from the Pick menu or pressing the
menu icon. The current line
will be appear as thicker red line than the other line. Picks on start and end line after the picking the
mutes must be placed at the same secondary id on the start time line for line one.
The trace mute interpolates the last spread sheet up to the end, therefore if the mute need to be
stopped at a certain tertiary key value for example (OIDN, SSPN, or SDPN) then next spread sheet
should be created, by picking the end mute time as zero or one sample.
The following mouse functions are allowed when picking the mutes:
Button 1
Add or insert a pick at the current trace. If the current line is after the starting time line one, then
the pick will be placed at the closest pick on the start line one.
Button 2
Delete all picks on the trace closest to the current trace.
Button 3
Move the pick closest to the current trace to the current trace. This function is the same as button
1 when the current line is after the starting line one.
Surgical mutes:
381
To pick surgical mutes, select Mute->Surgical mute from the Pick-Open menu. A blue line will
represent the interpolated mute between mute functions. A red line will represent a mute function at the
current primary id location (See Primary & Secondary ids below). Picked mute points will be drawn
with a red X. A line will be drawn to represent start time, and end time for picks. The current line can
be selected by selecting Circulate from the Pick menu or pressing the
menu icon. The current
line will be appear as thicker red line than the other line. Picks on start and end line after the picking the
mutes must be placed at the same secondary id on the start time line for line one. The following mouse
functions are allowed when picking the mutes:
Button 1
Add or insert a pick at the current trace. If the current line is after the starting time line one,
then the pick will be placed at the closest pick on the start line one.
Button 2
Button 3
Move the pick closest to the current trace to the current trace. This function is the same as
button 1 when the current line is after the starting line one.
Picking F-K polygons

To pick polygons for module FKFILT, select F-K analysis from the Pick-Open menu. A parameter dialog
will appear to request parameters. After the parameters are picked another window will appear on the right
hand side of the screen with a window title of F-K analysis. The following functions are available within
the F-K analysis:
Will perform a F-K analysis over the selected area in the seismic display window.
Will F-K filter the selected area in the seismic display window using the picked polygons(s).
Will swap the input and F-K filtered data in the seismic display window.
Show the color editor dialog.
Change F-K display parameters.
382
Create a new polygon.
Save the picked polygon(s) to a matrix for module FKFILT.
Close the current picking function.

To create a polygon:
1. Select an area in the seismic display window.
2. Press the left mouse button in the F-K spectra at the first polygon point.
3. Continue to press the left mouse button for additional points. An outline of the polygon will be drawn
as you pick. Optionally you can press and hold the button to drag the polygon using rubber band
lines.
4. Press the middle or right mouse button to terminate picking of the polygon.
When multiple polygons are present, the current polygon will be drawn with a thick line and each point
surrounded by a box. The other polygons will be drawn with a thin line. If the you wish to modify a
polygon that is not the current polygon, press the left mouse button in the area of the polygon that you
wish to modify.
Use the following mouse functions to modify a polygon:
Button 1
Insert a pick at the closest edge in the polygon. Optionally you can press and hold the button to drag
the polygon using rubber band lines.
Button 2
Delete the pick closest to the mouse location.
Button 3
Move the pick closest to the mouse location to the current location. Optionally you can press and
hold the button to drag the polygon using rubber band lines.
Picking windows
To pick windows or time gates for modules such as DECON, FILTER, and SGN1, select Windows from
the Pick-Open menu. A blue line will represent the interpolated window between window functions. A red
line will represent a window function at the current primary id location (See Primary & Secondary ids
below). Picked points will be drawn with a red X. The Number of windows parameter is the number of
windows required for the module. For DECON this would correspond to the number of deconvolution
operators. A start and end gate will be drawn for each window. The current gate can be selected by
383
selecting Circulate from the Pick menu or pressing the

menu icon. The current gate will be appear
as thicker red line than the other gates. Picks on start and end gates after the window one must be placed at
the same secondary id on the start gate for window one. The following mouse functions are allowed when
picking windows:
Button 1
Add or insert a pick at the current trace. If the current gate is after the starting gate for window one,
then the pick will be placed at the closest pick on the start gate for window one.
Button 2
Button 3
Move the pick closest to the current trace to the current trace. This function is the same as button 1
when the current gate is after the starting gate for window one.
Geometry Q.C.
The shot location may be viewed, moved, and optionally updated to a source spreadsheet. The following
parameters are used for geometry Q.C.:
Refractor Velocity: If linear moveout is not applied, this parameter and the next are used to display
a line above the predicted first breaks using the current geometry.
Refractor bulk shift (ms.): If linear moveout is not applied, the number entered will be used to shift
the line above the predicted first breaks.
Source specified by: The options allowed are:
X-Y: Source location specified by X and Y coordinates.
Receiver: Source location specified by receiver location.
Layout (X-Y): Source location specified by coordinates and receivers by spread layout.
Layout (Receiver): Source location specified by receiver location and receivers by spread layout.
Shot matrix to update: Source spreadsheet to update when the shot location is changed. This
spreadsheet is only modified if the Save button in the geometry display is pressed. It is suggested that
you copy your original source spreadsheet to a new one before updating the shot location back to the
database. If the spreadsheet is modified, make sure that you run the SOURCE module on the
modified spreadsheet and apply the geometry to the data with the GEOM module.
Header for shot ID:This is the trace header to use to match the trace with the ID in the source
spreadsheet. This should be the same trace header used in the GEOM module.
Use the following mouse functions in the main seismic display window to view the geometry:
Button 1
Display the geometry using the current geometry.
Button 3
Press and hold the button to drag the shot location flag to a new shot location. When the button is
released, the geometry will be displayed.
384
The geometry display consists of the map view on the left side of the window with the shot location
displayed with a red box, the closest receivers displayed with a blue circle and any other receivers
displayed as black receivers. The traces corresponding to the closest receivers will be displayed in the
right side of the window. At the bottom of the window is the current shot location information. To move
the shot location perform one of the following:
Press and hold the left mouse button in the map view to move the shot to a new location.
Change one of the shot location text widgets at the bottom of the window. WARNING: press the
return key in the text widget after modifying the value.
The following button are available in the geometry display:
Close: Close the geometry display.
Apply: Apply the current geometry changes to the main seismic display.
Save: Save the shot location changes to the currently defined shot spreadsheet.
Reset: Reset the geometry to the original location when the geometry display was first show.
Cancel: Reset the geometry to the original location and close the geometry display.
Help: Display this help file.
Receiver Geometry QC
The traces may be adjusted up or down, and optionally saved to a STATION spreadsheet. Apply linear
moveout to the input data before using this option. In the parameter window, select Apply LMO? as Yes
From pick menu select Receiver Geometry QC
A dialog will popup.
385
Fill the dialog form. Press OK Button

Keep the Simulation mode to NO if you want to save the adjusted traces to the new STATION file.
Select the traces in the display window. Use up and down arrow buttons to adjust the traces.
When you are done fixing, go to the pick menu again and select Close button.
A dialog will popup.
Press Commit button.

Another dialog will popup.
Press Continue Processing button. Or Press Add Shots button to Specify Additional Shots.
You can view the current status in the execution status file. The new STATION file will be saved in
the database.
Primary & Secondary ids

Some of the picking functions such as NMO mute and Windows request a primary and secondary key. If
the primary or secondary id is changed, make sure that when using the matrix for processing that you also
change the primary and secondary ids in that module.
DISPLAY will set the primary id to the minimum primary id within the current ensemble when picking
NMO mutes, horizons, or windows. Multiple primary ids per ensemble are not allowed. This will, for
example, allow functions to be picked on shot records.
386
Input Channels
2. Optional overlay: Optional GCI data type.
Output Channels
1. Output: Optional connection to next process GCI data type.
Parameters
Plot Type
Options: Wiggle, Wiggle & VA, Color, Color & wiggle, Color & wiggle
& VA, Wiggle & color VA
Use variable trace spacing?

Select Yes to display traces in irregular intervals, as determined by the values at a given header index. The
user can fix the size of the canvas on which the traces are drawn by defining a min and max range for the
given header and a units per inch metric. In this case, traces with identical header values for the given
header index will always be drawn in the same location.
GCI header index for trace spacing.

Input the GCI header index that should determine the space between traces. The default is the
ensemble key.
GCI header index min. value.

Input the minimum value for the given header index that should be displayed. The default is to define
no minimum thus omitting no traces.
GCI header index max. value.

Input the maximum value for the given header index that should be displayed. The default is to define
no maximum thus omitting no traces.
387
Units per inch.

Instead of traces per inch the user should define a measurement relative to the range of expected
header values. For instance, if header DIST is being used and the typical range is -5000 to 5000 a
reasonable units per inch would be 500, which would equate to a display canvas 20 inches wide. The
default is to display all traces.
Traces per inch

Enter the number of traces per inch for the trace display. The default is to compute a traces per inch such
that the entire ensemble will fit in the display.
Inches per second

Enter the number of inches per second for the trace display.. The default is to compute an inches per
second such that the entire trace length will fit in the display.
Apply automatic gain

If automatic scaling is chosen, DISPLAY will compute the average RMS amplitude level over the first
ensemble of traces. For non-amplitude type data like RMS velocities or Hilbert transform attributes, the
scaling is determined by the minimum and maximum values.
Specify amplitudes by a range of values?

Select No to specify the range of amplitudes using the gain in db. and a bias. Select Yes to specify the
range of amplitudes using the minimum and maximum values.
Gain (Db)
The amount of gain in db to apply to the data before plotting.
Bias
Percent of deviation on the baseline.
Amplitude corresponding to min. value

Specify the sample value corresponding to the minimum clipped value. For color displays, this is the
minimum color index.
388
Amplitude corresponding to max. value

Specify the sample value corresponding to the maximum clipped value. For color displays, this is the
maximum color index.
Clip (traces)
The number of trace spacings from the baseline at which the variable area shaded side of the trace will be
clipped. For color the minimum and maximum amplitude can be determined from this parameter to scale
the amplitudes over the number of colors in the color map.
Number of ensembles to display

This is the number of input ensembles to display with each ensemble separated by a vertical pane. The
first ensemble will be placed into the bottom pane. When the next ensemble is read, the ensembles will
scroll upwards.
Multiple-ensemble-display orientation
When the number of ensembles to be displayed is greater than one, this parameter will become visible
allowing the user to specify the primary orientation of the ensemble panes. The default is horizontal,
which means that the width is larger than the height, and the multiple ensembles are stack on top of one
another. Vertical will make the height of the ensemble pane larger than the width, and each pane will be
stack side-by-side.
NOTE: If you specify a vertical orientation, but the ensembles display with a horizontal orientation, then
you need to check to make sure you are using version 2.1 of the Motif runtime library. If your system is
using Motif 1.2, then multiple ensembles will always be displayed with the default horizontal orientation.
Options: Horizontal, Vertical
Ensemble alignment header key

If the Number of ensembles to display parameter is greater than one, this parameter allows you to align the
traces between each pane by a common header word. A typical example is using the SGEN (receiver)
header for shot sorted data when picking first breaks.
Options: None, CDPN, DIST, DMODIST, FCSN, FSPN, MBIN, MLIN, MSBN,
MSLN, OIDN, RSBN, RSLN, SDPN, SGEN, SBIN, SLIN, SSBN, SSLN, SSPN,
TIM1, TIM2, TLSN, Other
Ensemble alignment header index

If Other is chosen for parameter Ensemble alignment header key provide the header word index here.
389
Annotate time on each ensemble

When the number of ensembles to be displayed is greater than one, and the ensemble orientation is vertical
this parameter will be visible. Switching this parameter to No will remove the time annotations for the
ensembles displayed in the interior panels, saving screen space for trace rendering.
Save an image for every Display?

See Animation and comparison above. This option is only allowed if the Number of ensembles to display
parameter is one.
Number of Images to Save

See Animation and comparison above.
Draw timing lines?

Timing Line Increment
Enter the increment between timing lines in milliseconds.
Plot Direction
Options: Left to Right, Right to Left
Polarity
Options: Normal, Reverse
Apply LMO?
Select Yes to apply linear moveout to the input data. This is typically done to flatten the first breaks for
first break picking or geometry Q.C.
LMO Bulk Shift (ms)

This is the bulk shift to apply the input data after applying linear moveout.
LMO velocity
390
Start Time (ms)

Enter the start time to plot.
Ending Time (ms)

Enter the ending time to plot.
Colormap
If a color display is being produced select the color map to be used. The default is dependent upon the data
type.
Overlay Gain (Db)

The amount of gain in db to apply to the overlay data before plotting. This parameter requires the Overlay
input channel to be connected.
Overlay Clip (traces)

clipped. This parameter requires the Overlay input channel to be connected.
Overlay Bias
This parameter requires the Overlay input channel to be connected.
Display Window Title

The given title will displayed at the top of the window.
Window Size and Location

Specify a window size and location. By default the window will fill the screen (or perhaps several screens
making up a virtual desktop). Alternatively, choose to define specific window geometry or pick from the
list below a predefined window geometry.
Options: Full Screen, User Defined, Left Half, Right Half, Top Half,
Bottom Half, 1 of 4 Left to Right, 2 of 4 Left to Right, 3 of 4 Left
to Right, 4 of 4 Left to Right
If User Defined is chosen for parameter Window Size and Location provide the following 4 window
geometry parameters:
391
Window x origin
Window y origin
Window width
Window height
Annotate additional header?
Select Yes to input a GCI header index which will be used to annotate the trace data. The header values
will be displayed above the ensemble key header values.
GCI header index to annotate.

Spectra of multiple dsets?
392
DLIST
Module Description
Parameters
Module Description
DLIST is a stand alone module that creates a list of files of the given directory.
If you want to create a list of files for the given extension in all the sub directories, then for the parameter
Search directory tree? select Yes.
The list of files in all subdirectories will be created.
The list is created in the home directory. This list can be imported into a FILES matrix, which can be used
by the SEGYREAD, and RFMT modules if these parameters are used:
SEGYREAD: Use alternate disk file import method?
RFMT: Alternate file import method using a matrix?
See also: RFMT, and SEGYREAD.
Parameters
393
Enter dir fullpath.

Output filename.
Extension to input files.
Search directory tree?
Select YES to search sub-directories.
Options: YES, NO
394
DMO3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
DMO3D is the 3-D DMO stack or common offset application. After NMO removal (true RMS velocities),
DMO3D will apply "Theta DMO" and output stacked data. If common offset sorted data is input to
DMO3D, the output will also be common offset sorted with DMO applied. See the module DMODIST for
further details. A partial dataset is saved to a temporary disk file to enable program restart.
DMO3D is a true amplitude dip moveout process that will correct for azimuthal variations. This integral
(Kirchhoff-style) DMO algorithm will compute a series of zero offset traces corresponding to locations
between the source and the receiver and sum them into stack bins. For most integral DMO algorithms,
application of a 45 degree phase shift is required to correct phase distortions, Deregowski (1985) noted
that the 45 degree phase shift is appropriate only for large offsets and small times. In our 3D "Theta"
DMO program, the phase are corrected for all times and offsets with a varying filter. This algorithm is
able to achieve virtually the same results as from FK algorithms except that our algorithm will treat the
amplitude for all dips equally. FK algorithms tend to gradually attenuate amplitudes as the dip increases.
If FLEX has been applied and traces have not been duplicated in the module GEOM and FLEX causes a
trace to be summed into a bin with no non-FLEXed traces, then that CMP will not be output. This can
happen if all of the traces contributing to a CMP are all FLEXed traces. This is of particular concern if
common offset data is input. To avoid this problem, duplicate the FLEX traces with the modules GEOM.
DMO3D will use the following trace headers:
Header name
Description
DIST
HDR(21)
SX
SY
GX
GY
MUTST
MUTEND
Source to Receiver distance

Scalar to be applied to all coordinates
Source X coordinate
Source Y coordinate
Receiver X coordinate
Receiver Y coordinate
Mute start. Set to zero upon output.
Mute end. Set to the number of zero samples
preceding the first live sample.
Midpoint bin number
Midpoint line number
Midpoint starting flex line number
Midpoint ending flex line number
Number of traces summed to this trace.
MBIN
MLIN
MSFL
MEFL
FOLD
395
Average Offset Distribution

The Average Offset Distribution is the way to describe the offset distribution in a CMP versus
source-to-receiver distance manner. The following parameters are required:
1. Minimum offset: This should be the average minimum source-to-receiver distance.
2. Offset pattern: This is the increment in CMPs between identical offset distributions. With traditional
marine geometry, e.g. 120 chan 60 fold, every other CMP contains identical offset distributions. On a
common offset display, every other CMP would be missing. Usually the following formula can be
used:
Shot interval
Offset pattern = ------------CMP interval
NOTE: For an offset pattern of zero, the offsets are not modified and the minimum and maximum
offsets should be the absolute minimum and maximums, not the average.
3. Offset increment: This should be the difference between the common offset planes within a particular
CMP gather. Usually the following formula can be used:
Offset increment = Offset pattern * Geophone interval
4. Maximum offset: This should be the average maximum source to receiver distance.
The offset planes used for computations are an average offset over the offset patterns. For example, if we
define the following:
Minimum offset:
200
Offset pattern:
2
Offset increment: 50
In full fold, every odd CMP would contain offsets 200, 250, 300, 350,... The even CMPs would contain
offsets 225, 275, 325, 375, ... The average offset planes would contain 212.5, 262.5, 312.5,...
Offsets that fall between average offset planes will be adjusted to the nearest offset plane.
DMO 3D Input/Output Types

DMO 3D is capable of Input/Output of common offset stacks, stacks and pre-stack common midpoint
gathers (CMP(s)).
1. Common offset data is input, then the output will also be common offset data.
2. Pre-stacked data of any sort is input, then output may be stacked data or pre-stack CMP gathers. The
Desired CMP interval parameter determines the maximum fold that the pre-stack CMP gathers can
attain. If more than one trace falls within an interval, then the traces are stacked.
396
Max. CMP fold = ( Max. offset - Min. offset ) / CMP interval
References
Deregowski, S.M., 1985, An integral implementation of dip moveout: Presented at the 47th Annual EAEG
Meeting, Budapest, Hungary.
Deregowski, S.M., 1986, What is DMO?: First Break, v. 4, no. 7, p. 7-24..
Zhucheng Shang and Eugene Starr, 1991, A fast solution to the amplitude, phase, and aliasing problems in
integral DMO and migration: 61th Ann. Internat. Mtg. Soc. Expl. Geophys., Expanded Abstracts, p.
1215-1217.
Zhucheng Shang and Eugene Starr, 1991, Three-dimensional velocity-gradient DMO and overhang
imaging: 61th Ann. Internat. Mtg. Soc. Expl. Geophys., Expanded Abstracts, p. 1201-1203.
Hale, D., 1988, Dip moveout processing; SEG short course notes, Soc. Explor. Geophys.
Input Channels
Output Channels
1. Dataset to hold partial stacks: Required connection to dataset DNS1 data type.
2. Output data to next process: Required connection to next process GCI data type.
Parameters
Restart?
Select Yes to restart DMO3D after it previously aborted.
Output pre-stack data (i.e. CMP gathers)?

Use this feature to output pre-stacked CMP gathers. It has no effect if the input data is common offset
sorted data. It causes a very large increase in memory requirements if set to YES.
397
Desired offset interval in a CMP

Use this feature to set the offset interval within a CMP. This parameter is a distance. If more than one
trace falls within the offset interval then they will be stacked. Required if Output pre-stack data (i.e. CMP
gathers)? = YES.
Average RMS velocity in zone of interest

Algorithm to use
Constant velocity or depth-variable velocity. Depth-variable velocity is a time stretch method that works
best with smooth velocity models and modest velocity variation. The depth-variable option has minimal
run time penalty compared with constant velocity. Currently does not vary velocity laterally.
Options: Constant, V(z)
RMS velocities
Matrix describing the velocity function. Given in time and RMS velocity, program converts to interval
velocity internally. Required if Algorithm to use = V(z).
Matrix Type: RMSVEL
Offset pattern
Offset increment
Required if Offset pattern > 0.
Minimum offset
Maximum offset
398
Number of lines in the span

In shot DMO, this would typically be the difference between the minimum MLIN and the maximum
MLIN between shot lines plus the difference between the minimum Y coordinate and the maximum Y
coordinate on a shot line divided by the midpoint line interval. In other words, the maximum number of
midpoint lines between the source and the receiver between two shot lines.
When DMO3D is used for stack only (i.e. turn offset to zero), the number of lines in the span should be
more than the number of lines one shot gather covers.
Warning: too small a span size may lead to reduced fold.
Maximum dip before migration

Degrees of dip for taper
DMO3D will taper the DMO operator from the maximum dip (previous parameter). This will tend to
decrease the background noise at the expense of increased execution time.
Start taper value

Top of trace taper start value. Code this parameter as 1.0 to not apply a top of trace taper. The taper start
value will be multiplied by the trace at the mute time coded in the trace header and ramped up to a taper
value of 1.0.
Taper length(Ms.)
Length of top of trace taper in Ms.
Normalize output by fold?

Required if Normalize output by fold? = No.

Required if Normalize output by fold? = No and Stack Normalization technique = fold plus next parm.
399
Number of processors?
This is the number of processors you intend to use. DMO3D may decide to use more logical nodes to
handle datasets larger than 2 Giga bytes.
Restart data set flush interval (traces)

Enter the number of traces to process before flushing the partial stack data set to disk. The partial stack
data set is used to restart DMO3D if a previous execution of DMO3D aborted or crashed for some reason.
400
DMODIST
Module Description
Input Channels
Output Channels
Parameters
Module Description
DMODIST can be used in a step prior to running modules DMO3D, DMOS,... to apply DMO or migration
to common offset sections. This module is used to create a header word (DMODIST) that is used to sort
the data into common offset range sections. To apply to common offset sections perform the following:
1. Apply module DMODIST with the offset interval desired for the output of modules DMO3D,
KTMIG,... The offset interval parameters in modules DMO3D and DMOS are used to help prevent
aliasing. The offset interval in this module is used to stack a range of common offsets to create a
common offset stack section.
2. Sort the data with the READ or SORT modules with the sort order keys set to (DMODIST, MLIN,
MBIN) or (NONE, DMODIST, SDPN) where the keys are (Primary, Secondary, Ensemble). The sort
order key (NONE, DMODIST, SDPN) will only work with the module DMOS.
3. Apply the module DMO3D, KTMIG,... The output data will be common offset sorted.
TYPE
Queue
Input Channels
Output Channels
Parameters
401
Use fixed offset increment?

Select No to input a variable spaced offset increment.
Offset pattern
This will usually be set to one. However if you wish for the binned offset to match the output offset
interval, set the Offset pattern, Offset increment, and Minimum offset to the same values as used in the
modules DMO3D and DMOS.
Offset increment
This is the offset increment for the output of modules DMO3D, KTMIG...
Minimum offset
This is the center of the first offset range to be output by DMO3D, KTMIG,... If you are outputting signed
offsets, this is the minimum positive offset.
Select matrix type

Options: DISTOFF, COFFOFF
Offset groups
Matrix Type: DISTOFF
Output signed offset?

Select Yes to process the positive and negative offsets separately.
402
DMOG
Module Description
Input Channels
Output Channels
Parameters
Module Description
DMOG will apply Theta DMO to traces that have normal moveout applied. Output will be CMP gathers.
Input does not have to be CMP sorted. After application and normal moveout addition, proper DMO
velocity analysis may be run. A CMP location matrix may be specified to allow execution on specific
CMPs or groups of them.
The 2D DMO program is a true amplitude dip moveout process that will correct for azimuthal variations
in velocity. The integral (Kirchhoff-style) DMO algorithm will compute a series of zero offset traces
corresponding to locations between the source and the receiver and sum them into stack bins. For most
integral DMO algorithms, application of a 45 degree phase shift is required to correct phase distortions,
Deregowski (1985) noted that the 45 degree phase shift is appropriate only for large offsets and small
times. In our 3D DMO program, the phase can be corrected for all times and offsets. This algorithm is able
to achieve virtually the same results as from FK algorithms except that our algorithm will treat the
amplitudes for all dips equally. FK algorithms tend to gradually attenuate amplitudes as the dip increases.

1. Minimum offset: This should be the average minimum source- to-receiver distance.
common offset, every other CMP would be missing. Usually the following formula can be used:
Shot interval
offsets should be the absolute minimum and maximums, not the average. WARNING: Dmog with
Offset pattern = 0 may run very slowly. Dmog is table driven, and offset pattern = 0 forces a new
table calculation for each offset.
403
Minimum offset:
200
Offset pattern:
2
References
Deregowski, S.M., 1986, What is DMO?: First Break, v. 4, no. 7, p. 7-24.
1215-1217.
Input Channels
Output Channels
Parameters
404
Gathers to extract
Number of CMPs to hold in memory

CMP-sorted data requires only one CMP location held in memory. Care must be exercised in choosing this
parameter for other "sort" orders, e.g. it needs to be the difference between the minimum SDPN and the
maximum SDPN between input shots for shot-ordered data.
CMP interval (Feet or Meters)

Algorithm to use
RMS velocities
Matrix Type: RMSVEL
Offset pattern
Offset increment
This is also used for the output offset increment between offset planes.
Minimum offset
Maximum offset
Minimum mute time on far offset (ms.)
405

DMOG will taper the DMO operator from the maximum dip (previous parameter). This will tend to
Start taper value

value of 1.0.
Taper length(ms.)
406
DMOS
Module Description
Input Channels
Output Channels
Parameters
Module Description
DMOS is the 2-D DMO stack or common offset application. After NMO removal (true RMS velocities),
DMOS will apply Theta DMO and output stacked or common offset data. If common offset sorted data is
input to DMOS, the output will also be common offset sorted with DMO applied. See the module
DMODIST for further details.
The 2D DMO program is a true amplitude dip moveout process that will correct for variations in velocity
due to dipping events. The integral (Kirchhoff-style) DMO algorithm will compute a series of zero offset
traces corresponding to locations between the source and the receiver and sum them into output bins. For
most integral DMO algorithms, application of a 45 degree phase shift is required to correct phase
distortions, Deregowski (1985) noted that the 45 degree phase shift is appropriate only for large offsets
and small times. In our DMO program, the phase can be corrected for all times and offsets. This algorithm
is able to achieve virtually the same results as from FK algorithms except that our algorithm will treat the

Shot interval
WARNING: DMOS with Offset pattern = 0 may run very slowly. DMOS is table driven, and offset
pattern = 0 forces a new table calculation for each offset.
407
Minimum offset:
200
Offset pattern:
2
References
Deregowski, S.M., 1986, What is DMO?: First Break, v. 4, no. 7, p. 7-24.
1215-1217.
Input Channels
Output Channels
Parameters
408

parameter for other "sort" orders, e.g. it needs to be the difference between the minimum SDPN and the
maximum SDPN between input shots for shot-ordered data.
Number of CMPs in the line

This is used for dip calculations.
Algorithm to use
best with smooth velocity models and modest velocity variation. The depth-variable option has a minimal
run time penalty compared with constant velocity. Currently the program does not vary velocity laterally.
RMS velocities
Matrix Type: RMSVEL
Offset pattern
Offset increment
Minimum offset
Maximum offset
Minimum mute time on far offset (ms.)
This is used to minimize memory usage.
409
Normalize stack by fold?

Required if Normalize stack by fold? = Yes.

Required if Normalize stack by fold? = Yes and Stack normalization technique = fold plus next parm.

DMOS will taper the DMO operator from the maximum dip (previous parameter). This will tend to
decrease the background noise at the expense of increased execution time. Some taper is desirable to
minimize a Gibbs effect.
Start taper value

value of 1.0.
Taper length(ms.)
410
DNG1
Module Description
Input Channels
Output Channels
Parameters
Module Description
DNG1 is a program that will apply Theta DMO to 3-D seismic data and produce bin gathers at
user-specified bin locations. This Kirchhoff DMO algorithm is a true amplitude DMO provided there is an
even distribution of offsets and azimuths.
The 3D DMO program is a true amplitude dip moveout process that will correct for azimuthal variations
in velocity. The integral (Kirchhoff-style) DMO algorithm will compute a series of zero offset traces
corresponding to locations between the source and the receiver and sum them into stack bins. For most
integral DMO algorithms, application of a 45 degree phase shift is required to correct phase distortions,
Deregowski (1985) noted that the 45 degree phase shift is appropriate only for large offsets and small
times. In our 3D DMO program, the phase can be corrected for all times and offsets. This algorithm is able
to achieve virtually the same results as from FK algorithms except that our algorithm will treat the
Velocity
DNG1 requires NMO removal via a representative single averaged velocity-time model prior to
application. A velocity that differs greatly from the RMS velocity can produce a common offset section
that distorts the dip.
Input Data
Data should be binned via the GEOM application prior to DNG1 execution. The input data may be sorted
in any order.
Muting
If DNG1 is being run for the purpose of velocity analysis, the tendency would be to not mute the data.
DNG1 will run faster as the mute gets deeper. If a mute is not desired, then the user should at least input a
mute function to mute the data before the first breaks. Mutes are applied after NMO is applied.

411
Shot interval
Minimum offset:
200
Offset pattern:
2
In full fold, every odd CMP would contain offsets 200, 250, 300, 350, ... The even CMPs would contain
offsets 225, 275, 325, 375, ... The average offset planes would contain 212.5, 262.5, 312.5, ...
References
Deregowski, S.M., 1986, What is DMO?: First Break, v. 4, no. 7, p. 7-24..
1215-1217.
412
Input Channels
Output Channels
1. Output: Required connection to dataset DNG1 data type.
Parameters
Restart?
Algorithm to use
RMS velocities
Matrix Type: RMSVEL
Desired offset interval in a CMP

Bins to extract
Offset pattern
413
Offset increment
Minimum offset
Maximum offset
DNG1 will taper the DMO operator from the maximum dip (previous parameter). This will tend to
Start taper value

value of 1.0.
Taper length(ms.)
414
DNG2
Module Description
Input Channels
Output Channels
Parameters
Module Description
DNG2 will output gathers from the DNG1 data set which has Theta DMO applied to 3-D seismic data.
Input Channels
1. Input : Required connection from dataset DNG1 data type.
Output Channels
Parameters
Correct bin interpolation from 0 ms. to
415
DTYPE
Module Description
Input Channels
Output Channels
Parameters
Module Description
This program allows the user to set or reset the data type and vertical axis of a data stream. At present,
only the plotting routines and the three component programs access the data type.
Input Channels
Output Channels
Parameters
Which data type?
Options: P wave or Amplitude (This is the normal data type.),
Velocity, Instantaneous Amplitude, Instantaneous Phase,
Instantaneous Frequency, SV, SH, Well Log, VSP
Which axis type?

Options: Time (This is the normal axis type.), Depth, Frequency
416
ELASTICP
Module Description
Input Channels
Output Channels
Parameters
Module Description
The ELASTICP module computes the elastic parameters p-wave velocity (Vp), s-wave velocity (Vs), and
Density from elastic impedance curves. The elastic impedance curves are computed from constant angle
gathers (XAVA) that are run through an acoustic impedance inversion (INVERSN).
The module assumes the input elastic impedance curves have positive amplitudes. This means that the
output from the INVERSN module for acoustic impedance of the angle range stacks must not have the
low-velocity trend removed. The best output from INVERSN will be Trend Average.
For best results, the data should be multiple free, migrated, and preferably zero-phased. The spectrum of
the seismic trace should be flat within the zero to nyquist range.
The elastic impedance (EI) is a function of the p-wave velocity, s-wave velocity, density, and incidence
angle. To relate the EI to seismic, the stacked data must be some form of angle stack rather than a constant
range of offsets. The EI function has enabled far-offset angle stack data to be inverted using technology
developed for acoustic impedance inversion. An undesirable feature of the EI function has been that its
dimensionality varies with incidence angle and provides numerical values that change significantly with
incidence angle. These problems have been overcome by normalizing the EI function with constants
Vp-average, Vs-average, and Density-average.
The normalized elastic impedance function is defined as:
EI(angle) = Vpo * Deno * [ ( Vp/Vpo)**A * (Vs/Vso)**B * (Den/Deno)**C) ]
Where:
A
= 1 + tan2(angle)
= -8 * K * sin2(angle)
= 1 - 4 * K * sin2(angle)
= ( Vs * Vs ) / ( Vp * Vp )
Vpo
= The average p-wave velocity (Vp) taken from well logs. (ft/s or m/s)
Vso
= The average s-wave velocity (Vs) taken from well logs. (ft/s or m/s)
Deno = The average density taken from well logs. (gm/cc)
417
The original Elastic Impedance equation from Connolly (1999) was not normalized. If you wish to
reproduce this equation then you can set the Vpo, Vso, and Deno to a value of 1.
The typical processing sequence is:
1) Prepare NMO-corrected CMP gathers for AVO analysis,
2) Run module XAVA to build angle gathers (at least 3 angles per CMP),
3) Run the INVERSN module to compute the elastic impedance for each angle trace. Do not perform
Trend Removal for scaling but performing Trend Averaging will improve the results,
4) Run the ELASTICP module on the inverted gathers.
The user has the option of outputting the Vp, Vs, and or the Density curve. The DIST header word is
modified to reflect which trace.
DIST = 20 - The Vp trace.
DIST = 21 - The Vs trace.
DIST = 22 - The Density trace.
A VSVPDEN matrix can be input that contains the average Vp, Vs, and Density at specific start times.
The default is to use 1 for each average. The value of these constants should be chosen as averages from
the Vp, Vs, and Density well logs.
A VS2VP2 matrix can also be input with the Vs**2/Vp**2 (K) constant versus start time. The default is to
compute this constant using the Vp and Vs entered above in the VSVPDEN matrix.
In areas where there is no well information or for a quick recon look. I assume a Vp/Vs ratio of 2 and a
density of 2. I estimate the average p-wave velocity (Vp) but looking the at RMS velocities from NMO.
Then divide the Vp velocity by 2 to get the s-wave velocity (Vs). These values can be placed into the
VPVSDEN matrix for a first run of the module.
The user has the option to specify the start and stop time in which to perform the EI computation.
References:
Connolly, P., 1999, Elastic impedance: The Leading Edge, 18, 438-452.
Whitcombe, D. N., 2002, Elastic impedance normalization: Geophysics, 67, 60-62.
Whitcombe, D.N., Connolly, P.A., Reagan, R.L., Redshaw, T.C., Extended elastic impedance for fluid and
lithology prediction: Geophysics, 67, 63-67.
418
Input Channels
1. GCI input: Required connection from previous process GCI data type.
Output Channels
Parameters
Elastic parameter output options
The module can output a p-wave (Vp), s-wave (Vs), and or a Density (Den) curve. The user can output
any of the above. If more that one curve is output, the SELECT module will have to be used to separate
them. The Vp curve has a DIST header word of 20, the Vs curve has a DIST header word of 21, and the
Density curve has a DIST header word of 22.
Average Vp, Vs, and Density

The module uses a normalized version the Elastic Impedance function. To remove the dimensionality as a
function of angle, constants Vpo, Vso, and Deno are used. If the values of these constants are chosen to be
averages from the Vp, Vs, and Density well logs, then the EI(angle) will vary around unity. This
modification removes the dimensionality dependence and stabilizes the function.
Enter a average p-wave velocity (Vpo), s-wave velocity (Vso) and Density (Deno) at user specified start
times. The velocities are in f/s or m/s, depending on the units chosen for the area/line. The Density should
be in gm/cc.
For a quick look, the user can assume a Vp/Vs ratio of 2 and a density of 2. The user can look at the RMS
velocities from NMO to build a set of Vp versus time. Then divide the Vp by 2 to get a Vs.
Matrix Type: VPVSDEN
Vs2/Vp2 constant (K)

The elastic impedance function has a constant K defined as Vs**2/Vp**2. The default is to compute this
constant using the Vp and Vs entered in the above average matrix. The user can also specify the K
constant versus start time using this matrix.
Matrix Type: VS2VP2
419
Start time (ms)

Enter the start time in milliseconds. Samples above the start time are ignored.
End time (ms)

Enter the end time in milliseconds. Samples below the end time are ignored.
420
ELETOFLT
Module Description
Input Channels
Output Channels
Parameters
Module Description
ELETOFLT is a standalone program that computes shot and geophone statics needed to change datum
from shot/geophone elevation to CMPdatum (floating datum) or optionally to a user specified flat datum.
Parameters
Datum
Select Float to compute and output statics that move shots/geophones to floating datum (CMPdatum).
Select Fixed to compute statics to move shots/geophones to a user specified flat datum.
Options: Float, Fixed
CMPdatum FLOATING datum elevations

Select CMPdatum matrix generated by running STATIC in a flow.
Fixed datum elevation

If the Fixed option was selected enter the fixed datum elevation.
Replacement velocity
Shot FLOATING datum statics
Enter the name of the output SHOT statics matrix.
Matrix Type: STATSRC
421
Geophone FLOATING datum statics

Enter the name of the output GEOPHONE statics matrix.
Matrix Type: STATGEO
422
ENDIF
Module Description
Input Channels
Output Channels
Parameters
Module Description
ENDIF is used with IF to select user specified traces for a processing sequence. The result is a single flow
where some of the output has been selectively processed and the remainder simply passed.
Input Channels
Output Channels
Parameters
Primary header key
Select the primary header key to describe traces to process.
Primary GCI index

Required if Primary header key equal other.

Select the secondary header key to describe traces to process.
Secondary GCI index

Required if Secondary header key equal other.
423
Tertiary header key

Select the tertiary header key to describe traces to process.
Tertiary GCI index

Required if Tertiary header key equal other.
Groups to pass
Name of the EXTRACT matrix describing the traces to be processed.
Matrix Type: EXTRACT
IF storage file name (full path)

This file name must EXACTLY match the file name you specified in the IF module. Example:
/tmp/DAVE-IF-ENDIF-4. This will use a file created by IF in the /tmp directory. NOTE: The user should
examine the /tmp directory to remove old IF-ENDIF files.
424
ENSBAL
Module Description
Input Channels
Output Channels
Parameters
Module Description
ENSBAL balances trace amplitudes for the input ensemble by two different methods.
The first method uses a window with a sloping top and flat bottom to define trace gates for amplitude
estimation. The sloping window top allows the user to exclude first breaks from alpha-trim magnitude
trace amplitude estimates. If the user wants to control the background amplitude, each trace is multiplied
by a scalar to bring its amplitude to the user specified background value. If the user wishes to preserve the
original background amplitude, the trace measurements are then sorted for an alpha-trim estimate for the
whole ensemble. Each trace is then scaled to the original background amplitude.
The second method is a background amplitude preserving AGC using average amplitude measurements
over a moving time gate.
ENSBAL would typically be used to compensate for vertical amplitude "stripes" on CMP gathers that are
composed of traces from different surveys.
Input Channels
Output Channels
Parameters
Method
Select either trace-by-trace or vertically continuous (AGC).
Options: Trace-by-trace, Vertically continuous
425
Near offset (top of window)

If Method equals Trace-by-trace - To describe the sloping top of window two (2) offset-time points must
be specified. Enter the near offset.
Window start time at near offset (ms)

If Method equals Trace-by-trace - Enter the time at the near offset (above) for sloping window start.
Far offset (top of window)

If Method equals Trace-by-trace - Enter the far offset for sloping window.
Window start time at far offset (ms)

If Method equals Trace-by-trace - Enter the time at the far offset (above) for the sloping window.
Window end time (ms)

If Method equals Trace-by-trace - Enter bottom time of window for amplitude computations.
Vertical Alpha-trim percent

If Method equals Trace-by-trace - Enter the alpha-trim mean percent used to compute each trace
(magnitude) amplitude using samples in the gate.
Horizontal Alpha-trim percent

If Method equals Trace-by-trace - If user wished to retain the original background amplitude enter
alpha-trim mean percent to compute a background amplitude from the individual trace amplitudes (above).
User specified ensemble reference amplitude?

If Method equals Trace-by-trace - Select YES or NO.
Reference amplitude value

If Method equals Trace-by-trace - If YES was selected for User specify ensemble reference amplitude?
enter the desired background value.
Time length of statistics window (ms)

If Method equals Vertically continuous - Enter the amplitude estimate gate length.
426
427
ENSCLN - Ensemble clean

Module Description
Input Channels
Output Channels
Parameters
Module Description
ENSCLN use a flexible, correlation generated beam to track samples of an event. These samples are
statistically combined to form an output sample. The result is a reduction in random noise on ensembles
with or without NMO.
Input Channels
Output Channels
Parameters
Cleanup method
Output samples are computed by an alpha-trim mean, just a median, a weighted mix or a semblance
weighting of the input samples.
Options: Alpha-Trim mean, Median, Weighted mix, Semblance weight
Tracking gate height (ms)

This value is the height of the model trace gate in ms. Typically 150 ms for data with no NMO.
Sometimes larger gates help on data with NMO applied.
Signal estimate width in traces (odd)

This value is the total width of the beam in traces.
428
Signal estimate height in samples (odd)

If Semblance weight is used as the cleanup method this value will be the beam height. Typically 3 to 9
sample should suffice.
Addback percent
If Semblance weight is used this value will control the amount of raw data added back for cosmetics.
Maximum center-to-edge dip (ms)

This value is the maximum observed data dip over half the beam.
Percent trim
When the Alpha-Trim mean is used this is the alpha-trim mean percent applied before output stack
computation.
Weight method
The output samples may also be computed by a flat or linearly tapered stack of input samples.
Options: Flat, Linear
Number of threads
The more threads used (up to the number of CPUs) the faster the execution.
Copyright 2013 GeoCenter LP.
429
ENSDCN1
Module Description
Input Channels
Output Channels
Parameters
Module Description
ENSDCN1 performs ensemble minimum-phase deconvolution by the Wiener-Levinson least squares
technique. ENSDCN1 is same as the ensemble deconvolution in module DECON with a trimmed mean of
0% except that ENSDCN1 does not require any particular sort order.
ENSDCN1 will stack the normalized autocorrelations within each ensemble id in the survey. The number
of ensembles is determined from the geometry database. At the end of the job, ENSDCN1 will compute
all of the operators. Another pass over the data can then be made to apply the operators with module
ENSDCN2.
***WARNING***
Do not put multiple ENSDCN1 modules for different ensemble domains in the same queue. You must
apply the results of say the shot domain ENSDCN1 before you can calculate the autocorrelations for the
geophone domain. If you have shot ordered input data you can however run ensemble deconvolution with
DECON followed by ENSDCN1 for the geophone correction. In a second pass you can apply the
geophone correction.
ENSDCN1 will need disk space to hold all of the autocorrelations and operators for each ensemble for the
entire survey.
algorithm.
If Spiking deconvolution is selected, an option is provided to perform minimum phase, zero phase, and
phase only deconvolution. The Wiener-Levinson filter used to deconvolve the data is minimum phase, so
by default, if minimum phase is chosen, then a normal deconvolution is performed. You can optionally
430
phase portion (imaginary part) is zero or minimum depended on the user selection. Typically, if the input
data is minimum phase, then this filter should be minimum phase. The Inverse band filter is then
convolved with the windowed input trace during the operator design phase of the program.
Input Channels
Output Channels
2. Dataset for ENSDCN2: Required connection to dataset ENSDCN data type.
3. CGM: Optional connection to dataset CGM data type.
Parameters
Ensemble domain to operate on
Options: Source, Geophone, Midpoint, Offset
Minimum offset
Maximum offset
Offset increment
Required if Ensemble domain to operate on = Offset.
Options: Spiking Deconvolution, Predictive Deconvolution
431
Time variant?
Operator length(ms.)
Prewhitening(%)
Prediction gap(ms.)

Start design time(ms.)

End design time(ms.)

Primary header key

Required if Space variant design windows? = Yes.
TLSN

Required if Space variant design windows? = Yes.
TLSN
432
Design times


Matrix Type: DECON
Decon operator phase option

You can chose to perform minimum phase decon, which is the default. This option will apply the
minimum phase and amplitude of the Wiener-Levinson filter. The zero-phase option will convert the
Wiener-Levinson filter to zero phase and then apply amplitude and phase. The phase only option will
convert the Wiener-Levinson filter to zero phase and then apply the phase only portion.
of the program.
433
Filter phase





the Gibbs Effect.
Support restart capability?

Select "Yes" to flush the computations to disk every so often so that a restart can be performed if the job is
aborted.
Restart?
Required if Support restart capability? = Yes. If the job previously aborted, select "Yes" to read the
previous computations from disk. The seismic input routine should start at the last trace processed from
the aborted ENSDCN1 run.
434
Maximum overlap between restarts

Required if Support restart capability? = Yes. This is the number of live traces that will be processed
before the computations are flushed to disk. When a job is restarted, there is a possibility that
autocorrelations could be stacked twice up to this number of live traces. Every time the computations are
flushed to disk, ENSDCN1 will print the headers TRSN, SDPN, DIST, SGEN, and SSPN. Choosing a
small number will result in a bigger execution listing and slower execution time.
435
ENSDCN2
Module Description
Input Channels
Output Channels
Parameters
Module Description
ENSDCN2 will apply deconvolution operators calculated from module ENSDCN1.
Ramp
|<->|
Ramp
|<->|
____________
______________
_______________
|
|\ /|
|\ /|
|
|
Op. #1
| X |
Op. #2
| X |
Op. #3
| ...
|____________|/ \|______________|/ \|_______________|
^
^
^
^
^
^
0
End1
Start2
End2
Start3
End3
When performing deconvolution, overall amplitudes may decrease. When "Restore Amplitude" is
requested, a scalar is derived by computing the ratio of the energy of the filtered input application window
over the filtered deconvolved application window. If this is not requested, scaling is unity.
Input Channels
2. Dataset from ensdcn1: Required connection from dataset ENSDCN data type.
Output Channels
Parameters
Restore amplitude?
436
Low frequency(hz.)
High frequency(hz.)
Time variant?
Primary header key
TLSN, other

TLSN, other
Application times
Required if Time variant? = Yes. If a time horizon (TIM1 or TIM2) was added into the time-variant
design window time in module ENSDCN1, the horizon will also be added to the application times.
437
ENSFFT
Module Description
Input Channels
Output Channels
Parameters
Module Description
ENSFFT performs a standard one dimensional fast Fourier transform or its inverse on an ensemble. The
input must be in real/imaginary Fourier pairs (as output by TRACEFFT). The output may be configured as
complex frequency pairs or amplitude and phase. Phase may be output in radians or degrees. The real and
imaginary components may be grouped by frequency or real/imaginary component.
The transform is computed on real/imaginary pairs at the same trace time in adjacent traces. The offset is
used to order and "bin" the input traces. The offset reference defines the "center" of the ensemble. This
might be thought of as the zero offset location. Parameters should be chosen so that one trace occupies
each offset bin.
Input Channels
Output Channels
Parameters
Fourier Transform Direction
Transform from time to frequency domain (Forward) or frequency to time (Reverse).
Options: Forward, Reverse
Transform Coordinates
The Fourier transform may be represented in amplitude and phase or sin and cos.
438
Options: Amplitude-Phase, SIN-COS
Transform Order
The transform trace is either ordered in complex pairs (Complex, ie. sin,cos) or all real values first in the
first half of the trace then the imaginary values (Burst).
Options: Burst, Complex
Phase Units
If the Transform Coordinates are set to Amplitude-Phase the phase may be in radians or degrees.
Options: Degrees, Radians
Maximum Offset Expected

Header Containing Offset ID
TLSN, other
Header ID Index for Offset

Required if Header Containing Offset ID equal other.
Offset Increment
Header Containing Offset Reference
TLSN, other
Header ID Index for Offset Reference

Required if Header Containing Offset Reference equal other.
Copyright 2004 GeoCenter, Inc.
439
ENSMATH
Module Description
Input Channels
Output Channels
Parameters
Module Description
ENSMATH performs simple mathematical operations on two SeisUP data sets. Data set 1 is from a
previous process. Data set 2 is from a GCI data file. The two data sets must have the same sampling rate.
The number of samples of the two data sets can be different. The original sort orders of the two data sets
can also be different. ENSMATH will load the second dataset using the same sort order of the first dataset.
In addition, ENSMATH allows trace mis-match in the two datasets. In the case of any missing traces, dead
traces will be outputted. It can check additional two headers SGEN and SSPN for some special cases.
The Arc Tangent computation assumes the "Data set to subtract" is the denominator of the tangent and
the "Seismic input" is the numerator or X and Y, respectively, in Cartesian coordinates. Angles computed
by the Arc Tangent option are in radians and assume traditional Cartesian polarity.
Input Channels
2. Data set to subtract: Optional GCI data type.
Output Channels
1. Difference traces: Optional connection to next process GCI data type.
Parameters
Ensemble operation
Options: Add, Subtract, Multiply, Divide, Cross-correlation,
Multiply by ABS, Arc Tangent
440
Additional headers checking?
441
ENSSCALE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Ensemble Scale will apply a time variant scalar to a group of traces. The module performs trace-by-trace
scaling based upon amplitudes of surrounding traces in the ensemble. The result is a subtle smoothing of
the amplitudes across the ensemble. The ensemble scaling should compensate for acquisition related
amplitude variations, fold variations, noise, and imperfect amplitude compensation due to other processes.
The module computes several types of scalars:
Median
Mean
Root Mean Square
Maximum Magnitude
The Median method computes the mean for each trace within a group of traces for each window. Then the
median mean value for the group is selected at the scalar numerator.
Scalar = Median mean of group / Mean of trace
The Mean method computes the mean for each trace within a group of traces for each window. Then the
mean value for the group is computed as the scalar numerator.
Scalar = Mean of group / Mean of trace
The Root Mean Square (RMS) method computes the RMS for a group of traces within the window. Then
the mean RMS is computed for the group and used as the scalar numerator.
Scalar = RMS of group / RMS of trace
The Maximum Magnitude method selects the maximum amplitude for each trace within a group of traces
for each window. Then the maximum amplitude is selected from the group of traces and used as the scalar
numerator.
Scalar = Max. Amp. of group / Max.
Amp. of trace
An alpha trim mean can be applied to the mean of the traces samples within the window. If a alpha trim of
20% is selected, then the module will rejects the top and bottom 10% of the samples when computing the
mean within the window. This in effect rejects the outlier samples so that the mean more closely
resembles the mean of the trace.
442
The number of traces in the group can be selected. The number of traces represents a running window of
traces over which the scalar is computed. The default is to use all the traces in an ensemble. The number
of traces must be odd, the module will add one to the number if you enter an even number of traces. If you
reduce the number of traces in the group, the module will run faster. If you select 1, then the module
applies single trace scaling.
The minimum and maximum scalar multiplier option allows you to set a limit on traces that falls outside
the normal amplitude range. Use this option to prevent boosting weak traces or lower high amplitude
traces. The user selects the multiplier that triggers the limit. Example: The scalar computed for a trace is
six, but the maximum limit is set to five, this trace will not be scaled within this window. The user has the
option to zero the trace values within the window or leave them alone by not apply the scalar.
The number of non-zero samples in a window is compared to the threshold set by the user. If there are too
many zeros in a window, then that trace window is not used in the calculations. This parameter will allow
you to throw out trace windows that contain to many zeros from the calculations.
A window matrix specifies the start and end time of time windows over which to compute the scalar. Up
to 100 windows can be defined. Windows may also overlap. The window centers must increase in time for
each successive window or the program will abort. The user can also set one start and stop time to use for
the entire seismic survey
Windows can be time-adjusted by TIM1 or TIM2 in program HORIZON. Typically, this is used to add a
water bottom time to the window times.
As an aid to computing values, the program will optionally print statistics for each trace. The TRSN is
printed for each trace along with the mean (or selected type) for each window of this trace. Plus the mean (
or selected type) for each window of the group traces that contributed.
Input Channels
Output Channels
Parameters
Scale type
Select the method for computing the scalar.
443
Options: Median, Mean, Root Mean Square, Maximum Magnitude
Alpha trimmed mean of samples (%)

The mean/RMS/Magnitude for the trace can be alpha trimmed for each window. The module computes the
mean/RMS/Magnitude for each traces sample in the window. The user can select to reject the high and
low values by entering an alpha trim percent. If 20% is entered, then the highs and lowest 10% of the trace
samples are rejected before performing the calculation.
Number of traces for scale computation

Select the number of traces to use for computing the mean/RMS/Magnitude. The number of traces must be
odd; the module will add one trace to an even number of selected traces. The number of traces provides a
running window in the trace number domain for computing a scalar to balance the amplitudes.
Minimum scalar limit option?

Use this option to limit the scalar multiplier. You may not want to boost the amplitude of very weak
traces. Use this option to limit the size of the multiplier to a specific value.
Minimum scalar multiplier limit

Enter the scalar multiplier to use for the limit. Example: The user selects the Median option. Within a trace
window the mean is two, but the mean for the trace group is 10. So the scalar is 10/2 is equal to five. If the
user set the limit at five, then this trace is weaker than the limit.
Trace computation option

Select the method to use when a trace fails the limit option. The user can either zero the trace in the
window or leave the trace alone and do not apply the scalar in the window.
Options: Zero trace in window, Do not apply scalar
Maximum scalar limit option?

Use this option to limit the scalar multiplier. You may not want to weaken the amplitudes of very strong
traces. Use this option to limit the size of the multiplier to a specific value.
Maximum scalar multiplier limit

Enter the scalar multiplier to use for the limit. Example: The user selects the Median option. Within a trace
window the mean is 20, but the mean for the trace group is 2. So the scalar is 20/2 is equal to 10. If the
user set the limit at 5, then this trace is stronger than the limit.
444
Trace computation option

Select the method to use when a trace fails the limit option. The user can either zero the trace in the
window or leave the trace alone and do not apply the scalar in the window.
Options: Zero trace in window, Do not apply scalar

Specify the percent of the window that must have non-zero trace values before it is used in the
calculations. If a trace window contains too many zeros, it can be thrown out of the calculations.
Time variant windows?

Select to enter the start/stop times in a matrix or enter just one start/stop time for the survey. If the user
wants to enter multiple windows in time, then select "YES". Another parameter appears asking for the
start/stop windows matrix.
Start and stop time for windows

Enter the matrix editor to enter multiple start/stop times. Only one set of start/stop times will be used.
Matrix Type: ENSWIN
Start time (ms.)

Enter the start time to perform scaling in milliseconds. This parameter will appear is the user selected
NO to time variant windows above.
End time (ms.)

Enter the stop time to perform scaling in milliseconds. This parameter will appear is the user selected
NO to time variant windows above.

Select to add additional time to the start time of each window. The header words TIM1 or TIM2 defined in
module HORIZON can be used. Typically, this will be used to add a water bottom time to the windows for
each trace. The TIM1 and TIM2 header words are taken from the trace header and added to the window
times.
445

Select to add additional time to the stop time of each window. The header words TIM1 or TIM2 defined in
module HORIZON can be used. Typically, this will be used to add a water bottom time to the windows for
each trace. The TIM1 and TIM2 header words are taken from the trace header and added to the window
times.
Print statistics?
The module will print the Mean/RMS/Magnitude for each trace and the trace group.
446
EQDIST
Module Description
Input Channels
Output Channels
Parameters
Module Description
Given a set of (x,y) points in a 2D crooked line, EQDIST samples (interpolate) the points so that the first
and possibly also the last points are preserved and the points in between are uniformly distributed,
following the crooked line trajectory.
Input Channels
1. Input: Required connection from dataset ASCII data type.
Output Channels
1. CGM output dataset: Optional connection to dataset CGM data type.
Parameters
Plotting options
The user has two options for displaying results. One is GNU plot where he/she will be provided with an
X-term window to play with GNU plot parameters and the other is CGM plot where he needs to pipe the
output into a file and use a CGM display program after running EQDIST
NOTE - GNUPLOT is a free program that is available for most platforms.
Options: GNU Plot, CGM Plot
Select text file format

At the moment only two formats are supported. The internal SEI ASCII format and Internal GeoCenter
format.
Options: GeoCenter format, SEI format
447
Distance between stations.

The desired distance between stations is a choice of the user, however if both the first and last points are
constrained and the distance is not appropriate the program will compute the error and if the relative error
is larger than 5% it will abort and suggest an appropriate distance.
Acknowledge both starting and ending point?

The default is to fix the end points but the user has the option to fix only the first point.
Extend survey points ?

If the user wants to extend more points before the start of the input data and after the end input data, he
can choose so by providing the number of points on each end. The default for this option is not to extend
points.
Points to extend survey before the first station.

Number of output points before the start of the input data.
Points to extend survey after the last station.

Number of output points after the end of the input data.
Output to STATION file?

The user can choose to output the data directly into an STATION matrix. The default is not to output this
file into an STATION matrix.
Output STATION filename.

Name of the STATION matrix to output the interpolated crooked-line.
Annotate XY,STATIONS
The user has the option to annotate either the station numbers or the X,Y coordinates.
Options: Plot XY, Plot STATIONS
448
Step value for output annotation.

When many points are considered, a big step valued is suggested, to avoid clustering of text around the
points.
Step value for input annotation.

When many points are considered, a big step valued is suggested, to avoid clustering of text around the
points.
Print selection
This option provides direct feedback to the user in the execution status log. The default is not to print data
into the execution status log.
Options: Print Input, Print Output, None
CGM plot size

This option is self-explanatory. It asks for the size of the CGM plot for the output data.
Options: 33 inches, 32 inches, 31 inches, 30 inches, Other
Enter CGM plot size in inches.

Required if CGM plot size is Other. Another self-explanatory parameter.
Recompute STATIONS?
Enter shotpoint intervals.
449
EQDMO
Module Description
Input Channels
Output Channels
Parameters
Module Description
EQDMO performs Kirchhoff-style 2-D/3-D dip moveout correction on common offset data. It has the
following features:
DMO equalization to reduce irregular sampling effects on prestack DMO,
Spatial dealiasing of 3-D DMO operator,
Anti-aliased 2-D DMO operator,
Bin borrowing to minimize spatial aliasing,
Multithread parallel processing, and
Swathsize to reduce memory requirements.
Input data
The input data must be NMO corrected and the primary header key must be DMODIST (See module
COFF about how to create DMODIST). The following trace headers must be filled properly before
EQDMO.
Word Name
8
TRID
12
22
23
24
25
66
67
80
Description
Trace identification code: 1 = seismic data
2 = dead 3 = dummy 4 = time break 5 = uphole
6 = sweep 7 = timing 8 = water break
9 = auxiliary 10 = label (ASCII)
DIST
Distance from source point to receiver group
SX
Source coordinate - X
SY
Source coordinate - Y
GX
Group coordinate - X
GY
Group coordinate - Y
MBIN
Midpoint bin #. This is the sequential midpoint
number within a midpoint line. This is the same
as SDPN for 2-D lines.
MLIN
Midpoint line # (Used for 3-D only).
DMODIST Distance from source point to receiver group
assigned by module COFF.
If DMO equalization will not be applied, it is recommended that pre-migration normalization be

performed before EQDMO (See module COFF about how to do pre-migration normalization).
DMO equalization
450
DMO equalization in EQDMO is based on a plane-wave constraint that DMO should pass flat events
unaltered. An equalization filter is designed to correct any distortion of flat events due to irregular
sampling (Black and Schleicher, 1989). There are three options in EQDMO for DMO equalization:
Amplitude, Phase, and Amplitude and Phase. It is recommended the user apply Amplitude equalization
only if the structure of the data is complicated. If DMO equalization is chosen, pre-migration
normalization should not be applied EQDMO.
DMO dealiasing
DMO dealiasing option in EQDMO is for 3-D data only. Since 3-D DMO response from source to
receiver may not pass bin centers so that the discretization of the continuous DMO operator to a 3-D space
causes spatial aliasing of 3-D DMO operator (Beasley and Mobley, 1997). Bilinear interpolation is used in
EQDMO for mapping the continuous DMO operator to the 3-D space. It is always recommended to apply
spatially dealiased 3-D DMO operator although it may increase the run time of EQDMO.
Bin borrowing
To minimize irregular sampling effects on common-offset DMO, it is recommended to borrow traces to
fill in the gaps of common-offset data before EQDMO (See module COFF about how to borrow seismic
traces). The borrowed traces should be removed after DMO by specifying parameter Delete borrowed
traces after DMO.
References
Beasley, C. J., and Mobley, E., 1997, Spatial Dealiasing of 3-D DMO: 67th Ann. Internat. Mtg., Soc.
Expl. Geophys., Expanded Abstracts, 1119-1122.
Black, J. L., and Schleicher, K., 1989, Effect of irregular sampling on prestack DMO: 59th Ann. Internat.
Mtg., Soc. Expl. Geophys., Expanded Abstracts, 1144-1147.
Input Channels
Output Channels
Parameters
451
Apply DMO equalization?

Equalization option
Options: Amplitude, Phase, Amplitude and Phase
Apply spatially dealiased 3-D DMO operator?

Source to receiver distance option
Options: DIST, DMODIST
Delete borrowed traces after DMO?

Min. midpoint bin number of output
Max. midpoint bin number of output
Min. midpoint line number of output
Max. midpoint line number of output
Max. number of lines in one swath
This parameter is used to reduce the memory requirements. For a 3-D survey, instead of placing the whole
output space in the memory only swathsize number of lines are placed in memory. Here the assumption is
that, due to feathering (marine surveys) or due to the variations in the azimuth, the traces in any input line
may produce output traces that lie in any of the swathsize number of lines surrounding the input line. In
other words for any input line, a band of swathsize number of lines in the output space is required. The
input line lies at the center of this band, and can produce an output trace located anywhere in this band.
For a 2-D line, the swathsize is 1.
Bin interval (distance units)

Line interval (distance units)
DMO aperture (percentage of source-to-receiver distance)
Max. frequency (Hz)
452
Cutoff time (ms) for logarithmic stretch

Taper at the cutoff time (ms)
Restore mute
Max. available memory (MB)
The default is the maximum allowed on 32 bit systems.
Number of threads to use

NOTE: The next four parameters are used when using a variable cutoff time for logarithmic stretch. If the
Cutoff times matrix is input Cutoff time (ms) for logarithmic stretch: is used as the minimum cutoff. Using
a variable cutoff time may increase memory usage but significantly reduce run times.
NOTE: There are subtle amplitude issues with this code primarily due to the variable length of the
FFT operators. It is generally most noticeable below 5 Hz.
Noisy traces and noise bursts should, in general, be removed from the data prior to EQDMO. If they are
not removed, they account for the majority of the amplitude differences between the constant and variable
cutoff cases.
Primary cutoff time header key

TLSN
Secondary cutoff time header key

TLSN
Cutoff times
NOTE: The cutoff time is set when a new DMODIST or DIST ensemble is found. It is not variable within
an offset range. Accordingly, use only a single function for the entire job. The program will not abort if
more than one function is input, but the results may not be as expected.
The cutoff times should be a bit ahead of the first breaks. i.e. This is NOT a stack mute. Data ahead of the
cutoff times is lost. If the cutoff times are after the first arrivals the output amplitudes are disturbed.
453
Maximum offset
NOTE: The maximum time found in either the Cutoff times matrix or the time at the maximum offset is
used to assign work space. If the Cutoff times matrix does not cover the entire offset range and Maximum
offset is less than the maximum offset present, an array overflow can occur.
Modified on Dec. 16, 1998 by Riju
454
EXPHORZ
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use module EXPHORZ to export an interpreted horizon to an external file.
Parameters
Horizon to export
Select the horizon name you wish to export.
Output filename
Enter the desired output file name for the exported horizon. If no path information is input the default is to
place the file in your home directory.
Output Format
Select the desired information and column ordering for the exported horizon.
Options: X-Y-Z, MLIN-MBIN-Z, MLIN-MBIN-X-Y-Z
Minimum MBIN to output

Enter the minimum MBIN number to output. Default is to use the minimum defined in the horizon.
Maximum MBIN to output

Enter the maximum MBIN number to output. Default is to use the maximum defined in the horizon.
MBIN increment to output

Enter the MBIN number inrement to output. Default is to use the increment defined in the horizon.
455
Minimum MLIN to output

Enter the minimum MLIN number to output. Default is to use the minimum defined in the horizon.
Maximum MLIN to output

Enter the maximum MLIN number to output. Default is to use the maximum defined in the horizon.
MLIN increment to output

Enter the MLIN number inrement to output. Default is to use the increment defined in the horizon.
456
EXTRACT
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module will select a user-specified dataset and save it to tape or disk in GCI format. EXTRACT
writes the data directly to the output medium, so the WRITE module does not need to be used.
Input Channels
Output Channels
1. Dataset: Optional GCI data type.
Parameters
Use absolute value of the trace header values?
Select "Yes" to use the absolute value of the extracted header values to determine if this trace should be
extracted.
Primary header key

TLSN, other
Primary GCI index

Required if Primary header key = other.
457

TLSN, other
Secondary GCI index

Required if Secondary header key = other.
Tertiary header key

TLSN, other
Tertiary GCI index

Required if Tertiary header key = other.
Groups to extract
458
FAKE3D2
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module generates pseudo 3-D data that can be used for survey modeling.
The program assumes regular geometry. Shot to hydrophone offsets are computed and the input trace that
is nearest to that offset is output.
Input Channels
Output Channels
1. Dataset: Optional SEGY data type.
Parameters
# of sources
Each input profile produces one output profile.
# of streamers
# of channels per streamer
Distance between sources crossline
Required if # of sources > 1.
459
Distance between streamers crossline

Required if # of streamers > 1.
Distance between stern and sources

Distance between stern and near group
Distance between source points inline
If stacks are to be generated with the output data, this parameter needs to match the input data. Otherwise
the input data will need to be decimated to match this parameter.
Distance between receivers on streamer inline

Offset difference tolerance
File on tape to write to
Optional file number within a tape data set to write to. File numbers start from one.
EBCDIC reel header

Matrix Type: SEGYEBC
Starting SGEN number

This is the SGEN of the first hydrophone location on the first shot.
Increment in SGEN numbers between streamers

This should be set so there are no gaps in SGEN numbers in the output data.
460
FBPBO2D
Module Description
Input Channels
Output Channels
Parameters
Module Description
START
FBPBO2D (First Break Pick by Offset for 2D) is a program designed to help the user pick first breaks on
2D data for refraction statics. Connect FBPBO2D to a GCI shot record dataset conditioned for first break
picking, but, do NOT apply LMO. Upon execution a control window is shown. Please select the "Offset
SECTION" option to start. The control window will have more functionality in the future. The new
window is called the OFFSET section. The first menu option is the File option. If you have already made
some picks and they are in the matrix selected in the menu, the first option in File will load the picks into
FBPBO2D. At the top right of the menu are two arrow buttons. To get started viewing the traces by offset
click on the right arrow a few times until a offset gather appears. At the top of the section is the offset
center value, and its index. (A list of offset centers and indexes is in the Execution Status). The traces on
the display are within 200 units of this OFFSET value. At this point we suggest you use the arrow keys to
scan through the offsets to decide where the first breaks are. The OFFSET section size, trace amplitudes
and clip can be adjusted with the "Display" menu option. Also some trace info is offered in the label below
the OFFSET section.
Simple PICKING
The main control for the OFFSET section is the menu option "MODE". Clicking on "MODE" shows eight
options. All of the above discussion of just viewing picks can be made in the first option "View Picks"
where any mouse clicks will not make or change any picks. Simple picking on the offset section is made
by selecting the "Select each pick" option. The help string at the bottom of the display explains some of
the mouse button functionality. MB1 puts a red X (makes a pick) at the peak or trough (or at) the pointer
position. MB2 near an existing pick deletes it. MB3 will place a pick at the pointer position. Shift plus
MB1 allows multiple picks and Shift plus MB2 allows multiple deletes. Finally, depressing the "Control"
key and MB1 at the same time with the pointer over an existing pick will create a new display with the
shot having that picks trace. Upon creation the shot display is in "View picks" MODE. Select "Select
each pick" MODE to make or adjust picks on the shot. In this mode and with LMO applied ("Display"
menu option) the user can use MB1 or MB3 for pick projection. Shift plus MB1 allows multiple picks and
Shift + MB2 allows multiple deletes. Control plus MB1 makes one pick at the desired feature, Control
plus MB3 makes one pick at the pointer location. Picking on the shot display is very useful for pre-picking
other offsets for QC. Leave the shot display for a moment and return to the OFFSET section and apply
"Control + MB1" to a different picked trace. A new shot will now be shown in the shot display with LMO
already applied along with any other shot display changes. While the pointer is in the shot display use the
"n" key to advance to the next shot (OIDN) and the "b" key to go backwards. Picking as many of the
offsets on a shot will provide guide picks for other offsets in the OFFSET window. These displays and
461
picking features allow the user to view and decide WHERE the picks should be made. The next section
will outline a much faster picking procedure.
Picking with a search guide
Suppose the user has made a series of scattered picks all along an offset section. The missing picks may be
filled by picking a search guide and using it to predict pick locations. On the OFFSET section pick "Select
SEARCH guide" under the MODE menu option. Help is available in the bottom string of the OFFSET
display. Start at the left most trace and pick a guide function through existing first break picks. The guide
points will show up as green squares connected by a purple line. A minimum of three points must be made
to see the line. (The program uses cubic splines so 3 points for a spline is a minimum). When finished
picking go to MODE and select "SEARCH to get all picks". All the missing picks should be filled in. The
program is now in "Select each pick" mode for pick updating. When the user is satisfied with all the picks
for the current offset, click the red "right" arrow to proceed to the next unpicked offset section. Go to the
MODE menu option and select "AutoFIND Search Guide". The search guide from last offset is
"projected" (by correlation) to this new offset. Adjust the search guide for these first breaks then use
"SEARCH to get all picks". In this manner the user can "bootstrap" picks from one offset to another. The
MODE menu has options to "Clear ALL picks for this OFFSET", i.e., start over for this offset, "Clear
SEARCH GUIDE for this OFFSET", i.e., start the search guide all over, and, "Snap pick times" to align
all traces with first break picks. The second application of "Snap pick times" puts the display back to
pre-snap condition.
Search menu options
Click on the Search menu option in the OFFSET display and select "Adjust Search parameters". A type-in
menu appears to change values used in pick searching. The first item, "Maximum peak or trough search
(samples)", affects the way picks are projected in the shot display and in the "SEARCH to get all picks"
option on the OFFSET display. The second item, "Snap pick times to (ms)" sets the time location for
snapped picks. The third and fourth items control the correlation procedure for moving a search guide
from a picked offset to a non-picked offset.
OFFSET selection without arrow buttons
If the user wishes to display an offset without using the arrow buttons clicking on the OFFSET menu
option allows the user to enter the desired offset value. The offset section nearest this value will be
displayed
Output picks
When the user is finished picking the picks are saved by selecting the "File" menu option on the OFFSET
section followed by "Output completed FBPs". The program is terminated by selecting the "File" menu
option on the CONTROL window followed by "Exit"
462
Input Channels
1. Input: Required connection from dataset GCI data type.
Output Channels
1. Output: Required connection to dataset GCI data type.
Parameters
Minimum offset needed (ft/m)
This is the minimum offset value of traces to be picked. This value may be negative.
Maximum offset needed (ft/m)

This is the maximum offset value of traces to be picked. This value may be negative. The program gets the
geophone group interval from the line DB level and computes a number of offset centers by (offmax offmin) / group interval + 1. A list of these offset centers and their indexes is in the flow Execution Status.
Maximum time needed (ms)

This is the time in ms of the deepest pick on a raw shot record. It is typically 1000 to 1500.
Pick feature
Peak or Trough are the most commonly used options.
Options: Peak, Trough, None
First break picks matrix

This matrix will contain the first break picks made in the program. If this matrix already contains picks,
they may be input by using the File menu of the OFFSET section. When finished picking on the OFFSET
or SHOT displays use the File menu on the OFFSET section to output the latest picks to this matrix.
Matrix Type: AFS1B
463
FBPICKMC
Module Description
Input Channels
Output Channels
Parameters
Module Description
FBPICKMC is a module for fast marine or land first break picking. The picking algorithms are
multi-channel scans for the first breaks in the vertical direction only. An optional linear-with-offset mute
usually helps stabilize the picking by zeroing the noise above the first breaks. An optional pick continuity
checker may remove mispicks in the marine environment. Optional output allows the picks to be viewed
in DISPLAY (after FBPICKMC in the flow) over the transformed traces used in computing pick locations.
This view can guide parameter updates for better results. Picks will be placed in header word 77.
The quality of the picks is improved with high S/N ratio especially above the first breaks. For best results,
remove the pre-first break noise and the high energy low frequency noise trains before attempting first
break picking. If high frequency noise is present, a low pass filter may prior to FBPICKMC may yield
better good-pick statistics.
The data sent into FBPICKMC can be in any ensemble order, however, picking in SHOT order is fastest.
Input Channels
Output Channels
Parameters
Output
Select Original traces to pass the original input out of FBPICKMC. Select Transformed traces to view the
data used to derive the picks.
Options: Original traces, Transformed traces
464
Pick algorithm
Four pick algorithm are offered for varying dataset conditions. The most versatile option being Average
power from bottom is the default. The next best for land or marine is Adaptive prediction. 2 Windows and
Global ratio are alternatives for marine data.
Options: 2 Windows, Global ratio, Average power from bottom,
Adaptive prediction
Threshold percent
If Adaptive prediction is selected above, Threshold percent of the average magnitude of the trace power
will be the prediction error where the first break pick is placed. If the pick is above the desired location,
increase Threshold percent. If the pick is below the desired location, decrease the Threshold percent.
Filter length (samples)

If Adaptive prediction is selected above, the value is the length of the prediction filter.
Top gate length (ms)

If 2 Windows is selected above this value will be the length of the top gate directly above a bottom gate.
Depending upon the Transform option below, the ratio of magnitude/power/accumulated power in the
bottom gate divided by the value in the top gate will determine the pick location. If the pick is above the
desired location, either lengthen the top gate or shorten the bottom gate, If the pick is below the desired
location do the reverse.
Bottom gate length (ms)

If 2 Windows is selected above this value will be the length of the bottom gate directly above a bottom
gate. Depending upon the Transform option below, the ratio of magnitude/power/accumulated power in
the bottom gate divided by the value in the top gate will determine the pick location.
Transform
If 2 Windows is selected above, traces are converted into magnitude, or power or accumulated power
before applying the 2 window analysis to locate the pick.
Options: Magnitude, Power, Accumulated power
Test criteria
If 2 Windows is selected above, the pick may be based upon the maximum of the transform or the first
location of the threshold value of the transform.
465
Options: Maximum ratio, Ratio threshold
Threshold percent
If 2 Windows and Ratio threshold are selected, this value is the percent of average
magnitude/power/accumulated power that will locate the pick.
Prediction window width

This is the number of traces used to predict the pick for the center trace. Land datasets may require only 1
trace. Marine datasets with highly variable first break pick definition may require 3 or more.
Minimum pick time (ms)

This is the minimum time for any first break pick in the survey. This is especially useful to constrain pick
analysis in deep marine environments.
Maximum pick time (ms)

This is the maximum time for any pick in the survey. It is useful for pick constraint in both land and
marine data.
Apply correlation check?

Select YES for marine shots where pick time are smoothly changing from trace to trace. Select NO for
most land datasets.
Correlation gate length (ms)

If YES was selected for Apply correlation check, enter a correlation gate length. Each pilot pick will be in
the center of the gate.
Maximum pick variation (ms)

If YES was selected for Apply correlation check, enter the maximum expected trace-to-trace pick time
change.
Pick feature
Select Peak if the first visual first break feature is a peak, otherwise Trough. Select none to set the number
of search samples described below. A raw pick is adjusted within a search range to find the largest Pick
feature. The search range is specified by Samples up and down in search described below.
Options: Peak, Trough, None
466
Samples up and down in search

Select the peak/trough search gate in samples above and below the raw pick.
Apply velocity mute?

Muting the noise above the first breaks may help pick both land and marine datasets. This mute is linear
with distance at the selected velocity below.
Water velocity
If YES was selected for Apply velocity mute above, enter the velocity of the linear mute. This will
typically be water velocity for marine data. Be careful to select a velocity high enough for land data as to
not mute the first breaks.
Load picks in First Break matrix?

Select yes if the picks are from a land dataset to be used in refraction statics. Select no if the picks are to
be used in marine multiple rejection.
Output first break picks matrix

If YES was selected for "Load picks to First Break matrix?", this is the name of the first break pick file.
This matrix expects SLIN as primary key, SBIN as secondary key, and FCSN as pick order.
Matrix Type: AFS1B
Load picks in HORIZON matrix?

Select yes if the picks are water bottom time picks from a marine dataset to be used in multiple rejection.
Output HORIZON matrix

If YES was selected for "Load picks to HORIZON matrix?", this is the name of the HORIZON file. This
matrix expects SBIN (or SSPN) as primary key, FCSN as secondary key.
Matrix Type: HORIZON
467
FCVFB
Module Description
Input Channels
Output Channels
Parameters
Module Description
FCVFB generates a first-break data geometry file for input to GLI (refraction statics program from
Hampson-Russell) just like module CVFB, but, FCVFB uses trace headers to extract the geometry rather
than the SeisUP DB file. Generating the GLI input with FCVFB can be many times faster than CVFB.
Input Channels
Output Channels
Parameters
GLI input file (full path and name)
This is the full path and name of the output GLI file.
Total number of shots

This value is the total number of shots in the dataset. A slightly larger value is OK, but a smaller value will
cause an abort.
Maximum number of channels per shot

This value is the maximum number of channels per shot with first break picks. A value that is too small
will cause an abort.
468
First break picks matrix name

Select the first break pick matrix name from the matrix editor.
Matrix Type: AFS1B
Minimum first break time (ms)

This is the minimum expected first break time value. A value of zero (0) is typical.
Maximum first break time (ms)

This is the maximum expected first break time of any channel in the dataset. Traces with first break times
greater than this value will not be loaded. This action is for editing bad first break picks.
Maximum distance
This is the maximum distance desired for any trace with a first break pick. Picks from traces beyond this
distance will nor be loaded.
469
FDAF
Module Description
Input Channels
Output Channels
Parameters
Module Description
FDAF removes low frequency noise, performs time variant/invariant spectral whitening, acts as a
frequency band filter.
Input Channels
Output Channels
Parameters
Mode ?
FDAF operates in 4 modes, Low frequency attenuation, time variant spectral whitening, time invariant
spectral whitening, and frequency band attenuation.
Options: Attenuate low frequency noise, Time variant spectral
enhancement, Time invariant spectral enhancement, Frequency band
attenuation
Spectral control factor

This value controls the attenuation of low frequency noise above the line drawn from the corner frequency
amplitude back to 0 at 0 frequency.
470
Velocity of noise
Many ensembles have noise in a linear pattern if the traces are sorted by offset. This linear pattern may
have a velocity associated with the start of the noise pattern. On shots it may be the ground roll
propagation velocity.
Test velocity value?

To visually see where the filter will start select YES to this question. In a display after FDAF only the data
above this filter start time will be present. This allows the user to adjust the noise velocity.
Enhancement frequency reference

Time variant/invariant frequency enhancement needs a reference frequency to anchor spectral shaping.
The user may specify the reference frequency somewhere between the low and high corner frequencies,
or, and probably best, have the program use the maximum frequency between the corners.
Options: Use specific frequency, Use maximum frequency
Reference frequency
For spectral enhancement if "Use specified frequency" was selected, enter a frequency value between the
low and high corner frequencies.
Top start frequency

For time variant spectral enhancement enter the desired start frequency for the top of the trace. Amplitudes
at all frequencies below this value will be set to 0.
Top low corner frequency

For low frequency attenuation, this is a frequency above the low frequency noise that needs attenuation.
For spectral enhancement, this value is the corner frequency of the desired spectrum after spectral
enhancement.This value applies to the TOP of the input traces (0 time).
Top high corner frequency

For time variant spectral enhancement this is the corner frequency of the desired spectrum after
enhancement at the top of the traces.
Top end frequency

For time variant spectral whitening this value will be the high cut frequency for the top of traces. Any
amplitudes for frequencies above this value will be set to 0.
471
Bottom start frequency

For time variant spectral enhancement enter the desired start frequency for the bottom of the trace.
Amplitudes at all frequencies below this value will be set to 0. The start frequencies are linear with time.
Bottom low corner frequency

For low frequency attenuation, this is a frequency above the low frequency noise that needs attenuation.
For spectral enhancement, this value is the corner frequency of the desired spectrum after spectral
enhancement.This value applies to the BOTTOM of the input traces (maximum time). Low frequency
attenuation or spectral enhancement parameters linearly change from top to bottom of the traces.
Bottom high corner frequency

For time variant spectral enhancement this is the corner frequency of the desired spectrum after
enhancement at the bottom of the traces. The desired high corner frequencies will be linear with time.
Bottom end frequency

For time variant spectral whitening this value will be the high cut frequency for the bottom of traces. Any
amplitudes for frequencies above this value will be set to 0. The end frequencies are linear with time.
Start frequency
For time invariant spectral enhancement this is the start frequency. All amplitudes for frequencies below
this value are set to 0.
Low corner frequency

For time invariant spectral enhancement this is the desired low corner frequency.
High corner frequency

For time invariant spectral enhancement this is the desired high corner frequency.
End frequency
For time invariant spectral enhancement this is the desire end frequency. Amplitudes for frequencies
above this value will be set to 0.
Low zone frequency

For frequency band attenuation this is the start frequency of attenuation.
472
High zone frequency

For frequency band attenuation this is the end frequency of attenuation.
Zone attenuation factor

For frequency band attenuation all amplitude spectra values between start and end will be multiplied by
this value. If this value is greater than 0., the amplitudes in the band will be boosted rather than attenuated.
Spectral smoother length percent

For spectral enhancement the input data spectra is smoothed from 0 to Nyquist frequency. This smoothed
spectra is then used to adjust the original spectra to meet the desired values. This value is the length of the
smoother used on the original spectra.
Frequency boost factor

This is the power applied to the frequency boost ratio, i.e, (desired value / smoothed actual value) **
frequency boost factor.
Gate length (ms)

The spectral estimate for a data sample needs a number of samples surrounding it. This collection of
samples is called a gate.
Taper length percent

Time gates are usually tapered to get better spectral estimates. Ten percent taper is reasonable for most
windows.

Fourier transforms are padded to prevent spectral wraparound. Thirty percent padding (30%) is
reasonable.
Number of threads
FDAF is coded to run in a multi-CPU environment. Using from 4-8 CPUs for large ensembles reduces
process time.
473
FDMIG2D
Module Description
Input Channels
Output Channels
Parameters
Module Description
FDMIG2D performs poststack time migration/modeling using explicit wavefield extrapolators. This
migration/modeling has good handling of vertical and lateral velocity variations and relatively steep dips.
The input data must be poststack and corrected to a flat datum. Either a Remez or Gaussian taper method
is employed to produce filters to perform the wavefield extrapolation. An extrapolation time factor, time
varying hi-cut frequencies, and reduction limit were added to improve the speed of the method. The
smaller the extrapolation time factor, the greater the speed. The reduction limit controls the amount of
reduction in the number of Remez operators used. The greater the limit, the greater the speed. Also the
smaller the band-width, the greater the speed.
References
Soubaras, R., 1996, Explicit 3-D migration using equiripple polynomial expansion and Laplacian
synthesis: Geophysics, 61, 1386-1393.
Input Channels
Output Channels
Parameters
Min. midpoint bin number
Max. midpoint bin number
474
Min. midpoint line number

Max. midpoint line number
CMP or bin interval
Line interval
RMS velocities
Matrix Type: RMSVEL
Migration/Modeling option
Options: Migration, Modeling
Extrapolator design
Options: Remez exchange, Gaussian taper
Number of velocities for extrapolation tables

Minimum interval velocity
Maximum interval velocity
Velocity application percentage
Maximum output time (ms)
Number of points for Remez operator
Maximum dip (degrees)
Extrapolation time factor
This special divisor causes a pseudo depth step to be used. The smaller this number, the larger the depth
step and the quicker the migration can be accomplished.
475
Reduction limit
The reduction limit controls how large the pseudo depth step can be compared to the normal depth step. If
the limit were 40, then for lower frequency ranges of data, a pseudo depth step might be as large as 40
normal depth steps. Of course, the larger this limit, the quicker the program can finish.
Number of zero padded traces on section sides

Taper at trace start (ms)
Taper at trace end (ms)
Time padding ratio (%)
Low cut derivation frequency (Hz)
Low pass derivation frequency (Hz)
High pass derivation frequency (Hz)
High cut derivation frequency (Hz)
Time variant application frequency parameters?
Time variant frequencies (Hz)
Matrix Type: FILEFREQ
Restore mute?
476
FDMIG3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
Explicit Finite Difference Time Migration-3D performs poststack time migration on 3D seismic data
sets using explicit finite difference wavefield extrapolators. This migration has good handling of vertical
and lateral velocity variations and relatively steep dips. The input data must be poststack and corrected to
a flat datum. This program also requires that the in-line and x-line CMP distance is equal (i.e. square CMP
bins ).
Finite-difference migration is a two step process: wavefield extrapolation and imaging. The wavefield
extrapolation phase consists of downward continuing the data using the scalar wave equation into a
configuration corresponding to a repositioning of the plane. The imaging phase consists of outputting a
portion of the migrated data coinciding to the zero offset travel time of the repositioned dataset. The data
is then recursively migrated by using the output of one wavefield extrapolated as input for the next
wavefield.
Three dimensional migration is achieved by using 2D Remez extrapolation filters and a McClellan
Transform to extrapolate the wavefield in three dimensions. The 2D extrapolation filters are built using the
Remez Exchange algorithm. McClellan transformations provide an efficient method for implementing in
three dimensions, two-dimensional digital filters that have a particular form of symmetry, circular in this
case, such as the Remez filters.
The Remez filters that are designed depend on the maximum dip, the number of points in the filters, and
the number of velocities. A larger dip requires a longer filter, on default, the number of points in the filter
are computed from the maximum dip that the user specifies. A filter is built for the number of velocities
specified. A large number of velocities will linearly increase the memory required to store the filters.
Velocities encountered during the migration are interpolated to the nearest velocity that was computed for
the filters.
Selecting a maximum frequency less than the Nyquist frequency will speed up the migration. If the data
has frequencies above the selected frequency then it should be bandpass filtered prior to the migration to
avoid artifacts affiliated with abruptly truncating the frequency band. I recommend that the user look at the
frequency spectra of the stacked data before migration to determine the low and point points for the
frequency range. Users who routinely use the Nyquist frequency will find slow running migrations.
The program uses a proprietary variable depth step technique to enhance program performance.
477
Trace padding should be added to reduce wrap-around effects in the frequency domain. Values in the
range of 30 to 50 percent are adequate for normal dataset. Padding will linearly increase runtimes for the
migration.
The output sample rate of the data can be selected as well as the total time to migrate. These values
determine the size of the migrated output traces when the program is done. They also are used to compute
the number of time steps that the migration performs. Small time steps will provide more detail but also
increase the time it takes to migrate the data. Large time steps will decrease the resolution of the data but
also run much faster.
A time step extrapolation multiplier is provide to speed up the migration at the expense of resolution.
Small multipliers will sometimes speed up the migration considerably with very little loss in resolution.
The migration time step is computed by: input sample rate * multiplier.
If the program abruptly stop due to system failure, it can be restarted by using the restart menu option.
Every once in awhile, the program will checkpoint at which time it stores the current state of the data on
disk.
This program accepts poststack seismic data that has been corrected to a flat datum. If your data has been
corrected to a floating or sloping datum then you will need to re-apply datum statics. The migration needs
a trace for every CMP in the survey. If CMP(s) are missing they will be filled in prior to the migration.
Migration using McClellan transformations requires a circular symmetry. For this reason, the in-line and
x-line CMP interval must be equal. Another way to put this is that square CMP bins are required.
Velocities used in this migration are interval velocities. If you are inputting velocities via a VIP file then
the velocities must be in interval velocity. If you are inputting velocities via a matrix, then the velocities
should be RMS velocities. The program will convert matrix RMS velocity to interval velocity.
The speed of this program is generally related to:
Number of frequency steps computed. The greater the frequency range migrated, the greater the number of
frequency steps required.
The extrapolation time factor. The smaller the number, the greater the speed.
The reduction limit. The greater the number, the greater the speed.
Number of time steps chosen.
The time step extrapolation multiplier chosen.
Number of X and Y bins.
Number of points in the Remez filter.
Choose these values carefully to increase the performance of this program.
478
References
Hale, David, 1991, 3-D depth migration via McClellan transformations: Geophysics, 56, 1778-1785.
Soubaras, Robert, 1992, Explicit 3-D migration using equiripple polynomial expansion and Laplacian
synthesis: 62nd Annual Internat. Mtg., Soc. Expl. Geophys., Expanded Abstracts, , 92, 905-908.
Soubaras, R., 1992, Explicit extrapolation operator synthesis for 2D and 3D migration using the Remez
algorithm: 54th Mtg. Eur. Assoc. Expl Geophys., Abstracts, , 92, 238-239.
Input Channels
2. VIP velocity dataset: Optional connection from dataset SEGY data type.
Output Channels
1. GCI output: Required connection to next process GCI data type.
2. Finite diff mig output: Required connection to dataset FDMIG data type.
Parameters
Number of threads to use?
The performance of this migration can be increased by using threads on multi-CPU machines. Do not
attempt to use threads on a single CPU machine as this will actually slow the migration. Enter the number
of threads to use. The number of threads should be directly related to the number of CPU in the machine.

Select the starting midpoint bin number to use. Bin numbers before this value will not be used in the
migration or in the subsequent output. The default is Get from DB, which means, the first bin defined in
the database will be selected.

Select the ending midpoint bin number to use. Bin numbers after value will not be used in the migration or
in the subsequent output. The default is Get from DB, which means, the last bin defined in the database
will be selected.
479

Select the starting midpoint line number to use. Line numbers before this value will not be used in the
migration or in the subsequent output. The default is Get from DB, which means, the first line defined in
the database will be selected.

Select the ending midpoint line number to use. Line numbers after value will not be used in the migration
or in the subsequent output. The default is Get from DB, which means, the last line defined in the
database will be selected.
CMP or bin interval

Enter the CMP interval in feet or meters. This value will apply to both the in-line and x-line directions.
The default is Get from DB", which will get the in-line and x-line CMP intervals from the database.
RMS velocities
Select or build a matrix velocity file. If you are using a VIP file then this field is ignored. Please be sure to
enter RMS velocities because the program will convert them to interval velocities.
Matrix Type: RMSVEL
Maximum dip to migrate (degrees)

Enter the maximum dip to migrate in degrees. Estimate the dips that are contained in the seismic data that
you plan to migrate. A larger dip requires a longer extrapolation filter which will increase program
runtimes. Whereas a smaller dip will run faster but will not migrate dips past the maximum.
Example: A 30 degree max. dip will compute a 13 point Remez filter. A 70 degree max. dip will compute
a 25 point Remez filter.
Extrapolation time factor

This special divisor causes a pseudo depth step to be used. The smaller this number, the larger the depth
step and the quicker the migration can be accomplished.
Reduction limit
The reduction limit controls how large the pseudo depth step can be compared to the normal depth step. If
the limit were 100, then for lower frequency ranges of data, a pseudo depth step might be as large as 100
normal depth steps. Of course, the larger this limit, the more quickly the program can finish.
480
Number of points for Remez operator

Enter the number of points in a Remez filter. The default is to compute the number of points based upon
the maximum dip entered above. You can override the computation based upon dip by entering a value
here. The computed option will perform a linear operation from 30 to 70 degrees: 30 degree dip = 13
points, 70 degree dip = 25 points.
Remez filter dimensions for memory: filter[# of freq.] [# of velocities] [# of points]
Number of velocities for Remez operator

Enter the number of velocities to use for Remez filter calculations. During the migration, the program will
select a velocity index from the velocity found in the data. The velocity found in the data is interpolated to
the closest velocity index in the pre-save filter memory.
Remez filter dimensions for memory: filter[# of freq.] [# of velocities] [# of points]
Velocity application percentage:

Extrapolation multiplier for time step
The multiplier to determine the size of the time step taken during migration. The migration time step is a
function of the input sample rate times the multiplier.
Mig Time Step = Input Sample Rate * multiplier
The multiplier will speed up the migration sometimes with very little loss in resolution. The higher the
multiplier the more resolution is lost, so pick this parameter very carefully.
Migration sampling interval (us)

Enter the output time sampling interval of the seismic data in microseconds. The default is to set the
output sample rate to the input sample rate. This parameter also determines the number of steps required to
extrapolate the wavefield. For each time step, the complete set of frequency must be run through to
extrapolate the wavefield. A small time step will increase the time it takes to perform the migration. A
small time step means a slow migration while a large time step will mean a faster migration.
Maximum migration time (ms)

Enter the maximum time in milliseconds to perform the migration. A 2000 ms time will migrate the data
from 0 to 2 seconds. A 5000 ms time will migrate the data from 0 to 5 seconds. The default is to set to the
trace length of the input seismic data set.
481

The trace will be tapered from 0 to this time in milliseconds. The tapering will prevent the creation of
artifacts caused by the abrupt start of live data at the beginning of the trace.

The trace will be tapered from this time to the end of data in milliseconds. The tapering will prevent the
creation of artifacts caused by the abrupt end of live data at the end of the trace.
Inline side taper (# of traces)

This is the number of zero traces to pad to both sides of the in-line midpoint bins. Decreasing this
parameter will result in a faster execution time but data at the ends of the section could wrap around to the
other side of the section and cause upswings. Increasing this parameter will increase execution time and
could avoid artifacts on the sides of the section. Ideally this parameter should be the maximum depth
divided by four times the midpoint bin interval. However, if mostly flat data is at the ends of your section
a smaller number will do.
Crossline side taper (# of traces)

This is the number of zero traces to pad to both sides of the cross-line midpoint lines. Decreasing this
divided by four times the midpoint line interval. However, if mostly flat data is at the ends of your section

This migration operates in the frequency domain so there may be some FFT wrap around effects. These
effects can be eliminated by padding the trace. A 30 percent padding should be sufficient. If spikes exist in
the shallow section of the data then you might want to increase the padding. Be aware that padding will
increase the run time of the program, so choose this value carefully.

Enter the low cut frequency in Hertz. Specify the lowest usable frequency in the data. Be sure to bandpass
filter the data prior to the migration to avoid artifacts affiliated with abruptly truncating the frequency
band. Run times will increase with increasing frequency steps so choose this value carefully.
482

Enter the low pass frequency in Hertz. This frequency in conjunction with the low cut specified above are
used to compute the cosine taper used on the FFT data.

Enter the high pass frequency in Hertz. This frequency in conjunction with the high cut specified below
are used to compute the cosine taper used on the FFT data.

Enter the high cut frequency in Hertz. Specify the highest usable frequency in the data. Be sure to
bandpass filter the data prior to the migration to avoid artifacts affiliated with abruptly truncating the
frequency band. Run times will increase with increasing frequency steps so choose this value carefully.
Time variant application frequency parameters?

Matrix Type: FILEFREQ
Restore mute?
Select whether to re-apply the top mute after the migration. The mute will computed by finding the first
non-zero value on a input trace.
Maximum addressable memory (MB)

Enter the maximum amount of addressable memory in megabytes. For a 32 bit machine having a 31 bit
address field, use no more than 2048. For a 24 bit machine having a 23 bit address field, use no more than
8. For a 36 bit machine having a 35 bit address field, use no more than 32768. The amount of memory this
program uses is related to the :
# number of threads(processors).
# CMP bins * # of frequency steps.
# CMP bins * # of time steps.
If the program can store the complete wavefield in memory at one time, it can run much faster. Otherwise
it will be going to disk more often to read/write the current wavefield buffer. The program will also try to
store the velocity index array and part of the migration output array in memory to increase performance.
483
Threaded programs will require more memory than non-threaded programs.
Restart?
Select YES to restart the program after a previous failure of the program. While the migration is running,
it will checkpoint and save the current state of the data. If the program dies abruptly due to system
failure, the program can start where it left off or last did a checkpoint. If this is a new run on the seismic
data, due to new parameters then select NO which will start at the beginning of the program.
484
FDUMP
Module Description
Parameters
Module Description
FDUMP is a stand alone module to dump the contents of a disk file and print it in the job execution listing.
It can be very useful in defining data formats such as SEGY, or any BIN disk file, examples of which are
shown below. The HEXADECIMAL, ASCII and EBCDIC data dump formats are available.
The listing produced by this dump is below.
EXAMPLE
**** SeisUP Seismic Processing System, v2009.0 (64-bit) ****
GeoCenter, Inc.
Thu Jul
5 09:38:14 2012
-------------------------------------------------------------------------Host: godzilla
Process ID: 9784
-------------------------------------------------------------------------***Processing for the following module:
*FDUMP
Input format
Maximum number of K-bytes to read
Number of bytes to dump
Number of records to dump.
Dump type
:
:
:
:
:
SEGY
64
1024
10
Hexadecimal
Successfully opened for input, file: /mnt/gz4/seisup/usr/example/data/1.segy

*** Input data format is IBM floating point
Read 240 bytes
00000 c340f140
00020 4040c3d6
00040 c3d9c5e6
00060 40c39985
00080 d4c1d740
000a0 c340f340
000c0 d6c640d9
000e0 40404040
on record 1
c3d3c9c5 d5e34040
d4d7c1d5 e8404040
40d5d640 40404040
85924040 4040e64b
c9c44040 40404040
d9c5c5d3 40d5d640
c5c5d340 40404040
40404040 40404040
40404040
40404040
40404040
d3814ba4
40404040
40404040
e8c5c1d9
40404040
40404040
40404040
c340f240
99859485
40404040
40404040
40404040
40404040
40404040
d3c9d5c5
95a340a4
40404040
4040c4c1
4040d6c2
40404040
40404040
40c3a897
9589a3a2
40404040
e860e2e3
e2c5d9e5
40404040
40404040
9985a2a2
40404040
40404040
c1d9e340
c5d94040
Read 10240 bytes on record 2

00000 c340f440 c9d5e2e3 d9e4d4c5 d5e37a40 d4c6c740 40404040 40404040 404040d4
00020 d6c4c5d3 40404040 40404040 40404040 e2c5d9c9 c1d340d5 d6404040 40404040
485
00040
00060
00080
000a0
40404040
d9c5c3d6
c5c3d6d9
c340f640
40404040
d9c44040
c4404040
e2c1d4d7
User time:
System time:
40404040
404040f0
40404040
d3c540c9
40404040
4040c1e4
4040c3c4
d5e3c5d9
c340f540
e7c9d3c9
d740c6d6
e5c1d340
c4c1e3c1
c1d9e840
d3c44040
404040f2
40e3d9c1
e3d9c1c3
40404040
40d4e240
c3c5e261
c5e261d9
40404040
40e2c1d4
0.1 sec.
0.1 sec.
Parameters
Input format
Define the input connection type.
Options: SEGY, BIN

This buffer size should be large enough to read the largest physical record in the input data set. The
handler may not be able to the read the data set if the buffer is too small.

Number of 8 bit bytes to convert and dump.

Number of physical records to dump.
Dump type
Define the conversion format to use for the data .
Options: Hexadecimal, ASCII, EBCDIC
See also: TDUMP
486
FILTER
Module Description
Input Channels
Output Channels
Parameters
Module Description
FILTER is a time-domain time-variant (or time-constant) bandpass filter program. In the time-constant
mode, only the four filter "corner" points are required. Low and high cut points are 60 db down Low and
high pass points are 100% pass points. The time-variant mode triggers generating a multi-dimensional
matrix having primary and secondary header keys. Up to five filters and their corresponding start and stop
times may be chosen.
Ramp
|<->|
Ramp
|<->|
______________
______________
_______________
|
|\ /|
|\ /|
|
| Filter #1
| X | Filter #2
| X | Filter #3
| ...
|______________|/ \|______________|/ \|_______________|
^
^
^
^
^
^
0
End1
Start2
End2
Start3
End3
Input Channels
Output Channels
Parameters
Filter application domain
Select Time to apply the designed filters in the time domain. This option will result in faster runs if the
time domain filters are short. This option also can minimize artifacts if spikes are encountered. Select
Frequency to apply the designed filters in the frequency domain. This option could result in faster runs if
the time domain filters are long. This option can produce a more accurate filtered output especially if you
are applying low pass filters.
487
Options: Time, Frequency
Phase of the operator(s)

This parameter is only available if performing time domain filtering.
Options: Zero, Minimum
Time variant?
Filter type
Options: Ormsby, Butterworth
Low cut (hz.)

Required if Time variant? = No and Filter type: = Ormsby.
Low slope (db/octave)

Required if Time variant? = No and Filter type: = Butterworth. Set to 0 if Low pass (hz.) = 0.
Low pass (hz.)

High pass (hz.)

High cut (hz.)

Required if Time variant? = No and Filter type: = Ormsby.
High slope (db/octave)

Required if Time variant? = No and Filter type: = Butterworth.
Primary header key

TLSN
488

TLSN
Filters
Required if Time variant? = Yes and Filter type: = Ormsby.
Matrix Type: FILTER
Filters
Required if Time variant? = Yes and Filter type: = Butterworth.
Matrix Type: FILTERB

489
FKFILT
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKFILT performs frequency-wavenumber domain filtering. The filters can be specified in the form of a
fan or a polygon.
A total of 5 different windows are allowed. Each window may contain several polygons or fans which
make up a complex filter. The boundaries of the windows can vary in space. Since one FK panel contains
many traces, the center trace is used in interpolating the time windows. This is especially important to note
for stacked data if Time-space variant filters? is Yes. A stacked panel typically contains 700 traces.
The T window # and Filter number referenced in the FKFANV, FKPLOY and FKPOLYV matrices are
indices and have to be sequential starting from 1. The FKPLOYV matrix references both, they should be
equal. If Time-space variant filters? is Yes, the matrix given by Space variant time windows: must have at
least as many time zones as there are filters. The time zones must overlap and cover the entire trace
without gaps.
Input Channels
Output Channels
Parameters
Filter function
Options: Reject, Pass
490
Filter type
Options: Fan, Polygon
Time-space variant filters?

WARNING If Time-space variant filters? = No and the matrix specified by Fan filter: or Polygon filter:
has multiple spread sheets, each spread sheet is treated as a separate filter. Aside from increasing
execution time, this can have unexpected effects if Filter function: = Pass. Ideally, all filters should be on
the same spread sheet for one location.
Fan filter
Required if Filter type: = Fan and Time-space variant filters? = Yes.
Matrix Type: FKFANV
Fan filter
Required if Filter type: = Fan and Time-space variant filters? = No.
Matrix Type: FKFAN
Polygon filter
Required if Filter type: = Polygon and Time-space variant filters? = Yes.
Matrix Type: FKPOLYV
Polygon filter
Required if Filter type: = Polygon and Time-space variant filters? = No.
Matrix Type: FKPOLY
Primary header key

Required if Time-space variant filters? = Yes.
TLSN
491

TLSN
Space variant time windows

Wavenumber taper (% Nyquist)

Required if Filter type: = Polygon.
Frequency taper (% Nyquist)

Required if Filter type: = Polygon.
Max number of traces per FK transform

Overlap between FK transforms(# of traces)
Taper at trace start(ms)
Taper at trace end(ms)
Spatial padding
Options: No-to save time, Yes-to unwrap noise
Temporal padding
Options: No-to save time, Yes-to unwrap noise
DB down in reject zone
492
Restore mute?
493
FKINT
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKINT is an unaliased F-K domain trace interpolator. It interpolates prestack / poststack data by halving
the original trace interval. The input data can be either 2-D or 3-D in any sorted order. Interpolation is
performed on the ensemble basis. For prestack common shot / receiver ensembles, FKINT automatically
divides each ensemble into several trace groups so that there is no big trace gap in each group. Trace
headers are linearly interpolated in each group. If parameter newgeo is specified to use the new midpoint
geometry, header words SDPN, MBIN, MLIN, MCX, MCY, MSFL, and MEFL will be updated based on
the X and Y coordinates. For prestack interpolation, header words MSBN, MSLN, SSBN, SSLN, RSBN,
RSLN, and SGEN are also updated to use the new information in the database. The new geometry can be
created by the STATION module.
References
Gulunay, N., and Chambers, R.E., 1996, Unaliased f-k domain trace interpolation (UFKI): 66th Ann.
Internat. Mtg., Soc. Expl. Geophys., Expanded Abstracts, 1461-1464.
Spitz, S., 1989, Seismic trace interpolation in the F-X domain: Geophysics, 50, 785-794.
Input Channels
Output Channels
Parameters
Spatial gate (# of traces)
494
Temporal gate (# of samples)

Spatial taper (# of traces)
Temporal taper (# of samples)
Use the new midpoint geometry?
Output 0 FOLD header for interpolated traces?
495
FKKFILT
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKKFILT performs a 3 dimensional Fourier transform and filter. Each ensemble input to FKKFILT
contains all traces to be included in a transform. The time axis is transformed to frequency. The K (wave
number) axes (Kx, Ky) are defined by header words. Each axis is defined by 7 parameters. Two
parameters define the header containing the values positioning the trace along the axis. The increment and
maximum value parameters define the size of each axis. The reference header word defines the center of
each axis. The real trace interval defines the actual wave number values.
FKKFILT allows the transforms to be output to a GCI data set. The transforms may be displayed for
analysis and determination of mutes for the filter function. Other processing may be performed in FKK
space and the resulting data sets transformed back to TXX space. Header words store the input trace
geometry for the inverse transform. Transforms may be output as complex pairs or amplitude and phase.
Input Channels
Output Channels
Parameters
Type of Fourier Transform
Transform from time to frequency domain (Forward), frequency to time (Reverse), or time to time with
muting (MUTE) in the frequency domain.
Options: Forward, Reverse, Mute
496
Transform Order
The transform trace is either ordered in complex pairs (Complex, i.e. sin,cos) or all real values first in the
Phase Units
Starting time to transform

The starting time of the window to be transformed. This parameter is accessed if Type of Fourier
Transform is set to Forward or Mute.
Ending time to transform

The ending time of the window to be transformed. This parameter is accessed if Type of Fourier
Transform Length Multiplier

The Fourier transform length is set to the next power of 2 greater than the transform window. This
parameter allows the user to lengthen the transform. This parameter is accessed if Type of Fourier
Output trace length

The output trace length may be set to any portion of the original transformed data. Note that the original
transform start and reference times will be used in reconstructing the trace. This parameter is accessed if
Type of Fourier Transform is set to Reverse.
497
Header Containing Offset for Kx

This is the header key which defines the Kx axis. This parameter is accessed if Type of Fourier
Options: CDPN, DIST, DMODIST, FCSN, FSPN, MBIN, MLIN, MSBN, MSLN,
OIDN, RSBN, RSLN, SDPN, SGEN, SBIN, SLIN, SSBN, SSLN, SSPN, TIM1,
TIM2, TLSN, Other
Header ID Index for Offset Kx

Header key ID which defines the Kx axis. This parameter is accessed if Header Containing Offset for
Kx is set to other.
Maximum Offset Expected for Kx

Determines the maximum offset included in the Kx direction. This parameter is accessed if Type of
Fourier Transform is set to Forward or Mute.
Offset Increment for Kx

Specifies the header word value increment in the Kx direction. This parameter is accessed if Type of
Header Containing Offset Reference for Kx

The header contains the reference value (center) for the of Kx axis. This parameter is accessed if Type of
TIM2, TLSN, Other
Header ID Index for Offset Reference for Kx

Header key ID used for reference in the Kx direction. This parameter is accessed if Header Containing
Offset for Kx is set to other.
Distances between stations/receivers in Kx direction

Specifies the actual spacing of stations (traces) in the Kx direction. It is used to compute proper wave
number (K) values. This parameter is accessed if Type of Fourier Transform is set to Forward or Mute.
The value is used to compute proper wave number values.
498
Header Containing Offset for Ky

This is the header key which defines the Ky axis. This parameter is accessed if Type of Fourier
TIM2, TLSN, Other
Header ID Index for Offset for Ky

Header key ID which defines the Kx axis. This parameter is accessed if Header Containing Offset
Reference for Kx is set to other.
Maximum Offset Expected for Ky

This will determine the maximum offset in the Ky direction. This parameter is accessed if Type of
Offset Increment for Ky

Specifies the header word value increment in the Ky direction. This parameter is accessed if Type of
Header Containing Offset Reference for Ky

The header contains the reference value (center) for the of Ky axis. This parameter is accessed if Type of
TIM2, TLSN, Other
Header ID Index for Offset Reference for Ky

Header key ID used for reference in the Ky direction. This parameter is accessed if Header Containing
Offset Reference for Ky is set to other.
Distances between stations/receivers in Ky direction

Specifies the actual spacing of stations (traces) in the Kx direction. It is used to compute proper wave
number (K) values. This parameter is accessed if Type of Fourier Transform is set to Forward or Mute.
The value is used to compute proper wave number values.
499
Primary surgical mute header key

This parameter is accessed if Type of Fourier Transform is set to MUTE.
Options: NONE, CDPN, DIST, DMODIST, FCSN, FSPN, MBIN, MLIN, MSBN,
Primary surgical mute header index

This parameter is accessed if Primary Surgical Mute Header Key is set to other.
Secondary surgical mute header key

Secondary surgical mute header index

This parameter is accessed if Secondary Surgical Mute Header Key is set to other.
Ensemble surgical mute header key

Ensemble surgical mute header index

This parameter is accessed if Ensemble Surgical Mute Header Key is set to other.

Value in the chosen header will be added to the mute times.
500
Surgical Mutes
The name of the surgical mute matrix that will be used to mute the transformed data. Mute values are
coded in radial wave number Kr = (Kx 2 + Ky 2 ) 1/2 (header DIST) and frequency (Start Time, End Time).
Units implied are 10 6 cycles/distance unit.
Matrix Type: SRGMUTE
Taper the mute?

Options: Yes, No
Taper length (Hz)

The Taper length is coded in number of Hertz.
Suppression in mute zone (dB)

The Suppression is coded in dB.
501
FKMIG
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKMIG will perform 2-D or two-pass 3-D Stolt F-K migration/modeling on stacked data.
F-K Migration/Modeling Algorithm

FKMIG uses the Stolt algorithm which is exact for a constant velocity medium. To accommodate a mild
velocity variation, Stolt introduced "Stolt Stretch". This is basically a stretching of the time section to an
approximately constant-velocity section (pseudo-depth). This stretch is defined by a combination of the W
factor and the base velocity. After migration/modeling, the constant-velocity section is converted back to
the original time section. The user may invoke a high resolution algorithm if noise retention is not
selected.
W Factor
The theoretical range for the W factor is between zero and two. When W equals one, the effect is the exact
constant velocity Stolt algorithm. When the W factor is less than one, the impulse response will compress
inward along the steep flanks. When the W factor is greater than one, the impulse response opens up. This
gives the appearance of changing the aperture. When the velocity is constant, W greater than one implies
over migration at steeper dips. While W less than one implies under migration at steeper dips. Typical W
factor values should be between 0.5 and 1.0 for a variable velocity media.
Velocities
To accommodate velocity variation in the in-line and cross-line direction VIP velocities should be
attached to the VIP input channel. Users should select the options in module VIP to compute RMS
velocities and be TIME oriented.
*** NOTE ***
The VIP velocities need to be smooth in the in-line and cross-line direction to prevent angular distortions
in the constant-velocity section. Therefore heavy smoothing should be requested within the module VIP.
If no VIP velocities are input, FKMIG will derive a single velocity function for migration/modeling by
computing the average of the velocities in the input velocity matrix parameter.
502
Base Velocity
The base velocity is used to determine the depth sample interval for the constant-velocity conversion.
Normally the user should specify the maximum frequency of interest and the program will calculate the
base velocity. To manually input the base velocity, a good rule-of-thumb to use to avoid aliasing is to
enter a base velocity equal to or less than:
Nyquist frequency
---------------------------- * Minimum Velocity
Maximum Frequency to Migrate
The approximate number of samples in the constant-velocity section is:

Maximum Input Velocity
Number of Input Samples * ---------------------Base Velocity
The time direction transform will be the number of samples in the constant-velocity section times two and
raised to the next power of two. The difference between this transform size and the number of samples in
the constant-velocity section is a pad of zeros.
Two Dimensional Transformation

The transformation to F-K space is done by a horizontal and vertical Fast Fourier Transform. The input
data should be as free as possible of spikes. Sharp cutoffs in the data may produce spikes in the F-K
domain transformation. To help alleviate these sharp cutoffs, FKMIG has the following options:
1. Top of trace linear taper
2. Bottom of trace linear taper
3. Linear taper across the ends of the section.
Noise Removal and Retention

Migration will move data from the apparent dip to the true dip. For dips measured at 45 degrees, migration
will move those dips to 90 degrees. Any data that was above 45 degrees is noise. FKMIG can retain noise
beyond a certain dip limit as well as noise at the spatial Nyquist as defined in the following diagram.
Spatial
Spatial
Nyquist
Nyquist
_________________________________________________ Temporal
|
|
|
|
| Nyquist
|
|
|
|
|
|
|
MIGRATED
|
MIGRATED
|
|
|
|
|
|
|
| N | \
|
/ | N |
| O |
\
|
/
| O |
F | I |
\
|
/
| I | F
| S |
\
|
/
| S |
| E |
\
|
/
| E |
|
|
\
|
/
|
|
503
|
|
NOISE
\
|
/
NOISE
|
|
|
|
\ | /
|
|
|_____|_________________\|/_________________|_____|
-100%
0
+100%
Reference
Claerbout, J. F., 1985; Imaging the earths interior; Blackwell Scientific Publications.
Stolt, R. H., 1978; Migration by Fourier Transform: Geophysics, Vol 43, 23-48.
Yilmaz, O., 1987; Seismic Data Processing, SEG, pp 241-353.
Input Channels
2. VIP velocity dataset: Required connection from dataset SEGY data type.
Output Channels
Parameters
Max. memory to use for transpose (MBytes)
The number of words required for an in-core migration/modeling is the number of depth samples in the
constant-velocity section times the next power of two for the X-direction transform. If there is not enough
physical memory to hold the constant-velocity section, the migration/modeling could dramatically slow
down. If the section cannot fit into this parameters number of Mega-bytes, then an out of core algorithm
will be used via the hard disk.
Restore mute?
Top of trace taper (ms.)
Bottom of trace taper (ms.)
504
Edge taper multiplier factor

Edge and zero zones will be multiplied by a ramp function from this number to 1.0 over a user specified
number of traces.
Number of traces to taper at 0 ms.

Number of traces to taper at record length
Base velocity
The user should normally default this parameter and FKMIG will compute the base velocity using the
highest frequency of interest in the input data.
Highest frequency of interest

This is used to compute the default base velocity.
Migration/Modeling ALPHA factor

The ALPHA factor can be used as follows:
>1.0
=1.0
<1.0
Attenuate the relative amplitude of dipping

events and birdwings.
Keep the original amplitudes.
Boost the relative amplitude of dipping events.
Depth decay factor

Scalar function to apply to the input data before 2-D FFT and remove after 2-D inverse FFT
N
Scalar(D) =
2500
---D
Where:
D = Depth
N = Decay Factor
This factor is used to suppress birdwings by increasing the amplitude in the shallow section and
decreasing the amplitude in the deep section. Suggested values for N range from 0 to 2.0. A value of zero
will result in no decay.
505
W Factor
See above for an explanation.
RMS velocities if no VIP input

If no VIP velocities are attached to the VIP input channel this parameter is required to derive a single
average velocity function for migration/modeling.
Matrix Type: RMSVEL
Velocity percentage to use

This is the percent by which the input velocities will be multiplied. This will be applied to either the VIP
velocities or the computed average velocity.
Migration/Modeling:
Options: Migration, Modeling
Retain noise?
Required if Migration/Modeling = Migration.
High resolution?
Required if Retain noise? = No or if Migration/Modeling = Modeling.

Required if Retain noise? = Yes.
Roll-off between max. dip & noise

Required if Retain noise? = Yes. This is the roll-off in degrees between the migrated dips and the noise.
Percent of dip noise to include

Required if Retain noise? = Yes. This is the percentage to apply to the noise beyond the maximum dip to
migrate.
506
Maximum K to migrate (%)

Roll-off between max. K & noise

Required if Retain noise? = Yes. This is the roll-off in percent between the migrated K frequencies and the
noise.
Percent of K noise to include

Required if Retain noise? = Yes. This is the percentage to apply to the noise beyond the maximum K to
migrate.
Inline & crossline padding (traces)

This is the minimum number of dead traces to be padded at the end of the section to prevent wraparound
of the 2-D transformed data. Ideally this should be:
(Maximum velocity) * (Maximum time (Sec.))
-----------------------------------------2 * (Distance between two CMPs)

507
FKMOD
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKMOD will perform 2-D or two-pass 3-D Stolt/Disher F-K modeling on stacked data.
F-K Modeling Algorithm

FKMOD uses the Stolt/Disher modeling algorithm which is exact for a constant velocity medium. To
accommodate a mild velocity variation, Stolt introduced "Stolt Stretch". This is basically a stretching of
the time section to an approximately constant-velocity section (pseudo-depth). This stretch is defined by a
combination of the W factor and the base velocity. After modeling, the constant-velocity section is
converted back to the original time section.
W Factor
The theoretical range for the W factor is between zero and two. When W equals one, the effect is the exact
constant velocity Stolt algorithm. When the W factor is less than one, the impulse response will compress
inward along the steep flanks. When the W factor is greater than one, the impulse response opens up. This
gives the appearance of changing the aperture. When the velocity is constant, W greater than one implies
over modeling at steeper dips. While W less than one implies under modeling at steeper dips. Typical W
factor values should be between 0.5 and 1.0 for a variable velocity media.
Velocities
To accommodate velocity variation in the in-line and cross-line direction VIP velocities should be
attached to the VIP input channel. Users should select the options in module VIP to compute RMS
velocities and be TIME oriented.
*** NOTE ***
The VIP velocities need to be smooth in the in-line and cross-line direction to prevent angular distortions
in the constant-velocity section. Therefore heavy smoothing should be requested within the module VIP.
If no VIP velocities are input, FKMOD will derive a single velocity function for modeling by computing
the average the velocities in the input velocity matrix parameter.
508
Base Velocity
The base velocity is used to determine the depth sample interval for the constant-velocity conversion.
Normally the user should specify the maximum frequency of interest and the program will calculate the
base velocity. To manually input the base velocity, a good rule-of-thumb to use to avoid aliasing is to
enter a base velocity equal to or less than:
Nyquist frequency
---------------------------- * Minimum Velocity
Maximum Frequency to Model
The approximate number of samples in the constant-velocity section is:

Maximum Input Velocity
Number of Input Samples * ---------------------Base Velocity
The time direction transform will be the number of samples in the constant-velocity section times two and
raised to the next power of two. The difference between this transform size and the number of samples in
the constant-velocity section is a pad of zeros.

domain transformation. To help alleviate these sharp cutoffs, FKMOD has the following options:

Modeling will move data from the true dip to the apparent dip. For dips measured at 90 degrees, modeling
will move those dips to 45 degrees. Any data that was above 45 degrees is noise. FKMOD can retain noise
beyond a certain dip limit as well as noise at the spatial Nyquist as defined in the following diagram.
Spatial
Spatial
Nyquist
Nyquist
_________________________________________________ Temporal
|
|
|
|
| Nyquist
|
|
|
|
|
|
|
MODELED
|
MODELED
|
|
|
|
|
|
|
| N | \
|
/ | N |
| O |
\
|
/
| O |
F | I |
\
|
/
| I | F
| S |
\
|
/
| S |
| E |
\
|
/
| E |
|
|
\
|
/
|
|
509
|
|
NOISE
\
|
/
NOISE
|
|
|
|
\ | /
|
|
|_____|_________________\|/_________________|_____|
-100%
0
+100%
Reference
Claerbout, J. F., 1985; Imaging the earths interior; Blackwell Scientific Publications.
Stolt, R. H., 1978; Modeling by Fourier Transform: Geophysics, Vol 43, 23-48.
Yilmaz, O., 1987; Seismic Data Processing, SEG, pp 241-353.
Input Channels
2. VIP velocity dataset: Required connection from dataset SEGY data type.
Output Channels
Parameters
Max. memory to use for transpose (MBytes)
The number of words required for an in-core modeling is the number of depth samples in the
constant-velocity section times the next power of two for the X-direction transform. If there is not enough
physical memory to hold the constant-velocity section, the modeling could dramatically slow down. If the
section cannot fit into this parameters number of Mega-bytes, then an out of core algorithm will be used
via the hard disk.
Restore mute?
510

number of traces.

Base velocity
The user should normally default this parameter and FKMOD will compute the base velocity using the
highest frequency of interest in the input data.
Highest frequency of interest

This is used to compute the default base velocity.
Modeling ALPHA factor

The ALPHA factor can be used as follows:
>1.0
=1.0
<1.0
Attenuate the relative amplitude of dipping

events and birdwings.
Keep the original amplitudes.
Boost the relative amplitude of dipping events.
Depth decay factor

Scalar function to apply to the input data before 2-D FFT and remove after 2-D inverse FFT
N
Scalar(D) =
2500
---D
Where:
D = Depth
N = Decay Factor
This factor is used to suppress birdwings by increasing the amplitude in the shallow section and
decreasing the amplitude in the deep section. Suggested values for N range from 0 to 2.0. A value of zero
will result in no decay.
511
W Factor
See above for an explanation.
RMS velocities if no VIP input

If no VIP velocities are attached to the VIP input channel this parameter is required to derive a single
average velocity function for modeling.
Matrix Type: RMSVEL

This is the percent by which the input velocities will be multiplied. This will be applied to either the VIP
velocities or the computed average velocity.
Retain noise?
Maximum dip to model (degrees)

Required if Retain noise? = Yes. This is the roll-off in degrees between the modeled dips and the noise.

Required if Retain noise? = Yes. This is the percentage to apply to the noise beyond the maximum dip to
model.
Maximum K to model (%)


Required if Retain noise? = Yes. This is the roll-off in percent between the modeled K frequencies and the
noise.

Required if Retain noise? = Yes. This is the percentage to apply to the noise beyond the maximum K to
model.
512
Inline & crossline padding (traces)

of the 2-D transformed data. Ideally this should be:
(Maximum velocity) * (Maximum time (Sec.))
-----------------------------------------2 * (Distance between two CMPs)

513
FKMRC
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKMRC removes surface related multiples by the "model then subtract" concept. The model is generated
by F-K upward extrapolation of the original shot record, adding an extra "water bounce". The resulting
multiple model is aligned with the original data by cross-correlation, then adaptively subtracted from the
original data. If the original datas near trace has non-zero offset, traces constructed from the near trace
(using NMO stretch) are added to fill the gap. This improves the model quality for the near offset traces.
When a shot is transformed into the F-K domain, the padding in time is 50% and the padding in K is 50%
for trace spacings <= 15 meters, other wise the K padding is 150%. Water bottom reflection time is
required in an input header (TIM1 or TIM2). These values are obtained by picking a HORIZON in
DISPLAY using the SBIN and DIST keys. Enough shots have to be picked to accurately describe the
water bottom reflections. If the water bottom times (depths) vary slowly, less shot have to be picked than
if the water bottom varies rapidly. If the water bottom reflection times are picked too far above the true
time, the model estimate will suffer under-extrapolation errors. If the picked times are too far below the
true times, the model estimate will suffer over-extrapolation errors, and in addition, may have needed
events cut off depending upon the Header adjustment time parameter.
Input Channels
Output Channels
Parameters
FKMRC has two modes of operation. In Multiple estimate mode, the extrapolated shot record is output for
QC. It should help determine if the anti-alias filter is necessary. When compared to the original input shot
record, the extrapolated water bottom reflection should line up in time very near the first water bottom
multiple reflection on the original. If not, then perhaps the water velocity needs adjustment, or perhaps the
water bottom reflection time is not accurate, or has the wrong key.
514
In Multiples removed mode, the multiple estimate is aligned with , then subtracted from the original shot
and the result is output.
Output type
Options: Multiple estimate, Multiples removed
Nearest offset (ft or m)

Receiver spacing (ft or m)
Water velocity (ft/sec or m/sec)
Header describing water bottom reflection times(ms)
The water bottom reflection times are loaded into TIM1 or TIM2 by using the HORIZON module in the
flow before FKMRC. Remember to use the same keys as those used when picking the water bottom
reflection times in DISPLAY.
Header time adjustment (ms)

The linear water surface wave is removed prior to extrapolation by muting the shot above the water
bottom reflection time (input in TIM1 or TIM2). The constant header time adjustment value is added to
the header time (TIM1 or TIM2) to define the end time of the mute. The effects of the mute may be seen
on the Multiple estimate output.
Use anti-alias option?

If the receiver spacing is above about 12.5 meters (45 feet) spatial aliasing creates extrapolation artifacts.
These artifacts may or may not degrade the final multiple-removed results. If degradation is present, these
artifacts can be removed by selecting yes to Use anti-alias option.
Maximum time shift (ms)

Each trace in the multiple model is correlated with the corresponding trace on the original data to
determine the best time shift. Every multiple trace is shifted between plus and minus this maximum value
in the best shift determination prior to subtraction.
Number of channels in subtraction filter (odd)

The multiple record is subtracted from the original record using a multi-channel adaptive subtraction filter.
The number of channels may range from 1 to 21. The more channels used, the smoother the results, the
longer the run times and the lower the adaptation rate. Use the lowest number of channels needed to
515
smoothly remove the multiple events.
Subtraction filter length (ms)

The subtraction filter length should be as short as possible, yes cleanly remove multiple events. A general
starting value may be 1/8 to 1/4 the dominant frequency wavelength. This is the second most critical
parameter in multiple subtraction.
Adaptation rate
This is the most critical subtraction parameter. If too low, little or no subtraction will occur. If too high,
the result may be dead (0) values where the multiple event appeared. If really too high, total instability
could result in black areas on the DISPLAY screen. Experiment by starting low (.01) and increasing by
.05 until the multiple events are removed smoothly and cleanly. Another method is to bracket a good value
by experimenting with alternately low and high values.
516
FKPLOT
Module Description
Input Channels
Output Channels
Parameters
Module Description
FKPLOT performs 2D Fourier transform on the data and displays the amplitude spectrum in terms of
magnitude, power or DB down. The events, which dip down with ensemble key value, will be mapped
into the quadrant with positive frequency and positive wavenumber.
The radial lines indicates the dips in ms/trace. The vertical line is 0. There are nine radial lines on each
side of the vertical. They correspond to +/- 1, 2, 4, 8, 16, 32, 64, 128, 256 ms/trace in dip.
Input Channels
Output Channels
1. Fk plot file: connection to dataset CGM data type.
Parameters
Output type
Amplitude, DB down or power.
Options: Amplitude, DB down, Power
Horizontal plot size (inches)

Vertical plot size (inches)
517
Number of contour levels

Max number of traces per FK transform
Start of time window(ms)
End of time window(ms)
Taper at window start(ms)
Taper at window end(ms)
Spatial padding
Options: No-to save time, Yes-for high resolution
Temporal padding
Options: No-to save time, Yes-for high resolution
Maximum frequency of interest(Hz)
518
FLAT
Module Description
Input Channels
Output Channels
Parameters
Module Description
FLAT flattens a user specified horizon by cross correlating each trace with a pilot trace. The search
window is critical to the power of flattening. The search window has been found to work best if it is
between one and one and a half dominant periods in length. Too large a window can cause cycle skipping.
With too small a window, the full wavelet will not be covered.
Input Channels
Output Channels
Parameters
Header key for pilot trace
TLSN
Pilot trace number

Time of the horizon (ms)
Time to put the horizon(ms)
519
Search window(ms)
The default depends on the sampling rate because the search is very sensitive to the number of samples.
The horizon is
Options: Peak, Trough
520
FLEX
Module Description
Input Channels
Output Channels
Parameters
Module Description
FLEX can be run to normalize the offset distribution for 3-D areas that have imperfect fold distributions
due to the acquisition method. FLEX normally is applied to enhance multiple suppression, avoid wavelet
distortions, and avoid stacked amplitude variations. FLEX can also help out the 3-D DMO process
because the correct amplitude and phase will be produced by an even distribution of traces within an offset
plane.
FLEX will duplicate or move traces from adjacent traces in the cross-line direction. If there is dip in the
cross-line direction, cross-line smear can occur and can attenuate high-frequency reflections. The amount
of smear is determined by the amount of cross-line dip, reflection time, and the velocity.
Within the SeisUP system the midpoint cell coordinates are located at the center of the cell. FLEX will
make the normally rigid cell boundaries overlap onto adjacent cells. The result is that traces can be spread
or duplicated across multiple midpoint lines. After GEOM is applied, each trace will contain the start
FLEX line number (MSFL) and the ending FLEX line number (MEFL). Traces are not actually
duplicated, rather when they are stacked, the same trace will be used in multiple midpoint lines. Currently
the modules that support the FLEX headers are DMO3D, DNG1, CVA3D, and STACK3D. The MLIN in
the header corresponds to the midpoint line where the trace belongs without FLEX.
FLEX will split the offset range into offset groups. The starting offset will correspond to the center of the
first offset group. The number of offset groups is determined by the maximum offset minus the minimum
offset divided by the offset increment plus one.
For each offset group, the user can reject traces that exceed a user specified maximum fold or duplicate
traces from adjacent lines to achieve a minimum fold. For the maximum fold check, FLEX will keep
traces that are the closest to the cell center. For the minimum fold check, FLEX will attempt the use traces
that were rejected due to the maximum fold. The traces closest to the cell center within a percentage of the
cross-line cell size outside the cell boundary will be used. The percentage can be linearly tapered by
specifying values to use at the minimum and maximum offset or offset variant percentages can be
specified with a matrix.
FLEX will print out a line of text for each shot line whenever FLEX is deleting, loading, and saving a line
so that the user may determine the progress of FLEX for large projects. At the end of the program, FLEX
will print out the following for each offset group:
521
1.
2.
3.
4.
5.
6.
7.
Offset group number (Group#)

Flex percentage (Flex)
Offset range (From & To)
Number of input traces (#Input)
Number of traces to drop (#Drop)
Number of extra traces after duplication (#Add)
Number of flex traces (#Flex=#Input+#Add-#Drop)
Parameters
Minimum offset
This is the center of the first offset range.
Maximum offset
This an offset in the last offset range.
Increment between offset ranges

Minimum fold for each offset range
For offset range folds lower than this amount, FLEX will duplicate traces from adjacent midpoint lines.
Maximum fold for each offset range

For offset range folds higher than this amount, FLEX will drop traces furthest away from the cell center.
Use a linear overlap?

Crossline overlap (%) at the minimum offset
Crossline overlap (%) at the maximum offset
Crossline overlaps
Use this matrix to specify offset variant flex overlays.
Matrix Type: FLEXOVP
522
FLEXBIN
Module Description
Input Channels
Output Channels
Parameters
Module Description
FLEXBIN will perform flexible binning on common offset sorted data. FLEXBIN can be run to normalize
the offset distribution for 3-D areas that have imperfect fold distributions due to the acquisition method.
FLEXBIN normally is applied to enhance multiple suppression, avoid wavelet distortions, and avoid
stacked amplitude variations. FLEXBIN can also help out the 3-D DMO or pre-stack migration process
because the correct amplitude and phase can be produced by an even distribution of traces within an offset
plane. If there are dipping events, smearing can occur and can attenuate high-frequency reflections. The
amount dip, reflection time, and the velocity determine the amount of smear. Within the SeisUP system
the midpoint cell coordinates are located at the center of the cell. FLEXBIN will make the normally rigid
cell boundaries overlap onto adjacent cells. The result is that traces can be spread or duplicated across
multiple midpoint bins.
FLEXBIN will duplicate or move traces from adjacent traces within an ensemble. To perform flexible
binning in the cross-line direction on data that has been offset binned, sort by DMODIST, MBIN &
MLIN. To perform flexible binning in the in-line direction sort the data by DMODIST, MLIN & MBIN.
The fold after using FLEXBIN can be determined after stack by extracting the fold from the trace header
by using the DBHDR module. The DMODIST trace header word can be set with the COFF or DMODIST
modules.
FLEXBIN is similar to the FLEX module except for the fact that FLEX uses geometry from the database
and stores the flexible binning information in the database so that other modules like the FOLD and
GEOM modules can use the flexible information. FLEXBIN on the other hand performs flexible binning
based upon the data and does not directly store flexible information in the database. The module FLEX
also can be used to perform flexible binning only in the cross-line direction. FLEXBIN can be used to flex
523
bin in the cross-line or in-line direction. FLEXBIN can also be used on large surveys where it is desired
not to increase the database size. FLEXBIN also will produce more accurate flexible binning if traces are
killed or dropped.
The user can reject traces that exceed a user specified maximum fold or duplicate traces from adjacent
lines to achieve a minimum fold. For the maximum fold check, FLEXBIN will keep traces that are the
closest to the cell center. For the minimum fold check, FLEXBIN will attempt the use traces that were
rejected due to the maximum fold check. The traces closest to the cell center within a percentage of the
cross-line cell size outside the cell boundary will be used. The percentage can be linearly tapered by
specifying values to use at the minimum and maximum offset or offset variant percentages can be
specified with a matrix.
Any traces that are borrowed or copied will have the trace header FOLD set to zero. This can be used for
example to provide a even distribution of traces within an offset for pre-stack migration and then after
migration remove all borrowed or copied data.
Input Channels
Output Channels
Parameters
Minimum fold for each offset
If the fold within an offset is lower than this amount, FLEXBIN will duplicate traces from adjacent
midpoint cells.
Maximum fold for each offset

If the fold within an offset is higher than this amount, FLEX will drop traces furthest away from the cell
center.
Use a linear overlap?

Select Yes to enter a constant or linear overlap from the minimum to the maximum offset. Select No to
input an offset variant overlap spreadsheet.
524
Minimum offset
If performing a linear overlap, enter the minimum binned offset.
Maximum offset
If performing a linear overlap, enter maximum binned offset.
Midpoint cell overlap (%) at the minimum offset

If performing a linear overlap, enter the midpoint cell overlap corresponding to the minimum offset. The
overlap percentage used will be linearly interpolated between for offsets between the minimum and
maximum offsets entered. This value is the percentage of adjacent midpoint cells to allow for flexible
binning. For example a value of zero is no borrowing of adjacent bins and a value of 50% will allow any
midpoints between the edge of the current cell to the center of the adjacent midpoint cell. A value of 200%
will allow bin borrowing from two whole adjacent bins.
Midpoint cell overlap (%) at the maximum offset

If performing a linear overlap, enter the midpoint cell overlap corresponding to the maximum offset. This
value is the percentage of adjacent midpoint cells to allow for flexible binning. For example a value of
zero is no borrowing of adjacent bins and a value of 50% will allow any midpoints between the edge of
the current cell to the center of the adjacent midpoint cell. A value of 200% will allow bin borrowing from
two whole adjacent bins.
Midpoint cell overlaps

If you are not using a linear overlap, use this matrix to specify offset variant flex overlaps.
Matrix Type: FLEXOVP
Minimum midpoint cell (MBIN or MLIN) number

If sorting by offset, MLIN and MBIN then enter the minimum MBIN number to process. If sorting by
offset, MBIN and MLIN then enter the minimum MLIN number to process. Any midpoints prior to this
number will be dropped.
Maximum midpoint cell (MBIN or MLIN) number

If sorting by offset, MLIN and MBIN then enter the maximum MBIN number to process. If sorting by
offset, MBIN and MLIN then enter the maximum MLIN number to process. Any midpoints after to this
number will be dropped.
525
FOLD
Module Description
Input Channels
Output Channels
Parameters
Module Description
FOLD is a process which reads the geometry database, calculates the fold distribution, and optionally
creates an attribute in the database and / or creates a CGM plot. FOLD can optionally read the fold from
an input attribute that could have been created with the module DBHDR. Specifying a minimum and
maximum offset limits the fold to enable offset distribution evaluation.
Output Channels
1. CGM Output: Optional connection to disk file
Parameters
Fold type
Select Pre-stack to calculate and display the fold within common offsets. Select Post-stack to calculate
and display the fold after CMP stack.
Options: Pre-stack, Post-stack
Input fold from

Select Databaseto calculate the fold from the database. Select Fold attribute to input the fold from a fold
attribute.
Options: Database, Fold attribute
Input fold attribute name

This could have been created with the module DBHDR to plot the actual fold versus the fold calculated
from the database. The actual fold may be different due to missing data, duplicate data, or trace kills. This
parameter is only displayed if the parameter Fold type: parameter is Post-stack.
526
Matrix Type: DBFOLD
Pre-stack input fold attribute name

This could have been created with the module DBHDR to plot the actual fold versus the fold calculated
from the database. The actual fold may be different due to missing data, duplicate data, or trace kills. This
parameter is only displayed if the parameter Fold type: parameter is Pre-stack.
Matrix Type: DBFOLDOFF
Use FLEX binning result?

Minimum offset
Maximum offset
Minimum common-offset (distance units)
Maximum common-offset (distance units)
Common-offset increment (distance units)
DB fold attribute name
FOLD will output the calculated fold to a midpoint attribute in the database. This attribute can then be
viewed with the modules QCVIEW or XYMAP.
Matrix Type: DBFOLD
DB pre-stack fold attribute name

FOLD will output the calculated common offset fold to a midpoint attribute in the database.
Output CGM plot?

Number of bins per inch
Required if Output CGM plot? = Yes.
527
Number of lines per inch

Height of the plot for 2-D lines

Use custom colormap?
Select Yes to use a colormap created with QCVIEW or DISPLAY.
Colormap
Fold corresponding to minimum contour

Fold corresponding to maximum contour

Plot side label ?

User comments
Change side label font appearance ?
Title character thickness (inches)
Title character size (inches)
Side label character thickness (inches)
Side label character size (inches)
528
FORTHPIK
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module FORTHPIK performs automatic picking of anisotropic non-hyperbolic fourth-order NMO
corrections. The corrections are an anisotropic approximation to the three-term NMO formula. The output
is an ETANMO matrix that can be used in other modules like NMOR, NMOA, and KTMIG to perform
non-hyperbolic NMO corrections. The module outputs in the SeisUP data flow as seismic traces, the
non-hyperbolic semblance for each CMP analyzed.
Cleaning up the CMP gathers as much as possible before running this module will help improve the
performance of the program.
The CMP must not have any NMO applied.
RMS velocities input should be velocities used for migration. (i.e. the best RMS velocities you can pick).
FX Decon on the NMO gathers
Trace mixing of the NMO gathers
Bandpass filter (i.e. 2-6-30-40). You may want to try without the filter first.
Small window AGC
The input to the module consists of data for which the moveout is to be approximated by the three-term
NMO formula:
t**2 = t0**2 + (x/v)**2 - 2*eps*(x/v)**2*(x/v)**2/(t0**2+(x/v)**2 + 2*eps*(x/v)**2)
eps = epsilon (ETA)
x = offset
v = NMO velocity
For layered media characterized by large vertical velocity gradients and/or velocity anisotropy, the
moveout behavior of reflected events may deviate from the usually assumed hyperbolic formula when the
offset to depth ratio exceeds 1.0. In order to flatten events in such media, it is necessary to specify
deviations from the familiar hyperbolic moveout. This module uses the simple fourth order formula shown
above to characterize these deviations from hyperbolic. The parameter eps (short for epsilon) is often
referred to as the anellipticity and in simple models is a measure of the amount of anisotropy present in the
529
overburden.
The recommended procedure for exploiting this three-term formalism is as follows. Briefly, it consists of
first estimating the hyperbolic approximation to the moveout by applying standard velocity analysis
procedures to the relatively short offset portion of the data. This velocity field is then used by this module
to facilitate the scanning and picking of the anellipticity parameter, epsilon (ETA), as a function of CMP
location and time.
The input velocities to the module should be the velocities used to migrate the data. The user can specify
two methods for velocity input: RMSVEL matrix or a VIP RMS velocity file. If the user selects a VIP file,
then an extract matrix must also be provided.
The ETA picks are put into a ETANMO matrix. The time increment of the ETANMO matrix is selected
by the user. The ETANMO matrix can be used in modules NMOR, NMOA, SMOOTH, and KTMIG. The
non-hyperbolic method chosen in these modules should be Anisotropic
The ETANMO matrix can output spreadsheets of ETA values at user specified extract locations. The
extract locations are built using a VABINS3D matrix. If the VIP interval velocity method is chosen, then
the user must specify a extract location matrix. If the RMSVEL matrix velocity method is chosen, then the
user may specify the extract matrix. If no extract matrix is chosen for the RMSVEL method, then the CMP
locations are taken from the RMSVEL matrix and applied to the output ETANMO matrix.
This module replaces the input GCI seismic traces with the semblance on output. It actually outputs the
number of etas produced plus 4.
Trace 1 : Semblance(t) for eps_min
Trace 2 : Semblance(t) for eps_min+eps_inc
....
Trace NEPS : Semblance(t) for eps_max
The last four traces provide information that may be used for QC purposes or (optimistically) for
automatic picking.
Trace NEPS+1 : Blank trace (for separation)
Trace NEPS+2 : Maximum semblance for each window
Trace NEPS+3 : Epsilon at maximum semblance for each window
Trace NEPS+4 : Screened value of epsilon. Based on the specified
minimum semblance, epsilon is picked only if the
semblance exceeds semb_min. For semblances less than
530
semb_min, the picked epsilon is set equal to -eps_max.
Input Channels
2. VIP interval velocity file: Optional connection from dataset SEGY data type.
Output Channels
1. GCI output: Required connection to next process GCI data type.
Parameters
Start of analysis window (ms)
This is the beginning time (in ms) for the three-term moveout analysis.
End of analysis window (ms)

This is the ending time (in ms) for the three-term moveout analysis.
Window length for analysis (ms)

This is the window length for the analysis in milliseconds. For each analysis window within the specified
start and end times, the anellipticity is scanned and the corresponding epsilon vs. time and epsilon is
written into the output traces.
Window increment for analysis (ms)

This is the window increment for the analysis. It is recommended that this be half the specified window
length.
Maximum stretch allowed (%)

This parameter specifies how much the input data is permitted to be stretched in the course of applying
the three-term moveout formula. Any portions of the data stretched more than this value will be
automatically muted.
531
Minimum ETA (%)

This is the minimum value (in percent) of the anellipticity parameter, epsilon (ETA), to scan. The default
is -10.
Maximum ETA (%)

This is the maximum value (in percent) of the anellipticity parameter to scan. The default is 10.
ETA increment (%)

This is the increment (in percent) of the anellipticity parameter to scan.
Minimum semblance (%) for picking

This is the minimum semblance (in percent) which is used for picking the screened value of epsilon
contained in the last trace output from this process.
Method to input velocities

The input velocities can be an RMSVEL matrix or a VIP RMS velocity file. The VIP file can be attached
to the module.
Options: RMSVEL Matrix, VIP Interval Velocity File
Input RMS velocities

Enter the RMSVEL velocity matrix that was used for NMO corrections.
Matrix Type: RMSVEL
Use VABIN3D matrix for extract locations?

The ETA values can be output at user specified line/bin locations using a VABIN3D matrix. If the input is
a VIP interval velocity file, then the extract matrix must be provided. If the velocity input is a RMSVEL
matrix and the user selects NO here, then the module will output the ETANMO line/bin locations at the
same locations as the RMSVEL matrix.
Desired extract locations

Enter the VABINS3D matrix file.
532
Output ETA (Epsilon) values

Enter a new ETANMO matrix to store the output ETA values. The CMP locations are the same as the
input RMSVEL velocity matrix.
Matrix Type: ETANMO
Time spacing between output ETA values (ms)

Enter the time spacing between output ETA values in milliseconds. The output ETANMO matrix will
have ETA values output at this time interval.
Compute ETA values at extraction locations only?

To speed up the module through the dataset, it will compute an ETA trace at the extraction locations only.
If you set this to NO, then the module will compute an ETA trace for every CMP in the dataset. The
extraction locations are taken either from the RMSVEL matrix locations or the VABINS3D matrix
locations, whatever method was chosen by the user.
533
FRACDET
Module Description
Input Channels
Output Channels
Parameters
Module Description
In a horizontally stratified isotropic homogeneous media, all the converted S-waves are collected in the
radial and vertical channels. In this way it is not necessarily the transverse component of a 3C data set.
Some authors (Justice et al., 1986; Martin et al., 1986, Thomson, 1988) have given evidence of different
kinds of velocity anisotropy in the ground. This can allow S-waves to split in two components, fast and
slow, when it goes through an anisotropic layer. This phenomena is called S-wave birefringence. A
vertically fractured media introduces anisotropy in the wave velocity, then when an S-wave goes through
it will split in two components. The fast one (S_parallel), is parallel to the fracture orientation, and the
slow one (S_perpendicular), is perpendicular to the fracture orientation. This situation is shown in the
following Figure:
When the birefringence phenomena appears, there are some problems to face in the seismic data:
For converted waves, the S-wave energy is recorded in both horizontal geophone components,
decreasing the signal to noise ratio in the radial component, making the interpretation more difficult.
Both split S-wave components, fast and slow, bring energy to the radial and transverse records,
making the interpretation more difficult.
These problems can be solved, to determine the natural fracture axis by horizontal (radial and transverse
component) record analysis.
534
FRACDET is a module to perform rotation analysis over 2D post-stack seismic data. There are two
methods, correlation and energy maximization, to perform this analysis. This module produces a table
with the rotation angle for each CCP. Furthermore, using the correlation method the time delay between
the split shear waves is determined, and it can be used to estimate the fracture density.
Correlation method: This method determines the natural fracture orientation and the time delay between
the polarized slow and fast S-waves. It is based in the cross correlation between the radial and transverse
channels. This method was developed by Harrison (1992).
It is necessary to pick the horizon of interest, using the horizon picking tool of the interactive DISPLAY
module, in which the selected time analysis window will go through doing the cross correlation among the
samples of the horizontal component. The HORIZON module will interpolate the picks, placing them in
the trace header.
The FRACDET module connection and the later exposed functionality is shown in the next figure, each
parameter will be discussed later on.
Energy maximization: Michelena (1995) developed a method which allow us to obtain the direction of
the natural fracture orientation and the magnitude of the anisotropy. It is based in the maximization of the
energy ratio of the horizontal rotated components. Suppose we have the rotated energies of the horizontal
components Ei and Ec, its ratio will be something like:
R(alpha, omega, theta, Delta t) = Ei / Ec.
This last equation will be undetermined when there is no energy in the transverse component (Ec), this can
occur under two circumstances. The first is related to the fact that the converted wave is traveling in an
isotropic media. The second can occur, in an anisotropic media, when the receiver line is parallel or
perpendicular to the anisotropic axis. This method has problems when the fractures are oriented 45
degrees from the receiver line. In the other hand, this method is faster than the correlation method,
therefore it is useful for a quick overview.
Using QCVIEW for fracture orientation analysis
535
QCVIEW, is an stand alone module for interactive geometry attribute Q.C. Choosing the Custom Pick, a
dialog will pop up when executing QCVIEW. This module was modified to save the results of the rotation
analysis as new geometry attributes. When FRACDET is run the tables which save the estimated angles
and time delays will appear in the MIDPOINT order at the dialog window, see picture.
This tool allows us to plot the behavior of the estimated fracture orientation angle versus a geometry
parameter. The estimated angles can be smoothed using the SMTHANG module and this new angle values
can be plotted again. In general it is necessary to smooth the estimated angles of fracture orientation to
avoid spikes.
References
Harrison, M. P., 1992, Processing of P-SV surface seismic data, anisotropy analysis, dip moveout and
migration: PhD thesis, University of Calgary.
Michelena, R. J., 1995, Quantifying errors in fracture orientation and density estimated from P-S
converted waves: submitted to Geophysics.
Input Channels
1. Radial horizontal component: Required connection from dataset GCI data type.
2. Transversal horizontal component: Required connection from dataset GCI data type.
536
Output Channels
Parameters
Method
Select the method to perform the rotation analysis, correlation or energy maximization as mentioned
before.
Options: Correlation, Energy maximization
Get time from

The values of the picked horizon using the horizon picking tool of the interactive DISPLAY module are
saved in a matrix table. The HORIZON module will interpolate the picks placing them in the trace header
(TIM1 or TIM2).
Options: TIM1, TIM2
Size of the window (ms)

This parameter defines the size of the time window. It is in milliseconds.
Maximum value for delta t (ms)

This parameter is needed to estimate the time delay between the split shear waves when they go through
an anisotropic media. It is needed only when the correlation method is used.
Rotation angle attribute name

This is the name of the matrix which will save the estimated angles for each CCP. This will be a matrix of
MLIN (Mid point line number) dimensions, and for each MLIN there is a vector which will save the
calculated angles.
Matrix Type: PSROTANG
Time delay attribute name

This is the name of the matrix which will save the time delay between split shear waves generated when
they go through an anisotropic media. It is needed only when the correlation method is used.
537
Matrix Type: SVSHTSHIFT
Number of MBINs.
First MBIN
Number of MLINs.
First MLIN
538
FREQTUNE
Module Description
Input Channels
Output Channels
Parameters
Module Description
The FREQTUNE module uses spectral decomposition to image and map temporal bed thickness and
geologic discontinuities over large seismic surveys. A short window is centered over a specific time
sample or horizon and this zone is transformed to the frequency domain. The resulting spectra can be
viewed in cross-section or plan view. At dominate frequencies, the signal-to-noise ratio is high and results
in clear pictures of thin-bed tuning.
Spectral decomposition provides a novel means of utilizing seismic data and the discrete Fourier transform
to image and map seismic stratigraphic features. By transforming the seismic data into the frequency
domain via a maximum entropy spectral analysis, the amplitude spectra delineates temporal bed thickness
variability such as channel sands and complex fault systems. The concept behind spectral decomposition is
that a reflection from a thin bed has a characteristic expression in the frequency domain that is indicative
of the temporal bed thickness.
The difference in frequency response between a long-window and a short-window amplitude spectrum is
significant. The transform from a long trace approximates the spectrum of the wavelet, but the transform
from a short trace comprises a wavelet overprint and a local interference pattern representing the acoustic
properties and thickness of the geologic layers spanned by the window. The shorter the window, the less
random the sampled geology. In small windows, the geology acts a local filter on the reflecting wavelet,
thereby attenuating its spectrum. The resulting amplitude spectrum is not white and represents the
interference pattern within the window.
The most common approach to characterize thin beds using spectral decomposition is to use the "zone of
interest" method. The user starts by mapping a horizon or selecting a specific time. A short window
(100ms) around this zone is transformed from the time domain to the frequency domain. The resulting
"spectra cube" can be viewed in cross-section or plan view (common frequency slices). The frequency
slice is typically more useful because it allows the user to visualize thin-bed interference patterns in plan
view. Amplitude versus frequency behavior/tuning can be expressed by animating through the entire
frequency range.
In frequency-slice form, thin bed interference appears as coherent amplitude variations. Random noise
speckles the interference pattern. At dominate frequencies, the high signal-to-noise ratio (SNR) results in
clear pictures of thin-bed tuning. Away from the dominant frequencies causes the SNR to degrade
resulting in a noise map.
539
The module uses a maximum entropy power spectra method to estimate the amplitude spectra at each
frequency. This method is more stable in short windows than a discreet Fourier transform (DFT).
The module will analyze the data using two methods: Volume and Horizon. In the volume method, the
user enters a start and stop time. Typically, one sample is used (i.e. start=1000ms, end=1000ms). The
analysis takes place over the window with the chosen sample in the center. In the horizon method, a
HORIZON matrix is specified. The HORIZON matrix is typically built in the DISPLAY module and
tracks one specific seismic event. At each trace, the HORIZON sample is analyzed over the window with
the sample in the center of the window.
The module has two types of output: Frequency slices, Maximum amplitude frequency. In the frequency
slice method, each sample is analyzed over the window. The output is the amplitude at each frequency
selected. Example: The user selects a start/end time that corresponds to one sample. If the user chooses 0
to 70 hertz as the frequency range, the module will output 70 amplitudes, one for each frequency. If more
than one sample is analyzed then the module will output 70 amplitudes * number of samples. In the
maximum amplitude frequency method, the maximum amplitude is found and the frequency
corresponding to that amplitude is output.
References
G. Partyka, J. Gridley, J. Lopez, Interpretational applications of spectral decomposition in reservoir
characterization. The Leading Edge, March, 1999.
G. Partyka, L. Peyton, R. Bottjer, Interpretation of incised valleys using new 3D seismic techniques: A
case history using spectral decomposition and coherency. The Leading Edge, September, 1998.
Input Channels
Output Channels
Parameters
Lowest frequency of interest (Hz)
Enter the lowest frequency of interest in hertz. This frequency should be below the dominant frequencies
expected in the seismic data.
540
Highest frequency of interest (Hz)

Enter the highest frequency of interest in hertz. This frequency should be above the dominant frequencies
expected in the seismic data.
Number of poles in maximum entropy approximation

The maximum entropy computation scales as the product of N (number of data points) and M (the number
of poles). In practice, one wants to limit the number of poles to a few times the number of sharp spectral
features that one desires. While exact values depend on the application, one might take M=10, 20, or 50
for N=1000 or 10000. The larger number of poles will increase the computation time. If the number of
poles or the number of data points is too large, round-off error can be a problem.
Window length of data for spectral calculation (ms)

Specify the window length for the spectral computation in milliseconds. A short window is desired to
reduce the randomness of the geology. But a window too short will cause the maximum entropy
calculation to output poor values. Typical window ranges might be 60 to 150 ms.
Method of frequency tuning

Two methods are supplied for computation. In the "volume" method, a start and end time are entered. The
spectral computation is computed at each sample over the entire frequency range. Typically, the user will
choose one sample (example: start time=1000ms, end time=1000ms) In the "horizon" method, the user
enters a HORIZON matrix that was previously picked. This horizon is typically chosen over a specific
seismic event. The spectral computation is computed at the specified sample using the window over the
entire frequency range.
Options: Volume, Horizon
Start time (ms)

If the "volume" method was selected above, enter the start time in milliseconds.
End time (ms)

If the "volume" method was selected above, enter the end time in milliseconds.
Header to add to times

Optionally a time may be added to the start/end time. Enter the GCI header word that contains the time to
add.
541
Primary header key

If the "horizon" method was chosen, then a HORIZON matrix must be input. Enter the primary key of the
HORIZON matrix.
TLSN

If the "horizon" method was chosen, then a HORIZON matrix must be input. Enter the secondary key of
the HORIZON matrix.
TLSN
Time horizon
If the "horizon" method was chosen, then a HORIZON matrix must be input.
Output method
Two output methods are supplied. In the frequency slice method, an amplitude for each frequency is
output at each sample. Example: the user chooses 0 to 70 hertz over a time window start=1000ms to
end=1002ms. The output would be 140 amplitudes, 70 for each frequency at the first sample and 70 for
each frequency at the second sample.
In the maximum amplitude frequency method, the maximum amplitude value in the spectra is located at
each sample and the corresponding frequency value is output.
Options: Frequency Slices, Maximum Amplitude Frequency
542
FRFSTPRP
Module Description
Input Channels
Output Channels
Parameters
Module Description
FRFSTPRP performs the same preparation step for REFST as REFSTPRP, but reads shot geometry from a
shot ordered dataset. When using FRFSTPRP after a READ in a flow, the primary READ key should be
NONE, the secondary READ key should be SSPN and the ensemble READ key should be FCSN.
FRFSTPRP outputs a binary file needed by REFST.
Input Channels
Output Channels
2. Rfstout: Required connection to dataset RAS3D1 data type.
Parameters
Survey type?
Survey types are either 2D, 3D or OBC.
Options: 2D, 3D, OBC
First Break Times Matrix

Use the matrix editor to select the desired first break time matrix.
Matrix Type: AFS1B
543
Maximum offset for analysis (ft or m)

Enter the maximum offset of interest. First break time picks from traces with offsets greater than this value
will not be loaded.
Maximum channels per shot to use

Enter the maximum number of channels per shot.
544
FXDN
Module Description
Input Channels
Output Channels
Parameters
Module Description
FXDN suppresses random noise by using "F-X" deconvolution. First the seismic traces are transformed
into the frequency domain. For each frequency, assume a trace can be predicted by using a linear
combination of several traces in front of and behind this trace. This kind of filter is computed based on a
user-specified derivation window and using a complex Wiener-Levinson linear prediction algorithm. The
random noise will be filtered out because of its non-predictability.
Input Channels
Output Channels
Parameters
C
A
B
D
:_________________________:_____________:_____________:
^
current trace
C-D Derivation window
A-B Filter length
Derivation window (traces)

Derivation window specifies the number of traces from C to D. A unique filter is obtained for each
frequency on this window using the least-squares error Wiener-Levinson algorithm. A new filter is
computed for the next window. Generally, if the events are relatively linear, a larger window is more
powerful in suppressing the random noise, especially for stack data. If the data contains many faults or are
severely structured, a narrower window should usually be used. Otherwise, the output could be smeared.
545
If the input ensemble is smaller than the derivation window, the ensemble size will be used.
Filter length (traces)

Filter length is from A to B in the above diagram. Filter length specifies the number of traces used in
computing the current trace. This number is an even number and symmetrically distributed on each side of
a trace. If an odd number is specified, it will be forced to be the next lower even number. This number is
defaulted to 4 for relatively flat data. Usually, this is sufficient. A larger number will have a larger
smearing effect as well as a noise reduction effect. A longer filter also slows down the execution.
Temporal window (# of samples)

This specifies the number of samples (power of 2) to use in the Fourier transform. The number is always
rounded up to the next power of 2.
Temporal window overlap (%)

High cut Frequency (Hz)
Stack back percentage
This specifies the percentage of the input data to be added back into the output. This is sometimes
desirable to make the output more like the input.
To restore mute?
This switch tells the program if the mute is to be restored.
Perturbation (%*100)
To ensure the matrix solution is stable, a perturbation or white-noise term is needed. This number is
defaulted to 100 (i.e. 0.01%). For most data, this number works. However, if there are unreasonably high
amplitudes in the output but not in the input, this number needs to be increased.
546
FXYDMIG
Module Description
Input Channels
Output Channels
Parameters
Module Description
FXYDMIG is a 3D poststack one-pass frequency domain depth migration module. The migration is based
on the finite difference algorithm which solves the acoustic wave equation in the space-frequency domain.
FXYDMIG can accurately handle dips up to 65 degrees; but, in practice, it can be used to migrate dips up
to 80 degrees.
FXYDMIG can handle all types of velocity variations.
The sample interval on the output is set to 1000 times the depth interval and the number of samples is reset
to the number of depth samples. In normal seismic data the sample interval is in microseconds.
Input Channels
2. VIP dataset: Optional connection from dataset SEGY data type.
Output Channels
2. FXYDMIG-saved dataset: Required connection to dataset FXYDSV data type.
Parameters
Max. dip
Options: 45 degrees, 65 degrees

Matrix Type: FXYFREQ
547
Min. interval velocity

Max. interval velocity
Depth sampling interval(m or ft)
This is equivalent to the sampling interval in the time domain. A good estimate is to use the average
velocity times half of the sampling interval. e.g. 2500 m/s at 4ms will give 0.004*2500/2 = 5 m. Too large
a depth sampling interval will cause aliasing problems. A depth sampling interval that is too small will
waste resources.
Depth step for operator derivation(m or ft)

This is a speed up factor. It specifies how often the velocity dependent part of the operator is derived. The
price for this acceleration is a loss of accuracy in the velocity field. An upper limit of 20 times the depth
sampling interval is set to avoid skipping large velocity variations.
Maximum depth to output(m or ft)

Bin or CMP interval
Line interval
Inline padding (traces)
This is the number of zero traces to pad to both sides of the inline bins. Decreasing this parameter will
result in a faster execution time but data at the ends of the section will bounce back into the section.
Increasing this parameter will increase execution time and could avoid artifacts on the side of the section.
548
Crossline padding (traces)

This is the number of zero traces to pad to both sides of the crossline lines. Decreasing this parameter will
If only one line is being migrated, only a 2-D migration will be used thus no crossline pad is needed.

This parameter multiplied by the record length will be used to determine the time direction FFT. Numbers
greater than 100% will result in more zeros padded beyond the record length. This number should be high
enough to avoid wrap around effects at the end of the section. The greater the number the longer the
execution time.
Cross-line side taper at start time(# of traces)

Cross-line side taper at end time(# of traces)
In-line side taper at start time(# of traces)
In-line side taper at end time(# of traces)
RMS velocities
Matrix Type: RMSVEL
Number of processors
Restore mute?
Make up missing traces?
Dispersion control?
The default values for the next four parameters are sufficient most of the time. The theta values influence
stability and accuracy. Larger gamma values give rise to cleaner impulse responses, but may cause phase
distortions for steep dips. With the default gamma, the impulse response may look noisy inside the smile,
but tests show that this noise cancels out when stacked along events.
549
Inline theta
Required if Dispersion control? = Yes.
Inline gamma
Crossline theta
Crossline gamma
550
FXYDN
Module Description
Input Channels
Output Channels
Parameters
Module Description
FXYDN suppresses random noise by using "F-X-Y" deconvolution. First the seismic traces are
transformed into the frequency domain. For each frequency, assume a trace can be predicted by using a
linear combination of traces in the surrounding area. This areal filter is computed based on a user-specified
areal derivation window and uses a complex Wiener-Levinson linear prediction algorithm. The random
noise will be filtered out because of its non-predictability.
Generally, if the events are relatively planar, a larger window is more powerful in suppressing random
noise. If the data contain many faults or severe structures, a smaller window should be used.
The filter specifies the number of traces to use in computing the current trace. The current trace is centered
in the areal filter. A larger areal window will have a larger smearing effect as well as a stronger
noise-reduction effect. In addition, a larger areal filter slows down the execution.
Input Channels
Output Channels
Parameters
Inline derivation window (bins)
Crossline derivation window (lines)
551
Inline filter length (bins)

Crossline filter length (lines)
Temporal window (# of samples)
Temporal window overlap (%)
High cut Frequency (Hz)
Stack back percentage
To restore mute?
Perturbation (%*100)
552
FXYMIG
Module Description
Input Channels
Output Channels
Parameters
Module Description
FXYMIG is a 3D poststack one-pass frequency domain migration. The migration is based on the finite
difference algorithm which solves the acoustic wave equation in the space-frequency domain. FXYMIG
can accurately handle dips up to 65 degrees; but, in practice, it can be used to migrate dips up to 80
degrees.
FXYMIG can handle all types of velocity variations.
FXYMIG can optionally save the partial result. The partial result can be picked up by FXYMIGR to
continue the process if the process is aborted or the system crashed. There may be small errors in the step
zone where the termination occurred.
Input Channels
2. VIP dataset: Optional connection from dataset SEGY data type.
Output Channels
2. Fxymig-saved dataset: Required connection to dataset FXYSAV data type.
Parameters
Max. dip
Options: 45 degrees, 65 degrees
553

Matrix Type: FXYFREQ

Depth step (micro seconds)
Bin or CMP interval
This is the distance between two adjacent midpoint bins.
Line interval
This is the distance between to adjacent midpoint lines.

This is the number of zero traces to pad to both sides of the inline bins. Decreasing this parameter will
However, a larger pad can produce a section with edge artifacts because the migration impulse response
from a smaller pad bounces back into the section and helps cancel the impulse response from the interior
of the section. This could lead to an incorrectly imaged section at the sides of the section.

This is the number of zero traces to pad to both sides of the crossline lines. Decreasing this parameter will
If only one line is being migrated, only a 2-D migration will be used thus no crossline pad is needed.
However, a larger pad can produce a section with edge artifacts because the migration impulse response
554
from a smaller pad bounces back into the section and helps cancel the impulse response from the interior
of the section. This could lead to an incorrectly imaged section at the sides of the section.

execution time.
Cross-line side taper at start time(# of traces)

Cross-line side taper at end time(# of traces)
In-line side taper at start time(# of traces)
In-line side taper at end time(# of traces)
RMS velocities
Matrix Type: RMSVEL
Restore mute?
Dispersion control?
These default values for the next four parameters are sufficient most of the time. The theta values
influence stability and accuracy. Larger gamma values gives rise to cleaner impulse responses, but may
cause phase distortions for steep dips. With the default gamma, the impulse response may look noisy
inside the smile, but tests show that these noises cancel out when stacked along events.
555
Inline theta
Inline gamma
Crossline theta
Crossline gamma
556
FXYMIGEX
Module Description
Input Channels
Output Channels
Module Description
FXYMIGEX extracts the migrated portion of the data up to the current step. The unmigrated data will be
zeroes following the extracted output. FXYMIGEX can be applied any time once the migration starts.
Input Channels
1. Input: Required connection from dataset FXYSAV data type.
Output Channels
557
FXYMIGR
Module Description
Input Channels
Output Channels
Module Description
Restart one-pass FXY migration module FXYMIG.
Input Channels
1. Input: Required connection from dataset FXYSAV data type.
Output Channels
558
GAIN
Module Description
Input Channels
Output Channels
Parameters
Module Description
GAIN applies gain or amplitude recovery curves. GAIN accepts gain curves for multiple offsets and
CMPs. It then interpolates these curves to derive the curve for each particular trace. The form of this
interpolation is to compute the inverse curves, then linearly interpolate the inverse curves to derive the
inverse curve for the current trace. Options include following the water bottom or other structures, if times
are defined in the trace header by the process HORIZON as TIM1 or TIM2.
Input Channels
Output Channels
Parameters
Reference mean
Undo previous gain?
Header to shift functions
Primary header key

TLSN
559

TLSN
Gain curves
Matrix Type: GAIN
560
GAMLSEIS Maximum Likelihood Clustering

Module Description
Input Channels
Output Channels
Parameters
Module Description
The GAMLSEIS module clusters seismic attributes using the Geologic Analysis via Maximum Likelihood
System method. The clusters are separated into modes using a model-based, maximum likelihood system
wherein each sample is assigned to each mode with a fractional probability (mode probability assignment).
Therefore, samples are assigned to clusters that have similar seismic properties.
The mathematical term for a cluster is a mode. When analyzing seismic data, the term cluster or
mode might be considered equivalent to seismic rock type. GAMLSEIS defines mode distributions
assuming that each has a Gaussian distribution. The clustering process groups all seismic samples into
modes each of which has a similar seismic characteristic. Typically, for seismic data, 10 to 25 modes will
be selected.
The goal of clustering is to group samples into modes, which are distinct from one another as much as
possible. The degree of distinction of one mode to another is proportional to the degree of its isolation
when located in n-space (where n is the number of different seismic trace types used). The degree of
isolation will vary somewhat with the number of modes used. This degree of isolation is measured for
each solution by a computation of the entropy of the system. For distinct modes, the maximum entropy
(Em) possible is equal to the natural logarithm of the number of modes present. For modes that overlap in
n-space, the solution entropy (Es) will be somewhat less than the Em, and the difference between Es and
Em will generally increase with the degree of overlap among the modes.
During clustering, the probability of each seismic sample belonging to each mode is computed. At each
time sample, the sum of the probabilities of all modes equals one. A probability of one for a given mode
means that a seismic sample uniquely is assigned to that mode. It is not uncommon for the probabilities at
a given time are distributed among two or more modes, indicating that that time sample has characteristics
that overlap among modes. The assignment of probability is a measure of how perfectly a time sample fits
into a given mode is referred to as a fuzzy mode probability assignment. In the parlance of fuzzy logic,
fuzzy is also referred to as crisp. A crisp assignment is a yes versus no, or a 1 versus a 0. A fuzzy
assignment invokes a probability of fit. The probabilities are numerical values between 0.0 and 1.0
assigned to each time sample. During clustering, convergence is achieved when the probability change
between the last iteration and the next is less than 10e-3.
The AIC likelihood is the likelihood corrected for the number of free parameters (Akaikes information
Criterion (Akaike, 1973)). During clustering, the likelihood generally increases monotonically with the
iteration number and eventually reaches a plateau as the solution converges.
561
Highly correlated data can cause the clustering routine to become unstable. In this case the program will
abort. To attempt to stop the routine from aborting in case highly correlated data must be used several
methods are employed. If the correlation coefficient between two attributes is larger than a maximum
specified, the module will add random noise to the dataset. The amount of random noise is specified using
a signal-to-noise ratio. If the clustering is still aborting after adding random noise, the user may also
specify a correlation threshold. This will force the normalized covariance matrix to a maximum value. The
result cannot be considered totally valid if you change the correlation threshold.
The module allows the use of a start and stop time during clustering. This allows you to setup a window of
data to cluster. The user can also use the header words TIM1 and TIM2 to add addition time to the start
time. This should allow the user to track dipping events, because the start time will vary upon the
TIM1/TIM2 header word. Using a window of time will allow the cluster to complete quicker than using
the whole dataset. It also allows the user to specify time zones that might be specific to geological zones
of interest.
The module will not allow zero or dead-zones in the data. The dataset is check for start and end mutes. If
the data is zeroed below the start time, then the start time is adjusted downward. If a zero-zone is detected
above the end time, then the end time is adjusted upward.
The module will output up to three different datasets: Crisp Mode Assignment, Crisp Mode Probability,
and the Mode Probability. The Crisp Mode Assignment will output the mode number for each time sample
that had the greatest probability value. The Crisp Mode Probability output will be the probability value at
that mode. The Mode Probability plot will output probability values at a user-selected mode.
References
Akaike, H., 1973, Information theory and an extension of the maximum likelihood principle, in Petrov and
Csaki (eds.), Proceedings of the Second International Symposium on Information Theory: Akademai
Kido, Budapesht.
Burdick, B. J., 1997, Nichols Research Corporation, personal communication.
Cramer, H., 1963, Mathematical Methods of Statistics: Princeton, Princeton University Press.
Doveton, J. H., 1994, Geologic Log Analysis Using Computer Methods: Tulsa, The American Association
of Petroleum Geologists, 169 p.
Fisher, R. A., 1936, The use of multiple measurements in taxonomic problems: Annals of Eugenics, v.
VII, part II, p. 179-188.
Fukunaga, K., 1990, Introduction to Statistical Pattern Recognition (second edition): Boston, Academic
Press, Inc., 591 p.
Garvin, L. C., Nichols Research Corporation, personal communication, 1994.
562
Garvin, L. C., and Perlovsky, L. I., 1994, Statistical Pattern Recognition and Quantum Statistical Physics:
Current Topics in Pattern Recognition Research, v. 1, p. 237-250.
McCormack, M. D., 1991, Neural computing in geophysics: Geophysics: The Leading Edge of
Exploration, January, p. 11-15.
McNeil, D., and Freiberger, P., 1993, Fuzzy Logic: New York, Simon & Schuster, 319 p.
Mohaghegh, S., and Ameri, S., 1996, Virtual measurement of heterogeneous formation permeability using
geophysical well log responses: The Log Analyst, March-April, p. 32-39.
Moline, G. R., Bahr, J. M., Drzewiecki, P. A., and Shepherd, L. D., 1992, Identification and
characterization of pressure seals through the use of wireline logs: A multivariate statistical approach: The
Log Analyst, v. 33, no. 4 (July-August), p. 362-372.
Perlovsky, L. I., 1988, Cramer-Rao bounds for the estimation of means in a clustering problem: Pattern
Recognition Letters, v. 8, p. 1-3.
Perlovsky, L. I., 1989, Cramer-Rao bounds for the estimation of normal mixtures: Pattern Recognition
Letters, v. 10, p. 141-148.
Perlovsky, L. I., 1992, Maximum likelihood adaptive neural system application to nontraditional signal
classification, 3 rd Annual Office of the Naval Technology Full Spectrum Review, Proceedings, 1, p.
121-146, NUWC, New London, CT.
Perlovsky, L. I., 1994a, Computational concepts in classification: Neural Networks, Statistical Pattern
Recognition, and Model Based Vision: Journal of Mathematical Imaging and Vision, v. 4 (1), p. 81-110.
Perlovsky, L. I., 1994b, A model based neural network for transient signal processing: Neural Networks,
v. 7 (3), p. 565-572.
Perlovsky, L. I., and McManus, M. M., 1991, Maximum likelihood neural networks for sensor fusion and
adaptive classification: Neural Networks, v. 4, p. 89-102.
Perlovsky, L. I., and Marzetta, T. L., 1992, Estimating a covariance matrix from incomplete independent
realizations of a random vector: IEEE Transactions on SP, v. 40, no. 8, p. 2097-2100.
Press, W. H., Flannery, B. P., Teukolsky, S. A., and Vetterling, W. T., 1990, Modeling of Data, in
Numerical Recipes - The Art of Scientific Computing, Chapter 14, p. 498: New York, Cambridge
University Press.
Rogers, S. J., Chen, H. C., Kopaska-Merkel, C. C., and Fang, J.H., 1995, Predicting permeability from
porosity using artificial neural networks: AAPG Bulletin, v. 79, no. 12, p. 1786-1797.
Rogers, S. J., Fang, J. H., Karr, C. L., and Stanley, D. A., 1992, Determination of lithology from WELL
LOGS using a neural network: AAPG Bulletin, v. 76, no. 5, p. 731-739.
563
Shannon, C. E., and Weaver, W., 1959, The mathematical theory of communications: Urbana, Illinois
University Press.
TYPE
Stand Alone
Input Channels
1. Input: Required GCI data type.
Output Channels
1. Output1: Required GCI data type.
2. Output2: Optional GCI data type.
3. Output3: Optional GCI data type.
PARAMETERS
Parallel execution mode:
Default .....:None
Name ........:pmeth
Options .....:
None
Cluster
Number of nodes in the cluster

If the cluster mode is selected above then this parameter appears.
Default .....:2
Name ........:nnode
Min .........:1
Max .........:
564
Compute node list

This parameter provides the option of choosing the Compute node list. This parameter is only available
when running on a cluster. If there are more than one cluster, then they will be available in this list. This
list should be set up by the System Administrator.
Default .....:"Name of clusters"
Name ........:nodes
Type ........:Custom list

This parameter is used to specify a specific list of sub-nodes, from the Compute node list to be used to run
the migration on. This parameter is only available when running on a cluster. If the Compute node list has
many nodes, say 100 nodes named n1, n2, .. n100. If you wanted to run GAMLSEIS on 25 nodes, and
specifically nodes n26 to n50, you would enter 26 to 50 for the values of CPU index in the subnode
matrix. Also if you enter values 11 to 20, then the node listed 11 in the Compute node list, to the node
listed 20 in the Compute node list are used to run the migration on. Therefore it is the order of listing in the
Compute node list which determines which specific nodes of the cluster this job will be run on. This
parameter is useful if you plan to run several jobs on this cluster, and want them to run on different nodes.
Path to directory for node data storage

This is for local disk storage on the cluster node.
Default .....:/tmp
Name ........:path
Method to store temporary data

Default .....:Memory
Name ........:mem
Options .....:
Memory
File
Random number generator seed

If the Large Covariance method is selected above then this parameter appears. Enter a seed value for the
random number generator.
565
Default .....:12345
Name ........:seed
Min .........:1
Max .........:32767
Scalar (0.05 - 2.0)

If the Large Covariance method is selected above then this parameter appears. Enter a scale to perturb the
initial mode values. The larger the scale value, the larger the initial perturbation.
Default .....:1.0
Name ........:scal
Type ........:Float
Min .........:0.01
Max .........:2.0
Specify channels (attributes) to input

Matrix Type: DMUX
Number of modes
Select the number of modes to compute during clustering. Typically, this will be between 10 and 25
modes. For practical purposes, mode is to be considered a seismic rock type. So the number of modes
must be at least as big as the number of seismic rock times contained within the window.
Default .....:10
Name ........:mode
Min .........:2
Max .........:
Maximum number of iterations

Specify the maximum number of iterations to run on the data. If the data converges before this maximum,
the program will quit iterating and output the results. If the data has not converged, then the program will
end anyway and output results achieved at the maximum iteration. Typically, seismic data will need 50 to
500 iterations to converge. Many times though, the data is fairly close to the final result at 20 percent of
the iterations needed to converge.
Default .....:100
Name ........:iter
Min .........:1
566
Max .........:
Convergence goal
The module will quit clustering successfully when the convergence goal is met. The convergence is
defined to be when the greatest change in the mode probability assignment for all samples from
consecutive iterations is less than the specified value. Example < .0.001.
Default .....:0.001
Name ........:goal
Type ........:Float
Min .........:0.0000001
Max .........:10.0
RMS level of the data

Specify the maximum average RMS to apply to the data. Seismic data attributes with very high amplitudes
might cause the program to abort during mean value calculations. This parameters allow you to set the
average RMS of the data to this value. If the average RMS of the data is lower than this value, then
nothing is done. If the average RMS of the data is larger than this value, then the data is scaled to the
specified average RMS.
Default .....:2500.0
Name ........:rms
Type ........:Float
Min .........:1.0
Max .........:
Near-unity correlation threshold

This value can be used to keep the module running when using highly correlated attributes. This value
forces the normalized covariance to the specified value. By lowering the default value, the normalized
covariance between two attributes is reduced. This can help keep the clustering stable at the expense of
having result that might not be valid.
Default .....:0.9999
Name ........:thrs
Type ........:Float
Min .........:0.1000
Max .........:0.9999
567
Correlation coefficient to represent highly correlated data

The correlation coefficient between all attributes is measured. If the coefficient is greater than this value
then random noise will be added to the dataset. This may help when using highly correlated data, which
can cause the program to abort. Use this technique first, (before altering the correlation threshold), when
running with highly correlated data. The module status file will give you information as to which attributes
are highly correlation, by printing out the bad correlation coefficients as they are measured.
Default .....:0.97
Name ........:coef
Type ........:Float
Min .........:0.0
Max .........:1.0
Highly correlated data recovery method

Select the module response when highly correlated data is found. The default is to abort the module. You
may also add random noise to the dataset.
Default .....:Add random noise
Name ........:corr
Options .....:
Abort program
Add random noise
Signal to noise ratio

If the module is adding random noise to a highly correlated dataset. Then specify the signal-to-noise ratio
to use for the random noise generator. A smaller value adds more noise to the dataset.
Default .....:30.0
Name ........:snr
Type ........:Float
Min .........:1.0
Max .........:1000.0
Min. midpoint line number:

To select a subset of a 2-D or 3-D volume, enter the minimum line number to use from the dataset.
Default .....:"Get All"
Name ........:ybmin
Min .........:
568
Max .........:
Max. midpoint line number:

To select a subset of a 2-D or 3-D volume, enter the maximum line number to use from the dataset.
Name ........:ybmax
Min .........:
Max .........:
Min. midpoint bin number:

To select a subset of a 2-D or 3-D volume, enter the minimum bin number to use from the dataset.
Name ........:xbmin
Min .........:
Max .........:
Max. midpoint bin number:

To select a subset of a 2-D or 3-D volume, enter the maximum bin number to use from the dataset.
Name ........:xbmax
Min .........:
Max .........:
Start time (ms.)

To select a subset of the seismic time volume, enter the start time in milliseconds.
Default .....:0
Name ........:dstrt
Min .........:0
Max .........:
569
End time (ms.)

To select a subset of the seismic time volume, enter the end time in milliseconds.
Default .....:"Record length"
Name ........:dend
Min .........:0
Max .........:

The trace header values TIM1 and TIM2 can be added to the start time. This allows the user to track
dipping events or seismic rock types.
Default .....:NONE
Name ........:inds
Options .....:
NONE
TIM1
TIM2
Output Crisp Mode Assignment dataset?

Select YES to output the Crisp mode assignment number for each time sample. The Crisp mode
assignment will be the mode number that has the greatest probability value. Example: Clustered using 5
modes. At time sample 100, the probabilities at each mode for a seismic location are: 1=0.01, 2=0.2,
3=0.7, 4=0.1, 5=0.09. The module will output the value 3, because mode 3 has the greatest probability.
Default .....:Yes
Name ........:plot1
Options .....:
Yes
No
Output Crisp Mode Probability dataset?

Select YES to output the Crisp Mode Probability for each time sample. The Crisp mode probability will
be the greatest probability value for a time sample. In the above example, the module will output value =
0.7, which is the largest probability of the 5 modes.
570
Default .....:No
Name ........:plot2
Options .....:
Yes
No
Output Mode Probability dataset?

Select YES to output the probability values at a user selected mode. In the above example, if the user
selected mode 4, then the module will output value = 0.1.
Default .....:No
Name ........:plot3
Options .....:
Yes
No
Mode Number
Select the mode number to use for the above output dataset. The mode number must be less than or equal
to the number of modes defined for the clustering run.
Default .....:1
Name ........:pmode
Min .........:1
Max .........:
AUTHOR
Created on July 20, 2001 by Steve Jensen
571
GCHG2D
Module Description
Input Channels
Output Channels
Parameters
Module Description
GCHG2D (Geometry Change for 2D data) is an interactive source matrix view and update program.
Connect GCHG2D to a raw or amplitude prepared shot record dataset with geometry applied. Upon
execution, three graphics windows appear. The first is a shot record display with three shots plotted
vertically. The second is the row from the source matrix that describes the shot and geophone locations of
the middle shot (OIDN annotated in red). The third window is a map view showing the locations of the
three shots, i.e., shots and nearest stations. This program allows the user to change shot and/or geophone
positions and see the update immediately for QC, before committing the changes.
Shot Display
The right side of the shot display has control buttons to adjust the size, amplitude, clip, LMO and bulk
shift on the three shots. The first thing to try is to select the "Display" button to adjust these parameters.
Each parameter is controlled by a slider. The objective is to adjust each parameter such that geophone
alignment patterns are observable for each shot. Typically that means decreasing the BULK shift and
Trace time, increasing the Trace spacing and varying the LMO velocity. The mouse pointer drags a red
line across all shots for visual alignment. Sometimes it is possible to see misplaced shots or geophone
cable errors with this display. To change the middle OIDN in the shot display use the red arrow buttons at
the top right of the shot window. Also the OIDN data in the matrix row window will update as well as the
map window. Another way to change OIDN is to place the mouse pointer in the shot window and hit the
"n" key for next or the "b" key for back. Hold the keys down for continuous change.
Move SHOT
To change the SHOT station number for the middle shot just click in the "Shot stn" text area of the matrix
row window and type in the new station number. The "Try" button on the right of the shot window will
change color to yellow. Click on the yellow "Try" button and the shot window will update with the new
shot location. Also the map window will show the new location of the shot (Red OIDN number). If this
change is not what you wanted, just re-type the old "Shot stn" back into the matrix window and click
"Try" again.
Move Cable
To change the cable stations for the center shot edit the "first geo", "Pre gap", "Post gap" and "Last geo"
entries and click the yellow "Try" button. The changes will be shown on the middle shot. If the changes
are not what you want click the blue "Re-Set Cable" button immediately.
572
Select
To jump to an OIDN of choice click the "Select" button and type in the OIDN number. Click OK and the
shot window will update with the desired OIDN as the center shot.
Save
Click the "Save" button to output a complete source matrix with shot and cable changes made so far.
Map Display
The map window initially shows three shots (2 black stars and 1 red star except at start and end of line)
with their OIDN annotations and surrounding SGENs (station locations and IDs). The middle shot
annotated in red is the editable shot in the shot window. With the two top buttons on the upper right the
user may increase or decrease the number of shots annotated. The "Move SHOT" button allows the user to
then click on the red shot and move its position on the map. While the shot is moving the middle shot in
the shot display is being updated with new offsets and shot position. When a final new position is selected
the user clicks once again to anchor the shot. If the user wishes to retain this new position click the KEEP
button. The matrix row "Shot stn" and "skid" and "perp dist" will be updated.
Input Channels
Output Channels
Parameters
Original Source
Copy the original source matrix (type SRCRECSPD2) and rename. This will be the input matrix to
GCHG2D.
Matrix Type: SRCRECSPD2
Updated Source
Type a new output matrix name for source parameter updates.
573

574
GEOM
Module Description
Input Channels
Output Channels
Parameters
Module Description
GEOM is used to apply the geometry database to the trace headers. GEOM will read a shot id from the
trace header and match the geometry database with the id. If the id is not found in the database, GEOM
will print a message and drop the shot. GEOM is best run as one of the first steps after reading field data.
GEOM will update the following trace headers:
HEADER
-----1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28
29.
30.
31.
NAME
---Sequential midpoint number
Shot to group distance
Receiver group elevation
Surface elevation at source
Source depth below surface
Elevation & depth scale factor
Coordinate scale factor
Shot X coordinate
Shot Y coordinate
Group X coordinate
Group Y coordinate
Uphole time at source
Shot bin number
Shot line number
Midpoint station bin number
Midpoint station line number
Source station bin number
Source station line number
Receiver station bin number
Receiver station line number
Midpoint bin number
Sequential geophone number
Sequential shot point number
Midpoint cell center X coordinate
Midpoint cell center Y coordinate
Field shot point number
CMP surface elevation
Azimuth between the source and
receiver
575
SDPN
DIST
EG
ES
DEPS
SX
SY
GX
GY
UTS
MSFL
MEFL
SBIN
SLIN
MSBN
MSLN
SSBN
SSLN
RSBN
RSLN
MBIN
MLIN
SGEN
SSPN
MCX
MCY
FSPN
EC
AZIM
For 3-D data, if the shot matrix name is in the header and GEOM cannot find the name in the database the
following message will appear at the job monitor:
Cannot find LINE: #### ID: #### CHAN: ### in db, reply (q/a/st/sl/line)
The allowable responses are as follows:
q
a
st
sl
line
Stop sending data to the next process and quit the

program.
Abort immediately.
Skip the trace.
Skip the line.
Enter the shot matrix name in the geometry db in
place of "line". For example to respond with the
Input Channels
Output Channels
Parameters
Header for shot id
Options: OIDN, SSPN, FSPN, OTHER, OIDN and FSPN
Select option OIDN and FSPN to perform a secondary match check with the contents of the FSPN
header.
Header word index (GCI) for shot id

Required if Header for shot id = OTHER. Enter the word index into the trace header (GCI format) for the
shot id. The first word is one.
Show parameters for

Options: 2-D survey, 3-D survey
576

Required if Show parameters for: = 3-D survey. Select "Yes" to apply the result of flex binning.
Duplicate FLEX traces?

To reduce the data volume, SeisUP supports saving FLEX information in the trace header words MSFL
and MEFL. To duplicate traces that fall into a range of CMPs and not store the FLEX information in the
traces headers, select Yes.
Multiple 3-D shot matrices to apply?

Required if Show parameters for: = 3-D survey.
3-D shot matrix name in trace header?

Required if Multiple 3-D shot matrices to apply? = Yes. Select "Yes" to get the shot matrix name from the
trace header. GEOM expects the name the shot matrix name to be in ASCII format.
Show geometry matrix for

Input if Multiple 3-D shot matrices to apply? = Yes and 3-D shot matrix name in trace header? = No.
3-D shot matrix to apply

Input if Show geometry matrix for: = Land.
Matrix Type: SOURCE

Input if Show geometry matrix for: = Marine.
Matrix Type: SOURCE2
Shot matrix trace header key (GCI)

Input if Multiple 3-D shot matrices to apply? = Yes and 3-D shot matrix name in trace header? = Yes.
Select the GCI trace header key where the name of the shot matrix is located.:
Options: LINE, OTHER
577
Shot matrix name byte position in GCI header

Required if Shot matrix trace header key (GCI) = OTHER. Enter the byte number in the trace header
where the shot matrix name is located. The first byte in the header is one.
Number of bytes in shot matrix name

Required if Shot matrix trace header key (GCI) = OTHER. Enter the number of bytes for the shot matrix
name in the header. See also the previous parameter
Output dead traces corresponding to missing receivers?

Select Yes to output dead traces for receivers defined within a shot in the database but are missing from
the input shot record. This can be useful, for instance if one wished to interpolate receivers from dead
traces.
Output dead traces corresponding to missing shots?

Select Yes to output dead traces for shots defined in the database but missing from the input. This can be
useful, for instance if one wished to interpolate shot records from dead traces.
Print min/max statistics?
578
GEOMCK
Module Description
Input Channels
Output Channels
Parameters
Module Description
GEOMCK allows the user to visually identify spread location errors by displaying GEOMCK file with
QCVIEW.
GEOMCK computes the RMS levels of each trace. RMS levels for each profile are high pass filtered. The
resulting output is strongly tied to near surface amplitude anomalies and first arrival travel path effects.
Traces on the same geophone group and on the same refractor on neighboring profiles have very similar
amplitudes.
Depending on the depth of the anomaly, the apparent location of an amplitude anomaly may shift by one
geophone group across the shot gap in a 2-D split spread survey. In a 3-D survey, shot to geophone
azimuth has a similar effect.
The input to the program should have geometry assigned and NO amplitude adjustments. Dead and noisy
ground positions actually help verify the geometry. The strongest and weakest traces shown in the
QCVIEW display are candidates for being killed.
The program can give ambiguous results if the geophone array is picked up and redeployed between
profiles (i.e. overnight), if there are transient noise sources in the spread or if there are bad shots.
Suggested parameters to use in QCVIEW for 2-D data are:
View selection
Selection attribute:
Display shots as
Diagram type
Color attribute for receivers
Receiver gain attribute to plot
=
=
=
=
=
=
2-D surface display

NONE
Surface consistent
Receivers
Receiver gain
GEOMCK file
When Print the best fit results? = Yes, GEOMCK checks geophone spread locations by comparing trace
RMS amplitudes from profile to profile. Profiles that dont match their neighbors are flagged for global
comparison with all profiles. The three best fits are reported for each profile. NOTE This can take
exponential time. For large surveys, it may be desirable to execute GEOMCK with Print the best fit
results? = No and examine the QCVIEW display first.
The output from the this option lists each profile with mismatches and the shot number, geophone line,
largest normalized correlation peak, expected shift in geophone number and the three largest peaks from
the correlation. A shot matches a nearby shot if the expected shift equals one of the three peaks. Shots that
are more than one half spread length away will not match in this way as the correlations are limited in
579
length. Split spread data has the high and low side of the spreads treated separately. In a 3D survey, the
geophone lines are also treated separately.
The input geometry is also listed.
Input Channels
Output Channels
Parameters
Print the best fit results?
Select "Yes" to output the best fit results and the input geometry.
Number of correlations / spread

Required if Print the best fit results? = Yes.
Number of geophone positions in shot gap

Required if Print the best fit results? = Yes.
Debug level
As you may expect, this parameter is for debugging the program. It is not useful to general users as it
produces mass amounts of cryptic printout. It is shown if Number of geophone positions in shot gap? =
3333. Number of geophone positions in shot gap? can be set back to a reasonable number after this
parameter is set. The default value is 0. Debug level may take values up to 5.
GEOMCK database file

The output file to be displayed with QCVIEW.
580
Clip value
This parameter is the value the output filtered amplitude values are clipped to. Increasing this parameter
may allow some more subtle amplitude effects to be seen. However the default is reasonable for most
datasets.
581
GEOMEXT
Module Description
Input Channels
Output Channels
Parameters
Module Description
GEOMEXT can be used to extract geometry from trace headers and place this information into a geometry
matrix for the modules SOURCE and STATION. GEOMEXT will use the following trace headers to fill
in the matrix:
1.
2.
3.
4.
5.
5.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
HEADER
-----Original field record number
Trace number within the OIDN
Trace identification code
Elevation and depth Scale factor
Coordinate Scale factor
Shot X coordinate
Shot Y coordinate
Receiver X coordinate
Receiver Y coordinate
Line name
NAME
---OIDN
FCSN
TRID
EG
ES
DEPS
SX
SY
GX
GY
UTS
SSBN
SSLN
RSBN
RSLN
FSPN
LINE
Input Channels
Output Channels
582
Parameters
Stations
This parameter is required if the parameter Receiver specification by: is Coordinates.

Shot acquisition type
Land surveys will ask for the depth, uphole time, and the elevation for each shot in addition to the
information requested for marine data.
Source specification by
This is the method to specify the shot locations. If the method is Receiver location, the skid and
perpendicular offset is set to zero.
Options: Coordinates, Receiver location
Pattern specification by
This is the method to specify the patterns.
Options: Distance from shot, Receiver location
Get shot matrix name from trace Header?

Select Yes if you wish to create multiple shot matrices via the line name in the trace header named LINE.
Source
Required if Shot acquisition type: = Land, Source specification by: = Coordinates and Pattern
specification by: = Distance from shot and Get shot matrix name from trace Header? = No.
583
Source
Required if Shot acquisition type: = Land, Source specification by: = Coordinates and Pattern
specification by: = Receiver location and Get shot matrix name from trace Header? = No.
Matrix Type: SRCXYREC2
Source
Required if Shot acquisition type: = Land, Source specification by: = Receiver location and Pattern
Matrix Type: SRCRECXY2
Source
Required if Shot acquisition type: = Land, Source specification by: = Receiver location and Pattern
Matrix Type: SRCRECREC2
Source
Required if Shot acquisition type: = Marine, Source specification by: = Coordinates and Pattern
Matrix Type: SOURCE
Source
Required if Shot acquisition type: = Marine, Source specification by: = Coordinates and Pattern
Matrix Type: SRCXYREC
Source
Required if Shot acquisition type: = Marine, Source specification by: = Receiver location and Pattern
Matrix Type: SRCRECXY
584
Source
Required if Shot acquisition type: = Marine, Source specification by: = Receiver location and Pattern
Matrix Type: SRCRECREC
Patterns
Required if Pattern specification by: = Distance from shot and Get shot matrix name from trace Header?
= No.
Matrix Type: PATTERN
Patterns
Required if Pattern specification by: = Receiver location and Get shot matrix name from trace Header? =
No.
Matrix Type: PATREC
Handle duplicate receiver lines by

Options: Use first coordinates, Create new receiver line
Increment for new receiver lines

Required if Handle duplicate receiver lines by = Create new receiver line.
Print all coordinate mismatches

Required if Handle duplicate receiver lines by = Create new receiver line.
Options: Yes,No
Coordinate mismatch tolerance (feet/meters)
585
GEOMVIEW
Module Description
Input Channels
Output Channels
Parameters
Module Description
GEOMVIEW displays a map at a one-to-one scale of shot locations, geophone locations or midpoint
locations of data loaded in the DB file for the area and line.
SHOT MAP
GEOMVIEW begins by drawing a map of SSPNs, i.e., sequential shot number for each shot. SSPN is an
important number (trace header) because it identifies a unique position on the ground. On the menubar
there is a button called Zoom. Using Zoom the map size may be enlarged (zoom in). Apply the Zoom until
each shot is an individual triangle. When the user places the pointer over a triangle the shot identifiers and
coordinates appear on the info line at the bottom of the map. These values are from the SDB database (DB
file). This info is placed there when STATION and SOURCE are run. On the menubar is a button called
Map. Selecting it shows that shot elevation, depth, and uphole times may be colored at each shot position
and values at a selected shot annotated in the lower info line. The colorbar to the right of the map gives
color info. If shot and uphole were not zero (surface source), v0 (shot depth / shot uphole) may also be
displayed. The SHOT input1 option is used with the Input menubar button and will be described later.
GEOPHONE MAP
Select the Map button on the menubar then select GEOPHONE Locations. Zoom the map if necessary
until each geophone location is an individual square. The locations are colored by SGEN. Each SGEN
number corresponds to a unique ground location. Placing the pointer on a square gives the SGEN, RSLN,
RSBN, X and Y values for that location. The geophone elevations may be shown by selecting Map
followed by GEOPHONE Elevations. If a complete first break matrix was selected in the GEOMVIEW
menu before execution, selecting Map followed by GEOPHONE FBP Fold will display a fold map of
picks at each SGEN. This allows the user to see if any geophone stations are low on or void of first break
picks. The GEOPHONE Input1 option is used with the Input menubar button and will be described later.
MIDPOINT MAP
To view MIDPOINT maps of elevation, stack fold GEOMVIEW must be connected to a stack dataset.
The elevations and stack fold are read from the stacked trace headers. The CMPdatum is a matrix created
by module STATIC when using a floating datum (smoothed surface elevations). The CMPdatum values
must be input using the Input menubar option discussed below. Once they are read they can be displayed
using Map followed by CMPdatum elevations.
586
Find
The Find menubar option locates a shot (by OIDN or SSPN or FSPN), a geophone by SGEN, a receiver
line by RSLN, or a shot line by SLIN. To locate a shot with a known OIDN value, first display shot
locations by selecting Map from the menubar, then select SHOT Locations. Second select the Find option
from the menubar and select OIDN. A dialog appears asking for the OIDN number desired. Type in the
OIDN number and click on the OK button. The desired OIDN will be annotated on the map by a round
black dot with black X and + through it. NOTE: Click MB3 (mouse button 3) on the map to clear this find.
A similar procedure is followed for finding an SGEN using the GEOPHONE Location map. If the RSLN
and RSBN values for a geophone position are known, the position may be located on the GEOPHONE
Location map by selecting Map on the menubar followed by RSLN. A dialog appears for entry of the
RSLN/RSBN values. Enter these values and click OK and the position will be annotated. Sometimes a
survey will be composed of many parts specified by SLIN (shot line). Each SLIN has many SBINs or shot
locations. The location of a known SLIN/SBIN may be annotated similar to RSLN/RSBN for a geophone
position.
Input
The Input button on the menubar is used to prompt the user to specify and input shot statics, geophone
statics or CMPdatum elevations for map display. Select Map from the menubar then select SHOT
Locations. Select Input from the menubar then Shot domain input and a dialog appears asking for the shot
statics matrix name and the label to attach to the map. Click OK and the shot static matrix is opened and
values read. Next select Map from the menubar followed by SHOT Input1 and the shot statics will be
colored on the map shot locations. Similar procedures are used for displaying geophone statics and
CMPdatum elevations.
Trace data
Selected shots and geophones that belong to selected shots may be displayed using the Trace data menubar
option. NOTE: Be sure the GEOMVIEW is connected to a shot ordered dataset. Start with the SHOT
Location map. Select Trace data from the menubar followed by Type shot. A dialog appears asking for
SLIN, SBIN, Minimum offset and Maximum offset. Just click OK to see SLIN 1 and SBIN 1 shot position
annotated (similar to annotation used by Find) and the shots geophone positions annotated with black
squares. Return to the Type shot dialog and set the maximum offset to some smaller value like 5000. the
click OK. Using Type shot any individual shot and geophones may be examined. Now select Trace data
followed by Select shot. As the pointer moves over the map the shot under it and the shots geophones are
read and displayed real time. To reset everything select Trace data followed by Clear shot. This action
exits Trace data mode.
MAPCON
MAPCON is a flow tool that follows READ and precedes DISPLAY in a flow. This flow typically would
be used for first break picking. MAPCON (MAP CONnect) requires a menu parameter specifying a full
path to a temporary file, example: /tmp/mapcon. If that same path and file name has been entered into the
GEOMVIEW menu, MAPCON and GEOMVIEW will communicate. To see this start the flow containing
MAPCON. Then go to GEOMVIEW and select Trace data followed by MAPCON and move the pointer
onto the map. The shot whose traces appear in DISPLAY should be annotated on the map with its
geophones. Advance the shot (red arrow) in DISPLAY, move the pointer to GEOMVIEW map, and the
587
new current shot should be annotated.
Input Channels
1. GCI input dataset: Optional connection from dataset GCI data type.
Output Channels
1. CGM output dataset: Optional connection to dataset CGM data type.
Parameters
Trace sort order
GEOMVIEW may be connected to a shot ordered or stacked dataset. For a shot ordered dataset select
SLIN/SBIN/FCSN. For a stacked dataset select MLIN/MBIN.
Options: SLIN/SBIN/FCSN, MLIN/MBIN
MAPCON file name (full path)

GEOMVIEW can display the shot and geophone positions of a shot read through a separate flow with
MAPCON in the flow before DISPLAY. The MAPCON module has a file specifier as a parameter.
GEOMVIEW must have the identical file specifier to communicate with MAPCON. Example:
/tmp/mapcon uses a file called mapcon in the /tmp directory for MAPCON<->GEOMVIEW
communication.
First break picks file

Select a first break time matrix from the list. The picks from this file will be used to compute and display
geophone first break pick fold. If none are available, use the matrix editor to generate a test matrix. Only 1
spreadsheet with dummy times are needed.
Matrix Type: AFS1B
Plot size (inches)

Plot a grid line through center of every nth MLIN and MBIN
588
GEOVEL
Module Description
Input Channels
Parameters
Module Description
GEOVEL is an interactive program that will pick RMS velocity curves and optionally a forth order term.
Depending upon the velocity analysis options that created the GEOVEL input data set, the following
windows may be created:
1. Semblance.
2. Common offset stack over the analysis location. This may also be referred to as the input CMP
gather.
3. Constant or variable velocity stacks.
To the right of the windows is the menu icon bar. The menu icons can be used instead of using the menus
from the menu bar in each window.
Picking velocities
Velocities can be picked in the semblance or velocity stacks windows. The following mouse buttons may
be used to modify velocities:
Button 1
Add or insert a pick at the current mouse

location.
Ctrl-Button 1
Same as "Button 1" but search through a

window centered at the mouse location.
GEOVEL will perform a two dimensional search
through the semblance and compute the
maximum power by using a parabolic equation.
The horizontal extent of the search window
is between the minimum and maximum velocity
in the cube. The vertical extent of the
window is determined by Autopick window (ms).
Button 2
Delete the pick closest to the current mouse

location.
Button 3
Move the closest pick to the current mouse

location.
589
All picks are surrounded by a red box. In the semblance window, the box is annotated to the left or right of
the pick. When adding a pick in the stack window, the user can optionally pick between velocity functions
and the value used will be half way between the velocity functions for the panel. The last pick will be
automatically picked and drawn using the interval velocity between the last two picks.
Three velocity curves can be drawn in the semblance and velocity stack windows as follows:
1. Previous velocity curve. (Cyan)
2. Current velocity curve. (Red)
3. Next velocity curve. (Magenta)
If a variable velocity stack is input the user can optional display each of the variable velocity curves in the
semblance section.
Applying NMO
To apply normal moveout to the input gather, pick the velocity function and then select "Toggle NMO"
from the File menu or press the NMO menu icon. To restore the input gather when Gather mode =
Gather, select "Toggle NMO" again.
Selecting an analysis location

You may select an analysis location by one of the following ways:
1. Select "Next" from the File menu or press the right arrow menu icon to select the next analysis
location.
2. Select "Previous" from the File menu or press the left arrow menu icon to select the previous analysis
location.
3. Select "Select" from the File menu or press the dual arrow menu icon to select another location. After
selecting "Select", a dialog will appear with a title of "select". Press and drag the slider(s) to an
analysis location. If the analysis location does not exist, GEOVEL will select the nearest one.
Fourth order NMO

Fourth order NMO will be beneficial if ray bending occurs and you have large far offsets. This frequently
causes an event to be non-hyperbolic and cause the event to swing upwards. To pick a fourth order term,
select Yes for the parameter Create fourth order correction?. After picking an RMS velocity function that
will model the moveout as much as possible, select Toggle fourth order analysis. A fourth order analysis
will be performed from the input CMP gather. If a value of zero is picked, the NMO equation becomes the
same as the standard second order equation. After picking the fourth order term (C4), select Toggle fourth
order analysis again to create a new RMS analysis using the fourth order term just picked. You might
need to iterate picking of RMS and C4 until you are satisfied with the results.
590
File menu
Option
Shortcut Description
-------------------------------------------------------------
Previous
Ctrl+p
Select previous analysis

location.
Next
Ctrl+n
Select next analysis location.
Select
Ctrl+s
Select an analysis location

given a range.
Change parameters
Toggle NMO
Change various parameters.
Ctrl+t
Apply normal moveout or add

normal moveout back into the
gather.
Toggle fourth order analysis Switch between RMS (second order)

and C4 (fourth order) analysis.
Toggle horizon overlay
Turn on or turn off overlay of

interpreted horizons.
Edit color ..
Edit horizon attributes ..
Show the horizon attribute editor

dialog.
Print ...
Print screen.
Quit
Ctrl+q
Quit GEOVEL
Help menu
Use the Help menu to get help on the following topics:
591
Option
Description
-------------------------------------------------------------
On use
On how to use GEOVEL
On menu icons
On what the menu icons represent.
Input Channels
1. Input: Required connection from dataset GVL data type.
Parameters
Matrix for RMS velocities
Enter the name of a velocity matrix to output picked velocities to.
Matrix Type: RMSVEL
Create fourth order correction?

Minimum fourth order value
Maximum fourth order value
Number of fourth order values
This is the number of fourth order values used for the semblance analysis.
Matrix for fourth order corrections

Enter the name to store the picked fourth order corrections.
Matrix Type: 4THNMO
Overlay interpreted horizons?

Horizon matrix to overlay (Depricated)
This parameter is depricated. Select a matrix name only to convert it to the new format
592
Matrix Type: SURFACE
Wiggle type
Options: Wiggle only, Wiggle and VA
Bias
Traces per inch

Enter the number of traces per inch for the trace display.
Inches per second

Gain (db)
The amount of gain in db to apply to the trace data before plotting.
Clip (traces)
clipped.
Timing lines?
Timing line increment (ms)
VVS lines in semblance?
If variable velocity stacks are input to GEOVEL, optionally you can display each of the variable velocity
curves on the semblance display.
Semblance gain (db)

The amount of gain in db to apply to the semblance data before plotting.
Start time (ms)
593
Ending time (ms)

Autopick window (ms)
Length of the automatic velocity picker window.
Gather mode
Select the type of gather display. Selecting "Gather & NMO" will display the input gather next to the
NMO applied gather.
Options: Gather, Gather & NMO
Semblance colormap
Select cursor size?
Small, Large
Select line type

Heading 1, Heading 2
Windows orientation?
Default,Stack Gather Semblance, Stack Semblance Gather
594
GEOVEL3C
Module Description
Input Channels
Parameters
Module Description
GEOVEL3C is an interactive program that will pick RMS velocity curves. Depending upon the velocity
analysis options that created the GEOVEL3C input data set, the following windows may be created:
1. Semblance.
2. Common offset stack over the analysis location. This may also be referred to as the input CMP
gather.
3. Constant velocity stack.
To the right of the windows is the menu icon bar. The menu icons can be used instead of using the menus
from the menu bar in each window.
Picking velocities
Velocities can be picked in the semblance or constant velocity stack windows. The following mouse
buttons may be used to modify velocities:
Button 1

location.
Ctrl-Button 1
Same as "Button 1" but search through a

window centered at the mouse location.
GEOVEL3C will perform a two dimensional
search through the semblance and compute the
maximum power by using a parabolic equation.
The horizontal extent of the search window
is between the minimum and maximum velocity
in the cube. The vertical extent of the
window is determined by Autopick window (ms).
Button 2

location.
Button 3

location.
All picks are surrounded by a red box. In the semblance window, the box is annotated to the left or right of
the pick. In the constant velocity stack window, the pick is displayed on the closest constant plain. The last
pick will be automatically picked and drawn using the interval velocity between the last two picks.
595
Three velocity curves can be drawn in the semblance and constant velocity stack windows as follows:
Applying NMO
To apply normal moveout to the input gather, pick the velocity function and then select "Toggle NMO"
from the File menu or press the NMO menu icon. To restore the input gather when Gather mode =
Gather, select "Toggle NMO" again.

You may select an analysis location by one of the following ways:
1. Select "Next" from the File menu or press the right arrow menu icon to select the next analysis
location.
2. Select "Previous" from the File menu or press the left arrow menu icon to select the previous analysis
location.
3. Select "Select" from the File menu or press the dual arrow menu icon to select an an other location.
After selecting "Select", a dialog will appear with a title of "select". Press and drag the slider(s) to an
analysis location. If the analysis location does not exist, GEOVEL3C will select the nearest one.
File menu
Option
Shortcut Description
-------------------------------------------------------------
Previous
Ctrl+p
Select previous analysis

location.
Next
Ctrl+n
Select next analysis location.
Select
Ctrl+s
Select an analysis location

given a range.
Change parameters
Toggle NMO
Change various parameters.
Ctrl+t
Apply normal moveout or add

normal moveout back into the
596
gather.
Quit
Ctrl+q
Quit GEOVEL3C
Help menu
Option
Description
--------------------------------------------------------------
On use
On how to use GEOVEL3C
On menu icons
Input Channels
1. Input: Required connection from dataset GVL data type.
Parameters
RMS velocities
Enter the name of a velocity matrix to output picked velocities to.
Matrix Type: RMSV3C
Wiggle type
Bias
Traces per inch

597
Inches per second

Enter the number of inches per second for the trace display. The default is to compute an inches per
second such that the entire trace length will fit in the display. If entering the parameter from the
GEOVEL3C parameter dialog, enter a blank field to "Fit Section" if you had previously changed the
default.
Gain (db)
The amount of gain in db to apply to the trace data before plotting.
Clip (traces)
clipped.
Timing lines?
Timing line increment (ms)
Semblance gain (db)
The amount of gain in db to apply to the semblance data before plotting.
Start time (ms)

Ending time (ms)
Length of the automatic velocity picker window.
Gather mode
Select the type of gather display. Selecting "Gather & NMO" will display the input gather next to the
NMO applied gather.
Options: Gather, Gather & NMO
598
GNATTR
Module Description
Input Channels
Output Channels
Parameters
Module Description
GNATTR will extract the RMS instantaneous amplitude within a specified temporal window and output
an average shot or channel attribute to the ordered database.
Input Channels
Output Channels
Parameters
Shot Attribute name
The shot attribute is calculated by averaging the gains for each trace within a shot.
Matrix Type: RMSSSPN
Channel Attribute name

Add to existing attribute?

If "Yes", any existing attribute with the above name will be deleted.
599

Space variant windows?

Only one start and end window time should be entered into this matrix. Time-variant windows are not
supported at this time.
Window start time (ms)

Required if Space variant windows? = No.

Primary header key

Required if Space variant windows? = Yes.
TLSN

TLSN
Window times
Filter data prior to RMS calculation?
600

Required if Filter data prior to RMS calculation? = Yes.



Number of channels per shot
601
GNPLOT
Module Description
Input Channels
Output Channels
Parameters
Module Description
GNPLOT extracts the average instantaneous amplitude within the specified temporal window and
frequency range. The gain for each trace is computed relative to the grand average of all the traces. The
gain level is plotted in the shot-receiver domain.
Input Channels
Output Channels
1. CGM plot file: Required connection to dataset CGM data type.
2. Seismic trace: Optional connection to next process GCI data type.
Parameters
Shots per inch
Geophones per inch
Plotting range (+/- DB)
This is the range relative to the grand average of the all the traces. Amplitude above this range will be
assigned the same color as the upper limit. Similarly, amplitude below this range will be assigned the same
color as the lower limit.
Contour levels
The number of contour colors must be n * 4 + 1, or will be forced so.
602


Primary header key

TLSN

TLSN
Window times

603
GRNMTN
Module Description
Parameters
Module Description
This module allows the user to import/export geometry, refraction picks, and statics from Green Mountain
Geophysics (GMG) database files into SeisUP. The export option will output the geometry and the first
break picks to new Green Mountain database files. The import will load existing GMG geometry, first
break picks, refraction statics, and datum statics into SeisUP.
The import option allows the user to import GMG data into SeisUP. A typical scenario might be to build
the geometry using GMG and then import this to SeisUP to use as the SeisUP geometry. Another use will
be to load into SeisUP, refraction or datum statics computed in GMG.
The export option allows the user to send geometry and first break picks to GMG for refraction statics
computation. After the statics are computed in GMG, the user can then import the statics into SeisUP to
use in processing the seismic data.
Some GMG database file extensions:
.mas - The master GMG database file. This file is required.
.sor - The sources file. This file is required.
.sta - The stations file. This file is required.
.pat - The pattern file. This file may/may not be output by GMG but is always output by SeisUP.
.fbt - The refraction picks file.
If refraction or datum statics are imported but not geometry, then the source and station order must be the
same in SeisUP and GMG. All stations and sources must have a static value (i.e. you may not have
skipped stations or sources in the GMG file). The source/station statics will be read sequentially from
the GMG database files and placed in sequential order in SeisUP. If geometry is imported at the same
time, then the order will automatically be correct.
After a geometry import from GMG the modules STATION and SOURCE must be run to load the
SeisUP database. The queue module GEOM must also be run on the trace data.
If a GMG source pattern file is NOT used, then this will probably be a 2D survey. In this case, matrices
are built for STATION and SRCXYSPD2. Common 2D STATION module menu selections are:
604
*STATION
Receiver specification by: Coordinates
Stations : geometry
Common SOURCE module menu selections are:
*SOURCE
Source specification by: Coordinates
Pattern specification by: Spread Layout
Source geometry
If a GMG source pattern file was used then geometry matrices are built for STATION, SRCXYREC2, and
PATREC. Common 3D STATION module menu selections are:
*STATION
Receiver specification by: Coordinates
Stations : geometry
Common SOURCE module menu selections are:
*SOURCE
Source specification by: Coordinates
Pattern specification by: Receiver location
Source geometry
Patterns geometry
Parameters
Import/Export Green Mountain
Select to import from Green Mountain or export to Green Mountain database files.
Options: Import from, Export to
605
Output Green Mountain MASTER file name (.mas)

Enter the name of the Green Mountain master database file to build for the export. This file will have an
extension .mas. The .mas will be added to the file name if it is missing. The file will be placed in the
users home directory unless the full path name is given. Example: /user/home/data/test.mas.
Refraction picks matrix name

Select the first break pick matrix to export. This will be a SeisUP matrix of type AFS1B.
Matrix Type: AFS1B
Sample rate (ms) of data

Enter the sample rate of the data in milliseconds. This should be the sample rate of the seismic data that
the first break picks are based upon.
Input Green Mountain MASTER file name (.mas)

Enter the name of the Green Mountain master database file to load for the import. This file will have an
extension .mas. You must also include a path if needed. Example: /user/home/data/test. The .mas will
be added to the file name if it is missing.
Import geometry?
Select to import geometry from Green Mountain database files.
GEOMETRY matrix name

Enter the name of the new geometry matrix. If patterns are imported then geometry matrices: STATION
for stations, SRCXYREC2 for sources, and PATREC for patterns. If patterns are NOT imported:
STATION for stations, and SRCXYSPD2 for sources.
Import refraction picks?

Select to import first break picks from Green Mountain database files (if included). If a GMG file with
extenuation .fbt is included with the database files, then you can import the refraction picks into SeisUP.
Refraction picks matrix name

Enter the name of the new first break pick matrix.
606
Matrix Type: AFS1B
Import refraction statics?

Select to import refraction statics from Green Mountain database files.
Geophone statics matrix name

Enter the name of the new refraction geophone statics matrix. This will be a SeisUP matrix type,
STATGEO.
Source statics matrix name

Enter the name of the new refraction source statics matrix. This will be a SeisUP matrix type, STATSRC.
Import datum statics?

Select to import datum statics from Green Mountain database files.
Geophone statics matrix name

Enter the name of the new datum geophone statics matrix. This will be a SeisUP matrix type, STATGEO.
Source statics matrix name

Enter the name of the new datum source statics matrix. This will be a SeisUP matrix type, STATGEO.
607
GRVA
Module Description
Input Channels
Output Channels
Parameters
Module Description
This tool performs residual velocity analysis on pre-stack CMP gathers. The output is a VIP velocity cube
with the RMS velocities updated by residual velocity analysis.
GRVA requires cleaning up the CMP gathers as much as possible before running. This might include:
Using RMS velocities that are as accurate as possible.
Un-corrected CMP gathers (i.e. do not correct for NMO velocity).
Trace mute of 40 degrees.
FX Decon on the NMO gathers.
Trace mixing of the NMO gathers.
Small window AGC (500ms). See the TVEQ module.
The input CMP gathers to this module must be NOT be corrected for NMO velocity. The module will
perform the velocity corrections.
In AVO analysis, the gradient (slope) is very sensitive to residual velocity errors. We can use this
sensitivity to develop a product indicator to minimize the error within the gradient. This product indicator
is equal to IM(AB*) where B* is the conjugate of the analytic slope and A is the analytic intercept. The
imaginary part of their joint correlation coefficient quantifies the gradient quadrature component and is
proportional to the average of the fractional NMO velocity errors. The optimal NMO velocity is the one,
which nulls this imaginary correlation.
The user can select a starting and ending incidence angle to process. Typically the maximum incidence
angle should be 30 degrees or less. GRVA works only on the hyperbolic portion of the offsets. If you
include data in the non-hyperbolic region, then this module will not work as well. The hyperbolic region is
typically on the near-offset traces.
The user may select a start and stop time. This should allow the program to run much faster on a dataset.
The start/stop times must include enough data to fully analyze the target area. The module will update the
velocities with in the start/stop time but will use the old velocities outside this zone in the output VIP file.
GRVA outputs the new RMS velocity cube as a VIP file. The VIP file can be connected to several
modules that use RMS velocities, including: NMOR, AVOA, KTMIG, and other modules that accept VIP
file input. The VIP file can also be converted to a RMSVEL matrix using the VIPINV module.
608
The residual velocities can be smoothed in the line or bin direction by summing the analytic intercept and
slope. Be aware though, that the summing process will add much time to the overall processing time. If
you want this to finish quicker, you should set the Number of lines/bins to sum for residual analysis to
1. The input CMP gathers must be cleaner to use a lower number of summed traces.
The intermediate velocity cube and AVO traces can be stored in memory or mapped file. The program
runs faster if you can save this data in memory. If the program aborts due to lack of memory though, you
might have to set the storage devices to file.
The process can be run on a parallel cluster system. Several parameters that are common to GeoCenter
parallel processing modules are used. Enter the Compute node list and the Subnode list if need be. The
number of actual nodes to use from the list(s) is entered also. The node list is stored in the
QEDTOP/lib/nodes directory of your SeisUP system. To speed the transfer of the input CMP gathers to
the nodes, threads can be used to pass multiple CMP gathers simultaneously. This will probably be much
faster on multi-processor machines only.
Several iterations of the tool will probably be necessary. On the first run, input the initial RMSVEL matrix
or a VIP file as the input velocity cube. On subsequent runs of this tool, the updated VIP file is used as the
input velocity cube. Each time, the output VIP file will contain the updated velocities that have been
corrected from residual NMO. The number of iterations to run will vary; depending on how much residual
NMO is in the analysis window. In general, about 10 iterations should do it.
You can restart the process from the last iteration by selecting the velocity import method. Change the
parameter, Method to input start RMS velocities to VIP velocities from previous run. On the first
iteration this must be set to RMS velocity matrix to load the initial velocity cube.
References
Herbert W. Swan, Seismic velocities from amplitude variations with offset, SEG 2000 Expanded Abstracts.
Herbert W. Swan, Amplitude-versus-offset measurements errors in a finely layered medium, Geophysics,
Vol. 56, No 1, January 1991, p 41-49.
Input Channels
1. GCI Input: Required GCI data type.
2. VIP Velocity: Required SEGY data type.
Output Channels
1. VIP Velocity: Required SEGY data type.
609
Parameters
Number of iterations
Specify the number of iterations to run on the data. For each run, the updated VIP file as used as the input
velocity cube. This module will take several iterations to totally correct the data.
Default .....:5
Name ........:iter
Min .........:1
Max .........:
Min. midpoint line number:

Select the minimum midpoint line number as the starting point for the analysis. Use this parameter to
select a subset of the input seismic data set.
Default .....:Get All
Name ........:ybmin
Min .........:
Max .........:
Max. midpoint line number:

Select the maximum midpoint line number as the ending point for the analysis. Use this parameter to
select a subset of the input seismic data set.
Name ........:ybmax
Min .........:
Max .........:
Min. midpoint bin number:

Select the minimum midpoint bin number as the starting point for the analysis. Use this parameter to select
a subset of the input seismic data set.
Name ........:xbmin
Min .........:
610
Max .........:
Max. midpoint bin number:

Select the maximum midpoint bin number as the ending point for the analysis. Use this parameter to select
a subset of the input seismic data set.
Name ........:xbmax
Min .........:
Max .........:
Start of analysis window (ms)

Enter the analysis window start time in milliseconds. The residual velocity analysis can be performed over
a window of the data. The output VIP file will replace the velocities within the analysis window. The
velocities outside the analysis window will be copied from the old velocity data.
Default .....:0
Name ........:dstrt
Min .........:0
Max .........:99999
End of analysis window (ms)

Enter the analysis window end time in milliseconds. The residual velocity analysis can be performed over
a window of the data. The output VIP file will replace the velocities within the analysis window. The
velocities outside the analysis window will be copied from the old velocity data.
Default .....:Record length
Name ........:dend
Min .........:0
Max .........:99999
Minimum incident angle (deg)

Enter the minimum incidence angle to use in degrees. Seismic samples that have an incident angle less
than the minimum will not be used in the Intercept/Gradient calculation.
Default .....:3.0
Name ........:theta_min
Type ........:Float
Min .........:0.0
611
Max .........:90.0
Maximum incident angle (deg)

Enter the maximum incidence angle to use in degrees. Seismic samples that have an incident angle less
than the minimum will not be used in the Intercept/Gradient calculation.
Default .....:30.0
Name ........:theta_max
Type ........:Float
Min .........:0.0
Max .........:90.0
Minimum fold for computation

Specify the minimum fold required at each sample to compute residual velocity analysis. If the fold is less
than this value at a sample, then a computation is not made at this CMP.
Default .....:5
Name ........:fold
Min .........:1
Max .........:
Method to input starting RMS velocities:

Select as the input velocity model as a RMSVEL matrix or the VIP file attached as the output VIP file.
The GRVA module will need several iterations to completely correct for residual NMO. On the first run,
select the RMSVEL matrix to input. This is typically the RMSVEL matrix used in velocity analysis. On
subsequent iterations of the tool, the output VIP file will be used as the input velocity cube. The output
VIP file will be overwritten with the new velocities.
Default .....:RMSVEL velocity matrix
Name ........:methodv
Options .....:
RMSVEL velocity matrix
VIP velocities from previous run
RMS velocities:
Enter the RMSVEL velocity matrix to use as the input velocity cube.
612
Default .....:
Name ........:vname
Matrix type .:RMSVEL
Velocity smoothing filter length (ms)

Enter the velocity smoothing filter length in milliseconds. Input velocities will be smoothed over this time
window before they are used.
Default .....:0
Name ........:ismth
Min .........:0
Max .........:
Time spacing between output velocity values (ms)

The output VIP file will output time/velocity pairs using this time interval If you are output the VIP file
for another iteration of this tool, you will need to keep the time interval equal to the current sample rate. If
you want to use VIPINV to output a RMSVEL matrix, you will probably want to output a velocity value
every 100 ms.
Default .....:Sample rate
Name ........:compre
Min .........:1
Max .........:1000
Ricker wavelet center frequency (Hz)

The Ricker center frequency in hertz . This is used in the residual velocity analysis correction. Typically,
enter the dominate frequency of the seismic data in the zone of interest.
Default .....:30.0
Name ........:center
Type ........:Float
Min .........:5.0
Max .........:500.0
Correlation window length (ms)

The correlation window for residual velocity analysis in milliseconds. The correlation window should be
large enough not to be influenced by any anomalies in the target zone. It should also be small enough to
adapt to the changing statistics in the background signal.
613
Default .....:500
Name ........:corwin
Min .........:10
Max .........:5000
Number of lines to sum for residual analysis

The number of lines to use for averaging the intercept/gradient in residual velocity analysis. The modules
will create a mini-cube of intercept/gradient traces when computing the residual velocity analysis. This
helps smooth the velocity information over the survey.
Default .....:5
Name ........:line
Min .........:1
Max .........:
Number of bins to sum for residual analysis

The number of bins to use for averaging the intercept/gradient in residual velocity analysis. The modules
will create a mini-cube of intercept/gradient traces when computing the residual velocity analysis. This
helps smooth the velocity information over the survey.
Default .....:5
Name ........:bin
Min .........:1
Max .........:
Method to store temporary input velocity model:

The input velocity model is input from a RMSVEL matrix or the connected VIP file. The velocity cube is
input into either memory or mapped memory while doing the analysis. If memory is specified, the
velocity cube is stored in memory during the calculations. If the survey is too big or not enough memory is
available, then the velocity cube can be stored in a mapped memory file. This will slow the program down.
Name ........:mem1
Options .....:
Memory
File
614
Method to store temporary pre-stack attributes:

The program stores intermediate seismic attributes during the computation. The intermediate data can
either be stored in memory or as mapped memory files. If memory is specified, the attributes are stored in
memory during the calculations. If the survey is too big or not enough memory is available, then the
attributes can be stored in a mapped memory file. This will slow the program down.
Name ........:mem2
Options .....:
Memory
File
Parallel execution mode:

The program can be run in parallel on a cluster system.
Default .....:None
Name ........:pmeth
Options .....:
None
Cluster
Number of nodes in the cluster:

This parameter controls how many nodes are started when running on a cluster. The nodes are taken from
the list built by using the parameters described below to build a list of clusters nodes. The program, then
takes the first n nodes from the list to perform parallel processing.
Default .....:2
Name ........:nnode
Min .........:1
Max .........:
Compute node list:

when running on a cluster. If there are more than one cluster, then they will be available in this menu
parameter. The Compute node list(s) reside in QEDTOP/lib/nodes directory of your SeisUP system. It
should be set-up by the System Administrator.
615
Default .....:default
Name ........:nodes
Options .....:Output generated by command lst_nodes
Custom sub-node list:

This parameter is used to specify a specific list of sub-nodes, from the Compute node list described above.
This parameter is only available when running on a cluster. If the Compute node list has many nodes, say
100 nodes named n1, n2, .. n100. If you wanted to run this program on 25 nodes, and specifically nodes
n26 to n50, you would enter 26 to 50 for the values of CPU index in the subnode matrix. Also if you enter
values 11 to 20, then the node listed 11 in the Compute node list, to the node listed 20 in the Compute
node list are used to run the program on. Therefore it is the order of listing in the Compute node list which
determines which specific nodes of the cluster this job will be run on. This parameter is useful if you plan
to run several jobs on this cluster, and want them to run on different nodes.
Default .....:Use all
Name ........:subnodes
Matrix type .:MPISNODES
Number of threads to use on master to pass input data:

To speed the transfer of the input CMP gathers to the nodes, you can use threads on a multi-processor
computer. Specify the number of threads to use for input CMP gather transfers. This number should be a
multiple of the number of nodes used on the cluster for the most efficient transfer of the data.
Default .....:4
Name ........:nthread
Min .........:1
Max .........:
Path to directory for node data storage:
AUTHOR
Created on Jul 15, 2004 by Steve Jensen
616
GVLPICK
Module Description
Input Channels
Parameters
Module Description
GVLPICK can be used to automatically pick RMS velocities. This module requires a GEOVEL input data
set that contains velocity analysis information. This data set can be created with the CVA2D or CVA3D
modules. GVLPICK requires a reference guide function and a fairway defined as a percentage of the
reference guide function. A possible use of the module include picking velocities in an area with a coarse
analysis grid using the GEOVEL and then using this module to pick a finer grid.
GVLPICK parameters
617
Input Channels
1. Input geovel data set: Required connection from dataset GVL data type.
Parameters
Reference RMS velocities
Enter a reference RMS velocity matrix that will be used as a guide for picked functions.; GVLPICK will
interpolate between input reference functions if multiple functions are input.
Matrix Type: RMSVEL
Output picked RMS velocities

Enter the matrix name to store velocity functions picked by GVLPICK.
Matrix Type: RMSVEL
Re-pick velocities at reference locations?

Select Yes to pick velocity functions if the location being picked has been defined in the input reference
RMS velocities. If No is selected the function from the input matrix will be copied to the output picked
matrix.
Percentage & weight of reference function

This matrix will define the fairway to search for peaks that will be automatically picked. If desired a
weighting function can also be applied.
Matrix Type: GVLPREF
Time variant pick windows?

Select Yes to enter a time variant pick window definition. Select No to enter a fixed pick window.
Auto-pick window (ms)

Enter the pick window size over which GVLPICK will search for a peak semblance.
618
Minimum delta-t between pick times (ms)

Enter the minimum time increment between picked times.
Maximum deviation from the norm allowed (%)

After initial picks are make, GVLPICK will compute an average RMS velocity curve using semblance
weighted smoothing. Enter the maximum pick deviation allowed from the norm or average RMS velocity
curve. If a pick exceeds the maximum deviation, the pick will be dropped or moved depending upon the
parameter if pick deviates the norm:.
If pick deviates the norm

If a pick deviates from the norm select Move it to move the pick to the norm velocity limit. Otherwise
select Delete it to delete any picks that deviate from the norm.
Options: Drop it, Move it
Minimum window size for norm calculation (ms.)

The minimum window size will be used at picks with high semblance values to calculate the norm or
average RMS velocity curve.
Maximum window size for norm calculation (ms.)

The maximum window size will be used at picks with low semblance values to calculate the norm or
average RMS velocity curve. The norm or average RMS velocity cure will become smoother with a higher
window size.
Auto-pick windows
If the parameter Time variant pick windows? is Yes, enter the matrix name containing the time variant
pick windows to be used for automatic picking.
Matrix Type: GVLAWIN
Marine survey?
Enter Yes to pick the first velocity pick at the water bottom using a user specified water velocity.
Get water bottom time from

If the parameter Marine survey? is Yes, enter the trace header word location to retrieve the water bottom
time from.
619
Options: TIM1, TIM2
Water velocity (ft. or meters)

If the parameter Marine survey? is Yes, enter the water velocity to be used at the water bottom.
Velocity at zero time (ft. or meters)

If the parameter Marine survey? is No, enter the RMS velocity at time equal to zero.
Shift fairway & T.V. pick window by water bottom?

If the parameter Marine survey? is Yes, select Yes to shift the fairway function as well as the the time
variant pick function by the water bottom time. This can be used to allow the fairway and pick window
parameter to follow the water bottom.

Enter the minimum interval velocity. If a pick is made that will produce a velocity that is less than this
parameter then the pick window will be shifted by the minimum delta-t between pick times parameter to
search for another peak.

Enter the maximum interval velocity. If a pick is made that will produce a velocity that is more than this
parameter then the pick window will be shifted by the minimum delta-t between pick times parameter to
search for another peak.
Pick RMS velocity inversions?

Select Yes to allow the picker to pick an RMS velocity that is less than the previous picked time and
velocity. If No is selected and a peak picked will produce a velocity inversion then the pick window will
be shifted by the minimum delta-t between pick times parameter to search for another peak.
First midpoint bin to pick

Enter the first midpoint bin (MBIN) to pick and output.
Last midpoint bin to pick

Enter the last midpoint bin (M BIN) to pick and output.
620
First midpoint line to pick

Enter the first midpoint line (MLIN) to pick and output.
Last midpoint line to pick

Enter the last midpoint line (MLIN) to pick and output.
621
GVLPRINT
Module Description
Input Channels
Output Channels
Parameters
Module Description
GVLPRINT will output a velocity analysis plot in CGM format. The following will be output for each
analysis location:
1.
2.
3.
4.
5.
6.
Picked velocity function (If velocity picked)

Semblance
Interval velocity (If velocity picked)
Gather
Gather with NMO applied (If velocity picked)
Velocity stacks
GVLPRINT currently does not support plotting three component velocity information or fourth order
information.
Input Channels
1. Input geovel data set: Required connection from dataset GVL data type.
Output Channels
1. Output cgm data set: Required connection to dataset CGM data type.
Parameters
RMS velocities
Matrix Type: RMSVEL
622
Traces per inch

This parameter is for the gather display.
Inches per second

Gain (db)
Clip (traces)
Bias
Wiggle type
Start time (ms)

End time (ms)
Semblance display type
Options: Contour, Color cell, Color continuous contour
Number of contour intervals

Colormap
Options: Red/Black, Rainbow, Contour, Red/Blue, Greyscale
623
Number of color levels

Custom colormap
First midpoint bin to plot
Last midpoint bin to plot
First midpoint line to plot
Last midpoint line to plot
Width of semblance display (inches)
Width of interval velocity display (inches)
Annotate shotpoint numbers?
Scalar to multiply bins to derive shotpoints
The shotpoint number is calculated as follows: Shotpoint # = Scalar * CMP number + Constant
Constant to add to bins to derive shotpoints

Number of analysis across plotter
This is the number of analysis to plot side by side to conserve plotter paper.
Title to place at the beginning of each analysis
624
HAMPSON
Module Description
Input Channels
Parameters
Module Description
Run HAMPSON to read a static file written by the GLI3D program from Hampson and Russell. The
actual format of the file is in the HMATH format for the DISCO system. The following is an example:
GLI3D REFRACTION STATICS
*CALL
MODEL
INPUT
DATA
DATA
.
.
.
DATA
HMATH
*CALL
MODEL
INPUT
DATA
DATA
.
.
.
DATA
END
HMATH
SHOT
FIELD
SHOT
1
2
.
.
.
27
STAT
-10
-6
.
.
.
-29
STATION
STATION FIELD
STAT
500
-48
501
-42
.
.
.
.
.
.
640
-68
After HAMPSON is run the matrix names can be used in the module STATIC with Static type: =
Roll-along.
Input Channels
1. SEG P1 File: Required connection from dataset ASCII data type.
Parameters
625
Station static matrix name

Shot static matrix name

Abort if duplicate/out of order id found

Normally GLI3D outputs statics in the correct order. Conditions exist where duplicate indexes are output.
The statics may not be equal but are generally close. If you choose not to abort the job, the duplicate / out
of order values are dropped. Check these to see if there is a significant difference in statics.
626
HDRDUMP
Module Description
Input Channels
Output Channels
Parameters
Module Description
HDRDUMP will print selected trace header words. At the end of the job, HDRDUMP will also print the
minimum and maximum values found for each trace header. The minimum and maximum values are
searched over every trace in the job and not just the trace headers printed. There are 3 options to select the
headers to be dumped. A standard list of headers are dumped by default. These are:
TLSN, OIDN, FCSN, MBIN, MLIN, SDPN, TRID, DIST, STAT, MUTST, MUTEND,
SGEN, SSPN, FSPN, FOLD
Up to 4 additional headers may be added to this list. Another option is to select the Custom header dump
from DISPLAY. A final option is a list taken from an input matrix.
Input Channels
1. Input : Required connection from previous process GCI data type.
Output Channels
Parameters
Key for starting ID
TLSN, other
627
Header key number

Required if Key for starting ID = other.
Starting ID
Number of traces to dump
This is the maximum number of traces to dump. Once this limit is reached, traces will still be passed on to
the next process. HDRDUMP will not stop reading traces.
Exclude zero from min./max. search?

Select "Yes" to exclude values of zero when searching for the minimum and maximum values for each
trace header dumped.
Dump ensemble boundaries only?

Select "Yes" to only dump traces when a new ensemble is reached.
Print Header Page Headings?

Select "No" to omit header word ID row printed at the top of each page. This is useful if the ASCII values
are to be copied from the runlog.
Use user defined list of headers to dump?

List of headers to dump?
This variable is accessed if Use user defined list of headers to dump is set to YES .
Matrix Type: DUMPLIST
Use custom header dump from DISPLAY?

Select Yes to use the custom header dump used in the DISPLAY module.
Extra header #1 to dump

If you select a header, HDRDUMP will append this header to the end of the list of headers to dump.
TLSN, other
628
Extra header index #1 to dump

Required if Extra header #1 to dump = other.

TLSN, other


TLSN, other


TLSN, other

Dump OIDN FCSN and number of traces for each ensemble?

Select "Yes" to dump OIDN FCSN and the number of traces for each ensemble.
629
HDRINTP
Module Description
Input Channels
Output Channels
Parameters
Module Description
HDRINTP can be used to insert dead traces at missing trace locations that can be used by other modules
for interpolation such as from TRIP5D or LRADON. HDRINTP only works within an ensemble. Reasons
to use a secondary key may be for receiver line/bin within a shot record or to insert dead traces for offset
and azimuth within a CMP. Currently if multiple valid input traces fall into the same grid point, only one
of the traces for that grid will be output. In this case run HDRSTK to sum common grid points prior to
running this module.
As an example suppose one wished to mimic interpolation via TRIP for missing midpoint MBIN traces:
Primary header key
Primary increment
Primary spacing
Maximum interpolation distance(ft/mtr)
MBIN
1
110
NONE
220
Input Channels
Output Channels
Parameters
Primary header key
Enter the primary trace header key to determine if dead traces need to be inserted.
TLSN, Other
630
Primary header index

If the "Primary header key" above is "Other", enter the trace header index.
Primary increment
Enter the ordinal grid increment corresponding to the "Primary header key"
Primary spacing
For ordinal headers like MBIN, enter the spacing between "Primary increment"s. For header DIST, enter
the grid spacing increment between common offsets.

Enter the secondary trace header key to determine if dead traces need to be inserted.
TLSN, Other
Secondary header index

If the "Secondary header key" above is "Other", enter the trace header index.
Secondary increment
Enter the ordinal grid increment corresponding to the "Secondary header key"
Secondary spacing
For ordinal headers like MBIN, enter the spacing between "Secondary increment"s. For header DIST,
enter the grid spacing increment between common offsets.
Maximum interpolation distance(ft/mtr)

Enter the maximum interpolation distance threshold between adjacent live traces. If this threshold is
exceeded than a dead trace will not be inserted.
Extrapolate headers?
Select "Yes" to specify a minimum and maximum interpolation grid.
631
Primary minimum
If "Extrapolate headers?" is "Yes", enter the minimum primary interpolation grid value.
Primary maximum
If "Extrapolate headers?" is "Yes", enter the maximum primary interpolation grid value.
Secondary minimum
If "Extrapolate headers?" is "Yes", enter the minimum secondary interpolation grid value.
Secondary maximum
If "Extrapolate headers?" is "Yes", enter the maximum secondary interpolation grid value.
Primary grid minimum

If "Extrapolate headers?" is "No", enter the minimum absolute primary grid minimum. HDRINTP will
make sure the grid within the ensemble falls on this same grid. The default is to use the minimum value
within the ensemble to use as the minimum grid value.
Primary grid maximum

If "Extrapolate headers?" is "No", enter the maximum absolute primary grid maximum. HDRINTP will
make sure the grid within the ensemble falls on this same grid. The default is to use the maximum value
within the ensemble to use as the maximum grid value.
Secondary grid minimum

If "Extrapolate headers?" is "No", enter the minimum absolute secondary grid minimum. HDRINTP will
make sure grid within the ensemble falls on this same grid. The default is to use the minimum value within
the ensemble to use as the minimum grid value.
Secondary grid maximum

If "Extrapolate headers?" is "No", enter the maximum absolute secondary grid maximum. HDRINTP will
make sure the grid within the ensemble falls on this same grid. The default is to use the maximum value
within the ensemble to use as the maximum grid value.
Expected max. # output traces/ensemble

Enter the expected maximum number of output traces per ensemble after interpolation of headers.
632
Create geometry headers from interpolation?

Select "Yes" to create full geometry headers as used in GEOM or XYGEOM after the header is inserted.
This is a requirement for modules such as TRIP5D that need valid source and receiver coordinates.
Set SBIN,SLIN,SSPN?
If creating geometry headers after interpolation, select "Yes" to set the SBIN and SSPN equal to the value
of SSBN while also setting SLIN to the value of SSLN. Normally for land projects one would set this to
"No" but if this same parameter is set to "Yes" in XYGEOM then it should also be set here.
Verbose?
Select "Yes" to be more verbose regarding invalid trace locations.
633
HDRSTK
Module Description
Input Channels
Output Channels
Parameters
Module Description
HDRSTK stacks adjacent traces with some common trace header values. Header word FOLD will contain
the number of traces within each group (summed or other process). Other header values will be from the
first trace into the sum.
The header word adder and header word divisor are used to determine the grouping of the input traces, as:
value in header key + header adder
ID = --------------------------------------header divisor
The value ID is computed by truncating the value of the right side of above equation. Adjacent traces with
the same ID will be processed as a group, according to the option chosen. For instance, to sum two
adjacent offsets within a shot from a typical marine survey with a near offset of 275 m and a group
interval of 25 m (sum 275 & 300, sum 325 & 350 etc.), one needs to use an adder of 25 and divisor of 50.
The offset distribution will become 275, 325, etc. after HDRSTK.
HDRSTK operates within each ensemble only. It will not process across ensemble boundaries.
Processing options available include:
Mean.
The simple arithmetic mean value is found by the following formula:
where Si is the seismic sample value at a particular time on the ith trace within each ID group, and N is the
total number of traces to stack within the group. Amplitude values that are zero are ignored.
634
Alpha-trimmed mean.
The median and alpha-trimmed mean is found by the following formula:
where R is the percentage of traces to reject outside of the median, Si is the seismic sample value at a
particular time on the ith trace after sorting the amplitude values within each ID group, and N is the total
number of traces to stack within the group. When R is 0 the output is the same as the mean. When R is
100% the output is the median. Amplitude values that are zero are ignored prior to the sort.
Median.
The median option internally sets R to 100%, in the equation above.
Power.
This option provides three versions of cross power computations within each ID group. All Power options
may be smoothed in time by a running window smoother.
Power - Semblance.
Semblance is here defined as a Hilbert transform weighted normalized Cross Power. The computation is
identical to that performed by CVA3D.
Power - Cross Power.

Cross Power is the square of the sum of the samples at a given time minus the sum of the squares of the
individual samples.
Power - Normalized Cross Power.

The Cross Power computed above is normalized by the sum of the squares of the individual samples.
Diversity Sum.
A diversity sum weights each trace within a group prior to summation. The weights are defined by a
threshold. The threshold trace within a group is the alpha-trimmed sum of each traces running window
absolute value sum (AGC) multiplied by the threshold factor. When the running window absolute average
values (AGC) of a given trace within the group exceeds the threshold, the AGC function for the trace is
truncated to become the weight function. The summed trace is normalized by the sum of the AGC
functions.
635
References
Haldorsen, J., And Farmer, P., Suppression of high-energy noise using an alternative stacking procedure.
Geophysics, Vol. 54, No. 2, 181-190.
Input Channels
Output Channels
Parameters
Stack Method
Options: Mean, Median, Alpha-trimmed Mean, Power, Diversity Sum
Power Method
This parameter is accessed if Stack Method: is set to Power.
Options: Semblance, Cross Power, Normalized Cross Power
Samples to reject outside of median (%)

This variable is accessed if Stack Method: is set to Alpha-trimmed mean or Diversity Sum.
This is the variable R in the above formula for an alpha-trimmed mean. A value of zero corresponds to the
mean and a value of 100% corresponds to the median value.
Header key
TIM1, TIM2, TLSN, OTHER
636
GCI header index

This variable is accessed if Header key: is set to OTHER.
Header word adder

Header word Divisor
This variable is accessed if Stack Method: is set to Mean, Median or Alpha-trimmed mean.

This variable is accessed if Normalize stack by fold? = Yes.
Options: Square Root of Fold, Fold Plus Next Parm
# to add to fold before divide:

This variable is accessed if Stack Normalization technique = Fold Plus Next Parm.
Ensemble continuation print flag:

If coded Yes, a message will be printed on the listing if the current "sum" may be split between ensembles.
Normalize by fold?
This variable is accessed if Power Method: is set to Cross Power or Normalized Cross Power.
Semblance Smoothing Window(ms):

This variable is accessed if Stack Method: is set to Power.
Minimum Fold:
This variable is accessed if Stack Method: is set to Semblance.
The semblance will be set to "zero" if the number of live samples at any sample time is less than this
value.
637
Diversity Window(ms):
This variable is accessed if Stack Method: is set to Diversity Sum.
Diversity Threshold:
Diversity Suppression:
638
HILBERT
Module Description
Input Channels
Output Channels
Parameters
Module Description
HILBERT will compute various attributes using the Hilbert transform. When displaying the result of
HILBERT, it is suggested that you select Automatic scaling? = Yes in module DISPLAY.
Input Channels
Output Channels
Parameters
Instantaneous attribute
Options: Amplitude, Phase, Frequency
# points in running window filter

Required if Instantaneous attribute = Frequency.
639
HIP
Module Description
Parameters
Module Description
Use this module to interpolate interpreted horizons. A horizon value will be computed by triangulation for
every CMP that does not currently have a defined pick.
Parameters
Horizons matrix (Deprecated)
This parameter is deprecated. Select a matrix name only to convert it to the new format
Interpolate all horizons?

Horizon to interpolate
Midpoint bin number increment
Midpoint line number increment
640
HMTH
Module Description
Input Channels
Output Channels
Parameters
Module Description
Header Math. See HMTH matrix definition.
Input Channels
Output Channels
Parameters
Equations
Matrix Type: HMTH
641
HORIZON
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program HORIZON is used to set matrix-defined times in the trace header to be used by other programs.
Examples of use would be to simplify defining deconvolution start times, mute times or gain curve
application times by defining a matrix of times relative to water travel time vs. CMP in marine data. Two
different matrices may be specified and times stored in the header as TIM1 and TIM2.
Input Channels
Output Channels
Parameters
Use interpreted horizons?
Options: Yes, No
Select Yes to use previously picked post-stack horizons. Select No to use the horizon matrix.
Horizon:
Enter the previously picked post-stack surface horizon.
Primary header key

TLSN
642

TLSN
Time horizons
Place time in header

Options: TIM1, TIM2
643
Module HORZIMP
NAME
HORZIMP - Import horizons into matrix
DESCRIPTION
Module HORZIMP is used to import horizons into the SeisUP matrix. The following is part of an example
Landmark horizon file with 5 columns:
1273.00 1284.00 1229869.50 355463.00 3288.8570
1275.00 1282.00 1229979.50 355573.00 3287.3333
1281.00 1278.00 1230309.50 355793.00 3292.8000
1283.00 1282.00 1230419.50 355573.00 3299.1428
1283.00 1276.00 1230419.50 355903.00 3301.5000
Sometimes horizon files only have 3 columns like below:
1273.00 1284.00 3288.8570
1275.00 1282.00 3287.3333
1281.00 1278.00 3292.8000
1283.00 1282.00 3299.1428
1283.00 1276.00 3301.5000
or:
1229869.50 355463.00 3288.8570
1229979.50 355573.00 3287.3333
1230309.50 355793.00 3292.8000
1230419.50 355573.00 3299.1428
1230419.50 355903.00 3301.5000
644
TYPE
Stand Alone
INPUT CHANNELS
1. Horizon file
Required
ASCII data type
OUTPUT CHANNELS
None
PARAMETERS
Horizon name
Enter the HORIZON matrix name.
Primary key for horizon

Number of columns in horizon file
Are there MLIN/MBIN info?
Column number for MBIN
Required if Are there MLIN/MBIN info? = Yes.
Data format for MBIN

Column number for MLIN

645
Data format for MLIN

Column number for X coordinates

Required if Are there MLIN/MBIN info? = No.
Data format for X coordinates

Column number for Y coordinates

Data format for Y coordinates

Column number for Time/Depth

Data format for Time/Depth
Scaling factor for Time/Depth
646
HSUM
Module Description
Input Channels
Output Channels
Parameters
Module Description
HSUM performs trace-to-trace summing to reduce the number of traces. Only live, dead, and dummy
traces are summed. Two input traces are summed to produce one output trace. Auxiliary traces are passed
unsummed. HSUM requires RMS velocities to apply the partial NMO before summing.
More than two traces may be summed if:
1. There are duplicate FCSN traces
2. FCSN increment is not correctly specified
Input Channels
2. VIP velocity database
Optional
SEGY data type
GCI data type
Output Channels
Parameters
Input trace increment in FCSN
RMS velocities
Matrix Type: RMSVEL
647
IDLINBIN
Module Description
Parameters
Module Description
IDLINBIN prints mbin and mlin numbers associated with the xcoordinates and the ycoordinates values in
the execution status list. It also prints the distance from point to mbin/mlin center
Parameters
Use Xcoord and Ycoords list?
Yes or No options are available. If Yes option is selected, the user is asked to enter matrix name to enter
the coordinates. If No is selected then user can enter the xcoordinate and the ycoordinate in the text fields.
Midpoint matrix name

The IDLINBIN uses this matrix to input the xcoordinates and the ycoordinates.
Enter X coordinate to match

This is a text field for user input of xcoordinate.
Enter Y coordinate to match

This is a text field for user input of ycoordinate.
648
IDRENUM
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module renumbers record IDs to unique ID numbers. This module differs from UNDUPE in that it
will track individual ID numbers and only add the user specified increment value when a second
occurrence of that number is found rather than add the increment value to all ID numbers when any
duplicate record number is found.
Input Channels
Output Channels
1. Output: No connection is required, but renumbering will not be saved unless output to a flow with a
WRITE to dataset. Connection must be to GCI data type.
Parameters
Maximum number of records in dataset
This parameter is required for memory allocation. Any number larger than the total number of records is
sufficient.
Value to be added to create unique ID

This is the value that will be added to duplicate records.
Duplicate into "sets"?

If YES the increment value will only be added when a new occurrence of a user specified ID is found. The
increment value will then be added to everything after that occurrence until the next occurrence is found.
This has the effect of splitting record numbers into "sets" when the record numbers repeat themselves
more than one time.
649
ID to start "sets"
If duplicating into "sets" this parameter is the record number that starts each new set.
650
IF
Module Description
Input Channels
Output Channels
Parameters
Module Description
IF is the starting tool for selected traces to be processed between IF and ENDIF. ENDIF has menu
parameters that determine what traces are processed. The only parameter for IF is the storage file name
that connects IF with ENDIF. This file name should be something like: /tmp/LARRY-IF-ENDIF4 for both
modules. This puts a temporary file in the /tmp directory and IDs it to an IF - ENDIF pair using the 4.
NOTE: No module between IF and ENDIF may change the sample rate , number of samples or number of
traces per ensemble. Also, no module may hold an ensemble, ie, all modules must process every trace
passed in on the same call.
Input Channels
Output Channels
Parameters
IF ensemble storage file name (full path)
Example: /tmp/LARRY-IF-ENDIF4
651
IMPHORZ
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module IMPHORZ is used to import interpreted horizons into the SeisUP database. Interpreted horizons
can be used by modules such as GEOVEL, and ISOV. The following is part of an example Landmark
horizon file:
1273.00 1284.00 1229869.50 355463.00 3288.8570
1275.00 1282.00 1229979.50 355573.00 3287.3333
1281.00 1278.00 1230309.50 355793.00 3292.8000
1283.00 1282.00 1230419.50 355573.00 3299.1428
1283.00 1276.00 1230419.50 355903.00 3301.5000
Input Channels
1. Horizon file: Optional connection from dataset ASCII data type.
Output Channels
Parameters
Horizon option
Select the option for the horizon to be written to the database.
Options: New, Replace
652
New horizon name

Enter the name to be associated with the horizon to be imported.
Horizon to replace
Select the horizon to be replaced.
Input horizon format

For a userspecified horizon format, the user will be requested to input the column number in the ASCII
file for the horizon information. For a SeisUP specified horizon format, the user will be requested to input
the matrix in a format used by the HORIZON module. If the SeisUP format is used, make sure the primary
and secondary dimensions correspond to the trace header words MLIN and MBIN respectively.
Options: Landmark, User, SeisUP
Input SeisUP depth/time horizons

Enter the HORIZON matrix for the desired horizon to input. Make sure the primary and secondary
dimensions correspond to the trace header words MLIN and MBIN respectively.
Import using
If Coordinates is selected, this module will compute the midpoint bin and line using the current CMP
geometry parameters. This parameter is only available when the pick times are being imported from an
ASCII file.
Options: CMP #s, Coordinates
Column for MLIN

If the Input horizon format is User, enter the column number starting from one for the inline midpoint bin
number.
Column for MBIN

If the Input horizon format is User, enter the column number starting from one for the cross-line midpoint
line number.
653
Column for X coordinate

If the Input horizon format is User, enter the column number starting from one for the CMP X coordinate.
Column for Y coordinate

If the Input horizon format is User, enter the column number starting from one for the CMP Y coordinate.
Column for the horizon depth/time

If the Input horizon format is User, enter the column number starting from one for the interpreted pick
time. The pick time should be in milliseconds.
654
IMPLS3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use module IMPLS3D to create a synthetic for impulse response tests. IMPLS3D will create a pre-stack
common offset or stack volume where all traces are zero except for the middle trace.
Parameters
Offset (0=stack)
Source-receiver azimuth (degrees)
Length of traces to process (ms.)
Input sample rate (us.)
First impulse (ms.)
Increment between impulses
Impulse type
Options: ricker, spike
655
Peak frequency of the wavelet

Required if Impulse type = ricker.
656
INTGRT
Module Description
Input Channels
Output Channels
Parameters
Module Description
INTGRT does seismic trace integration to obtain an uncalibrated relative acoustic impedance in the
absence of well log calibration. A bandpass filter is applied to the input data. The trace is integrated and
scaled based on the minimum and maximum velocity information and RMS level. The output is filtered
using the post-integration low and high frequencies.
Input Channels
Output Channels
1. Pseudo log: Required connection to next process GCI data type.
Parameters
The following two filters produce fairly sharp cutoffs in the spectrum.
657
Low frequency on output (Hz)

High frequency on output (Hz)
RMS level of reflectivity
Reasonable values for this parameter are 0.02 - 0.05. It controls part of the trace scaling logic. Too large a
value will cause large amplitude low frequency events.
658
INVEL
Module Description
Input Channels
Output Channels
Parameters
Module Description
INVEL adds low frequency (velocity) information into (integrated) seismic traces.
Input Channels
Output Channels
Parameters
High pass frequency for velocity(Hz)
High cut frequency for velocity(Hz)
Average bulk density(metric unit)
RMS velocities
Matrix Type: RMSVEL
659
INVERSN
Module Description
Input Channels
Output Channels
Parameters
Module Description
INVERSN will compute a post-stack or pre-stack acoustic impedance inversion of seismic data. The
module will compute pseudo acoustic impedance, wide-band acoustic impedance, pseudo interval velocity
trace, wide-band reflectivity, sparse-spike reflectivity, or sparse-spike acoustic impedance on post-stack
seismic data. It also computes elastic impedance on pre-stack angle gather CMP data.
Input to the module for can be any kind of seismic data ensemble and a low frequency interval velocity
set. Output will be either: acoustic impedance, wide-band acoustic impedance, pseudo interval velocity
trace, wide-band reflectivity, sparse-spike acoustic impedance, or sparse-spike reflectivity.
For elastic impedance calculations, input should be a CMP gather that has been run through angle stacks
(XAVA). The output will be the acoustic impedance inversion for each trace in the gather. The output data
can be run through other tools (ELASTICP) to compute the elastic parameters Vp, Vs, and density.
This module attempts to combine low frequency velocity information obtained from a sonic log or
stacking velocities with the higher frequency seismic data. The output can be a trace representing acoustic
impedance, wide-band acoustic impedance, interval velocity, or wide-band reflection coefficients. For best
results, the data should be multiple free, zero offset, migrated, and preferably zero-phased. The spectrum
of the seismic trace should be flat within the zero to Nyquist range.
For the acoustic impedance and wide-acoustic impedance output, a scaling factor can be applied to the
output data. Two methods are supported. Trend Removal will attempt to remove the low velocity trend in
the data. In this method, the module subtracts a smoothed version of the trace and scales by the maximum
amplitude difference. Trend Averaging attempts to scale the low-velocity trend by using an average trend
value. For trend averaging, an average trend for the data is computed at the first line (ensemble). Then all
traces are scaled by this value. The user can override the average trend value in the menu by input a value.
The acoustic impedance computation can be started at a user specified value to aid in tying well logs or
other data types.
This module uses the recursive formula (trace integration) to compute acoustic impedance. The trace
integration will output the data at a lower frequency range than the original input data. To compensate for
this, two options have been added for frequency enhancement: Ricker wavelet, and RHO filtering. The
RHO filter reverses the frequency effects of integration by providing a frequency proportional amplitude
boost. The Ricker wavelet uses a dominant frequency to boost the amplitudes around the dominant
frequency.
660
This module convolves the estimated acoustic impedance series with the chosen frequency enhancement
filter to produce a frequency-enhanced inversion. The equations used to build the acoustic impedance log
is:
c(k) = ( r(k-j) * p(j) )
ac(k+1) = ac(k) * (1 +
c(k)) / ( 1 - c(k))
where:
ac(k) - the acoustic impedance at element k.
c(k) - the estimated band-limited reflection
coefficient at element k.
r(k) - the reflection coefficient from the seismic
trace at element k.
p(j) - the filter value at element j.
One option is to output an acoustic impedance or wide-band acoustic impedance trace. When velocity is
the primary value that indicates porosity, the acoustic impedance section can give clues to porosity
changes. The wide-band option takes the low frequency information from the velocity data and combines
it with the acoustic impedance to produce a wide-band acoustic impedance trace.
Another option is to produce an interval velocity trace. The seismic trace is integrated in the time domain
to produce an estimate of the maximum sonic log/stacking velocity frequency. The output pseudo interval
velocity trace will be band limited at the high frequency of the seismic trace. This option can be useful to
output a better stack or cube of interval velocities for the survey.
Another option is to produce a wide-band reflectivity series. This method assumes that the wide-band
reflectivity is the sum of the reflectivity derived from the low frequency interval velocity information and
the seismic trace high frequency information. The interval velocity trace and the seismic trace are
transformed to the frequency domain where they are added together to produce an estimate of the
wide-band frequency domain reflectivity series. This option is useful to output seismic data that matches
the well logs better.
A new option is to output sparse-spike reflectivity. The module will also compute sparse-spike acoustic
impedance using the standard acoustic impedance equation and the sparse-spike reflectivity. The
sparse-spike reflectivity series displays a minimum of structural variation. Such an algorithm can be used
to pick out major features in the acoustic impedance structure. Using a portion of the reliable frequency
spectrum the algorithm is good at estimating the high and low frequency content of the data. This helps in
constructing a broad-band acoustic impedance structure.
The sparse-spike solution uses a Simplex algorithm to reconstruct a sparse-spike series using a portion of
the spectrum. A linear relationship is built between the Fourier transform of the reflectivity function and
the reflection coefficients. Linear programming is used to minimize an objective function using constraints
such as polarity, weights, real and imaginary parts of the spectrum. The user enters the reliable portion of
the spectrum. Typically, this should center on the dominant frequency of the signal in the zone of interest
and include frequencies with high signal to noise ratio.
661
The user can adjust the amplitudes of the input data prior to the inversion. For best results, the final
maximum reflection coefficient (after scaling) should be less than 0.3 in the seismic data. A parameter,
Maximum RMS reflection coefficient value, is provided to help adjust the data below the 0.3 maximum.
The computed scalar is multiplied times the seismic data. A scalar can be computed for an entire
ensemble, a single trace, a user defined scalar, or no scalar applied.
The user can balance the acoustic impedance trace-to-trace by applying output scaling. The options are for
trend removal, trend averaging, or none. In the case of trend removal, the low-frequency trend of the data
is removed leaving acoustic impedance that is centered on zero. This will give a normal seismic trace look
to the data. In trend averaging, the trend is removed as in trend removal, but in the end, the low frequency
trends are averaged over a user specified trace range and then added back in. This give good balance to the
acoustic impedance trace-to-trace while at the same time, leaving the low frequency trend in the data. In
none, nothing is done to the acoustic impedance output data.
This module operates on a single trace at a time. Normally, you will input 2D or 3D stacked data. The
module will allow to you input any sort type including pre-stacked data.
A Hanning window can be applied to the wide band acoustic impedance or reflectivity series to prevent
ringing due to abrupt truncation of the data. This ringing is know as Gibbs phenomenon
The velocity information can be entered by either a matrix of RMS velocities or a VIP dataset. The
velocities can be derived from the stacking velocities used to stack the seismic data or can be computed
from a sonic long. The module can accept a matrix of velocities or you can connect the output from the
VIP module. If you connect a VIP dataset to the module, the VIP velocities must be interval velocities. If
you are inputting data from a matrix, then the matrix velocities must be RMS velocities. The module will
convert the RMS velocities to interval velocities in this case.
The module can perform the inversion over a window. The user has the option to select the starting and
ending window times. You should try to avoid the mute zone and zones that contain zeroes.
References:
K.A. Berteussen, B. Ursin, 1983, Approximate computation of the acoustic impedance from seismic data,
48, pages 1351-1358.
S. Levy, P.K. Fullagar, 1981, Reconstruction of a sparse spike train from a portion of it spectrum and
application to high-resolution deconvolution, 46, pages 1235-1243.
D.W. Oldenburg, T. Scheuert, S. Levy, 1983, Recovery of the acoustic impedance from reflection
seismograms, Geophysics, 48, pages 1318-1337.
Input Channels
662
Output Channels
Parameters
Inversion output
Select the output data type.
Options: Acoustic Impedance, Wide-Band Acoustic Impedance, Interval
Velocity, Wide-Band Reflectivity, Sparse-Spike Acoustic Impedance,
Sparse-Spike Reflectivity
Frequency enhancement filter

Select the frequency enhancement filter or None for no frequency enhancement. The output acoustic
impedance trace is convolved with the filter to enhance frequencies removed during the integration
process. For sparse-spike acoustic impedance, it is best to not perform frequency enhancement.
Options: Band-limited using Ricker wavelet, RHO filter, None
Peak frequency of the wavelet (Hz)

Enter the dominant frequency of the wavelet in Hertz. This option appears if the band-limited Ricker
wavelet option is chosen for frequency enhancement. The peak frequency should correspond to the
dominant frequency in the seismic data. This frequency is used to create a Ricker wavelet, which is
integrated with the seismic data to produce a band limited acoustic impedance response.
Output trace scaling method

The acoustic impedance trace can be scaled using several methods. The first method, Trend Removal,
attempts to remove the low frequency trend of the data by subtracting a smoothed version of the trace and
then scaling by the maximum amplitude. This will force the data to be centered on zero, which give the
acoustic impedance output a normal seismic appearance. The second method, Trend Averaging, attempts
to keep the low frequency trend in the data but first removes it and then averages it over a known number
of traces before adding it back in. This should give good balance to the acoustic impedance output. In
none, nothing is done to the acoustic impedance output.
Options: Trend Removal, Trend Averaging, None
663
Time window for smoothing (ms.)

The window length in milliseconds to get a smoothed version of the trace at a specific sample. This
smoothed value is subtracted from the trace for trend removal and averaged for the trace in trend
averaging. This parameter appears only if the output is acoustic impedance and the output trace scaling is
trend averaging or trend removal.
Number of traces for averaging (traces)

The number of traces to sum for the average trend that is being added back into a single acoustic
impedance trace. If the trend averaging is selected for output scaling of the acoustic impedance traces. The
low frequency trend is removed from the data as in trend removal. But for trend averaging the low
frequency data is averaged over this number of traces and then added back in. This should balance the
acoustic impedance values from trace-to-trace.
Starting acoustic impedance value

To tie the computed acoustic impedance to well logs or other data a starting acoustic impedance value can
be specified. The recursive formula will begin at this value. The units of this value will be gm-ft/cc-sec or
gm-m/cc-sec.
Highest frequency of interest in velocity data (Hz)

If the wide-band acoustic impedance or reflectivity series is chosen above then enter the highest frequency
to use in the velocity data in Hz. Typically less than 5 Hz, too high of a value will incorrectly bias the
output. Too low of a value will leave out information that would improve the match between the
reflectivity series and the sonic log.

When computing the wide-band acoustic impedance or reflectivity series, a Hanning window can be
applied. A Hanning window prevents ringing of the data due to abrupt truncation when applying a window
to the input trace. The Hanning window will prevent what is know as the Gibbs Effect.
Number of samples in a computation window

The sparse-spike series should be computed in small windows. This parameter allows you to specify how
many samples are in a window. The complete trace is then broken into windows of the size. The
sparse-spike series is computed for each window separately.
Lowest reliable frequency (Hz)

The sparse-spike series can be computed from a portion of the Fourier spectrum. Enter the lowest
frequency in hertz that is reliable in the data. This is typically the lowest frequency of the signal you are
trying to preserve. Not the noise. A hint might be to center the dominant frequency of the signal in the
high and low values. The reliable frequency band will typically be the data with the highest signal-to-noise
664
ratio.
Highest reliable frequency (Hz)

The sparse-spike series can be computed from a portion of the Fourier spectrum. Enter the highest
frequency in hertz that is reliable in the data. This is typically the highest frequency of the signal you are
trying to enhance. The reliable frequency band will typically be the data with the highest signal-to-noise
ratio.
RMS velocities
Select the RMS velocity matrix. If you are connecting a VIP module output then you can leave this field
blank. The VIP velocities must be interval velocities. When the input is from a matrix, the RMS velocities
will be converted to interval velocities.
Matrix Type: RMSVEL
Start time (ms.)

Enter the start time of the inversion in milliseconds. This time should usually be below the mute time of
the stacked data. This value should be set to avoid zeros in the data.
End time (ms.)

Enter the end time of the inversion in milliseconds. This value should be set to avoid zeros in the data.
Input trace scaling method

The input seismic data should be scaled prior to the inversion. For best results, the estimated reflectivity
from the traces should be less than 0.5. A scalar can be computed for an entire ensemble, a single trace, or
a user defined values. The computed or entered scalar is multiplied times the seismic data values. If
scaling has been done prior, then the user can choose to perform no scaling.
Options: Ensemble, Single Trace, User Defined, None
Maximum RMS reflection coefficient value

Enter the expected RMS reflection coefficient as estimated from the sonic log. This value is used to scale
the seismic traces. If you are obtaining velocities or amplitudes that are too high then reduce this value or
if the values are too low then increase this value. For best results, the estimated reflectivity from the traces
should be less than 0.5.
665
Scalar to apply
If the input scaling option above was User Defined, then this parameter appears. Enter the scalar to apply
to the whole data set. The scalar is multiplied times the seismic data values.
666
ISOV
Module Description
Input Channels
Output Channels
Parameters
Module Description
The program ISOV creates the iso-velocity profiles for 2-D or 3-D surveys and time slices for 3-D
surveys. Optionally a fourth order term may be plotted. Velocity input is from a previously existing
matrix. Interpolation between input points is linear for 2-D and tri-linear for 3-D using triangulation.
Plotting scales and number of contour levels may be chosen. The velocity resolution may be refined to
create a smoother plot. When 3-D is selected, matrices of midpoint lines, midpoint bins and time slices to
extract need to be defined. Optionally if interpreted horizons are available, the horizons will be overlaid
over the velocity section. For 3-D areas, the velocities will be extracted at the horizons and plotted. Output
is a CGM file.
Input Channels
1. Vip velocity dataset: Optional connection from dataset SEGY data type.
Output Channels
1. Output: Required connection to dataset CGM data type.
Parameters
Input velocity model type
Options: Time model, Depth model
Plot fourth order correction?

Fourth order terms.
Matrix Type: 4THNMO
667
RMS velocities
Matrix Type: RMSVEL

Inches per second
Colormap:
Plot Direction
This parameter is available only for 2-D areas.
Velocity resolution (ms.)

Decrease this value to decrease any stair-stepping effects in the plot.
Title
Fourth order Title
Colorbar options:
Velocity corresponding to minimum contour
Velocity corresponding to maximum contour
Fourth order corresponding to minimum contour
668
Fourth order corresponding to maximum contour

Use interpreted horizons?
Select Yes to overlay the interpreted horizons over the inline and cross-line profile plots. For 3-D areas,
the velocity will be extracted at each horizon and plotted. See below if the user wishes only to plot
selected horizons.
Interpreted Horizons matrix (Depricated)

This parameter is depricated. Select a matrix name only to convert it to the new format
Show parameters for survey type

Options: 2-D, 3-D
Midpoint lines to extract

Matrix Type: "ISOVLINS
Midpoint bins to extract

Matrix Type: ISOVBINS
Midpoint time slices to extract

Matrix Type: ISOVTIMS
Midpoint horizon slices to extract

If interpreted horizons are available, the default will be plot the velocities at all horizons. If only selected
horizons are desired, enter the horizon index in the following matrix.
Matrix Type: ISOVHORS
669
IVEP
Module Description
Changes to User Interaction / Default Parameters
Input Channels
Output Channels
Parameters
Module Description
IVEP (Interactive Velocity Estimation Program) is used to pick RMS velocity and NMO mute curves.
Notice: updates from IVEPs initial release version (SeisUP 2007) include changes to mouse button
functionality and default parameters. Please see section "Changes to User Interaction / Default
Parameters" for more information.
The input data set is created using CVA3D, similar to creating a data set for GEOVEL, EXCEPT you
must set the Output dataset format parameter to GCI.
Once the job is started a survey map, showing the midpoint grid and analysis points will be displayed, as
shown above. Unlike this figure all of the analysis points will initially be the same color. When a point is
selected for picking it will be shown with a red circle around it and the four neighboring points will
change in color. Analysis points where velocities have been picked will have a little red circle attached to
the upper left corner of its X.
Survey Map
670
To start the picking process at an analysis point either double click over it, or select the pick by clicking
over it once then using the "Pick" button in the right side toolbar, doing this will bring up two more
windows, displaying the gather and semblance views. You may simply click the "Pick" button without
first selecting an analysis point to start at the first point.
The analysis points may be navigated by using the directional arrow buttons in the right side toolbar.
The middle button will allow you to seek to an ensemble.
The preferences button, found in the right side toolbar labeled "Prefs.", will bring up a window from
which the user may change the appearance of components in the map, such as the background or analysis
point color. Also, you can toggle or change the color of the neighboring velocity curves. On the "Mouse"
tab of the Preferences window the user may toggle "Show Semblance/CVS Crosshairs". When toggled on,
crosshairs will be displayed in the CVS View while the mouse is over the Semblance view and vice versa.
Analysis Window
671
Once an analysis point is selected for picking the associated seismic views will be displayed, as seen in the
figure above. Each panel may be resized horizontally by dragging the dividing bar. Further, using the
icon the gather or CVS panels may be detached from its window, creating a new window containing
just that panel.
Gather, Semblance and CVS Views

Unlike GEOVEL, the gather will be interactively updated when picks are altered. NMO correction may be
toggled using the button with the red triangle. Just above it is the button to toggle mute picking in the
gathers. When NMO correction is turned on the guide function will be a straight line, but when off the
NMO hyperbola will be shown.
Navigate though the analysis points using the directional arrow buttons on the right side toolbar. Clicking
the "i" button will bring up the "inspector" for the corresponding seismic view. From this window the
gain, trace scale, sample scale and other common display preferences may be defined. You may set the
trace or sample scale to 0 to "Fit Section".
672
To interactively modify the semblance views color map double click, or right click the visual spectrum
bar shown in the lower right corner of the window, then select "Edit color table" from the contextual
menu.
Velocity and Mute Picking.

New picks are introduced by simply clicking in the semblance view. Hold down "ctrl" and then click to
"autopick" a point. Click and drag a pick to move it horizontally (in the velocity direction). Move a pick in
the time direction by holding down "shift", then click and dragging it. When the mouse is close enough to
drag a pick the cursor will change from the standard arrow to a hand icon. To remove the pick nearest the
cursor click the middle button. The nearest pick will be highlighted in blue. To move the pick to the
location of the cursor right click. Picking in the CVS view is identical.
Mute picking is similar except, by default, mute picks may be dragged in the time direction but not in the
offset direction. An interpolated guide function will be displayed in blue between analysis points where
the user has defined mute picks.
Color Table Editor
673
From the Color Table Editor window you may manipulate, load and save color tables (also known as color
maps). Along the left side of the window you see the color gradient, which is defined by the "color stops".
Click and drag the color stop arrow to make fine-tune changes to the gradient, or double click on it to
change its color. To insert a new color stop simply double click to the right of the gradient where you want
it inserted. Remove a color stop by selecting it then clicking the "Delete" button. You may shift all of the
color stops using the "Rotate" slider. The default number of colors is 256. You may reduce this to make
the gradient less smooth.
The "Presets" box will contain the four standard color maps shown here and then any you personally
create. To load a preset color map simply double click on it. After making changes you may want to save
it for future use - to do so rename it in the "Name" field, then click the "Save" button. The color map will
be stored in your home directory in folder: .seisup/gradients. However, the created colormap will not show
up in the "Presets" box until the next time you run the application.
674
Velocity Cube View / Picking Alternative Correction Terms
675
When making
picks for an
alternative
correction
method the
standard
time-velocity
semblance panel
is replaced by
two panels
which are used
to visualize the
velocity cube.
The example to
the right shows a
time-velocity-eta
cube visualized
by a
time-velocity
semblance panel
(on top) which is
movable in the
eta direction and
a velocity-eta
time slice (on
bottom) which is
movable in the
time direction.
When a pick is
made in the
semblance panel
the time slice is
moved to the
time at which
the pick was
made. In the
figure to the
right a pick was
made at time
694ms, so the
time slice below
is moved to
display the
velocity-eta field
at time 694ms.
Also, notice a
horizontal blue
line is draw
across the
semblance panel
at that time. At
this point the
user could adjust
the velocity and
eta of the pick
by clicking in
the time slice at
the desired
location.
To move to a
different time
slice without
making a pick
the user can
double-click in
the margin to the
left of the
semblance
panel. The user
can also
double-click in
the left side
margin of the
time slice to
update the eta
value for which
the semblance
panel is
displaying. In
the figure to the
right the
semblance panel
is shown at eta =
119. Notice the
blue horizontal
bar across the
time slice at eta
119. Instead of
double-clicking
in the left side
margin to set the
time or eta value
to be viewed, the
user can click
and drag the red
arrow icon in the
left side margin.
676
Changes to User Interaction / Default Parameters

Version 2007 to 2008: The default gain was changed from 10 to 0. This change is partially offset by
the addition of a Reference mean parameter.
Version 2007 to 2008: Mouse middle button was move pick changed to delete pick.
Version 2007 to 2008: Mouse right button was remove pick changed to move pick.
Input Channels
Output Channels
None
Parameters
Picked velocities are stored in the given matrix.
Matrix Type: RMSVEL
Matrix for HTI velocities

Picked velocities are stored in the given matrix.
Matrix Type: EVEL
Alternative correction matrix

Pick alternative correction terms to be stored to matrix, or import previously picked terms from matrix.
Options: None, Pick Anisotropic-VTI, Import Anisotropic-VTI, Pick
Anisotropic-HTI
Matrix for ETA terms

When parameter Alternative correction matrix is set to Pick Anisotropic-VTI the picked ETA
correction terms are stored in the given matrix. To pick ETA terms the input data set should be created by
CVA3D with its parameter Use 4th order(eta) NMO equation? set to Yes.
677
When parameter Alternative correction matrix is set to Import Anisotropic-VTI the given ETA
correction terms are applied. This allows the user to re-pick velocities without changing the given ETA
terms. In this case the input data set should be created by CVA3D with its parameter Import a ETANMO
matrix? set to Yes and given the same ETANMO matrix as given here.
Matrix Type: ETANMO
V-slow axis orientation

Velocity for t0 pick
A pick will be made automatically for the given velocity at time = 0. The default will set the velocity at
time zero to equal the first velocity picked by the user.

The height (in milliseconds) of the autopick window (default = 500).
Autopick window (velocities)

Width (in velocity) of the autopick window. The default is to search the entire velocity field for maximum
amplitude.
Mute Matrix Type

Choose the type of matrix to store mute picks or No Mutes to disable mute picking.
Options: No Mutes, NMOMUTE
NMO Mutes
Picked mutes are stored in the given matrix.
Time for nearest offset mute

A mute pick will be made at the given time for the nearest offset. The default will set the mute time at the
nearest off equal to the first mute time picked by the user.
Traces per inch

Number of traces displayed per inch in the gather and constant velocity stacks panels (default = 24). If set
to 0 the traces will fit the section.
678
Inches per second

Inches of data displayed per second in all seismic panels (default = 1.5). If set to 0 the traces will be scaled
to fit the section.
Gain (db)
The amount of gain in db to apply to the gather and constant velocity stacks before plotting (default = 0).
Clip (traces)
clipped (default = 1.5)
Reference mean
Select a reference mean value, so all traces in the dataset are in the same mean range (default = 2500). The
reference mean is applied to the gather and constant velocity stacks, not semblance.
Semblance Traces per inch

Number of traces displayed per inch in the semblance panel (default = 10), If set to 0 the traces will fit the
section.
Semblance gain (db)

The amount of gain in db to apply to the semblance before plotting (default = 0).
679
KAPTURE
NAME
KAPTURE - Kirchhoff migration aperture
DESCRIPTION
KAPTURE is a stand alone module which computes and prints out the aperture of Kirchhoff migration.
TYPE
Stand alone
INPUT CHANNELS
None
OUTPUT CHANNELS
None
PARAMETERS
RMS velocities:
Default .....:
Name ........:vfile
Matrix type .:RMSVEL
Time variant dips:

Default .....:
Name ........:dfile
Matrix type .:TVDIP
680
Velocity percentage to use:

Default .....:100.0
Name ........:vper
Type ........:Float
Min .........:50.0
Max .........:200.0
The lesser of BIN or CMP intervals:

Default .....:
Name ........:dx
Type ........:Float
Min .........:
Max .........:
Trace length (ms):

Default .....:4000
Name ........:ltrc
Min .........:
Max .........:
Output aperture every (ms):

Default .....:100.0
Name ........:dtms
Type ........:Float
Min .........:
Max .........:
AUTHOR
Created on Jun 22,1993
681
KFIL
Module Description
Input Channels
Output Channels
Parameters
Module Description
KFIL will perform high cut K filtering (Spatial filtering) with a 15 point roll-along filter. KFIL assumes
that there is an even trace spacing between traces. Up to five filters and their corresponding start and stop
times may be chosen. As shown below, the 100% response point is equivalent to the "High Pass"
frequency, and the 0% response point is the "High Cut" frequency.
100% Response Point Corner
A
|
Frequency
_____________________
/
|
\
Reject
/
Pass
|
Pass
\
Reject
/
|
\
/
|
\
_______________________________________________
-.5
0
+.5
K
0% Response Point
Corner Frequency
Example if in F-K spectrum:

K
(K = 1/X)
-.5
-.33
0
.33
+.5
__________________________________________
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
F
|
|
|
|
|
|
|
|
|
|
50|--------|----------|-----------|--------|-KFIL
|
|
|
|
| would
|
|
|
|
| reject
|
|
|
|
| frequencies
Nyquist|--------|----------|-----------|--------|-over 50 Hz.
|
All traces are
peak to trough
|
|
|
All peaks aligned
|
|
---------KFIL would reject
Frequencies in
traces that had
peak to trough
over three traces
or less.
682

Ramp
|<->|
Ramp
|<->|
_______________
_______________
_______________
|
|\ /|
|\ /|
|
|
Filter #1
| X |
Filter #2
| X |
Filter #3
| ...
|_______________|/ \|_______________|/ \|_______________|
^
^
^
^
^
^
0
End1
Start2
End2
Start3
End3
Input Channels
Output Channels
Parameters
Time variant?
100% Response point corner frequency

Primary header key

TLSN
683

TLSN
Low cut K filters

Matrix Type: KFIL

Restore amplitude?
Amplitude restoration Window (ms.)
Subtract filtered output from input?
684
KTMIG
Module Description
Input Channels
Output Channels
Parameters
Module Description
KTMIG performs Kirchhoff 2-D/3-D prestack/poststack time migration. It has the following features:
Option to produce migration stack or migration gathers,
Migration from datum, topography, or any floating reference,
Anti-aliased migration operator, with two different anti-alias filter option
Target-oriented migration,
Multithread parallel processing,
Multinode parallel processing, and
Restart after an abnormal exit.
Input trace headers
The following input trace headers are used in KTMIG. They must be filled properly before KTMIG. For
prestack migration, module GEOM can create these headers. For poststack migration, module MIDGEOM
has to be applied before KTMIG if the input data are not stacked through normal SeisUP flow.
Word Name Description
8 TRID Trace identification code: 1 = seismic data
2 = dead 3 = dummy 4 = time break 5 = uphole
6 = sweep 7 = timing 8 = water break 9 = auxiliary
10 = label (ASCII)
12 DIST Distance from source point to receiver group
(Used for prestack migration only).
13 EG Receiver group elevation
(Used for prestack migration from topography only).
14 ES Surface elevation at source.
(Used for prestack migration from topography only).
21 Scalar to be applied to all coordinates. If positive,
scalar is used as a multiplier; if negative, scalar
is used as a divisor.
22 SX Source coordinate - X
23 SY Source coordinate - Y
24 GX Group coordinate - X
25 GY Group coordinate - Y
66 MBIN Midpoint bin #. This is the sequential midpoint
number within a midpoint line. This is the same as
SDPN for 2-D lines.
67 MLIN Midpoint line # (Used for 3-D only).
74 MCX Midpoint cell center coordinate - X
75 MCY Midpoint cell center coordinate - Y
685
80 DMODIST Distance from source point to receiver group

assigned by module COFF.
(Used if parameter Has pre-migration normalization
been applied? is Yes. It is also used if the
input data is sorted as Primary Key: DMODIST;
Secondary Key: MLIN/MBIN; and Tertiary Key: MBIN/MLIN,
and the output option is selected as offset sections.)
Output trace headers

The following trace headers are created by KTMIG for the output.
Word Name Description
1 TLSN Trace sequence number
6 SDPN Sequential common midpoint number
7 CDPN Trace number within the CDP ensemble (each ensemble
starts with trace number one).
8 TRID Trace identification code: 1 = seismic data 2 = dead.
12 DIST Offset distance
21 Scalar to be applied to all coordinates. If positive,
scalar is used as a multiplier; if negative, scalar
26 Coordinate units: 1 = length (meters or feet)
2 = seconds of arc.
37 MUTST Mute time -- start. in samples
38 MUTEND Mute time -- end. in samples
39 Number of samples in this trace
40 Sample interval in microseconds for this trace
53 DC Datum elevation at depth point
54 MSFL Midpoint starting flexible line number
55 MEFL Midpoint ending flexible line number
66 MBIN Midpoint bin #. This is the sequential midpoint
number within a midpoint line. This is the same as
SDPN for 2-D lines.
67 MLIN Midpoint line #. This is the sequential midpoint
line number.
74 MCX Midpoint cell center coordinate - X
75 MCY Midpoint cell center coordinate - Y
79 FOLD Number of traces summed by NMO stack or partial stack
83 EC CMP surface elevation
Absorbing boundary
There are two ways to specify the absorbing boundary to reduce the edge artifacts. If a matrix of the CMP
fold is specified, the program will apply a taper around the boundary of the non-zero fold. Otherwise, the
taper is applied around the user defined boundary.
Migration velocity analysis
The following steps show the work flow option provided by SeisUP for migration velocity analysis.
1. KTMIG - Produces migration gathers at selected CMPs using DMO or stacking velocities.
2. NMOA - Applies the inverse NMO correction with the same velocities used for step 1.
3. CVA2D or CVA3D and GEOVEL - Analyze new velocities.
686
The above work flow can be iterated. The final migration can be obtained by either a rerun of KTMIG
using the new velocities or directly creating a migration stack from the existing migration gathers if they
are dense enough.
References
Lumley, D. E., Claerbout, J. F., and Bevc, D., 1994, Anti-aliased Kirchhoff 3-D migration: 64th Ann.
Internat. Mtg., Soc. Expl. Geophys., Expanded Abstracts, 1282-1285.
Abma, Ray, Sun, James and Bernitsas, Nick, 1999, Anti-aliasing methods in Kirchhoff migration:
Geophysics, Soc. Of Expl. Geophys., 64, 1783-1792.
Yilmaz, O., 1987, Seismic data processing: Soc. Expl. Geophys., Tulsa.
Input Channels
2. VIP velocity traces: Optional connection from dataset SEGY data type.
Output Channels
2. KTMIG-saved dataset for restart: Optional connection to dataset KTMIG data type.
Parameters
Migration option
Options: Poststack Migration, Prestack Migration
Output option
This parameter is for Prestack Migration. The three output options are (1) Migration Stack, (2) Migration
Gather, and (3) Migrated Common Offset Sections. If the input data is DMODIST sorted (i.e. sorted as
Primary Key: DMODIST; Secondary Key: MLIN/MBIN; and Tertiary Key: MBIN/MLIN) selecting the
third option (Common Offset Sections) is recommended, as the memory requirement is reduced
significantly, and this migration module also tends to run faster. The memory requirement is a huge factor
if you are trying to process a big 3-D survey. The memory requirement is reduced in this case, as all the
offsets do not have to be stored in the CPU memory at the same time. The data is processed one common
offset at a time. Each Common Offset Section processed is output before the next Common Offset Section
is processed. For the other two output options ( Migration Gather, and Migration stack) the data is only
output after all the input traces have been processed.
687
Options: Migration Stack, Migration Gather, Migrated Common Offset

Sections, Angle Gather
Minimum of first angle group (deg.):

Required if Output option = Angle Gather.
Maximum of first angle group (deg.):

Increment between angle groups (deg.):

Number of angle groups:

Has pre-migration normalization been applied?

This parameter is currently for Migration Gather only. There are two methods to apply the amplitude
normalization for prestack migration: pre-migration normalization and post-migration normalization.
Pre-migration normalization scales the input traces by the NMO fold before migration. Post-migration
normalization scales the migrated traces by the NMO fold. KTMIG internally performs post-migration
normalization. Pre-migration normalization can be applied by module COFF. If parameter Has
pre-migration normalization been applied? is Yes, KTMIG will disable the post-migration normalization
and offset parameters in KTMIG should be the same as those in module COFF. It is strongly
recommended to apply pre-migration normalization whenever it is possible.
Do you want to populate empty output bins?

By default, KTMIGs output gather/stack will have a distribution (regular or irregular) of bins which is the
same as the distribution (regular or irregular) of bins in the input gather/stack. In the attached figure an
input/output comparison is shown, featuring variable trace spacing as to highlight the distribution of bins.
688
Hence, if a location (output bin) is absent in the output, it is because it was absent in the input data, NOT
because such a bin cannot allocate possible contributions from the migration. It only means the location is
not shown.
If the parameter Do you want to populate empty output bins? is set to Yes, then the migration gather/stacks
will show a more complete output of the migration, including contributions to bins not present in the input.
If this parameter is set to No (default) then the output distribution of output locations (output bins) is the
same as the input gather/stack.
Maximum range of output ellipsoids (distance units):

This parameter Maximum range of output ellipsoids (distance units): is used to specify the value for bdist,
that is, the maximum b-distance (in distance units) of the migrated extra traces, within which they will be
output. Any output location (trace) with a bdist greater than this value will not be shown in the output. A
definition of "b-distance" is: the distance between a new possible output location (trace) and the input
trace (the midpoint of the src-rec pair, if prestack) from which data is migrated (see attached diagram). So
if this value is specified as 10, then the new output locations which fall within a circle centered on the
nearest live trace with a radius of 10 distance units are the only locations to be shown in the output.
689
So a bdist output gather/stack features these:

. Has more traces than the input. How many more will depend on the bdist value specified (see below). In
general, the larger the bdist, the more traces shown in the output.
. The new output bins are identified with OIDN=-1 in the headers.
. The amplitudes of the new traces are NOT the result of interpolation. Instead, they are a natural result of
the same migration kinematics and dynamics applied to all other samples during migration.
. In an impulse-response experiment, if the input data is a single trace (only one input bin), then the
no-bdist output will show a single trace too (not the expected smiles), while by contrast the nonzero bdist
output will show the expected classical smiles. On the other hand, if the input to the experiment is N zero
traces with only one non-zero trace, the no-bdist output will be N traces (smiles), and the nonzero bdist
output will have M traces, with M>N.
690
Variable with offset?

Required if Do you want to populate empty output bins? equals yes.
An additional feature allows the user to specify a different bdist value for each offset present in the input
data. This is done using a OFFBDIST matrix, as shown.
691
Note the following:

. If an offset value is not specified by the user in the bdist-offset matrix, then KTMIG will interpolate a
bdist value for that particular offset (linear interpolation).
. KTMIG prints in the execution status the values of dx and dy read from the DataBase. If a bdist value in
the matrix is less than 0.5max(dx,dy), (remember for example dx is the bin size of the data geometry,
equivalent to one half of the Average inline receiver interval, as shown in the STATION module menu),
then KTMIG will assign bdist=0.5max(dx,dy) to that particular offset, and the message WARNING: bdist
less than 0.5*MAX(dx,dy). Reassigned to 0.5*MAX(dx,dy) will be shown in the Execution Status window.
. In general, the larger the offset, the bigger the bdist needed.
. The population of bins, for each offset, should be carefully studied before migration. In some cases
(specially a merge of several surveys), it is very possible that for a given offset the population of bins in
the input data is OK for some sectors and very scarce for others. In such a case, an amplitude discontinuity
(low amplitudes) can be observed in some traces of both the input and the output of the migration, even
though a big bdist is assigned to those offsets. That is because the bdist feature is not an interpolation, but
a process of the migration itself, so if the input information is scarce, the output of the migration will be
scarce too, as expected from the kinematics and dynamics of Kirchhoff time migration.
Offset-dependent values of maxbdist:

Matrix Type:OFFBDIST
Minimum offset (distance units)
692
Maximum offset (distance units)

Offset increment (distance units)
CMP-Fold matrix to obtain live output CMPs
This parameter is for prestack migration, when the interpolated traces are not output, and the input data is
DMODIST sorted. If this parameter CMP-Fold matrix to obtain live output CMPs: is specified, then the
specified matrix is used to determine the live CMPs, for which the computations are done. If an input data
set has lots of missing traces or holes, using this option speeds up the migration, as computation is not
performed for those output CMPs which do not exist in the input data. This matrix of type DBFOLDOFF
is generated using the module DBHDR . If this option is not used, that migration is performed at all the
CMPs in the output space.
Surface reference of output

Options: Fixed Datum, Floating Datum, Topography
Output datum (distance units)

Matrix for midpoint floating datum
Matrix Type: USRMBIN
Surface reference of input

Options: Fixed Datum, Floating Datum, Topography
Input datum (distance units)

Header index for receiver floating datum
Header index for source floating datum
Perform Converted Wave Migration?
If this parameter Perform Converted Wave Migration? is set to Yes, then the Converted Wave migration is
performed. In this case the seismic energy goes downward as P-wave and after reflection, it mode
converts, and travel upward as S-wave. Hence the both Vp and Vs velocities are also required.
693
RMS velocities referenced to output

The RMS velocities are referenced to the output space. Hence if the output datum is different from the
input datum, then the RMS velocities should be referenced to the output datum, not the input datum. This
parameter is only available when performing a PP migration, and not available when performing a
converted wave migration. A progress bar of the velocity-reading process for migration is shown in the
Execution Status windows during run time.
Matrix Type: RMSVEL
RMS Vp velocities referenced to output

This parameter is only required when doing converted wave migration. The RMS P-Wave velocities are
referenced to the output space. Hence if the output datum is different from the input datum, then the RMS
Vp velocities should be referenced to the output datum, not the input datum.
Matrix Type: RMSVEL
RMS Vs velocities referenced to output

This parameter is only required when doing converted wave migration. The RMS Vs velocities are
referenced to the output space. Hence if the output datum is different from the input datum, then the RMS
Vs velocities should be referenced to the output datum, not the input datum.
Matrix Type: RMSVEL
Alternate corrections
If this parameter is set to Taylor C4, then the fourth order coefficients are used in the migration equation
to preform curved ray time migration. The fourth-order coefficients are picked during velocity analysis.
Options: Taylor C4, None, Anisotropic-VTI, Anisotropic-HTI
Fourth order terms

Required if Alternate corrections equals Taylor C4. This parameter specifies the name of the matrix for
the Fourth order terms. The fourth-order coefficients are picked during velocity analysis. Care should
taken when picking fourth-order velocity analysis, as the migration algorithm is very sensitive to large
jumps in those values.
Matrix Type: 4THNMO
ETA terms
Required if Alternate corrections equals Anisotropic-VTI.
Matrix Type: ETANMO
694
Angle beta value

Required if Alternate corrections equals Anisotropic-HTI.
Elliptical velocities
Required if Alternate corrections equals Anisotropic-HTI.
Matrix Type: EVEL
Migration start time (ms)

Migration end time (ms)
Output sample rate (us)
This parameter defines the sample rate of the output traces in microseconds. It can be different from the
input sample rate. Choosing a large value of this parameter can reduce the run-time of KTMIG. If KTMIG
is to create time slices, this parameter specifies the increment between time slices. For migrated traces, this
parameter should be limited to (500000/Maximum Frequency).
Min. midpoint bin number of output

Max. midpoint bin number of output
695
Increment of output bin numbers

Min. midpoint line number of output
Max. midpoint line number of output
Increment of output line numbers
Time varying maximum dip?
If this parameter Time varying maximum dip? is set to Yes then KTMIG applies a time varying dip limit to
the migration process. The time varying maximum dips are specified in a matrix. This matrix of type
TVDIP. In this matrix, the third column named "TAPER (degrees)" is not used in this module, and may be
set to zero. Limiting the migration dip can improve the speed of KTMIG. Caution must be used to choose
this parameter. Choosing a small dip for the shallow part (time less than 1.0 sec) may destroy the shallow
data. It is therefore advisable to start with a high dip limit for shallow part, and then decrease the dip limit
as you go deeper.
Time variant Dip

This parameter specifies the name of the matrix for time varying maximum dip.
Matrix Type: TVDIP
Migration dip limit (degrees)

If the parameter Apply time varying maximum dip? is set to No then the parameter Migration dip limit
(degrees): can be used to specify a constant (non time variant) dip. Limiting the migration dip can
improve the speed of KTMIG. Caution must be used to choose this parameter.
Aperture - Time at zone of interest (ms)

This time is used to compute the full-aperture for migration. The maximum velocity at this time, along
with the maximum dip in the zone of interest (user specified) is used to compute the aperture. An
approximation for the full-aperture (diameter) is
aperture = time * maximum velocity at this time * sin(maximum dip at this time)
Limiting the migration aperture can significantly reduce the run-time of KTMIG. The migration aperture
computed here is applied to the whole area. If the spatially varying migration aperture is specified by the
user, then this constant aperture is not used.
696
Aperture - Maximum dip at zone of interest (degrees)

This maximum dip, along with the maximum velocity in the zone of interest is used to compute the
full-aperture for migration. The maximum velocity is computed at the time specified in the previous
parameter.
Spatially variant migration aperture

Limiting the migration aperture can significantly reduce the run-time of KTMIG. Caution must be used to
choose this parameter as it may impose a time-variant dip filter on the migration. An approximation for
the full-aperture (diameter) is
maximum velocity * maximum time * sin(dip)
Matrix Type: APERTURE
Percentage for adding back aliasing noise

This parameter controls the aliasing of migration operators. It is recommended to use 0 for prestack
migration and 50 for poststack migration.
% of aperture after which anti-aliasing to be applied:

This parameter controls when the anti-aliasing filter has to be applied. If equal to 0 the anti-aliasing is
applied at all the output location, if equal to 100, no anti-aliasing filter is applied. If equal to 50,
anti-aliasing filter is applied to those output locations which lie at a distance greater than half the aperture
from each input trace location. This Parameter is used to speed up the migration process. If no
anti-aliasing filter is applied, the migration is approximately twice as fast. Care should be taken as the
operator is aliased at greater dips, if no anti-aliasing filter is applied.
Velocity to control number of anti-alias filter coefficients

This parameter control how much filtering should be applied. The number of filter coefficients is
proportionally inverse to the velocity. That is, a large velocity would have only a few coefficients and little
or no anti-aliasing would be performed. A small number will create a bigger number of coefficients and
more filtering would be applied.
Amplitude Treatment option

This parameter determines the type of Amplitude treatment be applied.
Options: GeoCenter., Based on Cohen et. al.
Apply amplitude decay correction?
697

Min. midpoint bin number of boundary
Max. midpoint bin number of boundary
Min. midpoint line number of boundary
Max. midpoint line number of boundary
Fold map to determine boundary
Matrix Type: DBFOLD
The following frequency parameters are used only for

2D migration. They will be ignored in 3D migration.
Are you running on a Cluster?
If the parameter Are you running on a Cluster? is set to Yes, then the migration is performed on a cluster.
In which case the parallelization is achieved using Message Passing. The cluster may contain several
nodes (computers), and each node may have one or more Processors (CPUs). If this parameter is set to No,
then the migration is performed on a SMP machine. In this case the parallelization is achieved using
Threads, and there may be one or more CPUs on this machine.
698
Job type
Options: Automatic, Customized
pick cluster system:

First node
Last node
Number of Processors on each Node of the Cluster:
This parameter specifies the number of nodes (computers) in the cluster, to be used for processing. This
parameter is only available if the parameter Are you running on a Cluster? is set to Yes. If the cluster you
are running this job on has 60 nodes, and you want to use all, then you specify 60 for this parameter. If
you want to use only half the nodes, then you specify 30 here. Each node in the cluster may have more
than one processors. The number of processors on each node of the cluster is specified in the next
parameter Number of processors on each Node of the Cluster:.
Number of processors on each Node of the Cluster

This parameter specifies the number of processors (CPUs) on each Node of the cluster. This parameter is
only available if the parameter Are you running on a Cluster? is set to Yes. If each node has more than one
processor, then a second level of Parallelization is achieved using Threads on each of the node. At this
time the limitation is that each node in the cluster must have at least the number of processors as specified
by this parameter. So if you have a cluster with some nodes having 4 processors, and others having only 2
processors, then a value of 2 must be used here.
Number of Processors (CPUs)

This parameter specifies the number of Processors (CPUs) available on the SMP machine for use. This
parameter is only available if the parameter Are you running on a Cluster? is set to No. If this parameter
has a value more than one, then the computations are Parallelized using Threads. Here it is assumed that
the job is being run on an SMP machine.
Compute node list

Options: default, "Name of clusters"
699

This parameter is used to specify a specific list of sub-nodes, from the Compute node list to be used to run
the migration on. This parameter is only available when running on a cluster. If the Compute node list has
many nodes, say 100 nodes named n1, n2, .. n100. If you wanted to run KTMIG on 25 nodes, and
specifically nodes n26 to n50, you would enter 26 to 50 for the values of CPU index in the subnode
matrix. Also if you enter values 11 to 20, then the node listed 11 in the Compute node list, to the node
listed 20 in the Compute node list are used to run the migration on. Therefore it is the order of listing in the
Compute node list which determines which specific nodes of the cluster this job will be run on. This
parameter is useful if you plan to run several jobs on this cluster, and want them to run on different nodes.

This parameter specifies the Maximum available memory (in MB) on the SMP machine. This parameter is
only available if the parameter Are you running on a Cluster? is set to No. A check is made to see if the
amount of memory needed by KTMIG to hold the input and migration parameters, migration data and
velocities is less than the value specified for this parameter. If not, A WARNING message is sent to the
Execution status file. If such a message is received, it is recommended to follow the instructions supplied
with the WARNING message.

This parameter specifies the Maximum available memory on the Master Node (in MB) of the cluster. This
parameter is only available if the parameter Are you running on a Cluster? is set to Yes. A check is made
to see if the amount of memory needed by KTMIG to hold input and migration parameters is less than the
value specified for this parameter. If not, A message is sent to the Execution status file, and the job will
ABORT. If more memory is available on the Master Node, please specify a larger value here, and rerun
the job.

This parameter specifies the Maximum available memory on each of the Compute Node (in MB) of the
cluster. This parameter is only available if the parameter Are you running on a Cluster? is set to Yes. A
check is made to see if the amount of memory needed by KTMIG to hold migration data and velocities is
less than the value specified for this parameter. If not, A WARNING message is sent to the Execution
status file. If such a message is received, it is recommended to follow the instructions supplied with the
WARNING message.
Memory for data buffer (MB)

This parameter specifies the amount of memory to be used for the data buffer, which in turn determines
the number of traces to be processed at a time. The default value for this parameter is 7 Mb. The effect of
this parameter is prominent when running on a cluster. If You are migrating a small volume on a large
cluster, increasing this parameter value may result in better load averages for the cluster, which translates
to a faster run. However, Caution must be used when specifying a large value for this parameter, as it may
700
slow down the data transfer to nodes on a cluster, depending on the network.
Restore mute?
If this parameter is Yes, the front mute will be restored for poststack migration and redefined for prestack
migration. All the dead bins will be left empty. This may cause the difference between the migration stack
and the stack of migration gathers because the dead bins are different between the final section and the
common-offset sections. To reduce the number of dead bins on the common-offset sections, the user can
either increase the offset increment in KTMIG or run module COFF with a large common-offset bin width
before migration. Although applying a mute can help to speed up prestack migration, it is wise to define a
less severe mute for migration gathers so it is adjustable after migration.

Options: NONE, MBIN, MLIN, SDPN

NMO mutes
Restart program?
If the module aborted in the middle of a previous run and the save intermediate result was selected, then
the module can be restarted from the last save point.
Save intermediate result for restart?

The module will optionally save the migration output to a restart file. Use the parameter below to specify
how often the restart file gets output. In the case where the module aborts, the user can Restart program
(see parameter above) so that the entire dataset does not have to be re-migrated.
Gap for flushing memory (# of traces)

Enter the number of traces for saving the intermediate migration results to the restart file.
Gap for dumping message (# of traces)

Enter the number of traces for producing a message to the status file. The message will state which line
and bin the migration is currently working on.
701
LAME
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module will compute the Lames modulii parameters for rigidity (Lambda-Rho) and
incompressibility (Mu-Rho). Input into this program is the acoustic impedance (INVERSN) traces
computed from the P-Wave and S-Wave (AVOA) traces.
The Lames modulii parameters for rigidity and incompressibility improve the identification of reservoir
zones by enhanced sensitivity to pore fluids. The module computes the Lames parameters: Lambda-Rho
(rigidity), Mu-Rho (incompressibility), and also outputs Lambda-Rho / Mu-Rho.
The Lames modulii parameter Lambda-Rho is computed using this equation:
Lambda-Rho = Ip * Ip - 2. * Is * Is
Where:
Ip
P-wave acoustic impedance trace.
Is
S-wave acoustic impedance trace.
The Lames modulii parameter Mu-Rho is computed using this equation:

Mu-Rho = Is * Is
This module expects CMP gather or 3D X-bin gather data. It expects at least two traces per ensemble with
DIST header words 1 or 2. The DIST 1 header word should be the P-wave (intercept) data from AVOA.
The DIST 2 header word should be the S-wave (gradient) data from AVOA. To prepare the data for this
module, here is an example flow:
Compute the Intercept and Gradient (least squares) or the P-Wave and the S-Wave (Geostack)
options in AVOA.
Run the P-wave/Intercept data through an inversion process like INVERSN to output acoustic
impedance. Separately run the S-wave/Gradient data through the inversion also. You may have to
scale the data using a module like ENSSCALE after the inversion.
Merge the P-wave/Intercept and the S-wave/Gradient data back into a CMP gather using modules
READ, SORT, and WRITE.
Run the merged acoustic impedance data through the LAME module to output Lames parameters.
702
References:
Input Channels
Output Channels
Parameters
Lame parameter to output
Select the Lames modulii parameter to output.
Options: Lambda-Rho, Mu-Rho, Lambda-Rho/Mu-Rho
Start time (ms.)

Enter a new start time in milliseconds if you do not wish to start at the first sample.
End time (ms.)

Enter a new end time in milliseconds if you do not wish to end at the last sample.
703
LAP
Module Description
Input Channels
Output Channels
Parameters
Module Description
LAP is designed to suppress localized noise bursts, such as spikes and ground roll. First, the amplitude
envelope is computed for each trace within the prescribed window. Then, the amplitude curve is smoothed
by a running-window filter and an exponential gain curve is computed through regression analysis.
Anomalies are then searched for based on the prescribed permissible DB variation. With the anomalies left
out, LAP recomputes a gain curve for the trace and searches for anomalies again. The amplitudes of the
noise bursts are then restored to the exponential gain curve.
LAP is a statistical process. If the number of (bad) burst samples dominate the window, LAP may not be
very effective.
Input Channels
Output Channels
Parameters
DB higher than average allowed
Dominant frequency of noise(Hz)
This parameter will be set to Nyquist if it exceeds it.

704

Input if Space variant windows? = No.
The window start time will be reset to the first sample if it is less than zero.

Input if Space variant windows? = No.
a
The window end time will be reset to the last sample if it exceeds the data length.
NOTE: The window end time must be at least 10 samples after the window start time. This applies to the
times input via the matrix also.
Primary header key

Input if Space variant windows? = Yes.
TLSN

TLSN
Window times
Print traces with spikes?
705
Number of traces to print

Input if Print traces with spikes? = Yes.
706
LCKF
Module Description
Input Channels
Output Channels
Parameters
Module Description
LCKF will perform low cut K filtering (Spatial filtering) with a 15 point roll-along filter. LCKF assumes
that there is an even trace spacing between traces. Up to five filters and their corresponding start and stop
times may be chosen. As shown in the diagram below, the 0% response point is equivalent to the "Low
Cut" frequency, and the 100% response point is the "Low Pass" frequency.
100% Response Point
A
|
Corner Frequency
___________
|
_____________
|
\ Reject | Reject /
|
|
Pass
\
|
/
Pass
|
|
\
|
/
|
|
\
|
/
|
_______________________________________________
-.5
0 |
+.5
K |
0% Response Point Corner Frequency

K
(K = 1/X)
-.5
-.33
0
.33
+.5
___________________________________________
|
|
|
|
| LCKF
|
|
|
|
| would
|
|
|
|
| reject
F
|
|
|
|
| frequencies
|
|
|
|
| under 50 Hz.
50|--------|----------|-----------|--------||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Nyquist|--------|----------|-----------|--------|
|
|
All traces are
peak to trough
_____________
LCKF would reject
Frequencies in traces
that had peak to peak
over three traces or
or more.
707

Ramp
|<->|
Ramp
|<->|
_______________
_______________
________________
|
|\ /|
|\ /|
|
|
Filter #1
| X |
Filter #2
| X |
Filter #3
| ...
|_______________|/ \|_______________|/ \|________________|
^
^
^
^
^
^
0
End1
Start2
End2
Start3
End3
Input Channels
Output Channels
Parameters
Time variant?

Primary header key

TLSN
708

TLSN
Low cut K filters

Matrix Type: LCKF

Restore amplitude?
709
LENGTH
Module Description
Input Channels
Output Channels
Parameters
Module Description
Input Channels
Output Channels
Parameters
New record length (ms.)
710
LENGTH2
Module Description
Input Channels
Output Channels
Parameters
Module Description
The length2 module will subtract or add a subset data to an existing dataset. The subtract method will pull
off a subset of data from the traces depending on a start and stop time. The add method will pad the traces
with zeros either before or after the existing data.
The subtract subset method gives the user a start time and end time for the subset. If you try to view the
data again in SeisUP, it will show from zero to the total time of the subset. You will have to pad the
beginning of the trace with zeros to reposition the data properly.
The add subset method will pad the traces with zeros either before or after the existing data in the set. All
existing data will be bulk shifted if you pad at the beginning of the traces.
Input Channels
Output Channels
Parameters
Add or subtract a subset of time to the traces
Select if you are subtracting a subset of the data or adding zeros to length the traces. If you subtract, you
enter a start and stop time and the new dataset will have these samples in it. If you add, you have to choose
if it is before or after the current data. Then the module will pad zeros.
Options: Add a subset, Subtract a subset
711
Start time (ms.)

If the subtract method was chosen this parameter will appear. Specify the start time to begin the data
subset in milliseconds.
End time (ms.)

If the subtract method was chosen this parameter will appear. Specify the end time to stop the data subset
in milliseconds.
Begin or end of the trace

If the add method was chosen this parameter will appear. Specify if zeros will be padded to the start or the
end of the current traces.
Options: Begin, End
Window length (ms.)

Chose the window length in milliseconds to perform the trace padding.
712
LINE3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
LINE3D will interpolate an arbitrary line from a 3-D stack volume by linear interpolation between the two
traces along the top two dominant dip planes at each common depth point. The dominant dip direction is
measured by finding the maximum coherency along a radial range of dips from neighboring neighboring
traces. TRACE headers will be interpolated. LINE3D will renumber the SDPN and MBIN trace headers
starting from one. The MLIN trace header will be set to the line number defined in the line(s).
Input Channels
Output Channels
Parameters
Define Line(s) to extract using
Select Midpoint bins to define the start, corner and end points of the line to extract. Otherwise select
Coordinates to define the point using X and Y coordinates.
Options: Midpoint bins, Coordinates
Line(s) to extract
Use this matrix to define the lines to be extracted by entering the points as MBIN and MLIN midpoint
numbers.
Matrix Type: MXLINE3D
713
Line(s) to extract
Use this matrix to define the lines to be extracted by entering the points as X and Y coordinates. When
using this method the fractional MBIN and MLIN midpoint numbers will be printed to the execution
status listing.
Matrix Type: MXLINE3DXY
Number of inline traces to use (bins)

This is the number of inline neighboring traces to use to determine the dominant dip. LINE3D will force
this number to a lower even number.
Number of crossline traces to use (lines)

This is the number of inline neighboring traces to use to determine the dominant dip. LINE3D will force
this number to a lower even number.
Minimum inline dip in Ms. per trace

Maximum inline dip in Ms. per trace
Inline Dip increment in Ms. per trace
LINE3D will determine the coherency at each dip increment.
Minimum crossline dip in Ms. per trace

Maximum crossline dip in Ms. per trace
Crossline Dip increment in Ms. per trace
LINE3D will determine the coherency at each dip increment.

Increasing this parameter will result in smoother dominant dip estimates in the time direction.
714

Extracted line midpoint interval
The default is use the smaller of the inline and crossline midpoint interval.
715
LINENAME
Module Description
Input Channels
Output Channels
Parameters
Module Description
LINENAME can be used to place a line name into the trace header so that GEOM can extract the shot
matrix name from the trace header. For 3-D marine projects, simple geometry and initial preprocessing
can be performed prior to receiving the UKOOA coordinate tapes. The initial geometry can be simple 2-D
style geometry. The key will be put the correct field shot point number (FSPN) into the header. Since
UKOOA puts the shotpoint number into the ID column of the source matrix, GEOM can be run on the
UKOOA entered geometry database and setting the following GEOM parameters:
Header for shot id
FSPN
Multiple 3-D shot matrixs to apply?
3-D shot matrix name in trace header?
Shot matrix trace header key
Yes
Yes
LINE
Input Channels
Output Channels
Parameters
Use custom line name matrix?
Select Yes to enter a trace header key and fill in a matrix that will define start and end trace header values
for a specified line name.
Line name (Max. 8 characters)

If the parameter Use custom line name matrix? is No, then enter the line name to be applied to all traces.
716
Trace header key

If the parameter Use custom line name matrix? is Yes, then enter the trace header key for the start and end
trace header values in the custom line name matrix.
TLSN
Line names
If the parameter Use custom line name matrix? is Yes, then enter the start and end trace header values in
the custom line name matrix.
Matrix Type: LINAME
717
LINSUB
Module Description
Input Channels
Output Channels
Parameters
Module Description
LINSUB will perform time variant signal enhancement by extracting the signal along the dominant dip
direction and then summing the signal with the original trace. The dominant dip direction is measured by
finding the maximum coherency along a range of dips from neighboring traces at each sample. If the
maximum coherency is less than a user specified threshold level, no signal will be extracted. After signal
extraction, the coherency is measured between the signal and the original trace at each sample. The
coherency is then used to calculate a weight to apply to the signal trace before summing with the original
trace.
LINSUB uses the ensemble header word (see GCI) to determine the distance away from the trace being
enhanced. This header word should be a sequential index like SDPN, MBIN, MLIN, FCSN, or CDPN.
LINSUB will drop dead and auxiliary traces.
Input Channels
Output Channels
Parameters
This is the number of neighboring traces to use to determine the dominant dip. LINSUB will force this
number to a higher odd number.
718

Dip search range by

Slowness,Velocity
Minimum dip in Ms. per foot(meter)

Required if Dip search range by is Slowness.
Maximum dip in Ms. per foot(meter)

Number of Dips to scan

Minimum Velocity
Required if Dip search range by is Velocity.
Maximum Velocity
Number of Velocities to scan


Output
Options: Signal, Signal & Original, Coherency

Required if Output: = Signal & Original.
719


summing with the original data at the coherency defined in the previous parameter. LINSUB will linearly


Matrix Type: DICE

Required if Output: = Signal & Original. If "Yes" is chosen, after summing the signal trace with the
original trace, the output trace will be normalized.
Estimation start time

Estimation stop time
Taper Length>
Header index of start header
720
Header to add to stop time

Header index of stop header
Noise band low cut frequency
Noise band low pass frequency
Noise band high pass frequency
Noise band high cut frequency
AGC Window Length
721
LOGREAD
Module Description
Input Channels
Output Channels
Parameters
Module Description
Read the well logs from a LAS format file. All the wells in the file are input into SeisUP.
This module can read logs from LAS version 1 and 2.
The user has the option to override several LAS header values. If the depth start and stop values are
specified by the user, the module will skip any well log data that is outside this range. If the depth
increment is overridden, then the use specified value is used instead of the header value.
The user can also override the x and y coordinates from the LAS header. The elevation can also be
overridden. The user specified values are used instead of the header values. In the case where the header
does not contain these values, then the user specified values are used.
REFERENCES
Canadian Well Logging Society - LAS Version 2.0, A Floppy Disk Standard for Log Data.
Input Channels
1. Input : Required LAS data type.
Output Channels
Parameters
Depth start (distance units)
Enter the depth stop value of the well in distance units (ft or meters). The default is to get it from the LAS
header in the Well Information section under keyword, STRT.
722
Depth end (distance units)

Enter the depth stop value of the well in distance units (ft or meters). The default is to get it from the LAS
header in the Well Information section under keyword, STOP.
Depth increment (distance units)

Enter the depth increment of the well in distance units (ft or meters). The default is to get it from the LAS
header in the Well Information section under keyword, STEP.
X coordinate
Enter the X coordinate of the well. This coordinate should match any seismic data that it is expected to tie.
The default is to get it from the LAS header in the Well Information section under keyword, XCOORD.
Y coordinate
Enter the Y coordinate of the well. This coordinate should match any seismic data that it is expected to tie.
The default is to get it from the LAS header in the Well Information section under keyword, YCOORD.
Elevation
Enter the elevation of the well from ground surface. The default is to get it from the LAS header in the
Well Information section under keyword, ELEV.
Save LAS header to matrix

Select to save the LAS header to a matrix. The header can be used later to output this well to a LAS file.
Matrix Type: LASHEADER
723
LRADON
Module Description
Input Channels
Output Channels
Parameters
Module Description
Overview
LRADON can be used to attenuate noise using a high resolution Radon transform. Noise can be random,
linear or multiples. Application can be global (whole ensemble) or local (time/space windows).
Alternative implementations of the Radon Transform in SeisUP are with the modules RADON, RADON1
or RADONC modules. Each of these modules are implemented in the frequency domain and follow the
approach that of Hampson(1986) using a least-squares formulation. The problem with this formulation,
under conditions of reduced aperture and inadequate traces spacing, an event will be smeared across
multiple P traces. The result is less signal to noise separation and when a mute is applied artifacts will
result. This leads to poor multiple attenuation and deterioration of primaries. Recently (Sacchi and Ulrych,
1995; Sacchi, 2002; Hermann et al., 2000; Ng and Perz, 2004; Hugonnet and Canadas, 1997; Cary, 1998)
high resolution transforms have been developed to overcome the shortcomings of the Hampson method.
Generally these methods constrain the spectra to be sparse not only in P but also in T using an iteratively
re-weighted scheme. These high resolution transforms allow increased separation between signal and
noise and decreased aliasing issues.
The Taup or Radon transform in general assume constant amplitude over particular moveout. Seismic data
however can be neither constant amplitude(AVO) and can contain complex moveout (I.E. Anisotropy). By
using local panels for the Radon transform each local segment can be better approximated. However the
smaller one goes in offset, the separation between signal and noise becomes worse in Radon P space.
Local Taup transforms are currently being utilized within the DICE and TRIP modules. Others are also
using local sub-space for Radon filtering (Wang, 2009) and for interpolation (Sacchi et al., 2004; Hermann
et al., 2000; Wang et al, 2010).
Ng and Perz(2004) showed that a Gauss-Seidel implementation using prioritized moveout parameters can
produce "super" high-resolution gathers. However their method tends to overemphasize whole P traces
and thus lacks sufficient temporal resolution. The net effect may prevent proper separation between signal
and noise events. The method used by LRADON extends their method to local space to achieve local
prioritization. In the case for local parabolic transforms, LRADON computes iterations consisting of
Gauss-Seidel iterations:
1) Weighted and/or threshold-ed Forward and Adjoint Radon transform
Forward transform:
724
Adjoint transform:
2) Accumulate Forward Q trace estimate with Radon spectra
3) Subtract current Adjoint trace from current residual data

The high
resolution semblance computation used in the first iteration for weight W is a combination of C2
semblance from Marfurt et al. (1998) and differential bootstrapped semblance from Abbad and Ursin
(2012). The semblance weight used is calculated as:
Where d H is the Hilbert portion of d. Nr is the number of bootstrap realizations. Typically this is some
number less than five. is the offset randomly sorted for each realization.
corresponding to the wavelet length.
is a time gate
Usage
For multiple attenuation, the data prior to using LRADON should have Normal Moveout (NMO) and
mute applied. By applying NMO, hyperbolic events become approximately parabolic. A mute should be
applied because moveout at far offsets and shallow times become complex and contain significant stretch
that cannot be modeled very well with LRADON.
725
To be able to properly remove noise from seismic data, the Radon transform must be able to model all
signal and linear noise. Anything left over (un-modeled noise) from an forward and inverse transform
should ideally be random noise. To properly allow amplitude variations, LRADON will subtract the
results from inverse Radon transform from the input data. The default in LRADON is to model the noise
by muting out the signal prior to the inverse transform. It is suggested to first not mute any signal and
make sure you have optimal parameters to model all events in the ensemble and thus minimize the
un-modeled noise. The following results may indicate need for adjustment:
High moveout/dip still in the record: Your min/max P values are not high enough
Complex moveout still left: Use local transform with smaller windows. It is suggested to start from a
global window (entire ensemble) and work your way to smaller windows. The offset direction is
more important than the time window. Making this too short will make the resolution in the P spectra
worse. Making it too big will cause complex moveout to not be modeled properly.
Aliasing
It is well known that to prevent aliasing in the time direction we should keep frequencies below nyquist
defined by
When using the Radon transform we need to prevent data aliasing and operator aliasing. Data aliasing can
occur if we violate:
where
, is the offset/trace spacing between traces in an ensemble and f max is the maximum frequency
defined by the user. However, LRADON attempts to minimize any data aliasing by using semblance
weighting. Notice though that semblance weighting only occurs in the first iteration but most of the energy
should be modeled at this time. For other iterations a constant is used for the weighting and thus data
aliasing could occur if the above equation is violated. When using LRADON for multiple attenuation and
to help minimize data aliasing, it is suggested to apply NMO with a velocity half way between the
multiples and primaries or:
Operator aliasing can also occur if the

spacing is too large. If this happens, the combination of forward
and inverse transform may fail to reconstruct the original or it may fail to properly model the signal and
noise. LRADON will by default compute the number of p traces as:
726
This equation will prevent operator aliasing at the defined maximum offset. LRADON has the option to
use a reference offset that is subtracted from the input offset. The reference offset used will be the center
of the current local offset window. If a linear Radon transform is used it is possible to reduce computation
time by defining the maximum offset to be the half local offset width and one would also have to define
the p min and p max at that offset. For parabolic or hyperbolic Radon transforms, the offset defined should
be the average absolute maximum offset in the data set.
Running windows
When using LRADON in a local sense, the user has the ability to specify the windows as follows:
1. Window chunks or adjacent groups of traces/samples
2. Running window
If one desires a running window. Specify the window to be one sample in size. I.E. for offset use the offset
interval and for time use the sample interval. Then specify the temporal/spatial overlap as the window size
minus the sample interval. Using a running window can improve results with complex moveout. However
keep in mind computation time will go up considerably. As an example the following are equivalent
window sizes:
Chunks
Running window
X direction window(ft/m)
5720
660
X direction overlap(ft/m)
5060
References
Abbad, B. and Ursin B., 2012, High-resolution bootstrapped differential semblance, 77, U390-U47 Abma,
R., and Kabir, N., 2006, 3D interpolation of irregular data with a POCS algorithm
Cary, P., 1998, The simplest discrete Radon transform: Presented at the 68th Ann. Internat. Mtg., Soc.
Expl. Geophys., Expanded Abstracts, 1999-2002.
Foster, D.J., and Mosher, C.C., 1992, Suppression of multiple reflections using the Radon transform:
Geophysics, 57, 386-395.
Hampson, D., 1986, Inverse velocity stacking for multiple elimination: Canadian Journal of Exploration
Geophysics, 22, 44-55.
Herrmann, P., Mojesky, T., Magesan, M. and Hugonnet, P., 2000, De-aliased, High-Resolution Radon
Transforms: 70th Ann. Internat. Mtg., 1953-1956
Hugonnet, P., Boelle J-L., Mihoub M., 2008, 3D High Resolution parabolic Radon filtering: 80th Ann.
Internat. Mtg., Expanded Abstracts, 2492-2496
727
Kabir, M., and Verschuur, D., 1995, Restoration of missing offsets by parabolic Radon transform:
Geophysical Prospecting, 43, 347-368
Kostov, C., 1990, Toeplitz structure in slant-stack inversion: Presented at the 60th Ann. Internat. Mtg.,
Soc. Expl. Geophys., Expanded Abstracts, 1618-1621.
Marfurt, K. Schneider, R. and Mueller, M., 1996, Pitfalls of using Conventional and Discrete Radon
Transforms on Poorly Sample Data: Geophysics, 61, 1467-1482
Marfurt,K., Scheet R., Sharp J. and Harper M., 1998, Suppression of the acquisition footprint for seismic
sequence attribute mapping: Geophysics, 63, 1024-1035
Ng M. and Perz M., 2004, High resolution Radon transform in the t-x domain using "intelligent"
prioritization of the Gauss-Seidel estimation sequence: 74 th Annual International Meeting, SP P3.4
Sacchi, M.D. and Ulrych, T.J., 1995, High-resolution velocity gathers and offset space reconstruction:
Geophysics, 60, 1169-117
Sacchi, M. D., and Porsani, M., 1999, Fast high-resolution parabolic Radon transform: Presented at the
69th Ann. Mtg, Soc. Expl. Geophys., Expanded Abstracts, 1477-1480.
Sacchi, M.D., Verschnuur D.J., and Zwartjes P.M., 2004,Data reconstruction by generalized
deconvolution: 74th Ann. Internat. Mtg., Expanded abstracts, 1989-1992
Thorson, J. and Claerbout, J., 1985, Velocity-Stack and Slant-Stack Stochastic Inversion: Geophysics, 50,
2727-2741.
Trad, D., Ulrych, T. and Sacchi, M., 2003, Latest views of the sparse Radon transform: Geophysics, 68,
386-399
Wang J. and Ng M., 2009, Greedy Least-Squares and its Application in Radon Transforms: CSEG
convention, Expanded Abstracts, 5-8
Wang J., Ng M. and Perz M., 2010, Seismic data interpolation by greedy local Radon transform:
Geophysics, 75, WB225-WB234
Input Channels
Output Channels
728
Parameters
Input data
Optionally one can input Taup/Radon spectra that has been processed with other modules. However keep
in mind only a global transform will be performed. If the spectra was created by a local method,
unpredictable results will occur.
Options: Seismic data, Taup spectra
Output
Normally one would want to output the signal minus the modeled noise. As an option, the modeled noise
can be output or for Q.C purposes the summed local Taup/Radon spectra can be output. If spectra is output
and the centered reference offset option is selected, then keep in mind that events will shift in tau and p
when local windows are used. So the same event can show up at multiple locations in this case. LRADON
automatically accounts for this in the muting process.
When the sole purpose is to use LRADON for interpolation, choose option noise or input. Option input
should be used if one wishes to output the non-interpolated traces untouched.
Options: signal-noise, noise, Taup spectra, input
Perform local transform?

Select Yes to perform a local transform. Select No to perform a global transform.
X direction window(ft/m)
Enter the spatial window width in feet or meters. A smaller window can allow complex moveout to be
modeled more accurately but at the cost of lower spectra resolution and possibly less signal/noise
separation. When testing this parameter it is suggested to start from a global offset window size
(maximum offset) and progress to a smaller window size.
X direction overlap(ft/m)
This is the overlap in feet or meters between spatial windows.
T direction window(ms.)
Enter the temporal window size.
729
T direction overlap(ms.)
This is the overlap between temporal windows.
Maximum offset (m or ft)

This is not the absolute maximum offset in the entire data set but rather an offset that corresponds to the
min/max P traces defined below. For parabolic and hyperbolic transforms this offset should be an average
global maximum offset while for linear transforms this can be defined at the local level. See description
above as well.
Window start time (ms.)

By default, LRADON will search for the first non-zero sample within a window and start from there.
Optionally this parameter will allow a start time to be added to this start time to reduce computation time
by concentrating only on a zone of interest. I.E. deep water multiple.

Optionally one can add the contents of a trace header to the start time. This header value must be defined
in milliseconds. As an example, the header TIM1 can contain the water bottom then combined with the
next parameter can allow transforming only the water bottom multiple.
Options: None, TIM1, TIM2
Trace header start time multiplier

This parameter will be multiplied by the start time to allow specific water bottom multiples times to be
added to the start time.
Minimum signal moveout (ms.)

Enter the minimum P moveout curve to be used by the Radon transform. This moveout is defined at the
maximum offset entered above.
Maximum signal moveout (ms.)

Enter the maximum P moveout curve to be used by the Radon transform. This moveout is defined at the
maximum offset entered above.
Number of curves
Enter the number of P curves to be used between the minimum and maximum curves at the maximum
offset. See Aliasing discussion above.
730
Use center offset as reference?

Select Yes to subtract the middle offset within the local spatial window from the input offset. This will
allow faster computation times. See discussion above and as well the spectra discussion.
Number of Gauss-Seidel iterations

Hopefully only one Gauss-Seidel iteration is needed to properly model the input data. Increasing this
parameter will allow additional data to be spread to Radon spectra to reduce the un-modeled residual.
Number of hires iterations

This is the number of sorted P Gauss-Seidel iterations. I.E. the loops are per transform:
One Gauss-Seidel set of iterations to determine dominate energy and thus P sort order for the first
hires iteration.
This parameter number of hires iterations
One gauss-Seidel set of iterations in sorted decreasing P energy order. If more hires iterations
are to be performed this spectra will determine P sort order for next hires iteration.
Highest frequency in input(Hz)

This parameter is only used to compute the number of P traces for the Radon transform.
Minimum number of live traces

This is the minimum number of live traces needed for each local window. If the number of traces is
below this threshold then the data for that window will be passed unchanged.
Transform type
Enter the Radon transform curve trajectory.
Options: Linear, Parabolic, Hyperbolic
Reference depth for hyperbolic transform

If the transform type is "Hyperbolic" then enter the reference depth for the Foster and Mosher equation:
731
Semblance low cut threshold

Optionally one may enter a minimum semblance threshold to allow when using semblance weighting. This
is semblance value between zero and one that starts the taper.
Semblance low pass threshold

Optionally one may enter a minimum semblance threshold to allow when using semblance weighting. This
is semblance value between zero and one that ends the taper.
Semblance temporal window (ms.)

This is the temporal smoothing
parameter applied to the semblance computation defined above.
mute
Allowable spectra mute options are:
signal: Mute signal or low P traces. This will allow the modeled inverse to subtract noise data from
the input.
noise: Mute the noise at high P traces. If the desired output is "noise" then this option will allow
signal to be output.
Mute type
The following spectra mute types are allowed:
Vertical P: Mute at constant P for all
NMO: Allow definition of a NMO mute that is pickable with the DISPLAY module.
None: No mute that should be used when testing parameters.
Minimum P for noise

Enter the minimum P value for noise when using mute type of "Vertical P".

Enter the primary trace header key when using mute type for NMO mute.
TLSN, Other
732
Primary mute header index

Enter the primary trace header index (starting from one) when using mute type for NMO mute.

Enter the secondary trace header key when using mute type for NMO mute.
TLSN, Other
Secondary mute header index

Enter the secondary trace header index when using mute type for NMO mute.
Mutes
Enter the NMO matrix name when using mute type for NMO mute.
Add start time to mutes?

Select Yes to allow adding the start time to the starting time of the mutes.
Temporal mute taper length (samples)

Optionally one may taper the mute temporally to avoid edge artifacts. Normally provided one mutes
at low amplitude areas then this taper is not needed for high resolution transforms.
Spatial (P) mute taper length (traces)

Optionally one may taper the mute spatially to avoid edge artifacts. Normally provided one mutes at
low amplitude areas then this taper is not needed for high resolution transforms.
Mute zone reduction amount (%)

Enter 100% to mute the spectra with hard zeros. Code less than 100 to scale down the mute zone.
Interpolate dead traces?

On option LRADON can be used to interpolate data. In this case selecting Yes will interpolate data that is
flagged as dead. The offset used should be defined in the trace header.
733
Number of POCS iterations?

If the input data is being interpolated, enter the number of Projection On Convex Sets (POCS) iterations to
be used. See Abma & Kabir (2006) and Kabir & Verschuur (1995). Because this module performs high
resolution Radon, it is expected that the most optimal interpolation will occur in the first POCS iteration
unless aperture effects are present in the Radon spectra.
Restore mute?
Select Yes to restore the mute found on the input data.
Perform window QC?

When performing a local Radon transform it is sometimes desirable to view the spectra and results from
just that window. Select Yes to perform this QC.
QC Time window location(ms)

When performing local window QC enter a time for any sample in the local window one desires to view.
QC offset window location(ms)

When performing local window QC enter an offset value for any sample in the local window one desires
to view.

To increase performance enter a value greater than one. Make sure in this case that the node you are
running on has multiple cores. LRADON will run in parallel over local windows when using this
parameter. Increasing this parameter for global mode will have no effect.
Number of cluster nodes to use

To run in parallel across ensembles use a value here greater than zero. Parallelisation will be done using
MPI. This option will allow global mode parallelisation. This option may be use along with thread based
parallelism if local mode is being run.
Compute node list

When using cluster nodes enter a matrix containing the nodes to use. Enter in MPICH2 format.
734
Verbose?
Select Yes to provide additional printout for diagnostic reasons.
735
MAPCON
Module Description
Input Channels
Output Channels
Parameters
Module Description
MAPCON is a flow tool that passes current ensemble ID information to a mapping tool called
GEOMVIEW. A typical flow places MAPCON before DISPLAY and the user is performing first break
time picking on shot records. In this case MAPCON sends the SLIN/SBIN number of each shot ensemble
that passes through MAPCON to GEOMVIEW. Simultaneously running GEOMVIEW in MAPCON
mode reads the shot (SLIN/SBIN from MAPCON) data from the input dataset and displays the shot and its
geophone locations on the map. This allows the user to see the map position of the current shot for first
break picks in DISPLAY.
Input Channels
Output Channels
Parameters
Ensemble option
The user must select SHOT for sending the current shot SLIN/SBIN to GEOMVIEW. Similarly select
MLIN to send the MLIN number of the current CMP gather or MBIN to send the MBIN number.
Options: Shot, MLIN, MBIN
Connect file name (full path)

This is the full path and name of the file that transfers ensemble IDs. Something like: /tmp/mapcon would
put a file under the /tmp directory.
736
737
MARINE
Module Description
Parameters
Module Description
Module MARINE will create the 2-D marine geometry for given set of lines. If the line does not exist,
MARINE will create the line and an empty flow. For special geometry situations that this module does not
provide:
Create the geometry as best as you can using this module.
Open the flow for the line needing special geometry.
Add a SOURCE and/or STATION module.
For shot changes, edit the parameters for the SOURCE module and change the Acquisition type
parameter to Marine, edit the source matrix named 2Dline and execute the SOURCE module.
For geophone or midpoint changes, edit the parameters for the STATION module and execute the
STATION module.
Parameters
Custom streamer layout?
Near trace channel number
Source to near trace distance
Pattern
Enter the distance from the source to each channel if a custom streamer layout is required.
Group interval
738
Shotpoint interval
Midpoint interval
Dataset name for reel numbers
If reel numbers are defined in the Lines matrix, MARINE will create a REEL matrix for this data set in
each line. A data set will not be created in the flow. To use this matrix, open the flow for the line(s), create
a data set using this name, and set the parameter Need reel info? to Yes. The other way to use this matrix
is to perform a Line copy in the flow editor from a master line that has this data set name in it and the
parameter Need reel info? set to Yes. When the Line copy is performed, a dialog will appear to verify
that you want to over write the REEL matrix. Respond No to the dialog.
Lines
For each line in this matrix, MARINE will create a flow for the line in SeisUP if it does not exist and then
setup the geometry.
Matrix Type: MARINEGEOM
739
MATCH
Module Description
Input Channels
Output Channels
Parameters
Module Description
This modules allows the user to substitute header values from a list.
Input Channels
Output Channels
Parameters
Input header key
NOTE If "none" is selected, the module will abort.
TLSN, other
Header ID index for input

Required if Input header key equal other.
Output header key

TLSN, other
740
Header ID index for output

Required if Output header key equal other.
Substitution matrix
Matrix Type: MATCH
Action for missing values

the interpolate option will put constant values outside of the range of the matrix.
Options: skip, abort, message, interpolate
741
MATCH2
Module Description
Input Channels
Output Channels
Parameters
Module Description
This modules allows the user to substitute 2 header values from a list. A match between both values on a
row of the input matrix, will put both output values into the output header words.
Input Channels
Output Channels
Parameters
Input header key 1
TLSN, other
Header ID index for input header key 1

Required if Input header key 1 equal other.
Input header key 2

TLSN, other
742
Header ID index for input header key 2

Required if Input header key 2 equal other.
Input value scalar

Input values in the matrix are multiplied by this value prior to header matching.
Output header key 1

TLSN, other
Header ID index for output header key 1

Required if Output header key 1 equal other.
Output header key 2

TLSN, other
Header ID index for output header key 2

Required if Output header key 2 equal other.
Output value scalar

Output values in the matrix are multiplied by this value prior to header matching.
Substitution matrix
Matrix Type: MATCH2
Action for missing values

Options: skip, abort, message
743
MATCON
Module Description
Parameters
Module Description
MATCON will convert ETANMO matrices to RMSVEL matrices and vice versa. The module may be
used to process picked eta fields by converting them to RMS Velocity fields, processing the field by
smoothing, for example, and converting back to an eta field.
Parameters
Input - Output:
Conversion from eta to velocity or vice versa.
Options: Eta to Velocity, Velocity to Eta
Velocity Matrix
Matrix Type: RMSVEL
Eta Matrix
Matrix Type: ETANMO
744
MCADPDCN
Module Description
Input Channels
Output Channels
Parameters
Module Description
Performs spiking or predictive decon with a continuously time varying filter. The filter may optionally be
designed from samples from traces on either side of the trace being deconvolved (multi-channel). The
multi-channel option tends to produce smoother and cleaner outputs at the expense of high frequency loss
and process time required. Four methods are implemented.
1. The Burg spiking method builds the filter using Burg algorithm. Optionally, multiple traces
contribute to the calculation of the Levinson recursion coefficients from forward and backward
prediction. This algorithm results in a very strong spectral whitening. Unfortunately some noise gets
enhanced along with the signal. Use the same filter length as for a Wiener-Levinson decon
application. The rate of adaptation is 1.0 or less.
2. The Forward-Backward Average spiking method uses a non-Burg adaptive average forward and
backward prediction filter. This method tends to produce clean results by whitening the data part of
the spectrum. Again use the same filter length as for a Wiener-Levinson decon application. The rate
of adaptation is from 1 to 100. It is necessary to start low, then move higher (increments of 10) to get
the desired whitening effect.
3. The Forward Average method may be used for mild spectral whitening, but is primarily used for
predictive (gapped) decon to attenuate all types of multiples. Application with zero prediction
distance will whiten the data. Application with a non-zero prediction distance will attenuate the
multiple reflections with time separation equal to the prediction distance (header time plus gap time)
and reversed in sign. This module may be cascaded (several consecutive occurrences) in the flow
with the same or different parameters. Water bottom multiples in marine data may be attenuated by
inputting common offset ensembles with the water bottom reflection times loaded in TIM1 or TIM2.
The common offset domain (with spatial amplitude corrections or balance) may be useful because the
water bottom related multiples may be very stationary (near constant time difference) without NMO
stretch. Unfortunately, the deconvolution process must be run separately on all offset sections of
interest, then sorted back to shot or cdp for further processing.To attenuate water bottom multiples
using input ensembles of shot or cdp, the data should be NMO corrected at water velocity (1500 m/s
or 5000 ft/sec) and the water bottom reflection times picked for these nmoed ensembles and
available in the TIM1 or TIM2 header. This NMO corrected water bottom time will be added to the
constant prediction time (gap) entered in the menu for the total multiple removal time. The filter
length for water bottom multiple attenuation should be a little more than the length of the water
bottom reflection.The adaptation rate may vary from 1 to 150. Again, start low, then increase in
increments of 10 until the desired effect is found.
4. The Multi-channel Single Filter method also performs adaptive spiking or predictive deconvolution.
The results are less severe, but usage the same as the Forward Average method above, except the
maximum rate of adaptation will be about 50.
745
It is CRITICAL that the data be smoothly varying in amplitude laterally (across ensemble traces), and that
traces with bad noise or spikes be killed. It is advisable to condition the lateral amplitudes with an
application of surface consistent amplitudes or with a module like ENSSCALE prior to applying
multi-channel adaptive decon. Sometimes better results can be obtained with two or more modules
cascaded with lower adaptation rates than one module with a high adaptation rate. The more channels used
to design the filter, the cleaner and smoother the results, but more process time is required. The post decon
amplitude restoration filter may be very desirable especially for whitening applications.
Example 1 - common offset application Marine Data - Flow 1, preparation
1. READ shot records and sort by OFFSET and specify start and end value the same.
2. DISPLAY the common offset ensemble and pick the water bottom reflection as a HORIZON using
the DIST and SSPN keys.
Marine Data - Flow 2, application
1. READ shot records and sort by OFFSET, same as 1 in preparation flow above.
2. MUTE all events above a clean water bottom reflection for best (cleanest) results.
3. HORIZON with the DIST and SSPN keys, TIM1 or TIM2, using name of water bottom horizon
times picked in (2) of preparation Flow 1 above. This step loads the water bottom reflection times
into the trace header TIM1 or TIM2.
4. MCADPDCN with the Forward Average method, 1-5 channels, 200 ms operator length (length of
water bottom reflection), 50 adaptation rate, gap of -30 (depending upon whether the water bottom
reflection was picked at the very inception, first peak, first trough or ?), TIM1 or TIM2 to get the
water bottom times, amplitude restoration YES and 0 to Nyquist.
5. MCADPDCN again (same parms but maybe lower adaptation) if the first application (4) did not
completely remove the water bottom multiple reflection.
6. MCADPDCN again (same parms) if the first applications (4) and (5) did not completely remove the
water bottom multiple reflection.
7. NMOA with water velocity to recover normal shot records. Remainder of flow.
Example 2 - NMOed shot record application Marine Data - Flow 1, preparation
1. READ shot records with the channels sorted by DIST.
2. NMOR with the velocity matrix values equal to water velocity (1500 m/s or 5000 f/s).
3. DISPLAY the shots and pick the NMO time corrected water bottom reflection as a HORIZON using
the SSPN and DIST keys.
Marine Data - Flow 2, application
1.
2.
3.
4.
READ shot records with the channels sorted by DIST.

MUTE all events above a clean water bottom reflection for best (cleanest) results.
NMOR with the velocity matrix values equal to water velocity (1500 m/s or 5000 f/s).
HORIZON with the SSPN and DIST keys, TIM1 or TIM2, using name of NMO corrected water
bottom horizon times picked in (3) of preparation Flow 1 above. This step loads the nmo corrected
water bottom reflection times into the trace header TIM1 or TIM2.
5. MCADPDCN with the Forward Average method, 1-5 channels, 200 ms operator length (length of
746
6.
7.
8.
9.
water bottom reflection), 50 adaptation rate, gap of -30 (depending upon whether the water bottom
reflection was picked at the very inception, first peak, first trough or ?), TIM1 or TIM2 to get the nmo
corrected water bottom times, amplitude restoration YES and 0 to Nyquist.
MCADPDCN again (same parms but maybe lower adaptation) if the first application (4) did not
completely remove the water bottom multiple reflection.
MCADPDCN again (same parms) if the first applications (4) and (5) did not completely remove the
water bottom multiple reflection.
NMOA with water velocity to recover normal shot records.
Remainder of flow.
References
L. J. Griffths, F. R. Smolka, L. D. Trembly, Adaptive Deconvolution: A New Technique for Processing
Time-Varying Seismic Data, Geophysics 42, 1977, pp. 742-759.
Cowan, C.F.N., and Grand, P.M., 1985, Adaptive Filters; Prentice-Hall Book Co.
Widrow, B., and Stearns, S.D., 1985, Adaptive Signal Processing; Prentice-Hall Book Co.
Clearbout, Jon F., Fundamentals of Geophysical Data Processing: With Applications to Petroleum
Prospecting, McGraw-Hill Book Co.
Input Channels
Output Channels
Parameters
Deconvolution Method
Options: Burg Spiking, Forward-Backward Average Spiking, Forward
Average, Multi-Channel Single Filter
Application
This selection is required for the Forward Average or Multi-channel Single Filter method because they
will perform both spiking and predictive decon.
747
Options: Spiking, Predictive
Number of channels in filter (odd)

For multi-channel applications, the adaptive filter(s) will use samples from a symmetrical pattern about the
trace to be deconvolved. If 5 traces are specified, samples from 2 traces on each side of, plus the samples
from the target trace will be used in adaptive computations. This symmetrical array pattern is broken at the
ensemble edges where the pattern tapers on and off.
Decon filter length (ms)

The filter length should be very close to the length of the source wavelet, or multiple event to be removed
for land data. The water bottom reflection may be useful in the marine case. Land data may require some
trial and adjustment.
Prediction gap (ms)

This value is constant (positive or negative), and will be added to the extra prediction time (below),if
selected. This value may be used to "adjust" the time varying prediction distance from the header. This
value may be the near surface reverberation time in a land survey (if reasonably constant).
Header describing extra prediction time

To apply predictive decon to marine shot records for water bottom multiple suppression, first remove
water velocity NMO from the shot to get the water bottom reflection and related multiples to be
"flat"(more stationary). In a display of water bottom flattened shot records, pick the "flattened" water
bottom reflection as a HORIZON with the SSPN and DIST keys. In the application flow before
MCADPDCN, remove water NMO and use the HORIZON module to transfer the NMO corrected water
bottom reflection times into TIM1 or TIM2. The total prediction distance (gap) for any trace will be the
value in this header plus the constant prediction gap (above). To apply predictive decon to common offset
sections for water bottom multiple suppression, first pick the water bottom reflection times on the
common offset section as a HORIZON with the DIST and SSPN keys. In the application flow before
MCADPDCN, use the HORIZON module to transfer the water bottom reflection times into TIM1 or
TIM2. Again, the total prediction time will be the value of this header plus the constant gap (above).This
header may contain the offset variant near surface reverberation time for a land survey.
Adaptation rate
This adaptation rate is for the Burg adaptive method. It must be 1.0 or less. This value affects the
magnitude of filter coefficient updates in the adaptive process.
748
Adaptation rate
This adaptation rate is for the non-Burg methods. This value affects the magnitude of filter coefficient
updates in the adaptive process. A value of 0 will do no decon. For a single application, use the highest
rate of adaptation possible before the results become unstable. In cases of multiple (cascaded)
applications, this value will be less than for the single application. To find the best rate, start at 1, then go
up by increments of 10 and observe the results. It will be obvious when the rate is too high.
Use RSLN to detect receiver lines?

Select YES for 3D land or other acquisition types where multiple receiver lines are linked in the same
ensemble, and, the lines may be identified uniquely by the RSLN header. This prevents line connection
edge effects.
Restore amplitude?
Low frequency (Hz)
High frequency (Hz)
749
MGEOM
Module Description
Input Channels
Output Channels
Parameters
Module Description
MGEOM is used to apply the geometry database to marine 3D trace headers. MGEOM will read a shot id
from the trace header and match the geometry database with the id. If the id is not found in the database,
MGEOM will print a message and drop the shot. MGEOM is best run as one of the first steps after reading
field data.
MGEOM will update the following trace headers:
HEADER
-----1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28
29.
30.
31.
NAME
Coordinate scale factor
Shot X coordinate
Shot Y coordinate
Group X coordinate
Group Y coordinate
Water depth at source
Shot bin number
Shot line number
Midpoint bin number
receiver
750
SDPN
DIST
EG
ES
DEPS
SX
SY
GX
GY
WDS
MSFL
MEFL
SBIN
SLIN
MSBN
MSLN
SSBN
SSLN
RSBN
RSLN
MBIN
MLIN
SGEN
SSPN
MCX
MCY
FSPN
EC
AZIM
If the shot matrix name is in the header and MGEOM cannot find the name in the database the following
message will appear at the job monitor:
Cannot find LINE: #### ID: #### CHAN: ### in db, reply (q/a/st/sl/line)
The allowable responses are as follows:
q
a
st
sl
line
Stop sending data to the next process and quit the

program.
Abort immediately.
Skip the trace.
Skip the line.
Enter the shot matrix name in the geometry db in
place of "line". For example to respond with the
Input Channels
Output Channels
Parameters
Header for shot id
Options: OIDN, SSPN, FSPN, OTHER
Header word index (GCI) for shot id

Required if Header for shot id = OTHER. Enter the word index into the trace header (GCI format) for the
shot id. The first word is one.

Select "Yes" to apply the result of flex binning.
Options: Yes, No
751
Duplicate FLEX traces?

To reduce the data volume, SeisUP supports saving FLEX information in the trace header words MSFL
and MEFL. To duplicate traces that fall into a range of CMPs and not store the FLEX information in the
traces headers, select Yes.
Options: Yes, No
Multiple shot matrices to apply?

Options: Yes, No
Shot matrix name in trace header?

Required if Multiple 3-D shot matrices to apply? = Yes. Select "Yes" to get the shot matrix name from the
trace header. MGEOM expects the name the shot matrix name to be in ASCII format.
Options: Yes, No

Matrix Type: SOURCEM
Shot matrix trace header key (GCI)

Input if Multiple 3-D shot matrices to apply? = Yes and 3-D shot matrix name in trace header? = Yes.
Select the GCI trace header key where the name of the shot matrix is located.:
Options: LINE, OTHER
Shot matrix name byte position in GCI header

Required if Shot matrix trace header key (GCI) = OTHER. Enter the byte number in the trace header
where the shot matrix name is located. The first byte in the header is one.
Number of bytes in shot matrix name

Required if Shot matrix trace header key (GCI) = OTHER. Enter the number of bytes for the shot matrix
name in the header. See also the previous parameter
752
Scale z values by 10
Options: Yes, No
753
MGRIDP1
Module Description
Parameters
Module Description
MGRIDP1 will output a SEG-P1 formatted file of the midpoint coordinates from the area database. The
following items will be printed for each midpoint grid location:
1.
2.
3.
4.
5.
MLIN
MBIN
Easting
Northing
Elevation (Presently only for S+G midpoint grid)
Parameters
Output file name
The file will be placed in the users home directory.
Survey name
Survey area
Client
Acquisition contractor
Processing contractor
Survey dates
754

755
MIDGEOM
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use MIDGEOM to apply the midpoint geometry in the database to stack data. If pre-stack geometry was
not defined perform the following:
1. Execute the STATION module. All parameters with the default of "calculated" should be replaced
with a valid number otherwise the module SOURCE will need to be executed.
2. Execute MIDGEOM on the stacked data.
Input Channels
Output Channels
Parameters
Header for CMP
This header will be used to match the corresponding number in the database.
Options: SDPN, MBIN/MLIN, OTHER
Header word index (GCI) for CMP
756
MIX3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
MIX3D is used to perform 3-D trace mixing to improve the signal- to-noise ratio of the data, generally on
a 3-D stack volume. If the data are sorted in the inline direction (3-D X-bin stack), the ensemble will be
the midpoint line (MLIN). Traces within the ensemble (in this case MBINs) are aligned between
ensembles and summed after applying a user defined weighting table. The following types of trace mixes
may be used:
Mean.
The mean value is found by the following formula:
where Wiis the weight, Siis the seismic sample value at a particular time on the ith trace, and N is the total
number of traces to mix over. Amplitude values that are zero are ignored.
Median and Alpha-trimmed mean.

The median and alpha-trimmed mean is found by the following formula:
757
where Ris the percentage of traces to reject outside of the median, Wiis the weight corresponding to the
seismic sample value after the sort, Siis the seismic sample value at a particular time on the ith trace after
sorting the amplitude values, and N is the total number of traces to mix over. When R is 0 the output is the
same as the mean mix. When R is 100% the output is the median mix. Amplitude values that are zero are
ignored prior to the sort.
References
Input Channels
Output Channels
Parameters
Mix type
Options: Mean, Median, Alpha-trimmed mean
Trigger for mix

MIX3D will either replace non-zero or zero value samples with the computed mix.
Options: Live, Zeros

Number of traces within an ensemble to mix over

This should be an odd number.
758
If Weight table is used this is limited to a maximum of 9.
Number of ensembles to mix over


A temporary work file is allocated that requires
(xbmax - xbmin +1) * ntpy * (the number of data + header samples) * 4
bytes.
Weight table
The default is to apply a weight of one for all samples.
Matrix Type: MIX3DWGT
Restore mute?
Subtract result from the original?
Select Yes to subtract the mixed result from the original trace. This option can be used to remove a linear
noise train from the input data.
Weighting scheme
Weighting scheme to use when NOT using a Weight table. The Boxcar uses a constant weight of 1. The
Gaussian tapers the response from 1 at the center down to 0.01 at the corners.
Options: Boxcar, Gaussian
Start time(ms)
Stop time
759
Add a header value to start/stop?

Options: Yes, No
Header to add
The value in this header word will be added to start/stop times.
TLSN, other
Header ID Index for header to add.

Required if Header to add equals other.
760
MIXD3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module MIXD3D performs dip guided 3-D trace mixing. Parameterization and algorithm are similar to
module MIX3D except that no specific Mean option is provided. The dip model is provided through the
auxiliary input data set. This model must contain a full ensemble of dip data traces for each output trace.
The model may be comprised of dip and azimuth traces or dip, azimuth and "switch" traces. The model
type, or style, must be coded. Header DIST must contain the trace type. The header word value that
identifies each trace type must be coded.
The dip model is defined with zero azimuth in the increasing ensemble index direction. This is the
Ensemble Dip direction. The azimuth angle increases in a counter clockwise direction (Cartesian sense). If
the dip, azimuth and "switch" trace model style (DeltaX/DeltaY option) is selected, the switch trace will
turn mixing on or off for trace values of "1" or "0" respectively.
The samples used to generate an output sample are defined by the dip values from the surrounding traces
within the mix foot print. The output sample values are found by the following formula after ordering by
sample amplitude:
where R is the percentage of traces to reject outside of the median, Wi is the weight corresponding to the
seismic sample value after the samples and corresponding weights are ordered by sample amplitude, Si is
the seismic sample value at a particular time (defined by the dip model) on the ith trace after sorting the
amplitude values, and N is the total number of traces to mix over. When R is 0 the output is the same as
the mean mix. When R is 100% the output is the median. Amplitude values that are zero are ignored prior
to the sort.
761
References
Input Channels
2. Dip Model: Required GCI data type.
Output Channels
Parameters
Mix, Edit or DICE
Options: Mix, Edit, DICE

This parameter is required if Mix, Edit or DICE equals Mix or Edit.
Number of traces within an ensemble to mix over

Number of ensembles to mix over

762

A temporary work file is allocated that requires
(xbmax - xbmin +1) * ntpy * (the number of data + header samples) * 4
bytes.
Weight table
The default is to apply a weight of one for all samples.
Matrix Type: MIX3DWGT
Restore mute?
Output Option
Options: Signal Only, Subtract from Input, Replace Input, Scale
Weighting scheme
Weighting scheme to use when NOT using a Weight table. The Boxcar uses a constant weight of 1. The
Gaussian tapers the response from 1 at the center down to 0.01 at the corners.
Options: Boxcar, Gaussian
Dip Model Source

Options: Dataset, Matrix
Header Word containing Model Primary ID

This parameter is required if Dip Model Source equals Dataset.
TLSN, other
763
Header ID Index for Model Primary ID

Required if Header Containing Model Primary ID is Other.
Header Word containing Model Secondary ID

TLSN, other
Header ID Index for Model Secondary ID

Required if Header Containing Model Secondary ID is Other.
Header Containing Model ID

TLSN, other
Header ID Index for Model ID

Required if Header Containing Model ID is Other.
Dip Model Style

Required if Dip Model Source equals Dataset.
Options: Dip/Azimuth, DeltaX/DeltaY
Dip ID
Required if Dip Model Style equals Dip/Azimuth.
Value of header word DIST defining "dip" traces for Dip/Azimuth model style.
Azimuth ID
764
Value of header word DIST defining "azimuth" traces for Dip/Azimuth model style.
Coherency ID
Value of header word DIST defining "coherency" traces for Dip/Azimuth model style.
Ensemble Dip ID
Required if Dip Model Style equals DeltaX/DeltaY.
Value of header word DIST defining traces containing dip in the ensemble direction for DeltaX/DeltaY
model style.
Secondary Key Dip ID

Value of header word DIST defining traces containing dip between ensembles direction for
DeltaX/DeltaY model style.
Mix Switch ID
Value of header word DIST defining "switch" traces for DeltaX/DeltaY model style.
Dip Model Style

Required if Dip Model Source equals Matrix.
Options: DeltaX/DeltaY, Dip/Azimuth
Dip Model Matrix

Required if Dip Model Source equals Matrix and Dip Model Style equals DeltaX/DeltaY.
Matrix Type: DIPMODEL
Header Word Containing Model Primary ID

TLSN, other
765
Header ID Index for Model Primary ID

Required if Header Word Containing Model Primary ID equals Other.
Header Word Containing Model Secondary ID

TLSN, other
Header ID Index for Model Secondary ID

Required if Header Word Containing Model Secondary ID equals Other.
Start time(ms)
Stop time
Taper Length
TLSN, other
Header index of start header

Required if Header to add to start time is Other.
Header to add to stop time

TLSN, other
Header index of stop header

Required if Header to add to stop time is Other.
766
Band Limit Signal

This parameter is required if Mix, Edit or DICE equals DICE.
Low Pass
This parameter is required if Band Limit Signal equals yes.
High Pass
Roll off width

AGC Window Length

Number of dips to scan

Dip scan type
Options: Percent of base dip, Ms per trace
Dip scan increment (%)

This parameter is required if Dip scan type equals Percent of base dip.
Dip scan increment (ms/tr)

This parameter is required if Dip scan type equals Ms per trace.
Warp plane to cone

Header containing cone offset
This parameter is required if Warp plane to cone equals yes.
767
Header ID Index for Cone Offset

This parameter is required if Header containing cone offset equals Other.
Dip to "P" Scalar (sec*tr/ms*ft)

This parameter is required if Warp plane to cone equals yes.
Output power traces

Edit window length(ms)
This parameter is required if Mix, Edit or DICE equals Edit.
Edit threshold
Edit suppression




This parameter is required if Use custom coherency-weight table? equals no.

768


This parameter is required if Use custom coherency-weight table? equals yes.
Matrix Type: DICE
769
MNMXAMP
Module Description
Module Description
MNMXAMP prints mlin, mbin, time and amplitude
770
MONOSUB
Module Description
Input Channels
Output Channels
Parameters
Module Description
MONOSUB is a monotonic noise estimation and subtraction module. The user specifies a target frequency
to be attenuated. The module uses inflection point interval times and amplitudes to estimate the additive
monotonic signal.
Input Channels
Output Channels
Parameters
Frequency to attenuate.
The frequency of the additive noise to be attenuated.
Output type
Options: Processed data, Noise model
Output the input data minus the estimated monotonic noise or the noise alone.
Minimum sequence length.

The minimum number of successive inflections intervals near the target frequency required to define a
valid estimate interval of the monotonic noise.
771
Print edits detected.

Will print for every trace the noise parameters found.
Restore mute.
Will restore the mute from trace headers after noise subtraction.
772
MPAS
Module Description
Input Channels
Parameters
Module Description
MPAS computes surface consistent autostatics for 2D and 3D data using the maximum stack power
concept described by Claerbout and Ronen in December 1985 Geophysics article "Surface-consistent
residual statics estimation by stack-power maximization" (Vol. 50, No. 12). MPAS inputs an NMOR
corrected dataset and outputs a shot and receiver residual statics matrix. Execution will be fastest if the
input dataset is CMP sorted. Also dead traces and traces muted too much to be used should be removed
before MPAS is run. One or more iterations may be done in a run where the next iteration applies the
statics updated in the last iteration. Experience has shown that at least 2 iterations should be done for best
results. The default is 4 iterations. If the survey is very large, it is recommended to run MPAS 1 iteration
at a time. The statics computed in the first iteration are input and updated during the second iteration, etc.
This is done with the "Input prior computed static?" option described below.
In this implementation, traces in a center CMP of an optional areal array (default of 3x3) of CMPs is
correlated against the sum (smash) of all the eligible traces in the areal array. If the correlation passes
some optional quality tests, it is summed to that traces shot correlation stack and to that traces receiver
correlation stack. The traces in all CMPs specified in the menu by MLIN and MBIN are subjected to the
correlation process. When all correlations are complete, the correlation stacks for each shot and receiver
are picked and the static values are output to the matrices for that iteration. Each iteration overwrites the
matrix values from the last iteration. There are three options to control the gate (window) length of the
traces used in smash and correlations. 1) Simple single gate with start and end time constant throughout
the survey. 2) single gate with variable start end end times defined in a matrix (picked MLIN by MBIN).
3) Multiple gates defined by a matrix (again picked by MLIN,MBIN). The first two single gate options
also allow for a HORIZON to be used to remove inline and crossline dip prior to smash and correlation.
Shot and receiver static convergence values are written to the "execution status" after each iteration. If the
average shot statics (and/or receiver statics) values are decreasing for every iteration, this signifies a stable
convergent solution. If these values are not converging, then the menu parameter must be reviewed.
Longer gates and/or shorter offsets may be needed depending upon the data and NMO velocity quality.
Maybe allowing a higher value for "Maximum size of second correlation peak" will help. Allowing a
larger maximum static value will sometimes help. If the data quality is poor, a larger smash zone (say 5x5)
may increase stability by providing higher statistics. If a pre-autostatic brute stack shows cycle skips,
allowing less than 100% of the statics to be used in the next iteration may help.
The menu defaults, after "Survey type?" selection, using the single constant time window, should provide
a reasonable result, providing the NMOR velocities are good. Please note that MPAS is sensitive to
velocity errors. The presence of significant RNMO will degrade the solution.
773
Input Channels
A GCI input dataset with NMOR applied is required. The time spent on I/O will be reduced if the input
dataset is sorted in CMP order. This would be the same dataset prepared for stack.
1. Input: Required GCI data type.
Output Channels
Two optional GCI datasets containing the correlation functions for each iteration. The statics are
determined from the peaks of the correlations. Statics are applied before each iteration so the correlations
should become more symmetric and peak closer to the zero point. Watch out for sidelobes that get larger
and jump across the peak. This could indicate a leg jump. The effect is generally more obvious on the
geophone correlations as they more likely to be sequentially numbered on the ground. Also any significant
RNMO will affect the symmetry of the correlations. The strength of each correlation is determined by how
many traces contribute and how close to "randomly distributed with zero mean" the other statics involved
are. A very weak correlation could indicate a poor quality static. The FOLD header contains the number of
valid correlations that contributed to the last iteration. MLIN is set to 1 and MBIN is set to SSPN or
SGEN. STTG and STTS are also filled in with the last iterations values.
774
This is the geophone output. The source output looks similar. In this area there are fourteen geophone
lines. This is easily seen by the FOLD header. The amplitude differences in the correlations are mostly
explained by the FOLD differences. The statics are relatively small here.
In one case during the development of the output option, a statics matrix was corrupted. There were wildly
improbable static values in the matrix. If values larger than the maximum static allowed are found in either
matrix, disconnect the output datasets and rerun the job. If this fixes the problem or not, please contact
GeoCenter.
1. Shot Correlations: Optional GCI data type. Read this dataset in STACK order.
2. Receiver Correlations: Optional GCI data type. Read this dataset in STACK order.
Parameters
775
Survey type?
Options: 2D, 3D
Input prior computed statics?

Statics may be computed in single or multiple iterations per run. If no prior autostatics have been
computed (fresh start), then select NO. To update statics from a prior run, select YES.
Input Source statics matrix

If YES was selected above for "Input prior computed statics?", select the matrix containing the desired
source statics. See "Output Source statics matrix" below. If the "Output Source matrix" has the same name
as this matrix, the final output source statics values will be written into this matrix and all prior values lost.
Input Geophone statics matrix

If YES was selected above for "Input prior computed statics?", select the matrix containing the desired
geophone statics. See "Output Geophone statics matrix below". If the "Output Geophone matrix" has the
same name as this matrix, the final output geophone statics values will be written into this matrix and all
prior values lost.
NOTE The next four parameters should be reflect the data input to MPAS. If they do not, MPAS may
abort with a NAV error. If the geometry in the database is correct, the defaults should work. In any event
there should be no data outside of the range given by these parameters.

If "Survey type?" is selected as 3D, specify the minimum MLIN desired for this statics analysis. For 2D
data MLIN is always 1.

If "Survey type?" is selected as 3D, specify the maximum MLIN desired for this statics analysis.

Specify the minimum MBIN desired for this statics analysis.
776

Specify the maximum MBIN desired for this statics analysis.
Minimum offset (ft or m)

Specify the minimum offset of any trace to be used in this statics analysis.
Maximum offset (ft or m)

Specify the maximum offset of any trace to be used in this statics analysis. If this is the first statics
analysis for this dataset, the NMO may not be optimum (especially noisy data), and it makes sense to
restrict the maximum offset of traces used to avoid the effects of poor NMO.
Smash line width in CMPs

If 3D is selected for "Survey type?" above, enter the MLIN width (odd number of CMPs) of the smash
zone.
Smash bin width in CMPs

Enter the MBIN width (odd number of CMPs) of the smash zone.
Correlation window(s)
Windows (gates) of traces of the input dataset are needed for correlations. Selection of these windows is a
processing art, but usually they are selected to enclose clean, continuous events on stack sections (MLINs
for this program). This version allows up to 5 time-spatially variant, overlapping windows, however, some
special features are available for just a single window. The single window may be a "constant time" width
all across the survey, or time-spatially variant. It may also have use a horizon (picked MLIN,MBIN) to
align the CMP traces before the pilot is formed, thereby taking structure into account.
Options: Single window, Multiple windows
Constant time window?

If "Single window" is selected above, selecting YES allows use of a constant time window throughout the
survey for statics analysis. Selecting NO, will require specification of a WINDOWS2 matrix name below.
Start time of window (ms)
777
End time of window (ms)

Correlation window matrix (picked MLIN,MBIN)
If "Constant time window?" is selected NO above, select the desired single window matrix.
Horizon guided window?

Either Constant time window or single window from a matrix may be horizon guided.
Window guide horizon (picked MLIN,MBIN)

If "Horizon guided window?" is selected YES above, select the desired horizon matrix.
Correlation windows matrix (picked MLIN,MBIN)

If "Multiple windows?" is selected for "Correlation window(s)" above, select the desired multiple window
matrix.
Number of windows
If "Multiple windows?" is selected for "Correlation window(s)" above, enter the number of windows
specified in the matrix.
Maximum static (ms)

This is the maximum statics value solved for during the run.
Percent samples non-zero for window

If any window has less than this percent of live (non-zero) samples, it is not used in the pilot or as a target
trace.
Maximum size of second correlation peak (pcnt)

If any correlation between target and pilot has a minimum of two positive peaks, and, the second largest
peak is larger than this percent of the largest peak, this correlation is not used in static computations.
778
Most of the shot and receiver static will be computed on the first two iterations. Further iterations refine
the static values.
Percent of static values passed to next iteration

If "Number of iterations" is greater than 1, the user may specify the percent of current static value to be
sent on to the next iteration. This may help prevent "cycle skips".
Output Source statics matrix

This matrix may have the same name as the source matrix specified if "Input prior computed statics?" was
selected (YES) above, however, we suggest separate names, usually related to the iteration number. If
these matrices have the same name, the original values will be overwritten by the output from this run.
Output Geophone statics matrix

This matrix may have the same name as the geophone matrix specified if "Input prior computed statics?"
was selected (YES) above, however, we suggest separate names, usually related to the iteration number. If
these matrices have the same name, the original values will be overwritten by the output from this run.
779
MSOURCE
Module Description
Parameters
Module Description
MSOURCE will allow you to input marine 3D source and receiver geometry. MSOURCE is similar to
SOURCE but will allow input of source and receiver depths. MSOURCE needs two types of information
as follows:
1. Source: This is composed of the the actual location of the shot and the location of the shot relative to
the receiver layout.
2. Pattern: The pattern will describe the receiver layout.
MSOURCE is normally run after the MSTATION program which defines the receiver and midpoint
locations. After MSOURCE is run, module MGEOM can be run to apply the geometry to trace headers.
As a replacement to MSOURCE, you can also run module UKOOA. UKOOA will read a UKOOA
formatted tape or disk data set and write the necessary information to the geometry data base.
For 3-D surveys, SeisUP can support multiple shot lines. Each shot line can reside at a different line
within the area. To scan for the line name with the parameter editor for modules such as MSOURCE and
MGEOM, first load the flow corresponding the line that actually holds the geometry line. SeisUP keeps a
list at the area level that contains the geometry line name and the line level name where the geometry
actually resides.
Parameters
Consolidate multiple 3-D shot matrices?
Select Yes to consolidate multiple shot matrices within a 3-D survey. For land surveys, every shot is
normally defined within a single shot matrix, but with a marine survey the geometry is usually split into
shot lines. By specifying Yes to this option the shot ids must be unique only within the shot matrix but the
line name must be specified in MGEOM. In addition, each time MSOURCE is run with a different
geometry matrix name, the shot matrix will be added to the area level 3-D geometry list. To see the list of
lines in the geometry list run module RT3D.
780
Scan & process lines option

This parameter only applies if multiple 3-D shot matrices are consolidated for this area. Select Single to
only process a single line. Select All or New to scan all lines within the 3-D survey and find any matrix
files that match the source and pattern specification method. Alternatively, select List to define an ordered
list of source matrices. With the All option, all lines are processed. This option should be used if the
geometry on any shot line was modified that would effect the minimum or maximum coordinates. With
the New option, only lines that have not been previously processed will be processed.
Options: All, Single, New, List
Pattern name same as source name?

If you are scanning all lines within a 3-D survey, then this option lets you define a single pattern name for
the entire survey. Otherwise, MSOURCE expects the pattern name to be the same as the source name.
Options: Yes, No
List of source matrices

This option is available when the Scan & process lines option is set to List. Lines will be processed using
only the given ordered list of source matrices.
Matrix Type: SRCMXLST
Source
Land source by coordinate and pattern by distance from source
Matrix Type: SOURCEM
Patterns
Pattern by distance from source
Matrix Type: PATTERNM
Print Shots?
Select "Yes" to print the X , Y, elevation, shot interval, and the change in elevation from the previous shot.
Check for duplicate shot ids in vector

Select the shot spreadsheet vector used to match the shot with the data when MGEOM is applied. A
duplicate shot id should not exist within the same spreadsheet when applying geometry to the data. If a
duplicate does exist, the first duplicate shot geometry will be applied. If a duplicate is found, a warning
message will be printed.
781
Options: Id: This is usually matched with the OIDN (field , FSPN:
This is the shotpoint number
782
MSTATION
Module Description
Parameters
Module Description
Run MSTATION to define the receiver and midpoint information for marine 3D surveys.
Parameters
Azimuth angle for grids to the inline direction
be established. The azimuth angle is the angle of the survey from the X-axis (from east to north) to the
inline shooting direction. A positive angle will rotate the survey clockwise. Proper rotation will result in
less computations and fewer bins. Both receiver and midpoint bins will be specified by grids.
Inline shooting direction from the origin

If a receiver or midpoint grid is defined, enter the direction from the origin used to define the inline or
MBIN/RSBN direction. As an example, if the azimuth angle is zero and the inline shooting direction is
counter-clockwise, then the MBINs will increase from the west to the east. If the inline shooting direction
is clockwise then the azimuth angle should be 90 degrees, the MBINs will increase from the south to the
north and the MLINs will increase from the west to the east.
This is the default orientation. Azimuth angle for grids of 0 and Inline shooting direction from the origin of
Counter-clockwise.
783
Azimuth angle for grids of 0 and Inline shooting direction from the origin of Clockwise.
Azimuth angle for grids of 90 and Inline shooting direction from the origin of Counter-clockwise.
784
Options: Counter-Clockwise, Clockwise

Code the receiver interval in feet or meters along the X-axis after rotation of the survey.

Code the receiver interval in feet or meters along the Y-axis after rotation of the survey.

A default origin will be calculated from the minimum X and Y coordinates in the survey.
785

Inline receiver number at the origin
This will be the first receiver bin number.
Crossline receiver number at the origin

This will be the first receiver line number.

The default will be to calculate the number of receiver bins from the maximum X and Y coordinates.

Code the midpoint interval in feet or meters along the X-axis after rotation of the survey. For midpoint
lines determined by S+G or Coordinates, this is the midpoint interval along the defined CMP line.

Code the midpoint interval in feet or meters along the Y-axis after rotation of the survey. For midpoint
lines determined by Coordinates, this is the CMP bin size perpendicular to the midpoint line.



786

coordinates.
787
MULP
Module Description
Parameters
Module Description
Program MULP can be used to perform several classes of operations on SeisUP format Time/RMS
Velocity functions
1.
2.
3.
4.
Shift the datum plane for a series of velocity functions.

Edit the RMS Velocity by limiting the implied interval velocities.
Resample the RMS Velocity functions to a constant time interval.
Apply a per cent weighting function to the RMS Velocity functions.
The datum plane shift can be accomplished in either time or depth. Shifting in time will preserve the input
RMS Velocity values but change their time positions. This operation implicitly changes the interval
velocity structure implied by the input RMS Velocity function. Shifting in depth will change RMS
Velocity values as well as their time position but preserve the implied interval velocity structure. The
depth shift method would generally be preferred.
The shift magnitude may be input in time or depth (distance). The USER option selects time shift input.
Bulk values as well as a multiplier and a CMP variable "horizon" matrix may be coded. Depth shifts are
specified by a floating datum matrix and/or fixed datum values. Time and depth values are converted to
match the shift method using the REPLACEMENT VELOCITY. Optionally, the first RMS Velocity value
may be used if no replacement velocity is entered. When a function is shifted down (material is added
above the existing datum), the appropriate velocity is used for the initial interval velocity value.
Velocity functions may be edited by modifying the implied interval velocity structure. Editing is
accomplished either by limiting the interval velocity by the defined minimum and maximum values or
removing any layer to layer interval velocity inversions.
Velocity function resampling may be performed either in time or depth. Resampling on input is always
accomplished in time. This will change the implied interval velocity structure. Resampling in time is an
interpolation of RMS Velocity values linearly between input time points. If input interpolation is selected,
any output resampling after a time shift will also be performed in time.
Selection of output resampling, or BOTH if depth shifting is selected, implies depth resampling. The
interval velocity structure will be preserved with RMS Velocity and time values recomputed and output at
the specified time interval.
RMS Velocity functions may be weighted by a specified per cent weight function matrix. Any weighting
is performed immediately after input and time resampling if it is requested. The matrix may be defined as
a function of CMP location or water bottom time. The water bottom time for each input velocity function
is defined as the second time pick in each function.
788
Parameters
Input RMS velocity matrix
The input RMS velocity matrix. Must have been built previously.
Matrix Type: RMSVEL
Output RMS velocity matrix

The output RMS velocity matrix. The module will build this matrix.
Matrix Type: RMSVEL
Output time sampling interval (ms.)

This option will resample the input velocity functions. The default is to keep the same input time interval.
The number of input plus the number of output points must be less than 100.
Output function maximum time (ms.)

This option allows the output velocity function length to be fixed at this time. Input functions will either
be truncated or extrapolated using the last interval velocity at the point of truncation.
Resample type
This option allows velocity functions to be resampled in either depth or time.
Options: Depth, Time
Allow velocity inversion on output?

This option will force replacement any interval velocity with the previous interval velocity if an interval
velocity inversion occurs.
Print detailed velocity information?

This option will print the output Time, RMS Velocity, Average Velocity, Interval Velocity, and Depth for
each time/velocity function. The starting and ending datum elevation and the time or depth shift applied
will also be printed.
789

If any layer interval velocity in any velocity function falls below this minimum, that layer interval velocity
will be set to this value. This is used if Shift velocity function? is Yes.

If any layer interval velocity in any velocity function falls above this maximum, that layer interval velocity
will be set to this value. This is used if Shift velocity function? is Yes.
Apply percentage function?

Select Yes to apply a percentage weighting function.
Primary & secondary keys

Weighting functions may be specified and interpolated by 3D bins or water bottom times. Choosing
"Water bottom time & NONE" will allow the application of percentage weighting functions dependent
upon the water bottom time. The water bottom time is taken to be the second time pick for each velocity
function. For example, for the following function:
Time
Velocity
--------------------0
4800
100
4500
1000
5500
100 would be the water bottom time.
Options: MLIN & MBIN, Water bottom time & NONE
Percentage function
The matrix that specifies the percentage weighting functions. This will be an array of time-percent values
based upon a primary and secondary key.
Matrix Type: MULPPER
Shift velocity functions?

MULP will use the Shift type Time/Depth and the interval velocity to compute new RMS velocity
functions.
790
Shift type
Select the method to specify shift values.
Options: User, Floating to fixed datum, Fixed to floating datum,
Fixed to fixed datum
Shift method
This option selects velocity function shifts in either depth or time.
Options: Depth, Time
Time (ms.) to add to all times in horizon matrix

This time will be added to the "HORIZON" time shift for each velocity function if User was chosen as the
Shift type.
Value to multiply all times in horizon after add

All total time shift values will be multiplied by this value if User was chosen as the Shift type.
Time horizon to shift velocity functions to.

This matrix is the same type matrix used in module HORIZON. The primary key is the midpoint line
number (MLIN) and the secondary key is the midpoint bin number (MBIN).
Fixed datum elevation

If "floating to fixed" or "fixed to floating" or "fixed to fixed" shift type was chosen, then enter the
elevation for the fixed datum.
Floating datum elevation

If "floating to fixed" or "fixed to floating" shift type was chosen, then enter the matrix that defines the
floating elevations.The floating datum elevation is normally computed when STATIC is applied. Note that
a value must exist in the matrix for every bin for which a velocity is input. No interpolation will be
performed.
791
Output fixed datum elevation

If "fixed to fixed" shift type was chosen, enter the final fixed output datum. The value entered for "Fixed
datum elevation" will be used for the input datum elevation.
Replacement velocity
If floating to fixed or fixed to floating or fixed to fixed Shift type is chosen, enter the replacement
velocity. This velocity is used to compute the time shift for the elevation difference found at a location if
the time shift method and datum shift type are is chosen. If 0.0 is entered, the initial interval velocity from
each input function will be used. This velocity will be used to compute depth shifts if the depth shift
method and USER shift type are chosen.The velocity entered here should be the true velocity, not the
RMS velocity.

If geometry has not been loaded for this area/line, then enter the minimum midpoint bin number for this
survey. Typically, this value will be 1. The loading and position of the floating datum matrix is dependent
on this value being correct. If you have geometry loaded, then accept the default to load from the database.

If geometry has not been loaded for this area/line, then enter the maximum midpoint bin number for this
survey. This value must be at least as large and the longest line in the survey. The loading and position of
the floating datum matrix is dependent on this value being correct. If you have geometry loaded, then
accept the default to load from the database.

If geometry has not been loaded for this area/line, then enter the minimum midpoint line number for this
survey. Typically, this value will be 1. The loading and position of the floating datum matrix is dependent
on this value being correct. If you have geometry loaded, then accept the default to load from the database.

If geometry has not been loaded for this area/line, then enter the maximum midpoint line number for this
survey. This value must be at least as large and the longest cross-line in the survey. The loading and
position of the floating datum matrix is dependent on this value being correct. If you have geometry
loaded, then accept the default to load from the database.
Updated on May 29, 2003 by John Stevens.
792
MUTE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Trace muting via program MUTE will zero out data in specified time windows relative to times specified
in a matrix. For a trace oriented mute, start and stop values are specified in a multi-dimensional matrix
capable of using primary and secondary header values. Optionally, start or end times can be adjusted
relative to matrices specified in program HORIZON as TIM1 or TIM2. Mute times are interpolated
between mute functions using triangulation.
For a contour oriented mute, the end time is described as a polygon within a matrix. A contour mute can
be used to mute a 3-D stack cube where the mute is picked off a series of time slices. Mute times are
interpolated between mute functions.
For NMO mute, trace muting is performed via a matrix of times relevant to primary and secondary header
values (e.g. CMP and offset). NMO mute is applied from zero-time to mute-time, and is used to mute out
the stretched zones at the shallow events, and far offsets.
For Surgical mute, trace muting is performed via a matrix of start and stop times relative to primary,
secondary and tertiary header values (e.g. MLIN, MBIN, DIST). Optionally, mute times may be
interpolated within each ensemble where mutes are defined, or interpolated by triangulation between all
ensembles.
Input Channels
Output Channels
Parameters
793
Mute type
Options: Trace, Contour, NMO, Surgical Mute
Header to add to start

Required if Mute type: = Trace.
Header to add to end

Primary header key

TLSN, Other
Primary mute header index

Required if Primary header key: = Other.

TLSN, Other
Secondary mute header index

Required if Secondary header key: = Other.
Mute functions
794
Matrix Type: MUTE
Primary header key

Required if Mute type: = Contour.
TLSN, Other

TLSN, Other
Mute functions
Matrix Type: MUTECONT

Required if Mute type: = NMO.

TLSN, Other

TLSN, Other
795
Mutes
Primary surgical mute header key

Required if Mute type: = Surgical Mute.
TLSN, Other
Secondary surgical mute header key

TLSN, Other
Tertiary header key

TLSN, Other
Tertiary mute header index

Required if Tertiary header key: = Other.

Surgical Mutes
796
Matrix Type: SRGMUTE
Interpolate:
Required if Mute type: = Surgical Mute. When No interpolation is used muting will occur only on traces
whose header values match an entry in the given surgical mute matrix. When Only Within Ensemble is
set muting is interpolated for traces in ensembles where mutes are provided. When Between Ensembles is
set muting is interpolated to traces in ensembles where no mutes are provided.
Options: No, Between Ensembles, Only Within Ensemble
Extrapolate:
Required if Mute type: = Surgical Mute, and Interpolate: = Only Within Ensemble. The surgical mute
can be extrapolated by applying the closest given mute within the ensemble (Constant) or by linearly
following the slope of closest two mutes within the ensemble (Linear).
Options: Constant, Linear
Taper the mute?

Select Yes to apply taper at the mute times.
Taper length
The taper is applied over taper_length samples at the mute times.
797
MVREC
Module Description
Parameters
Module Description
This program allows the user to do a restricted batch edit of a pattern matrix. Receiver lines equal Move
from receiver line: are changed to To this receiver line: if the pattern is in the range of Starting pattern
# to modify to Ending pattern # to modify AND the receiver bin is in the range of First receiver bin to
move to Last receiver bin to move.
This program is most useful where a receiver line must be changed on several patterns. It reports the
number of values changed.
NOTE - MVREC can be run repeatedly. It can have unintended results if the receiver line changes
overlap. The order of the runs can be critical.
Parameters
Starting pattern # to modify
Ending pattern # to modify
Move from receiver line
To this receiver line
First receiver bin to move
Last receiver bin to move
Pattern matrix to modify
Matrix Type: PATREC
798
NMO3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
NMO3D removes the normal moveout and dip moveout and performs bin center correction. NMO3D uses
the three-component RMS velocities (from module VA3C) to compute the dip moveout and bin center
correction.
Input Channels
Output Channels
Parameters

TLSN

TLSN
799
Three-component RMS velocities

Matrix Type: RMSV3C
Mutes
Compute average offset for mute?

Minimum offset
Offset pattern
Required if Compute average offset for mute? = Yes.
Offset increment
800
NMOA
Module Description
Input Channels
Output Channels
Parameters
Module Description
NMOA is the inverse of NMOR as it "adds back" removed delta-T using a given time/velocity table to
apply the NMO "pull-down" effect to the data. If muting has already been done with NMOR or MUTE,
the mute times are not affected, but the mute is now essentially irrelevant. RMS velocity matrices are as
used in NMOR.
Input Channels
3. GCI velocity dataset: Optional connection from dataset GCI data type.
Output Channels
Parameters

TLSN
801

TLSN
Mutes
RMS velocities
Matrix Type: RMSVEL
Non-hyperbolic correction method

Exact Taylor Expansion, None, Anisotropic-VTI, Anisotropic-HTI
Fourth order terms.

Required if Non-hyperbolic correction method equals Exact Taylor Expansion.
Matrix Type: 4THNMO
ETA terms.
Required if Non-hyperbolic correction method equals Anisotropic-VTI.
Matrix Type: ETANMO
Angle beta value

Required if Non-hyperbolic correction method equals Anisotropic-HTI.
Required if Non-hyperbolic correction method equals Anisotropic-HTI.
Matrix Type: EVEL
802
NMOR
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module NMOR executes normal moveout removal as defined by an RMS velocity field contained in a
user-specified matrix. Trace muting is performed via a matrix of times relevant to primary and secondary
header values (e.g. CMP and offset). Adjustments to mute times established by program HORIZON as
TIM1 or TIM2 in the trace header may also be employed. A stretch mute can optional be applied to the
data to mute distortions due to excessive stretching of the data. A mute taper can optional be applied to
avoid edge artifacts produced in any frequency domain processing due to abrupt start of data at the mute.
Non-hyperbolic NMO corrections can be made using the Taylor series 4 th order correction, or using a VTI
anisotropic correction (eta). An elliptical NMO correction for HTI media can also be performed, by
specifying values for V slow and V fast velocities.

Shot interval
803
Minimum offset:
200
Offset pattern:
2
Mutes
The program will also detect and mute traces where a combination of velocities and offsets causes the
data to crossover. This phenomenon usually happens if there are significant rapid decreases in the rate of
A mute taper can be applied to the data at the start mute time. Frequency domain processing can cause
artifacts in the data due to abrupt start of data at the mute. This option will taper the data at the mute start
to avoid this phenomenon.
Alternative Methods
In addition to the usual NMO correction approximation, the module can compute alternative methods of
NMO correction, useful for special cases. In the case of non-hyperbolic normal moveout, two methods
may be used: long spreads (Taylor 4 th order series expansion), and VTI anisotropic NMO correction (eta).
An elliptical NMO correction for HTI media can also be performed, by specifying values for V slow and
V fast .
Long Spreads (Taylor C4)

At long offsets, the NMO moveout becomes non-hyperbolic. "Very long offsets" means that the
offset/depth ratio is greater than one. Non-hyperbolic methods are needed in these cases.
In the first non-hyperbolic method, a 3-term Taylor series expansion of the NMO equation is used to
correct for 4 th order NMO. The C4 coefficient is manually selected in the GEOVEL module during
velocity analysis, and is input to NMOR on a 4THNMO matrix..
804
Polar (VTI) Anisotropy

In the second non-hyperbolic method, the anisotropic approximation to the NMO equation (Alkhalifah Tsvankin, 1994) is used. The epsilon (ETA) parameter is automatically selected using the FORTHPIK
module, and is input to NMOR on a ETANMO matrix.
where eta is defined as
(NB: this equation is written in previous versions of this manual as:

T**2 = T0**2 + (X/V)**2 - 2*eps*(X/V)**2*(X/V)**2/(T0**2+(X/V)**2 + 2*eps*(X/V)**2)
eps = epsilon (ETA)
Azimuthal (HTI) Anisotropy

For cases where a simple elliptical expression is wanted for HTI media with source-receiver offsets that do
not exceed the reflector depth, Greschka and Tsvankin (1998) calculated that the NMO correction can be
still done using the known hyperbolic expression
805
with the V nmo velocity given by
where t is total travel time, t o is 2-way zero-offset travel time, x is offset, V fast is the fast NMO velocity,
V slow is the slow NMO velocity, s is the slow velocity azimuth and V nmo (&#981) is the azimuthally
varying NMO velocity as a function of the source-receiver azimuth (&#981). Both V slow and V fast are
specified on a EVEL matrix as a function of time.
Two options are given to the user to specify the angle beta: (1) as a single value input via the parameter
menu, or (2) as a set of values (one beta value for every src-receiver pair) specified via a header word
chosen by the user.
806
References:
Gidlow, P. M. and Fatti, J.L., 1990, Preserving far offset seismic data using non hyperbolic moveout
correction: SEG 60th Annual International meeting, Expanded Abstracts, 90, 1726-1729.
May, B. T., and Straley, D. K., 1979, Higher-order moveout spectra: Geophysics, 44, 1193-1207
Taner, M. T., and Koehler, 1969, Velocity spectra - digital computer derivation and applications of
velocity functions: Geophysics, 34, 859-881.
Tsvankin, I. and Thomsen, L., 1994, Non hyperbolic reflection moveout in anisotropic media. Geophysics,
59, 1290-1304.
Al-Dajani, A. and Tsvankin, I., 1998, Non hyperbolic reflection moveout for horizontal transverse
isotropy. Geophysics, 63, 1738-1753.
Alkhalifah, T., and Tsvankin I., 1994, Velocity analysis for transversely isotropic media: Geophysics, 60,
no. 5, 1550-1566 (Sept/Oct 1995). CWP-145P.
Stevens, J., DeVault, B., Shear-wave azimuthal velocity anisotropy in a Williston Basin 9-C 3-D survey.
SEG/Houston 2005 Annual Meeting.
807
--------------------------------------
TYPE
Queue
Input Channels
1. GCI data from previous process
Required
GCI data type
2. VIP velocity dataset
Optional
SEGY data type
3. GCI velocity dataset
Optional
GCI data type
Output Channels
1. Output
Required
GCI data type
Parameters
Use converted wave NMO equation?

NONE, TIM1, TIM2
808

NONE, CDPN, DIST, FCSN, FSPN, MBIN, MLIN, MSBN, MSLN, OIDN, RSBN, RSLN, SDPN,
SGEN, SBIN, SLIN, SSBN, SSLN, SSPN, TIM1, TIM2, TLSN

RMS velocities
Matrix Type: RMSVEL
Alternative methods
Select to apply alternative NMO-correction methods. Use None to perform a NMO correction according
to the usual hyperbolic approximation.
Long Spreads (Taylor C4), None, Anisotropic VTI, Anisotropic HTI
Fourth order coefficients (C4)

Required if Alternative methods = Long Spreads (Taylor C4).
Use this option to apply a Taylor 4 th order NMO correction.
Matrix Type: 4THNMO
ETA terms
Required if Alternative methods = Anisotropic VTI.
Use this option to perform a NMO correction according to (Alkhalifah - Tsvankin, 1994) for VTI media.
Matrix Type: ETANMO
Choose origin of beta

Required if Alternative methods = Anisotropic HTI.
Unique beta, Get beta from header
Select this option to apply an elliptic approximation for the velocities in the normal moveout equation,
which can be applied to multi-azimuth non-converted wave data with source-receiver offsets that do not
exceed the reflector depth.
809
A space is made available in the user menu to specify both a value of beta (the slow velocity azimuth) and
the elliptical velocities. The elliptical velocities are input using a matrix with 3 columns: time, V slow and
V fast (see figure).
810
Angle beta value

Required if Choose origin of beta = Unique beta.
Header word for beta

Required if Choose origin of beta = Get beta from header.
Required if Alternative methods = Anisotropic HTI.
Matrix Type: EVEL
Mutes

Yes, No

Required if Apply NMO stretch mute? = Yes.
Taper the NMO mute?

Select Yes to taper the NMO mutes.
Yes, No
Taper length (time samples)

The taper is applied over Length of the taper to be applied samples after NMO mute.
811
Compute average offset for mute?

The following three parameters are used to compute the mute from an average offset. This will help
aliasing when performing DMO.
Yes, No
Minimum offset
Offset pattern
Offset increment
AUTHOR
Created on Jan 24,1994 by Bill
Updated in 2006 by P.Mora
812
NOISE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Noise is a program for adding random noise to data. The signal-to-noise ratio is expressed as a floating
point number. Signal can be measured relative to RMS, average or peak value. The noise is random 0 Hz
to Nyquist.
Input Channels
Output Channels
Parameters
Ratio of signal to noise
Signal determined by
Options: RMS, Mean, Maximum
RMS level of the signal
813
NOISEDIT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Spike and Noise Burst Edit will automatically detect and edit single sample spikes and multi-sample noise
bursts. Once detected, the spikes are removed by interpolating adjacent samples and noise bursts are
replaced with interpolated trace segments from surrounding traces.
Spikes are typically caused by instrument noise or tape errors. Noise bursts are long duration amplitudes
caused by footsteps on the geophone line, cable noise, raindrops and wind at isolated geophone stations.
The noise burst detection algorithm can fail around the first break energy. It is advisable to mute the first
breaks before attempting to edit noise bursts. Another technique is to pick mutes 100 to 200 ms above the
first break arrivals. Three domains are useful for noise burst editing, CMP, common offset, and the shot
domain. The shot domain can be effective if the noise does not span across adjacent traces at the same
time. The CMP domain is recommended for several reasons: 1) Geologic events are continuous in this
domain, 2) Bright spots are less likely to occur because the CMP domain is a collection from different
shots, 3) ensembles contain fewer traces resulting in faster run times.
Spike editing computes the median absolute amplitude within a time window. The ratio of each sample
absolute amplitude to the median amplitude is computed. If the ratio is larger than the user defined
threshold, then this sample is classified as a spike. The sample is replaced with a linear interpolation of the
sample above and below the spike.
Noise burst editing involves computing a three sample running average along the trace. This average is
then used to compute a ratio with the median amplitude of four surrounding traces. The ratio is then
compared to the user defined threshold. If the ratio is larger than the threshold, then this sample is flagged
as failed. The modules then attempt to expand the burst to make a more continuous noise block using the
minimum burst length as the expansion length. The flagged noise burst is then accepted or rejected based
upon the minimum burst length supplied by the user. The noise burst can optionally be replaced with a
trace segment that is interpolated from the four surrounding traces. You can also replace the edit noise
burst with zero values samples.
Input Channels
814
Output Channels
Parameters
Spike detection threshold
A sample is classified as a spike if the ratio of the absolute amplitude of the sample to the median absolute
amplitude in a window exceed this threshold.
Spike computation window length (ms)

Enter the length in milliseconds of the window used to compute the median amplitude for spike detection.
Noise burst detection threshold

A sample is marked failed when the ratio exceeds this threshold. A three sample running average is
computed for this trace and four surrounding traces. The ratio is the average for this sample to the median
sample computed from the four surrounding traces.
Minimum noise burst length (ms)

Enter the length of a noise burst in milliseconds. Noise bursts less than this value will be ignored. This
value should be one third to one fourth the length of a typical noise burst.
Do you want to interpolate edited zones?

Select YES to infill edited noise bursts by interpolating four surrounding traces. If NO is selected, the
edited zones are zero filled.
Print traces exceeding threshold?

Select YES to print the times that were edited for spikes and noise bursts.
Time/space variant start and end times?

This option allows you to select and build a matrix of start/stop times throughout the survey. The start/stop
times control when to edit for noise bursts. The data above and below the times are not included in noise
burst editing. If NO is selected then you must enter one start/stop time for the complete survey.
815

Enter the name of the WINDOW2 matrix time(s) file for noise burst editing. You can also build/edit the
file by pressing the . button.
Primary header key

Select the primary header key that corresponds to the primary key of the WINDOW2 matrix file.
TLSN

Select the secondary header key that corresponds to the secondary key of the WINDOW2 matrix file.
TLSN
Start time (ms.)

Enter a start time in milliseconds for noise burst editing.
End time (ms.)

Enter a stop time in milliseconds for noise burst editing.

You can optional add additional time to the start time of the window using this header key.

You can optionally remove time to the end time of the window using this header key.
816
NOPERMIT
Module Description
Input Channels
Output Channels
Parameters
Module Description
NOPERMIT allows the user to construct a matrix that contains one or more polygonal regions.
NOPERMIT allows the user to operate on the traces in one of seven coordinate spaces:
Source Coordinate - SX/SY
Receiver Coordinate - GX/GY
Midpoint Coordinate - MCX/MCY (This is the default coordinate space)
Source Station Crossline and Inline - SSBN/SSLN
Receiver Station Crossline and Inline - RSBN/RSLN
Midpoint Station Crossline and Inline - MSBN/MSLN
Midpoint Crossline and Inline - MBIN/MLIN
When defining data exclusion matrices the coordinates used to specify the vertexes should be in the same
coordinate space as specified in the coordinate space parameter.
The module accepts a single GCI data set input, and outputs a single GCI data set, and an optional CGM
data set. NOPERMIT will enumerate every trace in the data set and check to see if its location in the
specified coordinate space falls within one of the defined regions. The user specifies in the module
parameters whether interior or exterior traces should be rejected. That is, the user can choose to reject all
traces bound by the regions, or to pass those traces that fall within a region.
The figure below shows an example of how this module works. The green circles represent traces that
have been passed by the module, while the red xs represent traces that have been rejected. The blue lines
show the edges of the user defined regions. This image is an example of the modules optional CGM
output that is used to verify that traces were rejected as expected.
817
Additionally, the NOPERMIT module has a parameter that lets the user decide how to handle traces
whose coordinates fall on the edge or vertex of a polygon region. The user specifies whether or not the
edges are to be considered a part of the polygons.
Errors
NOPERMIT will return an error if it determines that one or both of the relevant trace headers contain no
meaningful data. That is, the module enumerates the values of the headers in each ensemble, keeping track
of how many values equal 0. If the number of zero-valued headers is greater than half of the input traces
818
for each ensemble, than the module will abort with an error message indicating which headers triggered
the error.
Input Channels
Output Channels
1. Trace map: Optional connection to dataset CGM data type.
2. Filtered data: Required connection to next process GCI data type.
Parameters
Matrix type:
Default, Time range
Data exclusion regions

Used if Matrix type is Default. The matrix type is REGIONS.
This matrix is used to define a region in a coordinate plane that serves as the data slicing criteria.
Coordinates for a trace are obtained from a pair of trace header fields (GCI formatted traces). The
particular pair of header fields used is specified by the user in the module parameter Coordinate space (see
below). If a traces coordinate falls in the interior of the polygon whose vertexes are defined by this
matrix, then that trace is passed to the next module. If the coordinate falls on the exterior of the polygon,
then the trace is not passed to the next module.
The matrix consists of three columns: the x-coordinate, y-coordinate and halo size. Each row contains the
x- and y-coordinate of the vertex (for coordinate spaces where x and y coordinates make sense), or the bin
and line number (for coordinate spaces where bin and line number are appropriate). The vertexes of the
polygon must be specified sequentially. Whether the coordinates are listed in clockwise order or
counter-clockwise order has no bearing on the modules operation; either order is acceptable.
Additionally, the array of vertexes is treated as circular, meaning that the vertex in the first row is
considered to be the next vertex after one defined in the last row of the matrix.
Multiple regions are defined by adding spreadsheets to the matrix: one sheet for each region.
819
Data exclusion regions (Time Range)

Used if Matrix type is Time range. The matrix type is REGIONST.
This matrix is used to define a region in a coordinate plane that serves as the data slicing criteria.
Coordinates for a trace are obtained from a pair of trace header fields (GCI formatted traces). The
particular pair of header fields used is specified by the user in the module parameter Coordinate space (see
below). If a traces coordinate falls in the interior of the polygon whose vertexes are defined by this
matrix, then that trace is passed to the next module. If the coordinate falls on the exterior of the polygon,
then the trace is not passed to the next module.
The matrix consists of five columns: the x-coordinate, y-coordinate, start time, end time and halo size.
Each row contains the x- and y-coordinate of the vertex (for coordinate spaces where x and y coordinates
make sense), or the bin and line number (for coordinate spaces where bin and line number are
appropriate). The vertexes of the polygon must be specified sequentially. Whether the coordinates are
listed in clockwise order or counter-clockwise order has no bearing on the modules operation; either order
is acceptable. Additionally, the array of vertexes is treated as circular, meaning that the vertex in the first
row is considered to be the next vertex after one defined in the last row of the matrix.
Multiple regions are defined by adding spreadsheets to the matrix: one sheet for each region.
Reject
This parameter lets the user specify whether the module rejects traces that fall in the interior of any of the
defined regions, or rejects traces that do not fall within any region. The default is to reject traces that are
inside of any of the defined regions.
Edge points are

This parameter lets the user specify how to handle traces that fall on the edge or vertex of a region.
Coordinate space
This parameter is where the user specifies which pair of GCI trace headers will define the coordinate space
in which the data slicing is performed.
Use Halos:
Long axis of the CGM plot
The default is 15.0 inches. The minimum is 4.0.
820
NOTCH
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module NOTCH can apply a notch rejection filter to the seismic data. The user specifies the center
frequency, the width of the notch, and the floor rejection. An adaptive method centers the maximum
spectral amplitude for rejection by searching within a range of frequencies. The filter can be applied in a
time/space-varying manner.
The NOTCH module will reject specific frequencies in the seismic data. This tool performs the filtering in
the frequency domain. The filter is applied on a trace-to-trace basis (single trace) within a specified time
window. The user specifies the notch frequency, the bandwidth (width of the notch), and the rejection
floor. A special adaptive method has been added that searches for the maximum spectral amplitude to
reject within a range of frequencies.
The notch filter will be useful for removing 50 or 60 hertz power-line noise. It can also be used to remove
ground roll and other noise that has a strong central frequency.
The notch filtering can be applied in a time/space-varying manner. If the user selects the time variant
option, then the NOTCHFIL and the WINDOW2 matrix must be completed. The NOTCHFIL matrix
controls how many filters to apply. Up to 5 filters may be specified. The WINDOWS2 matrix must have a
start/stop time for each filter specified. The start/stop times are taken from the first row of the spreadsheet,
where a maximum of 5 start/stop times can be specified.
If the standard method is chosen, the user enters the center frequency in the start frequency parameter.
A bandwidth and floor must also be specified. The center frequency is at the center of the bandwidth. Half
the bandwidth will slope into the center frequency on each side to form a notch. The floor controls how
much rejection is performed. A 100% floor will perform complete rejection whereas a 50% floor will
remove half of the spectral amplitude.
In the adaptive method, the user enters a start and end frequency range. The bandwidth and floor must
also be specified. The program will search for the maximum spectral amplitude in the search range. This
frequency is then used as the center frequency of the notch. This method takes into account the frequency
that is intended to be rejected may change in time and space. Typically, as the energy to be rejected moves
to farther offsets, the frequency content changes.
821
Input Channels
Output Channels
Parameters
Notch filter method
Select to perform standard notch filter or adaptive notch filtering. In standard notch filtering, the user
specifies the frequency to reject, the bandwidth of the rejection, and the floor of the rejection. In the
adaptive method, the user specifies a starting and ending frequency for the search, the bandwidth, and the
floor. The modules will search within a time window on a trace for the maximum spectral amplitude
within the frequency search range. This frequency is then the center frequency for the rejection.
Options: Standard, Adaptive
Time variant?
Specify if the filter will be time and space variant. If No is selected then the user enters the start and stop
time of the filter operation. If Yes is selected, then the user enters the filter parameters into a matrix. The
time windows are entered into a separate matrix.
Start rejection frequency (Hz.)

Enter the maximum rejection (center) frequency in hertz for the standard method. If the adaptive
method was chosen, then this is the starting frequency of the search range.
End rejection frequency (Hz.)

This parameter is used for the adaptive method only. Enter the ending frequency in hertz of the search
range.
Rejection bandwidth (Hz.)

Enter the bandwidth of the rejection filter in hertz. The maximum frequency rejection will occur in the
middle of the bandwidth. The frequency rejection slopes into the maximum rejection on each side to form
a notch.
822
Rejection floor (%)

The user can specify to perform complete rejection in the notch or partial rejection. The floor percent
specifies how much rejection to perform. A 100% floor rejection will remove all spectral amplitudes at the
central frequency. Whereas a 50% floor will remove half the spectral amplitude at the central frequency. A
25% floor will reject 1/4 of the spectral amplitude at the central frequency. This option is used to control
how much of the spectral amplitude is actually removed.
Start time (ms.)

Enter the start time of the filter operation in milliseconds. This option will appear if the time variant
method was not selected. The seismic trace from the start time to the end time will be filtered.
End time (ms.)

Enter the end time of the filter operation in milliseconds. This option will appear if the time variant
method was not selected. The seismic trace from the start time to the end time will be filtered.
Primary header key

Enter the primary key for the NOTCHFIL and the WINDOWS matrices. The primary key is used to
control which NOTCHFIL and WINDOWS spreadsheet is used for the filter operation.
TLSN

Enter the secondary key for the NOTCHFIL and the WINDOWS matrices. The secondary key is used to
control which NOTCHFIL and WINDOWS spreadsheet is used for the filter operation.
TLSN

This matrix controls the start/stop times when using time variant filtering. Each row contains 5 start/stop
times. Only the first row is used in the spreadsheet. A maximum of 5 filters can be applied. The number of
filters specified is controlled by the number of filter rows defined in the next parameter (Filters). A
start/stop time must be specified for each filter.
823
Filters
This matrix contains the start/stop frequencies, the bandwidth, and the floor rejection parameters. A
maximum of 5 filters can be applied. Each filter must have a corresponding start/stop time in the
WINDOWS2 matrix.
Matrix Type: NOTCHFIL

A time value can be added to the start time by specifying this parameter.

A time value can be added to the end time by specifying this parameter.
824
NSUB
Module Description
Input Channels
Output Channels
Parameters
Module Description
NSUB is a noise subtraction module. The user specifies a narrow band of frequencies. NSUB will then
generate a reference noise trace of these frequencies, cross-correlate with the input data, and subtract their
power spectra. The effect is similar to a notch filter, but the result is achieved by subtraction rather than by
discriminating against certain frequencies with conventional bandpass filtering.
Input Channels
Output Channels
Parameters
Low 60 db down point of reference noise
Low 0 db down point of reference noise.
High 0 db down point of reference noise
High 60 db down point of reference noise
825
NTEXT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module NTEXT uses water velocity NMO to infill missing near traces in any prestack ensemble. The
offset difference between the first two near -offset real traces is used as the extrapolation offset increment.
The infilled (manufactured) traces will have the negative of their offset values in GCI header index 77.
Since the output is an ensemble with more traces than the input, the user must specify the maximum
number of traces that could be added by this module. If this number is exceeded during execution, an error
warning will be issued and the flow will abort. Optionally this module can be used after infill to remove
the manufactured traces. Removal is done if a negative values exists in GCI header index 77.
Input Channels
Output Channels
Parameters
Mode
NTEXT will add near traces or remove the added near traces based on a negative value in GCI header
index 77.
Options: Add near traces, Removed interpolated traces
Maximum number of traces to add

This value allows the module to inform the SeisUP exec of the maximum ensemble size for subsequent
modules in the flow.
826
Extrapolation velocity
This velocity value guides the NMO infill process. It should be the velocity of water which is about 1500
m/sec or around 5000 ft/sec.
827
OFFSCALE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module OFFSCALE builds a scalar for each offset in a dataset and outputs an SGNE matrix that can be
used in module SGNE2 to apply the scalars. The scalar is computed using a mean value in an analysis
window and then referenced to a user input mean. Use this tool to scale all offsets to a base amplitude
value so that all offsets have a comparable amplitude range.
This tool does not apply a scalar to the data. It outputs a SGNE matrix, which must then be used by
module SGNE2 to actually apply the scalar.
The tool computes a mean value in an analysis window. The window is rejected if the number of valid
(non-zero) samples falls below a user specified minimum. One mean value is computed in the analysis
window and then applied to the whole trace length. The scalar at each offset is computed as follows:
Scalar = reference mean / window mean.
Reference mean - this mean is specified by the user to bring all amplitudes to a base value.
Window mean - this mean is the averaged mean computed for all traces with a common offset value.
The tool outputs a SGNE matrix with the computed scalars. This SGNE matrix can then be used by
module SGNE2 to scale the data.
For this tool to work properly, it must have valid offsets in GCI header word DIST. The tool sums and
averages all the mean values for an offset to determine the scalar to apply.
Input Channels
Output Channels
828
Parameters
Start time (ms)
Specify the start time of the analysis window in milliseconds.
End time (ms)

Specify the end time of the analysis window in milliseconds.
Minimum offset
Specify the minimum offset to scale. All offsets less than the minimum will not be scaled.
Offset increment
This specifies the increment to compute the offsets. Example: 100, an offset curve will be output for every
100 ft or m.
Reference mean
Specify the base level mean. All traces amplitude will be scaled to this level.

Specify the percentage of samples in an analysis window that must be non-zero to use the windowed trace
in the mean computation. If the number of valid samples is less than this percentage, then the trace is not
used to compute the mean for the offset.
SGNE curve matrix

Specify the name of the SGNE matrix to output with the scalar data. This matrix can then be input into
module SGNE2 to apply the scalars to the data.
Matrix Type: SGNE
Absolute value or RMS

This parameter gives the user a choice of using the average absolute value or the RMS value to determine
the scale values.
829
OMIT
Module Description
Input Channels
Output Channels
Parameters
Module Description
OMIT is a trace editing program which allows the user to delete or reverse the polarity of traces by using
multi-dimensional matrices of primary, secondary and tertiary header values. All traces which are deleted
have the trace ID code set to 2 (flagged as dead trace), and also, optionally, have all trace amplitudes set to
zero.
Input Channels
Output Channels
Parameters
Primary header key
TLSN, other
Primary header key value

Required if Primary header key equal other.

TLSN, other
830
Secondary header key value

Required if Secondary header key equal other.
Tertiary header key

TLSN, other
Tertiary header key value

Required if Tertiary header key equal other.
Traces to omit
Matrix Type: OMIT
Traces to reverse polarity

Matrix Type: OMIT
Zero omitted traces

Options: YES, NO
831
OPTDCN1
Module Description
Input Channels
Output Channels
Parameters
Module Description
The module OPTDCN1 determines post-stack optimum deconvolution operators that would enhance the
signal amplitudes by "spiking" them within a specified bandwidth. Normally these operators are
determined within design windows where data quality is the best. The amplitude spectra of the design
operators are given by the square root of the cross-correlation power spectrum, which is divided by the
auto-correlation power spectrum within the specified bandwidth. The phase of the deconvolution operators
could be zero or minimum phase. Optionally, these operators can also remove the phase of the data to
convert them to zero phase, if the input data have minimum phase. During the removal of the phase, the
module can also add or subtract a constant phase to the data. The diagnostic plots to determine the
maximum lag value for the correlation traces, and the optimum parameters of low-frequency and
high-frequency cut-off values for each design window, are produced by an accompanying module
OPTDCNPL.
The present module also has options to generate CGM plots for average auto-correlation and
cross-correlation power spectra, amplitude and phase spectra of the deconvolution operator, and the
time-domain operator itself within each design window. Additionally, a CGM plot may be generated
showing the wavelet of the input data and the output wavelet which is produced by convolving the input
wavelet with the deconvolution operators. The wavelet of input data is determined with a phase
assumption that is consistent with the one selected for the deconvolution operator. As an example, we
show below the plots of the time-domain decon operator (for zero-phase assumption), the wavelet of the
input data with the same phase assumption, and the corresponding output pulse after deconvolution. These
plots are generated only if a CGM plot dataset is connected as an output. Note the operator(s) generated in
this module is(are) applied to the data using the OPTDCN2. module.
There are three possible outputs from OPTDCN1. The user may select "output", which will pass the data
on to another module. Selecting "Dataset for OPTDCN2" will create an output disk volume for the
operators which can then be accessed by OPTDCN2. Selecting "Dataset for CGM plot" will save the
wavelet and decon operator information in a CGM file as discussed above.
An example of CGM plot of time-domain operator with the zero phase option selected:
832
An example of wavelet of input data (in black) and the corresponding output wavelet (in red) after
deconvolution:
(Note: In this example, the input data are assumed to have zero phase, consistent with the zero-phase
option selected for the deconvolution operator. The output wavelet here has zero phase. Otherwise, it
would have mixed phase. Similarly, for minimum phase option of the operator, input data are also
assumed to have minimum phase, and the output wavelet would then have minimum phase. For the
remove-phase option of the operator, input data should also have minimum phase. But, in this case, the
output wavelet would have zero phase.)
Input Channels
833
Output Channels
2. Dataset for optdcn2: Required connection to dataset OPTDCN data type.
3. Dataset for cgm plot: Optional connection to dataset CGM data type.
Parameters
Phase Option for the Decon Operator
The phase option of the deconvolution operator normally should be chosen according to the phase of the
input data. For example, if the input data have zero phase, one should choose the zero-phase option of the
decon operator, otherwise, the output will have mixed phase. Similarly, one should choose the minimum
phase option of the operator, if the input data have minimum phase. If the input data have minimum phase,
one can then select the remove-phase option to convert these data to zero phase. During the phase
removal process, one can also add or subtract a constant phase (see below).
Options: Zero-phase, Minimum-phase, Remove-phase
Phase value (Degree) to be added(+) or subtracted(-)

Required if Phase Option for the Decon Operator = Remove-phase.
Percent of lag data points to be used for triangular tapering

Correlation traces are triangular-tapered before computing the power spectra. Normally, one should use
100% of lag data points for this tapering. If one chooses a smaller percentage of lag values, some of the
autocorrelation values for lags exceeding the percent of data points will not be used in computing the
power spectrum.
Lower limit of Signal-to-Noise ratio to accept a seismic trace

This is a threshold value to accept a seismic trace within the design window. The signal to noise ratio
calculated from the zero-lag values of the auto-correlation and cross-correlation traces is compared against
this threshold value to accept the corresponding seismic trace within the design window. This is designed
to prevent contamination of the deconvolution operators by poor data.
Horizontal Width of CGM plots

Note these plots are generated only if a CGM plot dataset is connected as an output
834
Vertical Width of CGM plots

See note above.
Time variant?
Maximum Lag (ms.)
Required if Time variant? = No
The maximum lag value is used to compute the correlation traces. Diagnostic plots generated by the
OPTDCNPL module help in determining this maximum lag value.
Decon Operator length(ms.)

Note, the larger the deconvolution operator, the more effective is deconvolution in attaining the desired
bandwidth. However, there is a trade-off. Large operator length may adversely affect the relative
amplitude relationship of seismic events if they are not far apart. To avoid this effect, operator length
should be comparable to the length of the seismic pulse.
Frequency point#1 for filtering operator spectrum

Required if Time variant?=No
The program applies cosine-square amplitude tapering between frequency point#1 and point#2,
constant-amplitude (=1.0) filtering between frequency point#2 and point#3, and again cosine-square
amplitude tapering between frequency point#3 and point#4.
This parameter should be chosen from the plot of the signal-to-noise ratio spectra generated by the
OPTDCNPL module.

OPTDCNPL module.
835

OPTDCNPL module.

OPTDCNPL module.

Required if Space variant design windows? = No
Note that the data quality should be good for the design windows.

Required if Space variant design windows? = No
See also note above.
Primary header key

Required if Time Variant? = Yes , or Space variant design windows? = Yes
TLSN
836

Required if Time variant? = Yes, or Space variant design windows? = Yes
TLSN
Design times
Required if Time variant? = yes, or space variant design windows? = Yes


Required if Time variant ? = No
Deconvolution operators for time-varying gates

Required if Time variant? = yes
Matrix Type: OPTDCN
Starting midpoint number

Number of midpoints
837
OPTDCN2
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module applies to data the optimum deconvolution operators for each design gate, that were
previously determined by the module OPTDCN1. The objectives for applying these decon operators are
described in the module description for OPTDCN1. Note that the application windows that are used in this
module could be larger than the corresponding design windows.
Input Channels
2. Dataset from optdcn1: Required connection from dataset OPTDCN data type.
Output Channels
Parameters
Time variant?
Primary header key
Required if Time variant?= yes.
TLSN

Required if Time variant? =yes.
838
TLSN
Application times
839
OPTDCNPL
Module Description
Input Channels
Output Channels
Parameters
Module Description
OPTDCNPL generates a plot of average auto-correlation and cross-correlation traces, a plot of average
auto and cross-correlation power spectra, and also a plot of signal-to-noise ratio spectra for a selected time
and/or space gates. Optionally, it can also generate a plot of auto and cross-correlation traces at a selected
CMP to check the quality of data. The time and/or space gates over which these plots are made, are called
design gates in this module. These design gates should be chosen where data quality is the best. Plots of
auto and cross-correlation traces are helpful in determining the maximum lag that would be required to
calculate proper auto and cross-correlation power spectra, and consequently, signal-to-noise ratio spectra.
The maximum lag in each time gate should normally be about two and half times the expected length of
the seismic pulse, unless multiples are present within this lag value. From the signal-to-noise ratio spectra,
one would chose the low and high cut-off frequencies that would be used in designing the deconvolution
operator(s). Below are some examples of the diagnostic plots created by the module OPTDCNPL for one
design gate, and how they help determine the parameters for the next module to be used, OPTDCN1.
Display #1: Average Auto-correlation (in black) and Cross-correlation (in red) vs. Lag (ms.) within the
design gate.
Note that for appropriate values of maximum lag, there should not be any effect of multiples or
non-primary events on both the auto- and cross-correlation traces. Multiples generally create "ringing" in
the correlation traces. If the maximum lag values chosen to create these plots are found to be
inappropriate, rerun this module with appropriate values of the maximum lag to generate the revised
displays. These displays, particularly the average signal-to-noise ratio spectra, will be needed to pick the
low-frequency and high-frequency cut-off values, for the module OPTDCN1 (see below).
840
Display #2: Average signal-to-noise ratio spectrum within the design gate.
From this display, one should chose the low frequency and the high-frequency cut-off values for the next
module OPTDCN1. To choose these cut-off frequencies, we recommend the signal-to-noise ratio values in
the range of 0.3 - 0.5 or higher. To help in selecting the cut-off frequencies for deconvolution, the plot
shows a red line where signal-to-noise ratio is 1.0.
Note that if we had not chosen a reasonable value for the DB Down parameter for the "signal" power (see
parameter description below.), then average signal-to-noise ratio could unrealistically be increasing at high
frequencies, mostly due to the effect of numerical noise in both the spectra.
Display #3: Average auto-correlation (in black) and cross-correlation (in red) power spectrum within the
design gate
This display also helps in assuring that the data quality within each design window is indeed good. The
auto-correlation power spectrum shows the contribution of both the signal and the noise, whereas the
cross-correlation power spectrum supposedly shows the contribution of the signal only. That is why the
peak values in the cross-correlation power spectra should normally be less than that of the auto-correlation
power spectra. Note that the average signal-to-noise ratio spectrum, shown as display #2, was NOT
generated from these two average power spectra. Instead, it was prepared by averaging the signal-to-noise
ratio spectrum for individual traces, which produced more reasonable values of the signal-to-noise ratio.
841
Input Channels
Output Channels
2. Dataset for CGM plot : Required connection to dataset CGM data type.
Parameters
DB down from peak for practical limits of signal power
This parameter is required in obtaining a reasonable signal-to-noise ratio spectrum plot. Beyond this DB
down value, signal power would be considered to be zero, which would cause signal-to-noise ratio values
decrease at high frequency values. Otherwise, the computed signal-to-noise ratio values may be increasing
at high frequencies. From our experience, the default value has been set to 15 DB .
Lower Limit of signal-to-noise ratio to accept a trace for spectrum plots

This threshold is used to screen seismic traces. The signal-to-noise ratio value computed for zero lag of
auto and cross correlation traces is compared with this threshold to accept the corresponding seismic trace
within the design window. This is a way in avoiding bad data in the design window.
Percent of lag data points to be used for cosine tapering

Auto and cross correlation traces are tapered at the end of the traces prior to computing power spectra
from these traces. This cosine tapering helps in reducing high-frequency noise in the power spectra. For
heavy smoothing, one should use a high percent value, and vice versa.
CMP# to plot a sample of auto-correlation and cross-correlation vs. lags

One can also plot a sample of auto and cross-correlation traces at any desirable CMP point within the
design window. The default value is the first trace within the design window. No plot will be generated if
the CMP# is negative. The plot of the correlation traces at a selected CMP to check the quality of data.
Horizontal Width of plot

This is the horizontal width of the CGM plots.
842
Vertical Width of plot

This is the vertical width of the CGM plots.
Time variant?
Maximum Correlation Lag (ms.)
Required if Time variant?= No. This maximum lag value should be such that no multiples or non-primary
events would be included in the auto and cross-correlation traces. Roughly, maximum correlation lag
should be the same as the length of the seismic pulse. If the Maximum Correlation lag values used to
generate the plots, are found to be inappropriate, rerun the module OPTDCNPL with appropriate values to
generate the revised plots. Normally, the maximum correlation lag value should be two and half times the
expected pulse length, unless multiples are present within this lag value.

Required if Space variant design windows?= No.

Primary header key

Required if Time variant? = Yes, or if Space variant design windows? = Yes
TLSN

Required if Time variant?=Yes, or if Space variant design windows? = Yes.
TLSN
843
Design times


Required if Time variant?= No.
Lag lengths (ms) for time varying gates

Matrix Type: OPTDCNP1
Starting midpoint number

Number of midpoints
844
OPTMUTE
Module Description
Input Channels
Output Channels
Parameters
Module Description
This program organizes data so that, when traces are viewed with the DISPLAY module, the user can
easily select an appropriate front end mute. The input to this program should be unmuted, moveout
corrected CMP gathers.
There are three options to process the data. The first is the Running Sum which progressively stacks the
traces. By watching where the waveform changes due to NMO stretch, the mute can be picked. Amplitude
characteristics of this option can be deceiving. This is described in section 3.2.2 of Seismic Data
Processing by Ozdogan Yilmaz.
The Offset Order option simply sorts the data by absolute offset.
The Binned option quantizes the offsets and stacks the traces by offset. Dead traces are output if there are
no traces in the offset range for the output trace.
The output from this program should only be used to pick mutes. The only headers that are updated are
DIST, FOLD, MBIN, MLIN and SDPN.
Input Channels
Output Channels
Parameters
Output option
Options: Running Sum, Offset Order, Binned
845
Number of ensembles to combine

In areas of small dips and poor signal to noise, the output can be improved by combining several
ensembles. This is not recommended for data with strong dips.
Far offset
Required if Output option = Binned.
Offset increment
Required if Output option = Binned.
846
PAD3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use PAD3D to pad a 2-D or 3-D stack volume so that every CMP position is defined.
Input Channels
Output Channels
Parameters
847
PICKSHIF
Module Description
Input Channels
Output Channels
Parameters
Module Description
PICKSHIF adds a user specified time to all first break picks in a matrix and outputs the shifted picks to a
new matrix.
Input Channels
1. None
Output Channels
1. None
Parameters
INPUT First Break Times Matrix
Select the first break pick matrix to have its values shifted.
Matrix Type: AFS1B
OUTPUT First Break Times Matrix

Type the name of the desired time shifted matrix.
Matrix Type: AFS1B
Bulk shift (ms)

Type the desired shift time in ms. This value may be positive or negative.
848
PILOT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program PILOT computes the relative time shifts for each trace using the pilot trace method. The pilot
traces can be either internally generated or from an input data set.
Internal Model Option

PILOT can generate internal pilot traces using the optimized stack power option. First, zero shifts are
assigned to each trace. A pilot trace is computed by stacking one or several CMP gathers. Then, all the
traces in the gather(s) are cross-correlated with the pilot trace over the prescribed window within which
the signal dominates. The relative time shift for each trace is defined by the peak of the crosscorrelation
function. Finally, the time shifts are updated for each trace and the trace is shifted.
The above process is repeated until the time shift increments are small enough in each iteration, or until
the iterations exceed the prescribed maximum number. Multiple passes may improve the quality.
NOTE - While run times with this option may be significantly longer than with the external model option,
the quality of the solution is generally better.
External Model Option

PILOT can also take an external model. In this case, each input trace is crosscorrelated with the
corresponding model trace. The static shift is computed in one iteration.
PILOT can support both random and sequential access to to the model. When the ensemble key and the
secondary key of the model are equal to secondary key and primary key of the input data respectively,
PILOT will access the model sequentially. The model will not be loaded into memory to save disk space.
However, if the above keying condition is not satisfied, PILOT assumes random access to the model and
the model is loaded into memory to avoid the requirement of sorting the input data. Please, be sure that
there is enough disk space available.
The statics can be either applied to the gather in a non-surface-consistent way or passed to program
PILOT2 for surface consistent solutions.
849
Input Channels
2. Input model pilot traces: Optional GCI data type.
Output Channels
1. Dataset of time picks for ras2: Optional connection to dataset RAS1 data type.
2. Trim gather: Optional connection to next process GCI data type.
Parameters
Use an input model?
NO, if no input model is connected. YES, if connected to an input model.
Start of window (ms)

Start of the cross-correlation widow.
End of window (ms)

End of the cross-correlation window.
Maximum correlation shift (ms)

The maximum static shift amount allowed in ms for each correlation. For the external model option, this is
the maximum static allowed. For the internally generated model, the maximum possible static is Maximum
correlation shift (ms) * Maximum iterations:.
Maximum iterations
Required if Use an input model? = No. Maximum number of iterations.
# of ensembles in pilot calculation

Required if Use an input model? = No. The number of CMP gathers to stack to obtain the pilot trace.
More than one ensemble can be used in the pilot trace computation if the input data are very noisy.
However, if there is severe dip in the data, one ensemble is preferred since multiple ensembles may mix
the data too much and give rise to an inaccurate pilot. # of ensembles in pilot calculation: is rounded up to
the nearest odd number.
850
CMP/BIN weighting method

Required if Use an input model? = No.
Options: Linear ramp, Equal weight
Minimum CMP/BIN number

Required if Use an input model? = Yes.
Maximum CMP/BIN number

Minimum line number

Maximum line number

Output a sequential statics matrix?

NOTE - Outputting a sequential statics matrix can significantly slow down the execution of the program.
The matrix is accessed by TLSN. With a large number of traces on input, simply writing out the matrix
can take a substantial fraction of the jobs CPU time. If the data is input where TLSN is generally
decreasing, the matrix may be written out many times to allow the working buffer to keep current.
Sequential statics matrix name

Required if Output a sequential statics matrix? = Yes.
Matrix Type: STATSEQ
851
PILOT2
Module Description
Input Channels
Parameters
Module Description
Program PILOT2 decomposes the relative time shifts picked by either PILOT into four terms: the source,
receiver, structure (CMP or bin) and residual NMO. The Gauss-Seidel iterative algorithm is used in
solving the following simultaneous equations:
SHFT = SRC + GEO + CMP + RNM*OFF*OFF
SHFT:
SRC :
GEO :
CMP :
RNM :
TIME SHIFT FROM PILOT.

SOURCE COMPONENT
GEOPHONE GROUP COMPONENT
STRUCTURE TERM
RESIDUAL NMO COEFFICIENT
The sum of the squared error is checked after each iteration; the program will stop iterating when the error
is smaller than Error limit (MicroSeconds) or the iteration exceeds Max. number of iterations.
Input Channels
1. Input: Required connection from dataset RAS1 data type.
Parameters
Error limit (MicroSeconds)
The desired error limit. The program will stop if the error becomes smaller than this limit.
Max. number of iterations

The program will quit when the iteration number exceeds this value even if the error is still larger than
Error limit (MicroSeconds) to prevent going into an infinite loop.
852
Source Statics file

Name for the file which contains the computed source statics. This name will be needed by RAS3.
Geophone Statics file

Name for the file which contains the computed receiver statics. This name will be needed by RAS3.
Weight each term?

Although most of the time this can be defaulted to NO, there are circumstances in which one wants to
damp one of the four terms, e.g. if you specify Source damping (% * 100) as 5000. The program will
divide the error in source statics by 1.5 (i.e. 1+5000*0.0001) before it sums up the total error, so that the
error in source terms will be less important relative to the other terms.
Source damping (% * 100)

Required if Weight each term? = Yes.
Geophone damping (% * 100)

CMP damping (% * 100)

Offset damping (% * 100)

Interval for RNMO and dip listing.
853
PKMIG
Module Description
Input Channels
Output Channels
Parameters
Module Description
PKMIG is a parallel Kirchhoff migration program. It employs the techniques described by Shang and Starr
(1991) to achieve anti-aliasing and amplitude preservation. The sampling interval along the operator,
instead of the trace, is selected according to sampling theorem so that operator aliasing is averted both
spatially and temporally. True amplitude preservation is accomplished by using a factor related to the
curvature of the operator.
PKMIG is capable of dividing a seismic trace into segments to distribute calculations to the processors. It
can achieve load balancing because each machine will take as many segments as fast as it can.
The aperture width needs to be large enough to ensure a complete migration of all the data. The
time-variant dip matrix allows dip limiting to bypass data that may not exist and increase the program
speed. The module KAPTURE can be used to compute the aperture.
PKMIG only accepts SDPN sorted stacked 2-D data, and either X-bin or Y-bin sorted stacked 3-D data.
Reference:
Shang, Z. and Starr Jr., E. W., 1991, Fast Solution to Amplitude, Phase and Aliasing Problems in Integral
DMO and Migration: SEG Expanded Abstracts of 61st Annual International Meeting.
Input Channels
Output Channels
854
Parameters
Aperture width (# of CMPs)
Side taper at start time(# of traces)
Side taper at end time(# of traces)
Top of trace taper (in ms)
Bottom of trace taper (in ms)
RMS velocities
Matrix Type: RMSVEL
Time variant dips

Matrix Type: TVDIP
Number of node processes

Restore mute?
Bin or CMP interval
Line spacing
855
PLOT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Input Channels
1. Previous process: Required connection from previous process GCI data type.
Output Channels
1. Plot data set: Required connection to dataset CGM data type.
Parameters
Show various display parameters
Options: Side label parameters, Control parameters, S.P.
annotations, Seismic trace display parameters, Profile parameters
With side label(s)?

Required if Show various display parameters = Side label parameters.
Side label location

Required if With side label(s)? = Yes.
Options: Left side, Right side, Both Left and Right sides
856
Side label width (inches)

Required if Show various display parameters = Side label parameters. NOTE: This parameter also
controls the font sizes of the annotations in the label, because each section is automatically adjusted to fit
into the label. The larger the value the larger the font sizes.
Vertical shift of Side label (inches)

Line name
Required if Show various display parameters = Side label parameters. Also used for line tie information
retrieval. See Regular line tie information.
Show direction of shooting

Options: By degrees, By words
Shooting degrees
Required if Show direction of shooting = By degrees.
Shooting direction
Required if Show direction of shooting = By words.
Shot point range

Processing title line 3


857

Where to draw logo?

Options: At the top of the field info, At the top of the area info,
None
Vertical shift of logo (inches)

Required if Where to draw logo? = At the top of the area info.
Is there company logo?

Required if Where to draw logo? not = None.
Logo of the company

Required if Is there company logo? = Yes.
Company name as logo

Required if Is there company logo? = No.
Logo height (inches)

Required if Where to draw logo? not = None.
Area info
Matrix Type: PLOTSINGLE
Marine data?
858
Draw diagram of boat?

Required if Marine data? = Yes.
Antenna to energy source distance

Required if Draw diagram of boat? = Yes.
Energy source depth

Distance from source to near trace

Streamer length
Streamer depth
Number of traces per shot

Near trace number

Options: Maximum trace number, one
Marine field data

Required if Marine data? = Yes.
Matrix Type: PLOTTRIP
General field recording

Required if Show various display parameters = Side label parameters. NOTE: When inputting the field
parameters, be sure to use both columns of the spreadsheet. If only the left-hand column is used, the
column titles will extend beyond the side label boundary.
859
Matrix Type: PLOTENTRY
Processing sequence
How to get display parameters?

Options: Automatically generate, Through custom list
Custom display parameters

Required if How to get display parameters = Through custom list.
Processing company info

Matrix Type: PLOTSINGLE
Draw logo in the above info?

Options: Yes. At the top, Yes. At the left side, Yes. At the bottom,
Yes. At the right side, No logo to be drawn
Logo height (inches)

Required if Draw logo in the above info? not = No logo to be drawn.
Logo of the company

Required if Draw logo in the above info? not = No logo to be drawn.
Fonts thickness amply by

860
Show orientation map?

Title for orientation map
Show orientation map annotation?
Orientation map annotation font size (inches)
Insert external graphics file
Required if With side label(s)? = Yes.
Title for external graphics

Required if Insert external graphics file = Yes.
File name of external graphics

Required if Insert external graphics file = Yes. The file should be located in home directory or Seisup
current line or full path must be given.
Time of the first sample

Required if Show various display parameters = Control parameters.
Starting time (ms)

Ending time (ms)

Annotate heavy lines?

Timing line interval with heavy lines (ms)

861
Annotate medium lines?

Timing line interval with medium lines (ms)

Annotate light lines?

Timing line interval with light lines (ms)

Annotate single dot thin lines?

Timing line interval with thin lines (ms)

Line type for the thin lines

Required if Timing line interval with thin lines (ms) > 0.
Options: Solid, Dash, Dot, Dash-dot, Dash-dot-dot
Plot time velocity table?

Format for anno. time-velocity lists

Required if Plot time velocity table? = Yes.
Options: Time and RMSV, Time RMSV and Interval
RMS velocities
Required if Plot time velocity table? = Yes.
862
Matrix Type: RMSVEL
Have line tie intersections?

How to define line tie?

Required if Have line tie intersections? = Yes.
Options: by regular line & SP, by custom matrix
Regular line tie information

Required if How to define line tie? = by regular line & SP. The regular line tie matrix describes which
line name and shot point pairs intersect with which other pairs. Line name is used in retrieving line tie
information from the matrix, which means With side label(s) must = Yes in order to get line ties. The line
name is not case sensitive in the matrix.
Matrix Type: PLOTLT
Custom line tie information

Required if How to define line tie? = by custom matrix. The custom line tie matrix describes at which
key (SDPN for 2-D or MLIN for 3-D) draw the corresponding line tie.
Matrix Type: PLOTLTCUS
Have special text annotation?

Special text information

Required if Have special text annotation? = Yes.
Matrix Type: PLOTNOTETEXT
Have well symbols annotation?

863
Well symbols
Required if Have well symbols annotation? = Yes.
Matrix Type: PLOTSYMBOLS
Well symbol height (inches)

Derrick symbol height (inches)

Plot the distance legend?

Where to put the legend?

Required if Plot the distance legend? = Yes.
Options: Beginning end only, Ending end only, Both ends
Offset to the end(s) (in inches)


Legend title
Options: Kilometer, Mile
Overlay ensembles?
Required if Show various display parameters = Control parameters. Whether to plot one section of
seismic traces on top of another.
864
Number of ensemble layers vertically

Required if Overlay ensembles? = Yes. This parameter can be set from 1 to 8. If set to 1, the plot is similar
to Overlaying ensembles? = No but has timing line annotation for all ensembles.
Align vertically?
Required if Overlay ensembles? = Yes.
Gap between ensembles?

Required if Overlay ensembles? = No.
Gap for missing traces?

S.P. selection
Required if Show various display parameters = S.P. annotations.
If From calculation, the shot point numbers are calculated by the formula: SP # = SDPN (or MLIN for
3-D line) * Scalar + Constant;
if From trace header:
Options: NONE, CDPN, DIST, FCSN, FSPN, OIDN, MBIN, MLIN, MSLN, RSBN,
RSLN, SDPN, SGEN, SBIN, SLIN, SSBN, SSLN, SSPN, TLSN, TIM1, TIM2,
Other
If From custom matrix, the shot point numbers are retrieved from the custom matrix by means of
SDPN(2-D line) or MLIN (3-D line) values.
Options: From calculation, From trace header, From custom matrix
Scalar to mul. CMP No. to get S.P.

Required if S.P. selection = From calculation.
Scalar = Sign (1 / number of CDPs per shot point)
Sign = + if the shot points are ascending - if descending
865
Constant additive to get S.P.

Required if S.P. selection = From calculation.
Irregular custom S.P. matrix

Required if S.P. selection = From custom matrix.
Matrix Type: PLOTSPMX
Draw dead trace at each S.P. anno. ?

Custom tic mark matrix

Matrix Type: PLOTTIC
Trace header name?

Trace header index?
First S.P.
Required if S.P. selection not = From custom matrix.
Last S.P.
Annotating Frequency in terms of S.P.

Tic marks anno. freq. in terms of S.P.

Dead trace anno. Freq. in terms of S.P.

866
Annotate CMP (MBIN for 3D) values?

Annotate S.P. values?

Where to plot S.P. group?
Options: At top only, At bottom only, Both ends
Annotation font size (inches)

Required if Show various display parameters = S.P. annotations. This parameter is the font size of the
timing lines, line ties and RMS velocity annotations.
Annotation font thickness (inches)

The plot display mode

Required if Show various display parameters = Seismic trace display parameters.
Options: Wiggle only, Positive VA, Negative VA, Wiggle & positive
VA, Wiggle & negative VA, Wiggle & both VA, Both VA only, Color only,
Color & wiggle, Wiggle & color VA, Color & wiggle & black positive
VA, Color & wiggle & black negative VA
Color scheme
Required if The plot display mode has Color.
Gray scale of positive VA fill

Required if The plot display mode = Positive VA or Wiggle & positive VA or Wiggle & both VA or
Both VA only.
Options: Black, Dark gray, Gray, Light gray, White
867
Gray scale of negative VA fill

Required if The plot display mode = Negative VA or Wiggle & negative VA or Wiggle & both VA or
Both VA only. See the next parameter for critical explanation.
Physical plot dot per inch

Required if Gray scale of positive VA fill not = Black or Gray scale of negative VA fill not = Black.
NOTE When the user wants a gray scale plot, this parameter has to be set to the actual value of the plotter
that prints the plot, otherwise by using the default value (200), the hard copy may not be what is expected.
Allow overlap VA?

Required if Gray scale of positive VA fill not = Black or Gray scale of negative VA fill not = Black.
Rectify samples?
Polarity at which to plot data

Required if Rectify samples? = No.
Automatic scaling?
Required if Show various display parameters = Seismic trace display parameters. If automatic scaling is
chosen, PLOT will compute the average RMS amplitude level over the first ensemble of traces. For
non-amplitude type data like RMS velocities or Hilbert transform attributes. The scaling is determined by
the minimum and maximum values.

Required if Automatic scaling? = No. Select No to specify the range of amplitudes using the gain in db.
and a bias. Select Yes to specify the range of amplitudes using the minimum and maximum values.
Gain (db)
Required if Automatic scaling? = No. The amount of gain in db to apply to the data before plotting.
868
Bias (%)
Required if Automatic scaling? = Yes or Specify amplitudes by a range of values? = No.

Required if Specify amplitudes by a range of values? = Yes. Specify the sample value corresponding to the
minimum clipped value. For color displays, this is the minimum color index.

Required if Specify amplitudes by a range of values? = Yes. Specify the sample value corresponding to the
maximum clipped value. For color displays, this is the maximum color index.
Clip (traces)
Required if Show various display parameters = Seismic trace display parameters. The number of trace
spacings from the baseline at which the variable area shaded side of the trace will be clipped. For color the
minimum and maximum amplitude can be determined from this parameter to scale the amplitudes over the
number of colors in the color map.
Overlay gain (db)

Required if The plot display mode has Color and Automatic scaling? = No. The amount of gain in db to
apply to the overlay data before plotting. This parameter requires the Overlay input channel to be
connected.
Overlay clip (traces)

Required if The plot display mode has Color. The number of trace spacings from the baseline at which the
variable area shaded side of the trace will be clipped. This parameter requires the Overlay input channel to
be connected.
Overlay bias
Required if The plot display mode has Color. This parameter requires the Overlay input channel to be
connected.
Plotting direction
869
Number of traces per inch

Required if Show various display parameters = Seismic trace display parameters. Enter the number of
traces per inch for the trace display.
Inches per second

Required if Show various display parameters = Seismic trace display parameters. Enter the number of
inches per second for the trace display..
Wiggle thickness (inches)

Draw any profiles?

Required if Show various display parameters = Profile parameters.
Options: None, Draw one profile, Draw two profile, Draw three
profile, Draw four profile, Draw five profile
Show the parameters of

Required if Draw any profiles? = Draw two profile.
Options: The first profile, The second profile

Required if Draw any profiles? = Draw three profile.
Options: The first profile, The second profile, The third profile

Required if Draw any profiles? = Draw four profile.
Options: The first profile, The second profile, The third profile,
The fourth profile
870

Required if Draw any profiles? = Draw five profile.
Options: The first profile, The second profile, The third profile,
The fourth profile, The fifth profile
Profile location
Required if Draw any profiles? = Draw one profile or Show the parameters of = The first profile.
Options: Top, Bottom
Preferred top value

Preferred bottom value

Profile style
Options: Continuous, Histogram
Height (inches)
Source of profile values

Required if Draw any profiles? = Draw one profile or Show the parameters of = The first profile. If
From header, the values are read from trace headers; If From sequential list, the values are read
sequentially from the custom list; If From key list, the user provide two keys and the matrix that use the
keys to retrieve values; If From Statics, the values are read from Geophone and Shot statics.
Options: From header, From sequential list, From key list, From
Statics
GCI header word

Required if Source of profile values = From header.
871
Options: CMP surface elevation (EC), Time horizon of 1st pick

(TIM1), Time horizon of 2nd pick (TIM2), Datum elevation at depth
point (DC), Number of traces summed (FOLD), other
GCI header word number

Required if GCI header word = other.
Custom list
Required if Source of profile values = From sequential list.
Matrix Type: PLOTLIST
Key-value matrix
Required if Source of profile values = From key list.
Matrix Type: PLOTPRF
First GCI header word as key1

Options: Receiver station bin #, Receiver station line #, Other
First header word number as key1

Required if First GCI header word as key1 = Other.
Second GCI header word as key2

Second header word number as key2

Required if Second GCI header word as key2 = Other.
Static plot type?

Required if Source of profile values = From Statics.
872
Geophone statics
Shot statics
Profile title
Profile location
Required if Show the parameters of = The second profile.
Preferred top value


Profile style
Height (inches)

Required if Show the parameters of = The second profile. If From header, the values are read from trace
headers; If From sequential list, the values are read sequentially from the custom list; If From key list,
the user provide two keys and the matrix that use the keys to retrieve values; If From Statics, the values
are read from Geophone and Shot statics.
873
Statics
GCI header word


Custom list
Key-value matrix



874

Static plot type?

Geophone statics
Shot statics
Profile title
Profile location
Required if Show the parameters of = The third profile.
Preferred top value


Profile style
875
Height (inches)

Required if Show the parameters of = The third profile. If From header, the values are read from trace
Statics
GCI header word


Custom list
Key-value matrix

876



Static plot type?

Geophone statics
Shot statics
Profile title
Profile location
Required if Show the parameters of = The fourth profile.
Preferred top value

877

Profile style
Height (inches)

Required if Show the parameters of = The fourth profile. If From header, the values are read from trace
Statics
GCI header word


Custom list
878
Key-value matrix




Static plot type?

Geophone statics
Shot statics
879
Profile title
Profile location
Required if Show the parameters of = The fifth profile.
Preferred top value


Profile style
Height (inches)

Required if Show the parameters of = The fifth profile. If From header, the values are read from trace
Statics
GCI header word

880

Custom list
Key-value matrix




Static plot type?

Geophone statics
881
Shot statics
Profile title
882
PMNORM
Module Description
Input Channels
Output Channels
Parameters
Module Description
This modules counts the number of traces per DMODIST/MLIN/MBIN cell, then stores this value in the
FOLD header of each trace belonging to that DMODIST/MLIN/MBIN. This value is later used in the
SCALE module to adjust pre-migration amplitudes.
Input Channels
Output Channels
Parameters
Check sort keys?
If YES, only ensembles with sort keys and order DMODIST, MLIN, MBIN will be processed. This order
is necessary to prepare the FOLD header to properly scale ensembles for pre-stack migration.
883
POLINT
Module Description
Parameters
Module Description
POLINT does polynomial velocity interpolation. First, all the velocity functions are used to calculate a
best fit polynomial. Then, interpolated values are computed from this polynomial. POLINT is
recommended when strong smoothing is desired. Caution should be used in extrapolation since the
polynomial outside the controlled area is unconstrained.
Parameters
Matrix Type: RMSVEL
Show parameters for

Number of terms in line

Number of terms cross line
Number of terms in time
Expected sample rate of the data
Velocity model type to compute
Output velocity type

Options: RMS, Interval, Average
884
Maximum time(ms.) or depth

Print input velocity function info.?
885
POWER
Module Description
Input Channels
Output Channels
Parameters
Module Description
POWER will raise amplitudes to a specified power using the following steps:
1. Determine a weighting factor for each sample by taking the average of the absolute values of the
samples over Window length (ms.).
2. The weighting factors are raised to the power (Power factor - 1) and then applied to the input trace.
3. The resulted trace is then normalized to the same level as the input trace before output.
In general, POWER may be used to enhance the stronger signals and attenuate the weaker ones. The
resultant seismic traces thus become more sparse and have a cleaner look. On the other hand, if the
exponent (Power factor - 1) is less than 1 or negative, the weaker signals will be enhanced relative to the
stronger ones.
Input Channels
Output Channels
Parameters
Window length (ms.)
It is recommended that the window length be at least as great as half the period of the dominant signal in
the data in order to minimize waveform distortions.
886
Power factor
887
PSI3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
PSI3D performs prestack / poststack time migration on common-offset data. NMO, DMO, and the inverse
NMO should be applied before PSI3D for prestack imaging. If PSI3D is applied directly after DMO
without the inverse NMO, only poststack option should be used for common-offset migration. For
prestack migration, the primary header key of the input data must be DMODIST. PSI3D can handle
vertical velocity variations and the first order of horizontal velocity variations. It can take RMS velocities
from either a velocity matrix or a VIP file. The migrated common-offset data can be sorted back to CMP
gathers for residual velocity analysis or creating final migration stack.
Reference
Gardner, G. H. F., Wang, S. Y., Pan, N. D., and Zhang, Z., 1986, Dip-moveout and prestack imaging:
Ann. Mtg. Offshore Tech. Conf., Expanded Abstracts, Vol. 2, 75-81.
Input Channels
2. VIP velocity traces: Optional connection from dataset SEGY data type.
Output Channels
Parameters
Migration option
Options: Poststack Migration, Prestack Migration
888
Velocity handling
Options: Single Velocity Function, Spatially Variant Velocities
RMS velocities
Matrix Type: RMSVEL

Output matrix of migration velocity
Matrix Type: RMSVEL
Migration start time (ms)

Migration end time (ms)
Output sample rate (us)
This parameter defines the sample rate (microseconds) of the output traces. It can be different from the
input sample rate. Choosing a greater value than the input sample rate can reduce the run time of PSI3D.
This parameter should be limited to (500000/Maximum Frequency). The minimum value for this
parameter is 20.0.

Radial increment (distance units)
889
Migration aperture
Migration dip limit (degrees)
Fidelity of the antialias filter interpolation
This parameter specifies the fidelity of the antialias filter interpolation. The higher the fidelity of the
anti-alias filter interpolation, more the disk space and memory required, and slower the speed.
Percentage for adding back aliasing noise

Percentage for padding traces
This parameter specifies a percentage of the maximum number of padding traces for eliminating the
wraparound. The maximum number of padding traces is determined automatically in the program based
on the size of the survey and the migration aperture. The default of this parameter is set to zero. That is no
padding traces around the end of the section so it may cause upswings of migration but a faster execution
time.

Restore mute?
890

NMO mutes
Are you running on a Cluster?

This parameter Are you running on a Cluster? is set to Yes when running a job on a multi-node (more than
one node) cluster. If the job is being run on a multi-cpu SMP machine, this parameter should be set to No.

This parameter is available when the parameter Are you running on a Cluster? is set to No. This parameter
specifies the number of CPUs you are running this job on.
Number of cpus on the Master node

This parameter is available when the parameter Are you running on a Cluster? is set to Yes. This
parameter specifies the number of CPUs on the master node of the cluster where this job will be run. The
number of CPUs on the master node will determine how the fast the pre-processing is performed. For Big
surveys, this is a significant amount of time
Number of Nodes in the cluster

This parameter is available when the parameter Are you running on a Cluster? is set to Yes. This
parameter specifies the number of nodes of the cluster, on which this job will be run.
Compute node list


891
PSMIG2D
Module Description
Input Channels
Output Channels
Parameters
Module Description
Two of the most attractive features of phase shift migration are its capability to handle arbitrary vertical
velocity functions and its capability to migrate up to 180 degrees. PSMIG2D is a two-dimensional phase
shift migration. It can migrate turning waves as well as steep dips. Using a first order approximation,
PSMIG2D can handle smooth horizontal velocity variation.
PSMIG2D may produce a better image if the velocity function is scaled in some cases. The user can scale
the velocity function in a space-time variant manner. But the percentage variation in the CMP direction
should be smooth to avoid distortion of events.
The phase-shift migration operator is an anti-aliasing filter by nature. Therefore, when the steep dips and
overhung events are the targets of the migration, the preservation of low frequencies becomes very vital.
The multiples of the turning wave should be removed to make the geologic features, such as salt domes,
look clean.
Two-pass phase-shift migration will be equivalent to the one-pass 3D phase-shift migration if PSMIG2D
is instructed to compute only one velocity function for the migration. However, the user is encouraged to
input more than one velocity function since PSMIG2D will compute the average velocity function and this
average velocity function is generally smoother than any particular function. This will result in a smoother
migration operator.
In the FK domain, some of the areas are to be migrated outside of the FK space on the output section.
However, retaining some of this data will help to make the output section look less "wormy". With
PSMIG2D a percentage of this noisy data can be stacked back to the output section.
PSMIG2D can migrate 3D data and prestack 2D data in two passes.
PSMIG2D uses next closest "prime-factorable number" in the Fourier Transforms. This "prime-factorable
number" is not the prime number in normal algebraic sense. It is actually composed of mutually prime
factors from the set of {2,3,5,7,9,11,13}. The following is a list of the corresponding "prime-factorable
numbers" used in PSMIG2D. In phase shift migration, the time samples are doubled before rounding up to
the next "prime number". This is to avoid wrap-arounds. In the inline and cross line directions, the padded
number of traces is used directly.
From
1
2
3
5
To
1
2
4
6
Corresponding "Prime number"

1
2
4
6
892
7
9
11
13
15
17
19
21
23
25
27
29
31
33
37
41
43
45
49
53
57
61
67
71
73
79
81
85
89
91
97
105
111
113
121
127
131
133
141
145
155
157
161
169
177
181
183
199
209
211
221
225
235
241
253
261
265
8
10
12
14
16
18
20
22
24
26
28
30
32
36
40
42
44
48
52
56
60
66
70
72
78
80
84
88
90
96
104
110
112
120
126
130
132
140
144
154
156
160
168
176
180
182
198
208
210
220
224
234
240
252
260
264
280
8
10
12
14
16
18
20
22
24
26
28
30
32
36
40
42
44
48
52
56
60
66
70
72
78
80
84
88
90
96
104
110
112
120
126
130
132
140
144
154
156
160
168
176
180
182
198
208
210
220
224
234
240
252
260
264
280
893
281
287
289
309
313
331
337
353
361
365
391
397
417
421
441
463
469
481
505
521
529
547
561
573
617
625
631
661
673
721
729
771
781
793
841
859
881
911
925
937
991
1009
1041
1057
1093
1121
1145
1171
1233
1249
1261
1321
1387
1431
1441
1457
1541
286
288
308
312
330
336
352
360
364
390
396
416
420
440
462
468
480
504
520
528
546
560
572
616
624
630
660
672
720
728
770
780
792
840
858
880
910
924
936
990
1008
1040
1056
1092
1120
1144
1170
1232
1248
1260
1320
1386
1430
1440
1456
1540
1560
286
288
308
312
330
336
352
360
364
390
396
416
420
440
462
468
480
504
520
528
546
560
572
616
624
630
660
672
720
728
770
780
792
840
858
880
910
924
936
990
1008
1040
1056
1092
1120
1144
1170
1232
1248
1260
1320
1386
1430
1440
1456
1540
1560
894
1561
1585
1639
1681
1717
1761
1821
1849
1873
1981
2003
2017
2081
2185
2289
2311
2341
2465
2521
2575
2641
2731
2773
2861
2913
3081
3121
3169
3277
3361
3433
3641
3697
3745
3961
4005
4291
4369
4577
4621
4681
5041
5149
5281
5461
5545
5721
6007
6161
6241
6553
6865
6931
7281
7393
7921
8009
1584
1638
1680
1716
1760
1820
1848
1872
1980
2002
2016
2080
2184
2288
2310
2340
2464
2520
2574
2640
2730
2772
2860
2912
3080
3120
3168
3276
3360
3432
3640
3696
3744
3960
4004
4290
4368
4576
4620
4680
5040
5148
5280
5460
5544
5720
6006
6160
6240
6552
6864
6930
7280
7392
7920
8008
8190
1584
1638
1680
1716
1760
1820
1848
1872
1980
2002
2016
2080
2184
2288
2310
2340
2464
2520
2574
2640
2730
2772
2860
2912
3080
3120
3168
3276
3360
3432
3640
3696
3744
3960
4004
4290
4368
4576
4620
4680
5040
5148
5280
5460
5544
5720
6006
6160
6240
6552
6864
6930
7280
7392
7920
8008
8190
895
8191
8581
8737
9241
9361
10011
10081
10297
10921
11089
11441
12013
12321
12871
13105
13729
13861
14561
8580
8736
9240
9360
10010
10080
10296
10920
11088
11440
12012
12320
12870
13104
13728
13860
14560
15840
8580
8736
9240
9360
10010
10080
10296
10920
11088
11440
12012
12320
12870
13104
13728
13860
14560
15840
Input Channels
Output Channels
1. Phase shift migrated data: Required connection to next process GCI data type.
Parameters
Output option
Options: Normal wave only, Turning wave only, Both waves
Time variant dip filter

Required if Output option = Normal wave only.
Matrix Type: XYDIP
RMS velocities
Matrix Type: RMSVEL
896
Velocity handling
Options: Spatially variant velocities, Compute one velocity

Spatially variant velocity scaling?
Velocity percentages
Required if Spatially variant velocity scaling? = Yes.
Matrix Type: TSVP
Velocity % to use at trace start

Required if Spatially variant velocity scaling? = No.
Velocity % to use at trace end


This is the number of zero traces to pad to both sides of the section Decreasing this parameter will result in
a faster execution time but data at the ends of the section could wrap around to the other side of the section
and cause upswings. Increasing this parameter will increase execution time and could avoid artifacts on
the sides of the section. Ideally this parameter should be the maximum depth divided by four times the
midpoint bin interval. However, if mostly flat data is at the ends of your section a smaller number will do.
897

execution time.
Bin/CDP interval
Line interval
Min. frequency to migrate(Hz)

Required if Output option: = Normal wave only.
Max. frequency to migrate(Hz)

Side taper at trace start(# of traces)
Side taper at trace end(# of traces)
Restore mute?
Stack back random noise?
Stack-back noise percentage?
Required if Stack back random noise? = Yes.
898
PSMIG3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
PSMIG3D is a 3D phase shift migration which has accurate handling of vertical velocity variations and a
first order approximation of horizontal velocity variations. PSMIG3D can migrate up to 180 degrees, i.e. it
can do turning-wave migration or overhang imaging. The turning wave portion only takes a very small
portion of the computation time after the normal wave migration.
In some cases, PSMIG3D may produce a better image if the velocity function is scaled. The user can scale
the velocity function in a space-time variant manner. The percentage variation in BIN/LINE direction
should be smooth to avoid distortion of events. If the input velocity is not VIP velocity, the velocity needs
to be interval velocity to save conversion time. VIP works in the interval velocity domain directly and no
conversion is necessary.
The phase-shift migration operator is an anti-aliasing filter by nature. Therefore, when steep dips and
overhang events are the targets of the migration, the preservation of low frequencies becomes vital. The
multiples of the turning wave should be removed to make the geologic features, such as salt domes, look
clean.
In the FK domain, some of the areas to be migrated are outside of the FK space on the output section.
However, retaining these data will help to make the output section look less "wormy". With PSMIG3D a
percentage of the noisy data can be stacked back to the output section.
PSMIG3D can restart after an abnormal exit. It can fully recover and continue the migration if it was
aborted through geodraw. Any other unplanned abort may cause information loss and restart may produce
imperfect results. However, most of the time, the result will be acceptable.
If PSMIG3d was interrupted during the input phase, the user can restart from the last input line. Input at
restart will overwrite the last input. No parameters, or matrices or velocity files should be changed
between start and restart or restart and restart. Otherwise, the results wont be correct.
The CPU time required by PSMIG3D is determined by several factors. The following guide lines assume
single process and no paging. The speed of PSMIG3D is approximately linearly proportional to:
1. the product of the transform dimensions of inline, crossline and time. (Printed out in the status file)
2. the square of high-cut frequency when 1) is fixed. The low-cut does not have much influence.
The above are the two most important and decisive factors. Other factors, such as the velocity function,
also influence the speed but on a much smaller scale than the above two factors. Resampling the data can
substantially reduce the execution time as well as the demand for other resources, such as memory and
899
disk space. Before resampling the data, make sure that the data is bandpass-filtered to avoid aliasing. For
example, migration at 75 Hz and 4ms can be resampled to 6ms, you will save one third of the memory,
disk space and running time. If possible, cutting down the frequency to 55 Hz will reduce running time
almost by half. (from 1 to (11/15)**2, i.e. 0.54.)
PSMIG3D prints out the percentages each node has accomplished. These numbers are only an estimate
since there are many factors which effect the speed of the process. If PSMIG3D is the only process
running and does not page memory, these numbers are within +/- 5%.
PSMIG3D uses next closest "prime factorable number" in the Fourier Transforms. This "prime factorable
number" is not a simple prime number in an algebraic sense. It is actually composed of mutually prime
factors from the set of {2, 3, 4, 5, 7, 8, 9, 11, 13, 16}. The following is a list of the corresponding "prime
factorable numbers" used in PSMIG3D and PSMIG2D. In phase shift migration, the time samples are
multiplied by Time padding ratio (%): / 100 before rounding up to the next "prime factorable number".
This is to avoid wrap-arounds. In the inline and cross line directions, the padded number of traces is
directly used. To be efficient, PSMIG3D uses different transforms (complex or real). If you want to know
the next prime factorable number, you need to know the dimensions of the ensemble key and secondary
key. This list is for reference only. The actual dimension may be a larger one than the one given if the
larger one saves computation time. See the status file.
From
1
2
3
5
7
9
11
13
15
17
19
21
23
25
27
29
31
33
37
41
43
45
49
53
57
61
67
71
73
79
81
To
1
2
4
6
8
10
12
14
16
18
20
22
24
26
28
30
32
36
40
42
44
48
52
56
60
66
70
72
78
80
84
FFT dimension for

Ensemble Key
From
1
1
2
2
4
3
6
4
8
5
10
6
12
7
14
8
16
9
18
10
20
11
22
12
24
13
26
14
28
15
30
16
32
17
36
19
40
21
42
22
44
23
48
25
52
27
56
29
60
31
66
34
70
36
72
37
78
40
80
41
84
43
FFT dimension for

To Secondary key
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
10
11
11
12
12
13
13
14
14
15
15
16
16
18
18
20
20
21
21
22
22
24
24
26
26
28
28
30
30
33
33
35
35
36
36
39
39
40
40
42
42
44
44
900
85
89
91
97
105
111
113
121
127
131
133
141
145
155
157
161
169
177
181
183
199
209
211
221
225
235
241
253
261
265
281
287
289
309
313
331
337
353
361
365
391
397
417
421
441
463
469
481
505
521
529
547
561
573
617
625
631
88
90
96
104
110
112
120
126
130
132
140
144
154
156
160
168
176
180
182
198
208
210
220
224
234
240
252
260
264
280
286
288
308
312
330
336
352
360
364
390
396
416
420
440
462
468
480
504
520
528
546
560
572
616
624
630
660
88
90
96
104
110
112
120
126
130
132
140
144
154
156
160
168
176
180
182
198
208
210
220
224
234
240
252
260
264
280
286
288
308
312
330
336
352
360
364
390
396
416
420
440
462
468
480
504
520
528
546
560
572
616
624
630
660
45
46
49
53
56
57
61
64
66
67
71
73
78
79
81
85
89
91
92
100
105
106
111
113
118
121
127
131
133
141
144
145
155
157
166
169
177
181
183
196
199
209
211
221
232
235
241
253
261
265
274
281
287
309
313
316
331
45
48
52
55
56
60
63
65
66
70
72
77
78
80
84
88
90
91
99
104
105
110
112
117
120
126
130
132
140
143
144
154
156
165
168
176
180
182
195
198
208
210
220
231
234
240
252
260
264
273
280
286
308
312
315
330
336
901
45
48
52
55
56
60
63
65
66
70
72
77
78
80
84
88
90
91
99
104
105
110
112
117
120
126
130
132
140
143
144
154
156
165
168
176
180
182
195
198
208
210
220
231
234
240
252
260
264
273
280
286
308
312
315
330
336
661
673
721
729
771
781
793
841
859
881
911
925
937
991
1009
1041
1057
1093
1121
1145
1171
1233
1249
1261
1321
1387
1431
1441
1457
1541
1561
1585
1639
1681
1717
1761
1821
1849
1873
1981
2003
2017
2081
2185
2289
2311
2341
2465
2521
2575
2641
2731
2773
2861
2913
3081
3121
672
720
728
770
780
792
840
858
880
910
924
936
990
1008
1040
1056
1092
1120
1144
1170
1232
1248
1260
1320
1386
1430
1440
1456
1540
1560
1584
1638
1680
1716
1760
1820
1848
1872
1980
2002
2016
2080
2184
2288
2310
2340
2464
2520
2574
2640
2730
2772
2860
2912
3080
3120
3168
672
720
728
770
780
792
840
858
880
910
924
936
990
1008
1040
1056
1092
1120
1144
1170
1232
1248
1260
1320
1386
1430
1440
1456
1540
1560
1584
1638
1680
1716
1760
1820
1848
1872
1980
2002
2016
2080
2184
2288
2310
2340
2464
2520
2574
2640
2730
2772
2860
2912
3080
3120
3168
337
361
365
386
391
397
421
430
441
456
463
469
496
505
521
529
547
561
573
586
617
625
631
661
694
716
721
729
771
781
793
820
841
859
881
911
925
937
991
1002
1009
1041
1093
1145
1156
1171
1233
1261
1288
1321
1366
1387
1431
1457
1541
1561
1585
360
364
385
390
396
420
429
440
455
462
468
495
504
520
528
546
560
572
585
616
624
630
660
693
715
720
728
770
780
792
819
840
858
880
910
924
936
990
1001
1008
1040
1092
1144
1155
1170
1232
1260
1287
1320
1365
1386
1430
1456
1540
1560
1584
1638
902
360
364
385
390
396
420
429
440
455
462
468
495
504
520
528
546
560
572
585
616
624
630
660
693
715
720
728
770
780
792
819
840
858
880
910
924
936
990
1001
1008
1040
1092
1144
1155
1170
1232
1260
1287
1320
1365
1386
1430
1456
1540
1560
1584
1638
3169
3277
3361
3433
3641
3697
3745
3961
4005
4291
4369
4577
4621
4681
5041
5149
5281
5461
5545
5721
6007
6161
6241
6553
6865
6931
7281
7393
7921
8009
8191
8581
8737
9241
9361
10011
10081
10297
10921
11089
11441
12013
12321
12871
13105
13729
13861
14561
3276
3360
3432
3640
3696
3744
3960
4004
4290
4368
4576
4620
4680
5040
5148
5280
5460
5544
5720
6006
6160
6240
6552
6864
6930
7280
7392
7920
8008
8190
8580
8736
9240
9360
10010
10080
10296
10920
11088
11440
12012
12320
12870
13104
13728
13860
14560
15840
3276
3360
3432
3640
3696
3744
3960
4004
4290
4368
4576
4620
4680
5040
5148
5280
5460
5544
5720
6006
6160
6240
6552
6864
6930
7280
7392
7920
8008
8190
8580
8736
9240
9360
10010
10080
10296
10920
11088
11440
12012
12320
12870
13104
13728
13860
14560
15840
1639
1681
1717
1821
1849
1873
1981
2003
2146
2185
2289
2311
2341
2521
2575
2641
2731
2773
2861
3004
3081
3121
3277
3433
3466
3641
3697
3961
4005
4096
4291
4369
4621
4681
5006
5041
5149
5461
5545
5721
6007
6161
6436
6553
6865
6931
7281
7921
8009
8191
8581
9010
9241
9361
10011
10297
10921
1680
1716
1820
1848
1872
1980
2002
2145
2184
2288
2310
2340
2520
2574
2640
2730
2772
2860
3003
3080
3120
3276
3432
3465
3640
3696
3960
4004
4095
4290
4368
4620
4680
5005
5040
5148
5460
5544
5720
6006
6160
6435
6552
6864
6930
7280
7920
8008
8190
8580
9009
9240
9360
10010
10296
10920
11088
903
1680
1716
1820
1848
1872
1980
2002
2145
2184
2288
2310
2340
2520
2574
2640
2730
2772
2860
3003
3080
3120
3276
3432
3465
3640
3696
3960
4004
4095
4290
4368
4620
4680
5005
5040
5148
5460
5544
5720
6006
6160
6435
6552
6864
6930
7280
7920
8008
8190
8580
9009
9240
9360
10010
10296
10920
11088
11089
11441
12013
12871
13105
13861
11440
12012
12870
13104
13860
15015
11440
12012
12870
13104
13860
15015
Input Channels
2. VIP velocity dataset: Optional SEGY data type.
Output Channels
1. Migrated data: Required connection to next process GCI data type.
2. PSMIG3D-saved dataset: Required connection to dataset PSM data type.
Parameters
Restart?
Output option
Options: Normal wave only, Turning wave only, Both waves
Time variant dip filter

Matrix Type: XYDIP
RMS velocities
Matrix Type: RMSVEL
Velocity handling
Sometimes the overhang may be better imaged by computing one average velocity.
Options: Spatially variant velocities, Compute one velocity
904

Minimum interval velocity allowed.

Maximum velocity allowed.
Spatially variant velocity scaling?

Velocity percentages
Required if Spatially variant velocity scaling? = Yes.
Matrix Type: TSVP
Velocity % to use at trace start

Velocity % to use at trace end


This is the number of zero traces to pad to both sides of the inline midpoint bins. Decreasing this
divided by four times the midpoint bin interval. However, if mostly flat data is at the ends of your section
905

This is the number of zero traces to pad to both sides of the crossline midpoint lines. Decreasing this
divided by four times the midpoint line interval. However, if mostly flat data is at the ends of your section

execution time.
Bin/CDP interval
Line interval
Minimum frequency to migrate(Hz)

Maximum frequency to migrate(Hz)

Inline side taper at start time(# of traces)
Inline side taper at end time(# of traces)
Crossline side taper at start time(# of traces)
Crossline side taper at end time(# of traces)
CMP fold attribute
Matrix Type: DBFOLD
906

Restore mute?
Add back random noise?
Noise-stackback Percentage?
Required if Add back random noise? = Yes.
Number of processors?
Run-time QC slices
Matrix Type: PSMQC
907
PSUTIL
Module Description
Parameters
Module Description
PSUTIL is a utility which is used to generate different kinds of velocities. It is able to generate PS
migration velocities to perform post-stack seismic migration and PS RMS velocities. The PS migration
velocity is estimated using Harrisons equation (Harrison, 1992). The calculation of the the PS RMS
velocity can be estimated using either seismic or well information. When we use seismic information we
are referring to the P-wave RMS velocity obtained from the velocity analysis of conventional PP data and
the Vp/Vs ratio. When we use well information we are referring to Vp and Vs interval velocities obtained
from dipolar sonic logs. Here the traveltimes are one way.
References
Harrison, M.P., 1992, Processing of P-SV surface seismic data, anisotropy analysis, dip moveout and
migration: PhD thesis, University of Calgary.
Parameters
Velocity to calculate:
Options: PS migration velocity, RMS Vps, Interval Vs
Using:
Required if Velocity to calculate: is RMS Vps.
Options: Seismic information, Well information
Vp RMS velocities
Required if Velocity to calculate: is PS migration velocity or Using: is Well information.
Matrix Type: RMSVEL
Vps RMS velocities

Required if Velocity to calculate: is PS migration velocity or Interval Vs.
908
Matrix Type: RMSVEL
Vp/Vs ratio
Required if Velocity to calculate: is PS migration velocity or Interval Vs or Using: is Well information.
Vp interval velocity
Required if Velocity to calculate: is RMS Vps and Using: is Well information.
Matrix Type: RMSVEL
Vs interval velocity
Required if Velocity to calculate: is RMS Vps and Using: is Well information.
Matrix Type: RMSVEL
PS Migration velocity, output file:

Required if Velocity to calculate: is PS migration velocity.
Matrix Type: RMSVEL
PS RMS velocity, output file:

Required if Velocity to calculate: is RMS Vps.
Matrix Type: RMSVEL
Interval S-wave velocity, output file:

Required if Velocity to calculate: is Interval Vs.
Matrix Type: RMSVEL
909
PTHROW
Module Description
Input Channels
Output Channels
Parameters
Module Description
PTHROW computes first break pick times for a target shot from surrounding shots with existing picks. It
can be run on any shot ordered dataset but was designed for 3D. For a target shot, PTHROW reads
surrounding candidate shots within a user specified radius (through a separate flow pipe connected directly
back to the input dataset). For each candidate shot with picks the channels locations are analyzed for
distance from a target channel (projection distance) and for corresponding (shot to receiver) offset with a
target channel so pick stats can be accumulated for a target channel within the user menu specs. After all
candidate shots are read and stats for all eligible channels are accumulated, a pick for each channel is
computed and output to the first break pick matrix.
Input Channels
2. Direct: Required GCI data type.
Output Channels
Parameters
Minimum offset of interest
The user may only be interested in picking traces with some minimum offset.
Maximum offset of interest

The user may only be interested in picking traces with some maximum offset.
910
Offset distance tolerance

If the candidate trace has a shot-to-receiver offset within this distance difference of a target trace
shot-to-receiver offset, the pick from this candidate trace will be used in the computation of this target
traces first break pick.
Maximum projection distance

If the candidate trace is within this distance from the target trace, the pick from this candidate will enter
into the pick computation for this target trace.
Shot radius
Only shots within this distance from the target shot will be used in pick computations.
Statistics option
Each target trace will get a pick from statistical analysis of surrounding picks if this selection is YES.
Correlation option
Each target trace will be correlated with each eligible candidate trace to get a pick statistic for this target
trace if this selection is YES.
Correlation gate width (ms)

A gate of samples surrounding a pick on a candidate trace will be used to generate the correlation statistic.
Maximum time shift (ms)

Maximum correlation search time above and below the pick time.
Minimum correlation coefficient

If the normalized cross-correlation peak is below this value the correlation statistic from this candidate
trace will not be used in pick determination for a target trace.
Alpha-trim Mean percent

The pick for a target trace will be resolved by an alpha-trim analysis on the statistics for this target trace.
This parameter is the percent of the values unused at the ends after the statistics are sorted.
911
Mute velocity
A mute is applied at this velocity to reduce noise prior to statistics estimation. This mute MUST be above
all first break times.
OUTPUT first break picks matrix

This is the name of the output first break pick matrix. If the user has sparsely picked the first breaks,
PTHROW will honor those picks and use them as a guide to pick other first breaks. If the matrix is empty,
PTHROW will pick the first breaks as well as it can with no guide function.
Matrix Type: AFS1B
Pick feature
This will be a PEAK or TROUGH or none (no feature - raw pick).
Options: Trough, Peak, None
Feature search zone (ms)

The target trace will be scanned in both directions around the raw computed pick to find the desired
feature. If no feature is found the raw pick time will be output.
912
PTSLICE
Module Description
Input Channels
Output Channels
Parameters
Module Description
PTSLICE will plot time slices created by module CUT3D to a CGM dataset. PTSLICE will get the
number of midpoint bins per plot from the maximum number of traces per ensemble associated with the
data set. For SEG-Y data sets, this number is defined as a parameter in SEGYREAD.
Input Channels
Output Channels
1. CGM plot: Required connection to dataset CGM data type.
Parameters
Plot type
A dual polarity plot will fill the positive and negative variable area with a color and the negative samples
will be rectified to the right. A color cell plot consists of a rectangle for each sample. A continuous
contour plot will interpolate colors between defined samples. For color plots, the color corresponds to the
amplitude after gain is applied.
Options: Wiggle variable area, Variable area, Dual polarity, Color
cell, Continuous contour
913
Title
This string along the the time slice value will be annotated.
Gain (db)
Amount of gain to apply to the amplitudes prior to plotting.
Clip (traces)
Colormap
See CMAP data type for a description of the custom color maps.
Gaussian Smoothing
Apply a Gaussian smoothing algorithm to plot data.
Gaussian Operating Radius

How many neighboring pixels to take into consideration when blurring the current pixel when using the
Gaussian smoothing option.
Gaussian Sigma
Determines the strength or amount of effect neighboring pixels have on the current pixel when using the
Gaussian smoothing option.
Scaling Factor
How much to increase the resolution. A scaling factor of 2 will double the plots resolution.
Edited on 04/7/04 by CJB
914
PWAVO
Module Description
Module PWAVO performs basic AVO analysis (amplitude variation with offset) on P-wave data. The core
of the module functionality is a set if three options given to the user:
1. Computation of AVO intercept and gradient
2. Computation of AVO three polynomial coefficients
3. Computation of azimuthal AVO attributes
Coherent and random noise might degrade the AVO analysis. Noise can be reduced on the CMP gathers
by angle and offset-mixed super gathers as well as offsets-consistent amplitude corrections.
2D data
One of the most popular approximations for the P-wave reflection coefficient R iso pp between two
isotropic homogeneous layers separated by a horizontal flat interface, is the expression given by Shuey
(1985):
where is the incidence angle. Coefficients A,B,C are known as intercept, gradient, and 3rd coefficient,
respectively. All three coefficients can be estimated with module PWAVO.
Intercept and Gradient. Coefficients A,B are computed using a LS linear curve fitting estimation. Two
methods are used: standard linear regression, and Robust linear regression (Walden, 1991).
Three polynomial coefficients. All three coefficients A,B,C are computed using a LS second degree
polynomial curve fitting algorithm.
3D data
In the case of 3D data, azimuthal AVO attributes can be computed, based on Jenners algorithm (Jenner,
2002) (see Appendix).
Polarity Gates
915
each polarity gate.
Velocities
then it is recommended to smooth the velocities in the VIP program and not in AVOA.
Time Gates
References
916

Jenner, E., 2002, Azimuthal AVO: Methodology and data examples. The Leading Edge, August 2002,
p.782-786
Ruger, A., Reflection Coefficients and Azimuthal AVO Analysis in Anisotropic Media. SEG, Geophysical
Monograph Series No.10, 2001.
Zhang, H., Brown, J., A review of AVO analysis. CREWES research report 13, 2001.
Input Channels
1. Seismic input
Required
GCI data type
Module PWAVO works on 2D or 3D data. If 2D, data must be a CMP gather; if 3D, data must be a
common-bin sorted gather. In both cases, NMO correction should be already applied to the data (a
NMO-algorithm that appropriately considers anisotropy should be used when necessary).
Output Channels
1. Attribute pseudostack sections (see Appendix)
Required
GCI data type
917
Each pseudostack section has four stack traces, each one identified with a DIST header word value. Each
trace shows the value of a particular attribute vs time:
Option Intercept and gradient (linear fit)
Trace 1
DIST=19
Intercept(t)
Trace 2
DIST=20
Gradient(t)
Trace 3
DIST=21
Std.Deviation(t)
Trace 4
DIST=22
(void)
Option Three coefficients (polynomial fit)
Trace 1
DIST=19
C0(t)
Trace 2
DIST=20
C1(t)
Trace 3
DIST=21
C2(t)
Trace 4
DIST=22
Std.Deviation(t)
Option Azimuthal attributes (3D data)
Trace 1
DIST=19
Beta(t)
Trace 2
DIST=20
G1(t)
Trace 3
DIST=21
G2(t)
Trace 4
DIST=22
Std.Deviation(t)
A schematic of each output pseudostack is shown in the attached figures.
918
919
Parameters
The user has 3 items to select from a toggle list:
1. Intercept and Gradient (linear fit)
2. Three coefficients (polynomial fit)
3. Azimuthal attributes (3D data only)
Normalize amplitudes? (yes/no):

Allows the user to compute AVO attributes with regularized amplitudes. Valid only for options
Intercept and Gradient (linear fit) and Three coefficients (polynomial
fit).
AVO amplitude fit will be done?:

A common problem with AVO attribute stacks is residual NMO on the CMP gathers because of imperfect
velocity analysis. To compensate, amplitudes may be selected within polarity gates, thereby relieving the
requirement of exact NMO application. Polarity gates are computed using a stack of the CMP gather. The
amplitudes in the gate are used to compute a maximum value. The maximum value for each trace in the
gather is used in the best-fit analysis. The output values are blocked as constant values over each polarity
gate. Options:
1. At each sample
2. Polarity gate
Least squares method:

1. Standard Least Squares
2. Robust Least Squares
Maximum incident angle (deg.)

degrees (Shuey, 1985). However, PWAVO renders this as a parameter at the users discretion. PWAVO
will mute the data that has an angle of incidence greater than this maximum angle.
Minimum incident angle (deg.)

Seismic data at less than 3 degrees tends to be noisy and of poor quality. PWAVO renders this as a
parameter at the users discretion. PWAVO will mute the data that has an angle of incidence that is less
than this minimum angle.
920

survey.
Start time (ms.)

End time (ms.)


The next four parameters are used to adjust the start / end times from the matrix.
Primary window header key

Primary window header ID
Secondary window header key
Secondary window header ID
Header key to add to window start
Header ID to add to window start
921
Header key to add to window end

Header ID to add to window end
RMS velocities
Matrix Type: RMSVEL
Velocity smoothing filter length (ms):

A time domain running average filter can be applied to smooth the velocity function. The filter length
should be entered in milliseconds.
Input gather type:

Options:Offset gathers, Incident angle gathers
Header key for incident angle

Required if Input gather type: equals Incident angle gathers.
Options:none, CDPN, DIST, FCSN, FSPN, MBIN, MLIN, MSBN, MSLN, OIDN,
TLSN, other
Header ID for incident angle

Required if Header key for incident angle equals other.
922
Appendix
.............................
Pseudo-stack sections
By a pseudo-stack section we understand a gather in which traces display one value of an attribute per
time sample per CMP location.
For example, if a least-square best-fit linear approximation is used to compute a gradient pseudostack,
then the following algorithm can be used:
1. In a 2D dataset, take a NMO-corrected CMP gather with n traces.
2. For time t 1 , step through offsets to pick the (n-1) sample
amplitudes x i of traces 1 to n in the gather.
3. Use conventional least-squares to estimate the gradient (slope) of a
R P iso (theta) vs sin 2 (theta) plot with (n-1) samples.
923
4. Plot this single value of gradient as a point on a CMP-vs-time plot,

in the coordinates (CMP, t 1 ).
5. Repeat steps (1)-(3) for all times t i .
6. Repeat steps (1)-(4) for all CMP gathers.
7. Once all times and CMP gathers have been considered, the entire
resulting plot is called a gradient pseudo-stack section.
.............................
924
Azimuthal attributes
According to Ruger (1996), the equation for amplitude variation with incidence angle (up to approx. 35
degrees) and azimuth for an HTI layer overlain by an isotropic overburden can be approximated by
where theta=angle of incidence, phi=the source-receiver azimuth with respect to a predefined direction,
(e.g., true north), and beta=the angle between the chosen zero azimuth direction and either the isotropy or
symmetry axis planes (i.e. parallel or perpendicular to the fractures). I is the p-wave impedance contrast
divided by two. G 1 is the isotropic AVO gradient and G 2 (the anisotropic gradient) can be approximated
by
Without knowing beta, the first equation cannot be solved by linear-squares. However, such an equation
can be rewritten as
A least-squares fit of amplitudes can now be performed on equation this, without azimuth or offset
binning. This means that all available data are used and each point is represented at the correct offset and
azimuth. In addition, meaningful error estimates can be obtained.
The variables involved can be computed by the following expressions
925
Author:
Created on 2006 by P.Mora.
926
QC3D
Module Description
Parameters
Module Description
QC3D is a host stand-alone process which reads the 3-D Marine coordinate database and creates a report
file for quick check.
The report consists of the following information :
For each shotpoint: (Optional)
FSPN
SBIN
SPX
SPY
STNEAR
STFAR
AGTRINT
SAZIMUTH
TNEAR
TFAR
SINVL
Field shotpoint number.

Sequential shot bin number.
Shot X coordinate.
Shot Y coordinate.
Shot to receiver distance for the near offset.
Shot to receiver distance for the far offset.
Average geophone interval within the shot.
Azimuth from previous shot to current shot
Distance from the near trace on the previous shot to near
trace on the current shot
: Distance from the far trace on the previous shot to far
trace on the current shot
: Distance from the previous shot to the current shot.
:
:
:
:
:
:
:
:
For each line:

LINE
SLIN
NSHOTS
FSPN1
FSPNN
MINSND
AVGSND
MAXSND
MINSFD
AVGSFD
AXSFD
MINSAZ
AVGSAZ
MAXSAZ
MINSIN
AVGSIN
MAXSIN
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Line name
Sequential shot line number
Number of shots
First shot point number
Last shot point number.
Minimum shot to near distance
Average shot to near distance
Maximum shot to near distance
Minimum shot to far distance
Average shot to far distance
Maximum shot to far distance
Minimum azimuth from shot to shot
Average azimuth from shot to shot
Maximum azimuth from shot to shot
Minimum distance from shot to shot
Average distance from shot to shot
Maximum distance from shot to shot
For the project:
927
Minimum
Minimum
Maximum
Maximum
X
Y
X
Y
coordinate
coordinate
coordinate
coordinate
Note: The azimuth above is the direction in degrees where zero degrees is to the east.
Parameters
Print all shots?
Print lines
Options: all, include, exclude
Lines to include or exclude

Matrix Type: LINES
928
QCMUTE
Module Description
Output Channels
Parameters
Module Description
This module will use a user-specified mute matrix to create a color time slice plot and save it as a CGM
file.
Output Channels
1. CGM Output: Output CGM file.
Parameters
Mute type
Options: Trace, Contour
Primary header key

Options: MBIN, MLIN

Options: MBIN, MLIN
Mute functions
Matrix Type: MUTE
929
Primary header key

Options: MBIN, MLIN

Options: MBIN, MLIN
Mute functions
Matrix Type: MUTECONT
Colormap
Color contour?
Contour lines?
930
QCOMP
Module Description
Input Channels
Output Channels
Parameters
Module Description
Q compensation attempts to reverse the effects of wave propagation through an anelastic (not perfectly
elastic) earth. The two major effects of anelastic propagation are wave amplitude reduction and dispersion
(different velocities for different frequencies). This program is a phase only Q compensation program, so
it only attempts to compensate for the dispersion effect.
References
Inverse Q filtering by Fourier transform, 1991, Hargreaves, N., and Calvert, Geophysics v. 56, no. 4, pp.
519-527.
Input Channels
Output Channels
Parameters
Dispersion type
Two common models for the type of dispersion are the Futterman and Kjartansson models. These describe
different velocity variations with frequency. At normal frequencies, and for Q values greater than 5, the
two models are nearly identical. There is no run time difference between the dispersion types.
Options: Futterman, Kjartansson
931
Zero time-reference header

Inverse Q filters are fundamentally time dependent. If desired, the Q filtering may take some non-zero
time as a time origin. This is like applying a static shift, filtering the data below the new zero time, and
then reversing the static. Note that all the window start times are relative to the zero time-reference, i.e.,
the data for each Q window are selected after the trace is shifted to the zero time-reference. The zero
time-reference must be contained in either the tim1 or tim2 headers. The time should be in milliseconds.
The tim1 and tim2 headers may also be used as header to add to the Q window start time, so be aware of
possible conflicts.
Time Variant Q?
The Q value may be constant for the whole trace, or be described by a series of constant Q windows. The
run time of the program depends directly on the number of windows, i.e. three gates will take
approximately three times as long to run as one gate.
Q value
Option for NOT Time Variant Q only. For a constant Q, enter the Q factor. Large (in the 500-infinity
range) Q will have little effect on the data, while low Q (50-100) will act like a spiking deconvolution
filter.
Reference Frequency
Option for NOT Time Variant Q only. The reference frequency is just used in scaling the stretching of
frequencies within the program. A typical choice is the maximum frequency in the data or the Nyquist
frequency.
Fixed Q Gates
Option for Time Variant Q but NOT Space Variant Q only. Enter the matrix where the Q model is
described. Up to five windows may be described by entering their start times (in milliseconds). For each
window the Q is constant from the start time to the beginning of the next gate, or the end of the data. For
each window, a reference frequency is given, this is just used in scaling the stretching of frequencies
within the program. A typical choice is the maximum frequency in the data or the Nyquist frequency.
Matrix Type: QCOMPF
Q and Fref values

Option for Time Variant and Space Variant Q only. Enter the matrix where the Q value and reference
frequency for each window are specified. The start times for the windows as a function of position are
described in the "Q start times" matrix (see below).
932
Matrix Type: QCOMPV
Space Variant Q?
The Q window start times may change as a function of location, or not.
Q start time
Option for one Q window and NO Space variation. The start time is referenced to the zero
time-reference header (see below).
Primary header key

Option for Space variant Q only. If the Q model changes as a function of location, select one of the
keys, or headers which will be used to describe the Q model.
TLSN

Option for Space variant Q only. Select another header (optional) which will be used to describe the
model.
TLSN
Q Start & end times

Enter the name of the matrix where the Q model is described. This matrix may be graphically built in a
seismic data display. The Q windows may depend on two keys, typically these are data sorting keys, such
as CMP, offset, shot, etc. The Q start times between supplied keys are filled in by linear interpolation.
Times must increase. The start times are referenced to the zero time-reference header, see below. If Q is
NOT time variant i.e. only one window, only the first window in the WINDOWS2 matrix will be input.
Header to add to Q start time

A complex Q model may be best described as a set of times at various keys to get the general trend, to
which a header variable is added (perhaps a water bottom, uphole time, etc.) This header must be copied
into either the tim1 or tim2 headers. The tim1 and tim2 headers may also be used as a zero time-reference
header, (see above) so be aware of possible conflicts.
933
934
QCVEL
Module Description
Parameters
Module Description
This module will perform QC and repair of the velocities in a RMSVEL matrix. It will also flag but not
repair incorrect times.
The program fits the time-velocity pairs for a CMP to a least-squares straight line or a smoothed curve.
The mean distance from each point to the line is computed and then an overall average mean is computed.
A user specified value is multiplied times the mean to determine the distance from that line that constitutes
a bad velocity value. All velocity values that are outside of the value*mean distance will be flagged as
bad. All velocities that are less than or equal to zero are automatically flagged as bad and not used in the
least-squares/smoothed curve computation.
The value*mean can be increased or decreased to control bad velocity value selection. Increase the value
and less velocity numbers will be flagged as bad. Decrease the value to flag more velocity numbers as bad.
An option is to flag velocity inversions as bad. A velocity inversion occurs when a velocity decreases with
time. If inversions are flagged, they are not used in the least-square/smoothed curve computation.
The user can select to repair velocities that are flagged as bad. Two methods are employed: 1) Interpolate
a new value from the surrounding good values, 2) Take the velocity from a user specified matrix of
time-velocity pairs. If the interpolation method is selected, the program takes good values on each side of
the velocity in question to compute a new velocity. If the time-velocity matrix method is used, the user
builds a QCVELWIN matrix. The matrix will contain time and velocity pairs. During repair, the repair
velocity is taken from the matrix at the corresponding time zone.
The module will also flag incorrect times. An incorrect time is when the time value before it in the array is
less than or equal to the current time. This module will not repair incorrect times.
An option is to fix water velocity for marine survey. User can specify water velocity for velocity matrix.
Parameters
RMS velocities
Select the RMSVEL matrix to perform QC.
Matrix Type: RMSVEL
935
Fix water velocity for marine survey?

Select yes to fix water velocity for marine survey.
Water velocity(feet/meters)
Enter the water velocity value.
Method to fit velocity vs. time curve

Two methods are used to fit the time-velocity pairs from a CMP. In least-squares, a least squares straight
line is fitted to the valid data. In smoothed curve, a smooth curve is computed from the data. These
computed lines are used as the basis for computing mean distances.
Options: Smoothed Curve, Least Squares
Flag velocity out of range?

Select to flag velocities that are considered out of range. Out of range velocities are computed using the
fitted line and the value*mean distance. All velocities that are farther than the value*mean distance will be
flagged as bad.
( Value * mean ) which flags velocity out of range

Enter the value, which is multiplied times the mean to determine out of range velocities. A small value
will flag more velocities as bad. Whereas a large value will flag less velocities as bad. This number can be
changed to manipulate the number of out of range velocities to flag.
Flag velocity inversions?

Select yes to flag velocity inversions as bad. A velocity inversion has decreasing velocity with time.
Repair velocity values?

Select to repair the values that are flagged as bad.
Repair method
Select the method used to repair bad velocity values. If the interpolation method is selected, the program
takes good values on each side of the velocity in question to compute a new velocity. If the time-velocity
matrix method is used, the user builds a QCVELWIN matrix. The matrix will contain time and velocity
pairs. During repair, the repair velocity is taken from the matrix at the corresponding time zone.
Options: Interpolation, Time Window
936
Time versus velocity matrix name

This matrix contains time-velocity pairs. This matrix is used for repairing bad velocity values.
Matrix Type: QCVELWIN
937
QCVIEW
Module Description
QCVIEW provides a way to graphically view geometry related attributes. The pre-defined options for the
parameter View selection are:
1.
2.
3.
4.
5.
6.
7.
Custom Pick
Map view
2-D surface diagram
2-D sub-surface diagram
Fold distribution
2-D surface profile
3-D
Custom Pick
With the Custom Pick option, the user is able to customize a 2-D or 3-D plot by defining the attributes for
each axis of the plot. If the user chooses the option Custom Pick, a dialog will pop up when executing
QCVIEW.
938
The top list is a SHOT ordered list of shot line names. The user may select all or any combination of shot
lines to display.
The bottom list are lower level attributes. There are two buttons associated with the attribute list. If the
order is SHOT, they are labeled as SBIN and FCSN. If SBIN is pressed, the shot level attributes will be
shown in the list; if FCSN is pressed, the channel level attributes will be the ones showing (traces within
the shot). If the order is MIDPOINT, only one button is shown labeled MBIN which is the midpoint bin
within a midpoint line. Similarly, if the order is GEOPHONE, only one button is shown labeled RSBN
which is the geophone bin within a geophone line.
Custom Pick buttons

Select all:
Select all shot lines for display.
Deselect all:
Deselect all shot lines for display.
Order:
Switch the current order to either SHOT, MIDPOINT, or GEOPHONE. The X, Y, Z, Color, and
select attribute must all be from the same order.
Create new plot:
Will allow the user to create an additional plot on top of a the already defined plot(s).
View:
Create the custom designed plot.
Pick selection vector:
Allows the user to select an attribute for selecting a range of attributes to view at a time. To use this
button, press once with the left mouse button. The label will change to To pick an attribute. Then
pick an attribute from the attributes list. The user can re-pick by repress the button again.
Selecting axis attributes

To select an attribute for an axis, press the axis button to the left and then select attribute for that particular
axis. Press an already selected attribute again to unselect it. At the minimum an attribute must be selected
for the X and Y axis. If a Z attribute is selected a 3-D plot will be produced. If a Color attribute is
selected, the value displayed will be a scaled color within the current colormap. Multiple plots may be
selected for 2-D plots.
2-D plot interaction

In the 2-D plot viewing window, use the following buttons:
Print:
Output the plot to a plotter.
Color ..:
Edit colors.
939
Show grid:
Enable or disable the visible grid.
X Axis Reverse:
Reverse the X axis.
Y Axis Reverse:
Reverse the Y axis.
To zoom, press the left mouse button. Drag the rubber band box over the area you wish zoom. Release the
mouse button to initiate the zoom operation. Press the middle mouse button to unzoom to the previous
level.
Press the right mouse button will cause the point closest to the cursor position to stand out marked by a
black surrounding rectangle and the values of that point will be printed out on the right side. Subsequent
release of the right mouse button will make all this disappear.
3-D plot interaction

In the 3-D viewing window, use the following buttons:
Zoom out.
Zoom in.
Rotate left.
Rotate right.
Rotate up.
Rotate down.
Snap shot.
Animate snap shots.
Print image to a plotter
940
Exit.
Press and hold the left mouse button to rotate the object in the direction of the mouse movement.
Press and hold the middle mouse button to zoom the object. Move to the right to zoom in and to the left to
zoom out.
Press the Control key at the same time as the left or middle mouse button to only draw the cube frame
while moving the object. When the mouse is released, the full image will be drawn.
Type
Stand alone
Input Channels
None
Output Channels
None
Parameters
View selection
Default .....:Map view
Name ........:view
Options .....:
Custom Pick
Map view
2-D surface diagram
2-D sub-surface diagram
Fold distribution
2-D surface profile
3-D
941
Default .....:None
Name ........:map_sel
Options .....:
None
Sequential shot(SSPN)
Plot shots?
Default .....:Yes
Name ........:shot_opt
Options .....:
Yes
No
Color attribute for shots

Default .....:None
Name ........:shot_clr
Options .....:
None
Shot depth(SD)
Uphole time(SU)
Shot elev.(SE)
Shot static
Shot gain
Shot statics to plot

Default .....:
Name ........:shot_stat
Matrix type .:STATSRC
Shot gain to plot

Default .....:
Name ........:shot_gain
Matrix type .:RMSSSPN
942
Plot receivers within a shot?

Default .....:No
Name ........:rshot_opt
Options .....:
Yes
No
Color attribute for receivers within a shot

Default .....:None
Name ........:rshot_clr
Options .....:
None
First break
Azimuth
S-R distance
Receiver gain
First break attribute to plot

Default .....:
Name ........:rshot_brk
Matrix type .:AFS1B

Default .....:
Name ........:rshot_gain
Matrix type .:RMSFCSN
Plot midpoints?
Default .....:No
Name ........:mid_opt
Options .....:
Yes
No
943
Color attribute for midpoints

Default .....:None
Name ........:mid_clr
Options .....:
None
Azimuth
S-R distance
Plot midpoint cell center?

Default .....:No
Name ........:grid_opt
Options .....:
Yes
No
Color attribute for cell center

Default .....:None
Name ........:grid_clr
Options .....:
None
Fold
Midpoint elevation
Fold attribute to plot

Run the program FOLD and enter an attribute name for the parameter "DB fold attribute name". before
selecting the attribute name here.
Default .....:
Name ........:grid_fold
Matrix type .:DBFOLD
Plot receiver layout?

Default .....:No
Name ........:rec_opt
944
Options .....:
Yes
No
Color attribute for receiver layout

Default .....:None
Name ........:rec_clr
Options .....:
None
Receiver elevation
Receiver static
Total static
Geophone statics
Default .....:
Name ........:rec_stat1
Matrix type .:STATGEO
Shot statics
Default .....:
Name ........:rec_stat2
Default .....:None
Name ........:2d_sel
Options .....:
None
Sequential line #(SLIN)
Sequential shot #(SSPN)
Display shots as
Default .....:Sequentially
Name ........:2d_type
945
Options .....:
Sequentially
Surface consistent
Diagram type
Default .....:Receivers
Name ........:2d_surf
Options .....:
Receivers
Shots
Color attribute for receivers

Default .....:None
Name ........:2d_rec_clr
Options .....:
None
First break
Azimuth
S-R distance
Receiver gain

Default .....:
Name ........:2d_rec_brk
Matrix type .:AFS1B

Default .....:
Name ........:2d_rec_gain
Color attribute for shots

Default .....:None
Name ........:2d_shot_clr
946
Options .....:
None
Shot gain
Shots gain attribute to plot

Default .....:
Name ........:2d_shot_gain
Default .....:None
Name ........:2d_sub_sel
Options .....:
None
Sequential line #(SLIN)
Sequential shot #(SSPN)
Color for midpoints

Default .....:None
Name ........:2d_sub_clr
Options .....:
None
First break
Azimuth
S-R distance
Receiver gain

Default .....:
Name ........:2d_sub_brk
Matrix type .:AFS1B
947

Default .....:
Name ........:2d_sub_gain
Default .....:None
Name ........:fold_sel
Options .....:
None
Midpoint line #
Fold

Run the program FOLD and enter an attribute name for the parameter DB fold attribute name. before
Default .....:
Name ........:fold_mx
Plot shot static?

Default .....:Yes
Name ........:p_shot_s
Options .....:
Yes
No
Shot static attribute to plot

Default .....:
Name ........:p_shot_stat
948
Plot shot elevation?

Default .....:No
Name ........:p_elev
Options .....:
Yes
No
Plot shot depth?

Default .....:No
Name ........:p_shot_d
Options .....:
Yes
No
Plot uphole time?

Default .....:No
Name ........:p_shot_up
Options .....:
Yes
No
Plot receiver static?

Default .....:No
Name ........:p_rec_s
Options .....:
Yes
No
Receiver statics attribute to plot

Default .....:
Name ........:p_rec_stat
949
Plot total statics?

Default .....:No
Name ........:p_tot_s
Options .....:
Yes
No
Shot statics name

Default .....:
Name ........:p_tot_stat1
Receiver statics name

Default .....:
Name ........:p_tot_stat2
Plot receiver elevation?

Default .....:No
Name ........:p_ge
Options .....:
Yes
No
3-D plot
Default .....:Shots
Name ........:3d_opt
Options .....:
Shots
Receivers
Midpoints
950
Attribute for the Z-value & color

Default .....:Shot depth(SD)
Name ........:3d_z_1
Options .....:
Shot depth(SD)
Uphole time(SU)
Shot elev.(SE)
Shot static
Shot gain
Shot static attribute

Default .....:
Name ........:3d_z1stat
Shot gain attribute

Default .....:
Name ........:3d_z1gain

Default .....:Receiver elevation
Name ........:3d_z_2
Options .....:
Receiver elevation
Receiver static
Total static
Receiver statics attribute

Default .....:
Name ........:3d_z2stat1
951
Shot statics attribute

Default .....:
Name ........:3d_z2stat2

Default .....:Midpoint elevation
Name ........:3d_z_3
Options .....:
Midpoint elevation
Fold

Run the program FOLD and enter an attribute name for the parameter "DB fold attribute name". before
Default .....:
Name ........:3d_z3fold
Color scheme
Default .....:yellow_red_blue_11
Name ........:colormap
Options .....:Output generated by command:sup_cmaps
Dot pattern
Default .....:Default
Name ........:dottype
Options .....:
Default
Single point
952
Correlate colorbar?
Default .....:Yes
Name ........:iclbar
Options .....:
Yes
No
AUTHOR
Created on Apr. 20, 1995 by Bill
953
QDERIVE
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module produces estimates of Q-value within a time window, that can be used in other modules such
as QCOMP and AMPCOR. It uses a spectral ratio method applied on move-out corrected data. For each
selected offset in the input data, power spectra are calculated near the window top and bottom,
respectively, and logarithmic spectral ratio values of these two spectra are determined. An average Q value
within the window are then estimated by fitting a straight line through this data ( See Figure-1 below). It is
assumed that the input data has been corrected for spherical divergence, using at least an exponential AGC
for a moderate window (say, 400 ms).
Figure-1: Log spectral ratio values (in black) and the straight-line fit (in red) for Q estimation at a selected
offset distance.
This module also averages the spectral data over the selected offset and frequency ranges to prepare a
similar estimate for Q (see Figure-2 below). Hence, this estimate is likely to be the most reliable one.
Figure-2: AVERAGE log spectral ratio values of all selected offset distances (in black) and straight line fit
(in red) for Q estimation.
954
In the execution status of this module, there is a list of Q values determined for each selected offset
distance, and for the average spectra of all selected offsets. Overall average Q-value is also listed. In the
optional CGM output, there are plots of log spectral ratio data and the straight lines fitting these data.
Given this list and the optional CGM plots, the user can judiciously select the appropriate Q-value to be
used for the specific time window. (Note the CGM plots are generated only when a CGM output disk is
connected to the QDERIVE module.)
Input Channels
Output Channels
1. Dataset for cgm plot: Optional connection to dataset CGM data type.
Parameters
Start time (milliseconds) for Q-estimation
Note the start time and the end time defines the middle of each time window for which the average Q
value is estimated in this module. If the default is used, the first time window will be from 0 to record
length divided by two and the second time window will be from the record length divided by two to the
record length. If six second data is input, the start time is 2000, and the end time is 4000, the length of the
window will be 2000 ms. (4000-2000). The first time window will be from 0 to 3000 and the second time
window will be from 3000 to 5000.
955
End time (milliseconds) for Q-estimation

See the note for the Start time
Starting CMP Bin for Q-estimation

Note spectral ratios are averaged over several CMP bins for reliability in the Q-estimates. 5-10 CMP bins
are suggested for this averaging.
Ending CMP Bin for Q-estimation

See note for the starting CMP bin
Starting CMP Line for Q-estimation

Ending CMP Line for Q-estimation
Lower limit in Offset in each CMP bin for Q-estimation
One may select the offset range for Q estimation. Generally, far-offset traces have NMO stretch that may
affect Q-determination. Near-offset traces, on the other hand, may be too noisy, and may not have enough
sensitivity to Q. So, 1000-6000 offset range should generally produce better estimates of Q than other
ranges. Note, Q-values are estimated for each offset separately, and for average spectral ratio computed
from all selected offsets.
Upper limit in Offset in each CMP bin for Q-estimation

See note for the Lower limit in Offset
Offset increment within each CMP bin for Q-estimation

This is the desired increment between offset panels for Q-estimation.
Lower limit in frequency for Q-estimation

The user has an option to select the frequency range for Q determination, particularly for the straight line
fit of the log spectral ratio data. Note, larger the frequency, larger is the sensitivity to Q. However, seismic
signal is band-limited with a peak around 20 Hz. So, 5-60 Hz range should generally produce better
estimates of Q than other ranges.
956
Upper limit in frequency for Q-estimation

See note for the Lower limit in frequency.
Maximum DB-down value when signal power considered nill

This DB value is used to edit the power spectrum, so that spurious small peaks do not affect Q
determination. 15 DB seems to be a reasonable value for this purpose.
vertical width in CGM plot

horizontal width in CGM plot
RMS velocity matrix for the CMP bins
Matrix Type: RMSVEL
957
QFILTER
Module Description
Input Channels
Output Channels
Parameters
Module Description
QFILTER corrects the amplitude and phase of seismic data for energy decay caused by inelastic
attenuation and dispersion. The Q values can be input as cumulative effective Q or can be estimated from
interval Q or interval velocities.
A commonly observed phenomenon in seismic data is that the dominant frequency decreases with time
and space. This inelastic attenuation causes an exponential decay of energy with propagation distance. The
net result is high frequency attenuation and dispersion causing the seismic waveform to distort.
Statistical deconvolution such as spiking, predictive, and maximum entropy deconvolution perform best
when applied to stationary data. However, inelastic attenuation and dispersion cause the seismic data to be
non-stationary. A common practice has been to use multi-time gate deconvolution to correct for this loss
of high frequencies. The problem with this method is the deconvolution filters must be derived from
smaller windows so that the statistical assumptions are not meet. QFILTER will apply a smoothly varying
inverse filter to compensate for the amplitude and phase distortions caused by attenuation. After Q
compensation, the wavelet will closely meet the assumption of stationary allowing a single gate
deconvolution to be performed.
A typical Q value is 100. Normally, Q increases with increasing time. Lower Q values can sometimes be
seen in shallow unconsolidated rocks. Q can sometimes be estimated by the interval velocity in a area:
Velocity (ft/s)
6000
10000
15000
Q
60
100
150
Q values must be input by the user as a starting model for the filter design. The Q values can vary in both
time and space. The Q values can be input as effective cumulative Q, interval Q, or by interval velocity.
The module will interpolate the Q values for each line and bin in the survey using the input matrix. The
effective Q is estimated from the interval Q as:
Qeff = T / Sum( 1/Qint )
As a convenience, the user can use an interval velocity matrix to estimate the effective Q. The module will
estimate Q from the interval velocity as follows:
958
Qint = Interval Velocity / 100
Typically, the user will estimate an RMS velocity in both time and space for the survey. Another method
is to use the stacking velocities derived from NMO to input as the velocities used to estimate Q. The
module will accept a connection to a VIP file. The VIP file velocities must be interval velocity. Whereas,
an input matrix should be RMS velocities. The module will compute interval velocity from the RMS
velocities in the matrix.
The inverse Q filter can be adversely affected by noise in the data. This module has a maximum gain value
that can be changed so that noise does not affect the result as badly. Noisy data may require that a lower
value be entered in this parameter.
The module will allow the user to apply the inverse Q filter over a time window. The author does not
recommend this though. The module needs to look at the whole trace in time to properly correct for
inelastic attenuation. The user can also add time to the start and stop times. This is useful when the
window needs to track the water bottom.
References
Hale, D., An Inverse-Q Filter, Stanford Exploration Project, SEP-26.
Hargreaves, N.D., 1992, Similarity and the inverse Q filter: Some simple algorithms for inverse Q
filtering, Geophysics, Vol. 57, No. 7, p 944-947.
Hargreaves, N.D., Calvert, A.J., 1991, Inverse Q filtering by Fourier transform, Geophysics, Vol. 56, No.
4, p 519-527.
Input Channels
Output Channels
Parameters
Method of Q input
The module needs a model of Q in both space and time. The user has the option to compute Q based upon
the effective cumulative Q, interval Q, or interval velocity. The interval velocity is very handy because
typically, the user has a better idea of velocity in the area than knowledge of Q. Another convenience is
that the stacking velocities can be used here.
959
Options: Effective Q, Interval Q, Interval Velocity
Q functions
If effective Q or interval Q was selected above then this parameter appears. You must specify a matrix of
time-Q pairs. You can specify these function pairs based upon a line number and bin number for spatial
distribution of Q. If you have chosen, effective Q, then effective Q values must be entered into the table. If
you have chosen, interval Q, then interval Q values must be entered into the table.
Matrix Type: QVALUES
RMS velocities
If interval velocity was selected above then this parameter appears. You can enter a matrix of time-RMS
velocity pairs. The module will convert the RMS velocity matrix to interval velocity. Another option is to
connect a VIP velocity file to this module. Be aware that if you are connecting a VIP file, then these
velocities must be interval velocities.
Matrix Type: RMSVEL
Maximum gain to apply (dB)

The inverse Q filtering method can be adversely affected by noise. This parameter allows you to specify
the maximum gain that can be applied to the filtering process. Noisy data may require a smaller gain
value.
Start time (ms.)

Specify the starting time in milliseconds to perform inverse Q filtering.
End time (ms.)

Specify the ending time in milliseconds to perform inverse Q filtering.

Select the header word to use as an additional starting time for inverse Q filtering. This can be trace header
words TIM1 or TIM2. These header words typically will contain horizon times, like water bottom times.

Select the header word to use as an additional ending time for inverse Q filtering. This can be trace header
words TIM1 or TIM2. These header words typically will contain horizon times, like water bottom times.
960
961
RADON
Module Description
Input Channels
Output Channels
Parameters
Module Description
The generalized Radon transform can be used for random noise suppression and/or long-period multiple
suppression. RADON will transform shot or CMP gathers using parabolic, hyperbolic, or linear
integration surfaces. RADON accepts time-space variant mute functions in the RADON transform domain
to handle varying residual moveout. RADON can internally merge more than one ensemble together and
perform the transform to reduce the effect of noise. RADON can add back a percentage of the random
noise, which is outside the transform domain, back into the output so the input characteristics can be
preserved.
After normal moveout (NMO) correction, a shot or CMP gather can be thought of as being composed of
many different parabolic or hyperbolic events. Each curve can be described by the zero-offset time and the
residual moveout time at a certain offset (usually the far offset). RADON first decomposes an ensemble
into its many parabolic or hyperbolic components in the RADON-transformed domain. In principle, each
parabolic or hyperbolic event corresponds to a point in the RADON-transformed domain. To suppress
some of the events, RADON mutes out part of the transformed domain according to the user specification.
Finally, RADON inverts the muted transform back into the time-versus-offset domain, i.e. the original
ensemble.
RADON can suppress random noise because in the forward transformation process, it only searches for
curved events in a best least-squared-error-fit sense. Random noise does not line up, therefore it is
suppressed when transformed back to the ensemble.
RADON will not filter the ensemble if there are less than 3 live traces in the ensemble. This may occur if
the maximum number of traces in SEGYREAD or READ is less than the actual number of traces per
ensemble, i.e. the ensemble is split.
The residual moveout times can be defined as follows:
962
REFERENCE
Beylkin, G,.1987, The discrete Radon transform: IEEE Transactions of Acoustics, Speech, and Signal
Processing, 35, 162-712.
Chapman, C.H.,1981, Generalized Radon transforms and slant stacks: Geophysical Journal of the Royal
Astronomical Society, 66, 445-453.
Foster, D. J. and Mosher, C. C., 1992, Suppression of multiples using the Radon transform: Geophysics,
57, No. 3, 386-395.
Hampson, D., 1986, Inverse velocity stacking for multiple elimination: J. Can. Soc. Expl. Geophs., 22,
44-55.
Hampson, D., 1987, The discrete Radon transform: a new tool for image enhancement and noise
suppression: SEG Expanded Abstracts 1978, 141-143.
963
Input Channels
Output Channels
Parameters
Transform type
Options: Parabolic:, Hyperbolic, Linear

The reference depth is used for the hyperbolic transform (Foster/Mosher 1992) as follows:
Where Xk is the offset receiver position and Zref is the reference depth.
Far offset (m or ft)

This is used to determine the P values and to compute the aliasing boundary. An estimation, if not known
exactly, is acceptable.
Time-space variant radon mute?

Negative end time (ms)
This is the largest negative time for the noise zone.
Negative start time (ms)

This is the largest negative time for the data zone.
964
Positive start time (ms)

This is the largest positive time for the data zone.
Positive end time (ms)

This is the largest positive time for the noise zone.
Negative taper length (ms)

Positive taper length (ms)
Moveout increment (ms)
This is the P moveout increment on the reference offset. The number of P values in the T-P transform is
proportional to the range of minimum to maximum moveout divided by the moveout increment.
Header to shift mute by

Select TIM1 or TIM2 to shift the tau-p mute time by the contents of one of these trace header values. For
marine surveys, this option can be useful in allowing a mute to follow the water bottom multiple. The
trace headers TIM1 or TIM2 can be set with the HORIZON module. This parameter is only available if a
time-space variant radon mute is to be applied.
Radon mute matrix

This is a two dimensional spreadsheet in which your mute functions can be prescribed. The corresponding
dimension header keys have to be specified.
Matrix Type: RADON
Primary header key for above matrix

TLSN
Secondary header key for above matrix

TLSN
965
Frequency transform pad percent

Low frequency (Hz)
The frequency transform will be zero for any frequency below this value.s
High frequency (Hz)

The frequency transform will be zero for any frequency above this value.s

Several ensembles can be used in the transformation. If events are almost flat, the effect of random noise
and low fold can be reduced by using more than one ensemble. This parameter has to be used with
CAUTION. If there is significant dip, merging several ensembles may make the data aliased on the super
gather so RADON may function worse than if just one ensemble is used. For relatively high fold data,
using more ensembles may not be worth the time. Using more than one ensemble will substantially
increase the computing time because of the increased fold, and because RADON only outputs the center
ensemble for each transformation.
White noise (percentage * 100)

White noise is added to ensure that the computation is stable. It is entered as 100 times the percentage with
a default of 500. This value depends on the signal/noise ratio of the data. However, most of the time, the
default of 500 should be sufficient.
Input data
Specify Radon transform to input data from a previous RADON run and apply an inverse Radon
transform. Any radon space mute will be applied prior to the inverse transform. Because the original data
is not available, you will not be able to subtract the noise from the original nor add non-modeled noise into
the output. However you can use the module SUBSEGY to subtract the original data from modeled noise.
In this case because the forward transform drops dead traces, make sure you select only live traces using
the SELECT module prior to the SUBSEGY module.
Options: Seismic gather, Radon transform
To model
Options: Noise: Model the multiples, i.e. mute, Signal: Mute the
multiples in the transform
If the parameter Input data is Radon transform, the original data is not available for the subtraction so
only the modeled noise will be output. See the parameter description for Input data for description on how
to perform the subtraction.
966
Non-modeled noise addition option

If the parameter To model is Signal, two options are available to add back the non-model noise with the
modeled signal data to reduce the wormy appearance. The non-model noise is defined as the original data
less the modeled noise and signal. Usually the non-modeled noise is the data outside the modeled P data
and random noise.
The option Stackback is modeled signal added with a percentage of the non-modeled noise. The option
Threshold is a scaled down non-modeled noise section dependent upon the modeled signal added with the
modeled signal.
Options: Stackback, Threshold
Non-modeled noise stackback(%)

This is the percentage of the non-modeled noise that is added to the modeled signal data. A value of zero
will result in a wormy looking section that contains only the modeled signal data. While a value of 100%
will result in a section that is the same as a To model option of Noise (original-modeled_noise). This
option is only available if the parameter Non-modeled noise addition option is Stackback.
Non-modeled noise threshold(%)

This parameter specifies the maximum non-modeled noise threshold expressed as a percentage of the
modeled signal. Any non-modeled noise that exceeds this threshold will scaled down to this level prior to
adding with the modeled signal. This parameter is only available if the parameter Non-modeled noise
addition option is Threshold.
Window size for threshold calculation(points)

When the parameter Non-modeled noise addition option is Threshold, this is the running window size
expressed in points. The running window is applied to extract the envelope of the non-modeled noise and
the modeled signal.
To output
If the Radon transform is output, you will be able to apply some process such as DECON to the data and
then perform an inverse RADON transform by selecting Radon transform from the parameter Input data.
In this case all dead traces will be dropped but some dead traces with an offset of 999999 may appear to
save the trace header for the inverse Radon transform.
Options: Seismic gather : Output the inv, Radon transform: Output
the Radon transform, Q.C. panel: Output the input gather, output the
transformed data, output the noise
967
Apply mute to transform?

If Radon Transform was selected for To Output (above), answer Yes to apply the mute to the transform
before output.
Maximum number of traces per output ensemble

Enter the maximum number of traces per ensemble after an inverse Radon transform is applied. If shot
ordered data was entered prior to the forward Radon transform then this parameter is the number of
channels per shot.

Enter a value greater than one to spread the calculation over several threads.
t-p mute zone scalar(%)

This option will allow you to specify the scalar that is applied to the modeled noise if it is desired to only
attenuate the noise rather than completely remove it. This parameter is only available if the parameter To
model is Signal.
968
RADON1
Module Description
Input Channels
Output Channels
Parameters
Module Description
The generalized Radon transform can be used for random noise , linear noise, and long-period multiple
suppression. RADON1 will forward and inverse transform shot or CMP gathers using parabolic,
hyperbolic, or linear integration surfaces. RADON1 accepts constant and time-space variant mute
functions to accept or reject selected regions in RADON transform space. Linear noise is usually
suppressed on raw shot records using the linear transform with the P-filter mute matrix. Multiples are
removed using either the standard mute or P-filter mute on raw shot or NMO corrected CMP ensembles.
RADON can internally merge more than one ensemble together and perform the transform to reduce the
effect of noise. RADON can add back a percentage of the random noise, which is outside the transform
domain, back into the output so the input characteristics can be preserved.
THEORY
RADON programs compute samples in a domain called Tau-P by summing samples along prescribed
curves in the T-X (trace ensemble) domain. In Tau-P, the Tau vertical time axis directly corresponds to the
T vertical time axis and P traces are computed for a range of p values using a prescribed curve. Examples
curves include Tau + pX for linear curves, Tau + pX** 2 for the parabolic curves, and SQRT( Tau**2 +
pX**2 ) for hyperbolic curves. To compute a linear Tau-P contribution for a given Tau (time) and trace at
P, sum the sample on T-X trace 1 at time Tau+PX 1 , with the sample on T-X trace 2 at Tau+PX 2 , and
continue till T-X trace n with the sample at time Tau+PX n . A continuous event on a T-X trace ensemble
that follows a selected prescribed curve (for some Tau and P) will generate a large contribution on the
trace assigned to P at time Tau in RADON space. In general, Tau will take the same time range as T and P
will range from large negative values to large positive values. Allowing P to be negative means events that
curve up (toward low time) will be included in the transformed domain.
The paragraph above describes a form of forward RADON transform. The T-X domain can be
approximately reconstructed by essentially the reverse process. The inverse transform to recover samples
in T (time) and X (offset) sums samples on P traces, but with the sign in front of the P term reversed.
Again using the linear example, a sample at time T on a trace with offset X will be computed by summing
the sample on radon trace P 1 at time T - P 1 X with the sample from radon trace P 2 at time T - P 2 X, and
continuing till radon trace P m , with the sample at time T - P m X. The fidelity of the reconstructed T-X
domain (compared to the original) depends upon the P increment used in the forward transform. In theory,
the transform is an integral, implying continuous sampling in P will produce an exact T-X inverse. In
practice, P is discreetized, so the inverse is not exact. Also the time derivative of the Hilbert transform
(Rho filter) must be applied to each trace of the inverse transform to recover the original frequency
content. This is due to the forward and inverse transforms being double summing (integration) processes.
969
If the contribution of unwanted T-X events like linear noise or multiples can be isolated in Tau-P, by
zeroing (muting) these contributions and after inverse back to T-X, the events will be removed. This
procedure is used to remove unwanted linear noise and multiple events.
The inverse RADON transform may be cast as a set of linear equations whose solution yield the Tau-P
domain.
Another approach is to first take the Fourier transform of the traces (F-X) and then cast the inverse
transform as a set of linear equations. This series of RADON programs, RADON, RADON1, and
RADONC (cluster version) all use this approach due to the efficiency of solving for the transform in the
frequency domain.
PRACTICE
RADON programs compute samples in a domain called Tau-P by summing samples in the T-X (trace)
domain along prescribed curves. Examples curves include Tau + pX for linear curves, Tau + pX** 2 for
the parabolic curves, and SQRT( Tau**2 + pX**2 ) for hyperbolic curves. The method used to define the
P values where traces are output uses the time DIFFERENCE spanned by end condition curves in both
negative (curve up) and positive (curve down) directions. The program computes P traces so that radon
output starts where Tau + F(Pneg)*Xmax is equal to Negative end time (ms), is increment by Moveout
increment (ms), and stops where Tau + F(Ppos)*Xmax is equal to Positive end time (ms). P values are
computed internally to make this work. The number of P traces will be (Positive end time - Negative end
time) / Moveout increment. Events with curvature outside this selected range will not be represented in the
RADON transform. The end times are illustrated in the diagram below.
Mutes may be defined in 3 ways - 1) constant mute, 2) standard time-space variant mute, 3) P-filter
time-space variant mute.
1. The constant mute assumes the input trace ensemble has been manipulated (had LMO or NMO
applied) such that signal events are near flat (P=0). The P traces are muted from Negative time start
to Negative time end, and, from Positive time start to Positive time end (for ALL Tau) as illustrated
in the diagram below. The start times may be adjusted to retain any part or all the transform.
2. The standard mute matrix is less restrictive in that it can vary spatially and describe a more general
Tau-P region. However, the Tau-P mute region must include an edge of RADON domain. The format
is the same as for the constant mute.
3. The P-filter matrix is the most flexible of the mute definitions. For any Tau, the user specifies 4 time
(P trace) values. The mute value is 0. from Negative end time to p1, ramps up from p1 to p2, is flat
1.0 from p2 to p3, and ramps down to 0. at p4, and remains 0. to the Positive end time. This way an
arbitrary P band pass may be specified. This allows linear noise removal without the need for any
LMO or NMO prior to RADON. This also allows the user to define specific polygons in RADON
domain without having to include the edges. Examples are given on the parameter discussion for
P-filter matrix below.
Undesired events may be removed by 2 methods - 1) model signal, and 2) model noise. Once the End
times, Moveout increment and Mute parameters are selected, the user may select the noise removal
method. 1)By modeling signal, the mute will be applied to the RADON domain and the result inverse
transformed and output. 2)By modeling noise, the inverse of the mute will applied to the RADON domain,
970
the result inverse transformed and subtracted from the original T-X domain traces for output. Some
datasets show cleaner results modeling noise.
Linear events will make large contributions to the RADON domain around the P trace whose time is equal
to the time length of the linear noise measured from near to far offsets, and, at Tau equal to the time origin
of the noise on the near offset.
Multiple events typically exhibit higher P concentrations than primaries in the RADON domain after
parabolic or hyperbolic transform.
The white noise value should be as low as possible.
Do not filter transforms unless absolutely necessary.
USAGE
Initial
The menu defaults allow the parabolic forward and inverse of a small shot or CMP ensemble. Before
attempting to radon filter linear noise or multiples, test the Negative end time, Positive end time and
Moveout increment to ensure that just a forward followed by and inverse transform gives acceptable
fidelity of output to the original input ensemble. This is done by selecting NO for Time-space variant
radon mute, set the Negative start time to the Negative end time and Positive start time to Positive end
time, Positive and Negative taper lengths to 0., To output to Seismic, To model to signal, and Stackback
option with % stackback or threshold to 0. Try to select the minimum end times and largest moveout
increment that will yield good results. This is critical!
Linear noise removal
To remove linear noise, first observe the noise origin time and measure the time where the noise hits the
far offset traces. This far offset time difference will be the middle of the P range where the noise events
should concentrate in RADON space. Find the noise in the transform space by selecting linear "Transform
type", "To output" as Radon transform, and select NO for Apply mute to transform? The linear noise
should now be concentrated in a "region" of transform space vertically positioned at or near the noise train
origin time, and horizontally positioned at the far offset time difference P trace(s). Next, enter
time-p1,p2,p3,p4 rows in the P-filter matrix to describe the zone to be removed. Examples of entries are
described below in the P-filter matrix description. Once this matrix is complete, select YES for
Time-variant radon mute, YES for P-filter matrix, set Mode to reject, YES for apply mute to transform,
and view the output radon transform to see if the matrix entries were correct. Adjust the entries in the
P-filter matrix until ready for a test. Run again with "To model" set to signal, "To output" set to Seismic
traces to view the linear noise rejection on the data. To avoid confusion associated with the accept/reject
functionality, ALWAYS run a test and look at the output to be sure the result looks correct, i.e., the
desired events are being affected. If the linear noise is so steep that it never intersects the far traces, just a
forward and inverse linear transform, modeling signal, usually will attenuate the noise.
971
Multiple removal
residual moveout time at a certain offset (usually the far offset). The NMO velocity needed for RADON to
be an effective multiple rejector should correct the primaries to flat (or over-correct so the primaries lie in
the negative region of RADON (P) space) leaving the multiples with residual NMO, remaining in positive
P space. To suppress the multiple events, mute the region of positive Tau-P space where the multiple
contributions concentrate.
RADON1 first decomposes an ensemble into its many parabolic or hyperbolic components in the
RADON-transformed domain. In principle, each parabolic or hyperbolic event corresponds to a point in
the RADON1-transformed domain. To suppress some of the events, RADON1 mutes out part of the
transformed domain according to the user specification. Finally, RADON1 inverts the muted transform
back into the time-versus-offset domain, i.e. the original ensemble.
RADON1 can suppress random noise because in the forward transformation process, it only searches for
NOTES:
When using the menu mute, standard matrix, or P-filter matrix to mute linear noise or multiples and,
modeling SIGNAL, cleanest results are obtained by muting ONLY the zones where the undesired event
contributions concentrate. Excessive muting in RADON space usually causes noisy results or produces
artifact events after RADON processing.
RADON1 will not filter the ensemble if there are less than 3 live traces in the ensemble. This may occur if
the maximum number of traces in SEGYREAD or READ is less than the actual number of traces per
Usage suggestions:
Before attempting to radon filter linear noise or multiples, test the Negative end time, Positive end time
and Moveout increment to ensure that just a forward followed by and inverse transform gives acceptable
option with % stackback or threshold to 0. Try to select the minimum start times and moveout increment
that will yield good results. This is critical!
To remove linear noise, first observe the noise origin time and measure the time the noise hits the far
offset traces. This far offset time will be the middle of the P range where the noise events should
concentrate in RADON space. If the linear noise is so steep that it never intersects the far traces, just a
forward and inverse linear transform, modeling signal, usually will attenuate the noise. Find the noise in
the transform space by selecting linear "Transform type", "To output" as Radon transform, and select NO
for Apply mute to transform? The linear noise should now be concentrated in a "region" of transform
space vertically positioned at or near the origin time and horizontally positioned at the far offset time.
972
Next, enter time-p1,p2,p3,p4 rows in the P-filter matrix to describe the zone to be removed. Examples of
entries are described below in the P-filter matrix description. Once this matrix is complete, select YES for
Time-variant radon mute, YES for P-filter matrix, set Mode to reject, YES for apply mute to transform,
and view the output radon transform to see if the matrix entries were correct. Adjust the entries in the
P-filter matrix until ready for a test. Run again with "To model" set to signal, "To output" set to Seismic
traces to view the linear noise rejection on the data. To avoid confusion associated with the accept/reject
functionality, ALWAYS run a test and look at the output to be sure the result looks correct, i.e., the
desired events are being affected.
The diagram below represents a T-X ensemble with near offset at left and far offset at right with the traces
undisplayed. The menu mute and standard mute matrix residual moveout times are defined as labeled on
the right. For the curves shown, the P-filter mute values would be p1 = Negative start time - upper taper,
p2 = Negative start time, p3 = Positive start time, p4 = Positive start time + lower taper. The standard mute
matrix residual moveout times can be defined as follows:
973
REFERENCE
57, No. 3, 386-395.
44-55.
Input Channels
Output Channels
Parameters
Transform type
Select Parabolic or Hyperbolic to remove curved events like multiples. Select Linear to remove near
surface linear noise trains like ground roll.
Options: Parabolic, Hyperbolic, Linear

Required if Transform type equal Hyperbolic. The reference depth is used for the hyperbolic transform
(Foster/Mosher 1992) as follows:
974
Where Xk is the offset receiver position and Zref is the reference depth. Primary events reflected from this
depth are optimally resolved in RADON space. This value should be adjusted by visually examining the
Tau-P output to concentrate the noise events (multiples) in as small of zone as possible to minimize the
muting area.


Select NO if the noise events to be removed has no time or space variance, otherwise select YES and enter
the time-space variant parameters in one of two optional matrices described below.
P-filter matrix?
If YES was selected for "Time-space variant radon mute?" above, select NO for "P-filter matrix?" if the
standard mute matrix (described below) is appropriate for removing the noise. Select YES for "P-filter
matrix" to remove linear noise or multiples where careful, zone specific muting is necessary to avoid the
artifacts caused by muting to the edge, as in the standard mute matrix.
This matrix format requires time-p band pass values for any row (time - p1 - p2 - p3 - p4). For example,
suppose the Negative end time is 3000 and the Positive end time is 3000, an entry of 1000, -500, -400,
1000, 1500 used in Accept mode defines a pass band at 1000ms with mute values of 0. (t-p mute zone
scalar) from p = -3000 to p = -500, tapering up to 1. at p = -400, flat to p = 1000, finally tapering to 0. at p
=1500 and remaining 0. until p = 3000. This entry used in reject mode would just be the inverse, ie, 1.
from -3000 to -500, etc. Entries like 1000,-1000, -900, -700, -600, and 2000, 100, 300, 600, 900 are
perfectly acceptable and allow the flexibility to accept/reject any region of RADON1 space. For total
rejection in accept mode, make all the p entries the same like, 1000, 0, 0, 0, 0 and for all pass in accept
mode use something like 1000,-3000,-3000,3000,3000.The standard matrix only allows band pass/reject
about P=0. This P-filter matrix allows linear noise rejection without having to apply any NMO to the
ensemble. It is probably less confusing to think of and define the pass band in an accept mode,
understanding the implications of using it in reject mode.
For example, suppose a DISPLAY of the RADON transform shows a zone due to linear noise from Tau =
500 to Tau = 750 ms and on P traces 700 to 1000 ms at the top to traces 800 to 1000 ms at the bottom. The
first line in the P-filter matrix would be 496, 0, 0, 0, 0 to mute the whole transform above 500 ms. This
example assumes the sample rate to be 4 ms. The second line would be 500, 650, 700, 1000, 1100. This
describes a pass starting at P = 650 ms, ramping up to 700 ms, flat to 1000 ms, and ramping down to 1100
ms. The ramp length is 100 ms. If the zone-to-be-muted has straight sides we can define the third line as
750, 750, 800, 1000, 1100. A final entry line is needed to turn off the mute, 754, 0, 0, 0, 0. If the user sets
"To output" to Radon transform with "Apply mute to transform?" set to YES, and "Mode" set to Reject,
the muted zone will can be seen in DISPLAY if following RADON in the flow. To remove the linear
noise train, the user may use "To output" as Seismic gather, "To model" as Noise and "Mode" as Reject. If
the choice for "To model" was Noise, then "Mode" should be Accept. Multiple mute zones may be defined
on a spread sheet with each mute deeper in Tau than the one above.
975

This value defines the beginning curve of the RADON transform (Pmin - negative - curves up). Events
with time extent curvature above this value will not be represented in RADON space and, therefore, will
not be present after inverse transform.

This value is needed if "Time-space variant radon mute?" is NO. This is the largest negative time for the
data zone. The mute value is 0. between this value minus the "Negative taper length" and the "Negative
end time". See diagram above. To remove any negative time mute, set this value equal to the "Negative
end time".

This value is needed if "Time-space variant radon mute?" is NO. This is the largest positive time for the
data zone. The mute value is 0. between this value plus the "Positive taper length" and "Positive end time".

This value defines the ending curve of the RADON transform (Pmax- positive - curves down). Events
with time extent curvature below this value will not be represented in RADON space and, therefore, will
not be present after.

Needed when the mute is not Time-Space variant. The mute value ramps from 1.0 at "Negative start time"
to 0. over this time length. See diagram above. A typical value would be 50.0 when "Negative end time" is
not equal to "Negative start time".

Needed when the mute is not Time-Space variant. The mute value ramps from 1.0 at "Positive start time"
to 0. over this time length. See diagram above. A typical value would be 50.0 when "Positive end time" is
not equal to "Positive start time".

This is the P moveout increment on the reference offset. The number of P values in the Tau-P transform is
proportional to the range of minimum to maximum moveout divided by the moveout increment. The
smaller this value, the higher the fidelity in the forward and inverse transform. If too large, the result of
just forward and inverse transform may contain artifacts and random noise.
976

Radon mute matrix

Required if Time-space variant radon mute? is YES and P-filter matrix? is NO. This is a two dimensional
spreadsheet in which your mute functions can be prescribed. The matrix values must be in standard mute
matrix format (tau,negative start time,taper,positive start time,taper). The corresponding dimension header
keys have to be specified.
Matrix Type: RADON
P-filter mute matrix

Required if Time-space variant radon mute? is YES and P-filter matrix? is YES. If you specified YES to
"P-filter matrix?", the matrix row values must be in P-filter format (t,p1,p2,p3,p4). See discussion of
matrix values in "P-filter matrix?" above. The corresponding dimension header keys have to be specified.
Matrix Type: RADON1

If either the standard mute matrix or the P-filter mute matrix are used, the primary and secondary header
keys of these matrices must be specified.
TLSN

TLSN
977

This value specifies the pad length used in the Fourier transform to prevent event wraparound.
Low frequency (Hz)

The frequency transform will be zero for any frequency below this value.
Apply low frequency on forward transform

If Low frequency is greater than 0 Hz, YES will apply the low frequency filter just after forward
frequency transform. No will not apply the filter after forward frequency transform even if Low frequency
is above 0. This option is independent of Apply low frequency on inverse transform.
Apply low frequency on inverse transform

If Low frequency is greater than 0 Hz, YES will apply the low frequency filter just before inverse
frequency transform. No will not apply the filter before inverse frequency transform even if Low
frequency is above 0. This option is independent of Apply low frequency on forward transform.
High frequency (Hz)

The frequency transform will be zero for any frequency above this value.
Apply high frequency on forward transform

If High frequency is less than "Nyquist", YES will apply the high frequency filter just after forward
frequency transform. No will not apply the filter after forward frequency transform even if High frequency
is less than "Nyquist". This option is independent of Apply high frequency on inverse transform.
Apply high frequency on inverse transform

If High frequency is less than "Nyquist", YES will apply the high frequency filter just before inverse
frequency transform. No will not apply the filter before inverse frequency transform even if High
frequency is less than "Nyquist". This option is independent of Apply high frequency on forward
transform.

gather so RADON may function worse than if just one ensemble is used. For relatively high fold data,
increase the computing time because of the increased fold, and because RADON only outputs the center
978

Required if Input data is Seismic gather. White noise is added to ensure that the computation is stable. It
is entered as 100 times the percentage with a default of 100. This value depends on the signal/noise ratio
of the data. However, most of the time, the default of 500 should be sufficient. Very noisy data may
require a larger value.
Input data
Specify Radon transform to input data from a previous RADON run and apply an inverse Radon
To output
Required if Input data is Seismic gather. If the Radon transform is output, you will be able to apply some
process such as DECON to the data and then perform an inverse RADON transform by selecting Radon
transform from the parameter Input data. In this case all dead traces will be dropped but some dead traces
with an offset of 999999 may appear to save the trace header for the inverse Radon transform.

If Radon Transform was selected for To Output (above), answer YES to apply the mute to the transform
before output. This allow the user to see the part of RADON space that is affected.
Options: YES, NO

Needed when the "Input data" is Radon transform. Enter the maximum number of traces per ensemble
after an inverse Radon transform is applied. If shot ordered data was entered prior to the forward Radon
transform then this parameter is the number of channels per shot.
979
To model
MODE
RADON is in either accept or reject mode when using the P-filter matrix specification. Reject mode will
invert the matrix mute before application. If input is Seismic gather and Noise is modeled, use Accept to
have the noise described by the mute zone subtracted from the input data, If input is Radon transform and
Noise is modeled, use Reject to have the noise described by the mute zone subtracted from the input data.
Options: Accept, Reject

and random noise.
modeled signal.


980

the modeled signal.

Enter the maximum number of traces per ensemble after an inverse Radon transform is applied. If shot
ordered data was entered prior to the forward Radon transform then this parameter is the number of
channels per shot.

Enter a value greater than one to spread the calculation over several threads.

model is Signal.
981
RADONC
Module Description
Input Channels
Output Channels
Parameters
Module Description
The generalized Radon transform can be used for random noise, linear noise, and long-period multiple
suppression. RADONC will forward and inverse transform shot or CMP gathers using parabolic,
hyperbolic, or linear integration surfaces. RADONC accepts constant and time-space variant mute
functions to accept or reject selected regions in RADON transform space. Linear noise is usually
suppressed on raw shot records using the linear transform with the P-filter mute matrix. Multiples are
remove using either the standard mute or P-filter mute on raw shot or NMO corrected CMP ensembles.
RADONC can internally merge more than one ensemble together and perform the transform to reduce the
effect of noise. RADONC can add back a percentage of the random noise, which is outside the transform
domain, back into the output so the input characteristics can be preserved.
NOTE: RADONC has options for use on a single CPU platform, multi-CPU SMP platform, and a cluster.
When executing on a cluster, there is no Q. C. Output option, and, there can be only one RADONC using
the CLUSTER option in a flow. If more than one RADONC is attempted in a flow using the CLUSTER
option, the following error message will be issued: *** Cannot spawn more than one cluster session per
job ***. If two RADONCs are needed (the first for forward transform and the second for inverse), use the
CLUSTER option for the first and THREADS for the second.
THEORY
RADON programs compute samples in a domain called Tau-P by summing samples along prescribed
curves in the T-X (trace ensemble) domain. In Tau-P, the Tau vertical time axis directly corresponds to the
T vertical time axis and P traces are computed for a range of p values using a prescribed curve. Examples
curves include Tau + pX for linear curves, Tau + pX** 2 for the parabolic curves, and SQRT( Tau**2 +
pX**2 ) for hyperbolic curves. To compute a linear Tau-P contribution for a given Tau (time) and trace at
P, sum the sample on T-X trace 1 at time Tau+PX 1 , with the sample on T-X trace 2 at Tau+PX 2 , and
continue till T-X trace n with the sample at time Tau+PX n . A continuous event on a T-X trace ensemble
that follows a selected prescribed curve (for some Tau and P) will generate a large contribution on the
trace assigned to P at time Tau in RADON space. In general, Tau will take the same time range as T and P
will range from large negative values to large positive values. Allowing P to be negative means events that
curve up (toward low time) will be included in the transformed domain.
The paragraph above describes a form of forward RADON transform. The T-X domain can be
approximately reconstructed by essentially the reverse process. The inverse transform to recover samples
in T (time) and X (offset) sums samples on P traces, but with the sign in front of the P term reversed.
Again using the linear example, a sample at time T on a trace with offset X will be computed by summing
the sample on radon trace P 1 at time T - P 1 X with the sample from radon trace P 2 at time T - P 2 X, and
982
continuing till radon trace P m , with the sample at time T - P m X. The fidelity of the reconstructed T-X
domain (compared to the original) depends upon the P increment used in the forward transform. In theory,
the transform is an integral, implying continuous sampling in P will produce an exact T-X inverse. In
practice, P is discreetized, so the inverse is not exact. Also the time derivative of the Hilbert transform
(Rho filter) must be applied to each trace of the inverse transform to recover the original frequency
content. This is due to the forward and inverse transforms being double summing (integration) processes.
If the contribution of unwanted T-X events like linear noise or multiples can be isolated in Tau-P, by
zeroing (muting) these contributions and after inverse back to T-X, the events will be removed. This
procedure is used to remove unwanted linear noise and multiple events.
The inverse RADON transform may be cast as a set of linear equations whose solution yield the Tau-P
domain.
Another approach is to first take the Fourier transform of the traces (F-X) and then cast the inverse
transform as a set of linear equations. This series of RADON programs, RADON, RADON1, and
RADONC (cluster version) all use this approach due to the efficiency of solving for the transform in the
frequency domain.
PRACTICE
RADON programs compute samples in a domain called Tau-P by summing samples in the T-X (trace)
domain along prescribed curves. Examples curves include Tau + pX for linear curves, Tau + pX** 2 for
the parabolic curves, and SQRT( Tau**2 + pX**2 ) for hyperbolic curves. The method used to define the
P values where traces are output uses the time DIFFERENCE spanned by end condition curves in both
negative (curve up) and positive (curve down) directions. The program computes P traces so that radon
output starts where Tau + F(Pneg)*Xmax is equal to Negative end time (ms), is increment by Moveout
increment (ms), and stops where Tau + F(Ppos)*Xmax is equal to Positive end time (ms). P values are
computed internally to make this work. The number of P traces will be (Positive end time - Negative end
time) / Moveout increment. Events with curvature outside this selected range will not be represented in the
RADON transform. The end times are illustrated in the diagram below.
Mutes may be defined in 3 ways - 1) constant mute, 2) standard time-space variant mute, 3) P-filter
time-space variant mute.
1. The constant mute assumes the input trace ensemble has been manipulated (had LMO or NMO
applied) such that signal events are near flat (P=0). The P traces are muted from Negative time start
to Negative time end, and, from Positive time start to Positive time end (for ALL Tau) as illustrated
in the diagram below. The start times may be adjusted to retain any part or all the transform.
2. The standard mute matrix is less restrictive in that it can vary spatially and describe a more general
Tau-P region. However, the Tau-P mute region must include an edge of RADON domain. The format
is the same as for the constant mute.
3. The P-filter matrix is the most flexible of the mute definitions. For any Tau, the user specifies 4 time
(P trace) values. The mute value is 0. from Negative end time to p1, ramps up from p1 to p2, is flat
1.0 from p2 to p3, and ramps down to 0. at p4, and remains 0. to the Positive end time. This way an
arbitrary P band pass may be specified. This allows linear noise removal without the need for any
LMO or NMO prior to RADONC. This also allows the user to define specific polygons in RADON
983
domain without having to include the edges. Examples are given on the parameter discussion for
P-filter matrix below.
Undesired events may be removed by 2 methods - 1) model signal, and 2) model noise. Once the End
times, Moveout increment and Mute parameters are selected, the user may select the noise removal
method.
1. By modeling signal, the mute will be applied to the RADON domain and the result inverse
transformed and output.
2. By modeling noise, the inverse of the mute will applied to the RADON domain, the result inverse
transformed and subtracted from the original T-X domain traces for output. Some datasets show
cleaner results modeling noise.
Linear events will make large contributions to the RADON domain around the P trace whose time is equal
to the time length of the linear noise measured from near to far offsets, and, at Tau equal to the time origin
of the noise on the near offset.
Multiple events typically exhibit higher P concentrations than primaries in the RADON domain after
parabolic or hyperbolic transform.
The white noise value should be as low as possible.
Do not filter transforms unless absolutely necessary.
USAGE
Initial
The menu defaults allow the parabolic forward and inverse of a small shot or CMP ensemble. Before
attempting to radon filter linear noise or multiples, test the Negative end time, Positive end time and
Moveout increment to ensure that just a forward followed by and inverse transform gives acceptable
option with % stackback or threshold to 0. Try to select the minimum end times and largest moveout
increment that will yield good results. This is critical!
Linear noise removal
To remove linear noise, first observe the noise origin time and measure the time where the noise hits the
far offset traces. This far offset time difference will be the middle of the P range where the noise events
should concentrate in RADON space. Find the noise in the transform space by selecting linear "Transform
type", "To output" as Radon transform, and select NO for Apply mute to transform? The linear noise
should now be concentrated in a "region" of transform space vertically positioned at or near the noise train
origin time, and horizontally positioned at the far offset time difference P trace(s). Next, enter time-p1, p2,
p3, p4 rows in the P-filter matrix to describe the zone to be removed. Examples of entries are described
below in the P-filter matrix description. Once this matrix is complete, select YES for Time-variant radon
mute, YES for P-filter matrix, set Mode to reject, YES for apply mute to transform, and view the output
984
radon transform to see if the matrix entries were correct. Adjust the entries in the P-filter matrix until
ready for a test. Run again with "To model" set to signal, "To output" set to Seismic traces to view the
linear noise rejection on the data. To avoid confusion associated with the accept/reject functionality,
ALWAYS run a test and look at the output to be sure the result looks correct, i.e., the desired events are
being affected. If the linear noise is so steep that it never intersects the far traces, just a forward and
inverse linear transform, modeling signal, usually will attenuate the noise.
Multiple removal
residual moveout time at a certain offset (usually the far offset). The NMO velocity needed for RADONC
to be an effective multiple rejector should correct the primaries to flat (or over-correct so the primaries lie
in the negative region of RADON space) leaving the multiples with residual NMO, remaining in positive
P space. To suppress the multiple events, mute the region of positive Tau-P space where the multiple
contributions concentrate.
Random noise
RADONC can suppress random noise because in the forward transformation process, it only searches for
NOTES:
When using the menu mute, standard matrix, or P-filter matrix to mute linear noise or multiples and,
modeling SIGNAL, cleanest results are obtained by muting ONLY the zones where the undesired event
contributions concentrate. Excessive muting in RADON space usually causes noisy results or produces
artifact events after RADON processing.
RADONC will not filter the ensemble if there are less than 3 live traces in the ensemble. This may occur
if the maximum number of traces in SEGYREAD or READ is less than the actual number of traces per
The diagram below represents a T-X ensemble with near offset at left and far offset at right with the traces
undisplayed. The menu mute and standard mute matrix residual moveout times are defined as labeled on
the right. For the curves shown, the P-filter mute values would be p1 = Negative start time - upper taper,
p2 = Negative start time, p3 = Positive start time, p4 = Positive start time + lower taper.
985
REFERENCE
57, No. 3, 386-395.
44-55.
986
Input Channels
Output Channels
Parameters
Transform type
Select Parabolic or Hyperbolic to remove curved events like multiples. Select Linear to remove near
surface linear noise trains like ground roll.
Options: Parabolic:, Hyperbolic, Linear

The reference depth is used for the hyperbolic transform (Foster/Mosher 1992) as follows:
Where Xk is the offset receiver position and Zref is the reference depth. Primary events reflected from this
depth are optimally resolved in RADON space. This value should be adjusted by visually examining the
Tau-P output to concentrate the noise events (multiples) in as small of zone as possible to minimize the
muting area.


Select NO if the noise events to be removed has no time or space variance, otherwise select YES and enter
the time-space variant parameters in one of two optional matrices described below.
987
P-filter matrix?
If YES was selected for "Time-space variant radon mute?" above, select NO for "P-filter matrix?" if the
standard mute matrix (described below) is appropriate for removing the noise. Select YES for "P-filter
matrix" to remove linear noise or multiples where careful, zone specific muting is necessary to avoid the
artifacts caused by muting to the edge, as in the standard mute matrix.
This matrix format requires time-p band pass values for any row (time - p1 - p2 - p3 - p4). For example,
suppose the Negative end time is 3000 and the Positive end time is 3000, an entry of 1000, -500, -400,
1000, 1500 used in Accept mode defines a pass band at 1000ms with mute values of 0. from p = -3000 to
p = -500, tapering up to 1. at p = -400, flat to p = 1000, finally tapering to 0. at p =1500 and remaining 0.
until p = 3000. This entry used in reject mode would just be the inverse, i.e, 1. from -3000 to -500, etc.
Entries like 1000,-1000, -900, -700, -600, and 2000, 100, 300, 600, 900 are perfectly acceptable and allow
the flexibility to accept/reject any region of RADON space. For total rejection in accept mode, make all
the p entries the same like, 1000, 0, 0, 0, 0 and for all pass in accept mode use something like
1000,-3000,-3000,3000,3000.The standard matrix only allows band pass/reject about P=0. This P-filter
matrix allows linear noise rejection without having to apply any NMO to the ensemble. It is probably less
confusing to think of and define the pass band in an accept mode, understanding the implications of using
it in reject mode.
For example, suppose a DISPLAY of the RADON transform shows a zone due to linear noise from Tau =
500 to Tau = 750 ms and on P traces 700 to 1000 ms at the top to traces 800 to 1000 ms at the bottom. The
first line in the P-filter matrix would be 496, 0, 0, 0, 0 to mute the whole transform above 500 ms. This
example assumes the sample rate to be 4 ms. The second line would be 500, 650, 700, 1000, 1100. This
describes a pass starting at P = 650 ms, ramping up to 700 ms, flat to 1000 ms, and ramping down to 1100
ms. The ramp length is 100 ms. If the zone-to-be-muted has straight sides we can define the third line as
750, 750, 800, 1000, 1100. A final entry line is needed to turn off the mute, 754, 0, 0, 0, 0. If the user sets
"To output" to Radon transform with "Apply mute to transform?" set to YES, and "Mode" set to Reject,
the muted zone will can be seen in DISPLAY if following RADON in the flow. To remove the linear
noise train, the user may use "To output" as Seismic gather, "To model" as Noise and "Mode" as Reject. If
the choice for "To model" was Noise, then "Mode" should be Accept. Multiple mute zones may be defined
on a spread sheet with each mute deeper in Tau than the one above.

This value defines the beginning curve of the RADON transform (Pmin - negative - curves up). Events
with time extent curvature above this value will not be represented in RADON space and, therefore, will
not be present after inverse transform.

This value is needed if "Time-space variant radon mute?" is NO. This is the largest negative time for the
data zone. The mute value is 0. between this value minus the "Negative taper length" and the "Negative
end time". See diagram above. To remove any negative time mute, set this value equal to the "Negative
end time".
988

This value is needed if "Time-space variant radon mute?" is NO. This is the largest positive time for the
data zone. The mute value is 0. between this value plus the "Positive taper length" and "Positive end time".

This value defines the ending curve of the RADON transform (Pmax- positive - curves down). Events
with time extent curvature below this value will not be represented in RADON space and, therefore, will
not be present after inverse transform. This is the largest positive time for the noise zone.

Needed when the mute is not Time-Space variant. The mute value ramps from 1.0 at "Negative start time"
to 0. over this time length. See diagram above. A typical value would be 50.0 when "Negative end time" is
not equal to "Negative start time".

Needed when the mute is not Time-Space variant. The mute value ramps from 1.0 at "Positive start time"
to 0. over this time length. See diagram above. A typical value would be 50.0 when "Positive end time" is
not equal to "Positive start time".

This is the P moveout increment on the reference offset. The number of P values in the Tau-P transform is
proportional to the range of minimum to maximum moveout divided by the moveout increment. The
smaller this value, the higher the fidelity in the forward and inverse transform. If too large, the result of
just forward and inverse transform may contain artifacts and random noise.

Radon mute matrix

This is a two dimensional spreadsheet in which your mute functions can be prescribed. The matrix values
must be in standard mute matrix format (tau, negative start time, taper, positive start time, taper). The
corresponding dimension header keys have to be specified.
989
Matrix Type: RADON
Radon mute matrix (new)

If you specified YES to "P-filter matrix?", the matrix row values must be in P-filter format (t, p1, p2, p3,
p4). See discussion of matrix values in "P-filter matrix?" above. The corresponding dimension header keys
have to be specified.
Matrix Type: RADON1

TLSN

TLSN

This value specifies the pad length used in the Fourier transform to prevent event wraparound.
Low frequency (Hz)

The frequency transform will be zero for any frequency below this value.
Apply low frequency on forward transform

If Low frequency is greater than 0 Hz, YES will apply the low frequency filter just after forward
frequency transform. No will not apply the filter after forward frequency transform even if Low frequency
is above 0. This option is independent of Apply low frequency on inverse transform.
990
Apply low frequency on inverse transform

If Low frequency is greater than 0 Hz, YES will apply the low frequency filter just before inverse
frequency transform. No will not apply the filter before inverse frequency transform even if Low
frequency is above 0. This option is independent of Apply low frequency on forward transform.
High frequency (Hz)

The frequency transform will be zero for any frequency above this value.
Apply high frequency on forward transform

If High frequency is less than "Nyquist", YES will apply the high frequency filter just after forward
frequency transform. No will not apply the filter after forward frequency transform even if High frequency
is less than "Nyquist". This option is independent of Apply high frequency on inverse transform.
Apply high frequency on inverse transform

If High frequency is less than "Nyquist", YES will apply the high frequency filter just before inverse
frequency transform. No will not apply the filter before inverse frequency transform even if High
frequency is less than "Nyquist". This option is independent of Apply high frequency on forward
transform.

gather so RADONC may function worse than if just one ensemble is used. For relatively high fold data,
increase the computing time because of the increased fold, and because RADONC only outputs the center

White noise is added to ensure that the computation is stable. It is entered as 100 times the percentage with
a default of 100. This value depends on the signal/noise ratio of the data. However, most of the time, the
default of 100 should be sufficient. Very noisy data may require a larger value.
Input data
Specify Radon transform to input data from a previous RADONC run and apply an inverse Radon
991

To output
If the Radon transform is output, you will be able to apply some process such as DECON to the data and
then perform an inverse RADON transform by selecting Radon transform from the parameter Input data.
In this case all dead traces will be dropped but some dead traces with an offset of 999999 may appear to
save the trace header for the inverse Radon transform.

If Radon Transform was selected for To Output (above), answer YES to apply the mute to the transform
before output. This allow the user to see the part of RADON space that is affected.
Options: YES, NO

Needed when the "Input data" is Radon transform. Enter the maximum number of traces per ensemble
after an inverse Radon transform is applied. If shot ordered data was entered prior to the forward Radon
transform then this parameter is the number of channels per shot.
To model
Mode
RADONC is in either accept or reject mode when using the P-filter matrix specification. Reject mode will
invert the matrix mute before application. If input is Seismic gather and Noise is modeled, use Accept to
have the noise described by the mute zone subtracted from the input data, If input is Radon transform and
Noise is modeled, use Reject to have the noise described by the mute zone subtracted from the input data.
Options: Accept, Reject
992

and random noise.
modeled signal.



the modeled signal.

model is Signal.
Parallel execution mode

RADONC operates in three possible modes: 1) Threads for execution on SMP multi-processor machines,
2) Cluster for multi-node cluster machines, and 3) None for execution on single CPU machines.
993
NOTE: If two RADONC applications are needed in a flow, the first for forward transform and the second
for inverse, and the platform is a cluster, use CLUSTER for the forward and THREADS for the inverse
transforms. An attempt to use CLUSTER for both will not work.
Options: Threads, Cluster, None
Number of processors (CPUs)

Needed for the THREADS option. Enter a value greater than one to spread the calculation over several
CPUs.

Needed for the RADONC using the "Cluster" option. Enter the number of cluster nodes to use.
Compute node list

Needed for RADONC using the "Cluster" option. This parameter provides the option of choosing the
Compute node list. This parameter is only available when running on a cluster. If there are more than one
cluster, then they will be available in this list. This list should be set up by the System Administrator.

Needed for RADONC using the "Cluster" option. This parameter is used to specify a specific list of
sub-nodes, from the Compute node list to be used to run the migration on. This parameter is only available
when running on a cluster. If the Compute node list has many nodes, say 100 nodes named n1, n2, .. n100.
If you wanted to run KTMIG on 25 nodes, and specifically nodes n26 to n50, you would enter 26 to 50 for
the values of CPU index in the subnode matrix. Also if you enter values 11 to 20, then the node listed 11
in the Compute node list, to the node listed 20 in the Compute node list are used to run the migration on.
Therefore it is the order of listing in the Compute node list which determines which specific nodes of the
cluster this job will be run on. This parameter is useful if you plan to run several jobs on this cluster, and
want them to run on different nodes.
Output message interval

This limits the number of output ensemble messages. Messages will be output for MLIN divisible by this
parameter and MBIN divisible by 100.
994
RAS1
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program RAS1 picks static shifts using a statistical method. RAS1 computes the relative static shift by
crosscorrelating the current trace with a certain number of "near-by" traces. The term "near-by" is a
composite factor determined from the offset difference and the difference in the CMP distances between
the two traces. The user prescribes the number of "near-by" traces to crosscorrelate. The current trace is
crosscorrelated with each of the "near-by" traces. The relative static shift is defined by the peak of the
crosscorrelation function. The output pick for the current trace is an average of the picks close to the
median of all the picks.
Input Channels
Output Channels
1. Dataset of time picks for ras2: Required connection to dataset RAS1 data type.
Parameters
Start of the crosscorrelation window.
End of window (ms)

End of the crosscorrelation window.
Max. correlation shift (ms)

Half the length of the crosscorrelation operator. This limits the maximum static.
995
Number of traces to crosscorrelate

The number of "near-by" traces to use in computing the residual statics.
Maximum fold
Offset weight for trace selection
This parameter can vary the trace selection process. A larger offset weight will result in more traces being
used within the current CMP gather. A smaller offset weight will lead to more traces being used from near
by CMP gathers. Experience indicates a larger offset weight tends to give better results for low fold data.
Trimming threshold for averaging(ms)

RAS1 computes the residual statics by using only the picks which fall within Trimming threshold for
averaging(ms): of the median of all picks.
Allow to use traces from the same shot?

In the case of very low fold data but a very high number of traces per shot, most or all of the traces to be
crosscorrelated may come from the same shot. This consequently makes the estimation for the shot statics
inaccurate. To avoid this, the user can force RAS1 not to crosscorrelate traces from the same shot.
Number of traces/shot
Required if Allow to use traces from the same shot? = No. This number is used to allocate memory.
996
RAS2
Module Description
Input Channels
Parameters
Module Description
Input Channels
Parameters
CMP window for use in structure determination
CMP window for residual NMO determination
Surface source data?
Max distance to connect a source and phone.
Required if Surface source data? = Yes. The program will average the shot and nearest geophone static. If
no geophone is within Max distance to connect a source and phone. of a shot, the shot static will not be
averaged with any geophone static.
Source Statics file


997
RAS3
Module Description
Input Channels
Output Channels
Parameters
Module Description
RAS3 applies the statics computed and output to matrices by any of the statics programs that compute
surface consistent statics. Functionally, RAS3 is a subset of the STATIC program and may be replaced in
a future release.
Input Channels
1. Seismic data from previous process: Required connection from previous process GCI data type.
Output Channels
Parameters
Source Statics file

998
RAS3D1
Module Description
Input Channels
Output Channels
Parameters
Module Description
RAS3D1 is obsolete. It is being maintained for backwards compatibility. Use RESID1 / RESID2.
Program RAS3D1 picks the residual static shift using a statistical method. RAS3D1 computes the relative
static shift by cross-correlating the current trace with a certain number of "near-by" traces. The term
"near-by" is a composite factor determined from the offset difference and the difference in the bin and line
distances between two traces. The user prescribes the number of "near-by" traces to cross-correlate. The
current trace is cross-correlated with each of the "near-by" traces. The relative static shift is defined by the
peak of the cross-correlation function. The output pick for the current trace is an average of the picks close
to the median of all the picks.
The input data has to be bin sorted because RAS3D1 works on a swath of lines to ensure that both inline
and crossline traces are treated equally.
"Maximum fold" has to be given and must be no less than the actual maximum fold. The program will
crash if fold exceeds MAXFLD because this value is used to allocate memory in the pre processor.
Input Channels
Output Channels
1. Dataset of time picks for ras3d2: Required connection to dataset RAS3D1 data type.
Parameters
Restart option
Options: Not restart, Restart information, Restart execution
999

Start of the cross-correlation window.
End of window (ms)

End of the cross-correlation window.

The maximum shift allowed in cross-correlation. This also limits the maximum statics.

The number of near-by traces to use in computing the residual statics.
Maximum fold(Crucial)
Offset weight for trace selection
This parameter can vary the trace selection process. A larger offset weight will result in more traces being
used within the current CMP gather. A smaller offset weight will lead to more traces being used in the
near-by CMP gathers. Experiences indicates a larger offset weight tends to render better results for low
fold data.
Trimming threshold for averaging(ms)

RAS1 computes the residual statics by only using the picks which fall in the neighborhood of the median
of all picks. This threshold tells RAS1 which picks to use in the computation.
Allow to use traces from the same shot?

In the case of very low fold but very high number of traces per shot, most or all of the traces to be cross
correlated may come from the same shot. This consequently makes the estimation for shot statics
inaccurate. To avoid this, the user can force RAS1 not to cross correlate the traces from the same shot.
1000
1001
RAS3D2
Module Description
Input Channels
Parameters
Module Description
RAS3D2 is obsolete. It is being maintained for backwards compatibility. Use RESID1 / RESID2.
PROGRAM RAS3D2 decomposes the time shifts picked by RAS3D1 into the four components of source,
receiver, structure and residual NMO. It determines the residual NMO and structure terms within 2D
windows (lines and bins). It solves for the source and receiver terms using the Gauss-Seidel method.
The output matrices from RAS3D2 can be applied to data with RAS3 or STATIC.
Input Channels
1. Input: Required connection from dataset RAS3D1 data type.
Parameters
number of bins to use in residual NMO determination
number of lines to use in residual NMO determination
number of bins to use in structure determination
number of lines to use in structure determination
Surface source data?
Source Statics file
1002

Interval for RNMO listing
1003
RAS4
Module Description
Input Channels
Output Channels
Parameters
Module Description
RAS4 applies sequential statics computed and output by module PILOT to a RAS1 disk file. Static shifts
are applied to input traces in the order read from the input RAS1 data set. Headers SSPN and SGEN are
compared with the corresponding values from the data set. If a mis-match is detected, RAS1 will try to
resynchronize by searching for the current header values in the data set.
Input Channels
Output Channels
Parameters
Shift application
Options: Sequential, Other
Error processing
Options: Abort, Search
Search interval
Number of records to scan forward and backward to attempt to resynchronize the trace and dataset.
1004
Number of unresolved mis-matches allowed

RAS4 will abort after this number of unresolved header/dataset mis-matches.
1005
RDMO
Module Description
Input Channels
Output Channels
Parameters
Module Description
RDMO will perform velocity independent Dip Moveout using radial traces extracted from CMP gathers.
The algorithm works by collapsing the energy spread over hyperbolas that lie in the radial trace planes by
F-K migration of the radial trace profiles with the constant radial trace velocity.
The radial traces are constructed from CMP gathers with the equation:
X = U * T
Where
X = The distance from the shot to the receiver
U = The velocity of the plane through a hyperbolic
cylinder with axis in the T direction.
T = The two-way travel time in seconds.
RDMO requires the input to be CMP sorted and NMO applied with an average velocity function. The
velocities input to RDMO should be the same velocities input to the normal moveout process. In addition,
the starting velocity must not equal a U trace. If multiple velocity functions are input, the starting velocity
should be the same across the line. RDMO requires NMO to be applied so that an accurate radial trace
may be interpolated. RDMO then applies inverse NMO to radial traces. Traces output by RDMO will not
have NMO applied.
U definition
Extreme care should be taken when picking the U velocity planes that are extracted from CMP gathers. If
the velocity increment is not adequate, the output of RDMO will be spatially aliased. If the ending velocity
is not high enough, data from the far offsets will be truncated. Adequate U planes can be calculated using
the equation X=UT.
RDMO can, on option, extract U traces with a variable U increment from CMP gathers. RDMO will
determine the delta-U spacing at the maximum time until the far offset is reached by allowing the user to
select a delta-X sampling interval. The user can also define the delta-X sampling interval at the mute on
the far offset. RDMO will then interpolate a delta-X interval between the two points along with a
corresponding delta-U interval.
1006

The transformation from U-T space to F-K space is done by a horizontal and vertical Fast Fourier
Transform. The input data should be as free as possible of spikes. Sharp cutoffs in the data may produce
spikes in the F-K domain transformation. To help alleviate these sharp cutoffs, SMIG has the following
options:
NOTE: The bottom of trace linear taper should be zero (no taper) for AVO processing or else the far
offsets will be attenuated.
Reference
Forel, D., 1988, A three-dimensional perspective on two-dimensional dip moveout: Geophysics, Vol 53,
604-610.
Hale, I. D., 1983, Dip moveout by Fourier transform: Presented at the 53rd Annual SEG Meeting, Las
Vegas.
Input Channels
Output Channels
Parameters
Use evenly spaced velocity planes?
Starting velocity plane
Required if Use evenly spaced velocity planes? = Yes.
1007
Velocity plane increment

Number of velocity planes

Minimum offset
Required if Use evenly spaced velocity planes? = No.
Maximum offset
Offset increment
Required if Use evenly spaced velocity planes? = No. This is the interval between offsets within a CMP
gather. This number is normally twice the group interval.
Sampling factor at record length (%)

Required if Use evenly spaced velocity planes? = No. This is the percentage to apply to the offset interval
to compute the delta-X sampling interval at the maximum time from X=0 to X=Far offset.
Sampling factor at maximum offset (%)

Required if Use evenly spaced velocity planes? = No. This is the percentage to apply to the offset interval
to compute the delta-X sampling interval at the minimum time to process at the maximum offset.
Min. time to process at max. offset (ms.)

RMS velocities
Matrix Type: RMSVEL
Interpolate dead traces?

If "No" is chosen dead traces will be output as zeros. Otherwise dead traces will be made live traces.
1008
Apply DMO correction?

Choose "No" to perform only the U transformation. The output data should resemble the input data if the
U planes have a fine enough increment.

number of traces.

CMP padding (traces)
of the 2-D transformed data.
Time padding (samples)

This is the minimum number of zero samples to be padded at the end of the record to prevent wraparound

CMP interval
1009
READ
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module reads SeisUP internal formatted data from a tape or disk data set. For disk data sets, the user
has the option of reading the data set in one of many sort orders. If a particular sort order is chosen and the
sort keys are used for searching, then any starting id is accessed immediately rather than sequentially
reading the data from the beginning of the data set. Tape drive information will requested via the job
monitor.
Input Channels
1. Input : Optional GCI data type.
Output Channels
Parameters
Datasource
Options: Input connection, User specified dataset, User defined
dataset list
User specified dataset list

Required if Datasource is User defined dataset list.
Matrix Type: DSETLIST
1010
User specified dataset

Required if Datasource is User specified dataset.
Sort order to read

Options: Read sequential, Shot, Geophone, Offset, CMP gather, Stack,
3-D X-bin gather, 3-D Y-line gather, 3-D X-bin stack, 3-D Y-line
stack, Other, Binned X-bin offset, Binned Y-line offset
Primary sort header key

Required if Sort order to read is Other.
Primary sort header index

Required if Primary sort header key is Other
Secondary sort header key

Secondary sort header index

Required if Secondary sort header key is Other
Ensemble sort header key

1011
Ensemble sort header index

Required if Ensemble sort header key is Other
Use sort order keys for searching?

Select Yes to use the primary and secondary keys used to sort the data in the above parameter. If the Sort
order to read parameter is not Read sequential, the READ module will read the sort map and once found
in the map, will start reading the data from that point. Otherwise all searches for starting IDs will be
sequential starting from the beginning of the data set. Select No for this parameter to enter a user specified
primary and/or secondary key.
NOTE: READ will search for a trace containing Starting primary id AND Starting secondary id and will
read everything until a trace containing Ending primary id AND Ending secondary id is found. If you
wish to limit the data passed using the secondary id, use the SELECT module or select YES for the
parameter that asks "Get ensembles from selected ranges only?".
Get ensembles from selected ranges only?

Select YES if only ensembles within the selected primary and secondary keys are needed. Ensembles
outside the ranges will be thrown out and not processed. This will reduce the read and process time if only
a small sample is needed because not all ensembles are used. Select NO for normal reading (only the
primary key ranges are restricted, but the secondary key is not).
Primary search header key

TLSN, other
Primary search header ID index

Starting primary ID
Starting shot line (SLIN)
Starting receiver line (RSLN)
Starting offset (DIST)
1012
Starting midpoint line (MLIN)

Starting midpoint bin (MBIN)
Starting offset bin (DMODIST)
Ending primary ID
Ending shot line (SLIN)
Ending receiver line (RSLN)
Ending offset (DIST)
Ending midpoint line (MLIN)
Ending midpoint bin (MBIN)
Ending offset bin (DMODIST)
Secondary search header key
TLSN, other
Secondary search header ID index

Starting secondary ID
Starting shot bin (SBIN)
Starting receiver bin (RSBN)
Starting midpoint line (MLIN)
Starting midpoint bin (MBIN)
1013
Ending secondary ID
Ending shot bin (SBIN)
Ending receiver bin (RSBN)
Ending midpoint line (MLIN)
Ending midpoint bin (MBIN)
Max number of traces per ensemble
NOTE: If Max # traces per ensemble is defaulted, the value used is determined by the first data set.
Prefetch ensemble?
When this option is set to Yes the module will read in the traces for the next ensemble while subsequent
modules in the flow process the current ensemble. This will help reduce the overall run-time because
traces are being read from disk and processed at the same time. Notice, however, this option will not
improve run-times of jobs that require little or no processing time. Currently, this option is not available
when reading several data sets using the User defined dataset list.
Number of traces for sorting buffer

This option is available when the Sort order to read parameter is not Read sequential. The sorting buffer
is used to improve performance when reading traces non-sequentially. The user should choose the number
of traces for the sorting buffer based on the available system memory and size of the input data set.
Generally, it is not necessary to code this parameter for data sets with less than 500,000 traces, the sorting
buffer is more effective for use with very large data sets. Performance results will vary depending on the
input data set and sort order, but tests have shown, for example, reading CMP gathers from a data set that
is sorted by field records (OIDN, FCSN) can be 3 to 4 times faster using a sufficient sorting buffer.
Consider the following table when coding this parameter:
# Traces in input data set: # Traces to buffer:
1 to 5 million
10,000
5 to 30 million
100,000
> 30 million
200,000
NOTE: The number of traces you define for this parameter will be held in memory, so if you code 200,000
the module may require a few gigabytes. If you run several jobs at the same time in this manner you will
most likely exhaust all of the systems available memory.
1014
REFST
Module Description
Input Channels
Output Channels
Parameters
Module Description
REFST is a standalone program that computes time shifts (statics) to remove the spatially varying near
surface effects on seismic traces for 2D or 3D surveys. Acquisition geometry and first break time picks
(AFS1B matrix generated from picks made in DISPLAY) are input from the disk file built by REFSTPRP.
REFST connects to this disk file in the flow. The program builds a depth model of the near surface using a
refraction time term method. From the depth model statics to a fixed datum are computed and output into
STATSRC and STATGEO matrices. Use the COMBO option in the STATICS module to apply statics
from REFST.
Matrix data files are used for data input, output and storage. If the user is specifying v0 vs FSPN, the "v0
Matrix" must have at least 1 valid (FSPN, v0) entry. The source and geophone static matrices must have
names to output statics. All other matrices: initial, raw and smoothed refractor velocity and delay times
just need a name.
Program REFSTPRP "MUST" be run before REFST to generate the disk dataset used by REFST. Upon
REFST execution, the program reads the shooting geometry and first break picks from the RAS3D1
dataset. If there are no problems found, the SeisUP Refraction Statics CONTROL CENTER is displayed
on the screen with a default map of shot locations colored by their SSPN (surface position index). FSPN
(field shot point number) is also annotated in the bottom info window. The REFST flow menu provides
default values for refractor model and statics computation that may be overridden interactively during
operation.
NOTE: Stay platform consistent. Run REFSTPRP and REFST on the SAME computer. Failure to run on
the same platform may cause incompatibilities in the disk file output by REFSTPRP and read by REFST.
Five steps are required to compute and store statics with one extra step optional. These steps are annotated
by clicking MB1 (mouse button 1) on the light green FLOW button on the SeisUP Refraction Statics
CONTROL CENTER menu bar.
The first step in the FLOW menu, "Check Uphole Times", is optional. This step projects first break picks
from a shot to other shots nearby to get interpolated reciprocal times (shot - to - shot times). For example,
the travel time from shot 1 to shot 5 is the uphole time for shot 1 plus the interpolated first break time to
shot 5. The same analysis is applied for the time from shot 5 back to shot 1. Since each shot should have
reciprocal paths to many other surrounding shots, the average uphole time for the target shot can be
estimated from the reciprocal times. This is done in an iterative fashion and the estimated upholes
compared to the stated upholes for possible errors, which are indicated in the execution status printout.
Even if the data is shot with a surface source, this analysis may indicate shots where the first break picks
are a "leg out". After the uphole analysis is complete and printed, the user may optionally use the
1015
estimated upholes for further computation by selecting FLOW, Check Uphole Times, "Save Updated
Uphole Times".
STEP 1
The first required step in the FLOW is to define refractor offset values for at least one refractor at one map
location. This means assigning a refractor number to each pick within a desired offset range. The
maximum offset used is from the "Maximum offset for analysis" entry in the flow menu. Also required in
the menu is the "Maximum number of channels to use" item. A scan of a shot(s) in DISPLAY will
determine how many channels are need to span the offset range desired for refraction analysis. Typically
this maximum offset value is not known before refraction analysis, so, a trial run of REFSTPRP and
REFST may be needed to look at first break picks to visually determine the number of refractors and
maximum offset needed. To see the first break picks verses offset display, select the Refractor Offsets
button (under FLOW), then select the "Select Refractor Offsets - EDIT first break picks" button. The first
break picks for all shots in the survey will be display in a new window labeled "Select refractor offset
range". This display has a menu bar and a "tool" bar below. Notice the "Select Mode: FBP Edit" with the
FBP Edit in orange. This display has two (2) functions, 1) first break pick edit and 2) refractor offset
selection. To change to "Refractor Offset Selection" click MB1 on Function Mode in the menu bar and
select Change Function. The FBP Edit function will be described first.
Delete bad picks
The default first break times vs offset display gives the user a "first look" (initially) at ALL the data.
Typically there will be a central "cloud" trending from upper left (offset and time near 0) down and to the
right (increasing offset and time). Above and below the "cloud" will be bad picks, some random and
maybe some in local patterns (maybe clusters) that should be deleted before any refractor offset selection.
To delete a single pick (black square) place the pointer on the center of the pick and click MB2. To delete
picks above a line, first press and release the SHIFT key. The bottom of the window (info area) should
turn yellow. Then place the pointer at the left and below the start of picks to delete, press and hold down
MB1 and drag the pointer down and to the right, keeping the rubber band line below the picks to delete.
Upon release of MB1 the picks above the line should disappear. If the wrong picks were deleted, click
MB1 on the menu bar "UN-KILL" button colored in magenta. The same procedure is used to delete picks
below a drag line except use the CONTROL key to initiate the process. Another and perhaps faster
method to edit picks is to place the pointer at the upper left center of the pick cloud, press MB1 and drag
down and to the right in the center of the pick cloud, finally releasing MB1. The picks outside of a user
specified zone (ms above and below the rubber band line) should be gone. To select the zone size, click
MB1 on Function Mode, select "Change pick edit zone" and type in the desired value.
Show picks for a specific shot or shot for a specific pick
The MAP display is changed to a "coverage map" when the "Select refractor offsets" window (TX plot) is
first started. Initially the shots on the map are displayed black as well as the first break pick times in the
"Select refractor offsets" window. If the user clicks the MB2 button on a specific shot on the map, the
picks from that selected shot will be the only ones displayed in the "Select refractor offsets" window. That
shot selected will also change color. To return to all picks on the TX plot, click MB3 in the TX plot
window. Clicking MB3 on a pick in the TX plot will cause the shot that pick came from to change color
on the map. The shot color is reset as soon as the pointer is moved off the pick.
1016
Analysis location modes

When the TX plot is started, it defaults to "ALL locations" mode, meaning that if the near surface had
nearly uniform refractor geometry and velocity, the refractor offsets could be selected with all picks
displayed, and the user would be ready for Step 2. However, the refractor geometries and velocities
usually vary through out the survey, and the refractor offsets need selection at more than one location.
Clicking MB1 on the menu bar button "Analysis Location" shows three options for selecting locations, All
locations being the default. The second option is "Manual selection". Upon selecting "Manual selection", a
small red box appears on the map in the lower left corner, the size of this box comes from parameters
specified in the flow-map menu. Picks are displayed in the TX plot for any shots enclosed by the red box.
The user may now select locations using MB1 on the map to place the red box, and see the picks for these
shots. Selecting "Auto mode" under Analysis location will put the box back in the lower left corner,
allowing the user to use the arrow buttons next to "Location mode: Auto" info label to move the analysis
location box on the map. The size of the analysis box may be changed by MB1 click on the TX plot menu
bar button "Analysis Size". This will bring up a menu to type in the desired width, height, horizontal
overlap and vertical overlap of the analysis box locations in Auto Mode.
Selecting refractor offsets
To select refractor offsets set the "Select Mode" to "Refr Offs" (green in color) using the "Function Mode"
in the menu bar. When the TX plot is up in any of the location selection modes, the first break picks from
the shots enclosed by the red box on the map are shown in the TX plot. If the near surface of the survey is
composed of one or more layers with increasing velocity, the first breaks in the TX plot should show a
series of nearly straight line segments with definite angle changes at segment ends. If there are picks very
near the shot, the first segment (far left) may be treated as coming from the weathering layer (just under
the surface). Usually the first segment is from the wave refracted at and traveling across the bottom of the
weathering, also referred to as coming from refractor 1. The weathering layer velocity is typically not
recorded due to the first offsets being above 100ft and can sometimes be estimated from uphole data (shot
depth / uphole time). However, this may be very inaccurate in some surveys where the shot was never at
the bottom of the hole and/or the hole not at the recorded depth. Typically the uphole time is the most
trusted measurement and is used to tie the first break pick times to the surface. Subsequent linear segments
of picks may be interpreted as from refractors 2-5 if present. MB1 dragged across the refractor 1 picks will
turn those picks light blue and draw a straight line (L1 norm line fit) through them. Any picks with less
offset will be assigned to the weathering layer (refractor 0) and be colored grey, with a grey line fitted to
them. MB1 dragged again to the right of refractor 1 will turn those picks light green with a green line
fitted and displayed for refractor 2. This may be repeated for up to 5 refractors. Seldom will there be more
than two refractors in actual land surveys. Refractor 3 will be painted yellow, refractor 4 orange and
refractor 5 magenta. If you wish to change the initial selection, MB1 on the "RE-PICK" button in yellow
on the TX plot menu bar will reset all refractor distance, time, and colors to black for re-picking shots
currently in the TX plot. As you move on to a new location, the offset selections from the prior location
are projected forward, velocity based on these offsets computed and the picks colored. If the same
selections are good at this new location, MB1 the green "KEEP" button on the menu bar and continue to
another location. If the selections need updating, MB1 "RE-PICK" and re-select. As the "KEEP" or
"RE-PICK" process is happening, the shots contributing to the analysis are colored green on the map, with
the center shot colored red. Red means center of analysis and pick offsets will be stored with the center red
SSPN as the location for that analysis. When enough analysis locations are used to turn the coverage map
to mostly green, the refractor selection process is complete and the user is ready for step 2. At this point it
1017
is a good idea to store the refractor offsets in a matrix for future input by selecting the FILE menu bar
button on the TX plot and then the "Save Refractor Offsets & Initial Velocity" button colored orange.
Maps of shot depth, shot uphole times, shot surface elevation and geophone elevation
The MAP menu bar button on the CONTROL CENTER window allows the user to select maps displays
of shot data and geophone elevations. Also the velocity values annotated on the TX plot from the fitted
straight lines are available for map display with the Initial Velocity button member of MAP selection.
STEP 2
Refractor velocity estimates
After refractor offsets are defined the velocity computation step is next. The refractor offsets verses
SSPNs picked in step 1 were only selected at sparse locations on the map. To compute a refractor velocity
estimate for each SSPN the refractor offsets must be interpolated for every SSPN and a radius around each
SSPN specified to collect enough first break picks to compute a stable velocity estimate for each refractor
at every SSPN. This is done by selecting Refractor Velocity from the FLOW menu and selecting the
"Compute at each shot" option. A parameter menu will appear to allow the radius around each shot and a
pick kill deviation. Velocities are estimated by fitting an L1 norm line to the picks for each refractor. Any
picks that are the deviation amount or greater from this line in time will be deleted from any further use.
Upon completion of this part the results may be displayed in map view by selecting MAP on the control
center menu bar and Refractor Velocity from the menu, then select the refractor number. During the
velocity computation the minimum, maximum, and average velocity values for each refractor are printed
to the job "execution status". This is useful to determine the degree of smoothing that will be necessary to
ensure that the refractor velocities increase with depth. The velocities computed at this stage are referred
to as "raw" velocities. At the end of this computation the raw velocity values for all shots and refractors
are automatically written to the raw velocity matrix for later use.
Smooth refractor velocity
Refractor velocities MUST be sent through the smoothing stage for use in further steps. Smoothing is done
by selecting Refractor Velocity in the FLOW menu bar followed by selecting "Smooth shot velocity". A
parameter menu appears asking for "Spike removal percent" and "Velocity smoother radius". For any
SSPN the velocity values within the smoother radius are analyzed for the median value. If the value at the
SSPN is "Spike removal percent" higher or lower than the median, the value will be interpolated after
smoothing of all other non-spike values. If no spike is found, the velocity value at the SSPN is compute by
a cosine weighting of all velocities within the specified radius. This is repeated for all SSPN locations in
the dataset. Upon completion the smoothed velocity for each refractor may be seen by selecting the MAP
button on the control center menu bar, then the "Smoothed Velocity" button followed by the refractor
number button. As in the "raw" velocity computation, velocity statistics are printed to the job Execution
Status file. The velocity values computed at this stage are referred to as "smoothed" velocities. As
smoothed velocities are used in further computations, this step MUST be done. To perform this step
without actually smoothing the "raw" velocities, use a radius of 10 (some very small value) and the
"smoothed" velocities will be the same as the "raw". At the end of this computation the smoothed
velocities for all shots and refractors are automatically written to the Smoothed velocity matrix for for
later use.
1018
v0
The final necessary step for the velocity stage is to either input or compute v0. The first method is to enter
FSPN vs v0 in to the "v0 matrix" in the main REFST menu. Values from the matrix will be input and v0 at
all other SSPNs will be interpolated. This option is invoked by selecting FLOW, Refractor Velocity
followed by selecting the "Input v0" button. Remember to have this matrix named and values in it before
executing REFST. A second method to get v0 is to select the option "Compute v0 from uphole data" under
FLOW, Refractor velocity. This assumes the uphole and shot depth data are accurate. The third method to
get v0 is to select the option "Compute v0 from near offsets" under FLOW, Refractor Velocity. This
method assumes the first break picks from offset 0 to the first change in slope can be treated as being from
the near surface layer. If this option is selected, all the velocities annotated by the grey lines in the "Select
Refractor Offsets" stage are used in the computation of v0.
STEP 3
Delay Time Computation
After refractor velocities and v0 are available, shot and geophone delay times must be computed.
Discussions of the delay time method of refractor analysis can be found through out the literature, the
more recent being "Static Corrections for Seismic Reflection Surveys" by Mike Cox, #9 in the
Geophysical Reference Series from the SEG. Delay times are computed by selecting FLOW, Delay Times,
Compute Delay Times. A parameter menu appears for specification of the number of refractors to use, and
the number of iterations in the delay time decomposition. While selecting refractor offsets the user may
have picked up to 5 refractors. Suppose the user picked offsets for two (2) refractors. Sometimes most of
the near surface variation can be removed with just 1 refractor. As an experiment, the user may move
forward with just 1 refractor, eventually produce statics, and test them on a brute stack. If the event
continuity improvement is questionable, the user may return to this Delay Time stage and try 2 refractors,
eventually compute statics and stacking the data to see if the 2 refractor solution is any better. During the
delay time decomposition the average change in delay times between iterations is printed for shots and
geophones along with the average computation fold. If the average change in delay times for any refractor
is not decreasing on successive iterations, the decomposition is unstable. This may be due to bad picks,
bad refractor offset selection ,or bad geometry. In theory, the shot delay time should be the same as a
geophone delay time at the same location (surface consistent principle). For surface source data, they
should be very close. On shot hole data, there will be some differences. At the end of this computation all
shot and geophone delay times for all refractors will automatically be written into the source and
geophone delay times matrices for later use.
If, while picking the refractor offsets, you notice the near source layer being extremely variable in offset
range, select YES to the "Steep Dip option". This will compute delay times first to get an estimate of the
first layer dip angles. The delay times will be recomputed using the dip estimates to refine the offset (X)
term of the delay time equation: T = Ts + X/V2 + Tg, where Ts is the shot delay, Tg is the geophone
delay, X is the effective source-geophone offset and v2 is the velocity of refractor 2. Only the first layer
will be affected by this option, so only pick 1 refractor when using the "Steep Dip option".
STEP 4
1019
Layer Thickness and Refractor Elevation Computation

The near surface depth model must be computed from the delay times and refractor velocities. This is
done in a layer by layer fashion starting with the near surface layer and progressing downward. Before any
computation is begun, v0 is checked for values less than v1 for each shot. If it is not, a new v0 value is
interpolated to ensure v0 < v1 at any shot. The remaining refractor velocities are checked for increasing
velocity with each refractor. If there is an inversion, an error message will be written to the execution
status and the program will terminate. An inversion condition may be caused by assigning more refractors
than actually exist, using bad picks, or by not smoothing the raw velocities enough to remove bad values
caused by low fold computations.To compute layer thicknesses and refractor elevations, select Refractor
Depth from the FLOW menu, followed by "Compute Layer Thickness". A menu will appear that asks to
select the option to Smooth first refractor. If YES is selected, the user must select either Refractor 1
elevation or Layer 1 thickness, and specify a smoothing radius. The equation used for thickness
computation is 5.16 from the book Refraction Seismics by Dereck Palmer. Depth solutions for shot and
geophone are done separately. Sometimes there is no weathering velocity (v0) available for surface
shooting. In this case the user typically specifies a constant v0 at some FSPN and attempts a solution.
Optionally, the user may choose to use the constant v0 as a first approximation, then smooth the first
refractor elevation (optionally first layer thickness) then, v0 is recomputed for each shot. The updated v0
is projected into geophone coordinates and all layer thicknesses re-computed. On some datasets (steep
refractor 1 dip) this method may compute a better static solution, assuming the original constant v0 was a
reasonable average and that the actual first refractor depths are smooth. After the depth model is computed
the shot refractor elevations and geophone refractor elevation may be viewed by selecting Shot Refractor
Elevation or Geophone Refractor Elevation, then the refractor number, all from the MAP menu. The
elevations for a refractor are usually very close for shot and geophone for surface source data. Deep shot
hole data may have differences. Layer thickness statistics are printed in the execution status.
STEP 5
Shot and Geophone Statics Computation
The final step in refraction analysis is to compute statics for shots and geophones that moves them to the
fixed datum. The math includes subtracting the time from shot or geophone to bottom of refractor model
then adding the time to go from bottom of model back to surface at a user specified constant velocity or
bottom refractor velocity, and finally adding time from surface to the fixed datum at a replacement
velocity. In many cases the velocity used for the second part, bottom of model back to surface, will also be
the replacement velocity. If the acquisition method was subsurface, the user has a choice of using the
uphole time or the shot depth for computing the shot static. If the uphole time is most trusted, the uphole
time is used to tie the shot to the surface and proceeding as if it were a surface source. If the shot depth is
most trusted, time from the bottom of the shot hole to the bottom of the model is used as the first step.
After static values are computed the source and geophone statics are automatically written out to matrices
for further use.
Control Center Features
VScale
1020
VScale controls maximum and minimum values used to scale velocity maps. The default is to scale every
velocity map by max and min of all velocities input including v0. More detail may be seen on refractor
velocity maps if the VScale, "All but v0" option is selected. Selection of VScale, "Same refractor" means
only the max and min of refractor 1 initial, raw and smoothed values are used for any refractor 1 velocity
map. The same idea applies to any refractor #n. To return to the default case of all velocities select
VScale, "All velocities".
Zoom
Select Zoom followed by either "Zoom IN" to enlarge the map or "Zoom OUT" to shrink the map. Scroll
bars allow selection of the map areas in view.
Map Section
A cross section of map values may be displayed by selecting Map Section, then "Select Cross section
points", followed by a series of MB1 clicks on the map describing the cross section path, ending the path
by an MB2 click. If the path crosses any points on the map with legitimate map values, these values will
be plotted in a Map Cross Section window. On the Map Cross Section menu bar is a button named
"Section(s)" that allows switching between and over plotting of some shot and corresponding geophone
sections. Switchable/overplotable sections include elevation, delay times, refractor elevations and statics.
Remove the Map Cross Section window (File, Exit) before changing map value types. A suggested use of
the cross-section display is to check smoothed velocity values to find any refractor velocity inversions, as
these will cause program termination if uncorrected.
When analyzing 2D data, a cross section of the entire line (up to 3000 shots or geophones) may be seen by
simply clicking MB1 then MB2 on any shot or geophone of the line. If there are more than 3000 shots or
geophones, select only parts of the line with MB1 clicks and end with MB2.
Input Channels
1. Seismic Data: Optional GCI data type.
2. Preprocessed Data: Output from REFSTPRP module.
Output Channels
1. Output: Optional GCI data type.
Parameters
1021
run ID number (1 or greater):

Survey type?
Options: 2D, 3D
Number of refractors
This is a guess of the number of refractor needed to detail the near surface. This value may be overridden
during execution.

This value will determine the first break picks selected for analysis. Refraction analysis must have picks
from a far enough distance to detail the near surface. This parameter MUST have the same value as the
one used in REFSTPRP.

This value is the number of first breaks allowed per shot to detail the near surface. If too small, some
usable picks may be lost. The maximum value is the number of channels per shot. The user should
examine shot records in DISPLAY sorted by ABS(DIST) to see how many traces are needed to provide
first break data out to the maximum offset selected above. This parameter MUST have the same value as
the one used in REFSTPRP.
Refractor definition method

Select "Graphical" to specify initial values for the area rectangle size used in Manual or Auto selection
mode.
Options: Graphical, Matrix input
X width of analysis zone

This is the width (X width in ft/m) of the moving analysis zone used for refractor offset definition in
manual or Auto mode.
Y height of analysis zone

This is the height (Y height in ft/m) of the moving analysis zone used for refractor offset definition in
Manual or Auto mode.
1022
Percent X overlap
This is the X zone overlay percent using Auto mode.
Percent Y overlap
This is the Y zone overlap percent using Auto mode.
Compute refractor velocities?

Radius of zone
All the picks from shots within this radius of a target shot will be combined for a velocity analysis at the
target shot.
MS deviation for bad pick

After velocity lines are computed for each refractor at a target shot, any first break time pick that deviates
from its velocity line greater than this amount will not be used in further computations.
Spike removal percent

During velocity smoothing, the velocity values (for a refractor) within "Velocity smoother radius" of a
target shot are gathered, sorted and the median value found. If the current refractor velocity at the target
location is greater than this percent away from the median, the value at this location will be interpolated
after all other good values are smoothed.
Velocity smoother radius

The refractor velocity value at a target location is the weighted cosine of values within this smoothing
radius, assuming the current value is withing "Spike percent removal percent" of the median of values
within this radius.
Minimum refractor velocity

Maximum refractor velocity
v0 matrix:
This is a v0 verses FSPN matrix used for user input of v0 values. This matrix is essential when v0 is hand
typed and not computed internally.
Matrix Type: V0
1023
Compute delay times?

This is the number of iterations desired in the time term decomposition.
Steep refractor dip option?

Compute refractor depths?
Smooth refractor depths?
When the acquisition method is surface source or when no reliable v0 info is available, the user can
specify a constant v0, then smooth the first refractor elevation (or first layer thickness) to compute variable
v0 from the delay time and smoothed depth values. This assumes the first refractors geometry is smooth
and that the constant v0 input is a reasonable average of the actual value. This procedure can remove the
variable v0 effects from the statics solutions.
Smooth?
If YES was selected above, the user must decide to smooth either the first refractor elevation or first layer
thickness.
Options: First refractor elevation, First layer thickness
Length of smoother
The radius of smoothing about any shot point should be enough to remove the v0 variation of local shots.
Compute statics?
Elevation of FIXED datum:
This datum is also referred to as "final datum".
Velocity from model to surface?

This is the velocity used to compute time from bottom of the refractor model back up to the surface. The
user may specify the bottom refractor velocity (may vary over the survey) or a constant velocity.
Options: Use bottom refractor velocity, User specify
1024
Enter velocity from model to surface:

If the user selects "User specify" above for Velocity from model to surface, enter a constant value for that
velocity. In many cases this value will be the same as the replacement velocity specified below.
Velocity from surface to FIXED datum:

The value needed here is usually referred to as the replacement velocity.
Acquisition method:
Options: Sub-surface shooting, Surface shooting
What do you trust most?

Often times shots in holes exploded at depths less than those stated on the observers sheets. Occasionally
the uphole times reported are in error. When the v0 computed from uphole times and shot depths are
nearly the same as the first refractor velocity, v1, the shot hole information is suspect. Unfortunately the
uphole times are needed to tie first break times to surface, so they must be used. However, when
computing statics, the user may elect to use the shot depth to compute the time from shot to the bottom of
the refractor model rather than use the uphole time to tie to surface then finishing the computation as if
there were surface sources.
Options: The Shot depths, The Uphole times
Output Source statics matrix:

Output Geophone statics matrix:

EDITED First Break Times Matrix:

Matrix Type: AFS1B
List refractor velocities?

If YES was selected the raw and smoothed refractor velocities will be printed in the Execution Status file.
1025
REFSTPRP
Module Description
Output Channels
Parameters
Module Description
REFSTPRP is a standalone program that extracts geometry data needed for REFST (Refraction Statics)
from the Area/Line DB file and loads it into a binary output file for fast access by REFST. This program
MUST be run prior to REFST. Shot values extracted are:
SSPN (Sequential Shot Point Number) This is a shot index number going from 1 to the total number
of shots.
FSPN (Field Shot Point Number) This is a number where the first half is related to the X location and
the last half is related to the Y location of the shot.
SE (Shot Elevation) This is the surface elevation at the shot location.
SU (Shot Uphole) This is the time from the shot to the surface (0 for surface source).
SD (Shot Depth) This is the depth from surface down to the shot (0 for surface source).
SX (Shot X coordinate) This can be an absolute or relative X value.
SY (Shot Y coordinate) This can be an absolute or relative Y value.
NPTS (Number of first break picks for the shot) This maximum of this value is set by the user. The
maximum possible value is the number of recording channels per shot. If first breaks are only picked
for traces near the shot, this number can be less than the number of channels in the shot. It is used to
determine array sizes in REFST.
Each shot will have picked, at maximum, NPTS channels. For each usable channel the following attributes
are grouped and output:
SGEN (Sequential Geophone Number) This is a location index for geophone locations. It may start at
some number, increment, and end at a higher number.
OFFSET (Horizontal distance from shot to geophone) This number will always be positive.
FBT (First Break Pick Time) This is the first break time in milliseconds for the channel.
The time required for execution depends upon the platform and can take several hours for small datasets
and many hours for large (150000 shot datasets). NOTE: Run both REFSTPRP and REFST on the same
(endian type) platform or the output disk file may not be usable.
Output Channels
1. Output: Required connection to RAS3D1 formatted dataset.
1026
Parameters
Survey type?
Options: 2D, 3D, OBC
First Break Times Matrix

The first break times are generated prior to running REFSTPRP by using module RFS1 or picked/edited
interactively in module DISPLAY.
Matrix Type: AFS1B

This value will determine the first break picks selected for analysis. Refraction analysis must have picks
from a far enough distance to detail the near surface.

This is the number of channels picked per shot. The maximum value possible is the number of channels
per shot. During execution, if there were usable picks not loaded because this value was too low, this info
message will be issued : "WARNING - max channels per shot to use too LOW".
1027
REGRID
Module Description
Input Channels
Output Channels
Parameters
Module Description
REGRID is a module for 3-D poststack and prestack common offset regriding. Stack or common offset
volumes from one grid system can be resampled and mapped to another. The old grid system is specified
by the input parameters of this module. The new grid system is the current geometry defined by the
STATION module. Input trace headers MCX and MCY must exactly match the input parameters. Output
trace headers SDPN, MSFL, MEFL, MBIN, MLIN, MCX, and MCY will be redefined in this program
according to the new geometry. All the other output headers will be bi-linearly interpolated from the input.
Any input traces which are not covered by the new geometry will be dropped from the output. If the input
data are not aliased, REGRID can also be used as an interpolation program. It is highly suggested that if
you are regriding prestack common offsets that you do not sort the data back to common shots or common
geophones because the information in the interpolated traces will probably be incorrect.
The following procedure shows how to use REGRID to merge several 3-D poststack volumes into a new
grid system:
1.
2.
3.
4.
Step 1 - Define the new grid system using STATION.

Step 2 - Apply REGRID separately to different stack volumes and map them to the same geometry.
Step 3 - Use READ to read all the datasets together and merge them to one file.
Step 4 - Apply STACK to the new file.
NOTE - If REGRID hits an input ensemble that consists entirely of dead traces, it will stop as if it had
encountered the end of data. Remove dead traces prior to running REGRID.
Input Channels
Output Channels
1028
Parameters
Azimuth of the input survey in degrees
The default is to compute an azimuth that is derived from the first ensemble that is input.
Inline midpoint interval of the input survey

Crossline midpoint interval of the input survey
Number of midpoint bins of the input survey
Number of midpoint lines of the input survey
Maximum amount of memory to use (MB)
This will be limited to 2048 on 32 bit systems.
Interpolation method
The option None is primarily for unstacked data. Defaulting Azimuth of the input survey in degrees: is
possible but not advised with this option.
Options: Sinc, Bilinear, Nearest Neighbor, None
Inline interpolator length (# of bins)

Required if Interpolation method is set to Sinc. This will be set to the next larger even number if odd.
Crossline interpolator length (# of lines)

Required if Interpolation method is set to Sinc. This will be set to the next larger even number if odd.
Use reversed trace logic

REGRID can output reversed polarity traces along the edges of the survey. These are generally of low to
very low amplitude. Use this parameter to fix these traces.
1029
RELOC
Module Description
Parameters
Module Description
RELOC updates X and Y coordinates in Source and Station matrices.
Parameters
Survey Type
Options: 2D, 3D
Shot acquisition type:

Land surveys will in addition to marine information ask for the depth, uphole time, and the elevation for
each shot.
Modify Source/Station matrix:

Options: Source, Station, Both
Source specification by:

This is the method to specify the shot locations.
Options: Coordinates, Receiver location, Distance from previous shot
Required if Source specification by: is Coordinates or Receiver location.
This is the method to specify the receiver locations.
Options: Distance from shot, Receiver location, Spread layout
1030
Source
Required if Shot acquisition type: is Land and Source specification by: is Coordinates and Pattern
specification by: is Distance from shot and Modify Source/Station matrix: is Source or Both.
Source
specification by: is Receiver location and Modify Source/Station matrix: is Source or Both.
Source
specification by: is Spread layout and Modify Source/Station matrix: is Source or Both.
Matrix Type: SRCXYSPD2
Source
Required if Shot acquisition type: is Land and Source specification by: is Receiver location and Pattern
Source
Source
Land source by receiver and pattern by spread
1031
Source
Required if Shot acquisition type: is Land and Source specification by: is Distance from previous shot
and Modify Source/Station matrix: is Source or Both.
Matrix Type: SRCDXOFF2
Source
Marine source by coordinate and pattern by distance from source
Required if Shot acquisition type: is Marine and Source specification by: is Coordinates and Pattern
Matrix Type: SOURCE
Source
Marine source by coordinate and pattern by receiver location
Source
Matrix Type: SRCXYSPD
Source
Required if Shot acquisition type: is Marine and Source specification by: is Receiver location and
Pattern specification by: is Distance from shot and Modify Source/Station matrix: is Source or Both.
Source
Pattern specification by: is Receiver location and Modify Source/Station matrix: is Source or Both.
1032
Source
Pattern specification by: is Spread layout and Modify Source/Station matrix: is Source or Both.
Matrix Type: SRCRECSPD
Source
Required if Shot acquisition type: is Marine and Source specification by: is Distance from previous shot
and Modify Source/Station matrix: is Source or Both.
Matrix Type: SRCDXOFF
Shot time errors

Required if Survey type: is 2D and Modify Source/Station matrix: is NOT Station.
Shot time errors

Required if Survey type: is 3D and Modify Source/Station matrix: is NOT Station.
Matrix Type: AFS1B
Print Shots?
Stations
Required if Modify Source/Station matrix: is Station or Both.
Station time errors

Required if Survey type: is 2D and Modify Source/Station matrix: is NOT Source.
1033
Station time errors

Required if Survey type: is 3D and Modify Source/Station matrix: is NOT Source.
Matrix Type: AFS1B
LMO Velocity
Line Azimuth
Required if Survey type: is 2D.
Delta Time Bias

Azimuth increment
Azimuth bias
Update all files with same FSPN

Update matrices
Put radius/azimuth in SOURCE matrix
Update threshold
1034
REPEAT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module REPEAT will repeat each ensemble the coded number of times. Each repeated copy of the
ensemble will be identical except for the header word that contains the repetition number. Each copy will
in turn be passed to the remaining modules in the flow. After the last copy is passed, control will be
returned to head of the flow, usually READ.
The module may be used to perform trials, such as filter tests. For example, HMTH can be used to set a
header word (using the repetition number) tied to parameters pointing to filters coded in module CONV.
Input Channels
Output Channels
Parameters
Header to store count
The repetition number is stored in this header word.
TLSN, other
Header ID Index to store count

Required if Header to store count = other.
1035
Number of times each ensemble output

This number of copies of each ensemble are passed to all modules following REPEAT in the flow.
1036
RESAMP
Module Description
Input Channels
Output Channels
Parameters
Module Description
RESAMP resamples the seismic traces by retaining every resampling factor sample from the input traces.
No anti-alias filter is applied. The anti-alias filter should be applied in a previous FILTER module if
desired.
Input Channels
Output Channels
Parameters
Resampling factor
Options: 2, 3, 4, 5, 6
1037
RESID1
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program RESID1 picks static shifts using a statistical method. RESID1 computes the relative static shift
by crosscorrelating the current trace with a number of traces within a coordinate and offset range. The
relative static shift is defined by the peak of the crosscorrelation function. Three peaks on the
crosscorrelation function and other information are passed to RESID2 for solution.
Memory Requirements
variable
default
override parameters
nxbin
Get from DB
Maximum midpoint bin number Minimum midpoint bin number + 1
nybin
Get from DB
Maximum midpoint line number Minimum midpoint line number + 1
bmmax
5 by way of
MBIN / MLIN range
Maximum number of midpoint lines

to hold in memory
nctr
Number of traces to
crosscorrelate:
nchn
Get from DB
Number of traces/shot:
noff
Get from DB
Maximum fold:
nt
The number of
samples per trace
none
lhd
87 (header size)
none
maxnt_buf
Get from dataset
none (maximum number of traces

per ensemble)
mbuf
depends on if the data is 2D or 3D
For 2D data:
minimum of (nxbin,nybin,bmmax) * (nctr + 1) *
(maximum of (nchn,noff) + 1)
1038
for 3D data:
nxbin * minimum of (nybin,bmmax) * (noff + 1)
There are several in core arrays needed. Their sizes total to:
(nybin * (nxbin + 1) + maxnt_buf + mbuf * 6) * 4 bytes
The memory mapped (on disk) array needs:
(nt + lhd) * mbuf * 4 bytes
Input Channels
2. Dataset of time picks from previous RESID1: Optional connection from dataset RAS1 data
type.
Output Channels
1. Dataset of time picks for RESID2: Required connection to dataset RAS1 data type.
Parameters
The time zone(s) used for correlation is the single most critical set of parameters. Ideally, the time zone(s)
should be picked over the best signal to noise available.
Multiple time zones?

Set Multiple time zones? = Yes for a single time variant window.
Correlation windows
Required if Multiple time zones? = Yes.
Number of time zones

1039
Primary header key

TLSN

TLSN

Required if Multiple time zones? = No. Start of the crosscorrelation window.
End of window (ms)

Required if Multiple time zones? = No. End of the crosscorrelation window.
Header to add to correlation start time

Header to add to correlation end time

Max. correlation shift (ms)

Half the length of the crosscorrelation operator. This limits the maximum static. If the time zone is less
than 2.0 * Max. correlation shift (ms): long at a location, the location is not used. This allows time zones
to be pinched out and picked up again.
Normally, this parameter should be roughly three dominant periods of the data to allow for a leg jump
search in the solution phase. If the data has significant coherent noise, it should be smaller.
NOTE: This parameter directly impacts CPU time requirements.
1040

A maximum of Number of traces to crosscorrelate: equations will be written for every input trace. The
traces are randomly selected from all traces within an offset, coordinate range.
NOTE: This parameter directly impacts CPU time requirements and output dataset size. Reasonable
values for this parameter depend on the signal to noise ratio, the fold coverage and the number of traces
per shot. Number of traces to crosscorrelate: = 1 has produced good results on high fold 3-D surveys with
good signal to noise. Number of traces to crosscorrelate: = 10 was required for low fold 2-D data with
poor signal to noise. Exceptionally poor data may require a value of 20 or more.
NOTE: If this program is run reading in a previous equation file and using exactly the same data as
before, DO NOT USE THE SAME VALUE FOR THIS PARAMETER!
Maximum number of traces from the same shot.

This parameter attempts to spread the statistics as evenly as possible by limiting the number of traces that
may be crosscorrelated with a trace. It should be set to 0 for 100% data.
Maximum number of traces from the same geophone.

This parameter attempts to spread the statistics as evenly as possible by limiting the number of traces that
may be crosscorrelated with a trace. It should be set to 0 for 100% data.
Ratio of line spacing to bin spacing.

If the lines are two times as far apart as the bins, set Ratio of line spacing to bin spacing. = 2.0.
NOTE: If the lines are more than 10 times as far apart as the bins, set Ratio of line spacing to bin spacing.
= 0.0 and input the next two parameters directly.
Number of bins for each dip/RNMO unknown.

Required if Ratio of line spacing to bin spacing. = 0.0. One dip or RNMO unknown will be assigned for
each Number of bins for each dip/RNMO unknown. bins. This effectively smooths the RNMO and dip
solution.
The Radius for RNMO smoother (bins)., Radius for dip-x smoother (bins). and Radius for dip-y smoother
(bins). parameters in RESID2 are reset by this parameter.
Number of lines for each dip/RNMO unknown.

Required if Ratio of line spacing to bin spacing. = 0.0. One dip or RNMO unknown will be assigned for
each Number of lines for each dip/RNMO unknown. lines. This effectively smoothies the RNMO and dip
solution.
1041
The Radius for RNMO smoother (bins)., Radius for dip-x smoother (bins). and Radius for dip-y smoother
(bins). parameters in RESID2 are reset by this parameter.
% mute allowed.
Percentage of a trace within a time zone that may be muted and still be considered a live trace.
Extra parameters?
Extra parameters = Memory limitations is used for lines where the default space allocations are not
appropriate. Extra parameters = Expert mode should not be generally used.
Options: Normal, Memory limitations, Expert mode
CMP interval (ft. or m.)

Required if Extra parameters? = Memory limitations or Expert mode. This parameter seldom needs to
be changed.
Maximum offset difference.

Required if CMP interval (ft. or m.) = 0.0. This parameter limits the number of traces that may be
crosscorrelated with a trace. This parameter seldom needs to be changed.
Maximum coordinate difference.

Required if CMP interval (ft. or m.) = 0.0. This parameter limits the number of traces that may be
crosscorrelated with a trace. This parameter seldom needs to be changed.
MBIN / MLIN range

Required if CMP interval (ft. or m.) = 0.0. This parameter limits the range of possible target traces.
Maximum fold
Required if Extra parameters? = Memory limitationsi or Expert mode. This parameter is used for space
allocation. The value is not critical. The nominal maximum fold of live traces within the window(s) used
as opposed to the absolute maximum fold may generally be used.
allocation.
1042
Maximum number of midpoint lines to hold in memory

allocation.
Minimum midpoint bin number.

allocation.
Maximum midpoint bin number.

allocation.
Minimum midpoint line number.

allocation.
Maximum midpoint line number.

allocation.

Required if Extra parameters? = Expert mode. Threading the program has not proved to be a significant
speed up yet. For now use 1 thread only.
RESID1 assumes that relatively nearby traces have approximately the same signal, random static
differences, random noise, possibly some RNMO and dip. The crosscorrelation of two such traces should
look like an autocorrelation with a strong central peak and weaker side lobes. Like the following.
1043
If this looks too good to be true, it is. This is from synthetic data. A more realistic crosscorrelation, from
live data, looks like this.
1044
This crosscorrelation has six positive peaks. RESID1 assumes that the "correct" peak is one of the three
largest and is most likely to be the largest peak. The next three parameters attempt to identify
crosscorrelations where the assumption is violated and reject the picks. The following crosscorrelation,
from real data, illustrates that even strong correlations can be useless. The largest peak is actually negative
and there is virtually no standout between the largest positive peaks. One of the traces that generated this
crosscorrelation contained a noise burst.
1045
Minimum pick amplitude allowed.

Required if Extra parameters? = Expert mode. This parameter rejects crosscorrelations that are too weak.
Maximum ratio of secondary peak to primary.

Required if Extra parameters? = Expert mode. This parameter rejects crosscorrelations that have too little
standout.
Negative standout ratio.

Required if Extra parameters? = Expert mode. This parameter rejects crosscorrelations that have
negative peaks that are too large.
1046
RESID2
Module Description
Input Channels
Output Channels
Parameters
Module Description
RESID2 uses a conjugate gradient method to solve for surface consistent shot and geophone statics,
RNMO and dip.
RESID2 has several classes of equations. The trace to trace equations are derived from the correlations
done in RESID1. Taken alone, these consist of an overdetermined underconstrained system of equations
which needs some additional information to produce a reasonable solution. This is provided by the
constraint and bias equations.
Constraint equations try to keep the solution within reasonable bounds. For example; the statics are small.
Bias equations try to require certain unknowns to equal given values. For example; RNMO is zero. All
equations have weights that determine their relative effect.
Constraint and bias equation weights are multiplied by the average trace to trace equation weight ( <= 1.0
). If the weight is zero, no equation is written. Weights greater than 4.0 should be used with considerable
caution.
The smoother lengths mentioned below are the half width at half maximum of Gaussian functions. The
functions are cut off at the 1% response level.
There is considerable interplay between the equation weights and the smoother lengths. Large weights and
long smoothers tend to hammer the solution. Small weights and short smoothers may have little effect.
The execution status output by the program contains:
General information about the dataset.
The RMS error for an iteration and the percent change in the error to the previous two iterations.
Error analysis output.
A histogram of errors for the live equations.
The RNMO and dip solutions. NOTE - These are average values over the correlation window(s) used
in RESID1.
The shot and geophone statics and RMS errors. The RMS error is determined from all live equations
using the corresponding unknown. RMS errors tend to be larger where the fold coverage drops off.
They can also be large where there is a signal to noise problem. A zero RMS error is either an
unusually good solution or a case where all equations using the unknown were killed. Dont put too
much significance to any one RMS error value.
1047
Input Channels
1. Equation file: Required connection from dataset RAS1 data type.
Output Channels
1. Dip plot: Optional connection to dataset CGM data type.
Parameters
Source Statics file

Surface source?
This ties the statics of a surface source and the closest geophones.
Weight for surface source constraint equations.

Required if Surface source? = Yes. Set to zero if Maximum distance to tie source and phone. < 1.0.
Maximum distance to tie source and phone (ft. or m.)

Required if Surface source? = Yes.
This is in feet or meters.
Maximum number of iterations.

The solution will stop on or before Maximum number of iterations. passes.
Maximum percent of equations to kill.

This parameter is used to limit the number of trace to trace equations that can be killed at an error analysis.
It resets Error limit for trace to trace equations (msec). at each error analysis. The error limit used will
never be less than Error limit for trace to trace equations (msec)..
1048
This example, from a poor data line, shows the error function before an error analysis, the "best fit"
function of the trace to trace equations and the error function after equations were killed. The prominent
humps in the before curve are due to leg jumps. Only 35% of the primary picks were kept by the error
analysis.
Interval for RNMO and dip listing.

RESID1 outputs RNMO and dip unknowns every 10 bins and lines by default. This parameter controls
how often these unknowns are printed.
Solve for dip dependent RNMO (3-D only)?

Solve for RNMO in dip and strike directions. Solve for dip dependent RNMO (3-D only)? = Yes increases
CPU time requirements by roughly 50%. It is primarily used for 3-D data with steep dips.
Do the time zones follow structure?

Required if Data type = Time zones follow structure. If the time zones follow structure, they will be used
to build an initial dip solution. This will significantly improve the rate of convergence of the solution.
1049
Correlation windows
Required if Do the time zones follow structure? = Yes. The initial dip solution is the average of the
window start and end times. Windows that are pinched out should increase the start time and decrease the
end time by the same amount to avoid putting a transient into the dip solution.
Primary header key

Required if Do the time zones follow structure? = Yes.
TLSN

Required if Do the time zones follow structure? = Yes.
TLSN
The next three parameters are for the dip plot output for 3-D data.
Width of plot - inches (3D only)

Height of plot - inches (3D only)
Plot origin at
Options: lower left, upper left, lower right, upper right
Fudge factor for constraint equations

This parameter is to estimate the size of an array needed to keep track of which pick to use for each
equation. This may need to be increased if there are an unusually large number of dead shot or geophone
positions relative to the number of equations.
Data type
Data type = Normal data,Time zones follow structure or Low fold set normally hidden parameters to
reasonable values. Data type = Converted wave data displays parameters for converted wave data.
Optimal defaults for parameters for converted wave data have not been determined. Data type = Data
quality problems displays parameters for problem data. Data type = Expert mode displays additional
1050
parameters that should not generally be changed.

Options: Expert mode, Normal data, Time zones follow structure, Data
quality problems, Low fold, Converted wave data
Error limit for trace to trace equations (msec)

Required if Data type = Data quality problems or Data type = Expert mode.
Weight for small static constraint equations

Required if Data type = Data quality problems or Data type = Expert mode. This requires the shot and
geophone statics to have zero average values.
Weight for long wavelength constraint equations

Required if Data type = Data quality problems or Data type = Expert mode. This requires the statics
over an operator length average to zero.
Long wavelength operator length (ft. or m.)

Required if Data type = Data quality problems or Data type = Expert mode. This is in feet or meters.
The default is the maximum offset used minus the minimum offset used. This is an effective spread length
which may by significantly less than an actual spread length.
Weight for RNMO constraint equations

Required if Data type = Data quality problems or Data type = Expert mode. Set to zero if Radius for
RNMO smoother. < 1.0.
Radius for RNMO smoother (bins)

Required if Data type = Data quality problems or Data type = Expert mode. Set to 250.0 if Data type =
Low fold. This is in CMPs / MBINs or MLINs. If the defaults are used in RESID1, Radius for RNMO
smoother. < 40 will have no effect.
The next three parameters cause equations to be written that attempt to force the respective parts of the
solution to stay near their initial values (zero for RNMO and either zero or the values determined by
Correlation windows for dip x and dip y).
Weight for RNMO bias equations

1051
Weight for dip x bias equations

Time zones follow structure.
Weight for dip y bias equations

Time zones follow structure.
Bias weights?
Required if Data type = Expert mode. This parameter allows the constraint equation weights to be
adjusted for fold. Bias weights? = Stronger for low fold should be used for data with large changes in
fold coverage and regions of very low fold. For poor signal to noise data, use of Stronger for low fold or
Stronger for high fold may destroy the solution.
Options: Even weight, Stronger for high fold, Stronger for low fold
Solve for channel statics?

Required if Data type = Data quality problems or Data type = Expert mode. This option was included
for recording systems that require multiplex scan corrections. If the corrections are not done or are not
done correctly, the channel statics will have a pattern to their values. Otherwise, the expected values are
small and pseudo random. The hallmark of a multiplex scan problem is skewed statics: the shot statics
have a slope and the geophone statics have the opposite slope. Channel statics will not be solved for if the
number of geophones is less than twice the number of channels. Significant channel statics can also be
generated if the mute effectively kills a large fraction of the traces.
RMS error limit (msec)

Required if Data type = Data quality problems or Data type = Expert mode. If, after the first error
analysis, the RMS error drops below this value, the solution stops.
Cutoff in % change in RMS error

Required if Data type = Data quality problems or Data type = Expert mode. If, after the first error
analysis, the RMS error changes by less than Cutoff in % change in RMS error. % over two steps, the
solution stops.
Number of iterations between an error analysis

Required if Data type = Expert mode. During an error analysis, peaks may be swapped and equations
may be turned off or turned back on. Too low a value for this parameter may cause the solution to get
"lost".
1052
During an error analysis, equations may be turned off if their error exceeds the following values. A zero
value prevents the equation from being killed.
Error limit for static constraint equations (msec)

Error limit for RNMO and dip constraint equations (msec)

Error limit for small statics constraint equations (msec)

Error limit for bias equations (msec)

CMP interval (ft. or m.)

Weight for shot static constraint equations

shot static smoother. < 1.0.
Radius for shot static smoother (ft. or m.)

Weight for phone static constraint equations

geophone static smoother. < 1.0.
Radius for phone static smoother (ft. or m.)

1053
Weight for dip-x constraint equations

Time zones follow structure. Set to zero if Radius for dip-x smoother. < 1.0. Use of this parameter with
poor quality data is dangerous.
Radius for dip-x smoother (bins)

Low fold. This is in CMPs / MBINs or MLINs. If the defaults are used in RESID1, Radius for dip-x
smoother. < 40 will have no effect. Use of this parameter with poor quality data is dangerous.
Weight for dip-y constraint equations

Time zones follow structure. Set to zero if Radius for dip-y smoother. < 1.0. Use of this parameter with
poor quality data is dangerous.
Radius for dip-y smoother (bins)

Low fold. This is in CMPs / MBINs or MLINs. If the defaults are used in RESID1, Radius for dip-y
smoother. < 40 will have no effect. Use of this parameter with poor quality data is dangerous.
NOTE: At least one of the following two parameters must be set to Yes.
Solve for shot statics?

Required if Data type = Converted wave data or Expert mode. The normal processing flow for
converted wave data is to apply the shot statics derived from P wave data and zero geophone statics to the
converted wave data prior to RESID1. This parameter allows the user to prevent new shot statics from
being computed.
Solve for geophone statics?

Required if Data type = Converted wave data or Expert mode. This parameter allows the user to prevent
new geophone statics from being computed.
Solve for RNMO?

Required if Data type = Converted wave data or Expert mode. This parameter allows the user to shut off
RNMO calculations. This may be desirable for converted wave data.
1054
Solve for dip?

Required if Data type = Converted wave data or Expert mode. This parameter allows the user to shut off
dip calculations. This may be desirable for converted wave data.
1055
RESMERGE
Module Description
Input Channels
Output Channels
Parameters
Module Description
RESMERGE reads output files from two RESID1 runs and merges them. The output can either be input to
RESID2 or another RESMERGE to combine another RESID1 run. The normal reason to use RESMERGE
is for the case where the data is too large to run as a single pass through RESID1. Due to statistical
differences the static solution from two runs of RESID1 combined with RESMERGE will not exactly
match a single run of RESID1. The solution should be close. Some overlap of the RESID1 runs may help
reduce the differences.
Note that the data type RAS1 is rather generic and is used by several modules. RAS1 datasets from a
module other than RESID1 will not work. In addition, the parameters used by the different RESID1
modules should be the same. If the number of time zones, sample intervals, number of samples, number of
bins or lines for each RNMO or dip unknown or the maximum correlation shifts differ, RESMERGE will
abort.
Input Channels
1. Equation File 1: Required connection from dataset RAS1 data type.
2. Equation File 2: Required connection from dataset RAS1 data type.
Output Channels
1. Equation File Out: Required connection to dataset RAS1 data type.
Parameters
None
1056
RFMT
Module Description
Input Channels
Output Channels
Parameters
Module Description
RFMT will convert SEG-D and other trace sequential formats to the internal GCI format. SEG-D supports
the new revision 1 and 2 as described in the Digital Tape Standards. A new option is loading SEG-D disk
images.
For SEG-D, RFMT can handle the following formats:
1.
2.
3.
4.
5.
6.
20 bit binary demultiplexed (8015)

16 bit quaternary demultiplexed (8024)
8 bit hexadecimal demultiplexed (8042)
32 bit IEEE demultiplexed (8058)
For SEG-D revision 1.00 tapes, the RFMT module will print out a message indicating that is detected a
revision 1.00 tape. RFMT will also set the following information into the trace headers if they are
available in the SEG-D headers for geometry extraction::
1.
2.
3.
4.
5.
RSBN: Receiver bin number

RSLN: Receiver line number
SSBN: Source station bin number
SSLN: Source station line number
FSPN: Field shot-point number
The SEG-D option will now read disk images. Two disk image formats are supported: Image of original
record, or Using Kelman index file.
The Kelman index file method, will read the SEG-D data stored in the Kelman archive format. This
involves reading two files, the SEG-D disk image and the Kelman index file. The Kelman index file must
have the same name as the SEG-D disk image file with a .index at the end of the file name. The index file
must also reside in the same directory as the SEG-D disk image.
The Image of original record will read an exact duplicate as to what was originally on tape. Each tape
block must be written to the disk image exactly. This method uses block descriptions in the SEG-D header
to determine the length of the SEG-D headers.
1057
When reading disk images, an alternate method can be used to read multiple disk files. If this option is
chosen, then the disk file attached to the RFMT module is basically ignored and the files are read from a
matrix that the user has specified. Be aware though, that the disk file icon must still be attached to the
RFMT icon, it is just ignored.
Input Channels
1. Input : Required RFMT data type.
Output Channels
Parameters
Input format
Select either SEG-D or other. Other can be defined as any format.
Options: SEG-D, Other
Tape or disk
Select if this is a tape or a disk image for SEG-D format only.
Options: Tape, Disk
SEG-D disk format

Select to read an original tape image or to use the Kelman index file. The original record method must be
an exact copy of the tape. Also the block header information must be correct to determine the header size.
If the Using Kelman index file method is chosen, then the Kelman index file must reside in the same
directory as the SEG-D disk image. The Kelman index file must have the same name as the SEG-D disk
image but with a .index attached at the end of the name.
Options: Image of original record, Using Kelman index file
Alternate file import method using a matrix?

If the alternate import method is chosen, then the next three parameters as specified below are used to
input multiple disk images into the module. The typical way to select a file is to use the disk icon attached
to the RFMT module. If you use the alternate method, the disk icon must still be attached but it is ignored
and these three parameters are used to get the file names to load.
1058
Starting file path

If multiple datasets are to be input and the datasets have a constant part of the path, this parameter can be
used to supply it so the matrix only needs the variable part. If this parameter stops at a directory, a trailing
"/" is required.
File list
Enter multiple files names into the matrix rows. You are allowed an unlimited number of file names.
These three parameters must provide the exact path to the files.
Matrix Type: FILES
Extension to input files

IF the datasets have a common file extension, this parameter can be used to supply it.
For example:
Starting file path = /mnt/gz7/SEASCAN/
File list matrix containing:
Fred
Barney
Extension to input files = .segd
is exactly equivalent to
Starting file path =
File list matrix containing:
/mnt/gz7/SEASCAN/Fred.segd
/mnt/gz7/SEASCAN/Barney.segd
Extension to input files =
SEG-D type
Select the SEG-D format type. The Sercel 358 has a different method to apply the MP factor. If the data
was recorded from a Sercel 358, select this type to convert the amplitudes to millivolts properly. Select the
VISION System format to enable geometry extraction from that format
Options: Standard SEG-D, Sercel 358, VISION
Apply MP (descale multiplier)

Select "Yes" to apply the MP or descale multiplier in the SEG-D channel set descriptor. This option
should be used if the K-Gain in the acquisition system is changed while recording the data.
1059
Renumber live channels?

Selecting "Yes" will result in renumbering the channel number for live traces only. The channel number
for non-live traces will not be affected.
Number of extra bytes in the general header

In standard SEG-D, a 32 byte general header is followed by a series of channel set descriptors. The author
has seen non-standard SEG-D formats where additional bytes where added onto the end of the general
header. If you receive the wrong number of channels, this might be the case. A good guide to find the
extra bytes is to search for x0101 in the hexadecimal dump of the header after byte 32. The digits
x0101 usually indicate the scan type header and channel set within the first channel set descriptor. So
simply subtract 33 from the byte position of x0101 for this parameter.
Header definitions from main header

This spreadsheet will define GCI trace headers to fill from data in the SEG-D master header.
Matrix Type: RFMTSEGD
Header definitions from trace header

This spreadsheet will define GCI trace headers to fill from data in the SEG-D trace header.
Matrix Type: RFMTSEGD
Header definition bytes, offset from channels?

For data sets that have a variable number of channels per shot, header definitions usually are not at a fixed
byte location for each shot but are usually at a fixed byte location relative to the end of the channel set
descriptors. Select "Yes" to interpret the starting byte location in the header definitions to be offset from
the last channel set descriptor plus any skew data.
Length of trace to output (ms.)

On default, the module will compute the length of trace to output from the first valid record. This option
allows you to set another length of trace in milliseconds.
Maximum number of traces per ensemble

On default, the module will compute the maximum number of traces per ensemble from the first valid
record. This option allows you to set your own maximum number of traces per ensemble. An example use
might be: The first few records on tape are test with fewer channels than normal data recording. You can
force more channels to be input here.
1060
Print file and channel set information

When set to Yes print to the execution log the file format code and number of channel sets for each file, as
well as the number of channels, channel type, and start/end times for each channel set.
Maximum number of K-bytes per record on tape

If the input SEG-D tape is blocked, the possibility exists that the acquisition contractor could create long
block records that are greater than the standard 64K SCSI block size. If this happens you will probably get
the following error:
Dropping a block from OIDN ### that does not contain an evenly divisible number of traces in it. Read
65536 bytes, expected ### bytes per trace
If you get the the above error, run the module TDUMP and change the maximum number of K-bytes
parameter to larger numbers to find the proper number to enter for this parameter.
Input sort order

When selecting the sort order, the primary and secondary key must be defined in the header definition
matrix below. If the the ensemble header is not defined, it will be renumbered starting from one. For
example, If for shot ordered data the OIDN must be defined and if FCSN is not defined it will be
renumbered.
Options: Shot, Geophone, Offset, CMP gather, Stack, 3-D X-bin
gather, 3-D Y-line gather, 3-D X-bin stack, 3-D Y-line stack, Other
Index to primary header word

Enter only when selecting "Other" above.
Index to secondary header word

Index to ensemble header word


This will appear when the other format option is chosen. You must enter a value here which should be the
number of traces in the largest ensemble that will be encountered.
1061
# EOFs to skip at start of first tape

# of records to skip at start of first tape
# EOFs to skip on subsequent tapes
# records to skip on subsequent tapes
# consecutive EOFs for end of tape information
Sample rate (microseconds)
Record length (milliseconds)
Detached header for each ensemble?
By selecting "Yes" a header will be expected after the skipped records specified above. RFMT will
assume it reads another header when it reads a record of the same byte length as the first one read.
Number of bytes in attached trace header

# of bytes of header which overwrite seismic samples
Seismic sample type
Options: sign magnitude integer, 1s complement integer, 2s
complement integer, IBM floating point, IEEE floating point
Number of bytes per sample

This can be specified only for integer seismic sample types.
Header definitions
Matrix Type: RFMT
Starting id
The starting and ending id will use the secondary key value. For shot ordered data, this will be the OIDN.
For SEG-D this id will will be used to determine the maximum number of samples per trace, the sample
rate, and the maximum number of traces per ensemble for the entire data set.
1062
Ending id
ProMax internal data format?
To be honest the author is not certain this is ProMaxs internal format. The data we received was presented
as such but the format description did not say so and was riddled with typos. It might also be a
nonstandard archive format as it appears to include a checksum. The input is from disk and the SEG-D
disk format is Image of original record.
If you are having trouble reading the data, use the Unix od command or your favorite hex editor to dump
the first part of the dataset in hex format. If the first couple of words are 7ff700ff a5a50d0a try using this
parameter.
1063
RFS1
Module Description
Input Channels
Output Channels
Parameters
Module Description
RFS1 will pick first breaks (refractions) using a predicted time and an automated picker. The predicted
time can be computed from guide picks or a refraction model. For best results input picks should be every
2 to 5 shots. The automated picker uses a stabilized power ratio algorithm.
The first break is the first recorded signal attributed to energy generated by the seismic source. First breaks
are normally used for determining a near surface statics model.
RFS1 will perform the following:
Compute a predicted pick time using a guide pick or refraction model. The guide picks or refraction
model are designed using the DISPLAY module.
Optionally after a predicted pick time is computed, RFS1 will search for the maximum energy within
a window using a stabilized power ratio algorithm. A smoothing filter can optionally be applied to the
picks to bring poor picks into alignment.
Picks can be shifted down to the nearest peak or trough. A bandpass filter can optionally be applied to
trace before the shift to get rid of noise before the shift.
An option to replace bad picks with a statistically computed values. For a RSLN, a least square
algorithm is run over a user specify number of points. If a pick is more than 2 times the standard
deviation away from a best-fit line, then the pick is replaced with a value that falls on the best-fit line.
In a typical work sequence, the user will run the picker over a short range of shots. The critical parameter
to adjust is the stabilizer. If the algorithm is picking low, then decrease the stabilizer. If the algorithm is
performing, false picks then increase the stabilizer. Be aware that adjusting the pick to a peak or trough
might cause some picks to cycle skip (move to higher or lower peak/trough than intended). It is a good
idea to start with "NONE" for the adjustment. The automatic first break picker uses an algorithm known as
the stabilized power ratio. The algorithm uses the ratio of the power in a leading gate to the power in a
trailing gate. This value is typically at a maximum when the trailing gate is in the pre-first break noise and
the leading gate is in the first break signal.
To calculate a rough estimate of how to lay the window on the data refraction model or guide picks needs
to be designed. By default the refraction model is calculated using a single average refraction velocity.
Alternatively the user can input a refraction model via a matrix. This refraction model can be picked in the
DISPLAY module.
1064
The DISPLAY module also is used to build the guide picks needed to operate this module. Guide picks
should be performed at a regular interval through out the survey. If there is much variation in the refracted
layer depth then guide picks may have to be performed more often.
The width of the refraction energy envelope is the length of the complete refraction train. The refraction
train can be seen on the shot as low period, high amplitude values. A typically refraction train might be
120 ms. to 500 ms or greater in length. The program uses the envelope width and the window pick to
determine the search area on the trace. Make sure these values are large enough so that the search
algorithm can see the complete refraction train.
One problem with this type of algorithm is the occurrence of false picks in the pre-first break noise due to
short duration pulses such as footsteps or wind gusts. To avoid the false picks, the power ratio is stabilized
by adding a percentage of the power of the entire trace to the power in the trailing gate. A zero
stabilization factor results in no stabilization being applied. The suggested range for the stabilize factor is
0 to 50 percent. Higher stabilization factors (>50%) may result in late picks, while low stabilization factors
(0%) may result in false picks. Increasing the stabilizer tends to move the picks down into the refraction
train.
A least squares filter can optionally be applied to the picks. The filter can only be applied to dataset that
have the RSLN value assigned. After all picks for a shot are performed, the filter will be applied to the
picks. The user has the option to set the number of traces that the filter uses to determine the least squares
best-fit line. A best-fit line is computed over a user specified set of points. The perpendicular offset from
the best-fit line is computed for each pick. If the a pick is offset more than 2 times the standard deviation,
then this pick is considered bad and a replacement is computed. The replacement pick is computed on the
best-fit line.
After picking and filtering, the program can optionally adjust the pick up or down to the nearest peak or
trough. A bandpass filter can optionally be applied to the trace before making the shift. This will help in
areas of noisy data, where the picks are poor. The filter can get rid of the high and low frequencies and get
a better pick on the refractor.
You may supply gates to limit the trace segment where the automatic picker does the analysis. The gates
are determined by the refractor velocity, the window picks, and the initial picks. The initial picks are
entered by the user using the DISPLAY module. You need to perform initial picks over a subset of the
entire survey, typically every 5 to 10 shots.
Setting the parameters is a trail and error process. A place to start on any given dataset is to set:
envelope = 300 ms, window pick = 200 ms, stabilize = 10 %, modify = none
Look at the picks on the data using the DISPLAY module. The critical parameter to change is the
stabilizer. If the picks are delayed then decrease stabilizer, if picks are false then increase stabilizer. Look
at length of refraction train, is the envelope long enough. If the refractor surface is changing dramatically
over survey, you may have to increase window length. When the picks are close to how you like them,
then use modify to snap pick to a peak or a trough. Be aware that adjusting the pick to a peak or trough
will sometimes cause the picks to cycle skip.
1065
1066
Input Channels
Output Channels
2. Dataset for rfs2: Optional connection to dataset RFS1 data type.
Parameters
Method to predict initial pick
The module computes a predicted time to input for a trace into the automatic picker. The pick is then
computed within the pick window with the predicted time at the center of the window. There are three
methods to determine the predicted time: initial picks, refractor model, or refractor velocity. The guide
picks and refractor model are designed in the DISPLAY module.
Options: Guide Picks, Refractor Model, Refractor Velocity
1067
Initial guide picks

Enter the matrix file that contains the initial picks that were performed using DISPLAY module.
Matrix Type: AFS1B
Limit predicted time computation to the same RSLN?

This parameter limits the initial picks to the same RSLN as the trace that is currently being picked. If this
is set to no then all traces for a ensemble are used to compute the predicted time. If it is set to yes, then
only the traces with the same RSLN are used to compute the predicted time.
Refractor model
Optionally enter the matrix file that contains the refractor model that were performed using the DISPLAY
module. The default (calculated) is to compute the refractor model using the refractor velocity. In this case
only a velocity is input and not a refractor model matrix. This parameter is used to compute the initial
predicted first break pick.
Matrix Type: RMOD
Refractor velocity
Enter the average refractor velocity in feet/sec or meters/sec. Please use the DISPLAY module to select
this value when building the original guide picks. The picker uses this velocity to roughly align the
window on the data.
Output picks
This matrix holds the computed refractor picks.
Matrix Type: AFS1B
Search for maximum energy?

Select YES to use the automatic picker. If NO is selected then the automatic picker is not used and the
pick is just adjusted to a peak or trough. If you want RFS1 to use the picking algorithm, then this
parameter must be "YES".
First break energy envelope width (ms)

Enter the average width of the energy envelope in milliseconds of a typical first break signal. The energy
envelope can also be called the refraction train. A typical refraction train is 120 ms. to 500 ms in length.
1068
Power ratio stabilization factor

Enter a percentage of the power of the entire trace to add to the trailing window. This factor will help
stabilize the leading-to-trailing power ratio. The suggested range is 0% to 40%. This parameter is the most
critical value to change when attempting to get the picker to work properly. If the pick is lower in time
than intended, then decrease the stabilizer. If there are many false picks, then increase the stabilizer.
Pick window (ms.)

Enter the length of the pick window in milliseconds. The first break pick should reside within this
window. The leading and trailing window envelope entered above is added to this value. This determines
the analysis window for automatic first break picking.
Re-compute bad picks?

Select this option to locate bad picks by applying a least squares filter to the data. Least squares statistics
is performed on each pick using the surrounding user specified number of picks from the same RSLN. If
the standard deviation of the pick is 2 time greater than the surrounding picks, then this pick is recomputed
using the best-fit line that was computed for the least squares routine.
Filter length (traces)

Enter the length in samples to perform the least squares filtering.
Shift pick to nearest

Select to move the first break pick to the nearest pick or trough. This might cause some picks to cycle skip
( move to peak/trough that is lower/higher than intended ). It is a good idea to start with NONE to see how
the data looks and then run the module again with the adjustment.
Options: Trough, Peak, None
Apply bandpass filter before shifting?

A bandpass filter can optionally be applied to the trace before attempting to pick down to the nearest peak
or trough. This might be helpful on traces with noise, where the picks are poor.

Select the low cut frequency in hertz.
1069

Select the low pass frequency in hertz.

Select the high pass frequency in hertz.

Select the high cut frequency in hertz.
Number of channels per shot
1070
RLIV
Module Description
Input Channels
Output Channels
Parameters
Module Description
RLIV performs a linear moveout correction to a seismic trace. The time correction is a function of the
source-receiver offset distance (header word 12), the specified velocity and the specified additive time:
Delta time = Time to place removed data
Offset
------------Velocity(azim)
When restoring linear moveout, the sign of Delta time is reversed. The correctional velocity may be a
constant value or spatially variable, either 2D (using only the Secondary Header Word) or 3D (using both
Primary and Secondary words). The moveout velocity may alternately be taken from a trace header. The
latter is particularly useful when restoring linear moveout since RLIV stores the moveout velocity in
header 78 (VELO).
The correctional velocity and additive time are normally made available to other modules (Preprocessor
Communication). DISPLAY uses these values to present the data as if the linear moveout was performed
within DISPLAY. This function may be turned off.
Input Channels
Output Channels
Parameters
Linear moveout option
Options: Remove, Restore
1071
Azimuth variable velocity

Options: YES, NO
Vslow azimuth
Azimuth of the slow principle propagation axis.
Vslow
The slow velocity used for linear moveout correction.
Vfast
The fast velocity used for linear moveout correction.
Velocity Source
Options: Constant, Variable, Header(VELO)
Linear velocity
Required if Velocity Source = Constant.
Depth exponent "n"

Required if Velocity Source = Constant.
Primary Header Word

Required if Velocity Source = Variable.
The value contained in this header word will be used to interpolate the velocity by the first (and second)
vectors in the matrix (3D interpolation). NOTE: If "none" is selected, the interpolation will be 2
dimensional only according to the second vector and header word value.
TLSN, other
Header ID Index for Primary Header

Required if Primary Header Word equal other.
1072
Secondary Header Word

TLSN, other
Header ID Index for Secondary Header

Required if Secondary Header Word equal other.
Velocity Matrix Type

This matrix defines the spatially variable linear moveout correction velocities to use.
Options: LMOVEL, RMSVEL
LMOVEL Matrix Name

Matrix Type: LMOVEL
RMSVEL Matrix Name

Matrix Type: RMSVEL
Time to place removed data (ms.)

The same time used when removing linear velocity should be used when restoring linear velocity to
position the data at the original time.
Extend record length for removed data?

When removing linear velocity and the time to place the data is greater than zero, then by selecting "Yes"
the record length will be extended to prevent loss of data. Selecting this option when restoring linear
velocity will result in a reduction of the record length.
Use absolute value of offset

Compute static shift using signed or unsigned source/receiver offset.
1073
Set Preprocessor Communication?

Options: YES, NO
1074
RMHDR
Module Description
Input Channels
Output Channels
Parameters
Module Description
The RMHDR module is used to remove selected extended GCI trace headers. The standard GCI trace
header is comprised of 87 32-bit header fields. This module can be used to remove any number of fields as
long as it is not the original 87 32-bit header fields. The module is parameterized in a Header Extension
Matrix in which each row defines a field to be deleted. A field is defined by a field name and a type. The
default type is integer.
Known Issues
Using the READ module to read in multiple datasets with extended headers will fail when attempting
to open the second dataset.
Use this module to remove extended headers from a dataset.
Input Channels
Output Channels
Parameters
Header Extension Matrix
Matrix Type: GCIHDREXT
This is the matrix used to delete header fields. Each row of the matrix defines a field to be deleted, and a
field is defined by a name and a type. The type may be either integer or floating point, integer being the
default. Typically, a user will use the same matrix as the one used by the ADDHDR module.
1075
RNDCLN
Module Description
Input Channels
Output Channels
Parameters
Module Description
RNDCLN reduces the random noise content of the input traces. Any ensemble may be input, however,
depending upon the dataset, pre-stack NMO corrected shots, offset bins, or other combinations usually
produce a better stack. For strong cleanup use a small Cleanup strength. If the cleanup strength is set too
high, the data prediction may become unstable.
Input Channels
Output Channels
Parameters
Output
RNDCLN inputs an ensemble of traces with random noise and outputs the ensemble with the random
noise reduced.
Gate width (ms)

Samples in a time gate are used to estimate random noise in the trace. Use short gates on dipping data (200
ms) and longer gates on flat data (500ms or more).
Cleanup strength (inverse)

A small value (10 or less) cleans the data more than a larger value (50 or more). Different values will be
required for different gate widths.
1076
Number of threads
RNDCLN will run in parallel across many CPUs on the host machine. Unless the host has a single CPU,
using more (4 or more) will decrease processing time.
1077
ROTATE
Module Description
Input Channels
Output Channels
Parameters
Module Description
The module ROTATE is used to rotate the multicomponent data set by a fixed angle, or rotate each trace
by an angle estimated by FRACDET or smoothed values of angles generated by SMTHANG. This module
can be used on pre-stack or post-stack seismic data. For pre-stack data, the data rotation can be performed
within a range of offsets. The way this module is operated is similar to FRACDET.
Input Channels
1. input radial horizontal component: Required connection from dataset GCI data type.
2. input transversal horizontal component: Required connection from dataset GCI data type.
Output Channels
1. output radial horizontal component: Required connection to dataset GCI data type.
2. output transversal horizontal component: Required connection to dataset GCI data type.
Parameters
Rotate:
Options: Pre-stack data, Post-stack data
Rotate data set using:

Options: A fixed angle, A particular angle for each trace
Rotation angle:
1078
Rotation angle attribute name

Minimum Offset
Maximum Offset
Number of shots
Number of channels
1079
ROTATE2C
ROTATE2c - Applies initial geophone rotation to 3D3C data.
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module ROTATE2C mathematically rotates horizontal geophone trace pairs from the H1, H2 reference
frame to the Radial, Transverse reference frame. Both geophones in each trace pair occupy the same
surface location. Both components in each reference frame are orthogonal. The process is usually one of
the first performed in P-Sv data processing.
Normal 2D converted wave (P-Sv) field data exhibit a polarity reversal from one side of the shot to the
other. For a SeisUP data set, this corresponds to comparing traces with positive to those with negative
shot/receiver offset distances. This apparent polarity reversal can be understood by observing the response
of a horizontal geophone with its axis of motion parallel to the receiver line. The initial motion of the coil
of this geophone will be in opposite directions for shots located up the line and shots located down the line
from the geophone. By reversing the polarity of traces with negative offset distances, we ensure that all
receivers will be responding in the same sense to energy from any given shot. Polarity reversal is identical
to a 180 degree spatial rotation of the geophone.
The general principle is the same for 3D P-Sv data. However, the rotation angle may assume any value
between -180 and +180 degrees.
ROTATE2C observes the proposed SEG standard for multi-component data defined by Landrum, et al.
The standard defines the recording coordinate system as right handed with the positive Z axis pointing
down into the earth. The H1 horizontal geophone direction of motion defines the X axis. The H2 geophone
defines the Y axis. The convention defines the H1 geophone, or X axis geophone, as parallel to the
receiver line orientation in the direction of increasing station number, or line progression. This direction
and the right handed convention define the orientation of the H2 geophone. This configuration is
represented in Figure 1, below, for receiver lines oriented to the north.
ROTATE2C uses GCI header word 82, AZIM, and the H1 azimuth angle to rotate the trace pairs.
STATION and GEOM compute AZIM and place it in the trace headers. ROTATE2C rotates like trace
pairs through the angle from the coded receiver line azimuth to 180 - AZIM. If STATION and GEOM
have been run, the azimuth angle coded represents the direction of the H1 geophone in the SeisUP
orientation convention. SeisUP defines East as 0 degrees with positive azimuth angles to the north and
negative angles to the south. Thus a north oriented H1 geophone after GEOM would require coding
azimuth 90 degrees. ROTATE2C accepts only one azimuth angle. This implies all geophones must be
oriented identically on the ground.
1080
Rotation is performed in two steps; rotation through the acute angle and polarity reversal. ROTATE2C
first rotates each trace pair through the acute, or smaller, angle defined between AZIM and the geophone
line azimuth (H1). The second step is accomplished by reversing the polarity of all trace pairs with
positive AZIM values. SeisUP defines AZIM as the angle between a vector from the shot to the receiver
and the X axis. The vectors root, or shot end, is on the X axis.
For example, consider a geophone pair whose AZIM is 50 degrees, as approximated in Figure 1. The
receiver line azimuth is 90 degrees, or north in SeisUP convention. This receiver pair will be rotated -50
degrees. This points the radial component away from the source. Total rotation for the pair should be +130
degrees to point at the source. In this case, the initial rotation leaves the trace pair mis-aligned by 180
degrees. Reversing the polarity of this pair is identical to a 180 degree spatial rotation. Figure 2 represents
the first step in rotation.
1081
Figure 1
1082
Figure 2
References
Aki, K. and Richards, P.G., 1980, Quantitative methods in applied seismology.
Lane, M., Lawton D. 3-D converted wave asymptotic binning. CREWES Research Report. Volume 5
(1993)
Cary, P. 3D converted wave seismic processing. CREWES Research Report Volume 6 (1994)
Landrum, R. A., Brook, R. A., and Sallas, J. J., 1994, Polarity convention for vibratory
source/recording systems: Geophysics, 59, 315-322.
Pruett, R., 1987, Acquisition, processing, and display conventions for multi-component seismic data:
Soc. Expl. Geophys. Technical Standars Committee Report (Subcommittee on 3-C Orientation).
Sheriff, R. E., 1984, 2nd ed., Encyclopedic dictionary of exploration geophysics: Soc. Expl. Geophys.
Brown, R.J., Towards a polarity standard for multicomponent seafloor seismic data SEG 2000
Expanded Abstracts
1083
Input Channels
Output Channels
Parameters
TLSN, other

Required if Header Containing Component ID equals other.
H1 Component ID
Header word contents defining H1 traces.
H2 Component ID
Header word contents defining H2 traces.
Type of Rotation
Options: Radial-Transverse, Fixed Angle, Angle from Header, Angle
from Matrix
The "Angle from Matrix" option has not been implemented.
Angle to rotate all traces

Required if Type of Rotation equals Fixed angle.
1084
Header Containing Rotation Angle

Required if Type of Rotation equals Angle from Header.
TLSN, other
Header ID Index for Rotation Angle

Required if Header Containing Rotation Angle equals other.
Survey Azimuth Source

Required if Type of Rotation equals Radial-Transverse.
Options: Constant Angle, Header Word
Survey Azimuth (Compass Heading MINUS 90 Degrees)

Required if Survey Azimuth Source equals Constant Angle.
Header Containing Azimuth

Required if Survey Azimuth Source equals Header Word.
TLSN, other
Header ID Index for Azimuth

Required if Header Containing Azimuth equals other.
1085
ROTATE4C
ROTATE4C - Applies source and geophone rotation to 4C data.
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module ROTATE4C mathematically rotates horizontal source and geophone trace groups between the
H1/H2 field recording reference frame and the Radial/Transverse or an arbitrary constant azimuth
reference frame. Both geophones in each trace group and both sources in the group are assumed to occupy
the same surface locations respectively. Both source and both receiver components in each reference
frame are orthogonal.
Each input and output group will have 4 traces; one from each of 2 receivers for each of 2 sources. Each
pair of sources and receivers is orthogonal with a right handed sense. In vector notation H1 X H2 = H3.
H3 would be a vertical axis source or receiver. A portion of a common land acquisition scheme might look
like Figure 1. The notation used to define a given traces components is HX(source)/HX(receiver). The
convention on output puts H1 components in the respective line direction. Accordingly RR is equivalent to
H1H1 after radial/transverse rotation.
1086
Figure 1
Performing a rotation from field orientation to a radial/transverse reference frame gives the component
orientations in Figures 2 and 3. The figures show the same rotation for 2 different receivers from the same
source location.
Figure 2
1087
Figure 3
Note that the azimuth angles entered as parameters for source and receiver are compass headings. That is
north is zero degrees with angles increasing clockwise and decreasing counterclockwise. All other angles
are in SeisUP internal coordinates which correspond to standard Cartesian coordinates. East is zero
degrees with angles increasing counterclockwise.The parameters that might have produced the rotated data
in Figures 2 and 3 are shown in Figure 4.
Figure 4
The validation headers are used to ensure that traces found belong together. Errors are printed when this
validation fails or a component is missing from a given group. Validation headers need not be used.
The process may be threaded to speed execution.
The input data order is critical to proper execution. Traces must be grouped with like traces adjacent in the
input ensemble. There may be multiple groups within each ensemble. The example above was read using
FSPN as Primary Key, RSLN as Secondary Key and SGEN as the Ensemble Key. This ensured that traces
with common FSPN and SGEN were grouped together in the input data stream.
An example of an Alford or constant angle rotation, is shown in Figure 5. The input data are those shown
in Figure 1. The parameters are shown in Figure 6.
1088
Figure 5
Figure 6
1089
References
Aki, K. and Richards, P.G., 1980, Quantitative methods in applied seismology.
Landrum, R. A., Brook, R. A., and Sallas, J. J., 1994, Polarity convention for vibratory
source/recording systems: Geophysics, 59, 315-322.
Pruett, R., 1987, Acquisition, processing, and display conventions for multi-component seismic data:
Soc. Expl. Geophys. Technical Standards Committee Report (Subcommittee on 3-C Orientation).
Sheriff, R. E., 1984, 2nd ed., Encyclopedic dictionary of exploration geophysics: Soc. Expl. Geophys.
Brown, R.J., Towards a polarity standard for multicomponent seafloor seismic data SEG 2000
Expanded Abstracts
Input Channels
Output Channels
Parameters
TLSN, other

Required if Header Containing Component ID equals other.
H1/H1 Component ID
Header word contents defining H1/H1 traces.
H1/H2 Component ID
1090
H2/H1 Component ID
H2/H2 Component ID
Type of Rotation
Options: Alford one angle, Alford header-defined angle,
Radial-Transverse
Angle to rotate all traces

Required if Type of Rotation equals Alford one angle.
Header Containing Rotation Angle

Required if Type of Rotation equals Alford header-defined angle.
TLSN, other
Header ID Index for Rotation Angle

Required if Header Containing Rotation Angle equals other.
Survey Azimuth Source

Options: Constant Angle, Header Word
Receiver H1 Azimuth Compass Heading

Source H1 Azimuth Compass Heading

1091
Header Containing Source Azimuth

TLSN, other
Header ID Index for Source Azimuth

Required if Header Containing Source Azimuth equals other.
Header Containing Receiver Azimuth

TLSN, other
Header ID Index for Receiver Azimuth

Required if Header Containing Source Azimuth equals other.
Validation Header 1
TLSN, other
Header ID Index for Validation Header 1

Required if Validation Header 1 equals other.
Validation Header 2
TLSN, other

Required if Validation Header 2 equals other.
1092
Rotate
Options: Source and Receiver, Source Only, Receiver Only
Forward or Reverse Rotation

Options: Forward Rotation, Reverse Rotation

Ensembles contain multiple rotation groups
Options: YES, NO
1093
RSIM
Module Description
Input Channels
Output Channels
Parameters
Module Description
RSIM simulates an extended field array by mixing traces from the same shot with adjacent geophone
positions. The mixing is always symmetrical in terms of trace distribution, but the weights do not have to
be symmetrical. The number of weights needs to be odd to keep symmetry.
The simulated trace is scaled by the sum of the weights of contributing traces.
Input Channels
Output Channels
Parameters
Weights
Matrix Type: WEIGHTS
1094
RT3D
Module Description
Parameters
Module Description
RT3D will report receiver and midpoint grid information from the geometry database. RT3D prints the
following information for each shot matrix after translation and rotation has been performed:
LINE
MIN.
MAX.
MIN.
MAX.
MIN.
MAX.
MIN.
MAX.
#
#
X-COORD
X-COORD
Y-COORD
Y-COORD
X-BIN
X-BIN
Y-LINE
Y-LINE
X-BIN
Y-LINE
:Shot matrix name

:Minimum X coordinate
:Maximum X coordinate
:Minimum Y coordinate
:Maximum Y coordinate
:Minimum bin number
:Maximum bin number
:Minimum line number
:Maximum line number
:Number of bins (MAX-MIN)
:Number of lines (MAX-MIN)
(if
(if
(if
(if
(if
(if
STATION
STATION
STATION
STATION
STATION
STATION
run)
run)
run)
run)
run)
run)
RT3D will also print any calculated defaults as defined in STATION such as the origin and the number of
bins and lines.
Parameters
Print receiver grid information?
Print midpoint grid information?
Print source/rec. on midpoint grid information?
This option will scan the geometry database and report midpoint information from the source and receiver
coordinates, not the midpoint coordinates. This will allow the user to determine 3-D DMO parameters
such as the span size or which line to perform a restart on. The reason this may used for DMO is because
the DMO process is performed from the source to the receiver on the midpoint grid.
1095
RWSUM
Module Description
Input Channels
Output Channels
Parameters
Module Description
Input Channels
Output Channels
Parameters
Use the absolute value?
# points in running window filter
1096
RZERO
Module Description
Input Channels
Output Channels
Parameters
Module Description
RZERO will set the TRID header word to 2 (dead) on any trace where the Maximum % of zeros allowed is
exceeded.
Input Channels
Output Channels
Parameters
Maximum % of zeros allowed
1097
SCALE
Module Description
Input Channels
Output Channels
Parameters
Module Description
SCALE is a process for applying time-variant trace scaling or equalization. Types available are:
Absolute value mean trace equalization
Root mean square trace equalization
Constant scaling of trace
DB per second scaling of trace
Header option for scaling trace amplitude by headers
Time variant DB scaling of trace
A window matrix specifies the start and end time of time windows over which to compute the equalization
type specified. Application defaults to "center time" of window but may be biased by the user to another
time within the window. The scale constant default is 2500 for AVM and RMS, but may be altered by the
user. In the "constant scaling" option only times and integer multiplier scalars are required.
Application can be time-adjusted by TIM1 or TIM2 in program HORIZON. Primary and secondary header
keys are used in a multi-dimensional matrix for adjusting windows. Windows may also be adjusted in a
space-variant matrix which defaults to "no adders".
Input Channels
Output Channels
Parameters
1098
Scale type
Options: Absolute value mean, Root-mean-square, Constant scaling,
DB/sec., Header, T.V. DB
Windows
Required if Scale type: = Absolute value mean or Root-mean-square.
Matrix Type: SCLWIN
Scalars
Required if Scale type: = Constant scaling.
Matrix Type: SCLSCL
DB per second to apply

Required if Scale type: = DB/sec..
DB Scalars
Required if Scale type: = T.V. DB scaling.
Matrix Type: SCLDB
Pre-suppression level in percent


Required if Scale type: is not Header.
Primary header key

TLSN
1099

TLSN
Space-variant time adders

Scaling mode
Options: Single trace, Ensemble
Apply inverse?
Required if Scale type: = Constant scaling or DB/sec.. Select Yes to apply the inverse of the curve
derived from the scaling.
Operation
Required if Scale type: = Header.
Options: Addition, Subtraction, Multiplication, Division
Header index
Required if Scale type: = Header.
Alpha trimmed mean %

Required if Scaling mode: = Ensemble. This percentage of the outlier values will be rejected before
computing the scale.
1100
SCAT
Module Description
Output Channels
Parameters
Module Description
This program is used to generate the midpoint scatter plot, for 3-D surveys from the input coordinate
database. All lines may be plotted, or a list of lines to include or exclude may be generated. The plot will
be automatically scaled by the program, or the following scales may be chosen:
1:250,000
1: 62,500
1: 50,000
1: 24,000
1: 12,500
A user-specified scale is chosen by selecting "other". The line annotation increment (default 1) may also
be chosen. Output is a CGM file.
Output Channels
1. CGM Output: Connection to CGM disk file
Parameters
Draw lines

Matrix Type: LINES
Plotting scale
Options: auto, 250000, 62500, 50000, 24000, 12500, other
1101
Enter user scale

Line annotation increment
1102
SCDCN1
Module Description
Input Channels
Output Channels
Parameters
Module Description
SCDCN1 computes the logarithm of the amplitude spectrum which is needed by SCDCN2 to decompose
the signal into four components.
Either the entire trace or portion of the trace can be used in the computation. It is recommended that the
entire trace to be used, but when the signature varies with time very strongly, a time window may work
better for the zone of interest.
The user can supply a bandpass filter to SCDCN1, otherwise the entire bandwidth will be used. The filter
will be carried into SCDCN3.
The minimum offset and average offset increment are used to group the offsets into a discrete number of
distinctive groups.
Input Channels
Output Channels
1. Output: Required connection to dataset SCDCN1 data type.
Parameters
Windows for operator derivation?
1103
End design time(ms)

Primary header key
TLSN

TLSN
Windows



Minimum offset
Maximum offset
Average offset increment
1104
Minimum SSPN
Maximum SSPN
Minimum SGEN
Maximum SGEN
Minimum SDPN
Maximum SDPN
1105
SCDCN2
Module Description
Input Channels
Output Channels
Parameters
Module Description
SCDCN2 decomposes the logarithm of the amplitude spectrum of each trace into its source, receiver,
CMP and offset components by using Gauss-Seidel algorithm.
Relative error is used as the means of quality control. A grand average amplitude level is computed over
all the frequencies and all traces. For each iteration, the program computes an average residual, which is
the portion of energy not assigned to any of the four components. The relative error is defined as the
percentage of the average residual over the average amplitude level. The relative error can be used as (1)
an indicator for the proper number of iterations. If the relative error after each iteration only changes on
the order of a fractional percent, no more iterations are necessary; (2) an indicator for surface consistency.
If the amplitude spectra are perfectly surface-consistent, the relative error should be zero. However, many
other components may influence the amplitude and the surface-consistent model is not absolutely valid.
The relative error is usually not zero. It may be quite large, especially, when structural smoothing is
applied to the CMP component. The larger is the relative error, the less surface-consistent is the data set.
Large spikes may cause the SCDCN programs to produce noisy output. Be sure that trace editing modules
are applied before SCDCN programs.
Input Channels
1. Input scdcn1 file: Required connection from dataset SCDCN1 data type.
Output Channels
1. Output scdcn2 file: Required connection to dataset SCDCN2 data type.
Parameters
1106
Relative error tolerance (%)

Maximum iterations
Offset term
Options: Compute & apply, Compute only
CMP term
In-line structural smoothing(bins)

Cross-line structural smoothing(lines)
1107
SCDCN3
Module Description
Input Channels
Output Channels
Parameters
Module Description
SCDCN3 applies the surface-consistent components decomposed by SCDCN2.
Input Channels
2. Input: Required connection from dataset SCDCN2 data type.
Output Channels
Parameters
Restore amplitude?
If yes, the RMS amplitude will be restored to the same level as in input data.
1108
SCDECON1
Module Description
Input Channels
Output Channels
Parameters
Module Description
This program performs the first phase of a six component surface consistent deconvolution. Module
SCDECON2 has to be run to complete the process. SCDECON1 and SCDECON2 use any combination
of line, source, receiver, offset, or CMP components to derive accurate deconvolution filters which are
then applied to the input traces. Surface consistent deconvolution is normally run on shot data. The
deconvolution operators can be band-limited for improved operator stability. The deconvolution operators
can also be converted to zero-phase and an option exists to apply the phase only.
Surface consistent deconvolution is based on the concept that a seismic wavelet can be separated into line,
source, geophone, CMP, and offset components. For land data, typically all five components are used
during the decomposition phase but only the line, source, and geophone are applied during the application
phase. For marine data, the receiver component is not used at all because the geophones are in motion.
However the receiver component might be used in shallow marine conditions due to variable water bottom
depths. The components used for decomposition phase and application phase will be data dependent, so
the user might want to experiment.
Phase one of this process (SCDECON1) computes log power spectra of each input trace and stores spectra
in each component. After the entire survey is run through, Gauss-Seidel matrix inversion equations are
used to separate the log spectra into each component. The log spectra are written to a SCDECON1 file.
The file can then be input into phase two (SCDECON2) which builds deconvolution filters using the
components and applies them to the input traces.
Surface consistent deconvolution is normally run on raw shot data. But it can also be applied to any
pre-stack data type. The SC deconvolution should be run before processes that destroy the character and
phase of the wavelet. SC decon quality can be degraded when noise is in the data. In preparation for SC
decon you might want to run a de-spiking routine or other non-invasive noise reduction schemes. Try to
avoid using a bandpass filter before running SC decon because the filter will alter the phase and character
of the wavelet. If you need to filter, you might try an FK filter.
The module can store intermediate information in memory or files. If all the information can be stored in
memory then the module will run faster. The user can specify the amount of memory that the module can
use. If this memory amount is smaller than needed, then the module will store the information in files.
You can select any range of SSPN, SGEN, SDPN, and DIST for performing the deconvolution. Traces
outside the range of these trace headers will not be included in the decon, this includes the decomposition
and application phases. The exception is DIST which will exclude traces during the decon operator design
phase but will extrapolate the offset for all traces during decon application phase.
1109
algorithm. A trace window rejection factor is entered to skip trace windows that are too short. This
prevents the module from using design time windows that contain fewer than an acceptable number of
samples for decon operator design.
Design time windows can be selected so that a portion of the input trace can be used for decon operator
design. You can enter a start/stop time or build a matrix of start/stop times that may vary over the survey.
It is recommended that careful consideration be put on design time window as this will affect the decon
operator design and ultimately the quality of the deconvolution. During the decon application phase the
whole trace length is deconvolved.
Surface consistent deconvolution can accurately estimate the amplitude and phase of the wavelet. When
spiking deconvolution is chosen, an option is provided to perform minimum phase, zero phase, and phase
only deconvolution. The Wiener-Levinson filter used to deconvolve the data is minimum phase, so by
default, if minimum phase is chosen, then a normal deconvolution is performed. You can optionally
phase portion (imaginary part) is computed zero or minimum, depending on the user selected option.
Typically, if the input data is minimum phase, then this filter should be minimum phase. The Inverse band
filter is then convolved with the windowed input trace during the operator design phase of the program.
A new component has been recently added to SCDECON1 and SCDECON2. The component may be any
header word in the GCI format. The header words in the trace header must be valid values or the decon
will not work correctly.
The module allocates memory half-way through the process, when all the traces have been computed.
Sometimes this might abort the job if not enough memory is available. The module will now compute an
estimated amount of memory up front. The user has to specify the number of traces in the dataset. This
will only be a memory estimate allocation. The program will still have to make adjustments half through
the process. But in most cases, the estimate should be close enough.
1110
The module will output into the queue the surface consistent spectrum (amplitude vrs frequency) for each
component. By adding a GCI write or a trace display module below this module will save/view the
components. The components will be separated as stacked type lines with:
Line 1 - line component. There will be zero, one or many components.
Line 2 - source component. See header SSPN for shot number.
Line 3 - geophone component. See header SGEN for geophone number.
Line 4 - CMP component. See header SDPN for CMP number.
Line 5 - offset component. See header DIST for offset value.
1111
Also see the help file for SCDECON2 for more information.
References
Wang, X., Five-component adaptive surface-consistent deconvolution. CSEG National Convention,
Calgary, Canada, 1992.
Cary, P.W. and Lorentz, G.A., 1991, Four-component surface-consistent deconvolution. Geophysics vol.
58. No. 3, March 1993, pg. 383-392.
Cambois, G., 1989, Surface-consistent deconvolution. SEG expanded abstracts, sp4.4.
Levin, S.A., 1989, Surface-consistent deconvolution. Geophysics, vol. 54. No. 9, pg. 1123-1133.
Burg, J.P., 1972, The Relationship Between Maximum Entropy Spectra and Maximum Likelihood
Spectra, Geophysics, Vol. 37, pp 375-376.
1112
Burg, J.P., 1975, Maximum Entropy Spectral Analysis, Ph.D. Thesis, Stanford University.
Input Channels
Output Channels
1. Output: Required connection to dataset SCDECON1 data type.
Parameters
Maximum available memory (MB)?
You may specify the amount of memory to give this module in megabytes. If the memory is exceeded then
the module will store the intermediate information in files. This will slow the program down. If the
memory is not exceeded then the module will store all intermediate information in memory.
Minimum SSPN
Enter the minimum sequential shot number (SSPN) for SCDECON. Shot numbers below this value will
not be included in the decon. The default get from DB will get the smallest SSPN defined in the
database.
Maximum SSPN
Enter the maximum sequential shot number (SSPN) for SCDECON. Shot numbers above this value will
not be included in the decon. The default get from DB will get the largest SSPN defined in the database.
Minimum SGEN
Enter the minimum sequential geophone number (SGEN) for SCDECON. Geophone numbers below this
value will not be included in the decon. The default get from DB will get the smallest SGEN defined in
the database.
Maximum SGEN
Enter the maximum sequential geophone number (SGEN) for SCDECON. Geophone numbers above this
value will not be included in the decon. The default get from DB will get the largest SGEN defined in
the database.
1113
Minimum SDPN
Enter the minimum sequential common midpoint number (SDPN) for SCDECON. CMP numbers below
this value will not be included in the decon. The default get from DB will get the smallest SDPN defined
in the database.
Maximum SDPN
Enter the maximum sequential common midpoint number (SDPN) for SCDECON. CMP numbers above
this value will not be included in the decon. The default get from DB will get the largest SDPN defined
in the database.
Minimum offset
Enter the minimum distance from source to receiver (DIST) for SCDECON. Offsets below this value will
not be included in the decon phase one (SCDECON1) but will be used in phase two (SCDECON2). The
default get from DB will get the smallest DIST defined in the database.
Maximum offset
Enter the maximum distance from source to receiver (DIST) for SCDECON. Offsets above this value will
not be included in the decon phase one (SCDECON1) but will be used in phase two (SCDECON2). The
default get from DB will get the largest DIST defined in the database.
Offset increment (feet or meters)

Choose to use Wiener-Levinson Spiking or Predictive deconvolution. If Predictive is chosen then the gap
parameter must also be entered.
Options: Spiking Deconvolution, Predictive Deconvolution
Decon operator phase option

Required if Type of deconvolution: is Spiking Deconvolution. You can chose to perform minimum phase
decon, which is the default. This option will apply the minimum phase and amplitude of the
Wiener-Levinson filter. The zero-phase option will convert the Wiener-Levinson filter to zero phase and
then apply amplitude and phase. The phase only option will convert the Wiener-Levinson filter to zero
phase and then apply the phase only portion.
1114
Prediction gap (ms)

Enter the Predictive deconvolution gap in milliseconds. Required if Type of deconvolution: is Predictive
Deconvolution.

Enter the length of the deconvolution operator in milliseconds. This length is typically the length of the
wavelet that is to be deconvolved.
Decon operator pre-whitening (%)

Enter the white noise value in percent. The pre-whitening represents the percentage of white noise that is
added to the autocorrelation function in order to stabilize the inverse filter calculation.
of the program.
Filter phase


1115



the Gibbs Effect.
Trace window rejection ratio

Trace window length that fall below the rejection ratio will not be used for decon operator calculation. The
rejection window length is defined as:
trace window reject length = decon oper. length * trace window rejection ratio
320 (ms) = 160 (ms) * 2
Trace window length that are less than the reject window length are skipped. Please select the design
window length explained below carefully. This factor prevents to module from using time gates that are
too short for decon operator design.
Include LINE component in spectral decomposition?

Select YES to include the line component in the spectral decomposition.
Options: 1 line term only, No, Multiple lines
Starting LINE number

Required if Include LINE component in spectral decomposition? equals Multiple lines. NOTE: The
default value comes from the MLIN database entry, if lines are defined using any other header this must
be entered.
Ending LINE number

Required if Include LINE component in spectral decomposition? equals Multiple lines. NOTE: The
default value comes from the MLIN database entry, if lines are defined using any other header this must
be entered.
1116
Line header key

Required if Include LINE component in spectral decomposition? equals Multiple lines. This is the
header that determines what is considered a LINE. For example: If surveys are being merged, set TIM1 to
1 in one dataset and to 2 in the next and use LINE header key: as TIM1.
TLSN, other
Header word number

Required if LINE header key: equals other.
Include SOURCE component in spectral decomposition?

Select YES to include the source component in the spectral decomposition.
Include GEOPHONE component in spectral decomposition?

Select YES to include the geophone component in the spectral decomposition.
Include OFFSET component in spectral decomposition?

Select YES to include the offset component in the spectral decomposition.
Include CMP component in spectral decomposition?

Select YES to include the CMP component in the spectral decomposition.
Include OTHER component in spectral decomposition?

A sixth component may now be computed. The component may be linked to any valid GCI header word.
Minimum OTHER
Maximum OTHER
A maximum value can be specified for this parameter. If the trace header value is greater than this value,
then the trace is skipped for the spectral decomposition.
1117
OTHER header key

A minimum value can be specified for this parameter. If the trace header value is less than this value, then
the trace is skipped for the spectral decomposition.
TLSN, other
Header word number

Enter a valid GCI header word number. See the GCI header word definition link above to select the word
to use.
Number of Gauss-Seidel iterations

Enter the number of Gauss-Seidel iterations to perform. A Gauss-Seidel algorithm is applied to the
spectral sums to separate the information into each component. The Gauss-Seidel technique is iterative, so
several passes must be made for the data to converge.
Design time gates for decon?

Choose the method for decon design time gates. The default method is to enter a start and start time as the
design window. You can also choose to get the design times from a file. The selected window is pulled
from the input trace to use in the decon operator calculation.
Design time gate start(ms)

Enter the start time for decon operator design in milliseconds. The module will use a portion of the input
trace for decon operator design. This parameter represents the start time on the input trace. Trace values
above this time will not be used in operator design.
Design time gate end(ms)

Enter the end time for decon operator design in milliseconds. The module will use a portion of the input
trace for decon operator design. This parameter represents the end time on the input trace. Trace values
below this time will not be used in operator design.
Design time gates

Enter the decon time file or build a matrix of start/end times to use for decon operator design. Use the
matrix method to vary start/end times over the survey.
1118
Primary header key

TLSN

TLSN


Total number of traces in dataset

Specify the number of traces in the dataset that this module is processing. The module allocates memory
half-way through the process, when all the traces have been computed. Sometimes this might abort the job
if not enough memory is available. The module will now compute an estimated amount of memory up
front. But the user has to specify the number of traces in the dataset. This will only be a memory estimate
allocation. The program will still have to make adjustments half through the process. But in most cases,
the estimate should be close enough.
1119
SCDECON2
Module Description
Input Channels
Output Channels
Parameters
Module Description
This program performs the second phase of a five component surface consistent deconvolution. Module
SCDECON1 has to be run first to build the surface-consistent spectra file. SCDECON1 and
SCDECON2 use any combination of line, source, receiver, offset, or CMP components to derive accurate
deconvolution filters which are then applied to the input traces. Surface-consistent deconvolution is
normally run on shot data. This module must have a SCDECON1 file attached to it.
Surface consistent deconvolution is based on the concept that a seismic wavelet can be separated into line,
source, geophone, cmp, and offset components. For land data, typically all five components are used
during the decomposition phase but only the line, source, and geophone are applied during the
deconvolution phase. For marine data, the receiver component is not used at all because the geophones are
in motion. However the receiver component might be used in shallow marine conditions due to variable
water bottom depths. The components used for decomposition phase and application phase will be data
dependent, so the user might want to experiment.
Phase two of the process (SCDECON2) builds an autocorrelation function from the selected
surface-consistent power spectra. A Weiner-Levinson spiking or predictive filter is built from the
autocorrelation function. The filter is convolved with the proper input trace. The surface-consistent log
power spectra built in phase one are stored in a SCDECON1 file. This file must be attached to the this
module
Surface consistent deconvolution is normally run on raw shot data. But it can also be applied to any
pre-stack data type. The SC deconvolution should be run before processes that destroy the character and
phase of the seismic wavelet. SC decon quality can be degraded when noise is in the data. In preparation
for SC decon you might want to run a de-spiking routine or other non-invasive noise reduction schemes.
Try to avoid using a bandpass filter before running SC decon because the filter will alter the phase and
character of the wavelet. If you need to filter, you might try an FK filter.
The trace deconvolution portion of the process can be run in parallel using threads. It is recommend that
you run threads only on multi-node CPU computers. It will run slower on single CPU machines when
more than 1 thread is used.
The module performs Wiener-Levinson Spiking or Predictive deconvolution. If Predictive decon was
chosen then the gap must have been entered in phase one. The decon operator length chosen in phase one
is also used here.
1120
Options exist to apply any combination of the surface-consistent components that were built in phase one.
The exceptions are the line component must be applied in a five component decomposition. The source
component must be applied in a four component decomposition.
Also see the help file for SCDECON1 for more information.
References
Wang, X., Five-component adaptive surface-consistent deconvolution. CSEG National Convention,
Calgary, Canada, 1992.
Cary, P.W. and Lorentz, G.A., 1991, Four-component surface-consistent deconvolution. Geophysics vol.
58. No. 3, March 1993, pg. 383-392.
Cambois, G., 1989, Surface-consistent deconvolution. SEG expanded abstracts, sp4.4.
Levin, S.A., 1989, Surface-consistent deconvolution. Geophysics, vol. 54. No. 9, pg. 1123-1133.
1121
Input Channels
2. Input: Required connection from dataset SCDECON1 data type.
Output Channels
Parameters
Number of threads to use?
This program will run parallel using threads. Threads should be run on multi-CPU machines only. A
thread can be created for each processor (CPU) but speed may not increase linearly.
Restore amplitude?
Select YES to attempt to match the amplitude balance of the input trace data with the output trace data. If
spikes or excessive noise are in the trace then this process might not work properly. If the output trace data
looks bad or zeroed try setting this to NO.
Low frequency (hz)

Select the lowest frequency in hertz for amplitude balancing.
High frequency (hz)

Select the highest frequency in hertz for amplitude balancing.
Include LINE component in application?

Select YES to include the line component in the trace deconvolution. If the line component was used in
the first phase then it must be applied in the second phase because it contains the dominate spectra. If the
line component was not built in the first phase then it will never be applied in the second phase.
Include SOURCE component in application?

Select YES to include the source component in the trace deconvolution. If the source component was used
in the first phase but the line component was not ( four component ) then it must be applied in the second
phase because it contains the dominate spectra. If the source component was not built in the first phase
then it will never be applied in the second phase.
1122
Include GEOPHONE component in application?

Select YES to include the geophone component in the trace deconvolution. If the geophone component
was not built in the first phase then it will never be applied in the second phase.
Include OFFSET component in application?

Select YES to include the offset component in the trace deconvolution. If the offset component was not
built in the first phase then it will never be applied in the second phase.
Include CMP component in application?

Select YES to include the common mid-point component in the trace deconvolution. If the cmp
component was not built in the first phase then it will never be applied in the second phase.
Include OTHER component in application?

Select YES to include the other component in the trace deconvolution. If the other component was not
built in the first phase then it will never be applied in the second phase.
1123
SCPHD1
Module Description
Input Channels
Output Channels
Parameters
Module Description
This is the first of the three modules which computes the surface-consistent amplitude and phase. This
process is often referred to as surface-consistent deconvolution.
The objective of surface-consistent deconvolution is to remove the surface-consistent factors. These
include the variations in source signature, geophone coupling, near-surface weathering effects. The output
contains the grand average of all the wavelets. Only the phase variation is removed since the average
waveform phase can not be separated from the phase of the reflectivity.
This suite of programs can correction small residual statics which are less than half of the wavelength.
PREREQUISITES: in order to be able to unwrap the phase, CMP or BIN sorted data are required.
Accurate NMO has to be applied. Residual statics should have been corrected if it is very strong.
It is all right and may be necessary to combine surface-consistent deconvolution with other deconvolutions
such as predictive deconvolution since they have different functionalities.
Sometimes, surface-consistent deconvolution may not be very effective, especially, when the data are
noisy and the fold coverage is low. The deconvolution of the phase depends on the statistical assumption
that phase can be extracted by looking at the horizontal event.
SCPHD1 computes the logarithm of the amplitude and phase spectra which are needed by SCPHD2 to
decompose the signal into the four components: Source, receiver, CMP/BIN and offset.
The phase spectrum is partially unwrapped in the CMP domain by using the algorithm described by
Cambois and Staffa (1993).
Either the entire trace or portion of the trace can be used in the computation. It is recommended that the
entire trace to be used, but when the signature varies with time very strongly, a time window may work
better for the zone of interest.
The user can supply a bandpass filter to SCPHD1, otherwise the entire bandwidth will be used. The filter
will be carried over into SCPHD2 and SCPHD3.
The minimum offset and average offset increment are used to group the offsets into a discrete number of
distinctive groups.
1124
References:
Cambois, G. and Staffa, P.L., Surface-consistent phase decomposition in the log/Fourier domain,
Geophysics. 58, 1099-1111.
Input Channels
Output Channels
1. Output: Required connection to dataset SCPHD1 data type.
Parameters
Windows for operator derivation?
End design time(ms)
Primary header key
TLSN

TLSN
Windows
1125



Minimum offset
Maximum offset
Average offset increment
Minimum SSPN
Maximum SSPN
Minimum SGEN
Maximum SGEN
Minimum SDPN
Maximum SDPN
1126
SCPHD2
Module Description
Input Channels
Output Channels
Parameters
Module Description
SCPHD2 decomposes the logarithm of the amplitude and phase spectra of each trace into its source,
receiver, CMP and offset components by using Gauss-Seidel algorithm.
Relative error is used as the means of quality control. A grand average amplitude level is computed over
all the frequencies and all traces. For each iteration, the program computes an average residual, which is
the portion of energy not assigned to any of the four components. The relative error is defined as the
percentage of the average residual over the average amplitude level. The relative error can be used as (1)
an indicator for the proper number of iterations. If the relative error after each iteration only changes on
the order of a fractional percentage, no more iterations are necessary; (2) an indicator for surface
consistency. If the amplitude spectra are perfectly surface-consistent, the relative error should be zero.
However, many other components may influence the amplitude and the surface-consistent model is not
absolutely valid. The relative error is usually not zero. It may be quite large, especially, when structural
smoothing is applied to the CMP component. The larger is the relative error, the less surface-consistent is
the data set.
Large spikes may cause the SCPHD programs to produce noisy output. Be sure that trace editing modules
are applied before SCPHD programs.
For more information, please see SCPHD1 and SCPHD2.
Input Channels
1. Input scphd1 file: Required connection from dataset SCPHD1 data type.
Output Channels
1. Output scphd2 file: Required connection to dataset SCPHD2 data type.
Parameters
1127
Relative error tolerance (%)

Maximum iterations
Offset term
Source term (phase & amplitude)

Options: Apply both, Compute & apply amplitude only, Compute both
only, Not compute
In-line structural smoothing(bins)

Cross-line structural smoothing(lines)
1128
SCPHD3
Module Description
Input Channels
Output Channels
Parameters
Module Description
SCPHD3 applies the surface-consistent components decomposed by SCPHD2.
For more information, please see SCPHD1 and SCPHD2
Input Channels
2. Input: Required connection from dataset SCPHD2 data type.
Output Channels
Parameters
Restore amplitude?
1129
SEG2
Module Description
Output Channels
Parameters
Module Description
The SEG-2 module will read seismic/radar data from files that conform to the SEG-2 standard. The files
are read one after the other when using the file mask and list method. This module should read SEG-2 data
files from portable seismographs and ground-penetrating radar devices.
The application of seismic reflection and ground penetrating radar methods to engineering groundwater
and environmental problems created the need for a seismic format that was appropriate for portable
seismographs and personal computers. The Engineering and Groundwater Geophysics Committee of the
SEG created the SEG-2 format to handle this need. This module will read seismic/radar data files that
conform to the SEG-2 standard.
The user has to option to set the sample rate and length of the data. The default is to get the sample rate
from the SEG-2 header word "SAMPLE_INTERVAL". The module will compute a default trace length
from the SEG-2 header descriptor block. The record number is computed by the module by incrementing,
the user specified starting record number by 1 for every file loaded. The channel number of each record is
computed by the module, starting at 1 and increment by 1 for every trace in the file.
The SEG-2 files are read automatically, one after the other, using a file mask and list. The file names must
conform to this method for the module to read multiple files.
Example: The following files where recorded
3480.seg2, 3481.seg2, 3482.seg2, 3483.seg2, 3484.seg2
The file mask will be "3400". The mask list matrix will contain "80, 81, 82, 83, 84". The file extension is
"seg2".
The files must be moved to a directory, which can then be specified in the menu.
Example: You want to load two SEG-2 files, rec001.dat and rec002.dat from the floppy drive using
Windows NT. The file mask would be "rec000", the mask list matrix would contain "1,2", the extension
will be "dat", and the path will be "a:". This will build the files to load:
a:/rec001.dat
a:/rec002.dat
For Unix computers, the file names will be case sensitive.
1130
If your file names do not conform to the above method you can read them one at a time. The preferred
method will be to rename the files so that they conform to the mask method. If you just want to read one
file, you can put the file name in the mask field and leave the mask list matrix blank.
The module assigns the record number (OIDN) to each ensemble using a user specified starting number.
Each subsequent ensemble has an OIDN increased by one.
If the SEG2 data must be loaded in separate jobs, use the append feature of the WRITE module. This
will allow you to add new SEG2 data to the end of an existing dataset.
The module uses the following SEG-2 keywords:
SAMPLE_INTERVAL
RECEIVER_LOCATION
SOURCE_LOCATION
DELAY
DESCALING_FACTOR
POLARITY
STACK
the sample rate.

the receiver X, Y, and Z coordinates.
the source X, Y, and Z coordinates
pad zeros to beginning of trace.
to scale trace to millivolts.
to correct for polarity of trace.
to scale trace to millivolts.
Output Channels
Parameters
Maximum number traces per ensemble
Specify the maximum number of traces in a shot or ensemble. This value must be at least as large as the
biggest record on file. The default is to read the number of channels from the first SEG-2 file loaded and
use this as the maximum.
Length of traces to process (msec)

Specify the length of traces to output in milliseconds. The default is to compute the length of the traces
from the first SEG-2 file that is loaded. You can override this value but specifying a length of trace here.
The module uses the number of samples recorded in the SEG-2 header block when loading the data. With
this parameter, the user can pad or delete samples from the output trace.
Input sample rate (usec)

Specify the sample rate of the recorded data in microseconds. The default is to read the sample rate from
the first SEG-2 file that is loaded. The module uses the "SAMPLING_INTERVAL" keyword in the
SEG-2 file to load as the sample rate.
1131
Starting record number (OIDN)

Specify the starting record number. The default is to start at 1. The module will assign the GCI header
words Original Field Record Number (OIDN) and Energy Source Point Number (ESPN) to this value.
For every record loaded, the value is increment by 1.
Mask for input file names

Specify the mask to use for building file names. All files that are loaded must use the same mask. Example
files: job1.dat, job2.dat, job3.dat. The file mask would be "job0". The mask should contain a "0" (zero)
where the number replacement will take place. This must be at the end of the mask.
Example: rec100.sg2, rec101.sg2, rec103.sg2. The mask would be "rec000".
Mask list for input file names

The mask list is a SeisUP matrix that contains the values used in combination with the above mask to
build the file names. Example files: job1.dat, job2.dat, job3.dat. The matrix will contain three rows with
values "1, 2, 3".
Matrix Type: RECMASK
Extension for input files

Specify a file extension if the file names have one. Example job1.dat has file extension "dat". The "." is
automatically added by the module. Please remember that Unix is case sensitive for file names. If a file
name is "REC001.SEG2", then the extension must be "SEG2", not "seg2".
Path to input files

Specify the path name to the file(s) location. In most cases, you will transfer the files to a temporary
directory to load the files into SeisUP. You must enter the directory path here. Example: You copy files
"job1.dat" and "job2.dat" to the "/tmp" directory:
/tmp/job1.dat
/tmp/job2.dat
In this case you must enter the directory path to complete the file name for the module. Which in this case
would be "/tmp".
1132
SEGP1
Module Description
Input Channels
Parameters
Module Description
This module will read in a SEG-P1 formatted ascii file and update the coordinates in a source and station
matrix. The SEG-P1 format is described in Appendix A of the SEG standard exchange formats for
positional data. If the matrix you are updating already exists, SEGP1 will first search a matching id in the
spreadsheet. If a match is found, only the X, Y, and elevations are updated. Otherwise, a new row is added
to the end of the spreadsheet. The id used in for the source matrix is the shot number and the id used for
the receiver matrix is the geophone bin and line number.
Input Channels
1. Seg-p1 file: Required connection from dataset ASCII data type.
Parameters
Matrix to create
Options: Source, Receiver
Select the preferred SOURCE pattern layout scheme.
Source
1133
Source
Land source by coordinate and pattern by receiver location
Source
Land source by coordinate and pattern by spread
Stations
Coordinates for all receiver stations
# of digits for the geophone bin #

For 3-D surveys the receiver line number is usually coded as part of the station number in the SEG-P1 file.
For example in 501234, 501 could be the receiver line number and 234 can be the station number within
line 501. To extract the line number from the station number in the SEG-P1 file, enter the number of digits
for the bin number. In this example the number would be three. The default is to use one for the receiver
line number and use all of the station number in the SEG-P1 file for the receiver bin number.
Number of decimal places for the coordinates

This can usually be determined by looking at the header at the beginning of the SEG-P1 file.
Number of decimal places for the elevations

This can usually be determined by looking at the header at the beginning of the SEG-P1 file.
1134
SEGYREAD
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module reads SEGY format data from a tape or disk data set and converts it to SeisUP internal format
(GCI). SeisUP supports standard trace data formats like IBM, 4-byte integer, and 4-byte integer with gain
code as well as popular formats like IEEE, 2-byte and 1-byte Integers. Several common non-standard disk
image formats are supported, MS-DOS, Landmark, and Charisma. SeisUP now provides the ability to
re-map SEGY trace header entries to SeisUP trace header entries directly.
The input sort order defaults to "get it from the header" but a further menu is available in order to define
this order in cases where the code is not in the header. The "ensemble" therefore relates to this code. The
search id index relates to this code. Start and ending ids allow only those ensembles defined to be read as
input data.
SeisUP will input seismic traces as IBM floating point, IEEE floating point, 4-byte, 2-byte, and 1-byte
Integers. Be aware that SeisUP will attempt to scale the traces in 2-byte and 1-byte integers using the
"Trace Weighting Factor" in bytes 169-170 of the SEGY trace header.
SeisUP supports several popular disk image formats that violate the SEGY standard. These are MS-DOS,
Landmark TOD, and Charisma. These formats may now be imported and exported directly.
The user can override the number of data samples per trace. The default is to use the value in the main reel
header, bytes 3221-3222. The user can also set the maximum trace length to output. If traces are longer
than the maximum, they will be truncated. If traces are shorter than the maximum, they will be zero
padded.
The option to read variable length traces allows the user to read SEGY files and tapes that contain records
that have different trace lengths. For files, the number of samples in the trace is read from SEGY trace
header bytes 115-116. For tapes, the module will attempt to read each block at the maximum block size so
that all trace lengths can be input.
The user may select to apply or not apply the depth and elevation scalar and the coordinate scalar. On rare
occasions, these values may be incorrect in the SEGY trace header, so they can be skipped. The user also
has the ability to set reference X and Y coordinates. The references will be subtracted from the source and
receiver coordinates read from the SEGY trace header.
A trace header re-map option aids in transferring non-standard SEGY trace header values to SeisUP trace
headers. Modern SEGY files often contain additional information in the SEGY trace header to support 3D
data and geometry. The extended words are written to the empty SEGY trace header bytes 181-240. The
re-mappings are stored in a SeisUP matrix in the global database. Several common re-mapping matrices
1135
are already built for you, including the SeisUP re-mappings. The re-map matrix is defined as follows:
Column 1: The SeisUP header word name or the word index (starting from one). Please see the GCI data
type for the word names. Typical words are TLSN (trace sequence number, word 1 ), RSLN ( receiver
station line #, word 65). You may also select by word number, example: TLSN = word 1, RSLN = word
65.
Column 2: The SEGY word format, 4I, 2I, 1I, 4R, 8R, #A and #C. These represent 4-byte integer (4I),
2-byte integer (2I), 1-byte integer (1I), 4-byte float (4R), 8-byte double (8R), ASCII string transfer (#A)
and ASCII string conversion (#C). The # with the A and C" is a placeholder for the number of
characters associated with the ASCII string. Example: 8A is an 8 character ASCII string. The #A format
will copy ASCII characters from the data source to the output buffer byte-for-byte. The #C format, on the
other hand, is used to convert a numerical value in an ASCII string into a 32 bit integer. For example, the
string "516 " would be converted to the integer value 516 using the #C format.
Column 3: The floating or double number types, IEEE or IBM. Floating or double number will be written
as IEEE or IBM style numbers.
Column 4: The starting byte in the SEGY trace header, must be 1-240. Enter the starting byte number
where the re-map word begins in the SEGY trace header.
Example: A SEGY trace header has the CDP x-coordinate mapped into bytes 181-184 of the SEGY trace
header as a 4-byte IEEE float. We will want to map the value into the SeisUP CDP x-coordinate word
MCX.
MCX 4R IEEE 181
LINE 8A 233
SEGYREAD supports an alternate method to import SEGY disk image files. The SEGY files can be read
automatically, one after the other, using a file mask and list. When this new method is chosen, the old
method (using disk input icon) is ignored.
Example: The following files where recorded
3480.sgy, 3481.sgy, 3482.sgy, 3483.sgy, 3484.sgy
The file mask will be "3400". The mask list matrix will contain "80, 81, 82, 83, 84". The file extension is
"sgy".
The files must be moved to a directory, which can then be specified in the menu.
Example: You want to load two SEGY files, rec001.dat and rec002.dat from the floppy drive using
Windows NT. The file mask would be "rec000", the mask list matrix would contain "1,2", the extension
will be "dat", and the path will be "a:". This will build the files to load:
a:/rec001.dat
a:/rec002.dat
1136
Another disk method is to import additional datasets, using the Interactive option. This method will
prompt the user in the job monitor window to enter additional dataset names to import after it finishes
reading a dataset. The user must enter a valid SeisUP dataset name.
When using tapes, the user has the option to input multiple files on tape. The files start at one and are
incremented by one. A file starts with an EBCDIC header and binary header and is ended with an EOF.
The user enters sequential file numbers in a matrix. The default is to load all files, which means all files on
a tape are loaded and then another tape is requested. If the user selects no to multiple files, then the
modules requests another tape when an EOF is found.
For Unix computers, the file names will be case sensitive.
References
Digital Tape Standards, reprinted from Geophysics, v.32, p.1073-1084, v.37, p.36-44, v.40, p.344-352.
SEGY Usage Recommendations, PESGB Data Management Group, Distribution as of Oct. 31, 1997.
Input Channels
1. Input : Required SEGY data type.
Output Channels
Parameters
Disk or tape
Select if this will be a tape or disk job. The module will compare against the connected dataset and will
abort if the dataset and this flag disagree.
Options: Disk, Tape
Use alternate disk file import method?

Use this selection to ignore the old method to input disk files and use the new file mask method. If this
option is chosen, then several parameters below are seen. Use this method to import multiple SEGY files
automatically using the mask naming convention.
1137
Remember that the disk input icon that is connected to the SEGYREAD module is totally ignored.
Select alternate matrix type:

This parameter is required if Disk or tape equals Disk and Use alternate disk file import method? equals
yes.
Options: RECMASK, Files
Mask for input file names

This parameter is required if Select alternate matrix type: equals RECMASK.
Specify the mask to use for building file names. All files that are loaded must use the same mask. Example
files: job1.dat, job2.dat, job3.dat. The file mask would be "job0". The mask should contain a "0" (zero)
where the number replacement will take place. This must be at the end of the mask.
Example: rec100.sgy, rec101.sgy, rec103.sgy. The mask would be "rec000".
Mask list for input file names

The mask list is a SeisUP matrix that contains the values used in combination with the above mask to
build the file names. Example files: job1.dat, job2.dat, job3.dat. The matrix will contain three rows with
values "1, 2, 3".
Matrix Type: RECMASK
Extension for input files

Specify a file extension if the file names have one. Example job1.dat has file extension "dat". The "." is
automatically added by the module. Please remember that Unix is case sensitive for file names. If a file
name is "REC001.SEGY", then the extension must be "SEGY", not "segy".
Path to input files

Specify the path name to the file(s) location. In most cases, you will transfer the files to a temporary
directory to load the files into SeisUP. You must enter the directory path here. Example: You copy files
"job1.dat" and "job2.dat" to the "/tmp" directory:
1138
/tmp/job1.dat
/tmp/job2.dat
In this case you must enter the directory path to complete the file name for the module. Which in this case
would be "/tmp".
Starting file path

This parameter is required if Select alternate matrix type: equals FILES.
File list
Matrix Type: FILES
Extension to input files

Interactively open additional data sets?

If this is set to "Yes", at the end of any SeisUP dataset, SEGYREAD will ask the user (operator) in the job
monitor window if there are any additional data sets to open. If the response is "y" for yes then the user
should respond to the next question with a valid SeisUP dataset name. The dataset must exist and have the
same sample rate and number of samples as the first data set read (attached input channel). NOTE - If are
changing the sample rate or trace length in SEGYREAD you will not be able to use this option.
Multiple files on tape?

Several SEGY files may be written to one tape. This option allows you to read addition files from a tape
that might be stored past the first EOF on tape. File numbers start from one and increment sequentially.
The files must be separated by an EOF (end of file mark). The files must also begin with EBCDIC and
binary headers. The default is to read all files, which means that all files on a tape are read and then
another tape is requested. Be aware that the sequential file counter can span multiple tapes. If the user
selected no, then another tape is request after an EOF is found.
File number list

If Yes is selected for multiple file on tape, then this parameter appears. Enter the matrix editor to input the
sequential file number to input. If the user enters 1, 3, then the module will read the first file up to an EOF
or end of tape, then skip the next file to an EOF or end of tape, then read the third file to an EOF or end of
tape. The job will then end automatically.
1139
Matrix Type: SEGYLINES
Input sort order

Use this parameter to override the sort order flag in the reel header.
Index to primary header word

Index to secondary header word
Index to ensemble header word
Max # traces per ensemble
This parameter must be set to the maximum number of traces per ensemble. Failure to set the parameter
correctly, could cause the ensembles to be broken up. The user will typically set the larger than the
maximum traces per ensemble.
Use sort order key for searching?

Search header key
Search header id index
Starting id
Ending id
Input data sample format
This parameter allows you to directly set the input data sample format. The options are:
IEEE floating point
IBM floating point
Integer, 4-bytes
Integer, 4-bytes w/ gain code
Integer, 2-bytes
Integer, 1-byte
1140
The default is to read the "Data sample format code" from the binary SEGY reel header, bytes 3225-3226.
The IBM and Integer, 4-bytes and 4-bytes w/ gain code are from the SEGY standard. The others are
non-standard. The Integer 2-byte and 1-byte formats will attempt to read and apply the "Trace weight
factor" from the SEGY trace header bytes 169-170 as per the SEGY standard.
Disk image format

This option allows the user to read/write popular non-standard SEGY disk formats. The default is to
read/write Standard SEGY disk images. The supported disk formats include MS-DOS, Landmark TOD,
and Charisma.
Number of samples per trace (override main header)

Specify the number of samples in a data trace. The default is to read the value from the SEGY main reel
header, bytes 3221-3222. On rare occasions, the number of data samples in the reel header is incorrect.
Use this option to override the value in the main reel header.

Specify the length of the traces to output in milliseconds. The default Input length is to get the number of
trace samples from the SEGY binary reel header, bytes 3221-3222. If traces are longer that this value, then
they will be truncated. If the traces are shorter that this value, then they will be padded with zeros.

Optional override of the sample rate in the data set. The default Get from data" is to get the sample rate
from the SEGY binary reel header, bytes 3217-3218.
Variable length traces?

Specify YES to assume that SEGY trace lengths may vary. On occasion, a record might have
shorter/longer traces than other traces in the SEGY file. Use this option to read the number of data samples
from the trace header bytes 115-116 and read the appropriate trace length. For tapes, this option will cause
the module to read the largest block possible (65536 bytes ) so that any trace length can be accommodated.
Save EBCDIC header to matrix

Select to save the EBCDIC header to a matrix. If doing a SEGY output later, you can attach this header to
the output using the SEGYWRIT module.
Matrix Type: SEGYEBC
1141
Apply the coordinate scalar?

Specify to apply the coordinate scalar, bytes 71-72 of SEGY trace header. This option will allow you to
apply/not apply the coordinate scalar to the X and Y coordinates read from the SEGY trace header, bytes
73-88.
Apply the depth and elevation scalar?

Specify to apply the depth and elevation scalar, bytes 69-70 of SEGY trace header. This option will allow
you to apply/not apply the scalar to the depths and elevations read from the SEGY trace header, bytes
41-68.
Specify XY reference coordinates?

Select to input reference X and Y coordinates. The reference coordinates will be subtracted from the input
X and Y source and receiver coordinates. If you select YES, the two reference parameters below will
appear.
X reference coordinate
Enter the X reference coordinate. This value is subtracted from the SEGY trace header words Source
coordinate - X (bytes 73-76) and Receiver coordinate -X (bytes 81-84).
Y reference coordinate
Enter the Y reference coordinate. This value is subtracted from the SEGY trace header words Source
coordinate - Y (bytes 77-80) and Receiver coordinate -Y (bytes 85-88).
Re-map SEGY trace header entries?

This option allows the user to select a re-map matrix for re-mapping SEGY trace header entries. Modern
SEGY files often contains additional information in the SEGY trace header to support 3D data and
geometry. The extended words are written to the empty SEGY trace header bytes 181-240. SeisUP now
supports the ability to re-map any SEGY trace header word directly to a SeisUP trace header word. The
re-mapping requires the following information defined in the matrix whose name is entered below in the
next menu parameter:
station line #, word 65). You may also select by word number, example: TLSN = word 1, TSLN = word
65.
Column 2: The SEGY word format, 4I, 2I, 4R, 1I, 8R, #A and #C. These represent 4-byte integer (4I),
2-byte integer (2I), 1-byte integer (1I), 4-byte float (4R), 8-byte double (8R), ASCII string transfer (#A),
and ASCII string conversion (#C). The # with the A and C is a placeholder for the number of
1142
Column 3: The floating or double type, IEEE or IBM. Floating or double number will be written as IEEE
or IBM style numbers.
where the re-map word begins.
MCX.
MCX 4R IEEE 181
LINE 8A 233
Definitions for trace header

Enter the matrix name that contains the SEGY to SeisUP trace header mappings.
1143
SEGYWRIT
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module will output SEGY tape and disk files of the SeisUP seismic traces. SeisUP supports standard
trace data formats like IBM and 4-byte integer as well as popular formats like IEEE, 2-byte and 1-byte
Integers. Several common non-standard disk image formats are supported, MS-DOS, Landmark, and
Charisma. SeisUP now provides the ability to re-map SEGY trace header entries to SeisUP trace header
entries directly.
SeisUP will output seismic traces as IBM floating point, IEEE floating point, 4-byte, 2-byte, and 1-byte
Integers. Be aware that SeisUP will scale the traces in 2-byte and 1-byte integers and write the scaled
values as the "Trace Weighting Factor" in bytes 169-170 of the SEGY trace header. The native SeisUP
trace format for UNIX and Windows NT machines is IEEE. If you use this data format, the files will read
faster because a trace conversion is avoided.
SeisUP now supports several popular disk image formats that violate the SEGY standard. These are
MS-DOS, Landmark TOD, and Charisma. The format may now be imported and exported directly.
The module will optionally output an end-of-file mark EOF, the EBCDIC header (3200 bytes) and then
the binary header (400 bytes) at each line change. The modules will check for a line change at the first
trace in an ensemble. So make sure that the ensembles are broken into lines. This option follows the
guidelines of the PESGB SEGY usage recommendations.
A trace header re-map option has been added to aid in transferring non-standard SEGY trace header values
to SeisUP trace headers. Modern SEGY files often contains additional information in the SEGY trace
header to support 3D data and geometry. The extended words are written to the empty SEGY trace header
bytes 181-240. The re-mappings are stored in a SeisUP matrix in the global database. Several common
re-mapping matrices are already build for you, including the SeisUP re-mappings. The re-map matrix is
defined as follows:
65.
Column 2: The SEGY word format, 4I, 2I, 4R, 8R, and #A. These represent 4-byte integer (4I), 2-byte
integer (2I), 4-byte float (4R), 8-byte double (8R), and ASCII strings. The # with the A is the number
of characters associated with the ASCII string. Example: 8A is a 8 character ASCII string.
1144
MCX.
MCX 4R IEEE 181
LINE 8A 233
References
Digital Tape Standards, reprinted from Geophysics, v.32, p.1073-1084, v.37, p.36-44, v.40, p.344-352.
SEGY Usage Recommendations, PESGB Data Management Group, Distribution as of Oct. 31, 1997.
Input Channels
Output Channels
1. Dataset: Required SEGY data type.
Parameters
Disk or tape:
File on tape to write
Required if Disk or tape: equals Tape.
Several SEGY files may be written to one tape. This option allows you to append addition files onto a
single tape. File numbers start from one. You must increase this parameter by one each time you write to
the tape. If for example you wrote files 1, 2, and 3 to a tape then you must write to file 1 or to file 4. If you
write to 2 or 3 then you will get an error of "Invalid argument". If you write to file 1, any existing files
after this file will not be readable.
1145
Output data sample format

This parameter allows you to change the output data sample format. The options are:
IEEE floating point
IBM floating point
Integer, 4-bytes
Integer, 2-bytes
Integer, 1-byte
The IBM and Integer, 4-bytes are from the SEGY standard. The others are non-standard. The Integer
2-byte and 1-byte formats will scale the trace and put the weight factor into the SEGY trace header bytes
169-170 as per the SEGY standard.
Output EBCDIC and binary header at line change?

Required if Disk or tape: equals Tape.
Select to output a EBCDIC and binary header at each line change (tape only). The module will output a
end-of-file mark EOF, the EBCDIC header (3200 bytes) and then the binary header (400 bytes) at each
line change. The modules will check for a line change at the first trace in an ensemble. So make sure that
the ensembles are broken into lines.
Disk image format

Required if Disk or tape: equals Disk.
This option allows the user to read/write popular non-standard SEGY disk formats. The default is to
read/write Standard SEGY disk images. The supported disk formats include MS-DOS, Landmark TOD,
and Charisma.
Re-map SEGY trace header entries?

This option allows the user to select a re-map matrix for re-mapping SEGY trace header entries. Modern
SEGY files often contains additional information in the SEGY trace header to support 3D data and
geometry. The extended words are written to the empty SEGY trace header bytes 181-240. SeisUP now
supports the ability to re-map any SEGY trace header word directly to a SeisUP trace header word. The
re-mapping requires the following information defined in the matrix whose name is entered below in the
next menu parameter:
station line #, word 65). You may also select by word number, example: TLSN = word 1, TSLN = word
65.
1146
Column 2: The SEGY word format, 4I, 2I, 4R, 8R, and #A. These represent 4-byte integer (4I), 2-byte
integer (2I), 4-byte float (4R), 8-byte double (8R), and ASCII strings. The # with the A is the number
of characters associated with the ASCII string. Example: 8A is a 8 character ASCII string.
Column 3: The floating or double type, IEEE or IBM. Floating or double number will be written as IEEE
or IBM style numbers.
where the re-map word begins.
MCX.
MCX 4R IEEE 181
LINE 8A 233
Definitions for trace header

Enter the matrix name that contains the SEGY to SeisUP trace header mappings.
EBCDIC reel header

The user can build a EBCDIC reel header in a matrix that will then be put on tape/disk as the reel header.
If the default blank is left here, SeisUP will build a default EBCDIC header for you. This header will be
output as 3200 bytes. The typical layout is 40 rows of 80 characters in EBCDIC character format
Emulate a VIP file

This option was added to allow velocity files to be imported from third parties. No data verification is
attempted.
A VIP file is essentially a SEG-Y file with extra non-standard headers. The data sort order MUST be
either 3-D X-bin gather or 3-D X-bin stack.
VIP files are set up as a rectangular grid with velocities at every MBIN / MLIN location. The minimum
and maximum values for each must be input and must reflect the data present. Data outside of these
values will cause modules that read the file to abort. If in doubt, run SELECT before this module.
Velocity model type
1147
Velocity type
Minimum MBIN
Maximum MBIN
Minimum MLIN
Maximum MLIN
1148
SELECT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Input Channels
Output Channels
Parameters
Select "Yes" to use the absolute value of the extracted header values to determine if this trace should be
extracted.
Primary header key

TLSN, other
Primary GCI index

TLSN, other
1149
Secondary GCI index

Tertiary header key
TLSN, other
Tertiary GCI index

Groups to select
1150
SGN1
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program SGN1 computes the instantaneous mean amplitude for each input trace. It is the first program to
run in surface-consistent gain analysis. The output of SGN1 can be read by SNG2 which decomposes the
amplitude into source, receiver, CMP and offset terms. A matrix defining the time window from which
amplitude information is to be extracted can be specified by a multi-dimensional matrix. The amplitude is
measured over the prescribed bandwidth, but no actual filtering is applied to the data.
Input Channels
Output Channels
1. Output: Required connection to dataset SGN1 data type.
Parameters
The program can take either constant window or space variant windows.
Window times: Spread sheet contains the customized windows

1151
Primary header key

TLSN

TLSN
Window times

Band Pass filter is used to avoid the interference of high frequency noises.

Dump first record?
This parameter was added after a long running job aborted unexpectedly. The first record in the output file
is needed for SGN2 to run. If this parameter is set to yes, the SGN2 can run even if the SGN1 is killed. It
increases the I/O of the job but does not significantly increase the CPU time.
1152
SGN2
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program SGN2 decomposes the instantaneous amplitude information, picked by SGN1 into two-to-four
terms in a best-fit sense by using the Gauss-Seidel algorithm. The source and receiver terms are always
computed and applied while the CMP and offset terms are optional in both computation and application.
SGN2 will generate two color plots in the CGM format, outputting the average instantaneous amplitude
before and after the surface consistent solution. The user specifies the number of contour levels and the
amplitude deviation range (Plotting range). This range is the plus and minus range relative to the reference
mean on the input. Generally, two times the edit range is a good guess for the plotting range.
The amplitude plot after SGN2 should be much smoother than before. However, as the name "best-fit"
indicates, the solution is the best under the given conditions. The corrected amplitude will not be perfectly
flat in general because the equation system is overdetermined, i.e. it is not possible to completely satisfy
every point.
SGN2 can automatically edit the seismic traces as an option. The user will have to specify the positive and
negative (DB) range around the reference mean. Any traces outside this range after correction will be
selected and written into an OMIT matrix which can be used by SGN3 to kill the selected traces.
SGN2 also takes an existing OMIT matrix. It will ignore the traces in the OMIT matrix in the solution.
The output OMIT matrix will contain both the input OMIT traces and the newly-determined OMIT traces.
Note that the input OMIT matrix has to be an output from a previous SGN2 run.
Input Channels
1. Input: Required connection from dataset SGN1 data type.
Output Channels
1. CGM plot file: Optional connection to dataset CGM data type.
1153
Parameters
Error limit (milliDB)
Max. number of iterations
The maximum number of iterations at which the program discontinues reiteration even if the error is still
larger than the ERROR LIMIT. This is to prevent the program from going into infinite loops if the
solution is not convergent.
Min. offset
Offset interval
Offset term
Options: Compute & apply, Compute only, Dont compute
CMP term
Options: Compute & apply, Compute only, Dont compute
Weight each term?

The four terms can also be weighted in the solution. For instance, a damping factor of 5000 for offset
means the offset error is divided by 1.5, i.e. 1.0+0.001*5000, before summing into the total error. In other
words, the program will tolerate larger errors on offset than on the other terms.
Perturbation on source (% * 100)

Required if Weight each term? = Yes. See Weight each term? for an explanation.
Perturbation on geophone (% * 100)

Perturbation on CMP (% * 100)

1154
Perturbation on offset (% * 100)

Surface-consistent gain matrix

The spreadsheet matrix name to contain the computed surface-consistent gain information.
Matrix Type: SGN2
Input OMIT matrix?

An OMIT matrix matrix can be read. The omitted traces in the matrix will not be accounted for in the
solution and will be carried into the output OMIT matrix if chosen.
Input OMIT matrix name

Required if Input OMIT matrix? = Yes.
Matrix Type: OMIT
Automatic trace editing?

If Old Style, SGN2 will generate an OMIT matrix which can be read SGN3 and applied to the data. It can
also be read by the OMIT module. NOTE, if used by the OMIT module set Primary header key to SSPN,
Secondary header key to SGEN and Tertiary header key to NONE.
On extremely large surveys the output OMIT matrix may be too large for SGN3 or OMIT to open. If this
is the case, SGN3 will abort and OMIT will appear to hang. The number of spread sheets in the matrix is
the controlling factor.
The less than satisfactory solution is to use the Spread sheet limit parameter which causes the OMIT
matrix to be split into separate pieces every N spread sheets. This requires multiple OMIT modules in the
job flow. The name of the output matrices will be Output OMIT matrix name:001, Output OMIT matrix
name:002, Output OMIT matrix name:003, up to Output OMIT matrix name:999. The execution status
will list the matrix names.
If New Style, SGN2 will generate a single OMIT matrix which can be read by the OMIT module and not
by SGN3. NOTE, set Primary header key to NONE, Secondary header key to SSPN and Tertiary header
key to SGEN in the OMIT.
If None no OMIT matrix will be created.
1155
Output OMIT matrix name

Output OMIT matrix name
Required if Automatic trace editing? = Old Style or New Style. See the discussion in Automatic trace
editing?.
Matrix Type: OMIT
Spread sheet limit

Required if Automatic trace editing? = Old Style. The default value turns this parameter off. See the
discussion in Automatic trace editing?.
Negative threshold (DB)

Required if Automatic trace editing? = Old Style or New Style.
Positive threshold (DB)

Required if Automatic trace editing? = Old Style or New Style.
QC plot contour levels

The color contour levels in amplitude plot of source versus geophone diagram.
Shots per inch

Geophones per inch
Plotting range (+/- DB)
The dynamic range for amplitude plotting. This is the plus-and-minus range relative to the reference mean.
Generate SGN attribute matrices?

Select Yes to output a gain attribute to the database that can be viewed later with the module QCVIEW.
NOTE - This will significantly increase the run time of the program.
NOTE - Do not use the same name for SGN attribute on input: and SGN attribute on output:. They are the
same matrix type and SGN attribute on input: will be over written.
1156
SGN attribute on input

This attribute will be the amplitude of the data before SGN1,2,3. Required if Generate SGN attribute
matrices? = Yes.
SGN attribute on output

This attribute will be the amplitude of the data after SGN3 is applied. Required if Generate SGN attribute
matrices? = Yes.
Plot to create
This option was added as something of a kluge to avoid an abort that has proved difficult to track down
and eliminate. The abort is dependent on the size of the CGM file(s) and generally occurs when the plot
file is being closed. If you get an abort in a routine that starts with "plt_", turn off either of the plots and
resubmit. If it still aborts, turn both off.
Options: Both, Before SGN, After SGN, Neither
Printout level
On large surveys the listing file can get to be very large. Printing the corrections can take a significant
fraction of the execution time of this program.
Options: All, Killed traces, None
Ignore null data?

Equation block limit
This parameter was added to get around a rather nebulous size limit that is sometimes tripped with very
large surveys. The symptom of hitting the limit is that SGN2 will abort with an error during a write saying
there is no such file. As the file in question had just been created and initialized a few lines above the
abort, the message is wrong.
This is possibly a system dependent issue. If the default of 50000000 fails, please let GeoCenter
Programming know what system you are on and what did work.
1157
SGN3
Module Description
Input Channels
Output Channels
Parameters
Module Description
Program SGN3 applies the surface consistent gain computed by SGN2 to the input seismic traces.
The user prescribes the reference mean of the output data.
The user can optionally edit the traces by applying an OMIT file created by SGN2.
Input Channels
Output Channels
Parameters
Input gain file
Name of the spreadsheet file which contains the surface-consistent gain information in the format of
SGN2.
Matrix Type: SGN2
Reference mean amplitude

Automatic trace editing
1158
OMIT file name

Matrix Type: OMIT
Abort if OMIT matrix does not exist?

This option is helpful when run batch jobs to keep the job flow running even though SGN2 may not have
omitted any traces. The default is set to abort to warn the user when run interactively.
1159
SGNE1
Module Description
Input Channels
Output Channels
Parameters
Module Description
SGNE1 cross-equalizes gain between the prescribed TERTIARY( SOURCES, or RECEIVER, or CMPS
or OFFSETS). It computes the instantaneous amplitude of each trace and sum the result into its
corresponding TERTIARY number. After all the traces, the amplitude at each TERTIARY number is
normalized by the fold. A scale vector is computed to cross-equalize the amplitude between the
TERTIARYs. The scale vector at each TERTIARY is saved for application by SGNE2.
SGN modules (SNG1, SGN2 and SGN3) correct each trace with a constant gain. However, SGNE
modules (SGNE1 and SGNE2) adjust each trace using time variant gain. Therefore, SGNE modules also
balance the amplitude in time direction. SGNE modules are semi-surface consistent when only one pass is
used.
The SGNE1 module saves a dataset file containing the gains that are to be applied by SGNE2. This dataset
file must be connected to a SGNE2 module to complete the gain application.
Optionally, the SGNE1 module will save a matrix of type SGNE. This matrix contains the gains that are to
be applied by SGNE2. The matrix name can be supplied to SGNE2 via the menu.
USAGE & TIPS

Between SGNE1 and SGNE2, there should be no modules which can vary the amplitude. It is
recommended that SGNE1 is immediately followed by SGNE2.
NMO and explicit muting should proceed SGNE1 and SGNE2. SGNE1 extracts the amplitudes from all
the traces in the ensemble at each time sample, therefore, NMO needs to be applied. Explicit muting is
necessary because if the intended mute zone are not zeroed, the samples will be counted in the SGNE
program. If these numbers are wildly small or large, they can affect the gain curve in the data portion due
to the smoothing factor.
Input Channels
1160
Output Channels
1. SGNE1 data set: Optional connection to dataset SGNE1 data type.
2. To next process: Optional connection to next process GCI data type.
Parameters
Perform SGNE on
Options: SOURCE, GEOPHONE, CMP, OFFSET
Minimum offset
Required if Perform SGNE on: equals OFFSET.
Offset increment
Reference mean
Smoothing filter length (ms)
Output the SGNE curves in a matrix?
Options: YES, NO
The next four parameters MUST be input if the database does not contain valid information.
1161
Starting output line number (MLIN)

Required if Output the SGNE curves in a matrix? equals YES.
Starting output bin number (MBIN)

Required if Output the SGNE curves in a matrix? equals YES.
Increment between line locations

Required if Output the SGNE curves in a matrix? equals YES. If valid geometry exists and lininc is
greater than the number of MLINs present, it will be reset to the number of MLINs present.
It appears to be desirable for this parameter to be moderately large, on the order of 100.
Increment between bin locations

Required if Output the SGNE curves in a matrix? equals YES. If valid geometry exists and bininc is
greater than the number of MBINs present, it will be reset to the number of MBINs present.
It appears to be desirable for this parameter to be moderately large, on the order of 100.
SGNE curve matrix

Matrix Type: SGNE
Use old logic?

The old logic tended to blow up the shallow section on the near offsets and the deep section on the far
offsets.
Options: YES, NO
1162
SGNE2
Module Description
Input Channels
Output Channels
Parameters
Module Description
Input Channels
1. Sgne1 gain data: Required connection from dataset SGNE1 data type.
2. Input: Optional connection from previous process GCI data type.
Output Channels
Parameters
Input the SGNE curves in a matrix?
If equal YES, the input dataset is ignored.
Options: YES, NO
SGNE curve matrix

Required if Input the SGNE curves in a matrix? equals YES.
Matrix Type: SGNE
Perform SGNE on
Required if Input the SGNE curves in a matrix? equals YES.
Options: SOURCE, GEOPHONE, CMP, OFFSET
1163
Minimum offset
Offset increment
Read as needed
If equal YES, the input SGNE file is read as needed for each trace instead of being read into memory. This
allows very large datasets to be processed. The input sort order should be the same as the Perform SGNE
on parameter in SGNE1 for I/O efficiency.
Required if Input the SGNE curves in a matrix? equals NO.
Options: YES, NO
Apply or remove gain

1164
SLICE
Module Description
Input Channels
Output Channels
Parameters
Module Description
SLICE will extract a stack section corresponding to specified velocity functions by "slicing" through the
three-dimensional velocity-midpoint-time data cube that was created by module SMIG.
Input Channels
Output Channels
Parameters
RMS velocities
Matrix Type: RMSVEL
1165
SMIG
Module Description
Input Channels
Output Channels
Parameters
Module Description
SMIG will perform 2-D velocity independent dip moveout (DMO) or prestack migration. SMIG requires
that the input data be CDP sorted. A stretch mute can optional be applied to the data to mute distortions
due to excessive stretching of the data during NMO.
Migration Algorithm
The following is a description of the algorithm:
1. q(tn,y,h) - q(t0,y,vstk). Create a three-dimensional time- midpoint-velocity data cube by performing a
constant velocity stack over a suite of velocities.
2. q(t0,y,vstk) - Q(w,ky,vstk). 2-D Fourier transform.
3. Q(w,ky,vstk) - Q(w,ky,v). DMO applied by shifting of the velocity axis from higher to lower
velocities where vstk = v/cos(theta).
4. Q(w,ky,v) - Q(kt,ky,v). Stolt migration of each constant velocity section.
5. Q(kt,ky,v) - q(t0,y,v). Inverse 2-D Fourier transform.
6. q(t0,y,v) - q(t0,y). Velocities can be chosen with module VSLICE and an imaged zero-offset section
is produced by slicing diagonally down through the cube.
The DMO correction is V divided by cosine theta, therefore, the user should substitute the expected
maximum velocity with V and the greatest dip for theta in the above equation to represent the upper
velocity limit for this program.
To avoid aliasing when slicing a zero-offset section from the velocity cube, the velocity increment should
be calculated as follows:
cos(theta)
P < ------------------- * 100
2*F*T*sin(theta)**2
Where:
P
= The velocity increment in percent.
theta = The maximum dip after migration at time T.
T
= The greatest time in seconds where aliasing is to
be avoided.
F
= Frequency at time T.
1166
Use the following formula to calculate the number of velocities generated:

n = ln(vmax/vmin)*100/P+1
Where:
n
vmax
vmin
P
=
=
=
=
The
The
The
The
number of velocities generated.

maximum velocity.
minimum velocity.
velocity increment in percent.
Stack Normalization
When creating the velocity stacks, the following normalization techniques are available:
1. divide by the fold
2. add a constant to the fold prior to the divide
3. divide by the square root of the fold
In noisy unstacked data with constant amplitude along the length of the traces; normal stacking, i.e.
summing and dividing by the fold, produces a trace whose amplitude is higher at shallower times than
deeper. This is because fold is increasing with time, and the higher the fold, the more the normal stacking
reduces the amplitude of the noise component of the data. This effect is also seen on roll-in and roll-out,
where fold is changing. By adding a constant to the fold prior to division, the effect is to reduce the
amplitude of the low fold data relative to the higher fold data. This constant should not greater than square
root of maximum fold. By dividing by the square root of the fold, the effect is to increase the amplitude of
the higher fold data relative to the lower fold data.

domain transformation. To help alleviate these sharp cutoffs, SMIG has the following options:

Migration will move data from the apparent dip to the true dip. For dips measured at 45 degrees,
Migration will move those dips to 90 degrees. Any data that was above 45 degrees is noise. The removal
of this noise makes a migrated section appear too smooth or wormy looking. Some of the noise can be left
in to make the section appear more like the character of the original stack. SMIG can retain noise beyond a
certain dip limit as well as noise at the spatial Nyquist as defined in the following diagram.
1167
Spatial
Spatial
Nyquist
Nyquist
___________________________________________________ Temporal
|
|
|
|
| Nyquist
|
|
|
|
|
|
|
MIGRATED
|
MIGRATED
|
|
|
|\
|
/|
|
| N | \
|
/ | N |
| O |
\
|
/
| O |
F | I |
\
|
/
| I | F
| S |
\
|
/
| S |
| E |
\
|
/
| E |
|
|
\
|
/
|
|
|
| NOISE
\
|
/
NOISE
|
|
|
|
\ | /
|
|
|_____|__________________\|/__________________|_____|
-100%
0
+100%
Ray Bending
To correct for the effects of ray bending for vertical velocity variation, SMIG will on option use a
dip-dependent migration velocity in the frequency-wavenumber domain. Without this correction, dips
beyond 45 degrees will be under migrated at the imaging velocity used for the adjacent sediment. With
this correction, steeply dipping events and adjacent sediments can be imaged correctly with the same
velocity. SMIG will require a single average velocity function with more than one layer for the ray
bending correction.
Reference
Fowler, P., 1984, Velocity independent imaging of seismic reflectors: Presented at the 54th Annual SEG
Meeting, Atlanta.
Gazdag, J., 1978, Wave-equation migration with the phase-shift method: Geophysics, 43, 1342-1351
Hale, I. D., 1983, Dip moveout by Fourier transform: Presented at the 53rd Annual SEG Meeting, Las
Vegas.
1168
Input Channels
Output Channels
1. Velocity cube: Required connection to next process GCI data type.
2. Velocity cube for vslice: Optional connection to dataset SMIG data type.
Parameters
Using VIP file?
Select No (default) to run the module the usual way, via a series of constant velocity panels. In such a case
the user must specify the Starting Velocity, the Ending Velocity, and the Velocity Increment.
Select Yes to run the module with an already-known velocity function as the starting panel. In such a case,
a VIP file must be connected to the module (channel 2), containing such a velocity function. The user
must also specify the Number of Velocity Panels, and the Velocity Increment. The program will increase
the whole velocity-function by the % indicated, as many times as indicated by the Number of Velocity
Panels.
NOTE 1: Please remember SMIG has two output channels: OUT1 (GCI, connected to a WRITE module,
for instance), and OUT2 (connected to VSLICE only). When SMIG user selects constant-velocity option,
output sections (in OUT1) will show each constant velocity value in the header word VELO, and VSLICE
(in OUT2) will show each constant velocity value in the upper-right window. However, when SMIG user
selects VIP file option, VELO will show an integer ordinal number only, and VSLICE (upper right
window) will show only REFERENCE values starting always at 10, not actual velocity values.
NOTE 2: Module SMIG performs Fowler Migration, which is in turn based on Stolt migration, designed
specifically for constant velocity only. The introduction of this VIP-file option for a variable-velocity field
strictly contradicts the theoretical principles of the method. It is a useful practical feature though, in some
cases. It is intended for PRELIMINARY analysis only, to be used with the CVS-Only migration option.
All other migration options are voided when this VIP-file option is active.
Number of velocity panels

Enter the number of velocity panels in the velocity cube of the Fowler algorithm.
1169
Velocity Increment
Enter the velocity increment between panels of the velocity cube of the Fowler algorithm.
Starting velocity
Enter the velocity value for the first panel of the velocity cube.
Ending velocity
Enter the velocity value for the last panel of the velocity cube.
Velocity increment (%)

Enter the velocity increment between panels of the velocity cube.
Use ray bending correction?

Velocity function for ray bending
Matrix Type: RMSVEL


TLSN

TLSN
Mutes
This matrix is for muting the data after normal moveout is applied.
1170


Enter the amount of percentage stretch for the output traces after NMO has been applied. Enter a value of
0 to NOT apply a stretch mute. The author recommends starting at 30 for 30% stretch muting.
Max. memory to use for migration (MBytes)

Percentage of top mute to restore
SMIG will zero the mute time times this percentage samples after migration.
Percentage of bottom mute to restore

Migration option
Options: DMO only, Migration only, DMO and Migration, CVS only

number of traces.

Retain noise?
This is the roll-off in degrees between the migrated dips and the noise.
1171

This is the percentage to apply to the noise beyond the maximum dip to migrate.
Maximum K to migrate (%)

This is the roll-off in percent between the migrated K frequencies and the noise.

This is the percentage to apply to the noise beyond the maximum K to migrate.
CMP padding (traces)

Time padding (samples)

This is the minimum number of zero samples to be padded at the end of the record to prevent wraparound
of the 2-D transformed data. When performing DMO only this can be zero.

CMP interval

PMora, April 2010
1172
SMIGSAVE
Module Description
Input Channels
Output Channels
Parameters
Module Description
SMIGSAVE can be used to save or restore a velocity cube for interactive slicing with the module
VSLICE. To save disk space, the user may create a velocity cube with module SMIG, output to tape, and
later restore the cube to disk with module SMIGSAVE. An alternative method is to pick the velocities
with module VSLICE, save the cube with module SMIGSAVE, delete the cube from disk, and later
restore the cube with module SMIGSAVE to repick the velocities.
Input Channels
1. Input cube: Optional connection from previous process GCI data type.
2. Velocity cube from smig: Optional connection from dataset SMIG data type.
Output Channels
1. Output cube: Optional connection to next process GCI data type.
2. Velocity cube for vslice: Optional connection to dataset SMIG data type.
Parameters
Option to perform
Options: Save, Restore

1173
SMOOTH
Module Description
Parameters
Module Description
Create smoothed version of matrix types RMSVEL and 4THNMO.
An input matrix is specified and the values are read in and smoothed using a linear triangulation routine.
The smoothed values are output to a new matrix of the same type.
The amount of smoothing is determined using the Number of lines/bins to smooth over. A larger number
will create more smoothing than a small number.
The user extracts the new locations using the same type of matrix as in CVA3D to prescribe the velocity
locations. If the location is defined as a range, instead of a single bin and line value, the center is computed
and used as the output location.
Parameters
Input matrix type
Enter the type of matrix that will be smoothed.
Options: RMS Velocity, 4th Order NMO Correction

If a RMSVEL matrix was selected. Enter the existing RMSVEL matrix that will be smoothed.
Matrix Type: RMSVEL
Output RMS velocities

If a RMSVEL matrix was selected. Enter a new RMSVEL matrix that will contain the smoothed values.
Matrix Type: RMSVEL
1174
Input 4th order NMO correction

If a 4THNMO matrix was selected. Enter the existing 4THNMO matrix that will be smoothed.
Matrix Type: 4THNMO
Output 4th order NMO correction

If a 4THNMO matrix was selected. Enter a new 4THNMO matrix that will contain the smoothed values.
Matrix Type: 4THNMO
Input ETA NMO correction

If a ETANMO matrix was selected. Enter the existing ETANMO matrix that will be smoothed.
Matrix Type: ETANMO
Output ETA NMO correction

If a ETANMO matrix was selected. Enter a new ETANMO matrix that will contain the smoothed values.
Matrix Type: ETANMO
Input SGNE gain curves

If a SGNE matrix was selected. Enter the existing SGNE matrix that will be smoothed.
Matrix Type: SGNE
Output SGNE gain curves

If a SGNE matrix was selected. Enter a new SGNE matrix that will contain the smoothed values.
Matrix Type: SGNE
Number of bins to smooth over

Specify the number of bins to smooth over. A larger number will cause greater smoothing.
Number of lines to smooth over

Specify the number of lines to smooth over. A larger number will cause greater smoothing
1175

Enter the existing extraction matrix. This matrix is also used in CVA3D and VIPINV to specify the
locations to extract for the output matrix.
Expected output time interval for matrix (ms.)

Enter the sampling interval for smoothing and output in milliseconds. This is the time interval at which the
smoothing will be computed. The output matrix will have time values at this interval.

Specify a subset of the data. Enter the minimum midpoint line number to compute.

Specify a subset of the data. Enter the maximum midpoint line number to compute.

Specify a subset of the data. Enter the minimum midpoint bin number to compute.

Specify a subset of the data. Enter the maximum midpoint bin number to compute.
1176
SMTHANG
Module Description
Parameters
Module Description
This module is used to smooth the angle values generated by FRACDET and then use them in ROTATE
to rotate the seismic dataset. This process is done by forming a moving average of the angles.
Parameters
Number of midpoints to smooth over
Input rotation angle matrix
Output rotation angle matrix

1177
SMVSLICE
Module Description
Input Channels
Output Channels
Parameters
Module Description
SMVSLICE is an interactive module that is used to update a migrated section according to velocities
defined interactively by the user. The user defines a velocity function from a velocity cube created by the
module SMIG. The user will pick velocities values on some convenient locations, and SMVSLICE will
interpolate internally, thus building the whole velocity function. SMIG consists of the following two
windows:
1. The top window is the constant velocity display window. Velocities are picked in this window. The
existing velocity pick will identified by a red solid dot.
2. The bottom right window is the zero-offset section sliced from the velocity cube.
To the right of the seismic displays is the menu icon bar. The menu icons can be used instead of using the
menus from the menu bar.
The sash between the constant velocity window and the zero-offset section can be dragged with the mouse
to adjust the height of these windows.
Picking velocities
To pick velocities click the left mouse button in the constant velocity window. The following mouse
buttons may be used to modify velocities.
Button 1

location.
Button 2

location.
Button 3

location.
File menu
Option
Icon
Description
--------------------------------------------------------------
Increase velocity Cube-arrow up
Display the next velocity
1178
increment plain.
Decrease velocity Cube-arrow down Display the previous

velocity increment plain.
Slice
Cube-sliced
Output
Disk-arrow down Slice any CMPs that need

updating and save to the
output data set.
Change parameters
Slice the velocity cube using

the current velocity cube
over the currently displayed
CMPs.
Change various parameters
Print ...
Printer
Print screen.
Quit
Lightning bolt
Quit SMVSLICE
Help menu
Option
Description
--------------------------------------------------------------
On use
On how to use SMVSLICE.
On menu icons
Input Channels
1. Velocity cube: Required connection from dataset SMIG data type.
Output Channels
1. Output stack: Required GCI data type.
1179
Parameters
RMS velocities
Matrix Type: RMSVEL
Velocity plain increment

Wiggle type
Options: Wiggle only, Wiggle and VA, Contour
Bias
Traces per inch
Inches per second
Gain (db)
Clip (traces)
Timing lines?
Timing line increment
Plot Direction
Start time (ms)

Ending time (ms)
User defined velocities?
Minimum velocity?
1180
Maximum velocity?
Power colormap:
Select cursor size?
1181
SNR
Module Description
Input Channels
Output Channels
Parameters
Module Description
SNR is a random-noise-suppression program. It reduces the random noise by crosscorrelating the current
trace with a pilot trace. The pilot trace is the previous live trace. The random-noise components will have
zero crosscorrelation. Thus, only the signal components survive the cross- correlation.
Input Channels
Output Channels
Parameters
Pilot trace
The pilot trace can be either the previous filtered trace or the previous input trace. The option of "previous
filtered trace" is more powerful in suppressing random noises, but one bad trace may influence all the
ensuing traces. The option of "previous input trace" restricts the influence between two contiguously live
traces only.
Options: Previous filtered trace, Previous input trace
Space variant starting time?

Primary header key
TLSN
1182

TLSN
Start times
Matrix Type: SNR
Crosscorrelation window(ms)
Window overlap(%)
1183
SORT
Module Description
Input Channels
Output Channels
Parameters
Module Description
The program SORT will produce several specified trace sort-ordered. Nine specific options are specified
including "Other" which allows primary, secondary and internal ensemble sort order outputs. Max # of
traces per output ensemble must be coded. The number of traces to hold on disk relates to the maximum
number of traces which need to be input in order to output a given ensemble.
Input Channels
Output Channels
Parameters
Output sort order
Options: Shot, Geophone, Offset, CMP gather, Stack, 3-D X-bin
gather, 3-D Y-line gather, 3-D X-bin stack, 3-D Y-line stack, Other
Primary sort header key

Required if Output sort order equals Other.
Primary sort header index

Required if Primary sort header key equals Other.
1184
Secondary sort header key

Secondary sort header index

Required if Secondary sort header key equals Other.
Ensemble sort header key

Ensemble sort header index

Required if Ensemble sort header key equals Other.
Max # traces per output ensemble

Number of traces to hold on disk
1185
SOURCE
Module Description
Parameters
Module Description
SOURCE will allow you to input the source geometry. SOURCE needs two types of information as
follows:
1. Source: This is composed of the the actual or relative location of the shot and the location of the shot
relative to the receiver layout.
2. Pattern: The pattern will describe the receiver layout.
SOURCE is normally run after the STATION program which defines the receiver and midpoint locations.
After SOURCE is run, module GEOM can be run to apply the geometry to the headers. As a replacement
to SOURCE, you can also run the module UKOOA. UKOOA will read a UKOOA formatted tape or disk
data set and write the necessary information to the geometry data base.
For 3-D surveys, SeisUP can support multiple shot lines. Each shot line can reside at a different line
within the area. To scan for the line name with the parameter editor for modules such as SOURCE and
GEOM, first load the flow corresponding the line that actually holds the geometry line. SeisUP keeps a list
at the area level that contains the geometry line name and the line level name where the geometry actually
resides.
Parameters
Shot acquisition type
Land surveys will in addition to marine information ask for the depth, uphole time, and the elevation for
each shot.
Consolidate multiple 3-D shot matrices?

Select Yes to consolidate multiple shot matrices within a 3-D survey. For land surveys, every shot is
normally defined within a single shot matrix, but with a marine survey the geometry is usually split into
shot lines. By specifying Yes to this option the shot ids must be unique only within the shot matrix but the
line name must be specified in GEOM. In addition, each time SOURCE is run with a different geometry
matrix name, the shot matrix will be added to the area level 3-D geometry list. To see the list of lines in
1186
the geometry list run module RT3D.
Scan & process lines option

This parameter only applies if multiple 3-D shot matrices are consolidated for this area. Select Single to
only process a single line. Select All or New to scan all lines within the 3-D survey and find any matrix
files that match the source and pattern specification method. Alternatively, select List to define an ordered
list of source matrices. With the All option, all lines are processed. This option should be used if the
geometry on any shot line was modified that would effect the minimum or maximum coordinates. With
the New option, only lines that have not been previously processed will be processed.
Options: All, Single, New, List
Pattern name same as source name?

If you are scanning all lines within a 3-D survey, then this option lets you define a single pattern name for
the entire survey. Otherwise, SOURCE expects the pattern name to be the same as the source name.
Source specification by
This is the method to specify the shot locations.
Options: Coordinates, Receiver location, Distance from previous shot
This is the method to specify the patterns.
List of source matrices

This option is available when the Scan & process lines option is set to List. Lines will be processed using
only the given ordered list of source matrices.
Matrix Type: SRCMXLST
Source
1187
Source
Land source by coordinate and pattern by receiver location
Source
Land source by coordinate and pattern by spread
Source
Land source by receiver and pattern by distance from source
Source
Land source by receiver and pattern by receiver location
Source
Land source by receiver and pattern by spread
Source
Land source by distance from previous shot and pattern by offset
Matrix Type: SRCDXOFF2
Source
Marine source by coordinate and pattern by distance from source
Matrix Type: SOURCE
1188
Source
Marine source by coordinate and pattern by receiver location
Source
Marine source by coordinate and pattern by spread
Matrix Type: SRCXYSPD
Source
Marine source by receiver and pattern by distance from source
Source
Marine source by receiver and pattern by receiver location
Source
Marine source by receiver and pattern by spread
Matrix Type: SRCRECSPD
Source
Marine source by distance from previous shot and pattern by offset
Matrix Type: SRCDXOFF
Patterns
Pattern by distance from source
1189
Patterns
Pattern by receiver location
Matrix Type: PATREC
Print Shots?
Check for duplicate shot ids in vector

Select the shot spreadsheet vector used to match the shot with the data when GEOM is applied. A
duplicate shot id should not exist within the same spreadsheet when applying geometry to the data. If a
duplicate does exist, the first duplicate shot geometry will be applied. If a duplicate is found, a warning
message will be printed.
Options: Id: This is usually matched with the OIDN (field , FSPN:
This is the shotpoint number
1190
SPER
Module Description
Input Channels
Output Channels
Parameters
Module Description
SPER will compensate for loss of amplitude due to wavefront spreading assuming horizontal layering. The
correction is proportional to the reciprocal of the radius of the spherical wavefront. SPER can apply
corrections based upon near offsets which can be described approximately by 1/[v(t)**2 * t] for P-P data
and Vw/[v(t)**2 * t] for P-SV data. SPER can also upon option apply a more rigorous far offset based
correction that will use ray-tracing to determine divergence factors. This option is not available for
converted wave data.
The velocities input to SPER should be a single RMS velocity function averaged over the survey. If
multiple functions are input, SPER will interpolate the velocity and calculate the correction for each CMP.
If the converted wave algorithm, is used the RMS velocities should be derived via a converted wave NMO
algorithm.
For converted wave data,
References
Newman, P., 1973, Divergence Effects in a Layered Earth: Geophysics Vol. 38, No. 03, P. 481-488.
Input Channels
Output Channels
Parameters
1191
Apply converted wave algorithm?

Select Yes if P-SV data is being input.
PS RMS velocities
If the converted wave algorithm is being used, enter the matrix containing the converted wave RMS
velocity.
Matrix Type: RMSVEL
Weathering velocity determined from

If the converted wave algorithm is being used, a weathering velocity is needed. Select Trace header to get
the weathering velocity from the trace header number 27. If a zero value is in the trace header, a warning
message will appear in the execution status and no amplitude correction will occur. Select Constant to
specify a constant weathering velocity to all traces.
Options: Trace header, Constant
Weathering velocity
Enter a weathering velocity constant to be used for all traces. This parameter is required if the parameter
Weathering velocity determined from: is Constant.
Compute ray-traced correction?

This option is not available for converted wave data.
Apply or remove amplitude correction?

Average geophone interval (m or ft)

This parameter is needed for the ray-traced solution.
RMS velocities
Matrix Type: RMSVEL
1192
RMS reference amplitude

A global scale factor is computed based the first live ensemble. The scale will bring the RMS of the
ensemble to the reference.
Scale factor
If input, this parameter overrides RMS reference amplitude: and allows the data to be processed in
batches with the same scale factor. The default is to calculate the scale factor from the first live ensemble.
In this case the scale factor will also be printed to the execution status. Note - Scale factor: may be quite
small. Use scientific notation, i.e. 1.05872E-09.
1193
SPIKEDIT
Module Description
Input Channels
Output Channels
Parameters
Module Description
This program is used to automatically edit and zero out traces having amplitude which exceeds a running
average over a user-specified number of traces and db level. Those higher than db specified are killed. The
number of traces over which to average amplitude is user-chosen (as traces are read from a given data set).
The window for amplitude information may be fixed, can vary from TIM1 or TIM2 from program
HORIZON, or may be specified in a multi-dimensional spreadsheet having primary and secondary header
keys.
Input Channels
Output Channels
Parameters
db higher than average allowed
db lower than average allowed
SPIKEDIT will compute the absolute value mean over the user specified window (excluding zeros). If the
mean is less than the average from previous traces, this trace will be zeroed from the start of the window
or the trace will be killed depending upon the action parameter below.
Number of traces for average
1194
Print traces exceeding threshold?


Primary header key
TLSN

TLSN
Window times
High amplitude edit option

If "Zero to end" is selected, SPIKEDIT will apply a 100 ms. taper at the high amplitude sample and zero
the trace from that point to the end of the trace.
Options: Kill trace, Zero to end
Low amplitude edit option

If "Zero to end" is selected, SPIKEDIT will apply a 100 ms. taper at the start of the user specified window
and zero the trace from that point to the end of the trace.
Options: Kill trace, Zero to end
1195
Save trace kills in an OMIT matrix

Select Yes to save any traces that are killed or zeroed to a matrix so that they may be viewed, modified, or
applied to a different data set.
OMIT matrix name

Matrix Type: OMIT
OMIT Primary header key

TLSN
OMIT Secondary header key

TLSN
OMIT Tertiary header key

TLSN
Merge with existing OMIT matrix?

Select Yes to merge trace kills from an existing matrix. The default is to delete any existing OMIT matrix
prior to adding any trace kills from this run.
1196
SPRSKID
Module Description
Input Channels
Output Channels
Parameters
Module Description
SPRSKID was designed for the situation where shot points were specified but not receiver locations, and,
the shots were between stations. It is a 2D standalone that moves receiver bin coordinates 1/2 station
distance forward or optionally backward. The input STATION matrix will originally have shot point
coordinates. These coordinates need to be "skidded" to become receiver coordinates. Numerically this
amounts to averaging coordinates of two adjacent stations. Forward skidding moves the first station
towards the last. Backward skidding moved the last station toward the first. After the skid the stations are
written to a new STATION matrix. In the case of forward skid the user will have to add a new end station
to the new matrix. In the case of backward skid the user will have to add a new start station. Elevations are
also skidded and new end point entries will be needed.
Parameters
Input STATION matrix
Output STATION matrix

Skid direction
The station locations may be skidded forward or backward.
Options: Forward, Backward
1197
SPS
Module Description
Input Channels
Parameters
Module Description
Use this module to read Shell Processing Support (SPS) formatted files. SPS will create the receiver
matrix for module STATION along with the shot and pattern file for module SOURCE. After this module
is run perform the following:
1. Setup module STATION by selecting Coordinates for the parameter titled Receiver specification by:
and enter the name of the stations matrix entered below for the parameter titled Stations.
2. Setup module SOURCE by selecting Land for the parameter titled shot acquisition type:. Select
Coordinates for the parameter titled Source specification by:. Select Receiver location for the
parameter titled Pattern specification by:. Enter the name of the source matrix entered below for the
parameter titled Source. Enter the name of the pattern matrix entered below for the parameter titled
Patterns.
3. Enter any other parameters necessary for the modules STATION and SOURCE.
4. Run the modules STATION and SOURCE.
5. Apply geometry by running module GEOM.
References
SEG Technical Standards Committee, Shell Processing Support Format for Land 3-D Surveys.
Input Channels
1. Sps receiver file: Required connection from dataset ASCII data type.
2. Sps shot file: Required connection from dataset ASCII data type.
3. Sps relation file: Required connection from dataset ASCII data type.
Parameters
Prakla PS format?
Select Yes to input a Prakla-Seismos PS (processing support) formatted file. At this time the shot depth
and shot uphole time are not extracted from PS formatted files.
1198
Pre-1990 PS format?
If the parameter Prakla format? is Yes, then select Yes for this parameter to read in a PS formatted file that
is dated before December 1998.
SPS version 2?
IF the parameter Prakla format? is No, then select Yes for SPS version 2.1. This is supposed to be in the
H00 header card image but is frequently missing in one or more of the SPS files.
Stations
This matrix will define the coordinates and elevations for every live receiver in the survey.

Source
This matrix will define the shot information.
Print shots with missing patterns?

Select Yes to print shots that do not have pattern information defined from the relation file.
Delete shots with missing patterns?

Select Yes to delete shots from the shot spreadsheet that do not have pattern information defined from the
relation file.
Patterns
This matrix will define the pattern layout for the shots defined.
Matrix Type: PATREC
Use receiver pndx logic?

Some SPS files have the point index set for receiver positions that were reoccupied but moved. The
receiver location will be set to 10 times the bin plus the point index. The point index will be incremented if
the coordinates do not match a previously found entry. Valid values of the point index are 1 to 9. Select
Yes to use this logic. Select No to use the bin numbers as is. In many SPS files the point index is set to a
constant or a blank. A blank is set to 1.
1199
Are the elevation values reliable?

Some SPS files have been found to have inconsistently entered elevations. Select No if this is the case.
This parameter is used for the warning messages for receiver coordinates.
Horizontal coordinate tolerance

This parameter controls the warning messages for receiver coordinates. If a receiver card is found with
coordinates that differ by more than this parameter, the warning will be printed.
Elevation tolerance
This parameter controls the warning messages for receiver coordinates. If a receiver card is found with
elevations that differ by more than this parameter and Are the elevation values reliable? is set to Yes, the
warning will be printed.
The next couple of parameters were added because the line name fields can be split into subfields. See the
H31x header records to see what to expect. The defaults are the starts are 1 and the ends are 16 for each
field. A fairly common value for the start is 3.
R record line name start

Used if Prakla format? is No.
R record line name end

S record line name start

S record line name end

X record shot line name start

X record shot line name end

1200
X record receiver line name start

X record receiver line name end

1201
SQUEEZE
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module is used to re-scale the PS data set to PP time in order to correlate the horizontal components
with the vertical component. It is important to emphasize that the number of samples is not modified, a
re-assignment of the amplitude location is done.
Input Channels
Output Channels
Parameters
Vp/Vs factor for squeezing the data
1202
SRINTERP
Module Description
Input Channels
Output Channels
Parameters
Module Description
SRINTERP will interpolation source and/or receiver coordinate locations in a user specified direction. To
reduce acquisition costs, contractors will sometimes use coarse receiver or shot grids. This can sometimes
cause frequency smearing and aliasing. In addition one may need to merge multiple 3D projects with
different grid sizes. This module can be used to create new locations to reduce midpoint grid sizes.
If the end goal is to interpolate these new locations this module can be one step in that direction. If the
interpolation module needs dead traces to be replaced by interpolated ones such as by TRIP5D or
LRADON then module GEOM can be used to insert the dead traces once this module has been run. After
this module has been run, enter the new station, pattern and source information. Also remember to enter
the new number of channels per shot that is printed in the print-out when interpolating receivers.
Parameters
Interpolate
Select which coordinate location to be interpolated.
Options: Receivers, Sources
Input receivers
If interpolating receivers enter the input receiver matrix name.
Output receivers
If interpolating receivers enter the output receiver matrix name.
1203
Insert into patterns?

If interpolating receivers, select Yes to append the new receivers to each input pattern.
Input pattern
If inserting into patterns, this is the input pattern matrix.
Matrix Type: PATREC
Output pattern
If inserting into patters, this is the output pattern matrix. New receivers will be place at the end of the
pattern.
Matrix Type: PATREC
Input sources
If interpolating sources enter the input source matrix name.
Output sources
If interpolating sources enter the output source matrix name
Source grid from

SRINTERP will interpolate sources placed on a grid. Choose Midpoint grid to grid the source coordinates
to the midpoint grid. Receiver grid is similar to Midpoint grid except the module will use a receiver grid.
In this case make sure the receiver grid is NOT specified by random coordinates because SRINTERP
needs a fixed grid. When using a Midpoint grid it is possible that sources will be outside the midpoint grid
if default grid specification is being used in STATION. Choose FSPN pattern to extract a source bin and
line using a pattern specification from the FSPN column.
Options: Midpoint grid, Receiver grid, FSPN pattern
FSPN to SSBN(XXX) & SSLN(YYY) pattern

Enter the pattern to be used to specify the source bin(SSBN) and line (SSLN) from the FSPN column of
the source matrix. Use Xs for SSBN and Ys for SSLN. For example, XXXYYY can be used for an
FSPN of 842101 where 842 is the SSBN and 101 is the SSLN.
1204
Interpolation direction
Enter the desired interpolation direction.
Options: Line, Bin
Interpolation ratio
Enter the number of desired coordinate interpolations per input location. Interpolation will be half-way
between existing coordinates in the user specified direction. Interpolation is linear.
Options: 2:1, 3:1, 4:1
Minimum source/receiver interval(ft/m)

Enter the minimum source or receiver interval for new interpolated coordinates.
Renumber all by ratio amount?

If after interpolation the location bin or line number causes duplicates or is not divisible by the
interpolation ratio, then select Yes to multiply all location numbers by the interpolation ratio.
1205
SSDECON
Module Description
Input Channels
Output Channels
Parameters
Module Description
Source signature deconvolution will remove the signature of a known signal from the seismic trace data.
The seismic signal can be considered as the convolution of the source signal with the instruments,
geophones, and the earth response. If the source signature is known or estimated, then it can be removed
from the seismic trace. If the source signature has been recorded through the same instruments and
geophones as the seismic data then the effects of these can be removed, leaving the effects of the earth
response only.
This module can correct for the amplitude and phase of a signature or the phase only. Many times the best
result occurs when the phase only option is used to get the seismic data to minimum phase and then apply
a spiking decon afterward.
Either a time domain or a spectral domain decon can be applied. The spectral domain is much faster than
the time domain but also contains more noise than the time domain.
The input source signature can be input as an auxiliary trace in the record, as a user defined matrix, or as
an ASCII file. The user must identify the auxiliary trace using a GCI header word and an index number.
The user-defined matrix has one column of amplitudes that represent the source signature. The ASCII file
can contain n rows and m columns of amplitude values. The file must contain only source signature
amplitudes, separated by a space.
The user can set a delay for the onset of energy in the source signature. This is a very critical parameter
since the best decon will be when the onset of maximum energy is at the start of the wavelet. Look at the
wavelet and find the maximum amplitude energy, then pick the delay to be just before the onset of this
energy. The length will typically be chosen to be the same length as the seismic data traces.
Notches in the amplitude spectra of the source signature can cause the output data to ring at the notch
frequencies. To remove the ringing and improve the decon results; several method can be employed to
remove the notch affects. One option is to floor amplitude values in the amplitude spectra of the source
signature. If amplitude values fall below the maximum amplitude * floor percentage then that value will
be set equal to the amp*floor value. Other option is to smooth the amplitude spectra over the range where
the notch occur. A trapezoidal smoothing filter can be applied over a specific frequency range. The more
points in the filter, the more smoothing of the notches will occur.
1206
Input Channels
Output Channels
Parameters
Domain for the convolution
The deconvolution can be performed in the time domain or the spectral domain. The spectral domain will
be much faster, but may be noisy. The time domain should produce a cleaner deconvolution but will run
slower.
Options: Frequency, Time
Source signature is stored as a

The source signature can be input as an auxiliary trace in the record, as a matrix defined by the user, or as
an ASCII file.
Options: Aux trace in record, Matrix, ASCII file
Source signature wavelet matrix

If matrix was selected, enter the user-defined matrix that defines the source signature.
Matrix Type: SSDEC
Name of ASCII file (including path)

If ASCII file was selected, enter the file name including path. The file must contain only amplitude values
for the source signature. Any number of columns and row can be input. The amplitude values should be
separated by a space. Examples /seisdata/srcsig.txt, or e/miscdata/srcsig.txt.
Source signature trace header word

This is the trace header word that we will key on to locate the signature trace.
1207
TLSN, other
Source signature trace header index

If other is selected for the header index, then enter the number (word) of the header index that you want
to use.
Source signature trace header value

This is the value of the selected trace header word. Example the trace header word is FCSN (trace number
in original field record. The trace number where is the signature is located is 100. When the ensemble is
read in, the modules locate trace 100 in word FCSN and uses this as the signature trace.
Action if no signature trace in the record

When the source signature trace is not found for an ensemble, select the action to be taken. The choices
are to use the previous signature trace or abort the module.
Options: Abort, Use previous source signature trace
Output the processed source signatures as an auxiliary trace?

The source signature and other processed traces can be output with the normal seismic data as an auxiliary
trace. This trace will be at the end of the record. If the source signature is input as a matrix or ASCII file,
then this trace will be output. The amplitude spectra of the conditioned source signature will be output. If
the minimum phase option was chosen, then the minimum phase equivalent of the source signature will be
output.
Start time for signature wavelet (ms)

Occasionally, the signature is recorded with a delay. You can remove this by entering the delay time in
milliseconds.
Length of the signature wavelet (ms)

Enter the length of the filter window in milliseconds.
Filter correction type

Select to deconvolve for amplitude and phase or just phase.
Options: Amplitude and phase, Phase only
1208
Change source signature to minimum phase?

If phase only was selected above this parameter appears. The phase of the output trace can be forced to
minimum phase using this option. This should be give a good response when performing spiking decon
afterward.
Floor notches in the amplitude spectrum of signature?

Notches in the amplitude spectrum of the source signature can cause ringing in the output data. By adding
a floor value to the amplitude spectrum will provide some stability. The maximum amplitude is found in
the spectrum, any amplitude that falls below maxamp*floor will be set to maxamp*floor.
Amplitude floor (%)

Enter the percentage of the maximum amplitude found in the amplitude spectra of the source signature
that cause the floor to be added. All amplitude spectra values that value below the floor value will be set
equal to the floor value.
Starting frequency (Hz)

Flooring the amplitude spectra of the source signature can be performed over a specific frequency range.
Enter the starting frequency in hertz.
Ending frequency (Hz)

Flooring the amplitude spectra of the source signature can be performed over a specific frequency range.
Enter the ending frequency in hertz.
Smooth notches in the amplitude spectrum of signature?

Notches in the amplitude spectrum of the source signature can cause ringing in the output data. This
option allows smoothing of the notches to take place. The smoothing can be performed over a frequency
range and the amount of smoothing is controlled by the number of points in the smoothing filter.
Number of points in smoothing filter

Enter the number of points for the smoothing filter. More point in the filter will cause the notches to
become less pronounced.
Starting frequency (Hz)

Smoothing the amplitude spectra of the source signature can be performed over a specific frequency
range. Enter the starting frequency in hertz.
1209
Ending frequency (Hz)

Smoothing the amplitude spectra of the source signature can be performed over a specific frequency
range. Enter the ending frequency in hertz.
1210
SSMP
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module SSMP will resample data to a different sample rate using Lagrange interpolation (Time) or
Fourier transform (Frequency). SSMP may interpolate a greater or a lesser sample rate.
An anti-alias filter is included to apply when resampling to a greater sample rate. You can choose between
a minimum-phase or a zero-phase anti-alias filter. The zero-phase filter takes slightly more time but
preserves the data better. Aliasing is a distortion of data that occurs when the period of sampling is greater
than half the period of the seismic data. If you are resampling the data more finely, the anti-alias filter does
not need to be applied. No anti-alias filters are required for Fourier resampling.
Input Channels
Output Channels
Parameters
Output sample rate (usec.)
If the output sample interval is larger than the input, an integral multiple thereof and no anti-alias filter is
chosen, the appropriate samples are simply selected from the input trace.
The output sample interval must be greater than 20 micro seconds.
The ratio of the input to output sample interval must be less than 100.
1211
Apply an anti-alias filter?

Options: Yes, No
Select anti-alias filter phase

Options: Zero-Phase, Minimum-Phase
Resample Domain
Options: Time, Frequency
If the Frequency option is chosen, the input to output sample interval ratio must be a power of 2.
1212
STACK
Module Description
Input Channels
Output Channels
Parameters
Module Description
CMP stack will sum data having common CMP (SDPN) header keys.
Normalization may be division by fold, fold plus an integer, or square root of the fold. If geometry was not
defined, the number of CMPs in the line or dataset must be coded.
Input Channels
Output Channels
Parameters
parameter for other "sort" orders. For example, it needs to be the number of traces within a shot plus the
greatest number of CMPs between shots plus one for shot-ordered data.

# to add to fold before dividing
1213
X-T Taper
This option is used to apply a offset vs. time taper to the traces prior to stack. The taper values applied are
saved in the fold vector so that the stack trace will be properly normalized. This option can be used to
attenuate multiples buy applying a taper to the near offsets. The absolute value of the offset is used. The
default is to not apply an X-T taper.
Matrix Type: XTTAPER

If the geometry is not in the data base, a valid number must be input or the job may abort. If VSP data? =
Yes and there are more than one CMP to be stacked, Number of CMPs in the line should = the number of
CMPs times # of times to repeat the output trace.
Are you inputting stack data?

This feature can be used to stack together multiple stacks with common CMP numbers. STACK will apply
the fold options to the fold value in the trace header, multiply this value to the stack trace, and add the
modified fold value into the fold vector for later normalization.
VSP data?
# of times to repeat the output trace
Required of VSP data? = Yes.
1214
STACK3D
Module Description
Input Channels
Output Channels
Parameters
Module Description
STACK3D performs 3D stack. The input data can be in any sort order after NMO.
Input Channels
Output Channels
1. Dataset to hold partial stacks: Required connection to dataset DNS1 data type.
2. Stacked data to next process: Required connection to next process GCI data type.
Parameters
Restart?
Number of lines in the span
This parameter is used to allocate memory for holding data for output. The size of the memory block is the
number of bins times the number of samples in a trace (including the header) times Number of lines in the
span. If the data in input as 3-D Xbin gathers, set this parameter to 1. Otherwise, set this parameter to the
maximum range of MLINs you expect to see before a MLIN is complete.
1215


X-T Taper
This option is used to apply a offset vs. time taper to the traces prior to stack. The taper values applied are
saved in the fold vector so that the stack trace will be properly normalized. This option can be used to
attenuate multiples buy applying a taper to the near offsets. The absolute value of the offset is used. The
default is to not apply an X-T taper.
Matrix Type: XTTAPER
Are you inputting stack data?

This feature can be used to stack together multiple stacks with common CMP numbers. STACK3D will
apply the fold options to the fold value in the trace header, multiply this value to the stack trace, and add
the modified fold value into the fold vector for later normalization.
Restart data set flush interval (traces)

Enter the number of traces to process before flushing the partial stack data set to disk. The partial stack
data set is used to restart STACK3D if a previous execution of STACK3D aborted or crashed for some
reason.
What to do with traces outside MBIN/MLIN range

Options: nothing, print, abort
STACK3D will only pass to output those traces within the midpoint bin and line range given by the
parameters. If the data does not match the parameters, this parameter permits a warning message or an
abort.
Number to print
This limits the number of traces outside the midpoint bin and line range that are printed out. Required if
What to do with traces outside MBIN/MLIN range equals print.
1216
STATIC
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module STATIC computes and applies high resolution time shifts, or "static" corrections, to seismic
traces. Several application scenarios are available. They are described below. Statics may be applied to the
traces but the trace header will always be updated with the static values. Statics computed may be printed
on the execution listing if desired. Most options allow output of computed static values to a matrix. A
positive static value will push a trace down in time. STATIC options include:
Roll-along
Bulk
Datum
Sequential
Floating to fixed
Update datum only
Apply header value
Combination
Flatten first breaks
Flatten refractor mode
Ensemble Average
CMP Statics
Roll-along.
Roll along statics are shot and receiver statics calculated by another process or entered into a matrix by a
user. These matrix formats are described in "STATSRC" and "STATGEO" documentation. They are
applied to traces based on SGEN and SSPN header word values. If either SGEN or SSPN are not within
the matrix bounds, no static is applied. The static value from each matrix may be modified by a multiplier
and a bias prior to application. The multiplier may be computed from a weathering and sub-weathering
velocity as;
Multiplier = SQRT(( Vsw - Vw) / (Vsw + Vw)) Vsw = Sub-weathering Velocity, Vw = Weathering
Velocity
1217
Bulk
A bulk static shift will be applied to every live trace in the data set.
Datum
Datum statics will shift traces from the acquisition datum, usually the shot and receiver surface elevation,
to a flat or floating "Variable datum". The relevant values for datum static computation, such as station
elevations, must be entered into the data base prior to running "STATIC" if the "Datum" option is
selected. This is also true for options "Update datum only" and "Combination". This is accomplished by
executing modules "STATION" and "SOURCE". The static shifts are computed by:
Ts = ( Elevation datum - Elevation shot + Shot depth) / Replacement velocity
Tr = ( Elevation datum - Elevation rec + Shot depth ) / Replacement velocity - Uphole time .
Ts is the shot static shift. The shot elevation is the elevation of the surface at the shot. If a shot depth is not
supplied for a shot, SSPN, it will be interpolated. Tr is the receiver static shift. The shot depth used at a
receiver location is interpolated from the actual shot depths as is the uphole time. Interpolation is
accomplished by triangulation using x-y coordinates. These shot and receiver statics may be output to
matrices of type "STATSRC" and "STATGEO".
The datum plane may be a floating datum. If a floating datum is chosen, two options are available. The
datum elevation may be computed at each shot, receiver and CMP bin location
"Source/Receiver/Midpoint" or at CMP bin locations only "Midpoint Only". The datum is computed by
smoothing receiver elevations. Shot elevations will also be used if the Use shot and receiver elevations
option is chosen. The size of the smoother may be coded. If "Midpoint Only" is chosen and "Use
Intermediate/Final Datum" is selected, the shot and receiver statics will reflect a shift to the datum
chosen and the CMP static will be the shift to the floating datum. The datum may be biased using
"Constant to subtract from average geophone elevation". The CMP datum elevations will be output to
a matrix named by the user for later processing. Headers are updated with shot (STTS), receiver (STTG),
CMP (HDR(34)) and total (STAT) static values as well as shot (DS), receiver (DG) and CMP (DC) datum
value and uphole time (UTG) and shot depth (WDG) interpolated at each receiver location. Note that
(WDG) is the water depth at the receiver location. The water depth at the shot location (WDS) is set to the
shot depth at the shot (DEPS) for consistency.
If a "Data type" of "PS-Wave" is chosen, static shifts are computed by:
Ts = ( Elevation datum - Elevation shot + Shot depth) / P Replacement velocity
Tr = ( Elevation datum - Elevation rec + Shot depth ) / S Replacement velocity - Uphole time *
Vp/Vs
PS data sets require the datum static shift at the receiver to be made with a subweathering (replacement)
velocity appropriate for shear waves. "S Replacement velocity" is used for the Tr computation. It is also
necessary to convert the uphole time from P-Wave travel time to S-Wave travel time using "Vp/Vs".
1218
If the "Datum" option is chosen and a flat datum plane is to be used, the statics may be computed from
values in the appropriate header words rather than values from the data base. Note that after using module
"GEOM" to apply geometry, only elevations and shot location shot depths and uphole times are in the
headers.
Sequential
This option allows static shifts to be applied to traces based on their sequential order in the matrix
STATSEQ. The value of the header word chosen determines the sequence of the static used for that trace.
The dimension value from the matrix plus 1 represents the index of the first static value entry in the
matrix. The dimension value is an offset to be subtracted from the value in the header word defined by the
header key. Statics are then applied based on correspondents of the de-biased header value to the sequence
of statics in the matrix. If the dimension is 3, a trace with a header word value of 11 will have the 8th static
value from the matrix applied to it. If a trace header word value is 34, the 31st static will be applied. The
total static header word will be updated.
Floating to fixed
The conversion from a floating to a flat datum uses the sub-weathering velocity and shot and receiver
datum elevations previously stored in the trace headers by STATIC. These headers are HDR(27), DS and
DG respectively. If the "PS-Wave" "Data type" is selected, the shifts for shot and receiver paths will
computed using the sub-weathering velocity from the trace headers and the coded "S Replacement
velocity" respectively. If the "Treat data as stacked" flag is set to "Yes", the CMP floating datum header
word (DC) is used for both shot and receiver correction.
Update datum only

The floating datum computation above is made and inserted in the header words DS, DG and DC. No
statics are applied. The CMP datum values are written to a matrix.
Apply header value

The value stored in the selected trace header word is treated as a static shift. The shift is assumed to be in
milliseconds.The header value may be modified by a multiplier and a bias prior to application. The
multiplier may be computed from a weathering and sub-weathering velocity as;
Multiplier = SQRT(( Vsw - Vw) / (Vsw + Vw)) Vsw = Sub-weathering Velocity, Vw = Weathering
Velocity
Combination
This option applies statics computed by GLI3D and shifts the data to a floating datum plane. The GLI3D
statics are input in "STATSRC" and "STATGEO" matrices. In principle, any static set designed to
correct the data set from the surface to a known flat datum could be used. Values used for the replacement
velocities and datum elevations should match those used to compute the flat datum static set. A set of
datum statics from the surface to the floating datum are computed as a by-product. They may be output to
1219
matrices or ignored. The option performs the following sequence:

1. Compute the floating datum elevations as above.
2. Compute the statics to move the data from a flat datum to the floating datum.
3. Add these statics to the GLI3D statics and shift the data.
This is almost equivalent to:
1.
2.
3.
4.
"Update datum only".

"Roll-along" to apply GLI3D statics.
"Floating to fixed" with "Reverse the sign of the statics" = "Yes".
"Update datum only".
The refraction statics are applied and the data shifted to a floating datum. The datum elevations are in the
trace headers. The statics needed to move the data from the floating datum back to the surface may
optionally be output as noted above.
To get back to a flat datum, do either:
1. "Floating to fixed".
or, if "Source/Receiver/Midpoint" is used,
1. "Datum" to the desired flat datum.
2. "Roll-along" with "Reverse the sign of the statics" = "Yes". Use the optionally output statics from
the "Combination" option as noted above.
or, if "Midpoint Only" used,
1. "Apply Header Value" from HDR(34) using "Reverse the sign of the statics" = "Yes".
Flatten first breaks

This option simply shifts traces by the first break pick stored in the matrix coded in "First break picks".
The shifts are biased by the time entered in "Time to place first breaks".
Flatten refractor mode

The static shift for each trace is computed from the offset/time function in the matrix coded for "Refractor
model". This matrix is usually created by module RFS1. Static shifts for offset values found in header
word "DIST" not specified in the matrix will be interpolated or extrapolated.
Ensemble Average
The same static shift is applied to each trace in the ensemble. The static is computed by averaging header
word STAT from each trace. STAT is the total static applied to each trace. The shift is stored in HDR(34).
1220
CMP Statics
A static shift may be applied based on CMP location, that is MLIN and MBIN. The static shifts are input
in the "First Break Picks" matrix "AFS1B". The primary dimension in the matrix is ignored. The
secondary dimension is used for MLIN. The row number is MBIN. Values are interpolated for CMP
locations that are not input, that is the matrix cell is blank. The shift is accumulated into header word
HDR(34).
Input Channels
Output Channels
Parameters
Static type
Options: Roll-along, Bulk, Datum, Sequential, Floating to fixed,
Update datum only, Apply header value, Combination, Flatten first
breaks, Flatten refractor model, Ensemble Average, CMP Statics
Geophone statics
Required if Static type: = Roll-along. Static shifts are assumed to be in milliseconds.
Shot statics
Required if Static type: = Roll-along. Static shifts are assumed to be in milliseconds.
Factor by
Required if Static type: = Roll-along.
1221
Options: Multiplier, Velocities
Sub-weathering Velocity
Required if Static type: = Roll-along and Factor by: = Velocities.
Weathering Velocity
Required if Static type: = Roll-along and Factor by: = Velocities.
Static Value Multiplier

Required if Static type: = Roll-along and Factor by = Multiplier.
Static Value Bias(ms)

Required if Static type: = Roll-along.
Bulk static (ms.)

Required if Static type: = Bulk.
Datum Statics Source

Required if Static type: = Datum.
Options: Database, Headers
Data Type
Required if Static type: = Datum.
Options: P-Wave, PS-Wave
P Replacement Velocity
Required if Static type: = Datum. Enter the replacement velocity for datum statics.
S Replacement Velocity
Required if Data type: = PS-Wave. Enter the replacement velocity for datum statics.
1222
Vp/Vs for Uphole Time Conversion

Required if Data type: = PS-Wave.
Variable datum
Required if Static type: = Datum and Datum Statics Source: = Database.
Float datum at
Required if Variable datum = Yes and Datum Statics Source: = Database.
Options: Source/Receiver/Midpoint, Midpoint Only
Use Intermediate/Final Datum?

Required if Float datum at: = Midpoint Only.
Datum Elevation
Required if Static type: = Datum and Variable datum? = No or Use Intermediate/Final Datum? = Yes or
Datum Statics Source = Headers.
# to subtract from average geo. elevation

Required if Static type: = Datum and Variable datum? = Yes. If a variable datum is chosen, this number
will be subtracted from the computed variable datum values. The computed variable datum is the average
geophone elevation within a circle.
Radius of elevation window (Feet or Meters)

Required if Static type: = Datum and Variable datum? = Yes. This parameter defines the radius of the
circle over which an average geophone elevation is computed for the variable datum. If no geophones fall
within the circle, the nearest geophone will be used.
Use Shot and Receiver Elevations

Required if Static type: = Datum and Variable Datum = Yes. This parameter controls which surface
elevations are used in the floating datum computation.
Options: Yes, No
1223
Print computed statics?

Required if Static type: = Datum and Static Source: = Database.
Output statics to a matrix?

Required if Static type: = Datum. Choose "Yes" to save the computed statics to a matrix so that they may
be used for other reasons such as plotting.
Output geophone statics

Required if Output statics to a matrix? = Yes. Static shifts are assumed to be in milliseconds.
Output shot statics

Header key
Required if Static type: = Sequential.
TLSN, other
Header GCI index

Required if Header key = other.
Sequential statics
Required if Static type: = Sequential. Static shifts are assumed to be in milliseconds.
Matrix Type: STATSEQ
Datum Elevation
Required if Static type: = Floating to fixed.
1224
Treat data as stacked?

For unstacked data, the static computation to convert a floating datum to a fixed datum uses the average of
the shot and geophone datum elevations. For stacked data, the datum elevation at the CMP is used.
Datum Floated at
Options: Source/Receiver/Midpoint, Midpoint Only
P Replacement velocity
Required if Static type: = Update datum only. Enter the replacement velocity for datum statics.

Required if Static type: = Update datum only. This number will be subtracted from the computed
variable datum values. The computed variable datum is the average geophone elevation within a circle.

Required if Static type: = Update datum only. This parameter defines the radius of the circle over which
an average geophone elevation is computed for the variable datum. If no geophones fall within the circle,
the nearest geophone will be used.

Required if Static type: = Update datum only.

Required if Static type: = Update datum only. Choose "Yes" to save the computed statics to a matrix so
that they may be used for other reasons such as plotting.

1225
Output shot statics

Header containing static to apply

Required if Static type: = Apply header value. Static shifts are assumed to be in milliseconds. The header
value is treated as a static value to be applied. none is not a valid selection.
Options: none, STTS, STTG, STTC, STAT, TIM1, TIM2, other
Header GCI index

Required if Header containing static to apply = other.
Factor by
Required if Static type: = Apply header value.
Options: Multiplier, Velocities
Sub-weathering Velocity
Required if Static type: = Apply header value and Factor by: = Velocities.
Weathering Velocity
Required if Static type: = Apply header value and Factor by: = Velocities.
Header Value Multiplier

Required if Static type: = Apply header value and Factor by = Multiplier.
Header Value Bias(ms)

Required if Static type: = Apply header value.
Geophone statics
Required if Static type: = Combination. Static shifts are assumed to be in milliseconds.
1226
Shot statics
Required if Static type: = Combination. Static shifts are assumed to be in milliseconds.
Datum Elevation
Required if Static type: = Combination.
P Replacement velocity
Required if Static type: = Combination. Enter the replacement velocity for datum statics.

Required if Static type: = Combination. This number will be subtracted from the computed variable
datum values. The computed variable datum is the average geophone elevation within a circle.

Required if Static type: = Combination. This parameter defines the radius of the circle over which an
average geophone elevation is computed for the variable datum. If no geophones fall within the circle, the
nearest geophone will be used.


Required if Static type: = Combination. Choose "Yes" to save the computed statics to a matrix so that
they may be used for other reasons such as plotting.

Output shot statics

1227
Treat data as stacked?

For unstacked data, the static computation to convert a floating datum to a fixed datum uses the average of
the shot and geophone datum elevations. For stacked data, the datum elevation at the CMP is used.
Time to place flattened first breaks(ms.)

Required if Static type: = Flatten first breaks
First break picks

Required if Static type: = Flatten first breaks. Static shifts are assumed to be in milliseconds.
Matrix Type: AFS1B
Time to place flattened refractor model(ms.)

Required if Static type: = Flatten refractor model
Refractor model
Required if Static type: = Flatten refractor model. Static shifts are assumed to be in milliseconds.
Matrix Type: RMOD
Matrix name to store CMP floating datum

Required if Static type: = Datum or Static type: = Update datum only or Static type: = Combination.
This matrix is currently used for QC purposes only.
CMP Statics Matrix(AFS1B)

Required if Static type: = CMP Statics.
Matrix Type: AFS1B
1228
Static Value Multiplier

Static Value Bias(ms)

Apply statics to
STATIC will always add the statics to the proper trace header fields. Optionally the user can select not to
apply the static to the seismic trace.
Options: Headers & traces, Headers only
Reverse the sign of the statics

Remove instead of apply the static.
Option for 2D data

Required if Static type: = Datum,Update datum only or Combination and Datum Statics Source =
Database. Ignored for 3D data. STATIC computes the shot statics from the shot elevations, hole depths
and uphole times. The hole depths and uphole times are interpolated to the geophone locations.
Historically, 2D lines were set up where the X coordinate was the inline direction and interpolating in X
was entirely reasonable. This may not be true now, especially with crooked lines. The Y coordinates were
used as a secondary value.
Options: Use X coordinates, Use Y coordinates, Use 3D logic
The Use 3D logic option may be more robust.
1229
STATINTP
Module Description
Input Channels
Output Channels
Parameters
Module Description
If GLI (Hampson-Russell) refraction statics are computed on a decimated shot dataset, the resulting output
geophone statics may have missing values. STATINTP inputs long wavelength geophone and/or shot
statics and fills in the missing geophone values by spatial interpolation or nearest neighbor borrowing.
Parameters
Statics use for geophone interpolation
Missing geophone statics may be computed in 3 ways. 1) Use known geophone values only, 2) use both
shot and geophone values, and 3) use shot statics only. Usually option 1 is used. Only in rare cases will
options 2 or 3 be justified. Select which statics option to use.
Options: Only geophones, Geophones and Shots, Only shots
Input low frequency SHOT static

If an option needing shot statics was selected chose the long wavelength SHOT statics matrix.
Input low frequency GEOPHONE static

If an option needing geophone statics was selected chose the long wavelength GEOPHONE statics matrix.
Interpolated low frequency geophone static

Type an output GEOPHONE statics matrix name.
1230
Interpolation method
Missing geophone statics may be spatially interpolated from existing shot and/or geophone statics, or, the
nearest value taken. Select triangularization (interpolation) or Nearest neighbor.
Options: Triangularization, Nearest neighbor
1231
STATION
Module Description
Parameters
Module Description
Run STATION to define the receiver and midpoint information.
Parameters
Azimuth angle for grids to the inline direction
be established. The azimuth angle is the angle of the survey from the X-axis (from east to north) to the
inline shooting direction. A positive angle will rotate the survey clockwise. Proper rotation will result in
less computations and fewer bins.
Show parameters for

Inline shooting direction from the origin

If a receiver or midpoint grid is defined, enter the direction from the origin used to define the inline or
MBIN/RSBN direction. As an example, if the azimuth angle is zero and the inline shooting direction is
counter-clockwise, then the MBINs will increase from the west to the east. If the inline shooting direction
is clockwise then the azimuth angle should be 90 degrees, the MBINs will increase from the south to the
north and the MLINs will increase from the west to the east.
1232
This is the default orientation. Azimuth angle for grids of 0 and Inline shooting direction from the origin of
Counter-clockwise.
Azimuth angle for grids of 90 and Inline shooting direction from the origin of Counter-clockwise.
1233
Options: Counter-Clockwise, Clockwise
Choose "Grid" to overlay a receiver grid over the survey. Choose "Coordinates" to specify the actual
coordinates for every live receiver. Usually "Grid" is chosen for a marine survey while "Coordinates" are
usually used when a SEG-P1 file is available.
Stations
This matrix will define the coordinates for every live receiver in the survey.
1234
Average inline receiver interval

Average crossline receiver interval
Print receivers?
Select "Yes" to print the X , Y, elevation, geophone interval, change in elevation, and azimuth from the
previous receiver. This option can only be used if the coordinates are specified in a station matrix.

Code the receiver interval in feet or meters along the X-axis after rotation of the survey.

Code the receiver interval in feet or meters along the Y-axis after rotation of the survey.

A default origin will be calculated from the minimum X and Y coordinates in the survey.

Inline receiver number at the origin
This will be the first receiver bin number.
Crossline receiver number at the origin

This will be the first receiver line number.

The default will be to calculate the number of receiver bins from the maximum X and Y coordinates.

Station elevations
Code this matrix if a receiver grid was specified. The default is zero for all elevations.
Matrix Type: STAELEV
1235
Midpoint determined by
Choose Grid to overlay a midpoint grid over the survey. Choose S+G to specify the midpoint number as
the receiver closest to the shot plus the receiver number. With S+G the CMP number is two times the
geophone number. Choose Coordinates to define a crooked CMP line. Use options S+G or Coordinates
when the receivers are specified by coordinates. Options S+G and Coordinates are not available for 3-D
surveys.
Options: Grid, S+G, Coordinates

Code the midpoint interval in feet or meters along the X-axis after rotation of the survey. For midpoint
lines determined by S+G or Coordinates, this is the midpoint interval along the defined CMP line.

Code the midpoint interval in feet or meters along the Y-axis after rotation of the survey. For midpoint
lines determined by Coordinates, this is the CMP bin size perpendicular to the midpoint line.




coordinates.
1236
Midpoints
Enter the matrix name containing the coordinates of the corner points for a crooked CMP line. This option
is only available if option Midpoint determined by: is Coordinates.
1237
STKSNR
Module Description
Input Channels
Output Channels
Parameters
Module Description
STKSNR provides a flexible beam random noise attenuation for 2D and 3D stack (or offset) volumes. For
any trace target sample, a gate of samples (half above and half below this target sample) is used to track
the target sample on surrounding traces. A new sample is constructed from weighted tracked samples.
Output from exponential weighting scales each tracked sample (including the target) by e**(- PI *
dist**2) before summing. Alpha-trim mean output means sorting all the tracked samples then averaging
only the middle samples. Semblance output is the target sample weighted by the semblance coefficient
computed from all tracking gates. NOTE: STKSNR must follow READ in the flow AND a connection
pipe is required from the input dataset to STKSNR.
Input Channels
2. Direct: Required GCI data type.
Output Channels
Parameters
Beam xbin width in CMPs
This is the X length of the beam in bins (odd).
Beam ylin width in CMPs

For 3D this is Y height of the beam in bins (odd). For 2D this value is 1.
1238

Enter a gate length enclosing about 2 cycles of amplitude variation.

This maximum shift value restricts the tracking to the best local match.
Output statistic?
The output samples are constructed as described in the Module Description (above). For high signal to
random noise ratios exponential may be best. The strongest cleanup will be achieved with a 0% alpha-trim
mean (average). The semblance output will be dominated by ONLY coherent events.
Options: Exponential weight, Alpha-trim weight, Semblance weight
Alpha-trim mean percent

If Alpha-trim weight is selected for Output statistic? enter the alpha-trim mean percent.
1239
STRETCH
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use module STRETCH to stretch or compress a seismic trace. The number of samples per trace is not
modified.
Input Channels
Output Channels
Parameters
Stretch factor (ms./sec.)
Make this number negative to compress the traces.
1240
STRM
Module Description
Output Channels
Parameters
Module Description
STRM is a process which will create a plot of the streamer shape and shot locations for a 3-D Marine
coordinate database. All lines may be created or a matrix of lines to include or exclude may be defined.
Plotting scale defaults to "auto" but the following scales may be selected:
1:250,000
1: 62,500
1: 50,000
1: 24,000
1: 12,500
"Other" allows the user to enter his own. Shot symbol and shot annotation increments are user-chosen.
Execution generates a CGM disk file.
Output Channels
1. CGM Output: Connection to CGM disk file
Parameters
Draw lines

Matrix Type: LINES
Plotting scale
1241
Enter user scale

Shot symbol increment
Shot annotation increment
1242
STTINTP
Module Description
Parameters
Module Description
STTINTP can be used to interpolate statics. This module can be used where a user calculates statics for a
subset of the survey and then then the user wishes to interpolate the statics for the rest of the survey or
even a subset of the survey specified by midpoint bins. Interpolation is carried out with triangulation
using all non-zero input statics.
Please note that this module assumes a static of 0.0 msec is a missing value. Statics normally are expected
to be randomly distributed about zero so at least occasionally a good static will be replaced. Another
problem is that the interpolation is done by x and y location. If a shot or geophone reoccupies a location,
the first static will be replaced with the second. Please inspect the input and output.
Parameters
Input station static matrix name
Input shot static matrix name

Output station static matrix name

Output shot static matrix name


1243

1244
SUBSEGY
Module Description
Input Channels
Output Channels
Parameters
Module Description
SUBSEGY performs simple mathematical operations on two SeisUP data sets. Data set 1 is from a
previous process. Data set 2 is from a GCI data file. The two data sets must have the same sampling rate,
the same number of samples and the same trace headers. The program compares
SDPN,SGEN,SSPN,DIST and TLSN numbers between the two data sets. Any discrepancy in one of the
above will cause the program to terminate abnormally.
A shaping filter may be derived and applied to data set 1. In this case the user needs to specify a derivation
window for the filter. The program will compute the optimal filter which can transform data set 1 into data
set 2 on a per-trace basis. The filter is then applied to each trace in data set 1 before computing the
differences.
The Arc Tangent computation assumes the "Data set to subtract" is the denominator of the tangent and
the "Seismic input" is the numerator or X and Y, respectively, in Cartesian coordinates. Angles computed
by the Arc Tangent option are in radians and assume traditional Cartesian polarity.
Input Channels
2. Data set to subtract: Optional GCI data type.
Output Channels
1. Difference traces: Optional connection to next process GCI data type.
Parameters
Shaping filter
1245
Start of derivation window (ms)

Required if Shaping filter: = Yes.
End of derivation window (ms)

Filter length(ms)
Dataset operation
Multiply by ABS, Arc Tangent
Scale factor to apply to the secondary input

Compare trace headers?
Allow seeking capability to second dataset?
1246
SURFWAVE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Surface Wave Removal can attenuate surface wave noise by mixing adjacent traces and performing
horizontal correlation filtering in the frequency-space domain.
The module transforms the data to the frequency-space domain. A frequency dependent mix of adjacent
traces is performed. Horizontal correlation filtering is done at each frequency for the specified surface
wave velocity. The filtered data is then returned to the time-space domain. Frequency components above
the high cutoff frequency are unchanged.
The input velocity should be the apparent velocity of the surface wave. Typically, this can be measured
from the traces that are in-line to the source.
This module will work on 3D datasets, by sorting the data based upon the MLIN (midpoint line) or RSLN
(receiver line) header word. For shots, the typical line selection criteria will be RSLN. Each group of
traces within the ensemble with the same MLIN/RSLN will be filtered together. A new apparent velocity
is computed for lines that are not in-line to the source.
Under some circumstances, better noise attenuation is achieved by applying a gain function to the data
before running this module.
Selecting the proper high cutoff frequency is essential to removing the noise without also altering the
seismic signal.
Input Channels
Output Channels
1247
Parameters
Velocity of the surface wave
Specify the apparent velocity of the noise wave to attenuate in ft/sec or m/sec. Typically this value is the
true velocity of the noise wave.
Lowest frequency of surface wave (hz)

Specify the lowest frequency in hertz for the noise wave to attenuate. Typically, this should be zero.
Highest Frequency of surface wave (hz)

Specify the highest frequency in hertz for the noise wave to attenuate. Typically, this should not exceed
25-30 hertz. This value must be chosen very carefully, so that we attenuate the noise without altering the
true seismic signal.
Blending bandwidth (hz)

Specify a blending bandwidth in hertz to preserve continuity at the high frequency cutoff.
Header word for 3D line breaks

This module will work on 3D datasets. The traces must sorted based upon the MLIN (line number) or
RSLN (receiver line number ) header word. To properly filter 3D data, make sure that the MLIN/RSLN is
defined for each trace. By selecting NONE, no sorting is performed and all traces in the ensemble will be
filtered together.
For shot sorted data, typically the RSLN header word is chosen to break lines. For midpoint gather data,
the MLIN may be a better choice.
Options: MLIN, RSLN, NONE
Maximum number of traces to mix

Specify the maximum number of traces mixed at the low frequencies. The default is to use all traces in the
sort. At each frequency the number of traces in the mix is:
Mix = velocity / ( frequency * trace offset )
1248
SURMAT
Module Description
Input Channels
Output Channels
Parameters
Module Description
SURMAT inputs two prestacked or stacked datasets, co-located, that should visually match and displays
the trace groups next to each other. The stacks of the two datasets is computed and displayed (replicated)
to the right of the raw input data.The user selects the Match Zone menu button then with MB1 (mouse
button 1) clicks and drags a box over the datasets to select a time zone for analysis. When MB1 is
released, the zone of interest turns green and the cross-correlation of the stacks is computed and displayed.
If the two datasets were identical, the cross-correlation trace would be symmetrical with respect to the
center positive lobe. Typically the datasets are time shifted and have phase differences that affect the
symmetry of the cross-correlation. Frequency differences may be eliminated by filtering each input to the
same bandwidth before input to SURMAT. Different analysis zones may be selected just by repeating the
above procedure. The user may invoke a phase and time shift analysis by selecting the Filter menu button.
A dialog will appear with 3 options. Select option 1 - Phase filter target. Another dialog will appear asking
for the Phase angle increment in degrees. A typical value is 1. After a response is typed in and OK clicked,
the program computes cross-correlations phase shifted by the specified accumulated angle increment. The
resulting correlations are scanned for the maximum peak amplitude and the solution reported in the
EXECUTION STATUS as a best time shift in samples and the phase angle. This solution is applied to the
target dataset and displayed next to the reference dataset for visual examination. The process can be
repeated for another analysis zone by re-selecting the analysis zone and re-running the phase-shift
analysis. Best results are obtained when the correlation appearance is consistent over all analysis windows.
Input Channels
1. Reference: Required connection from dataset GCI data type.
2. Target: Required connection from dataset GCI data type.
Output Channels
1249
Parameters
Number of traces in REFERENCE dataset:
Number of traces in TARGET dataset:
Amplitude smoother length (ms):
1250
SWAP
Module Description
Input Channels
Output Channels
Parameters
Module Description
SWAP is used to "swap" or interchange the position of header keys to output data for use on other systems
requiring keys in different header word locations. As many as 4 "swaps" may be done in one job; to run
more than 4, initiate another "swap" application module.
Input Channels
Output Channels
Parameters
From header 1
To header 1
From header 2
To header 2
From header 3
To header 3
1251
From header 4
To header 4
1252
SYNDIP
Module Description
Input Channels
Output Channels
Parameters
Module Description
SYNDIP can be used to create constant velocity pre-stack 2-D or 3-D synthetic CMP or shot gathers. The
gathers can be generated for Planar events (horizontal and dipping) and Point Diffractor events. The user
can include either of these two type of event, or include both of them.
The user can specify the following attributes for each Planar event:
Midpoint Location
Time Location
Dip
Azimuth
Intercept (P) or Normal Incidence Reflection coefficient
Gradient (G)
The Midpoint Location is the spatial midpoint location (MBIN and MLIN) where the Planar event is
placed at the time given by Time Location, in a zero-offset time section. The Dip is the dip of the planar
event, and the Azimuth is the azimuth of planar event (measured in degrees, and clockwise from due
North). The Intercept (P) and Gradient (G) are used to compute the reflection coefficient based on the
approximation to the Zoepritz equations, as given by Shuey (1985).
The user can specify the following attributes for Point Diffractor events:
Midpoint Location
Time Location
The Midpoint Location is the spatial midpoint location (MBIN and MLIN) where the Point Diffractor
event is placed at the time given by Time Location, in a zero-offset time section.
The user has the option to specify data by midpoint and offset or by using shot records within the SeisUP
geometry database. Within a CMP the user can specify the distance between the source and receiver
(offset) and the azimuth of the source-receiver line.
Parameters
1253

Peak frequency of the wavelet
Velocity
Input the constant velocity for the medium in feet or meters.
Type of Events to include?

Options: Dipping, Both Dipping and Point Diffractors, Point
Diffractors
Dipping Events
Required if Type of Events to include? equals either Dipping or Both Dipping and Point Diffractors.
This spreadsheet will define the attributes for each planer event in the data set
Matrix Type: SYNDIPS
Point Diffractors
Required if Type of Events to include? equals either Both Dipping and Point Diffractors or Point
Diffractors.
This spreadsheet will define the attributes for each point diffractor event in the data set
Matrix Type: SYNDIFF
Data specification
Select Matrix to specify offset and azimuth for every CMP. Select DB to output shot records via the
geometry database
Options: Matrix, DB
Offsets and Azimuths

This spreadsheet will define the source-receiver offset and azimuths.
Matrix Type: SYNDIPOA
1254

References
Shuey, R. T., 1985, A simplification of the Zoepritz equations: Geophysics, 50, 609-614
Modified on Jun 5, 2001 by Riju John
1255
SYNTH
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module SYNTH computes a normal incidence synthetic seismogram from digital well log data. Two
computation options are available.
The "Sum" computation method accumulates travel time until a multiple of the output sample interval is
reached. The interval velocity in that interval is calculated from the depth traversed in this time interval.
This interval velocity sequence is then used to compute the reflection coefficient series.
The "Sync" computation method is not yet implemented.
The "Datum Velocity" static shifts the output seismogram as if this were the velocity above the first log
value.
Input Channels
Output Channels
Parameters
Output sample rate (usec.)
Output length (msec.)
Computation Option
Options: Sum, Sync
1256
Datum velocity
Header Word containing Trace ID
TLSN, other
Header ID Index for Trace ID

Required if Header Word containing Trace ID equal other.
Header value for depth trace

Header value for delta time trace
Header value for density trace
1257
TAUF
Module Description
Input Channels
Output Channels
Parameters
Module Description
TAUF is a module which can suppress linear noise in a time- and-space variable fashion. It solves for the
transform in the frequency domain and the transform is determined in a least-squared-error sense for each
frequency. Because TAUF does the tau-p transform in least-squared- error sense, it preserves the
frequency content of the data as well as reduces the random noise. Compared to the direct linear
summation plus Rho filtering method, this algorithm suppresses random noise and does not tamper the
amplitude spectrum.
TAUF can be applied on post stack data. The offset for poststack data is created using the CMP
coordinates. These coordinates are GCI internal words MCX and MCY. For data not processed with
SeisUP these words have to be filled before TAUF. When assigning coordinates to these headers a scale of
10 should be applied to be consistent with GCI format.
Large input ensembles can be partitioned to improve efficiency and sometimes quality. TAUF is an
ensemble base module. Make sure the MAX_ENSEMBLE parameter in exec.conf is sufficiently large to
contain the largest ensemble.
TAUF can be sped up by specifying a larger "p sampling factor". Too large a "p sampling factor" leads to
too few modeled linear events for the time window. This can cause the amplitude not to be preserved.
Dip definition:
The dips are defined by the moveout on the reference far offset. Negative indicates the time of the event
decreases with offset and positive means the time of the event increases with offset.
Input Channels
Output Channels
1258
Parameters
Maximum # of channels/ensemble
Reference far offset(RFO)
This usually is the far offset of the data set, but it does not has to be. This reference offset is used to define
the dips, i.e. a dip is described by the linear moveout on this offset. For post stack data and partitioning,
the reference far offset should be the CMP interval times number of traces per panel plus number of traces
to overlap.
Min. dip in data(ms @ RFO)

This should be (50 ms) less than the minimum dip which the user wants to preserve in the data.
Max. dip in data(ms @ RFO)

This should be (50 ms) larger than the maximum dip which the user wants to preserve in the data.
Space-time variant?
Low cut dip (ms @ RFO)
Low pass dip (ms @ RFO)
High pass dip (ms @ RFO)
High cut dip (ms @ RFO)
Header to add to window start
Primary header key

TLSN
1259

TLSN
Dip filtering windows

Matrix Type: TAUF
Low frequency (Hz)

High frequency (Hz)
Regular geometry?
If yes TAUF will allocate enough memory to save the operator for the later ensembles. This will speed
up the computation, but it requires an order of magnitude more memory (number of discrete frequencies
times). Choose no if you only have one ensemble.
Near offset
Offset pattern
Offset increment
To model
Options: Noise, Signal
Random noise stackback (%)

This is the percentage of the data out of the transform domain, to be added back to the output when the
signal is modeled. This option is off when noise is modeled.
To output
Options: Seismic gather, Tau-P transform, Q.C. panel
1260
p sampling factor (times default)

The default p value is determined by the high frequency and the sampling thereon. However, the p
sampling interval can be a few times larger because the dominant frequency is substantially lower than the
high frequency and because the default is determined on the far offset trace. For example,512 traces with
60 Hz high frequency and 30 Hz dominant can obtain acceptable quality with p sampling interval FOUR
(4) times larger than the default. This means a 16 times speed up. The speed up may be even more if
default p interval value entails memory paging. This factor is designed for high fold or stack data. For low
fold prestack data, the result may be sensitive to the factor. The default is suggested to be used since
TAUF is quite efficient for low fold with the default.

Partition the input ensemble?
The input ensembles can be partitioned to speed up execution or to have better quality in removing
localized linear events.
Number of traces per panel?

|<--Number of traces per panel->|<-overlap->|<-Next Panel
|-------------------------------|...........|
|
|-------------------Each round, TAUF will move forward number of traces per panel
plus number of traces to overlap.
Number of traces to overlap?

See above sketch for meaning.
1261
TAUPDMO
Module Description
Input Channels
Output Channels
Parameters
Module Description
This program performs dip move-out (DMO), outputting either stacked or unstacked "common offset"
seismic data. If common offset sorted data is input to TAUPDMO, the output will also be common offset
sorted with DMO applied. See the module DMODIST for further details.
The tau-p domain is essentially a dip decomposition of the seismic data. P values correspond to constant
dips, and tau values correspond to times. The range of P values is controlled by maxdip, the maximum dip
specified in the TAUPDMO parameter section. The individual seismic samples are mapped into the tau-p
domain based on the trace position, offset, and sample time. Then the tau-p data are inverse transformed
back into the time-distance domain and the resulting DMOed section is output to the data flow.
Input Channels
Output Channels
Parameters
Minimum CMP
The lowest CMP number that contributes to the output. Can be lower than the lowest CMP in the data
flow, including a negative CMP number, to allow "padding".
Maximum CMP
The highest CMP number that contributes to the output. Can be higher than the highest CMP in the data
flow, to allow "padding".
1262
CMP interval
The distance between CMPS, in the same units as the offset and velocity.
Minimum offset
Only the offsets between the minimum and maximum will be DMOed
Maximum offset
Only the offsets between the minimum and maximum will be DMOed
Maximum dip
The maximum dip in degrees after DMO. This controls the maximum P limit for processing.
Velocity
For constant velocity DMO, the velocity is used only to convert the maximum dip into units of traces and
time samples. Use the RMS velocity at the center of the zone of interest. For Velocity gradient DMO, the
velocity is used in the actual DMO computations, so use the velocity at the earths surface.
Dmo with velocity gradient model?

TAUPDMO can DMO the seismic data based upon a constant velocity model, or use a model based on a
linear change of velocity with depth. The velocity gradient correction takes significantly longer to apply.
Velocity gradient value

Set only if "Dmo with velocity gradient model?" = "Yes"
P Control
The number of slowness values (and the slowness increment) can be controlled one of three ways. The
conservative choice is "No Spatial Aliasing" which computes a slowness increment based on the range of
CMP positions and the maximum frequency in the data. With the slowness increment and the maximum
slowness (which is based on the maximum dip and the velocity), the number of slownesses is fixed.
Another option is to set the number of slownesses to equal the number of CMPs, which is helpful when
outputting the tau-p section to filter or analyze further. The third option is to set the number of slownesses
manually.
Options: No Spatial Aliasing, Same # as CMPS, Set Manually
1263
Number of P values
Set only if "P Control" = "Set Manually"
Data type to output

The program can either perform the full DMO process, and output CMP data, or output only the tau-p data
("Slowness Intercept") for diagnostic purposes and/or filtering. If producing CMP data, you may select
only those CMPS which were input, possibly leaving gaps, or all the CMPs in the range so the gaps are
filled in with DMOed data.
Options: Same CMPS as Input, All CMPS in Range, Slowness Intercept
Low cut frequency

The inverse tau-p transform is performed in the frequency domain. Setting frequency limits will speed up
the inverse transform, but also bandlimit the output. The low cut frequency is the absolute lower limit, no
frequencies below this will be passed.
Low pass frequency

The low pass frequency is the low end of the unfiltered output spectrum. Frequencies between the low cut
and the low pass are partially filtered.
High pass frequency

The high pass frequency is the high end of the unfiltered output spectrum. Frequencies between the low
pass and the high pass are unfiltered in the output.
High cut frequency

The high cut frequency is the absolute upper limit, no frequencies above this will be processed.
Normalize output by fold?

Normalization technique
Required if Normalize output by fold? = Yes.
1264

Required if Normalize output by fold? = Yes and Normalization technique = fold plus next parm.
1265
TCOPY
Module Description
Parameters
Module Description
Parameters
Maximum number of K-bytes per record
1266
TDAF
Module Description
Input Channels
Output Channels
Parameters
Module Description
TDAF removes ringing noise from input traces, or, applies a true time variant Weiner-Levenson spiking
deconvolution. Ringing noise is specified by a frequency range. Some ringing noise on shots has a
velocity of propagation. This velocity value provides the starting time of noise removal. Optionally only
the input data above the start of the filter can be output to view the start position of the filter. Noise
cleanup control may vary linearly from top to bottom of traces.
Input Channels
Output Channels
Parameters
Mode?
Select either ringing noise rejection or true time variant spiking decon.
Options: Frequency range attenuation, TTVD
Start frequency
Low frequency of the ringing noise range.
End frequency
High frequency of the ringing noise.
1267
Velocity of noise
Pre-stack ensembles where traces are sorted by offset may exhibit a linear noise pattern with offset. Enter
the velocity of this noise pattern. If the data is stacked, or sorted by common offset, enter a very large
value for the velocity, i.e., something like 99999999. To see where the filter will start in time select YES
to the parameter just below "Test velocity value?", and display one input ensemble.
Test velocity value?

Select YES to output the input data above the filter start. This option is useful for input ensembles sorted
by offset with linear ringing noise. Select NO to apply ringing noise rejection.
Top of trace noise reduction

This value is the INVERSE of the noise reduction strength. A value of 20 may be very strong but a value
of 150 may be very weak. These values are data dependent. Some experimentation will be necessary.
Bottom of trace noise reduction

This value is the INVERSE of the noise reduction strength. A value of 20 may be very strong but a value
of 150 may be very weak. These values are data dependent. Some experimentation will be necessary.
Gate length (ms)

For true time variant decon this value is the time gate length used to design the decon filter for the sample
at the center of the gate. This value must be greater or equal to the filter length.
Filter length (ms)

This value is the length of the spiking decon filter. This value must be less than or equal to the gate length.
White noise %
Percent of pre-whitening applied to the autocorrelation zero lag value prior to filter computation.
Taper length (ms)

Time gates may be linearly tapered at the ends for better spectral estimation.
Number of threads
This modules operates in parallel in a threaded mode across the number of CPUs specified. More CPUs
reduce process time.
1268
1269
TDUMP
Module Description
Parameters
Module Description
TDUMP is a stand alone module to dump, or convert data, from tape and print it in the job execution
listing. Data to dump may be specified either using the parameters below or through a matrix, DFORM. If
the parameters are used, only one dump may be performed without restarting the program. Several dumps
of the same data set may be obtained by using the matrix to specify dump parameters. TDUMP can be
very useful in defining data tape formats such as SEGY or SEGD, examples of which are shown below.
The matrix input also allows other options. In addition to the HEXADECIMAL, ASCII and EBCDIC data
conversion formats available with the fixed parameters defined below, the matrix allows conversions from
16 bit and 32 bit integer (INT16 and INT32) as well as two floating point conversion formats (IBMFP and
IEEEFP). Ends-Of-File and physical records may be skipped either forward or backward from the current
tape position. Each row in the matrix is interpreted as a new dump operation. All tape positioning is done
prior to the dump operation specified on each row of the matrix. Data may be dumped from the middle of
a record by skipping bytes. Any number of bytes may be dumped from as many records as desired. The
tape may also be rewound prior to any dumping.
EXAMPLE.1
The matrix below was designed to dump a SEGY tape.
1270

*** SeisUP seismic processing system ***
GeoCenter Inc.
Fri May 23 16:39:50 2003
Host: godzilla
Pid: 120256
***Processing for the following module:
*TDUMP
Variable dump format?
Dump
: 256
: Yes
: segy
16:39:50|Mount tape and respond unit #

16:39:58|132 local
Print format EBCDIC
00000C 1 CLIENT EASTERN
COMPANY DIGICON/GFS INC.
CREW NO 303
00050C 2 LINE 3-D
AREA HIGH ISLAND 3-D
MAP ID
000a0C 3 REEL NO E3D0089 DAY START OF REEL 188 YEAR 1996 OBSERVER
000f0C 4 INSTRUMENT: MFG I/O
MODEL RSR
SERIAL NO VARIOUS
00140C 5 DATA TRACES/RECORD
AUXILIARY TRACES/RECORD
CDP FOLD
00190C 6 SAMPLE INTERVAL 4 MS.
SAMPLES/TRACE 2048 BITS/IN
BYTES/SAMPLE
001e0C 7 RECORDING FORMAT RSR
FORMAT THIS REEL SEG-Y MEASUREMENT SYSTEM FEET
00230C 8 SAMPLE CODE: FLOATING PT
00280C 9 GAIN TYPE: FIXED
002d0C10 FILTERS: ALIAS
HZ NOTCH
HZ BAND
HZ SLOPE
DB/OCT
00320C11 SOURCE: TYPE AIRGUNS
NUMBER/POINT 1
POINT INTERVAL
00370C12
PATTERN: LINEAR
LENGTH
WIDTH
003c0C13 SWEEP: START
HZ END
HZ LENGTH
MS CHANNEL NO
TYPE
00410C14 TAPER: START LENGTH
MS END LENGTH
MS TYPE
00460C15 SPREAD: OFFSET
MAX DISTANCE
GROUP INTERVAL
004b0C16 GEOPHONES: PER GROUP
SPACING
FREQUENCY
MFG
MODEL
00500C17
PATTERN:
LENGTH
WIDTH
00550C18 TRACES SORTED BY: FIELDRECORD/CHANNEL
005a0C19 AMPLITUDE RECOVERY: NONE
005f0C20 MAP PROJECTION
ZONE ID
COORDINATE UNITS
00640C21
00690C22
006e0C23
Print format INT32
00000
1
1
00010
262148000
134219776
00020
0
0
00030
0
2
Print format INT16
00000
0
1
0
00010
4000
4000
2048
00020
0
0
0
00030
0
0
0
1
2048
0
2
5
65776
0
0
0
1
0
0
5
240
0
0
1271
15728640
65537
0
0
240
1
0
0
0
1
0
0

Print format INT32
00000
81601
00010
0
00020
0
00030
0
1
0
0
0
8926
0
0
0
1
65536
0
0

Print format INT32
00000
81602
00010
0
00020
0
00030
0
2
0
0
0
8926
0
0
0
2
65536
0
0

Print format INT32
00000
81603
00010
0
00020
0
00030
0
3
0
0
0
8926
0
0
0
3
65536
0
0

Print format INT16
00000
1 16065
0
00010
0
0
0
00020
0
0
0
00030
0
0
0
1
0
0
0
0
0
0
0
8926
0
0
0
0
1
0
0
1
0
0
0

Print format INT16
00000
1 16066
0
00010
0
0
0
00020
0
0
0
00030
0
0
0
2
0
0
0
0
0
0
0
8926
0
0
0
0
1
0
0
2
0
0
0

Print format INT16
00000
1 16067
0
00010
0
0
0
00020
0
0
0
00030
0
0
0
3
0
0
0
0
0
0
0
8926
0
0
0
0
1
0
0
3
0
0
0

Print format INT16
00000
1 16068
0
00010
0
0
0
4
0
0
0
8926
0
0
1
4
0

Print format IBMFP
000e8
0.0000e+00
0.0000e+00
000f8
9.4735e+08
9.4678e+08
Print format INT16
00000
1 16304
0
240
00010
0
0
0
0
9.4674e+08
9.4650e+08
0
0
8926
0
1272
9.4662e+08
9.4786e+08
0
1
240
0
00020
00030
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

Print format INT16
00000
1 16305
0
241
00010
0
0
0
0
00020
0
0
0
0
00030
0
0
0
0
User time: 0.1 sec.
System time: 0.1 sec.
0
0
0
0
8927
0
0
0
0
1
0
0
1
0
0
0
********** Job server hints **********

Fri May 23 16:40:12 2003
EXAMPLE.2
The matrix below was designed to dump a SEGY tape.

*** SeisUP seismic processing system ***
GeoCenter Inc.
Tue Jan 7 12:19:16 2003
Host: godzilla
Pid: 305423
***Processing for the following module:
*TDUMP
Dump format
: 256
: Yes
: devon-segd
12:19:16|Mount tape and respond unit #

12:19:37|132 local
<
Print format HEXAD
00000 28008015 00000083 00000110 26140114 22300000 00002000 00812001 02002626
00020 000af000 02001a00 1a000200 00000030 00000200 00000000 00000000 00000000
1273
00040 01010000 02000010

00060 01020000 1800499f
00080 4754322e 32205452
000a0 00010000 00000000
000c0 00020000 00000000
000e0 00010000 00000000
00100 00010001 00000000
00120 00010000 00000000
00140 00010001 00000000
00160 00020000 00000000
00180 00020000 00000000
001a0 00020000 00000000
001c0 00010000 00000000
001e0 00010000 00000000
00200 b8000011 e4000012
00220 2b000012 39000012
00240 c0000011 fd000027
00260 08000012 53000010
00280 1c000013 e1000010
002a0 00000000 00000280
002c0 00000028 00000000
002e0 00800006 00000001
00300 08001d1e 1e1d1f1d
00320 1f1d1e1d 271e1d1f
00340 3b803a81 3c7f3b7f
00360 3680397f 357f3781
00380 9683c66c 73038980
003a0 6b678182 6c675cc6
003c0 00002800 31353039
003e0 54415220 009000e4
00400 00160096 00010001
00420 00040018 4d414e49
00440 44542020 0328000a
00460 00010001 00030002
00480 53657276 37343631
004a0 20202020 50617261
004c0 20202020 bf490fdb
004e0 e373bfe8 4bf1324c
00500 2f9a4483 6000bf91
00520 a56f4039 336b4039
00540 090200d6 40003a10
00560 40003e00 0004c540
00580 01049040 00392800
005a0 003b1800 087e4000
005c0 0ca74000 3911010c
005e0 3a010310 d4400037
00600 8a400039 2800107d
00620 21011485 40003828
00640 00000000 00000000
00660 02649018 630265a6
00680 d0306102 5c993464
006a0 670251d9 4c650250
006c0 3e8c6465 02379368
006e0 7c18022d 1f001928
tpfunc=5 count=1
00369030
03201009
49414351
00025343
00044243
0006424c
00085444
000a5241
000c4644
000e4f52
00105341
00125349
0014564f
01401101
55000012
3a000012
0f000027
87000011
76000027
00000000
00000028
00010001
1d1e1e1d
1e1e3c80
3b7f3b7f
3780387f
977d8888
28737f82
39393739
0001ffff
0003001f
464f4c44
00000001
07d1001a
42504d31
2d4d6172
4072a41d
0c423f10
086588a2
3c283d03
0000ac40
00390801
04924000
3b200008
a940003a
090110a1
40003708
01148240
00000461
1c630265
02576f38
7e506502
640232a2
0af00000
05000048
02000200
00004e34
016b0004
02160010
00000000
022c0003
02320006
02380006
02460008
02720004
00000000
02aa0050
00402812
40000012
34000010
0f000010
80000014
0f000000
00280000
00000011
00040007
1d1e1e1e
3d803c7f
397f3a7f
3a7f347f
9d537a00
6a670000
00000340
00040001
54524942
03260002
00010001
000e0001
54303536
616e6861
96746d88
09d53f40
e373bfe8
2f9a4483
003b1800
04c54000
39010208
8140003c
19010c75
40003b10
0314d740
00380106
02741e08
95206302
660257a2
4b6c5463
6c630222
00000271
00010006
00030018
00150000
00010000
00020000
00020001
00010000
00010000
00010000
00020000
00020000
00010001
00010000
32000012
56000012
9b000012
d6000011
4a000011
28000040
28000280
00000001
00000028
1d1d1c1e
3d7f3d80
3780387f
35803680
8a7a937d
00000000
00052800
0002001e
49524420
00010050
000400e2
000e0012
20202020
6f202020
415854a6
c05a3f0c
4bf1324c
60002cfe
00be4000
3a110104
aa400033
28010889
40003720
0110a440
00381001
078e1788
60026b75
63a22462
3c620254
024cbd58
ca706202
08810000
1274
00000000
00000000
54454844
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
00000000
5b000010
4c000010
23000012
12000010
c2000011
ffff0028
000dcf28
00080005
0000000f
1c1d1d1c
3d803d80
39803780
3680387f
61788d9d
00000000
47455854
54524947
028a009b
00010001
00000af0
4578706c
37343433
4745434f
40000000
a56f4039
0c423f10
01164000
39200000
aa40003a
080108c0
40003d00
020c8b40
00391801
14ac4000
278b378d
0c630269
02609c28
68406402
62024c94
12977463
00000000
00000001
00000002
00015243
00034249
00054343
00074954
00095253
000b4143
000d5041
000f4b43
00115453
00135445
00155052
2d000011
aa000010
37000010
ae000011
ca000012
5001ffff
02808000
00000001
08000001
1f1e1e1f
3c803c7f
39803780
36807386
81935cc5
00000000
00010005
554e2020
001f0005
0005001c
41b8969e
6f726174
42202020
5f544155
0002bf91
336b4039
09d53f46
22010101
80400041
190804b9
40003810
000cbe40
003a2801
10b34000
3a180114
4794578d
98106402
64025db7
519c4462
5c620247
0214a478
00000000
00000000
00010102
01680003
016f00a7
02260006
00000000
022f0003
00000000
023e0008
024e0024
0276000c
02820028
02fa0028
cc000012
ab000012
7500000f
7e000012
0e000012
00000000
12c70000
00200001
08000018
1e1e1e1f
3b803c7f
36803780
54790769
28717f82
00000000
4e4f5253
01740116
00010001
4e455333
2a2e147a
696f6e20
20202020
20202020
086588a2
3c283d03
d3f23f0c
1eee0000
28000082
40003820
0008b340
00390901
0c814000
37200010
c0400033
00000000
687e1461
2c63025a
0254a248
91606302
6402209b
000098a3
Print format EBCDIC

00000???????c?????????????????a????????0?????????????????????????????????????????????
00050???????????????????????E?????????????????????????"????"???????+?????"???????????
000a0?????????????,?????????????????x???????????????????????????????????????????
??o???????&(?"???????????????????????&/?/?(/?/>?/
004b0???????|^"??????????O??U ?u?o?_h??"w ?????Oj?ohsT?OY.1?

Print format ASCII
00000(???????????&???"0???? ??? ???&&???????????????0?????????????????????????6?0???H
00050??????????????????????I?? ??????????????????????GT2.2 TRIACQ??N4????TEHD??RC?h??
000a0??????????SC?k????????????BI?o????????????BC??????????????CC?&????????????BL????
000f0??????????IT??????????????TD?,????????????RS?/????????????RA?2????????????AC????
00140??????????FD?8????????????PA?>????????????OR?F????????????KC?N?$??????????SA?r??
00190??????????TS?v????????????SI??????????????TE???(??????????VO???P??????????PR???(
001e0?????????@???@(?2???[???-???????????????U???@???V???L???????????+???9???:???4???
00230????#???7???u?????????????????????????????~???????S???????????J???????????????
00280????????v??????(??@???(P????????????????????(??(??????(???????????(???????(????
002d0????????????? ?????????????????????(????????????????????????????????????????????
00320?????????
????@?9????@?:????@?:????@?8 ???@?9(???@?9????@?3????@?8????@
005a0?;???~@?; ???@?<(???@?=????@?9????@?9????@?:???u@?7 ???@?:(???@?:????@?7????@?;?
005f0???@?9????@?7 ???@?9(??}@?7????@?8????@?:????@?3!???@?8(???@?8???????7?G?W?????
00640???????????a?t???ku?c?i??d?h~?a?d??c?e??c?e? c?c?$b??(d?]?,c?Z?0a?\?4d?Wo8f?W?
00690?de?7?hd?2?lc?"?pb???tc???xd? ?
006e0|??-???(???????q????????????????
Print format HEXA
00000 28000101 0001ff9c 00000000
00020 421b7831 421b6027 01007831
00040 6c2c7831 6c2c1001 481d7831
00060 60277831 1101421b 421b7831
00080 54220000 60276027 78316c2c
000a0 01017831 4e206c2c 421b1001
000c0 421b481d 78316027 1001481d
000e0 78317831 78310000 78317831
00100 78316c2c 00106c2c 7831421b
00120 421b1001 421b7831 7831421b
00140 1000421b 60276027 60270000
00160 6c2c6c2c 60276027 00006c2c
00180 54226027 78310000 60276c2c
001a0 481d6c2c 00006027 60275422
001c0 78311000 421b6c2c 6c2c6c2c
001e0 00006c2c 481d6027 481d0000
00000000
421b5422
6027421b
481d1111
00017831
421b7831
78317831
6c2c6c2c
6c2c1100
00006c2c
54226027
481d6c2c
78316027
6c2c0000
00006c2c
60275422
00000000
6c2c0000
00016027
421b421b
78316c2c
7831421b
481d1000
01017831
481d421b
6c2c7831
60277831
54220000
00006c2c
6c2c6027
6c2c6c2c
5422481d
01006c2c
78316027
6c2c7831
421b421b
4e200001
1111481d
421b7831
421b7831
6c2c7831
60270001
00006027
60276027
6c2c5422
60276027
6c2c0000
421b6c2c
78316027
421b0000
00006c2c
6c2c6c2c
481d421b
6c2c7831
481d1000
1011421b
60276c2c
78316c2c
60276c2c
60270000
00006027
60276c2c
78311010
00007831
6c2c6027
60276027
6c2c4e20
421b1100
00007831
421b6c2c
7831421b
78314e20
54220000
00006c2c
6027481d
54226c2c
481d5422

Print format HEXA
00000 28000101 0013ff9c 00000000
00020 bfd888da 84458445 23338445
00040 bfd8bb43 bd8d2333 88dabd8d
00060 8445bd8d 3232bb43 8445bd8d
00080 84452222 84458445 84459204
000a0 22228445 84458445 8d6f2222
000c0 84459204 88da88da 22228d6f
00000000
bfd8bd8d
bfd8bfd8
88da2233
22228d6f
88da8445
844588da
00000000
bd8d3333
23228445
88da88da
88da8445
8d6f9204
8d6f2232
22238445
bfd8bfd8
bfd88445
bfd8bd8d
84453232
222288da
84459204
88da8445
bb43bfd8
84452223
3332bb43
bfd888da
9204969a
bd8d8d6f
bfd83222
3333bd8d
88da88da
bd8db8f8
bd8d8445
8d6f2222
22228d6f
1275
000e0
00100
00120
00140
00160
00180
001a0
001c0
001e0
969a9204
88da8d6f
84452222
2222969a
9fc49b2f
9204969a
9fc49fc4
9b2f2222
22229204
9b2f2222
22228d6f
8d6f88da
92049204
969a9204
969a2222
22229b2f
969a969a
9204a459
9fc4969a
88da969a
8d6f9fc4
88da2222
22229204
9b2f969a
9fc49fc4
88da9204
ad832222
92048d6f
9fc42222
22229b2f
88da8d6f
969aa459
9b2f8d6f
9fc42222
22229b2f
a8eea8ee
22229204
9b2f9b2f
9b2f8d6f
8d6f9fc4
969a2222
22229b2f
969a9b2f
a459a459
ad83bb43
88da9204
969a8445
92042222
22229fc4
a4599fc4
9b2f969a
969a9fc4
a8ee2222
8d6f2222
22228d6f
920488da
a459969a
969a9fc4
969a2222
22229fc4
ad83ad83
8d6f8445
84458445
8d6f88da
969a2222
2222969a
9b2f9fc4
a459bb43
9fc49b2f

Print format HEXA
00000 28000101 0025ff9c 00000000
00020 ad079848 a2a7b766 0000b766
00040 b766ad07 98480000 a2a78de9
00060 ad079848 0000a2a7 a2a79848
00080 98480000 98488de9 9848a2a7
000a0 0000838a 8de99848 8de91000
000c0 9848a2a7 ad079848 01009848
000e0 838a9848 98480000 838a9848
00100 bc95bc95 1111bc95 b766b766
00120 838a1111 bc95b766 bc95b236
00140 1110b766 b766b766 a2a71110
00160 bc95b766 b236b766 1110b236
00180 8de98de9 8de91000 bc958de9
001a0 838abc95 00008de9 a2a7838a
001c0 bc951111 bc95bc95 bc95bc95
001e0 00118de9 838abc95 bc950100
00000000
a2a7a2a7
98488de9
ad070000
0000a2a7
b766838a
bc958de9
9848838a
b7661010
0011838a
b236bc95
bc95b766
838a838a
838a0110
1000bc95
838abc95
00000000
b7660000
00009848
a2a79848
8de9c1c5
8de98de9
98480100
00008de9
b7668de9
838ab766
bc95838a
838a1000
01118de9
838abc95
8de9838a
838a838a
0000b766
b766ad07
9848a2a7
8de9ad07
98480000
00008de9
8de9bc95
8de9838a
b766838a
b7661110
1011b766
bc958de9
bc95bc95
bc959848
8de91000
c1c58de9
9848b766
a2a70000
00009848
b7669848
98488de9
838a8de9
838a0111
01108de9
b766bc95
838ab766
8de99848
b7660001
1111bc95
bc95838a
ad070000
0000b766
9848ad07
a2a78de9
b7668de9
98480000
00008de9
838ab766
bc95b766
bc95838a
b7661111
1000bc95
838a838a
bc95bc95
8de98de9

Print format HEXA
00000 28000102 00010000 06000000
00020 a8e1bd4c 8c5caacf 1001a165
00040 43276aaa 67402222 500c5c77
00060 53cf427c 111163ac 44a04b14
00080 bfd43333 bc56b971 bd4dbba0
000a0 0000f3b4 fa875071 71ca0010
000c0 a8bfa7f9 b0539748 2202b3ea
000e0 bf338202 9bca98aa 9c855be0
00100 68577ebc 77377fa0 404dbcbf
00120 850d9999 bfeabdc8 bc26ba37
00140 9999afa1 ab42aee1 b91c8887
00160 6c906110 567d4de7 788879c0
00180 a1c7afcd 8cf13566 5bf86b24
001a0 764a7607 77776fe5 67a16986
001c0 68ae7777 58ec4fa0 512a585f
001e0 6666bcaf ace3a126 96686777
00000000
a8f42203
5eac6704
5aaf0001
3333b49d
4acc4f70
84b5a793
56ff7847
b2467888
9988baa3
8ceda504
4e285857
48cc4c38
79328888
77665936
8765b950
00000000
55622222
22226e17
4dc4beeb
b7c4bc1b
41927120
8cb3369a
bbbb475a
8a56b09f
be7987bf
b5068122
5b358877
667752ed
4b885ab7
4eb87d46
ae88a582
33338d0c
40cb487b
5cec4525
8032938d
bec02210
000045ac
b925806f
52c0577b
9be194da
90c18889
77509b5a
553e48ab
64d2436d
5fda5b01
59925435
93d991bc
4f425526
45112222
23339cdd
8c24a6f4
3a4c1c2c
b322b0a0
5134aa98
888896c4
94938f88
be768fdf
6d844354
55fd7777
88775028
69f04ff6
94703322
21014260
561f5ec0
bc74bbdf
b8d707d9
d8c71122
abaa9053
7ec7530a
8e1485eb
8222b84d
b87f4567
535468b2
647570b1
43eb76e7
9ea7a86f

Print format HEXA
00000 28000102 00090000 06000000
00020 9a6ebcb6 960398f8 2222b835
00040 ac149bcb 919f2222 8b009325
00060 c2ae9935 1122912c 89a7b3cc
00080 a3c92211 a64eb3a4 8ba99a6a
000a0 012270c7 64684c8f 5db42333
000c0 43107e07 7e357ed6 32224058
00000000
bbc3be9c
9831a656
aa1c2222
11129933
6d0b4376
6fed5c0b
00000000
b68a2101
2211b702
a659ab38
95ca85ff
4c174d9c
50422100
0000cc88
ba819ad8
b5c08e2c
ab21a19c
b6102200
333354c3
4e6e79b0
e67d16e5
8a37bd61
bd800001
22229d43
af37bd96
64946c24
44810397
bd921211
12228e63
acf2fa28
9fc2a355
81df115a
5a4b3222
01115a70
1276
000e0
00100
00120
00140
00160
00180
001a0
001c0
001e0
4eef54fe
6b9d59f7
58d81000
2222a5f3
200428d0
97b79141
68774281
95077766
566696bc
5f0c1221
2110427a
444a426b
a8a6a71a
0ebf3cda
97b68678
6531555d
a4d4b82e
b5029f55
78b44b36
7609598f
14291762
aa662211
1110645c
b0829a77
5a537e0c
9469af7f
94c46666
45df5cc8
62da0011
0112c467
b265bac7
60fa634d
4e5c5905
a1074566
6666ba1c
944d9803
11114acd
4a66689c
a30f8a91
8de7be14
54250057
89997786
b17ab66c
b4e2aaf4
9a9a9b41
5f3e747b
530f62df
b0f42222
0000fb71
490481ef
45e94d79
bccd8edb
a6f36655
7e4b2222
10114c32
93849463
367f1c16
8a5ca598
4e3d9877
7777af06
ad32bd2d
492e5ea4
7c74533c
a425a4de
14690000
8888b082
4110565e
9b249113
9c34a99b

Print format HEXA
00000 28000102 00170000 06000000
00020 62586f72 65d25639 22114dcb
00040 d310924f 833a2222 a6b4a973
00060 a96dbe6f 12108997 b8d48fd0
00080 641a2222 5f03587a 56f36325
000a0 1000bf5f 8e9fcc52 e5300000
000c0 3bdc6d68 3e58fd02 00000f8f
000e0 b2a481c9 b56d0000 c5180c55
00100 6784639e 00006f04 1fd3142e
00120 fc990111 9e88a2fd a1b3a6a7
00140 1111b01b b632b67f b1af1111
00160 b0dbf817 36ec6c67 11116931
00180 4a224766 40b91000 4b984590
001a0 82108245 2000a9cc 88dbe15b
001c0 af012211 aa8eb4ee 9cb8b514
001e0 00011b91 4e227b54 58701222
User time:
0.1 sec.
System time:
0.2 sec.
00000000
433c60a9
b37bad62
ae8d0012
22217716
a1cf8a2a
41c74dff
23fbd8b3
401a0000
1001ac3e
baddbdd9
738770e7
3e4e1d0f
c3d30001
1111ad3f
79d44272
00000000
496c0000
2222a630
1ace5f90
7d8c6d2d
b5e3fa32
20a90122
00019dd8
64622668
cb446787
bea8b4b2
7e951222
0112cc4f
e25f074c
b516bf82
432f404d
01227e3c
5d171c22
a0ad975b
5217412c
7ecb0000
0000398c
b20d9359
edcc70d0
f57d3abd
5d551001
11109d3c
7f15446b
ae468061
dbffac36
b5120000
688042cf
1e1c1600
99a92222
22224d69
3941e1d6
47b23e83
b7a3b13f
4e171111
11004ab8
5fd95bef
9bd1b948
4837464e
b1372222
2222af86
8766c60d
4d562222
0001e90a
a5daa6ee
4e265a7c
aeae83e7
26900000
2211ae09
54b95eee
4a8848d1
bb89b56e
a3180000
22224a08
a6379734
a3aeac57
f12c0a62
********** Job server hints **********

Tue Jan 7 12:19:43 2003
Parameters
This buffer size should be large enough to read the largest physical record in the input data set. The tape
handler may not be able to the read the data set if the buffer is too small. However, coding this parameter
overly large may cause trouble for some tape drives.
Rewind tape?
Rewind the data set to the beginning prior to executing any instructions below.
1277
# EOFs to skip, neg. for backwards.

Number of Ends-Of-File to skip from the current position in the data set prior to beginning the dump.
Positive values indicate a forward skip and negative values a backward skip.
# records to skip, neg. for backwards.

Number of physical records to skip from current position in data set prior to beginning the dump. Positive
values indicate a forward skip and negative values a backward skip.

Number of 8 bit bytes to convert and dump.

Number of physical records to dump.
Dump type
Define the conversion format to use for the data .
Options: Hexadecimal, ASCII, EBCDIC

If coded NO, the above parameters are used to define the dump. If coded YES, a matrix must be supplied
to define the dump.
Options: YES, NO
Dump format
Must be coded if Variable dump format = YES.
Matrix Type: DFORM
1278
TFDNOISE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module TFDNOISE performs noise suppression and sub-spectral balancing using sample wise median
thresholding within frequency subbands in the time-frequency space. This module will damp noise and
spikes within the frequencies of interest.
Several processing step should be taken before running this module:
It is a good idea to run spherical divergence before running this module.
The program should work best on NMO correct CMP gathers or perhaps offset gathers. But can be run on
any data ensemble.
Each ensemble is transformed separately into amplitude and phase components for each frequency
subband. If automatic thresholding is requested then the median spectral amplitude within each requested
frequency subband is calculated for the ensemble. The median of these medians (multiplied by the
threshold multiplier) becomes the threshold for that ensemble. Each sample of each requested subband is
compared against this threshold. If the sample amplitude exceeds the threshold then the median spectral
amplitude of the adjacent n samples within the subband is computed and installed at this location. The
effect is to replace outlier spectral amplitudes as defined within the frequencies of interest. If the threshold
is too small the data will be heavily balanced. If the threshold is too large, glitches and spikes may not be
adequately damped.
If your noise is isolated to a small set of subbands or a subset of times, you can decrease run times by
using the start/stop time and the min/max frequency of interest. The threshold determination and
validation search will be constrained to only those subbands and times requested. Alternatively, the
start/stop time of interest may be varied spatially using a matrix of type WINDOWS2. This matrix can be
created in the DISPLAY module. This approach may be useful to improve results in shallow data.
The number of adjacent traces over which to compute the spectral median is dependent on the noise to
suppress. The larger you make this number; generally the more balancing is done in the TF spectra. If you
are trying to de-glitch a dataset where the nature of the glitches are that they occur on single traces here
and there but perhaps over many samples within a trace then the default of 5 is great. If you have many
adjacent traces involved in the noise you are trying to suppress you will need to make this large enough to
see not just all the noise traces but a reasonable number of regular traces as well so that the noise traces
samples do not occupy the median. Ensembles with fewer traces than the required number used to
compute the spectral median will be skipped.
1279
It is a good idea to perform automatic threshold detection. In automatic mode, the record is analyzed for a
threshold value. This threshold is then multiplied by the threshold multiplier. This determines the
threshold that frequency subbands are validated against.
Input Channels
Output Channels
Parameters
Time and space variant window?
Options: No, Yes
Start time (ms.)

Enter the start time to filter in milliseconds.
End time (ms.)

Enter the end time to filter in milliseconds.
Primary header key for window matrix

TLSN
Secondary header key for window matrix

values.
1280
TLSN
Windows matrix
secondary key, start time, and end time values. Although up to five windows may be defined for each
secondary key TFDNOISE will only use the first window.
Number of samples in FFT sampling window

Enter the number of samples in the transform window. The sampling of the frequency subbands is related
to the number of samples put into the FFT transform. Under no circumstances will this value be less than
32 samples. We need a minimum of 32 samples to keep the forward and inverse transform stable.
Lowest frequency of interest (Hz)

Enter the minimum frequency subband to be processed in hertz. Any subband less than this value will not
be part of the threshold determination. This parameter is useful to decrease the runtimes in certain cases. If
you are unfamiliar with the time frequency character of the noise you are suppressing then you a better off
to let this value default. To get an idea of what is a reasonable value, you can perform a frequency
spectrum plot on selected ensembles and find the noise that you want to attenuate.
Highest Frequency of interest (Hz)

Enter the maximum frequency subband to be processed in hertz. Any subband greater than this value will
not be part of the threshold determination. This parameter is useful to decrease the runtimes in certain
cases. If you are unfamiliar with the time frequency character of the noise you are suppressing then you a
better off to let this value default. To get an idea of what is a reasonable value, you can perform a
frequency spectrum plot on selected ensembles and find the noise that you want to attenuate.
Number of traces to compute median spectral amplitude

Enter the number of adjacent traces over which to compute the median spectral amplitude when the
spectral threshold has been surpassed at any given sample. The larger you make this number; generally the
more balancing is done in the TF spectra. If you are trying to de-glitch a dataset where the nature of the
glitches are that they occur on single traces here and there but perhaps over many samples within a trace
then the default of 5 is great. If you have many adjacent traces involved in the noise you are trying to
suppress you will need to make this large enough to see not just all the noise traces but a reasonable
number of regular traces as well so that the noise traces samples do not occupy the median. Ensembles
with fewer traces than defined by this parameter will be skipped.
1281
Threshold detection method

Selecting automatic allows the program to do auto thresholding. It is recommended that you let the
program do auto thresholding as it can adapt in a ensemble to record the sense to change your data. It is
difficult, if not impossible, to do this using a global threshold.
Options: Automatic, Global
Automatic threshold multiplier

If automatic threshold detection is selected, then enter the threshold multiplier. A low threshold multiplier
means that more of the data will be filtered. A high threshold multiplier will filter less of the data. In
automatic mode, the threshold is determined for an ensemble. The computed threshold is then multiplied
by the threshold multiplier. This then is the threshold used to determine if samples should be filtered.
Global threshold value

Select the global threshold detection to apply a single threshold value to the dataset. Enter the value for the
global threshold.
Parallel execution mode

If the parameter Parallel execution mode is set to Cluster, then TFDNOISE is performed on a cluster. In
which case the parallelization is achieved using Message Passing. The cluster may contain several nodes
(computers), and each node may have one or more Processors (CPUs). If this parameter is set to Threads,
then TFDNOISE is performed on a SMP machine. In this case the parallelization is achieved using
Threads, and there may be one or more CPUs on this machine. If this parameter is set to None then
TFDNOISE is run on a single CPU on this machine.

This parameter specifies the number of nodes (computers) in the cluster, to be used for processing. This
parameter is only available if the parameter Parallel execution mode is set to Cluster. If the cluster you are
running this job on has 60 nodes, and you want to use all, then you specify 60 for this parameter. If you
want to use only half the nodes, then you specify 30 here. Each node in the cluster may have more than
one processors. The number of processors on each node of the cluster is specified in the next parameter
Number of processors on each Node of the Cluster:.
Number of processors on each Node of the Cluster

This parameter specifies the number of processors (CPUs) on each Node of the cluster. This parameter is
only available if the parameter Parallel execution mode is set to Cluster. If each node has more than one
processor, then a second level of Parallelization is achieved using Threads on each of the node. At this
time the limitation is that each node in the cluster must have at least the number of processors as specified
by this parameter. So if you have a cluster with some nodes having 4 processors, and others having only 2
processors, then a value of 2 must be used here.
1282
Number of threads
This parameter specifies the number of Processors (CPUs) available on the SMP machine for use. This
parameter is only available if the parameter Parallel execution mode is set to Threads. In this mode the
computations are parallelized using Threads. Here it is assumed that the job is being run on an SMP
machine.
Compute node list


This parameter is used to specify a specific list of sub-nodes, from the Compute node list. This parameter
is only available when running on a cluster. If the Compute node list has many nodes, say 100 nodes
named n1, n2, .. n100. If you wanted to run TFDNOISE on 25 nodes, and specifically nodes n26 to n50,
you would enter 26 to 50 for the values of CPU index in the subnode matrix. Also if you enter values 11 to
20, then the node listed 11 in the Compute node list, to the node listed 20 in the Compute node list are
used. Therefore it is the order of listing in the Compute node list which determines which specific nodes of
the cluster this job will be run on. This parameter is useful if you plan to run several jobs on this cluster,
and want them to run on different nodes.

This parameter specifies the Maximum available memory (in MB) on the SMP machine. This parameter is
only available if the parameter Parallel execution mode is set to Threads. A check is made to see if the
amount of memory needed by TFDNOISE is less than the value specified for this parameter. If not, A
message is sent to the Execution status file, and the job will ABORT. If more memory is available on the
machine, please specify a larger value here, and rerun the job. Alternatively, reducing the Number of
threads parameter will reduce the amount of memory required by TFDNOISE on the machine.

This parameter specifies the Maximum available memory on the Master Node (in MB) of the cluster. This
parameter is only available if the parameter Parallel execution mode is set to Cluster. A check is made to
see if the amount of memory needed by TFDNOISE is less than the value specified for this parameter. If
not, A message is sent to the Execution status file, and the job will ABORT. If more memory is available
on the Master Node, please specify a larger value here, and rerun the job.
1283

This parameter specifies the Maximum available memory on each of the Compute Node (in MB) of the
cluster. This parameter is only available if the parameter Parallel execution mode is set to Cluster. A
check is made to see if the amount of memory needed by TFDNOISE is less than the value specified for
this parameter. If not, A message is sent to the Execution status file, and the job will ABORT. If more
memory is available on the Compute Nodes, please specify a larger value here, and rerun the job.
Alternatively, reducing the Number of processors per node parameter will reduce the amount of memory
required by TFDNOISE on the node.
Print message when skipping an ensemble?

This parameter determines whether or not a warning message is printed to the execution log when an
ensemble is skipped because it contains fewer traces than defined in parameter Number of traces to
compute median spectral amplitude.

You can optional add additional time to the start time of the window using this header key.

You can optionally remove time to the end time of the window using this header key.
1284
TOVG0
Module Description
Input Channels
Output Channels
Parameters
Module Description
TOVG0 (Time Offset Variant Gain (version 0)) applies a t**N * e**(E*t) gain to each trace where N is
some real number (like 2.0), e is the constant 2.71828, E is some real number and t is time in seconds. The
gain will optionally start either at maximum amplitude (ungained shot) or at time 0. N may optionally be
increased with offset.
Input Channels
Output Channels
Parameters
E value in e**(E*t)
Default: 0.0
N value in t**N
Default: 2.0
N increase per 1000 units offset

Default: 0.0
1285
Start time of gain

Options: Maximum amplitude, Time 0
1286
TRACECAL
Module Description
Input Channels
Output Channels
Parameters
Module Description
Module TRACECAL performs a selected operation on the samples of the input traces. Available
operations include:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
ABS (Absolute value of each sample.)

Sine (Sine of each sample (Angle in degrees).)
Cosine (Cosine of each sample (Angle in degrees).)
Tangent (Tangent of each sample (Angle in degrees).)
Exponentiate (e raised to the sample power.)
Logarithm (Natural logarithm (ln) of each sample.)
ArcTangent (Arctangent of each sample.)
Invert (The inverse (1/sample) of each sample value.)
Square (Signed Square each sample value.)
Fill (Set trace samples to a coded ramp or header word contents.)
Mirror (Repeat each sample below the coded time the same distance above the coded time. )
Clip (Set values greater than the coded value to the value. )
Fill Sine (Fill the trace with a sine function of the frequency, phase and amplitude coded. )
Threshold (Set values greater than the coded threshold to value. Set values less than the coded
threshold to -value.)
Add (Add the coded value to all samples in each trace. )
Inflections (Output only samples at trace inflection points. )
Multiply (Multiply all samples in each trace by the coded value. )
Trace Extension (Replace leading and trailing zeros with first/last live samples. )
Flip (Reverse the order of samples in a trace. )
Trace Attributes (Find maximum, minimum, etc. sample values and put in trace header. )
Differentiate (Running difference derivative. )
Integrate (Running sum integration. )
Modulo (Remainder after division. )
Threshscale (Scale between zero crossings if thresh hold exceeded. )
Kurtosis (Compute kurtosis over sliding window. )
1287
Input Channels
Output Channels
Parameters
Header Containing Validation ID
Header word used to determine which traces are processed.
TLSN, other
Header ID Index for Validation ID

This parameter is accessed if Header Containing Validation ID is set to other.
Header value to Validate Operation

A trace is processed if the header above is set to this value.
Operation
Options: ABS, Sine, Cosine, Tangent, Exponentiate, Logarithm,
ArcTangent, Invert, Square, Fill, Mirror, Clip, Fill Sine,
Threshold, Add, Inflections, Multiply, Trace Extension, Flip, Trace
Attribute, Differentiate, Integrate, Modulo, Threshscale
Zero divide fill value

This parameter is accessed if Operation is set to Invert.
Fill value source

Options: Value, Header contents
1288
This parameter is accessed if Operation is set to Fill.
Samples to fill
Options: Non-Zero, All, Select
Select samples to fill

Options: First Zeroes, Last Zeroes, Both Zeroes, Window
This parameter is accessed if Samples to fill is set to Select.
Window start
This parameter is accessed if Select samples to fill is set to Window .
Window end
Header to add to window start

TLSN, other
Header ID Index to add to window start

This parameter is accessed if Header to add to window start is set to other.
Fill Value
This parameter is accessed if Operation is set to Fill and Fill value source is set to Value or if Operation
is set to Fill Sine.
Fill Value Increment

This parameter is accessed if Operation is set to Fill and Fill value source is set to Value.
1289
Header Containing Fill Value

Header word containing Fill Value.
TLSN, other
This parameter is accessed if Operation is set to Fill and Fill value source is set to Header contents.
Header ID Index for Fill Value

This parameter is accessed if Header Containing Fill Value is set to other.
Mirror time
This parameter is accessed if Operation is set to Mirror.
Clip Maximum Value

This parameter is accessed if Operation is set to Clip.
Clip Minimum Value

This parameter is accessed if Operation is set to Clip.
Frequency
This parameter is accessed if Operation is set to Fill Sine.
Phase
Phase
Threshold
This parameter is accessed if Operation is set to Threshold.
1290
Value
This parameter is accessed if Operation is set to Threshold.
Add value source

Value to Add
This parameter is accessed if Operation is set to Add and Add value source is set to Value.
Header Containing Value to Add

Header word containing Value to Add.
TLSN, other
This parameter is accessed if Operation is set to Add and Add value source is set to Header contents.
Header ID Index for Value to Add

This parameter is accessed if Header Containing Fill Value is set to other.
Multiply value source

Value to multiply by
This parameter is accessed if Operation is set to Multiply and Multiply value source is set to Value.
Header Containing Value to Multiply By

Header word containing Value to Multiply By.
TLSN, other
1291
This parameter is accessed if Operation is set to Multiply and Multiply value source is set to Header
contents.
Header ID Index for Value to Multiply By

This parameter is accessed if Header Containing Value to Multiply By is set to other.
Extend what
Options: Top, Bottom, Both
This parameter is accessed if Operation is set to Trace Extension.
Trace attribute to the header

Options: First non-zero, Last non-zero, Maximum, Minimum, Maximum
magnitude, Minimum magnitude
This parameter is accessed if Operation is set to Trace Attribute.
Header to store attribute value

TLSN, other
Header ID Index to store attribute value

This parameter is accessed if Header to store attribute value is set to other.
Header to store attribute time

Header word containing Value to Multiply By.
TLSN, other
1292
Header ID Index to store attribute time

This parameter is accessed if Header to store attribute time is set to other.
Modulo Base:
This parameter is accessed if Operation is set to Modulo.
Threshold:
This parameter is accessed if Operation is set to Threshscale .
Window Length(ms):
Length of kurtosis computation window in msec. This parameter is accessed if Operation is set to
Kurtosis .
1293
TRACECMB
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRACECMB performs simple mathematical operations between a pair of seismic traces. The trace pair
must be contained within the same ensemble. Multiple operators and operands are allowed. Module
READ can be used to create ensembles containing traces to be combined and passed to TRACECMB in
the flow. A user specified header word is used to identify operator and operand.
A shaping filter may be derived and applied to the operator. In this case the user must specify a derivation
window. The filter is applied to the operator prior to the combination operation.
The Arc Tangent computations assume the "Operator" is the denominator of the tangent and the
"Operand" is the numerator or X and Y, respectively, in Cartesian coordinates. Angles computed by the
Arc Tangent options are in radians and assume traditional Cartesian polarity.
The PZ Summation/Difference option will set the header ID word to 1 for the summation and 2 for the
difference traces on output.
By choosing YES for the Process All Trace Pairs parameter, each pair of traces in the input ensemble is
treated successively as an operator/operand pair. The output ensemble will thus contain the number of
traces in the input ensemble squared. Headers TIM1 and TIM2 will contain the values from the ID header
word for each trace pair operator and operand respectively.
Multiple trace pairs may be processed within a single ensemble by using the Validation Headers and the
Action parameter to define valid trace pairs. Headers TIM1 and TIM2 will contain the values from the
ensemble sort header word for each trace pair operator and operand respectively.
The Cartesian to Spherical option requires data be input in single three vector component ensembles.
The output three trace gathers consist of the radial component, the azimuth and elevation angle traces. The
Header Containing ID Component will be set to 1, 2 or 3 respectively. The azimuth and elevation angles
will vary between -90 and 90 degrees if a signed radial distance is selected. The azimuth will vary between
-180 and 180 degrees if the unsigned radial distance is selected.
Input Channels
1294
Output Channels
Parameters
TLSN, other

Required if Header Containing Component ID equal other.
Operator Component ID
Value of Header Containing Component ID which defines the operator.
Operand Component ID
Value of Header Containing Component ID which defines the operand.
Geophone Component ID
Value of Header Containing Component ID which defines the geophone for PZ summation.
Hydrophone Component ID
Value of Header Containing Component ID which defines the hydrophone for PZ summation.
Apply Shaping Filter

Options: YES, NO
Start of Filter Derivation Window (ms)

1295
End of Filter Derivation Window (ms)

Filter Length(ms)
Operation:
Multiply by ABS, Arc Tangent (-Pi/2 to Pi/2), Arc Tangent2 (-Pi to
Pi), PZ Summation/Difference, Convolution, Cartesian to
Spherical,Subtract - Minimize Energy
Scale Factor for Operator.

The operator trace is multiplied by this number prior to the operation.
Zero divide replacement value.

If a zero divisor is detected, the output is set to this value. This parameter is accessed if Dataset operation
= Divide.
Header Containing Validation Value 1

TLSN, other

Required if Header Containing Validation Value 1 equalother.
Header Containing Validation Value 2

TLSN, other

Required if Header Containing Validation Value 2 equalother.
1296
Action if header mismatch

Options: Process and set TRID to 5, Do Not Process, Process Valid
trace pairs only
Process All Trace Pairs

Options: YES, NO
Print validation failures

Options: YES, NO
Geophone X Component ID
Value of Header Containing Component ID which defines the X axis.
Geophone Y Component ID
Value of Header Containing Component ID which defines the Y axis.
Geophone Z Component ID
Value of Header Containing Component ID which defines the Z axis.
Compute signed radial distance

Options: YES, NO
Normalize Cross-correlation
Options: YES, NO
Computation Window(ms)
1297
TRACEFFT
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRACEFFT performs a standard fast Fourier transform or its inverse on a trace. The output may be
configured as complex frequency pairs or amplitude and phase. Phase may output in radians or degrees.
The real and imaginary components may be grouped by frequency or component. The reference point for
the forward transform may be set to any point within the window. The start time and reference point are
captured in the output trace headers so the original trace may be duplicated. The transform trace will
always be a power of 2 in length.
Input Channels
Output Channels
Parameters
Fourier Transform Direction
Transform from time to frequency domain (Forward) or frequency to time (Reverse).
1298
Transform Order
The transform trace is either ordered in complex pairs (Complex, i.e. sin,cos) or all real values first in the
Phase Units
Window Start Time (ms)

The start time of the window to be transformed. This parameter is accessed if Fourier Transform
Direction is set to Forward.
Window End Time (ms)

The end time of the window to be transformed. This parameter is accessed if Fourier Transform
Direction is set to Forward.
Transform Length Multiplier

The Fourier transform length is generally set to the next power of 2 greater than the transform window.
This parameter allows the user to lengthen the transform to prevent wrap around. This parameter is
accessed if Fourier Transform Direction is set to Forward.
Reference Time
The phase reference time within the window to be transformed. This parameter is accessed if Fourier
Transform Direction is set to Forward.
Output trace length

The output trace length may be set to any portion of the original transformed data. Note that the original
transform start and reference times will be used in reconstructing the trace. This parameter is accessed if
Fourier Transform Direction is set to Reverse.
1299
TRANSPOS
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRANSPOS will transpose the axes within an ensemble. That is
TRACE(HDR(ENSKEY),TIME) => TRACE(TIME,HDR(ENSKEY)).
After the transpose operation, traces will lie horizontally rather than vertically in DISPLAY. TRANSPOS
can be used to compute time slices for an entire stacked volume. The sample interval will be set so that
DISPLAY will label the vertical axis properly.
Input Channels
Output Channels
Parameters
Ensemble Sample Interval
The expected interval between values of the ensemble header word.
Minimum Ensemble Value

The minimum expected ensemble key value.
1300
Maximum Ensemble Value

The maximum expected ensemble key value.
Ensemble bias value

The bias will be subtracted from the ensemble key value prior to transposition. For reverse transposition,
use the bias value coded in the forward transposition.
Forward or reverse ensemble

Output Ensemble Interval

Options: Use Input SI, Scale Input SI, Index
Output Interval Scalar

Scalar to be applied to input sample interval for ensemble key interval.
1301
TRCPLOT
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRCPLOT is the simplified version of PLOT. With fewer parameters, it is basically used to plot prestack
traces. All parameters have default. The timing lines automatically drawn are the 100ms lines in most
cases. The user has the option to draw the 10ms timing lines (dot lines). The default timing line
annotations are on both sides of the plot, user is given the option to annotate between ensembles.
Input Channels
Output Channels
1. Plot data set: Required connection to dataset CGM data type.
Parameters
Show GCI trace header word 5
Options: NONE, Ensemble key, Primary key, Secondary key, CDPN, DIST,
FCSN, FSPN, OIDN, MBIN, MLIN, MSBN, MSLN, RSBN, RSLN, SDPN, SGEN,
SBIN, SLIN, SSBN, SSLN, SSPN, TLSN, Other
GCI trace header word 5 number

1302




The plot display mode
Options: Wiggle only, Positive VA, Negative VA, Wiggle & positive
VA, Wiggle & negative VA, Wiggle & both VA, Both VA only, Color only,
Color & wiggle, Wiggle & color VA, Color & wiggle & black positive
VA, Color & wiggle & black negative VA
Color scheme
Gray scale of positive VA fill
Gray scale of negative VA fill

1303
Physical plot dot per inch

Allow overlap VA?
Polarity at which to plot data
Automatic scaling?
If automatic scaling is chosen, TRCPLOT will compute the average RMS amplitude level over the first
ensemble of traces. For non-amplitude type data like RMS velocities or Hilbert transform attributes. The
scaling is determined by the minimum and maximum values.

Select No to specify the range of amplitudes using the gain in db. and a bias. Select Yes to specify the
range of amplitudes using the minimum and maximum values
Gain (db)
The amount of gain in db to apply to the data before plotting.
Bias (%)

Specify the sample value corresponding to the minimum clipped value. For color displays, this is the
minimum color index.

Specify the sample value corresponding to the maximum clipped value. For color displays, this is the
maximum color index.
Clip (traces)
clipped. For color the minimum and maximum amplitude can be determined from this parameter to scale
the amplitudes over the number of colors in the color map.
1304
Overlay gain (db)

The amount of gain in db to apply to the overlay data before plotting. This parameter requires the Overlay
input channel to be connected.
Overlay clip (traces)

clipped. This parameter requires the Overlay input channel to be connected.
Overlay bias
This parameter requires the Overlay input channel to be connected.
Plotting direction
Number of traces per inch

Inches per second

Enter the number of inches per second for the trace display.
Wiggle thickness (inches)

Starting time (ms)
Ending time (ms)
Annotate heavy lines?
Interval with heavy timing lines (ms)
Annotate medium lines?
Interval with medium timing lines (ms)
1305
Annotate light lines?

Interval with light timing lines (ms)
Annotate dotted lines?
Interval with dotted timing lines (ms)
Gap for missing traces?
Gap between ensembles?
Width of ensemble gaps (inches)
Need timing line anno. between gaps?
How to make gap annotations?
Options: Based on number of ensembles, Based on custom matrix
Number of ensembles between anno.

Custom matrix for gap annotations
Matrix Type: TRCPLOT_GAP
Width of anno. gaps (inches)

Annotation mode in the gaps
Options: Single annotation, Double annotations
Comment
Matrix Type: TRCPLOT_CMT
Print processing history detail

By default, option None is selected and no history is printed in the side label. If you select option
Modules, it prints the job queue and modules names used for that job queue. If you select option
Parameters, it prints the job queue, modules names and the parameters for each module used for that job
queue. If option Matrix is selected, the job queue, modules names, the parameters and, the contents of
selected matrices are printed in the side label.
1306
Options: None:, Modules:, Parameters:, Matrix:
Print default parameters

In case of option Matrix or Parameters if you select Yes, all the parameters are printed in the side label.
if you select No, default parameters are not printed in the side label.
1307
TRCREM
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRCREM is a general purpose trace removal tool. The default mode is for removing the manufactured
near traces from a pre-stack ensemble added previously by the NTEXT module. In this case any trace with
a negative value in GCI header index 77 will be removed. The second option allows the user to remove
specific traces based upon their indices (position) in the ensemble.
Input Channels
Output Channels
Parameters
Remove option
Options: Use header 77, Remove by trace indices
Starting trace number in ensemble

This value refers to the trace index (position) of the traces as they are passed into TRCREM.
Number of traces to skip

This value refers to the stride of removal. If consecutive traces are to be removed, it should be 0. To
remove every other trace it should be 1.
1308
Number of traces to remove

This value must be set for the largest ensemble in the dataset. This module will not try to remove
non-existent traces.
1309
TRIMCMP
Module Description
Input Channels
Output Channels
Parameters
Module Description
The TRIMCMP module optimizes trace alignments within a CMP gather. This module will be useful for
removing residual NMO errors within the CMP gather for later AVO analysis. The pilot trace for the static
correction can be built using stacks of nearby CMPs or an external pilot dataset can be connected. The
module computes and applies trim statics in a time variant manner using time gates selected by the user.
After all efforts have been made to obtain the optimum surface-consistent statics and NMO velocity
corrections have been applied, trim statics can be computed and applied to the CMP gather. The user
selects time gates interactively using SeisUP. The seismic trace is split using the time gates for the trim
static analysis. The traces within the CMP gather are cross-correlated against a master pilot trace. The
cross-correlations are used to pick time shifts, which best align the traces within the gather. The output
trace is shifted by the static within the time gate using Lagrange Interpolation.
The technique should work well in data areas with low to moderate noise. If the residual NMO errors are
large, you might have to perform several runs of this module to remove all the static error.
A subset of the dataset can be used by providing a min/max bin and line number. The default is to find the
min/max values from the database.
Two methods for the pilot trace are provided. The internally built pilot trace is the stacked sum of all the
traces within the CMP gather. The master pilot trace is the stacked sum of nearby pilot traces. The module
allows the user to specify how many pilot traces are stacked into the master pilot trace. An external dataset
can also be connected to the module. The external dataset should contain pilot traces that are used to
compute the statics. The external dataset traces must have the same number of samples, sample rate, and
line/bin numbering scheme as the internal dataset. In both methods the data may optionally be muted prior
to entering the computations. The output data is not muted.
The module will accept a matrix of time-space variant time gates. A static value is computed for the center
of each time gate and trace. The static is interpolated from time gate center to the next time gate center.
The module will also accept a start and end time along with a window gate. The start/stop times will be
broken into separate windows of gate length. The last window might be shorter than the other windows if
the start/stop time is not divisible by the gate length. The static applied will be interpolated from gate
center to gate center.
The user has the option to specify a time header value to add to each start and stop time. This allows the
time to be adjusted to follow seismic events that might be dipping. The user has the option to apply GCI
header word TIM1 to the start time and TIM2 to the end time for each window.
1310
The user can specify a minimum number of samples with the time gate to be non-zero before the trace is
used in the analysis. If a time-gated trace has less than the minimum needed samples, then the static is set
to zero for this time-gate.
For each correlation between the pilot and trace, a correlation coefficient is computed. This value lies
between 0 and 1, with 1=perfect fit, while 0=absolutely no fit. The module allows you to set a minimum
correlation coefficient that is acceptable to apply a static. If the correlation coefficient for a time gated
trace is less than the minimum, then the static is not applied to that time-gated trace.
A maximum allowed static limit is also entered to limit the amount of static correction applied to the trace.
The static will never exceed the maximum allowed static. If time variant gates are used, then the total
static for the trace will not exceed the maximum allowed.
Input Channels
2. Input model pilot traces: Optional GCI data type.
Output Channels
Parameters
Method to use pilot
Select to compute the pilot traces from nearby CMPs or get the pilot traces from an external dataset.
Options: Build pilot from input data, External pilot from another
dataset
Bins to include in pilot calculation (odd number)

Specify the number of pilots to stack for the master pilot used in the statics computation. A pilot is the
stacked trace for each CMP ensemble. The master pilot is built using several nearby pilots that are stacked
together. This parameter represents the number of nearby pilots to stack for the master pilot. This value is
expressed as bin numbers. If the data is 2D then the value used for comparison is the sequential CMP
number (SDPN, header word 6). For 3D surveys, the comparison number is midpoint bin number (MBIN,
header word 66).
1311

A subset of the data can be used. Enter the minimum midpoint bin number to use.

A subset of the data can be used. Enter the maximum midpoint bin number to use.

A subset of the data can be used. Enter the minimum midpoint line number to use.

A subset of the data can be used. Enter the maximum midpoint bin number to use.
Maximum allowed static (msec)

Specify the maximum static in milliseconds to limit the magnitude of the computed static. The static
within a time window cannot exceed this value.

Specify the number of samples in the time window that must be valid before this trace is used in the
analysis. This value is expressed in the percent of live (non-zero) values within the time window. The
trace within the time gate will be rejected for static analysis if the number of valid samples is less than the
percentage stated for this parameter.
Minimum correlation coefficient allowed (0 to 1)

Specify the minimum correlation coefficient that is allowed before the static value is ignored for a
time-gated trace. For each correlation between the pilot and trace a correlation coefficient is computed.
This value lies between 0 and 1, with 1=perfect fit, while 0=absolutely no fit. The module allows you to
set a minimum correlation coefficient that is acceptable to apply a static. If the correlation coefficient for a
time gated trace is less than the minimum, then this static is not applied to that time-gated trace. This
parameter allows you to ignore static picks when the pilot and trace to not correlate very well. A value of
0.0 means that all correlation coefficients are allowed.
Time and space variant windows?

1312
Start time (msec)

Specify the start time in milliseconds for the time gate to use in the analysis. This option will appear if a
End time (msec)

Specify the end time in milliseconds for the time gate to use in the analysis. This option will appear if a
Window gate length (msec)

The start and stop time window can be broken into separate time gates. The window gate is specified in
milliseconds. Each window gate will have a static computed. The statics will be interpolated from gate
center to gate center.
Primary header key

TLSN

values.
TLSN
Windows matrix
secondary key, start time, and end time values.

If the trace header has a start time in it, you can use it to adjust the trace window start time. Use this
feature to track an event in space and time. See GCI trace header word 84 (TIM1).
1313

If the trace header has a end time in it, you can use it to adjust the trace window end time. Use this feature
to track an event in space and time. See GCI trace header word 85 (TIM2).
Apply a mute to the computation

This option allows the user to apply a mute to the data going into both the internally generated pilot and
the traces used to perform the correlations. The output data is not muted.
Mute matrix
Required if Apply a mute to the computation is Yes.

Required if Apply a mute to the computation is Yes. If you have chosen to mute the traces going into the
computations, enter the primary header key for the mute matrix values.
TLSN

Required if Apply a mute to the computation is Yes. If you have chosen to mute the traces going into the
computations, enter the secondary header key for the mute matrix values.
TLSN
Mute taper (msec)

Required if Apply a mute to the computation is Yes.
Read external pilot as needed

Required if Method to use pilot is External pilot from another dataset. The default is to read the external
pilot into memory. It is faster to do so but there may not be enough memory available.
1314
TRIP
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRIP will interpolate traces by linear interpolation between two traces along the top two dominant dip
directions. The dominant dip direction is measured by finding the maximum coherency along a range of
dips from neighboring traces. TRIP can interpolate missing traces and/or interpolate new traces. TRIP uses
the ensemble header word (see GCI) to determine if there are missing traces. When interpolating new
traces, the ensemble header word is renumbered. TRIP will drop dead and auxiliary traces before the
ensemble header word is checked when determining the number of traces to interpolate. Traces headers
will also be linearly interpolated.
Input Channels
Output Channels
Parameters
This is the number of neighboring traces to use to determine the dominant dip. TRIP will force this
number to a lower even number.
Number of output traces per input trace

Code a one to interpolate missing traces. The default will result in twice as many traces per ensemble.
1315
First input ID within each ensemble

TRIP will renumber the ensemble header word when the number of output traces per input trace is greater
than one. TRIP will multiply the ensemble header word by the number of output traces per input trace. To
make the new ensemble header words start at the same starting input ensemble id, enter the original
starting value here.
The preceding paragraph has caused some confusion. What happens is that ensemble header is multiplied
by Number of output traces per input trace which if you are doubling the number of bins will give you
twice the starting number. The output ensemble number is the above minus First input ID within each
ensemble * ( 1 - Number of output traces per input trace).
Max. # of traces to interpolate between traces

This is the maximum number of traces to interpolate between existing input traces. The default is two
times the number of output traces per input trace.
Minimum dip in Ms. per trace

Maximum dip in Ms. per trace

Dip increment in Ms. per trace
This is the dip increment in Ms. per trace between the minimum and maximum dip defined above. TRIP
will determine the coherency at each dip increment.

Increasing this parameter will result in smoother dominant dip estimates in the time direction.
Set fold to 0 on interpolated traces

The default is to interpolate the FOLD header.
1316
TRIP5D
Module Description
Input Channels
Output Channels
Parameters
Module Description
TRIP5D can be used to perform 5D interpolation using inverse distance weighting along the top two
dominate dip directions. The dominant dip direction is measured by finding the maximum coherency
along a range of dips from neighboring traces within a user specified radius of the trace needing to be
interpolated. The traces interpolated are those flagged as dead. Whereas other interpolation algorithms use
binned trace header words. TRIP5D uses coordinates and thus no bin center correction is needed prior to
running this module.
5D interpolation
5D interpolation is actual 4 spatial coordinates plus time. Interpolation is not performed in time or
frequency but the industry has used this convention and this is used here. TRIP5D can perform 2D, 3D,
4D or 5D interpolation. 2D and 3D interpolation is performed in-core while the others are performed
out-of-core via the hard disk drive. Although the following keys are requested, they are not actually used
but rather used to define the interpolation direction:
Primary: This is the outer most sort and usually corresponds to the primary sort key in the READ
module.
Secondary: This is the second slowest key and usually corresponds to the secondary sort key in the
READ module.
Y: This is the second fastest key within the ensemble sort key as defined in the READ module.
X: This is the fastest key within the ensemble sort key as defined in the READ module.
Pre-processing
TRIP5D uses the source and receiver coordinates to determine spatial locality. Make sure the
coordinates match the trace headers being used for the sorting and thus the keys mentioned above.
Although not a requirement, it is suggested to apply NMO prior to running TRIP5D. A mute may be
applied but is not mandatory either.
Inject dead traces for those you wish to interpolate. Use either of the following module groups:
HDRINTP: This module will insert dead traces corresponding to missing gridded locations.
Make sure to turn on the parameter "Create geometry headers from interpolation?" to "Yes"
because TRIP5D requires valid source and receiver coordinates.
SRINTERP and GEOM: This combination can be used to interpolate new sources or receivers
that typically would be used within a land environment. SRINTERP will define the new
coordinates and GEOM will insert dead traces corresponding to them.
1317
Trajectories
TRIP5D will search for the dominate dip direction between a user specified range. Increasing this range
will result in increased computations while having an inadequate range will result in poor interpolation.
Trajectories are defined in Milliseconds per unit of distance, I.E. Ms/ft or Ms/m. To determine the proper
range, the following is suggested:
Sort to each interpolation direction. I.E. CMP, inline common offset, x-line common offset.
Within each ensemble determine the maximum local time difference and the distance between those
points. When measuring over common offsets use MCX and/or MCY to determine distance. For
CMP gathers use the half offset defined as ABS(DIST/2). Once the time difference and spatial
distance are calculated, the trajectory is then simply time divided by the distance.
Prior to running a full 5D interpolation it is suggested to perform a trial 2D or 3D interpolation using
the measured trajectories to make sure one has adequate interpolation.
Radial distance
TRIP5D requires two different radial measurements as follows:
Dip scanning: TRIP5D will scan for the dominate dip direction for all traces falling within this radius.
Increasing this distance can help in a noisy environments but only if the events are linear within this
distance. However be forewarned that increasing this distance will cause the computation to be
increased exponentially.
Interpolation: TRIP5D will use inverse distance weighting for all traces within this radius. The
module TRIP only used linear interpolation between the two closest traces. Increasing this distance
can produce unwanted somewhat linear artifacts in the presence of random noise. Currently this
distance must be less than or equal to the dip scanning radius.
Override: It is possible to specify a minimum and/or maximum number of points to allow the radial
distance to be expanded or contracted.
If after interpolation some traces are still dead, one can Q.C. the interpolation process by observing the
following header words:
Header 43: 0 means the header was not interpolated while 1 means it was.
Header 44: For interpolated or dead traces, this is the minimum distance found between surrounding
traces and the one being interpolated. If the trace is dead and falls within the user specified
interpolation dip or interpolation radius, it is possible the criteria for the number of traces within this
range have not been met.
References
Abma, R., 2009, Issues in multi-dimensional interpolation: SEG Technical Program Expanded Abstracts,
1152-1156
1318
Lu, L., 1985, Application of local slant stack to trace interpolation: 55th Annual International Meeting,
SEG, Expanded Abstracts, 560-562.
Stanton, A., Kreimer, N., Bonar, D., Naghizadeh, M., and Sacchi, M., 2012, A comparison of 5D
reconstruction methods: SEG Technical Program Expanded Abstracts 2012, pp. 1-5.
Trad, D., 2008, Five-dimensional seismic data interpolation: 78th Annual International Meeting, SEG,
Expanded Abstracts, 27, 978982
Trad, D., 2009, Five-dimensional interpolation: Recovering from acquisition constraints: Geophysics,
74(6), V123-V132.
Wang, J., Ng, M., and Perz, M., 2010: Seismic data interpolation by greedy local Radon transform:
Geophysics, 75(6), WB225-WB234
Wojslaw, R., Stein, J., and Langston, T., 2012, 5D Semblance Based Interpolator in Exploration - Theory
and Practice: 74th Conference and Exhibition, EAGE, Extended Abstracts, B024.
Input Channels
1. Input: Required connection from previous process - GCI data type.
Output Channels
1. Next process: Required connection to next process - GCI data type.
Parameters
Interpolation dimension
Select the desired interpolation dimension.
Options: 2D, 3D, 4D, 5D
X direction header key

Y direction header key
1319
S direction header key

P direction header key
Select the key corresponding to this direction. TRIP5D does not use this actual header word but rather
uses it to determine interpolation direction. I.E. For CMP sorted input data and for full 5D interpolation
this would be Primary=MLIN, Secondary=MBIN, Y=AZIM and X=DIST. For a 4D interpolation select
nothing for the Y direction if one wishes to ignore azimuth.
Options: MBIN, MLIN, DIST, AZIM, nothing
X direction trajectory minimum(Ms/(ft/m))

Y direction trajectory minimum(Ms/(ft/m))
S direction trajectory minimum(Ms/(ft/m))
P direction trajectory minimum(Ms/(ft/m))
Enter the minimum trajectory for this direction that is used for dip scanning measured in time divided by
unit distance.
X direction trajectory maximum(Ms/(ft/m))

Y direction trajectory maximum(Ms/(ft/m))
S direction trajectory maximum(Ms/(ft/m))
P direction trajectory maximum(Ms/(ft/m))
Enter the maximum trajectory for this direction that is used for dip scanning measured in time divided by
unit distance.
*************End of X section*****************
*************End of Y section*****************
*************End of S section*****************
1320
*************End of P section*****************
Dummy parameters that serve to break up the parameter display.
S direction minimum key value

For 4D and higher interpolations, enter the minimum Secondary direction header value. This value is used
to store ensembles to the hard disk drive for out of core computations.
S direction maximum key value

For 4D and higher interpolations, enter the maximum Secondary direction header value. This value is used
S direction key value increment

For 4D and higher interpolations, enter the Secondary direction header value increment. This value is used
Maximum frequency in the data(c/s)

TRIP5D will automatically compute the dip scan increment based upon this parameter and the maximum
radial dip scan distance. Specify the maximum frequency for observed reflection events wishing to be
interpolated. Do not necessarily enter the nyquist frequency for this parameter will impact not only
computation time but also the impact of conflicting dips at a certain location.
Maximum radial dip scan distance(ft/m)

TRIP5D will scan for the dominate dip direction for all traces falling within this radius. Increasing this
distance can help in a noisy environments but only if the events are linear within this distance. However be
forewarned that increasing this distance will cause the computation to be increased exponentially.
Maximum radial interpolation distance(ft/m)

TIP5D will use inverse distance weighting for all traces within this radius. Increasing this distance can
produce unwanted somewhat linear artifacts in the presence of random noise. Currently this distance must
be less than or equal to the dip scanning radius.
Interpolation power factor

For traces falling within the maximum radial interpolation distance, they are weighted by an inverse
distance calculation as follows:
, where d is the distance between the interpolated trace and the
neighboring trace and p is this interpolation power factor.
1321
Minimum # of traces for dip scan

Enter the minimum number of traces to be use for dip scanning. Enter a value of four to roughly
correspond to the default in the module TRIP. If the minimum is not met, the radius of the dip scanning
search will be increased but not allowed to increase too far from the maximum interpolation radius.
Minimum # of traces for interpolation

Enter the minimum number of traces to be used for interpolation. If the number of traces that fall within
this radius is not enough, TRIP5D will not interpolate the trace. A value of 1 can result in increased linear
artifacts while a higher value can result in too few interpolations.
Maximum # of traces for interpolation

Enter the maximum number of traces to be used for interpolation. Increasing this parameter can result in
traces that are smeared and with less noise as compared to non-interpolated traces.

Increasing this parameter will result in smoother dominant dip estimates in the time direction but could
harm conflicting dips.
Set fold to 0 on interpolated traces

This parameter also exists in FKINT and TRIP and is included for other modules that use this
methodology to indicate if the trace is interpolated or not.
Maximum memory to use per node(MB)

For large surveys, it is possible for 5D interpolations to need a large amount of memory. Enter the
maximum amount of memory to use in megabytes for each node.
Number of cluster nodes to use

Enter the number of cluster nodes to use for each interpolation. For 3D and lower transforms, different
ensembles with be used on different nodes. For 4D and 5D interpolation, the interpolation problem will be
distributed over the nodes.
Compute node list

When using cluster nodes enter a matrix containing the nodes to use. Enter in MPICH2 format.
1322
Number of threads to use per node

To increase performance enter a value greater than one. Make sure in this case that the node you are
running on has multiple cores.
Verbose?
Select Yes to output more verbose print-out.
1323
TVEQ
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVEQ is an amplitude equalization module. Options to perform absolute value mean, bi-directional, or
alpha trim mean are included. Gaining the data by the mean over time windows is the traditional way to
perform "Automatic Gain Control" or AGC. A new option allows you to save the applied gain values to a
GCI dataset file so that you can remove the gain later.
The gaining options include:
ABSOLUTE VALUE MEAN applies absolute-value-mean (AVM), "AGC", to data on a
sample-by-sample basis with a user-specified window length. This is the traditional approach to
Amplitude Gain Correction. The AVM level (default 2500) may be specified. The presuppression level
(default 0%) allow zones much below the amplitude envelope to remain unscaled, such as data before
"first breaks".
BIDIRECTIONAL MEAN uses a forward and backward looking set of sliding windows to equalize the
data. As each data sample is corrected it is preceded by a forward-looking window and followed by a
backward looking window. The windows are separated by a gap with the analyzed data in the center of the
gap.
ALPHA TRIMMED MEAN uses a single window but does not include data in the analysis window,
which is far in value from the absolute value mean of the window.
A new option allows the applied trace sample gains to be saved to a GCI dataset if a data set is connected
to the appropriate output channel. The "saved gain" dataset can then be connected to another TVEQ on the
input channel and the "Gain" removed from the data set input through the read module. Although a
compatibility check is made between the input and the gain data set, the removal is performed
sequentially. This implies the gain and input data sets must be written in the same order with no missing
data.
Input Channels
2. Optional input gains: Optional connection from dataset GCI data type.
1324
Output Channels
2. Optional output gains: Optional connection to dataset GCI data type.
Parameters
Apply or remove gain.
Select to apply or remove the gain values to the seismic trace data. If you want to remove the gains at a
later time then the Apply method must be computed once with the following parameter: Save applied
gains for later removal, set to YES. If the REMOVE option is selected then there must be a valid GCI
dataset containing the saved gain values on a geodraw icon input or output channel.
Gain correction method.

Select the gaining method. Three choices are offered: Absolute value mean, bi-directional mean, and
Alpha trimmed mean.
Options: Absolute value mean, Bi-directional mean, Alpha trimmed
mean
Pre-suppression level in percent.

Required if Gain correction method. = Absolute value mean. The presuppression level (default 0%)
allow zones much below the amplitude envelope to remain unscaled, such as data before "first breaks".
Gain window length (ms).

Enter the gain window in milliseconds. This window is used to compute the means, then the mean is
applied to the trace values in the window.
Reference mean.
Select a reference mean value, so all traces in the dataset are in the same mean range.
Percentage, alpha, of the window samples used.

Required if Gain correction method. = Alpha trimmed mean. A value of 0.0 is the same as the AVM
method. A value of 100.0 is a median AGC.
1325
Number of samples between data and edge of windows.

The number of samples between the data sample being corrected and edge of each sliding window. If zero,
no gap will exist between the windows. If 1, a two sample gap will exist between the windows.
Required if Gain correction method. = Bi-directional.
1326
TVMULT
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVMULT will perform time variant multiple attenuation using a low cut K filter especially designed for
multiple attenuation. Input should be CMP gathers with normal moveout applied using velocities
corresponding to the multiples (Multiples should be flat). If you are subtracting the filtered output from the
input, the velocities should correspond to the real data. Better results have been experienced by using
multiple velocities and not subtracting.
After TVMULT is run, module NMOA should be run using the same velocities used in the NMOR before
TVMULT. TVMULT assumes that there is an even trace spacing between traces. Up to five filters and
their corresponding start and stop times may be chosen.
1327
1328
Input Channels
1329
Output Channels
Parameters
Time variant?
Primary header key
TLSN

TLSN
Low cut K filters

Matrix Type: LCKF

Restore amplitude?
1330
TVSA
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVSA (time variant spectral adjustment) is a trace-by-trace time variant (adaptive) frequency band noise
rejection module. Typical use is to remove source generated low frequency noise from shots with SPER
applied. Each sample of interest is spectrally analyzed using a gate surrounding the sample, the spectrum
adjusted over a user selected range, inverse transformed and that new sample output.
Input Channels
Output Channels
Parameters
Velocity of noise
The noise velocity is the slope of a line from the shot with the noise cone below.

The spectrum for each sample is smoothed and used to detect anomalous components. The smoother
length is this percent of the total FFT length.
Start adjustment frequency

Start frequency to adjust in Hz.
1331
End adjustment frequency

End frequency to adjust in Hz.
Gate length (ms)

The gate length of 300 msec surrounding any sample will suffice for most land shots to estimate the
lowest frequency present.

The gate surrounding a sample is tapered by this length at each end before FFT to avoid "zero frequency"
problems.

Padding in the frequency domain is common to reduce circular convolution artifacts.
Spectral adjustment power

This value controls the strength of the anomalous spectral bump reduction. Start low (.2 or .3) and increase
if anomalous components remain.
Number of spectral adjustments

Increasing the number of adjustments gives stronger stronger bump reduction.
Minimum offset for amplitude reference computation

A reference amplitude spectrum is computed from traces with this offset as minimum at the center time
described below. This spectrum is used to adjust spectral amplitudes in the spectral zone between start and
end frequencies.
Time for amplitude reference computation (ms)

Center gate time for traces used to compute the spectral reference as described above.
Number of threads
Desired number of threads for parallel execution. Set this number to number of CPUs on SMP machine.
1332
TVSAC
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVSAC (time variant spectral adjustment) is a trace-by-trace time variant (adaptive) frequency band noise
rejection module written for cluster execution. Typical use is to remove source generated low frequency
noise from shots with SPER applied. Each sample of interest is spectrally analyzed using a gate
surrounding the sample, the spectrum adjusted over a user selected range, inverse transformed and that
new sample output.
Input Channels
Output Channels
Parameters
Velocity of noise
The noise velocity is the slope of a line from the shot with the noise cone below.

The spectrum for each sample is smoothed and used to detect anomalous components. The smoother
length is this percent of the total FFT length.
Start adjustment frequency

Start frequency to adjust in Hz.
1333
End adjustment frequency

End frequency to adjust in Hz.
Gate length (ms)

The gate length of 300 msec surrounding any sample will suffice for most land shots to estimate the
lowest frequency present.

The gate surrounding a sample is tapered by this length at each end before FFT to avoid "zero frequency"
problems.

Padding in the frequency domain is common to reduce circular convolution artifacts.

This value controls the strength of the anomalous spectral bump reduction. Start low (.2 or .3) and increase
if anomalous components remain.
Number of spectral adjustments

increasing the number of adjustments gives stronger stronger bump reduction.
Minimum offset for amplitude reference computation

A reference amplitude spectrum is computed from traces with this offset as minimum at the center time
described below. This spectrum is used to adjust spectral amplitudes in the spectral zone between start and
end frequencies.
Time for amplitude reference computation (ms)

Center gate time for traces used to compute the spectral reference as described above.
Number of threads per node

Desired number of threads for parallel execution. Set this number to number of CPUs on the selected
cluster node.
1334

Enter the desired number of nodes to use.

Default 1.
Compute node list

Enter the name of a list of cluster nodes to use.

Build a node list.
1335
TVSE
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVSE is a module to perform time variant spectral enhancement of usable frequencies in a trace. Seismic
traces generally have a "red" spectrum rich in the lower frequencies. Typically an application of spiking
deconvolution will change the trace spectrum to flat or "whiten the spectrum". TVSE applies a time
variant algorithm to tip the spectrum up toward the higher frequencies or "blue" the spectrum. The user
specifies the desired four frequency bandwidth trapezoid at top and bottom of the trace. Make sure the
trace has usable reflections within this bandwidth. "Blueing" is controlled by "Spectral adjustment power"
and "Blueness slope". The defaults should produce a "flat" spectrum across the specified bandwidth. If a
full flat bandwidth is not achieved and falls short of the specified bandwidth, most likely there are no
reflections in the higher bandwidths.
Input Channels
Output Channels
Parameters
Top start frequency
The final amplitude spectra after TVSE should be trapezoidal and the four user defined frequencies may
vary linearly from top of trace to bottom of trace. Typically the low frequency start and corner is the same
for the whole trace.

See Top start frequency above.
1336

This is the frequency where the output amplitude spectra will change slope. If "blueness slope" is zero the
spectra should be flat until the high corner frequency. If the spectra drops before the high corner, some
higher frequencies were not recorded at this sample rate. If the "Blueness slope" is a positive number the
spectrum should slope upward with higher frequency.

See Top low corner frequency above.

This is the frequency where the spectrum should change slope and head steeply down toward the Top end
frequency.

See Top high corner frequency above.
Top end frequency

This is the highest frequency for spectral adjustment at top of trace.

See Top end frequency above.

If the final output spectra falls below the specified frequency parameters raising the Spectral adjustment
power may help shape the spectra.
Blueness slope
This is the slope of the spectral from from low corner frequency to high corner frequency.
Gate length (ms)

This length in ms should be about the length of one cycle of the lowest frequency of interest.
1337

This should be about 5% of the gate length (at least 3 samples).

Typically 30% padding will prevent Fourier wraparound.
Number of threads
This number should be equal to or less than the number of CPUs on your server.
1338
TVSEC
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVSEC is a module to perform time variant spectral enhancement of usable frequencies in a trace. This is
the same module as TVSE but TVSEC runs on the cluster. Seismic traces generally have a "red" spectrum
rich in the lower frequencies. Typically an application of spiking deconvolution will change the trace
spectrum to flat or "whiten the spectrum". TVSEC applies a time variant algorithm to tip the spectrum up
toward the higher frequencies or "blue" the spectrum. The user specifies the desired four frequency
bandwidth trapezoid at top and bottom of the trace. Make sure the trace has usable reflections within this
bandwidth. "Blueing" is controlled by "Spectral adjustment power" and "Blueness slope". The defaults
should produce a "flat" spectrum across the specified bandwidth. If a full flat bandwidth is not achieved
and falls short of the specified bandwidth, most likely there are no reflections in the higher bandwidths.
Input Channels
Output Channels
Parameters
Top start frequency
The final amplitude spectra after TVSEC should be trapezoidal and the four user defined frequencies may
vary linearly from top of trace to bottom of trace. Typically the low frequency start and corner is the same
for the whole trace.

See Top start frequency above.
1339

This is the frequency where the output amplitude spectra will change slope. If "blueness slope" is zero the
spectra should be flat until the high corner frequency. If the spectra drops before the high corner, some
higher frequencies were not recorded at this sample rate. If the "Blueness slope" is a positive number the
spectrum should slope upward with higher frequency.

See Top low corner frequency above.

This is the frequency where the spectrum should change slope and head steeply down toward the Top end
frequency.

See Top high corner frequency above.
Top end frequency

This is the highest frequency for spectral adjustment at top of trace.

See Top end frequency above.

If the final output spectra falls below the specified frequency parameters raising the Spectral adjustment
power may help shape the spectra.
Blueness slope
This is the slope of the spectral from from low corner frequency to high corner frequency.
Gate length (ms)

This length in ms should be about the length of one cycle of the lowest frequency of interest.
1340

This should be about 5% of the gate length (at least 3 samples).

Typically 30% padding will prevent Fourier wraparound.
Number of threads per node:

Desired number of threads to use on each cluster node. Set this to the number of CPUs on the selected
cluster node.
Number of Nodes in the Cluster:

Set this to the number of cluster nodes you wsh to use.

Enter the number of CPUs on each cluster node.
Compute node list

Enter the name of a list of cluster nodes to use.

Build a node list.
1341
TVTRIM
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVTRIM is a continuous time variant trim static application (not gate-by-gate). The static for any sample
depends upon the correlation coefficient of its gate with the pilot and if that correlation coefficient is
greater than a user specified minimum. If the coefficient is lower than the minimum this sample will be
shifted by an interpolated value based upon the strong correlation nearest above and that nearest below in
time. NOTE: The quality of the trim statics will depend upon the signal to noise ratio and coherence of the
events on the input pilot stack.NOTE: TVTRIM searches the pilot dataset for a trace matching the
MLIN,MBIN of the current ensemble for static analysis. If the pilot cannot be found, the gather is passed
without static analysis and application.
Input Channels
2. Pilot: Required GCI data type.
Output Channels
Parameters
Enter a value large enough to enclose the event character, say 150 ms or a bit more.
Maximum static (ms)

Enter the maximum static value desired, usually just a few ms, like 8-12.
1342
Minimum correlation coefficient (ms)

For data with good signal to noise this should be high, say .6-.7. On datasets with excessive random noise
this value should be reduced to maybe .3-.5.
Percent live samples needed for usable gate

Traces with few live samples give poor correlation estimates.
Number of threads
More threads means faster execution. A reasonable number is the number of CPUs on the server.
1343
TVZD
Module Description
Input Channels
Output Channels
Parameters
Module Description
TVZD is a time domain process that performs continuous time variant zero phase deconvolution. TVZD
will dynamically whiten the frequency spectrum of a trace within a user specified frequency pass band.
The input trace is partitioned into a number of sub-bands and the amplitudes of these sub-bands are
equalized using a continuously time variant technique. The equalization technique can be one of the
following:
1. For each sub-band, an AGC is applied. To restore the original amplitude, TVZD can on option force
the envelope of the sum of all the sub-bands to be equal to the envelope of the input data.
2. An average envelope is computed by summing all of the envelopes for each sub-band and then
removing the smallest and largest envelope values. Each sub-band is then equalized to the average
envelope. Removing the smallest and largest values will prevent any unusually sized envelope from
being included in the average and messing up the true amplitude property of the process.
Input Channels
Output Channels
Parameters
Time and space variant?
Select Yes to specify filters in a matrix that are time and space variant.
1344
Primary header key

When specifying time and space variant filters select a primary trace header key corresponding to the
primary key in the application time matrix.
TLSN

When specifying time and space variant filters select a secondary trace header key corresponding to the
secondary key in the application time matrix.
TLSN
Custom filter specification?

Select Yes to specify each of the narrow band-pass filters and a reference mean to be applied to each band.
Select No to automatically calculate the band-pass filters and set a reference mean of 2500 to each band.
T.V. Filters
When specifying time and space variant filters and not custom filters, use this matrix to define the time
variant filters to be used.
Matrix Type: TVTVZD
Application times
When specifying time and space variant filters, use this matrix to define the application window for each
of the filters defined in the T.V. Filters matrix or the Custom filters matrix.
Custom filters
When specifying time and space variant custom filters, use this matrix to define specify each of the narrow
band-pass filters and a reference mean to be applied to each band.
Matrix Type: TVTVZDC
1345
Custom information
When specifying time and space variant custom filters, use this matrix to define the adaptation window
size and the start/end trace header words to be added to the application window time.
Matrix Type: TVTVZDD
Adaptation length(ms.)
This is the window length used to extract the envelope. This parameter will only be displayed when not
performing time variant filtering.
Filter option
A linear filter means that the bandwidth of each sub-band is the same. For the geometric filter, each
sub-band is expanded as the frequency increases. Thus the bandwidths for the low frequency sub-bands is
less than for the higher frequency sub-bands. This better focuses on narrow band residual ground roll,
which is typically low frequency. This parameter is required if you are not using a custom filter design.
Options: Linear, Geometric
Start frequency(hz.)
For the linear filter option, this is the 100% starting frequency point. A cosine squared taper is applied
before this point. For the geometric filter option, this is the 50% point on the low side of the first
frequency sub-band taper. This parameter is required if you are not using a custom filter design.
End frequency(hz.)
For the linear filter option, this is the 100% ending frequency point. A cosine squared taper is applied after
this point. For the geometric filter option, this is the 50% point on the high side of the last frequency
sub-band. This parameter is required if you are not using a custom filter design.
Number of filters
The trace will be partitioned into this many sub-bands. This parameter is required if you are not using a
custom filter design.
Bandwidth ratio of the highest to lowest filter

This parameter is required for the geometric filter option. This parameter is required if you are not using a
custom filter design.
1346
Custom filters
This parameter is required if a custom filter design is selected.
Matrix Type: TVZD
Minimum operator lag percentage

TVZD compute filters in the frequency domain, transforms to the time domain, and truncates the
operators. The truncation is determined by scanning the time domain operator and finding the last filter lag
that is minimum percentage of the zero lag value. Decreasing this parameter will result in increased
accuracy but increased execution times.
Use average envelope method?

This option determines the equalization method. Select Yes to use the average envelope method. Select No
to use the AGC method.
Restore amplitude?
Select Yes to force the output envelope to be equal to the input envelope when the equalization method. Is
the AGC method.
1347
UKOOA
Module Description
Input Channels
Parameters
Module Description
UKOOA can read a UKOOA formatted tape or disk file to the geometry database. Presently UKOOA
supports 3-D offshore survey format in the P1/84 and P1/90 formats. SeisUP will support the other survey
types in the P1/84 and P1/90 formats in the future.
This module will remove blanks from any line names extracted from from the UKOOA file.
Many recent UK00A data sets contain information about water depths at the source location on the "S"
card and receiver depths on the "R" cards. These may be extracted and written to matrices for inclusion in
trace headers. The matrices used at present are SOURCEM and PATTERNM. Processing and application
of the data in these matrices is accomplished using modules MSTATION, MSOURCE and MGEOM.
Input Channels
1. UKOOA file: Required ASCII data type.
Parameters
3-D restart?
Choose "Yes" if you are adding more navigation information to the database.
UKOOA version
Options: Pre-1984, P1/84, P1/90
PATTERN matrix type

If you select "Distance from shot", the output format will be in the internal format. If you select "Receiver
location", UKOOA will output a source matrix type of SRCXYREC. Receiver locations will be ignored.
Options: Distance from shot, Receiver location
1348
Get marine depths?

Required if PATTERN matrix type = Distance from shot and UKOOA version = P1/90. This parameter
controls whether source water depths and receiver depths are extracted from the UK00A input data.
Options: Yes, No
Number of traces per data record

Number header records at beginning
C.C. for start of line name.
C.C. for end of line name.
C.C. for start of X coordinate.
C.C. for end of X coordinate.
C.C. for start of Y coordinate.
C.C. for end of Y coordinate.
C.C. for start of shot point #.
C.C. for end of shot point #.
C.C. for start of channel #.
C.C. for end of channel #.
C.C. for start of shot id code.
C.C. for end of shot id code.
C.C. for shot adder code.
First shot point
This is the minimum shot point for each shot line input.
1349
Last shot point

This is the maximum shot point for each shot line input.
Renumber the channel number?

Save line name in db
When using the LINE header index in the SeisUP trace header, the size of the name is limited to eight
characters. To save the line name in the database as an eight character name, select First 8 Char. to
truncate the line name after eight characters. Select Last 8 char. to use only the last eight characters in the
line name. The default will save the line name in the database with the name of line as read from the
UKOOA file.
Options: As is, First 8 Char., Last 8 Char.
Number of bad cards allowed to skip over.

If the program finds more than Number of bad cards allowed to skip over. card images it does not
recognize it will abort. Bad card images can arise from I/O errors or nonstandard UKOOA files. I/O errors
generally produce corrupt or out of sync data bases. Nonstandard UKOOA files generally contain
comments that describe the data which may be useful. The program can not determine which is which, it is
up to the user to determine if the output can be used.
Lines to extract
Select all to extract all lines from the UKOOA data set. Select include to specify the lines to extract from
the UKOOA data set. Select exclude to specify the lines not to be extracted from the UKOOA data set.
This is accessed only if the area is a 3-D area.

Enter the matrix name containing a list of lines to include or exclude.
Matrix Type: LINES
1350
UNDUPE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Use UNDUPE to create unique ids or drop duplicated ids. UNDUPE can check for duplicate primary
ids or duplicate secondary ids within a primary id.
Examples:
1) To remove duplicate OIDNs:
Create unique:
Primary header key
Determine primary id boundary by:
Action for duplicate ids:
Primary id
OIDN
FCSN
Change in primary id
Drop trace
To correctly handle sequential OIDNs with the same id, make the primary id boundary parameter
"Decrease in secondary id" so that when the FCSN number decreases a new primary id will be assumed.
2) To renumber duplicate OIDNs:
Create unique:
Primary header key
Number to add to duplicate ids:
Primary id
OIDN
FCSN
Renumber
100
The number to add to duplicate ids should be greater than the maximum input OIDN. If a data set
contains OIDNs 1 to 16, 1 to 99, and 4 to 50, then UNDUPE will renumber the OIDNs to 1 to 16, 101 to
199, and 204 to 250.
3) To remove duplicate FCSNs:
Create unique:
Primary header key
Primary id
OIDN
FCSN
Drop trace
4) To renumber RSLNs based on OIDN and RSBN:
1351
Create unique:
Primary header key
Tertiary header key
Number to add to duplicate ids:
Tertiary id within secondary id

OIDN
RSBN
RSLN
Decrease in secondary id
Renumber
1
RSLN will be renumbered from 1 and increment by 1 each time RSBN decreases. RSLN will start over at
1 whenever OIDN changes.
TYPE
Queue
INPUT CHANNELS
1. input
Required
GCI data type
OUTPUT CHANNELS
1. next process
Required
GCI data type
PARAMETERS
Create unique:
Default .....:Secondary id within primary id.
Name ........:itype
Options .....:
Primary id
Secondary id within primary id
Tertiary id within secondary id
1352
Primary header key

Default .....:OIDN
Name ........:pkey
Options .....:
none
CDPN
DIST
FCSN
FSPN
MBIN
MLIN
MSBN
MSLN
OIDN
RSBN
RSLN
SDPN
SGEN
SBIN
SLIN
SSBN
SSLN
SSPN
TIM1
TIM2
TLSN
other
Primary header GCI index

Code if previous header key is "other".
Default .....:
Name ........:ipkey
Min .........:
Max .........:
1353

Default .....:FCSN
Name ........:key
Options .....:
none
CDPN
DIST
FCSN
FSPN
MBIN
MLIN
MSBN
MSLN
OIDN
RSBN
RSLN
SDPN
SGEN
SBIN
SLIN
SSBN
SSLN
SSPN
TIM1
TIM2
TLSN
other
Secondary header GCI index

Default .....:
Name ........:ikey
Min .........:
Max .........:
1354
Tertiary header key

The tertiary header is reset whenever the primary header changes.
Default .....:none
Name ........:tkey
Options .....:
none
CDPN
DIST
FCSN
FSPN
MBIN
MLIN
MSBN
MSLN
OIDN
RSBN
RSLN
SDPN
SGEN
SBIN
SLIN
SSBN
SSLN
SSPN
TIM1
TIM2
TLSN
other
Tertiary header GCI index

Default .....:
Name ........:itey
Min .........:
Max .........:
1355

Default .....:Change in primary id
Name ........:iopt
Options .....:
Decrease in secondary id
Step in secondary id

NOTE: If Tertiary header key is not none, this is set to Renumber.
Default .....:Drop trace
Name ........:iact
Options .....:
Drop trace
Renumber
Number to add to duplicate ids

This parameter is displayed only if renumbering the ids. Whenever a duplicate id is found, the id will
incremented by this amount to create a new unique id. All subsequent ids will add this amount to the id.
This number should be higher than any ids on the input data.
Default .....:100
Name ........:iadd
Min .........:
Max .........:
Step size
This parameter is displayed only if Determine primary id boundary by: is Step in secondary id and
Create unique: is Primary id.
Default .....:50
Name ........:step
Min .........:1
Max .........:
1356
Auxiliary primary header key

This parameter is displayed only if Determine primary id boundary by: is Step in secondary id and
Create unique: is Primary id.
Default .....:none
Name ........:aux
Options .....:
none
CDPN
DIST
FCSN
FSPN
MBIN
MLIN
MSBN
MSLN
OIDN
RSBN
RSLN
SDPN
SGEN
SBIN
SLIN
SSBN
SSLN
SSPN
TIM1
TIM2
TLSN
other
Auxiliary primary key index

Default .....:
Name ........:iaux
Min .........:
Max .........:
1357
Use new tertiary header logic

The old logic ignored the contents of the tertiary header. The new logic uses the contents.
Default .....:NO
Name ........:itert
Options .....:
YES
N
Renumber cyclic OIDNs?

Required if Action for duplicate ids: equals Renumber.
Default .....:NO
Name ........:itert
Options .....:
YES
NO
Renumber the duplicate ids only?

Required if Action for duplicate ids: equals Renumber.
Default .....:NO
Name ........:itert
Options .....:
YES
NO
AUTHOR
Created on March 4, 1993 by Bill
1358
UNSCALE
Module Description
Input Channels
Output Channels
Parameters
Module Description
Input Channels
2. Data for scale determination: Required GCI data type.
Output Channels
Parameters
Apply inverse scaling?
Scale type
Options: Absolute value mean, Root-mean-square, Constant scaling
Windows
Matrix Type: SCLWIN
Scalars
Matrix Type: SCLSCL
Pre-suppression level in percent
1359

Primary header key

TLSN

TLSN
Space-variant time adders

1360
VA3C
Module Description
Input Channels
Output Channels
Parameters
Module Description
VA3C performs 3-component velocity analysis. Using the prescribed velocity in-line dip and cross-line
dip, it computes the semblance panel after correcting for the normal moveout, dip moveout and bin center
displacement. The output will be read in by GEOVEL3C. The user can pick the velocities on
GEOVEL3C. The dip and velocity information is automatically output to the specified matrix for later use
by NMO3D and other programs.
Input Channels
Output Channels
1. Geovel dataset: Required connection to dataset GVL data type.
Parameters
Output gather?
Coherency type
In-line dips
Matrix Type: VA3CDIP
Cross-line dips
Matrix Type: VA3CDIP
1361


TLSN

TLSN
Mutes
Velocities
Analysis locations

AGC Reference mean
Apply mute
1362
VCOR
Module Description
Input Channels
Output Channels
Parameters
Module Description
Vibroseis correlation is done on a per record basis, each record having exactly one sweep trace. If no
sweep trace is found in the record, either the previous sweep trace will be used or the program will abort.
The program will abort if no sweep trace is found on the first record. The sweep trace will be discarded
after correlation.
Input Channels
Output Channels
Parameters
Sweep trace header word
TLSN, other
Sweep trace header index

Sweep trace header value
Sweep trace length(ms)
1363
Output trace length(ms)

Action if no sweep trace in the record
Options: Abort, Use previous sweep trace
Convert data to minimum phase?

This option will compute the minimum phase equivalent of the Klauder wavelet within Vibroseis data.
The Klauder wavelet is the autocorrelation of the sweep. Convolution of the zero-phase Klauder wavelet
with the minimum-phase seismic wavelet yields a mixed phase wavelet, so deconvolution programs that
are based upon the minimum phase assumption will have a greater least square error. By converting the
Klauder wavelet to minimum phase, convolution of the Klauder wavelet with the seismic wavelet yields a
minimum phase wavelet.
1364
VELCONV
Module Description
Input Channels
Output Channels
Parameters
Module Description
Convert one type of VIP velocity into another. The input and output velocities can be RMS, interval, or
average velocities. Conversion between a time model and depth model is performed along vertical rays.
Input Channels
1. Input velocities: Required SEGY data type.
Output Channels
1. Output velocities: Required SEGY data type.
Parameters
Was input generated by VIP?
Select NO if importing velocities that were generated from another processing system.
Input sample rate (Time=us.)

Input the sample rate for velocities not created by VIP. If the input is a time model, the sample rate is
expressed in microseconds. For a depth model the sample rate should be in feet or meters.
Input velocity model type

Enter the input velocity model type for velocities not created by VIP.
1365
Input velocity type

Enter the input velocity type for velocities not created by VIP.
NOTE! The next four parameters are used to tell any module that uses the output file the range of traces to
expect. They must accurately reflect what is in the data. VELCONV DOES NOT USE THEM TO
RESTRICT THE NUMBER OF VELOCITY TRACES OUTPUT. If you want a subset of the velocity
field, cut it down before VELCONV.

Enter the minimum midpoint bin number for velocities not created by VIP.

Enter the maximum midpoint bin number for velocities not created by VIP.

Enter the minimum midpoint line number for velocities not created by VIP.

Enter the maximum midpoint line number for velocities not created by VIP.
Output sample rate (Time=us.)

Enter the desired output sample rate.

Enter the desired maximum time or depth to output The default is to use the same maximum as in the
input velocity data set. If converting between time and depth, this parameter must be entered.
Velocity model type to output


1366
Velocity output format:

Options: SEGY, GCI
1367
VELSMTH
Module Description
Input Channels
Output Channels
Parameters
Module Description
VELSMTH is a velocity smoothing program using a Gaussian filter. It can smooth velocity
three-dimensionally. The velocity should be read in X-bin gather or stack order.
Input Channels
Output Channels
Parameters
Smoothing in-between horizons?
Radius of lines to smooth over
Half of smoothing window in number of MLIN traces.
Radius of bins to smooth over

Half of smoothing window in number of MBIN traces.
Radius of sample points to smooth over

Half of smoothing window in number of samples.
1368
Smoothing degree(the smaller, the smoother)

Small number usually between 0 and 2.
Smoothing parameters in-between horizons

Required if Smoothing in-between horizons? = Yes.
Matrix Type: SMOOTHHORZ
Smoothing parameters for horizons

Required if Smoothing in-between horizons? = Yes.
Matrix Type: SURFSMOOTH
1369
VEXTRACT
Module Description
Input Channels
Output Channels
Parameters
Module Description
VEXTRACT is a queue based module that can be used to convert input data to a matrix. For instance one
may read VIP or other velocity type data sets, use SELECT to specify a grid, and finally this module to
create the matrix. This module will automatically decimate the input data to meet the maximum size
requirement for the matrix file. Currently this maximum size is set at 100 samples. No velocity type
conversion is performed. If velocity type conversion is desired see module VELCONV.
Input Channels
Output Channels
Parameters
RMS velocity matrix
Enter a desired output RMS matrix name.
Matrix Type: RMSVEL
1370
VIBMIN
Module Description
Input Channels
Parameters
Module Description
VIBMIN will compute the minimum phase equivalent of the Klauder wavelet. The Klauder wavelet is the
autocorrelation of the Vibroseis sweep. The Vibroseis method injects the full sweep into the earth as
signal. The first step in processing Vibroseis data is the cross correlation of the sweep with the recorded
data traces. This step is often performed in the field as the data are recorded. The operation collapses the
returning sweep signals to their auto-correlations or Klauder wavelets. The Klauder wavelet is zero phase
since it is an auto-correlation function. All earth filtering, instrument and geophone responses are
generally assumed to by minimum phase in nature. The convolutional model for the recorded seismogram
defines the recorded wavelet as the convolution of the injected signal with all the distortion operators
mentioned above. Convolution of the zero phase Klauder and minimum phase distortions leaves a mixed
phase wavelet on the recorded seismogram.
Many deconvolution routines, including the Weiner-Levinson algorithm used in spike deconvolution,
assumes the seismic wavelet to be minimum phase. The mixed phase wavelet left on the seismogram by
Vibroseis correlation can be converted to minimum phase by the addition of the minimum phase function
appropriate for the amplitude spectrum of the Klauder wavelet. This is accomplished by using the
minimum phase Klauder equivalent wavelet output by VIBMIN. Converting the Klauder wavelet to
minimum phase, will help ensure a zero phase result from spike deconvolution.
To apply the phase to the full data set, use module CONV. Code to apply PHASE ONLY.
The Klauder wavelet may be defined to VIBMIN by the input of a sweep, a Klauder wavelet or sweep
parameters. If the vibroseis data is un-correlated, there will usually be a sweep recorded in an auxiliary
channel. If it is field correlated, there will likely be a Klauder wavelet in an auxiliary channel. If there is
not a sweep or Klauder wavelet, the sweep parameters are recorded on the observer logs.
Input Channels
1. Input: Optional GCI data type.
Output Channels
1. Output: Optional GCI data type.
1371
Parameters
Sample rate when operator applied (us.)
Output CONV matrix name
Derive sweep from

Options: Calculation, Sweep, Klauder
Sweep length (ms.)

Sweep start frequency (hz.)
Sweep end frequency (hz.)
Sweep taper length (ms.)
Klauder center time (ms.)
Trace header to key on
TLSN, other
Trace header GCI index

Trace header value to identify sweep/Klauder
Output sweep
This is the sweep computed by the module.
1372
VIEWER3D
Module Description
Input Channels
Parameters
Module Description
VIEWER3D can be used to interactively display three-dimensional seismic data by using volume
rendering technology. It allows you to add/manipulate an ortho slice or an oblique slice. It can display
multiple "ortho" (axis-aligned) slices through the data volume with animation capability. It also allows
you to select what volume needs to be loaded and how (memory management), what color map to use with
this volume, what color map to use with slices, and the type of background to use for the main window. In
addition, it provides a way to control a region of interest (sub-volume).
Main Window
In this window you can see the seismic data volume, the current color map and the histogram of the
current data set.
You can use the mouse to rotate, pan, and zoom the volume.
Control Parameter Interface
This window provides an interface to perform different operations on the current visualized data set.
Input Channels
1. Input GCI data set: Required connection from dataset GCI data type.
Parameters
NONE
1373
VIMPEXP
Module Description
Input Channels
Parameters
Module Description
VIMPEXP will import or export velocity functions from or to ASCII files. The currently supported
velocity files will output the midpoint bin (MBIN), midpoint line (MLIN), X coordinate and the Y
coordinate for each function. With the 2-D Charisma format the line name and shotpoint are output. Each
function will also have all of the time/velocity pairs specified. A description of the SeisUP format will be
included in the ASCII file. Below is an example SeisUP velocity file:
H***********************************************
H*
SeisUP(R) Velocity export file
*
H***********************************************
H
H SURVEY NAME:
Some Survey Name
H SURVEY AREA:
Some Survey Area
H CLIENT:
Some Client
H PROCESSING CONTRACTOR: Some Company
H COMMENT:
Sample comment
H CREATED:
Fri Jul 28 17:13:56 2000
H
H
D card:
H
MLIN:
Crossline midpoint number
H
MBIN:
Inline midpoint number
H
X:
X coordinate
H
Y:
Y Coordinate
H
H
V card:
H
TIME:
Time corresponding to VELO(Ms)
H
VELO:
Velocity corresponding to TIME
H
D
21
21 751716.8 986512.5
V
0
9571
V
7
9571
V
536
10464
V
933
13071
V
1135
14535
V
1353
14749
V
2041
16607
V
2570
17249
V
3072
17641
D
21
41 751737.6 984312.6
V
0
9571
V
7
9571
V
326
10214
V
699
12714
1374
V
V
V
V
1049
1341
2558
3072
14071
14321
16035
16331
Input Channels
1. Velocity file: Optional connection from dataset ASCII data type.
Parameters
Operation to be performed
Options: Import, Export
Velocity file format

Options: SeisUP, Landmark, Charisma (2D), Focus, Western Geophysical
VELF, ProMAX (2D)
Matrix type
Matrix Type: RMSVEL
Matrix for 4THNMO velocities

Matrix Type: 4THNMO
Add to existing velocity matrix?

Select Yes to add any imported velocity functions to an existing matrix. This can be used for example
when merging multiple surveys together. Select No to first delete any existing matrix and then add any
imported velocity functions to a new matrix.
Output file name

Enter the file name to store the exported velocity functions. If an absolute path is not entered, the file will
be placed relative to your home directory.
1375
Import using
Select Coordinates to compute the midpoint bin numbers from the coordinates specified in the input
velocity function. Select Midpoint # to use the midpoint bin numbers specified in the input velocity
function.
Options: Coordinates, Midpoint #
Scalar to mul. CMP No. to get S.P.

Enter the scalar to derive the shotpoint in the equation sp=CMP*scalar+constant.
Scalar = Sign (1 / number of CMPs per shot point)
The sign of the scalar will be positive if the shot points are ascending and negative if descending
Required if velocity format is Charisma (2D).
Constant additive to get S.P.

Enter the constant to derive the shotpoint in the equation sp=CMP*scalar+constant.
Required if velocity format is Charisma (2D).
Line name
Enter the line name to be placed in the exported Charisma (2D) velocity file.
Survey name
Survey area
Client
Processing contractor
Comment
1376
VIP
Module Description
Input Channels
Output Channels
Parameters
Module Description
VIP is a velocity interpolation program for input of velocity matrices and output of velocity information
for every CMP or "bin" so specified. Interpolation between input points is linear for 2-D and tri-linear for
3-D using. The output data is 25:1 of the input data, i.e. coding 4 ms produces 100 ms interval information
on output unless the compression ratio is changed. The output velocity type may be Average, RMS or
Interval. An option is to input and smooth a 4 th order correction matrix.
If interpreted horizons are available, the user may optionally use Dix interpolation. Dix interpolation is
computed as follows:
1. Interpolate the RMS velocity at the horizons. Average velocity will be interpolated if average
velocity is being output.
2. Compute the interval velocity between the horizons.
3. Force the velocity between the horizons to be the computed interval velocity.
4. If desired, convert the interval velocity to RMS or average.
Dix interpolation is performed after the RMS velocity cube is interpolated and smoothed.
An option was added to smooth a 4 th order NMO correction matrix. This type matrix can be created in
NMOA and NMOR. The VIPINV module will allow you to output the VIP file as a matrix.
A new option is added to create GCI format velocity file for QC purpose. In Addition, headers MCX and
MCY are set in SEGY or GCI format output. Also, more smoothing options such as time-varying and
vertical smoothing are added.
Input Channels
Output Channels
1. Output file: Required connection to dataset SEGY data type (default) or GCI data type.
1377
Parameters
Input matrix type
Required if Input matrix type = RMS.
Input interval velocities

Required if Input matrix type = Interval.
Input average velocities

Required if Input matrix type = Average.
Input 4th order NMO corrections

Required if Input matrix type = 4 th order NMO.
Show parameters for

Smooth velocities?
Time variant smoothing?
Required if Smooth velocities? = Yes.
Number of bins to smooth over

Required if Time variant smoothing? = No.
Number of lines to smooth over

Required if Time variant smoothing? = No and Show parameters for: = 3-D survey.
Time variant smooth parameters

Required if Time variant smoothing? = Yes.
1378
Vertical smoothing?
Required if Smooth velocities? = Yes.
Number of samples to smooth over

Required if Vertical smoothing? = Yes.
Expected sample rate of the data (ms.)

Output compression ratio (#:1)
The default is to output 25 velocity samples per expected sample rate. Modules that use a VIP velocity
cube will interpolate the velocities to the sample rate needed. If the velocity model is fairly smooth in the
time or depth direction, this is adequate. The advantage is a smaller memory footprint for the modules
needing VIP velocities. If a high degree of accuracy is needed, a smaller compression can be specified.
The user can also specify a compression ration of 1:1, read the VIP velocity cube with SEGYREAD, and
attach the post-stack data to the DISPLAY or PLOT module to create a velocity section overlaid with the
seismic data.
Velocity model type to compute

Use Dix interpolation between interpreted horizons?
See above for a description of Dix interpolation.
Horizons matrix (Deprecated)

This parameter is deprecated. Select a matrix name only to convert it to the new format

Print velocity function info.?
1379


1380
VIPINV
Module Description
Input Channels
Parameters
Module Description
VIPINV extracts, from a VIP file, the RMS velocity functions at user-specified locations. The user uses
the same type of matrix as in CVA3D to prescribe the the velocity locations. If the location is defined as a
range, instead of a single bin and line value, the center is computed and used as the output location. A new
option is to output a 4 th order NMO correction matrix.
VIPINV automatically checks for the input velocity type in the VIP file and converts it to RMS if
necessary.
A new option was added to output a 4 th order NMO correction matrix. This type matrix can be created in
NMOA and NMOR. Use the VIP module to input the original 4THNMO matrix and smooth it.
A new input channel was added to accept GCI format VIP velocity or 4 th order NMO. In this option, there
is NO velocity type checking so a same type GCI input should be used according to output matrix type.
Input Channels
1. Input vip file: Optional connection from dataset SEGY data type.
2. Input vip file: Optional connection from dataset GCI data type.
Parameters
Output matrix type

Options: RMS, 4th Order NMO
RMS velocity matrix

Required if Output matrix type equal RMS.
1381
Matrix Type: RMSVEL
4 th order NMO correction matrix:

Required if Output matrix type equal 4th Order NMO.
Matrix Type: RMSVEL
1382
VIPMATH
Module Description
Input Channels
Output Channels
Parameters
Module Description
VIPMATH does mathematical operations on two VIP files. Input 1 is the operand. Input 2 is the operator.
Input Channels
1. Input vip file 1: Required connection from dataset SEGY data type.
2. Input vip file 2: Required connection from dataset SEGY data type.
Output Channels
1. Output vip file: Required connection to dataset SEGY data type.
Parameters
Operation
Options: Division, Subtraction
Scale to be applied to quotient

Options: SEGY, GCI
1383
VORMED
Module Description
Input Channels
Output Channels
Parameters
Module Description
The stand alone program VORONOI creates scalars with areas of Voronoi polygons in the survey.
These polygons tend to be large for border traces, so that it is recommended to scale, clip or filter them.
This program gives that options and offer some statistics on those areas.
The output file from this module is used by the program VOLSCL to scale the traces accordingly with
the areas of the Voronoi polygons.
Input Channels
1. Input: Required connection from dataset BIN data type. Data file with input areas.
Output Channels
1. Output: Optional connection to dataset BIN data type. Data file with processed areas.
Parameters
Run median filter to despike areas?
Sometimes outliers come specially in border traces. A median filter is a good option to use.
Window length for median filter

The default is 3, small number is recommended. A big filter length will try to smooth data out.
Do you want to clip areas?

Description forthcoming.
1384
Enter threshold minimum value

To avoid areas too large that will cause migration smiles.
Enter threshold maximum value

To increase amplitude in zones where large density of traces are. Since there are more traces in that zone,
data is in a way more
reliable so scaling data out sometimes is not recommended.
Do you want to scale the areas?

To keep amplitudes (globally) within reasonable values. For example when the units are feet the bin size
(in area) could
be more than 10000 sqf. Those scales will amplify the amplitudes. Very big numbers are not
recommended because they
can limit the arithmetic precision on processes. It is recommended to have amplitudes close to one and
within a few orders
of magnitude around it.
Pick normalization value

The default is Median because it is the "most common" number. However the options of mean, max and
fixed number can be used.
Care should be taken with these parameters. For example the mean is sensitive to outliers. The maximum
can take small values too
close to zero. A fixed number sometimes is recommended because the user can control the amplitude
range easily.
Options: Median, Mean, Max, Fixed number
Enter value
This option only works if a fixed number is chosen. Here the user should enter that scalar.
1385
VORONOI
Module Description
Input Channels
Output Channels
Parameters
Module Description
This stand alone module compute a Voronoi tessellation for the set of midpoint coordinates of traces in
data sorted by offset bins (DMODIST). Then finds the area of each Voronoi polygon around each input
trace and save this area in a file for later use BIN. This file is just an array of floats with an area per each
trace. The file should be read by the module VORSCL to scale traces according to the areas of the
surrounding Voronoi polygon before Kirchhoff migration is applied.
Input Channels
Output Channels
1. Output: Required connection to data set of BIN type.
2. Output: Optional matrix of STATION format.
Parameters
Check sorting keys?
The data are assumed to be sorted in DMODIST. Saying "yes" to this parameter implies that if data are not
sorted in DMODIST the program will abort. Saying no will force the program to run, whether or not the
data is sorted in DMODIST.
Select input sorting

Options: Common Offset, Common Shot
1386
Joggled Input?
When some midpoint locations are very close to each other, the computation might be unstable, since the
polygons are almost degenerated (with at least one side of length zero). Saying "yes" to this parameter
makes the program to introduce a random "noise" that will separate the midpoints by an small amount and
would make the process more stable.
Pick treatment to border traces

Another cause of instability comes from the borders. Usually the border polygons have an area which is
much larger than the average polygon. This would have the effect of amplify the amplitude for the border
traces. The user can overwrite this amplitude by picking the area of a "good" (inside) neighbor, or assign
them a fixed number (for example the assignation of zero would knock them out, this could serve as a way
to taper the edges), assign them the median found on each offset or the mean found on each offset. If the
option "Fixed number" is input then a request to input the fixed number will pop up. Internal polygons that
are degenerated will be assigned this area as well.
Options: Good neighbor, Fixed number, Median, Mean
Enter value
Provide the value that will be inserted as area of any border polygon or inside polygons that are
degenerated.
Do you want to clip areas?

Here the user has the option to limit the spread of areas so that there is not much variation between the
scalars that will be applied. An extreme of limiting the maximum and minimum to one number will leave
the data with exactly the same relative amplitude. Sometimes very large or small amplitudes correspond to
numerical artifacts and do not match the physical reality. Here the user has a tool to improve the span of
areas after judging if the found areas do make sense.
Enter threshold minimum value

Minimum area allowed on output file.
Enter threshold maximum value

Maximum area allowed on output file.
Do you want to scale the areas?

Sometimes areas are big numbers and introduce large amplification to the traces before migration. Having
traces with small (but not too small) amplitudes is good because more accuracy can be retained when
using floating or double point arithmetic. An scale value that bring the areas to a "small" (by small I mean
something close to the absolute 1) can be obtained after normalization. The options for this normalization
1387
are the median for the first offset, the mean for the first offset, the maximum on the first offset or a given
fixed number. The program will only scale the data based on ONE scalar so that the relative amplitude is
preserved.
Pick normalization value

Here the options to normalize data are laid out. A fixed number can be given or pick some statistical
parameters from the first offset. If a fixed number is selected then the user should provide that number
upon request.
Options: Median, Mean, Max, Fixed number
Enter value
Enter value here if the option "Fixed number" was selected.
Do you want to QC the areas?

Enter yes if you want to generate an output matrix in STATION format.
DMODIST
Enter the DMO distance if the option "Do you want to QC the areas?" was selected.
Output matrix name

Enter the name of the output matrix if the option "Do you want to QC the areas?" was selected.
1388
VORSCL
Module Description
Input Channels
Output Channels
Parameters
Module Description
This module scale traces according to the area of the Voronoi polygons for each DMODIST gather. Those
areas are stored in a BIN dataset. This dataset is created by the stand alone module VORONOI.
Input Channels
2. Input: Data set in binary BIN format with areas. This data set is created initially with the module
VORONOI and perhaps processed with the module VORMED.
Output Channels
Parameters
Enter number of traces for verbose info
This parameter controls how often information is printed out.
Save areas in FOLD record of trace headers?

If Yes, save the areas in the FOLD header word.
1389
VSLICE
Module Description
Input Channels
Output Channels
Parameters
Module Description
VSLICE is an interactive module that is used to determine the velocity field from a velocity cube created
by the module SMIG. SMIG consists of the following four windows:
1. The top right window is the constant velocity display window. Velocities can be picked at the current
analysis location. An iso-velocity line will be overlaid on top of the section. Any existing velocity
analysis locations will identified by a red "v" at time zero.
2. The bottom right window is the zero-offset section sliced from the velocity cube.
3. The middle window is the display of adjacent CMPs from each constant velocity migration over the
current analysis location. This window will use the velocity plain increment when displaying adjacent
velocity panels. Velocities can be picked in this window.
4. The left window is the power display over the current analysis location. Velocities can also be picked
within this window. This window also contains the interval velocity displayed to the left of the power
display.
To the right of the seismic displays is the menu icon bar. The menu icons can be used instead of using the
menus from the menu bar.
The sash between the constant velocity window and the zero-offset section can be dragged with the mouse
to adjust the height of these windows.

To select an analysis location:
1. Press and hold the left mouse button in the constant velocity window.
2. Drag the mouse. You will see the velocity, CMP, and time at the mouse location displayed at the
bottom of the window. An outline of a red rectangle representing the analysis location will also be
displayed.
3. Release the mouse button at the requested analysis location.
4. Press the analysis menu icon or select "Analysis" from the file menu.
The power will then be calculated over the analysis window and displayed in the power window.
1390
Picking velocities
Velocities can be picked in the constant velocity window, the adjacent velocity window, or in the power
display. The following mouse buttons may be used to modify velocities.
Button 1

location.
Ctrl-Button 1
Same as "Button 1" but search through a window

centered at the mouse location. VSLICE will
perform a two dimensional search through the
power and compute the maximum power by using
a parabolic equation. The horizontal extent
of the search window is between the minimum
and maximum velocity in the cube. The vertical
extent of the window is determined by a
parameter titled "Autopick window (ms)".
Button 2

location.
Button 3

location.
All picks are surrounded by a red box. In the power display, the box is annotated to the left or right of the
pick. In the constant velocity display and the adjacent velocity display, the pick is displayed on the closest
constant velocity plain. The last pick will be automatically picked and drawn using the interval velocity
between the last two picks.
Three velocity curves can be drawn in the power and adjacent velocity windows as follows:
File menu
Option
Icon
Description
--------------------------------------------------------------
Increase velocity Cube-arrow up
Display the next velocity

increment plain.
Decrease velocity Cube-arrow down Display the previous

velocity increment plain.
1391
Analysis
Analysis
Make the current highlight

window in the constant
velocity window the current
analysis location and
calculate the power.
Slice
Cube-sliced
Slice the velocity cube using

the current velocity cube
over the currently displayed
CMPs.
Output
Disk-arrow down Slice any CMPs that need

updating and save to the
output data set.
Change parameters
Change various parameters
Edit color
Print ...
Printer
Print screen.
Quit
Lightning bolt
Quit VSLICE
Help menu
Option
Description
--------------------------------------------------------------
On use
On how to use VSLICE.
On menu icons
Input Channels
1. Velocity cube: Required connection from dataset SMIG data type.
1392
Output Channels
1. Output stack: Required GCI data type.
Parameters
RMS velocities
Matrix Type: RMSVEL
Number of CMPs per analysis

Velocity plain increment
Wiggle type
Bias
Traces per inch
Inches per second
Gain (db)
Clip (traces)
Timing lines?
Timing line increment
Power gain (db)
This is the amount of gain to apply to the power display
1393
Plot Direction
Start time (ms)

Ending time (ms)
Power colormap
Select cursor size?
Options: Small, Large
1394
VSUM
Module Description
Input Channels
Output Channels
Parameters
Module Description
VSUM will perform a vertical sum from input records.
The following is an example to sum adjacent field file ids:
Primary ID header key
Secondary ID header key
Replace primary & secondary ID as:
Summed GCI index
IDs to sum
Minimum summed value
Maximum summed value
Bin size within output ensemble
Number of output ensembles to hold
NONE
OIDN
First ID
FCSN
something
1
48
1
1
The contents of matrix something could be as follows:

Sec. strt| Sec. end| Delta Sec.| # Sec. grps
---------|---------|-----------|--------------------1
|2
|2
|999
The above would sum common channels from OIDNS 1-2, 3-4, 5-6,...
The following is an example to create 3-D super-gathers or common offset stacks from CMP sorted data:
Replace primary & secondary ID as:
Summed GCI index
IDs to sum
Replace summed id as:
MLIN
MBIN
Middle ID
DIST
gathers
200
2500
50
Bin center
10 (Maximum per line)
The contents of matrix "gathers" could be as follows:
1395
Pri. strt| pri. end| Delta Pri.| # Pri. grps

---------|---------|-----------|--------------------9
|11
|10
|10
Sec. strt| Sec. end| Delta Sec.| # Sec. grps

---------|---------|-----------|--------------------49
|51
|10
|10
The above would sum offsets 175-224, 225-275, ... to CMPs (49,9)-(51,11), (59,9)-(61,11), ...
(49,19)-(51,21), ...
Input Channels
Output Channels
Parameters
Select "Yes" to use the absolute value of the trace header values to determine if this trace should be
summed.

TLSN, other
Primary ID GCI index

Option "NONE" is not a valid option.
TLSN, other
1396
Secondary ID GCI index

IDs to sum
Matrix Type: VSUM
Replace primary & secondary ID as

Options: First ID, Middle ID, Last ID
Summed header key

TLSN, other
Summed GCI index

This is the center of the first bin to sum.

This is any value within the last bin to sum

Any header values falling within this bin size will be summed.
Replace summed id as
Options: Bin center, Average

Increase this number when the data to be summed is not sequentially ordered. For example, shot ordered
data and extracting CMP common offset stacks.
1397
WAVELET
Module Description
Input Channels
Output Channels
Parameters
Module Description
WAVELET extracts the wavelet from each trace within the proscribed derivation window. Shaping or
dephasing filters are designed based on the extracted wavelet and are applied to the data to convert the
input wavelet into the user-desired wave form.
WAVELET separates the wavelet from the trace by using Taners exponential decay method. A seismic
trace is comprised of the convolution of the wavelet with the reflection coefficients and random noise. The
noise and reflection coefficients can be considered as randomly distributed. Therefore, we can obtain the
wavelet from the autocorrelation of the seismic trace if the wavelet is of minimum phase. However, the
wavelet is not always of minimum phase. To overcome this limitation, we employ the exponential decay
algorithm developed by Taner (1980). It can be proved that any given causal wavelet can be converted
into a minimum- phase wavelet by applying a proper exponential decay curve to the trace. The wavelet is
extracted on the decayed trace and the exponentiation effect is removed by applying the inverse of the
decay curve.
Once the wavelet is extracted from the data, an operator can be computed to convert it into any
user-desired wave form. The wavelet can be mixed with the ones from neighboring traces to improve its
appearance and stability. The weights in the weighting can either be equal or slanted.
The filter length is recommended to be about 1.5 times the dominant wavelength. Shorter filters will cause
information loss and longer filters may include periodic reflections into the wavelet due to the fact that the
reflection coefficients can rarely perfectly meet the assumption of being random.
WAVELET always outputs the wavelet-processed traces. However, the wavelets can be optionally output
for QC purposes. Each trace in the wavelet file contains two or three discrete wavelets depending upon the
options coded. The first wavelet is the extracted wavelet from the input data. The second is the output
wavelet before any additional phase shift. If no additional shift is coded this will be the wavelet form on
the output data. A third wavelet is displayed if additional phase shift is desired. This phase-shifted wavelet
is then the wave form on the output data. Each wavelet is Filter length(ms): long and separated by Filter
length(ms):.
Reference:
Taner, M. T., and Coburn, K. W., 1980, Surface consistent estimation of Source and receiver response
functions: Presented at the 50th Annual Internation SEG Meeting, November 18, Houston
1398
Input Channels
Output Channels
1. Wavelet-processed traces: Required connection to next process GCI data type.
2. Wavelets: Optional GCI data type.
Parameters
Windows for filter derivation?
End design time(ms)
Primary header key
TLSN

TLSN
Windows
Header to add to design-start time

1399
Header to add to design-end time

Filter length(ms)
Decay rate (per sample)
Average wavelet over (# traces)
Averaging method
Options: Equal weight, Linear ramp
Starting weight of ramp

Phase of desired wavelet?
Options: Zero phase, Minimum phase
Phase to add upon the above wavelet (deg.)

Restore amplitude?
1400
WAVEMULT
Module Description
Input Channels
Output Channels
Parameters
Module Description
Wavemult performs wave equation multiple removal on pre-stack seismic data. First synthetic split
spreads are constructed from the input data by the reciprocity principle. Essentially each is duplicated with
traces shot (SSBN) and receiver (RSBN) swapped, and the offset is negated. Then if the data are not
already in shot order, the data are internally sorted into common shot coordinates, The data are then
"continued" via the wave equation from the recording surface to the water bottom, then back to the
surface. Phase shifts are used to actually perform the continuation. The continuation simulates the effect
that traveling the water column has on the seismic record, essentially adding a multiple to the record. This
multiple, and any other multiples which follow the same path are then "adaptively" subtracted from the
recorded seismic data. The algorithm roughly follows Berryhill and Kim, Geophysics 1986.
Data may be in any order for input, if the data are in shot order (SSBN), they remain in shot order,
otherwise the program outputs CMP (MBIN) sorted data. Note, if the data are input in shot order, a
slightly different synthetic split spread is constructed. In this case the trace is duplicated with the offset
negated. This is not a true synthetic split spread, but the runtime and temporary storage required for a sort
are much reduced, and for some datasets, the results can be better. In general, inputting CMP sorted data
will produce better results, however a disk file double the size of the input data is required for the duration
of the job.
Note the data should not have statics, normal moveout or aggressive deconvolution applied. This process
works best on "raw" records, where the water bottom reflections are unaltered.
This module requires valid header values for MBIN, SSBN, RSBN, and DIST. The MBIN, SSBN and
RSBN are used to sort the data and construct the synthetic split spreads. Within a spread, the data are
ordered by offset for the continuation. The offset DIST may be positive or negative, and is used to
compute the position of the trace for the continuation. In addition a water bottom must be supplied, loaded
into either header TIM1 or TIM2.
Input Channels
1401
Output Channels
Parameters
Water bottom header
The time in milliseconds of the water bottom must be loaded into the trace header, either in location tim1
or tim2. The water bottom time is typically picked from a stack, or from normal moveout corrected near
traces. These times are the most sensitive control in the process. If the water bottom has a great amount of
relief, the times may best be picked from a migration (where velocity = water velocity).
Average water velocity

Wavemult uses a constant velocity for the water, 1500 meters/sec or 5000 feet/sec are typical values.
Offset increment
The offset bin size used for continuation. Equal to the average geophone spacing.
Multiple match quality

Wavemult uses an amplitude normalized cross-correlation to determine what is a multiple and what is a
primary reflection. The multiple match quality sets the cutoff point for which events are considered
multiples. A match quality of 0.0 would consider every event to be a multiple, and 1.0 would mean only a
"perfect" match is accepted. Data not considered to be multiples (match quality is below the cutoff) are not
changed by the program. Values of 0.5 through 0.2 are suggested, but some experimentation is also
suggested to see which match quality works best for a particular data set.
Do you need more cryptic program controls?

This option adds more detailed controls to the parameter list.
Maximum multiple window size (ms)

When attempting to remove a multiple, the program looks at windows of data. These windows begin at the
predicted multiple time and can be as large as the multiple time for a give offset, but not larger. Smaller
maximum window allows more variable seismic character to be compensated for by the program. The size
is also roughly proportional to the water bottom time. Suggested values are between 100 (shallow water,
i.e. water bottom times in the hundred ms range) and 500 milliseconds (for water bottom times in the 1 or
2 second range).
1402
Offset of CrossCorrelation window (ms)

When searching for a multiple, wavemult cross correlates a window of data from the original shot against
another window of data from the continued shot. The window length is the minimum of the multiple
repeat time or the Maximum multiple window size (ms) specified above. The cross correlation windows
usually start a little before the predicted multiple arrival time, so full waveform may be used in the cross
correlation. Offset of CrossCorrelation window (ms) is the amount of data in milliseconds to to add to the
cross correlation window relative to the predicted multiple arrival time.
Maximum Shift of whole trace (ms)

Wavemult allows an overall shift between the original shot and the continued data, to compensate for
small static errors.
Maximum Shift of each window (ms)

Wavemult searches for a multiple by cross correlating the original shot and the continued data within a
window around the predicted multiple arrival time. Maximum Shift of each window (ms) is the maximum
shift (in milliseconds) between the original shot window and the continued data window.
Volume of printout info

An option for testing, causes the program to print out lots of info regarding quality of cross correlations,
window start & stop times, etc. Verbose = 2 is VERY verbose, and is only suggested on a couple shots at
most.
Output continued data only?

For testing. One way to test the accuracy of the water bottom time picks is to compare the continued shots
against the original data. If the picks are accurate, the water bottom multiples on both data sets will line
up. If they do not roughly line up, wavemult cannot identify a particular event as a multiple. This option
short circuits the multiple removal and puts the continued shots back into the flow, so they may be saved
or displayed.
1403
WRITE
Module Description
Input Channels
Output Channels
Parameters
Module Description
WRITE will output a SeisUP internal formatted data set to tape or disk. A new feature allows you to
append more data to an existing dataset.
Disk data sets

For disk data sets, a compressed map file is written along with the seismic data so that the module READ
can read in one of many sort orders. Data sets can span multiple disk volumes. If this module runs out of
disk space the following message will be displayed in the job monitor:
Not enough disk space available, reply (c/a)
Respond with "c" to continue after freeing some disk space. Respond with "a" to abort.
A new feature in the WRITE module is the ability to append new data to an existing dataset. A new menu
item has been added to the module for the append option. The append feature will be useful in field
operations, where all the data is not available at once but collected on a daily basis. Seismic data that is
collected each day can be appended to the existing dataset for the survey. Other uses will be when a job
aborts or a tape input job must be aborted or canceled for some reason. You can now add tape or disk
inputted data on separate job runs into one larger dataset.
Be aware that the append option will not work when the output is tape. The appended data is always added
onto the end of the existing disk file. Please be sure that an incomplete ensemble is not sitting on the
boundary of an appended dataset. If you are trying to append data to a job that previously aborted, there
might be an incomplete ensemble that was written to the dataset. So now, when you try to append data at
the aborted ensemble, you will have extra data sitting at the boundary. It might be a good idea to view the
end of an existing dataset to check for unwanted data before attempting to append new data.
Tape data sets

For tape data sets without reel numbers specified through the flow editor, tapes are allocated through the
seismic data inventory (SDI) database. The WRITE routine will request for a particular type of tape to
mount. The operator/user can get a list of available tapes through the SDI program (sdinv) and mount one
of those tapes. The WRITE routine will then read the reel number from the tape and verify that the tape is
available for allocation. The WRITE routine will not write to tapes where the reel number cannot be read
or if the tape is not a scratch tape. Tapes can be initialized with a tape number with the program "tapeinit".
The tapeinit program can be invoked as follows:
1404
tapeinit reel drive

where:
reel = The reel number.
drive = The drive number the tape is mounted on.
For tape data sets with reel numbers specified through the flow editor, the WRITE routine will attempt to
read the reel number from the tape and verify that the correct reel is mounted. If the reel header cannot be
read or if the wrong reel is mounted, the WRITE routine will request the operator/user if the program
should continue to write over the tape or mount another tape. If the WRITE routine runs out of tapes given
by the user, the WRITE routine will request the operator/user for an additional reel number.
Input Channels
Output Channels
1. Dataset: Required GCI data type.
Parameters
Append to current dataset (disk only)
Select YES to append additional data onto an old dataset. Choose NO to start writing data at the
beginning of the file. This option allows you to keep adding data to the end of an existing dataset. This
option works on disk files only, not tapes. Also required is a valid map file that is normally written along
with the dataset. It is up to the user to decide if the data being append is of the appropriate type. Typical
uses for this option will be: Adding data to an existing dataset due to an aborted or canceled job, In the
field when data is being collected daily.
Limit files to 2GB?

SeisUP can support multiple files per data set. To limit the size of each file within a data set to 2
Gigabytes then select Yes. This may be used when it is desired to exchange the data set between systems
that do not support files greater than 2GB. Select No to write the maximum file size supported by the
operating system and file system.
1405
Use Default keys?

Select YES to use the default map keys. The defaults are mbin, mlin, sbin, slin, rsbn, rsln, dist, and
dmodist. Selecting NO will bring up 8 more parameters that allows the user to customize which map keys
are used for sorting. This will reduce the time it takes to read and sort if the user needs to sort according to
map keys that are not the defaults.
NOTE: Writing out using non default keys would result in writing a version 5 dataset. Versions of SeisUP
prior to 2007 are only capable of reading up to version 4 datasets. If needed, a version 4 dataset can be
made by writing out the dataset using the default map keys.
Set mapkey[0] to:

Displayed if Use Default keys? = No.
Enter mapkey number (1-87):

Displayed if Set mapkey[0] to: = Other.
Set mapkey[1] to:


Set mapkey[2] to:


Set mapkey[3] to:


1406
Set mapkey[4] to:


Set mapkey[5] to:


Set mapkey[6] to:


Set mapkey[7] to:


1407
WTNRC
Module Description
Input Channels
Output Channels
Parameters
Module Description
Wavelet transform noise rejection - cluster edition. This module uses real, symmetrical Morlet wavelets to
perform a spectral analysis for every sample under a velocity guided line. User selected parts of the
spectrum are set to zero (spectral filtering) before an inverse transform is done. The user specified filter
parameters can linearly vary from top to bottom of the trace. This process runs on a single trace by trace
basis. See "Ground-roll suppression using the wavelet transform, 1997 Geophysics, vol 62, no 6., pp
1896-1903"
Input Channels
Output Channels
Parameters
Start analysis frequency (Hz)
Start frequency of the data, typically 5 Hz or more.
End analysis frequency (Hz)

End frequency of interest. For 4ms sampling this should be at least 100Hz but less than 125Hz. For 2ms
data this should be at least 200Hz but less than 250Hz.
Number of analysis frequencies

This number will define the frequency sampling rate of the spectral analysis. A "rule of thumb" can be
(Frequency range) / 3.
1408
Maximum number of samples per wavelet (odd)

This value needs to be large enough to accurately represent the lowest frequency of interest. Usually 251
will be OK. Since we are using real symmetrical wavelets this number MUST be odd.
Top of trace start filter frequency (Hz)

Beginning frequency of desire filter at TOP of trace.
Top of trace end filter frequency (Hz)

End frequency of desired filter at TOP of trace.
Bottom of trace start filter frequency (Hz)

Beginning frequency of desired filter at BOTTOM of trace.
Bottom of trace end filter frequency (Hz)

End frequency of desired filter at BOTTOM of trace.
Velocity of surface noise

Chose this velocity for the line to be about 50ms or so above the noise on the near traces. This gives the
filter a time zone for taper-on.
Number of threads per node

Each cluster node has at least one CPU and usually more. This value should equal that number of CPUs.

How many nodes do you want to use on the cluster? This number should match the number of nodes
specified in the node list (see below)

Enter the same number as number of threads.
Compute node list

Select a node list.
1409

Build a node list.
1410
XAVA
Module Description
Input Channels
Output Channels
Parameters
Module Description
XAVA extracts angle of incidence CMP gathers, angle-range limited CMP gathers or incidence angle
value CMP gathers from the input common midpoint gathers (CMP) or common bin gathers. The angle of
incidence CMP gathers can be used for analysis of AVO properties or as input to the AVO Attributes
Stack (AVOA) module.
Angle limited CMP gathers are the input CMP gathers muted outside a specified range of incidence
angles. The user enters a minimum and maximum incidence angle and the module will output the same
CMP gather with all data outside the angle range muted.
Incidence angle value CMP gathers are the input CMP gathers but the value output is the computed
incidence angle. The following is an example output from this display where the background color
represents the incidence angle value and the wiggle trace represents the input CMP gather:
1411
Angle of incidence gathers produce a new CMP gather with values mapped into time and angle of
incidence space. The user prescribes the range of the first angle group, the increment of the group center
and the number of groups. XAVA will stack the data within each group range and place the average
incident angle (degrees) into the header where offset (DIST) is located and put the average fold (FOLD)
into the fold header. Since the iso-incident-angle contour runs across the traces, the fold varies with time
for each output trace. An average is computed by taking the algorithmic mean of the fold at all the
non-zero samples.
1412
This is an example of how the data is partitioned into group ranges. In this example, Minimum of first
angle group(deg.): = 5, Maximum of first angle group(deg.): = 15, Increment between angle groups(deg.):
= 10 and Number of angle groups: = 3. The range of offsets contributing to each output trace is indicated
by the shading. The kinks are due to the velocity function.
Input Channels
2. VIP velocity dataset: Optional connection from dataset ( disk file only ) SEGY data type.
3. GCI velocity dataset: Optional connection from dataset ( disk file only ) GCI data type.
Output Channels
1. Angle range gather: Required connection to next process GCI data type.
1413
Parameters
Method for gather
Select to produce angle of incidence CMP gathers, angle limited CMP gathers or incidence angle value
CMP gathers. The angle of incidence option will place samples in time and distance into samples in time
and angle. The angle limited gathers will output the original CMP gather but muted outside the specified
angle range. The incidence angle value CMP gather will output the original CMP gather but the seismic
data will be replaced by the computed incidence angle.
Options: Angle of Incidence Gathers, Angle Limited CMP Gathers,
Incidence Angle value CMP Gather
Minimum of first angle group(deg.)

Enter the starting minimum angle in degrees. This parameter will appear if the Angle of Incidence
method above is chosen. This value is the minimum angle for the first angle group that will be outputted.
Maximum of first angle group(deg.)

Enter the starting maximum angle in degrees. This parameter will appear if the Angle of Incidence
method above is chosen. This value is the maximum angle for the first angle group that will be outputted.
Increment between angle groups(deg.)

Enter the increment in degrees to use for building additional angle groups. This parameter will appear if
the Angle of Incidence method above is chosen. The minimum and maximum starting angles selected
above will be incremented by this amount for every additional angle group.
Number of angle groups

Enter the number of angle groups to build using the min/max starting angle and the increment selected
above. This parameter will appear if the Angle of Incidence method above is chosen. This value will
determine how many traces are output for each input CMP gather. The center angle for each group is put
in the header word DIST.
Example:
start min angle=0, start max angle=8, increment=8, number of angle groups=3 trace1: 0-8 degrees.
trace2: 8-16 degrees. trace3: 16-24 degrees.
1414
Minimum angle to output (deg.)

Enter the minimum angle in degrees to use for angle limited gathers. All input CMP data with an
incidence angle less than this value will be muted. This parameter will appear if the Angle Limited
Gathers method above is chosen.
Maximum angle to output (deg.)

Enter the maximum angle in degrees to use for angle limited gathers. All input CMP data with an
incidence angle greater than this value will be muted. This parameter will appear if the Angle Limited
Gathers method above is chosen.
RMS velocities
was previously built or may enter the time-velocity pairs in a spreadsheet. The velocities entered should be
Matrix Type: RMSVEL
1415
XEQU
Module Description
Input Channels
Output Channels
Parameters
Module Description
XEQU will perform cross equalization of an input data set and a model data set. XEQU will design a
shaping filter to apply to the input data set to match the model data set using a least square error criterion.
The model data set can be another seismic data set or a synthetic. XEQU will output the shaping filter in
CONV time domain format.
If multiple CMPs are given for the input or model trace, XEQU will compute an average trace over the
range of CMPs. This will help increase the signal to noise ratio. Although, the frequency content could be
lowered.
XEQU will output the following traces:
Trace type
Trace Header(7)
--------------------------------------------------------------1) Average input trace duplicated (n) times.
1
2) Average model trace duplicated (n) times.
2
3) Output trace duplicate (n) times
3
4) Input cross-correlation
4
5) Output cross-correlation
5
6) Shaping filter
6
XEQU will also print the average square error between the output trace and the model trace. A value of
0.0 means a perfect match.
As a general rule, XEQU will work the best with longer operators. Better results can also be generated by
attempting to time tie the two data sets with a static shift prior to running XEQU.
Input Channels
2. Model: Required GCI data type.
Output Channels
1416
Parameters
Starting CMP from the input
This is the first CMP to design the operator from.
Number of CMPs to use from the input

Starting CMP from the model
This is the first CMP to design the operator from.
Number of CMPs to use from the model

Operator length(ms.)
Prewhitening(%)
Output CONV matrix name
Number of traces to duplicate for output
1417
XYGEOM
Module Description
Input Channels
Output Channels
Parameters
Module Description
XYGEOM is used to apply the geometry transformation to the trace headers using the existing source and
receiver coordinates in the header. XYGEOM is similar to module GEOM except that XYGEOM does not
need source information via the SeisUP database. XYGEOM only needs grid information from module
STATION. This is most beneficial for large marine surveys whereby having geometry information in the
database consumes large disk resources. If XYGEOM detects an invalid midpoint coordinate then it will
make the trace(s) dead.
XYGEOM will update the following trace headers:
HEADER
-----1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22
23.
24.
25.
NAME
Shot bin number
Shot line number
Midpoint bin number
receiver
1418
SDPN
DIST
EG
ES (closest receiver)
UTS
MSFL
MEFL
SBIN
SLIN
MSBN
MSLN
SSBN (optional)
SSLN (optional)
RSBN
RSLN
MBIN
MLIN
SGEN
SSPN (optional)
MCX
MCY
FSPN
EC
AZIM
Input Channels
Output Channels
Parameters
Apply midpoint geometry?
Select "Yes" to set midpoint oriented headers.
Apply source geometry?

Select "Yes" to set source oriented headers.
Set SBIN,SLIN,SSPN?
Select "Yes" to set SBIN and SSPN to the value of SSBN. This allows computation of a unique source ID
if no duplicate source coordinates exist in the dataset.
Apply receiver geometry?

Select "Yes" to set receiver oriented headers.
Verbose?
Select "Yes" to print out additional information for invalid source or receiver coordinates.
1419
XYMAP
Module Description
Output Channels
Parameters
Module Description
XYMAP will create a map view of 2-D or 3-D geometry. SOURCE and STATION must have been run
previously.
Output Channels
1. CGM Output: Optional connection to disk file
Parameters
Plotting scale
Enter user scale

Entered only if above option is other
Plot shots?
Choose Yes to plot the shot locations.
Shots plotting option?

Choose All to plot the all shots. Choose Swaths to plot the selected swath/swaths. The list of swaths need
to be provided in the matrix.
Swaths to plot
Matrix Type: LINES
1420
Shot annotation increment

Enter a zero to not annotate shots.
Annotate shot line?

Select Yes to annotate the shot line with the name of shot matrix. The shot line will be annotated next to
the last shot for each shot line.
Plot receivers?
Choose Yes to plot the receiver locations. The receiver line number will be annotated next to the last
receiver for each line.
Receiver annotation increment

Enter a zero to not annotate receivers.
Connect receivers with a line?

For each receiver line a line will be drawn between receiver bins if Yes is selected.
Plot midpoints?
Select Yes to plot a cross hair at every midpoint location.
Plot midpoint cells?

Select Yes to plot the midpoint cell boundaries.
Midpoint cell annotation increment

Enter a zero to not annotate the midpoint lines(s). For 2-D surveys, this is the midpoint bin increment. For
3-D surveys, this is the midpoint line increment.
Plot stacking fold?

Select Yes to fill the midpoint cell with the fold calculated from the module FOLD. For 2-D lines that
have a midpoint numbering scheme of shot plus geophone (S+G), there is no maximum cross-line interval.
In this case XYMAP will display only a square for the midpoint cell. For all other midpoint numbering
schemes, XYMAP will display the fold using the proper inline and cross-line spacing as defined in the
module STATION.
1421

Matrix Type: DBFOLD

Select Yes to use a colormap created with QCVIEW or DISPLAY.
Colormap
Create color symbols?
Select Yes to display the shot, receivers, and midpoints in color. Select No to display them in black and
white. If a fold map is to be displayed then the default will be No.
Plot side label ?

Comments
Required if Plot side label ? = Yes.
Matrix Type: TRCPLOT_CMT
Change side label font appearance ?

Required if Plot side label ? = Yes.
Title character thickness (inches)

Required if Change side label font appearance ? = Yes.
Title character size (inches)

Side label character thickness (inches)

1422
Side label character size (inches)

1423
ZAVO
Module Description
Module ZAVO performs basic AVO analysis (amplitude variation with offset) on P-wave data. The core
of the module functionality is a set if three options given to the user:
1. Computation of AVO intercept, gradient and zero-crossing points
2. Computation of AVO three polynomial coefficients
3. Computation of azimuthal AVO attributes
Coherent and random noise might degrade the AVO analysis. Noise can be reduced on the CMP gathers
by angle and offset-mixed super gathers as well as offsets-consistent amplitude corrections.
2D data
One of the most popular approximations for the P-wave reflection coefficient R iso pp between two
isotropic homogeneous layers separated by a horizontal flat interface, is the expression given by Shuey
(1985):
where is the incidence angle. Coefficients A,B,C are known as intercept, gradient, and 3rd coefficient,
respectively. All three coefficients can be estimated with module ZAVO.
Intercept, Gradient and Zero-crossing points. Coefficients A,B are computed using a LS linear curve
fitting estimation. Two methods are used: standard linear regression, and Robust linear regression
(Walden, 1991). Every two points on a Cartesian B-A plot (gradient-intercept plot) determine a straight
line, which can have at most two zero-crossing points with the coordinate axes. Such zero-crossing points
"a" and "b" are also computed and shown (see Appendix).
Three polynomial coefficients. All three coefficients A,B,C are computed using a LS second degree
polynomial curve fitting algorithm.
3D data
In the case of 3D data, azimuthal AVO attributes can be computed, based on Jenners algorithm (Jenner,
2002) (see Appendix).
Polarity Gates
1424
each polarity gate.
Velocities
then it is recommended to smooth the velocities in the VIP program and not in ZAVO.
Time Gates
References
1425
Jenner, E., 2002, Azimuthal AVO: Methodology and data examples. The Leading Edge, August 2002,
p.782-786
Ruger, A., Reflection Coefficients and Azimuthal AVO Analysis in Anisotropic Media. SEG, Geophysical
Monograph Series No.10, 2001.
Zhang, H., Brown, J., A review of AVO analysis. CREWES research report 13, 2001.
Input Channels
1. Seismic input
Required
GCI data type
Module ZAVO works on 2D or 3D data. If 2D, data must be a CMP gather; if 3D, data must be a
common-bin sorted gather. In both cases, NMO correction should be already applied to the data (a
NMO-algorithm that appropriately considers anisotropy should be used when necessary).
Output Channels
1. Attribute pseudo stack sections (see Appendix)
1426
Required
GCI data type
Each pseudo stack section has four stack traces, each one identified with a DIST header word value. Each
trace shows the value of a particular attribute vs time:
Option Intercept, Gradient and Zero-crossing (linear fit)
Trace 1
DIST=19
Intercept(t)
Trace 2
DIST=20
Gradient(t)
Trace 3
DIST=21
b(t)
Trace 4
DIST=22
a(t)
Option Three coefficients (polynomial fit)
Trace 1
DIST=19
C0(t)
Trace 2
DIST=20
C1(t)
Trace 3
DIST=21
C2(t)
Trace 4
DIST=22
Std.Deviation(t)
Option Azimuthal attributes (3D data)
Trace 1
DIST=19
Beta(t)
Trace 2
DIST=20
G1(t)
Trace 3
DIST=21
G2(t)
Trace 4
DIST=22
Std.Deviation(t)
A schematic of each output pseudo stack is shown in the attached figures.
1427
1428
1429
Parameters
The user has 3 items to select from a toggle list:
1. Intercept, Gradient and Zero-crossing points (linear fit)
2. Three coefficients (polynomial fit)
3. Azimuthal attributes (3D data only)
Regularize amplitudes? (yes/no):

Allows the user to compute AVO attributes with regularized amplitudes. Valid only for options
Intercept and Gradient (linear fit) and Three coefficients (polynomial
fit).
AVO amplitude fit will be done?:

A common problem with AVO attribute stacks is residual NMO on the CMP gathers because of imperfect
velocity analysis. To compensate, amplitudes may be selected within polarity gates, thereby relieving the
requirement of exact NMO application. Polarity gates are computed using a stack of the CMP gather. The
amplitudes in the gate are used to compute a maximum value. The maximum value for each trace in the
gather is used in the best-fit analysis. The output values are blocked as constant values over each polarity
gate. Options:
1. At each sample
2. Polarity gate
Least squares method::

1. Standard Least Squares
2. Robust Least Squares
Maximum incident angle (deg.)

degrees (Shuey, 1985). However, ZAVO renders this as a parameter at the users discretion. ZAVO will
mute the data that has an angle of incidence greater than this maximum angle.
Minimum incident angle (deg.)

Seismic data at less than 3 degrees tends to be noisy and of poor quality. ZAVO renders this as a
parameter at the users discretion. ZAVO will mute the data that has an angle of incidence that is less than
this minimum angle.
1430

survey.
Start time (ms.)

End time (ms.)




RMS velocities
1431
Matrix Type: RMSVEL
Velocity smoothing filter length (ms)

A time domain running average filter can be applied to smooth the velocity function. The filter length
should be entered in milliseconds.
1432
Appendix
.............................
Pseudo-stack sections
By a pseudo-stack section we understand a gather in which traces display one value of an attribute per
time sample per CMP location.
For example, if a least-square best-fit linear approximation is used to compute a gradient pseudo stack,
then the following algorithm can be used:
1. In a 2D dataset, take a NMO-corrected CMP gather with n traces.
2. For time t 1 , step through offsets to pick the (n-1) sample
amplitudes x i of traces 1 to n in the gather.
3. Use conventional least-squares to estimate the gradient (slope) of a
R P iso (theta) vs sin 2 (theta) plot with (n-1) samples.
1433
4. Plot this single value of gradient as a point on a CMP-vs-time plot,

in the coordinates (CMP, t 1 ).
5. Repeat steps (1)-(3) for all times t i .
6. Repeat steps (1)-(4) for all CMP gathers.
7. Once all times and CMP gathers have been considered, the entire
resulting plot is called a gradient pseudo-stack section.
.............................
1434
Zero-crossing points
ZAVO computes a pseudo stack section where traces 1 and 2 correspond to intercept and gradient
respectively (see section "Output channels"). For every 2 pairs of samples of such traces, ZAVO computes
one value for zero crossing points "a" and "b" of the gradient-intercept plot (see figure below)(*)
Values of "a" and "b" for every time are displayed in traces 3 and 4.
(*) For example, for a given time t, b(t) is computed using I(t), I(t-1), g(t), g(t-1)
1435
.............................
1436
Azimuthal attributes
According to Ruger (1996), the equation for amplitude variation with incidence angle (up to approx. 35
degrees) and azimuth for an HTI layer overlain by an isotropic overburden can be approximated by
where theta=angle of incidence, phi=the source-receiver azimuth with respect to a predefined direction,
(e.g., true north), and beta=the angle between the chosen zero azimuth direction and either the isotropy or
symmetry axis planes (i.e. parallel or perpendicular to the fractures). I is the p-wave impedance contrast
divided by two. G 1 is the isotropic AVO gradient and G 2 (the anisotropic gradient) can be approximated
by
Without knowing beta, the first equation cannot be solved by linear-squares. However, such an equation
can be rewritten as
A least-squares fit of amplitudes can now be performed on equation this, without azimuth or offset
binning. This means that all available data are used and each point is represented at the correct offset and
azimuth. In addition, meaningful error estimates can be obtained.
The variables involved can be computed by the following expressions
1437
Author:
Created on 2007 by P.Mora.
1438
ASCII Data Type

NAME
ASCII - ASCII data type
DESCRIPTION
The ASCII data type is a text file.
1439
BIN data type

NAME
BIN - SeisUP data type
DESCRIPTION
The BIN data type is a SeisUP internal format used by several modules. The exact format depends on the
module.
AUTHOR
Compiled 06/14/2010 by David Dunbar
1440
CGM Data Type

NAME
CGM - CGM data type
DESCRIPTION
The CGM data type is a computer graphics metafile with extensions for seismic traces.
1441
CMAP Data Type

NAME
CMAP - Color map data type
DESCRIPTION
Color maps are in the $QEDTOP/lib/cmaps directory. Within the color map file, the symbol # in column
one results in that line being ignored. Each line corresponds to a color. Within a line, the RGB values for
that color are entered in free field format. RGB values range from 0 (No intensity) to 255 (Full intensity).
The following is an example:
#
#
#
0
0
0
255
255
Rainbow colormap from blue to red

0
255
255
255
0
255
255
0
0
0
1442
COMPRESS Data Type

NAME
COMPRESS - SeisUP data type
DESCRIPTION
The COMPRESS data type is a SeisUP internal format used by the COMREAD and COMWRITE
modules.
AUTHOR
1443
DNG1 Data Type

NAME
DNG1 - DNG1 data set
DESCRIPTION
The DNG1 data type is a temporary file that contains partially completed 3-D CMP gathers for the module
DNG1. This data set can be released after DNG2 is successfully run. The DNG1 data set must be on disk.
1444
DNS1 Data Type

NAME
DNS1 - DNS1 data set
DESCRIPTION
The DNS1 data type is a temporary file that contains the partial sums of DMO3D. The DNS1 data set will
be read by DMO3D when restarted.
This type of data can be released after the successful execution of DMO3D. The DNS1 data set must be
on disk.
1445
ENSDCN Data Type

NAME
ENSDCN - SeisUP data type
DESCRIPTION
The ENSDCN data type is a SeisUP internal format used by the ENSDCN1 and ENSDCN1 modules.
AUTHOR
1446
FDMIG Data Type

NAME
FDMIG - SeisUP data type
DESCRIPTION
The FDMIG data type is a SeisUP internal format used by the FDMIG3D module.
AUTHOR
1447
FXYDSV Data Type

NAME
FXYDSV - SeisUP data type
DESCRIPTION
The FXYDSV data type is a SeisUP internal format used by the FXYDMIG module.
AUTHOR
1448
FXYMIG data type

NAME
FXYMIG - FXYMIG data set
DESCRIPTION
The FXYMIG data type is a temporary file that contains several sub-data sets saved for the module
FXYMIGR. FXYMIGR will read these sub-data sets and continue the finite difference FXY domain
migration.
A FXYMIG data set usually occupies immense disk space. This data type should be deleted after the
successful execution of FXYMIGR.
1449
FXYSAV Data Type

NAME
FXYSAV - FXYSAV data set
DESCRIPTION
The FXYSAV data type is a temporary file that contains several sub-data sets saved for the module
FXYMIGR. FXYMIGR will read these sub-data sets and continue the finite difference FXY domain
migration.
A FXYSAV data set usually occupies immense disk space. This data type should be deleted after the
successful execution of FXYMIGR.
1450
GCI Data Type

The GCI data type is the SeisUP internal format used by the READ and WRITE modules for storing
seismic trace data and headers. All integers are 32-bit 2s compliment and all floating point numbers are
32-bit IEEE.
Dataset Header Specification

Byte
1-8
9-32
33-56
57-80
81-104
105-116
117-120
121-124
125-128
129-132
133-136
137-140
141-144
145-148
149-152
153-156
157-160
161-164
165-168
Description
Character string SeisUP to identify the format
Host name of the system that the dataset was created on
Area name
Line name
User login name
Dataset name
Media type: 0 = Disk, 1 = 8mm, 2 = 9 track, 3 = 3480
UNIX formatted dataset was creation date
Version (currently 4)
Job ID
Number of samples per data trace
Sample interval x1000. For time data, the unit is microseconds.
Number of words per attached trace header
Primary key trace header field index
Secondary key trace header field index
Ensemble key trace header field index
Vertical axis data type: 0 = Time, 1 = Depth, 2 = Frequency
Sample data type:
0 = Amplitude
1 = Velocity
2 = Instantaneous amplitude
3 = Instantaneous phase
4 = Instantaneous frequency
5 = SV
6 = SH
7 = Well log
8 = VSP
169-172
173-176
177-180
181-184
185-200
Byte order: 0 =
Tape density: 0
Number of reels
Number of bytes
Unused
Big endian, 1 = Little endian

= High density, 1 = Low density
used so far
per sample (for compression)
Extended Trace Header Registry

Byte
1-16
17-20
Description
Header name
Header type: 0 = 32-bit integer, 1 = 32-bit IEEE float
1451
Reel Header Specification

Byte
1-16
17-20
21-24
25-28
29-32
33-36
37-40
41-44
45-48
49-56
Description
Reel name.
Tape unit number to which data was written
File on tape
Tape ordinal or current index within the data set
Last primary key written
Last secondary key written
Last ensemble key written
Last line sequence number written (TLSN)
Reel status: 0 = Assigned and opened, 1 = Successfully closed
Unused
Tape Data Layout

On tape, the reel header is appended to the general header and written as the first block on each tape in the
data set. The extended header information is then written as a single block (87-nhdr)*20 bytes long.
Where nhdr is the number of attached trace header words defined in the general header bytes 141-144.
This is then followed by optional history block(s), a single EOF, and the seismic data with attached trace
headers. The seismic data is terminated by an EOF at the end of a tape.
Block
1
2
3
1-n
Description
General header, reel header (required)
Extended trace header registry
Dataset history blocks (optional)
EOF
Seismic data
EOF
The last ids in bytes 29-40 of the reel header are the last IDs written from the previous tape.
The above headers are also written to the SDI database except that the reel headers are repeated for each
tape written and the last ids in bytes 29-40 of the reel header are for the current tape.
For disk data sets a reel header is also written to the SDI database but only one reel is defined.
Sorting
Examples for the sort order header key values are as follows:
Sort order
Shot
Shot
Shot
Shot
Geophone
Geophone
pkey
0
SLIN
0
0
0
RSLN
skey
SSPN
SBIN
OIDN
FCSN
SGEN
RSBN
ekey
FCSN
DIST
0
0
DIST
FCSN
max_ens
# traces
# traces
# traces
# traces
# traces
# traces
1452
per
per
per
per
per
per
shot
shot
shot
shot
geophone
geophone
CMP gather
CMP gather
Stack
Stack
Offset
Offset
MLIN
0
0
0
DIST
DIST
MBIN
SDPN
MLIN
MBIN
MLIN
MBIN
DIST
DIST
MBIN
MLIN
MBIN
MLIN
#
#
#
#
#
#
traces per CMP

traces per CMP
bins per line
lines per bin
bins per line
lines per bin
pkey
Primary key trace header word field
skey
Secondary key trace header field
ekey
Ensemble key trace header field
max_ens
Trace Header Specification

Each trace within a data set contains an attached trace header as follows:
Field ID
Name
TLSN
Trace Line Sequence Number The trace number within a line.

The TLSN continues to increase if additional reels are required
on the same line.
TRSN
Trace Reel Sequence Number The trace number within a reel

(each reel starts with TRSN 1
OIDN
Original ID Number The original field record number.
FCSN
Field Channel Shot Number The trace number within the

original field record.
ESPN
Energy Source Point Number Used when more than one

record occurs at the same effective surface location.
SDPN
Sequential Depth Point Number Sequential common midpoint

number. This is a number assigned by SeisUP when the geometry
of midpoint grid is established.
CDPN
Common Depth Point Number Trace number within the CDP

ensemble. Each ensemble starts with CDPN 1.
TRID
Trace status identification code: 1 = Live seismic data, 2 = Dead,

3 = Dummy, 4 = Time break, 5 = Uphole, 6 = Sweep, 7 =
Timing, 8 = Water break, 9 = Auxiliary, 10 = ASCII Label
8
9
Description
Number of vertically summed traces yielding this trace.
1453
10
Number of horizontally stacked traces yielding this trace.
11
Data use: 1 = Production, 2 = Test
12
DIST
Distance from shot location to receiver station. A negative value

indicates that the receiver station is located relative to the shot in
a direction that is opposite the line shooting direction.
13
EG
Surface elevation at receiver station position.
14
ES
Surface elevation at source position.
15
DEPS
Source depth below surface (a positive number).
16
DG
Datum elevation at receiver station position.
17
DS
Datum elevation at source position.
18
WDS
Water depth at source position.
19
WDG
Water depth at receiver station position.
20
Scalar to be applied to the following header field values: EG, ES,

DEPS, DG, DS. If the scalar value is positive, then it is used as a
multiplier; if it is negative, then it is used as a divisor. Possible
scalar values include 1, 10, 100, 1,000, and 10,000.
21
Scalar to be applied to the following header field values: SX, SY,

GX, GY, MCX, and MCY. If the scalar value is positive, then it
is used as a multiplier; if it is negative, then it is used as a divisor.
Possible scalar values include 1, 10, 100, 1,000, and 10,000.
22
SX
Source position x-coordinate.
23
SY
Source position y-coordinate.
24
GX
Receiver station position x-coordinate.
25
GY
Receiver station position y-coordinate.
26
Coordinate units: 1 = length (meters or feet), 2 = seconds of arc.
27
VW
Weathering velocity.
28
VSW
Sub-weathering velocity.
29
UTS
Uphole time at source position.
30
UTG
Uphole time at receiver station position.
31
STTS
Source static correction.
32
STTG
Receiver station static correction.
1454
33
STAT
Total applied static. This value is 0 if no static has been applied.
34
STTC
CMP Static
35
LAGB
Lag Time B Time in milliseconds between the time break
36
DELAY
Recording time delay Time in milliseconds between the

initiation of the energy source and the start of data recording.
37
MUTST
Starting mute time in units of samples.
38
MUTEND
End mute time in units of samples.
39
NSAMP
Number of samples in this trace.
40
INTVL
Sample interval in milliseconds for this trace.
41
GAINT
Gain type of field instruments: 1 = Fixed, 2 = Binary, 3 =

Floating point, 4-n = User specified.
42
Instrument gain constant (dB).
43
Instrument initial/early gain (dB).
44
Correlated: 1 = No, 2 = Yes.
45
Sweep frequency at start (Hz).
46
Sweep frequency at end (Hz).
47
Sweep length (ms).
48
Sweep Type: 1 = Linear, 2 = Parabolic, 3 = Exponential, 4 =

Other.
49
Sweep trace taper length at start (ms).
50
Sweep trace taper length at end (ms).
51
Taper Type: 1 = Linear, 2 = cos**2, 3 = Other
52
Unassigned
53
DC
Datum elevation at midpoint cell position.
54
MSFL
Midpoint Starting Flexible Line number.
55
MEFL
Midpoint Ending Flexible Line number.
56
SBIN
Sequential shot number within an SLIN. For 2D lines this is the

same as the SSPN.
1455
57
SLIN
SeisUP assigns this number according to an imported source

geometry file number. For land surveys, this number is 1 for
every shot unless multiple source files have been loaded. For
marine surveys, this number corresponds to a sail line, or swath,
number.
58
MSBN
Midpoint Station Bin Number SeisUP assigns the nearest

receiver station bin number to this header when geometry is
applied.
59
MSLN
Midpoint Station Line Number SeisUP assigns the nearest

receiver line number to this header when geometry is applied.
60
YEAR
Year in which the data was recorded.
61
DAY
Day of the year on which the data was recorded.
62
SSBN
Shot Station Bin Number SeisUP assigns the nearest receiver

station bin number to this header when geometry is applied.
63
SSLN
Shot Station Line Number SeisUP assigns the nearest receiver

line number to this header when geometry is applied.
64
RSBN
Receiver Station Bin Number
65
RSLN
Receiver Station Line Number
66
MBIN
Midpoint Bin Number This number is assigned by SeisUP

when the midpoint grid geometry is defined.
67
MLIN
Midpoint Line Number This number is assigned by SeisUP

when the midpoint grid geometry is defined.
68
Geophone group number of the first trace within the original field
record.
69
Geophone group number of the last trace within the original field
record.
70
Gap size Total number of groups dropped.
71
Unassigned
72
Sequential Gephone Number This number is assigned by

SeisUP when a projects geometry is created, and is guaranteed to
uniquely identify each receiver station in the projects geometry
database. The SGEN may not start from 1, but is guaranteed to be
sequential.
SGEN
1456
73
SSPN
Sequential Shot Number This number is assigned by SeisUP

when a projects geometry is created, and is guaranteed to
uniquely identify each shot event in the projects geometry
database. SSPN assignment starts from 1 and increases
sequentially for each shot event.
74
MCX
Midpoint cell x-coordinate.
75
MCY
Midpoint cell y-coordinate.
76
FSPN
Field Shot Point Number This number uniquely identifies each

shot point location in the field.
77
Unassigned
78
VELO
Velocity (constant velocity stacks)
79
FOLD
Number of traces summed/stacked to produce this trace.
80
DMODIST
Distance from source location to receiver station location that is

assigned by the DMODIST module.
81
Unassigned
82
AZIM
Azimuth between the source and receiver station locations.
83
EC
Surface elevation at the midpoint cell.
84
TIM1
Time horizon of first pick (ms).
85
TIM2
Time horizon of second pick (ms).
86
LINE
First four ASCII characters of line name.
87
Last four ASCII characters of line name.
1457
GVL Data Type

NAME
GVL - SeisUP interactive analysis data type
DESCRIPTION
The GVL data type is a SeisUP internal format used by interactive analysis modules.
AUTHOR
Compiled 10/08/92 by Bill Starr
1458
KTMIG Data Type

NAME
KTMIG - SeisUP data type
DESCRIPTION
The KTMIG data type is a SeisUP internal format used by the KTMIG module for restarts.
AUTHOR
1459
LAS Data Type

NAME
LAS - Data type
DESCRIPTION
The LAS data type is a well log format used by the LOGREAD module.
AUTHOR
1460
OPTDCN data type

NAME
OPTDCN - SeisUP data type
DESCRIPTION
The OPTDCN data type is a SeisUP internal format used by the OPTDCN1 and OPTDCN2 modules.
AUTHOR
1461
PSM data type

NAME
PSM - SeisUP data type
DESCRIPTION
The PSM data type is a SeisUP internal format used by the PSMIG3D module.
AUTHOR
1462
RAS1 data type

NAME
RAS1 - RAS1 data set
DESCRIPTION
The RAS1 data type is a temporary file that contains the raw time shift information picked by module
RAS1 or RESID1. Module RAS2 or RESID2 can take this data type and perform surface-consistent
analysis.
This data type can be released after the successful execution of RAS2 or RESID2. The RAS1 data set
must be on disk.
1463
RAS3D1 data type

NAME
RAS3D1 - SeisUP data type
DESCRIPTION
The RAS3D1 data type is a SeisUP internal format used by the RAS3D1 and RAS3D2 modules.
AUTHOR
1464
REG data type

NAME
REG - SeisUP data type
DESCRIPTION
The REG data type is a SeisUP internal format used by the GRIDTRNS, REGREAD, REGWRITE, RVA,
SPROMIG, SPROTRNS and VELHORZ modules.
AUTHOR
1465
RFMT data type

NAME
RFMT - RFMT data set
DESCRIPTION
The RFMT data type is a a catch all term for SEG-D and "OTHER" (mostly oddball SEG-Y) datasets.
1466
RFS1 data type

NAME
RFS1 - SeisUP data type
DESCRIPTION
The RFS1 data type is a SeisUP internal format used by the RFS2 module.
AUTHOR
1467
SCDCN1 data type

NAME
SCDCN1 - SeisUP data type
DESCRIPTION
The SCDCN1 data type is a SeisUP internal format used by the SCDCN1 and SCDCN2 modules.
AUTHOR
1468
SCDCN2 data type

NAME
SCDCN2 - SeisUP data type
DESCRIPTION
The SCDCN2 data type is a SeisUP internal format used by the SCDCN2 and SCDCN3 modules.
AUTHOR
1469
SCDECON1 data type

NAME
SCDECON1 - SeisUP data type
DESCRIPTION
The SCDECON1 data type is a SeisUP internal format used by the SCDECON1 and SCDECON2
modules.
AUTHOR
1470
SCPHD1 data type

NAME
SCPHD1 - SeisUP data type
DESCRIPTION
The SCPHD1 data type is a SeisUP internal format used by the SCPHD1 and SCPHD2 modules.
AUTHOR
1471
SCPHD2 data type

NAME
SCPHD2 - SeisUP data type
DESCRIPTION
The SCPHD2 data type is a SeisUP internal format used by the SCPHD2 and SCPHD3 modules.
AUTHOR
1472
SEG-Y data type

NAME
SEGY - SEG-Y data type
DESCRIPTION
The SEG-Y data type is as defined by the S. E. G. with extensions as defined in the GCI data type. The
SEG-Y format is used by the modules SEGYREAD and SEGYWRIT.
The binary reel header is defined as follows:
Byte
Numbers
1-4
5-8
9-12
13-14
Half
word
Full
word
1
2
3
4
15-16
17-18
19-20
10
21-22
11
23-24
12
25-26
13
27-28
14
29-30
15
31-32
16
33-34
17
Description
Job identification number.
Line number
Reel number
Number of data traces per record
(includes dummy and zero traces
inserted to fill out the record or
common depth point).
Number of auxiliary traces per record
(includes sweep, timing, gain, sync
and all other non-data traces).
Sample interval in microseconds. (for
this reel of data).
Sample interval in microseconds. (for
original field recording).
Number of samples per data trace (for
this reel of data).
Number of samples per data trace (for
original field recording).
Data sample format code:
1 = IBM floating point (4 bytes)
2 = fixed point (4 byte integer)
3 = fixed point (2 byte integer)
4 = fixed point w/gain code.
6 = IEEE floating point (4 bytes)
Auxiliary traces use the same number
of bytes per sample.
CDP fold (expected number of data
traces per CDP ensemble).
Trace sorting code:
1 = as recorded or shot sorted
2 = CDP ensemble or CDP sorted
3 = single fold continuous
4 = horizontally stacked
5 = geophone sorted
6 = channel sorted (FCSN)
7 = offset sorted
Vertical sum code: 1 = no sum 2 =
two sum N = N sum (N=32767)
Sweep frequency at start.
1473
35-36
37-38
39-40
18
19
20
9
10
10
41-42
43-44
21
22
11
11
45-46
23
12
47-48
24
12
49-50
25
13
51-52
26
13
53-54
27
14
55-56
28
14
57-58
29
15
59-60
30
15
61-64
65-68
69-72
73-76
77-80
16
17
18
19
20
81-84
85-88
89-92
93-96
97-100
21
22
23
24
25
101-104
26
Sweep frequency at end.

Sweep length (ms.)
Sweep type code: 1 = linear 2 =
parabolic 3 = exponential 4 = other
Trace number of sweep channel.
Sweep trace taper length in MS. at
start if tapered (the taper starts at
zero time and is effective for this
length.)
Sweep trace taper length in MS. at end
(the ending taper starts at sweep
length minus the taper length at end).
Taper type: 1 = linear 2 = cos**2
3 = other
Correlated data traces: 1 = no
2 = yes
Binary gain recovered: 1 = yes
2 = no
Amplitude recovery method: 1 = none
2 = spherical divergence 3 = AGC
4 = other
Measurement system: 1 = meters
2 = feet
Impulse signal: 1 = increase in
pressure or upward geophone case
movement gives a negative number.
Polarity: 2 = Increase in pressure or
upward geophone case movement gives a
positive number.
Vibratory Polarity Code: Seismic
signal Lags Pilot by: 1 = 337.5 to
22.5 degrees 2 = 22.5 to 67.5 degrees
3 = 67.5 to 112.5 degrees 4 = 112.5
to 157.2 degrees 5 = 157.5 to 202.5
degrees 6 = 202.5 to 247.5 degrees
7 = 247.5 to 292.5 degrees 8 = 292.5
to 337.5 degrees
Not used
Not used
"GCI "
GCI version
Byte order 0 = Big Endian 1 = Little
Endian
Primary trace header word key.
Secondary trace header word key.
Ensemble trace header word key.
Maximum # of traces per ensemble.
Vertical axis data type. 0 = Time
1 = Depth 2 = Frequency
Data type of the samples. 0 =
amplitude 1=velocity 2=inst.
amplitude 3=inst. phase
4=inst. frequency
1474
Each trace within a data set contains an attached trace header as follows:
Word
1
Bytes
1-4
Word
1
Name
TLSN
5-8
TRSN
3
4
9-12
13-16
3
4
OIDN
FCSN
17-20
ESPN
6
7
21-24
25-28
6
7
SDPN
CDPN
29-30
TRID
31-32
33-34
10
9
10
35-36
37-40
11
12
DIST
11
41-44
13
EG
12
13
45-48
49-52
14
15
ES
DEPS
14
15
16
17
18
53-56
57-60
61-64
65-68
69-70
16
17
18
19
20
DG
DS
WDS
WDG
18
71-72
21
Description
Trace sequence number within line
(numbers continue to increase if
additional reels are required on
the same line).
Trace sequence number within reel
(each reel starts with trace number
one).
Original field record number
Trace number within the original
field record.
Energy source point number (used
when more than one record occurs at
the same effective surface location).
Sequential common midpoint number.
Trace number within the CDP ensemble
(each ensemble starts with trace
number 1).
Trace identification code: 1 =
seismic data 2 = dead 3 = dummy
4 = time break 5 = uphole 6 = sweep
7 = timing 8 = water break 9 =
auxiliary 10 = label (ASCII)
Number of vertically summed traces
yielding this trace. (1 is 1 trace,
2 is 2 summed traces, etc.)
Number of horizontally stacked traces
yielding this trace. (1 is 1 trace,
2 is 2 stacked traces, etc.)
Data use: 1 = production 2 = test
Distance from source point to
receiver group (negative if opposite
to direction in which line is shot).
Receiver group elevation; all
elevations above sea level are
positive and below sea level are
negative.
Surface elevation at source.
Source depth below surface (a
positive number).
Datum elevation at receiver group.
Datum elevation at source.
Water depth at source.
Water depth at group.
Scalar to be applied to all
elevations and depths specified in
bytes 41-68 and 141-144 to give real
value. Scalar = 1, 10, 100, 1000, or
10,000. If positive, scalar is used
as a multiplier; if negative, scalar
Scalar to be applied to all
coordinates and depths specified in
bytes 73-88 to give a real value.
Scalar = 1, 10, 100, 1000, or 10,000.
1475
19
20
21
22
23
73-76
77-80
81-84
85-88
89-90
22
23
24
25
26
23
24
24
25
25
26
26
91-92
93-94
95-96
97-98
99-100
101-102
103-104
27
28
29
30
31
32
33
27
105-106 34
27
107-108 35
28
109-110 36
28
29
29
30
111-112
113-114
115-116
117-118
30
119-120 41
31
31
32
32
33
33
34
121-122
123-124
125-126
127-128
129-130
131-132
133-134
34
135-136 49
35
35
137-138 50
139-140 51
36
36
37
37
38
141-142
143-144
145-146
147-148
149-150
52
53
54
55
56
DC
MSFL
MEFL
SBIN
38
151-152 57
SLIN
37
38
39
40
SX
SY
GX
GY
UTS
UTG
STTS
STTG
STAT
MUTST
MUTEND
42
43
44
45
46
47
48
If positive, scalar is used as a

multiplier; if negative, scalar is
used as a divisor.
Source coordinate - X
Source coordinate - Y
Group coordinate - X
Group coordinate - Y
Coordinate units: 1 = length
(meters or feet) 2 = seconds
of arc.
Weathering velocity.
Sub weathering velocity.
Uphole time at source.
Uphole time at group.
Source static correction.
Group static correction.
Total static applied (zero if no
static has been applied).
Lag time A. Time in ms. between end
of 240 byte trace identification
header and time break.
Lag time B. Time in ms. between time
break and the initiation time of the
energy source.
Delay recording time. Time in ms
between initiation time of energy
source and time when recording of
data samples begins
Mute time -- start. in samples
Mute time -- end. in samples
Number of samples in this trace.
Sample interval in ms. for this
trace.
Gain type of field instruments: 1 =
fixed 2 = binary 3 = floating point
4 = n = optional use
Instrument gain constant, (db)
Instrument early or initial gain (db)
Correlated:
1 = no 2 = yes
Sweep frequency at start
Sweep frequency at end.
Sweep length in ms.
Sweep type: 1 = linear 2 =
parabolic 3 = exponential 4 = other
Sweep trace taper length at start in
ms.
Sweep trace taper length at end in ms.
Taper type: 1 = linear 2 = cos**2
3 = other
0
Datum elevation at depth point
Midpoint starting flexible line number
Midpoint ending
flexible line number
Shot bin #. This is the sequential
shot number within a shot line. For
2-D lines, this is the same as SSPN.
Shot line #. This is the sequential
1476
39
153-154 58
39
155-156 59
40
40
41
157-158 60
159-160 61
161-162 62
41
163-164 63
42
165-166 64
42
167-168 65
43
169-170 66
43
171-172 67
44
173-174 68
44
175-176 69
45
45
46
47
48
49
50
51
52
53
54
177-178
179-180
181-184
185-188
189-192
193-196
197-200
201-204
205-208
209-212
213-216
70
71
72
73
74
75
76
77
78
79
80
55
55
56
57
58
59
60
217-218
219-220
221-224
225-228
229-232
233-236
237-240
81
82
83
84
85
86
87
shot line number.

Midpoint station bin #. This is the
station bin # nearest to the CMP.
MSLN
Midpoint station line #. This is the
station line # nearest to the CMP.
Year data recorded.
Day of year.
SSBN
Source station bin #. This is the
station bin # nearest to the shot.
SSLN
Source station line #. This is the
station line # nearest to the shot.
RSBN
Receiver station bin #. This is the
station bin # nearest to the receiver.
RSLN
Receiver station line #. This is the
station line # nearest to the receiver.
MBIN
Midpoint bin #. This is the
sequential midpoint number within a
midpoint line. This is the same as
SDPN for 2-D lines.
MLIN
Midpoint line #. This is the
sequential midpoint line number.
Geophone group number of trace
number one within original field
record.
Geophone group number of last trace
within original field record.
Gap size (total number groups dropped).
0
SGEN
Sequential geophone #
SSPN
Sequential shot #
MCX
Midpoint cell center coordinate - X
MCY
Midpoint cell center coordinate - Y
FSPN
Field shotpoint number
Unassigned
VELO
Velocity (Constant velocity stacks)
FOLD
Number of traces summed (stack)
DMODIST Distance from source point to
receiver group that is assigned by
module DMODIST.
Unassigned
AZIM
Azimuth between the source and receiver
EC
TIM1
Time (Ms.) horizon of first pick.
TIM2
Time (Ms.) horizon of second pick.
LINE
1st 4 bytes of line name (ASCII)
2nd 4 bytes of line name (ASCII)
MSBN
1477
SGN1 data type

NAME
SGN1 - SGN1 data set
DESCRIPTION
The SGN1 data type is a temporary file that contains the instantaneous amplitude information picked by
module SGN1. Module SGN2 can take this data type and perform surface-consistent analysis.
This data type can be released after the successful execution of SGN2. The SGN1 data set must be on
disk.
1478
SGNE1 data type

NAME
SGNE1 - SeisUP data type
DESCRIPTION
The SGNE1 data type is a SeisUP internal format used by the SGNE1 and SGNE2 modules.
AUTHOR
1479
SMIG data type

NAME
SMIG - SeisUP data type
DESCRIPTION
The SMIG data type is a SeisUP internal format used by the SMIG, SMIGSAVE and VSLICE modules.
AUTHOR
1480
Matrix 3DDIR
MATRIX NAME
3DDIR --
DESCRIPTION
DIMENSIONS
None
VECTORS
Line name
Default .....:
Min .........:
Max .........:
Rule ........:
Directory
Default .....:
Min .........:
Max .........:
Rule ........:
# shots
Default .....:
Min .........:
Max .........:
Rule ........:
1481
Min. Rec. X
Type ........:Double
Default .....:0
Min .........:
Max .........:
Rule ........:
Max. Rec. X
Default .....:0
Min .........:
Max .........:
Rule ........:
Min. Rec. Y
Default .....:0
Min .........:
Max .........:
Rule ........:
Max. Rec. Y
Default .....:0
Min .........:
Max .........:
Rule ........:
Min. Mid. X
Default .....:0
Min .........:
Max .........:
Rule ........:
1482
Max. Mid. X
Default .....:0
Min .........:
Max .........:
Rule ........:
Min. Mid. Y
Default .....:0
Min .........:
Max .........:
Rule ........:
Max. Mid. Y
Default .....:0
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module SOURCE.
AUTHOR
Created on Nov 15,1995 by David Dunbar
1483
Matrix 3DREFDEF
MATRIX NAME
3DREFDEF -
DESCRIPTION
DIMENSIONS
None
VECTORS
SSPN
Default .....:0
Min .........:1
Max .........:
Rule ........:
NDist0
Default .....:0
Min .........:0
Max .........:
Rule ........:
FDist0
Default .....:0
Min .........:0
Max .........:
Rule ........:
1484
NDist1
Default .....:0
Min .........:0
Max .........:
Rule ........:
FDist1
Default .....:0
Min .........:0
Max .........:
Rule ........:
NDist2
Default .....:0
Min .........:0
Max .........:
Rule ........:
FDist2
Default .....:0
Min .........:0
Max .........:
Rule ........:
NDist3
Default .....:0
Min .........:0
Max .........:
Rule ........:
1485
FDist3
Default .....:0
Min .........:0
Max .........:
Rule ........:
NDist4
Default .....:0
Min .........:0
Max .........:
Rule ........:
FDist4
Default .....:0
Min .........:0
Max .........:
Rule ........:
NDist5
Default .....:0
Min .........:0
Max .........:
Rule ........:
FDist5
Default .....:0
Min .........:0
Max .........:
Rule ........:
1486
AUTHOR
Created on Jun 17, 2004 by Larry
1487
Matrix 4THNMO
MATRIX NAME
4THNMO -- 4th order velocity correction
DESCRIPTION
4THNMO matrix type contains time variant 4th order velocity information. This matrix type is used by
many different modules.
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Rule ........:Ascending order
1488
C4
The units are the 4th root of (ms) / (feet or meters).
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Nov. 24, 1998
1489
Matrix AFS1B
MATRIX NAME
AFS1B -- First break matrix
DESCRIPTION
This matrix is used to store first break picks. Each row corresponds to a channel number with a shot.
DIMENSIONS
SLIN
Min .........:1
Max .........:
Max # SP ....:999999
SBIN
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Time (ms.)
Default .....:"No pick"
Min .........:0
Max .........:
Rule ........:
1490
SEE ALSO
Module RFS1,
Module DISPLAY.
AUTHOR
Created on June 3, 1993 by Bill
1491
Matrix AMPSTAT
Matrix Description
Dimensions
Summary Group Type(ms)
Default .....:Ensemble
Min .........:
Max .........:
Max SP ......:1
Vectors
Group Key
Default .....:
Min .........:
Max .........:
Rule ........:
MIN Amp
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
MAX Amp
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1492
ABS Mean
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
RMS
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Median Amp
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1493
Matrix AMPWIN
Matrix Description
Vectors
Time1 (ms)
Default .....:
Min .........:
Max .........:
Rule ........:
Time2 (ms)
Default .....:
Min .........:
Max .........:
Rule ........:
1494
Matrix APERTURE
MATRIX NAME
APERTURE -
DESCRIPTION
This matrix defines spatially variant migration apertures. The apertures specified should be the Full
Apertures.
DIMENSIONS
None
VECTORS
Line
Default .....:
Min .........:
Max .........:99999
Rule ........:
Bin
Default .....:
Min .........:
Max .........:99999
Rule ........:
Aperture (distance units)

Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
1495
AUTHOR
Created on Jan 16, 2003 by herman
1496
Matrix AUTC
Matrix Description
Vectors
Autocorrelation length(ms)
Default .....:160
Min .........:0
Max .........:
Rule ........:
Start Header
Default .....:NONE
Rule ........:
End Header
Default .....:NONE
Rule ........:
1497
Matrix AVGVEL
MATRIX NAME
AVGVEL -- Average velocity
DESCRIPTION
AVGVEL matrix type contains time variant average velocity information.
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Velocity
Default .....:
Min .........:1000
Max .........:99999
1498
Rule ........:
AUTHOR
Created on Sept. 13 1995 by David Dunbar
1499
Matrix AVOC
Matrix Description
Dimensions
MLIN
Min .........:1
Max .........:
Max # SP ....:999999
MBIN
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Time (ms.)
Default .....:"No selection"
Min .........:0
Max .........:
Rule ........:
1500
Matrix CMPDATUM
MATRIX NAME
CMPDATUM -- CMP datum elevation matrix
DESCRIPTION
This matrix is used by the STATIC module to pass midpoint datum elevations to other modules.
DIMENSIONS
MLIN index
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
Datum
The row number should correspond to the relative MBIN index. In other words the actual MBIN is
computed as the row number plus the first MBIN in the survey minus one.
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module STATIC.
AUTHOR
Created on July 20, 2000 by David
1501
Matrix COFFOFF
Matrix Description
Use this matrix to define the starting and ending offset values for each offset bin for the module COFF.
Start and end offset values are allowed to overlap adjacent offset bins if it is desired to copy the trace to
adjacent offset bins. An example use for this parameter is for 3-D land surveys where one desires to have a
greater offset bin interval for the short offsets and a smaller offset interval on the long offsets.
Vectors
From
Type.........:Integer
Default......:
Min..........:0
Max..........:
Rule.........:Ascending order
To
Default......:
Min..........:0
Max..........:
1502
Dialog COLORSURFDEF
Horizon attribute editor dialog
Use this dialog to change the attributes for interpreted horizons. Attributes that can be changed are color,
line style, and line color.
To change the color, press on the colored button. A color editor dialog will appear as follows:
1503
Select one of the "Base colors" or select one of the "Custom colors". If a "Custom color" is selected, an
RGB color editor will appear as follows:
Select the RGB values for the color desired.
The following buttons are available on the horizon attribute dialog:

Ok
Apply any changes and pop-down the dialog
1504
Save
Apply any changes and save the current attributes to the database.
Apply
Apply any to the current display.
Cancel
Cancel any changes and pop-down the dialog.
Help
Show this document.
1505
Matrix CONVFREQ
Matrix Description
Use this matrix to define a filter in the frequency domain. Values will be linearly interpolated between
defined frequency points. Values not defined at DC or Nyquist will be the nearest defined value.
Vectors
Frequency(Hz)
Type ........:Float
Default .....:
Min .........:
Max .........:
Amplitude
Type ........:Float
Default .....:1.0
Min .........:
Max .........:
Rule ........:
Phase(deg)
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
See Also
Matrix CONVFREQ1, Matrix CONVTIM, Module CONV.
1506
Matrix CONVFREQ1
Matrix Description
Use this matrix to define a filter in the frequency domain. Values will be linearly interpolated between
defined frequency points. Values not defined at DC or Nyquist will be the nearest defined value. Enter
deeper filters in sequence below the first. Enter sequential time gates on each row (for 3 gates there will be
3 Start time, End time rows). The last end time will default to the record length if left blank or if it is
coded greater than the record length.
Vectors
Frequency(Hz)
Type ........:Float
Default .....:
Min .........:
Max .........:
Amplitude
Type ........:Float
Default .....:1.0
Min .........:
Max .........:
Rule ........:
Phase(deg)
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
Start time(ms)
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
1507
Rule ........:
End time(ms)
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
See Also
Matrix;CONVTIM, Matrix;CONVFREQ, Module;CONV.
1508
Matrix CONVTIM
Matrix Description
Use this matrix to define a filter in the time domain. Each successive sample will correspond to one
sample interval.
Dimensions
t0 sample #
Enter the sample number corresponding to time zero. All samples before this sample will considered the
negative time for a two sided filter.
Min .........:1
Max .........:
Max # SP ....:1
Vectors
Filter
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
See Also
Matrix CONVFREQ, Matrix CONVFREQ1, Module CONV.
1509
Matrix CONVTIME
Matrix Description
This matrix does not appear to have ever been used. Use this matrix to define a filter in the time domain.
Each successive sample will correspond to one sample interval.
Dimensions
none
Vectors
filter
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
See Also
Matrix CONVFREQ, Matrix CONVFREQ1, Matrix CONVTIM, Module CONV.
1510
Matrix CVAETAS
Matrix Description
Vectors
Eta
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1511
Matrix CVAVELS
Matrix Description
Dimensions
none
Vectors
Velocity
Default .....:
Min .........:1
Max .........:
Rule ........:Ascending
1512
Matrix DBFOLD
MATRIX NAME
DBFOLD - Fold distribution database attribute
DESCRIPTION
This matrix is used to hold the post-stack fold distribution attribute in the database. This attribute is
entered with module FOLD and can be viewed with module QCVIEW.
DIMENSIONS
MLIN index
This is the MLIN index starting from 1 within the database.
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Fold
The row number is the MBIN index starting from 1 within the database.
Default .....:"No fold"
Min .........:0
Max .........:
Rule ........:
AUTHOR
Created on Dec. 9, 1994 by Bill
1513
Matrix DBFOLDOFF
MATRIX NAME
DBFOLDOFF - Pre-stack fold distribution database attribute
DESCRIPTION
This matrix is used to hold the pre-stack fold distribution attribute in the database. This attribute is entered
with module FOLD or DBHDR. The pre-stack fold distribution is defined as the CMP fold within a
common offset.
DIMENSIONS
MLIN
Min..........:1
Max..........:
Max # SP.....:999999
Offset
Min..........:1
Max..........:
Max # SP.....:999999
VECTORS
Fold
Default......:"No fold"
Min..........:0
Max..........:
Rule.........:
1514
AUTHOR
Created on Nov 22, 1999 by Bill
1515
Matrix DECON
Matrix Description
Vectors
Operator length(ms)
Default .....:160
Min .........:0
Max .........:
Rule ........:
Prewhitening(%)
Type ........:Float
Default .....:.1
Min .........:0
Max .........:
Rule ........:
Prediction gap(ms)
Default .....:32
Min .........:0
Max .........:
Rule ........:
Start Header
Default .....:NONE
Rule ........:
End Header
Default .....:NONE
Rule ........:
1516
1517
Matrix DFORM
MATRIX NAME
DFORM -- Dump format definition
DESCRIPTION
This matrix is used by module TDUMP.
DIMENSIONS
None
VECTORS
Skip EOFs
Number of Ends-Of-File to skip from the current position in the data set before executing the dump
defined by this row of the matrix. Positive values indicate a forward skip and negative values a backward
skip.
Type ........:integer
Default .....:0
Min .........:
Max .........:
Rule ........:
Skip Recs
Number of physical records to skip from current position in the data set before executing the dump defined
by this row of the matrix. Positive values indicate a forward skip and negative values a backward skip.
Default .....:0
Min .........:
Max .........:
Rule ........:
1518
Skip Bytes
Number of 8 bit bytes to skip from the beginning of each record defined by this row of the matrix.
Default .....:0
Min .........:
Max .........:
Rule ........:
Bytes/dump
Number of 8 bit bytes to convert and dump in each record defined by this row of the matrix.
Default .....:0
Min .........:
Max .........:
Rule ........:
Rec/dump
Number of physical records to dump defined by this row of the matrix.
Default .....:0
Min .........:
Max .........:
Rule ........:
Format
Define the conversion format to use for the data defined by this row of the matrix. Seven (7) possible
formats are understood by TDUMP. No leading blanks are allowed. Interpretation IS case sensitive.
Available formats are:
- HEXADECIMAL
- EBCDIC
- ASCII
- INT16
- INT32
- IBMFP
- IEEEFP
Type ........:string
Default .....:INT32
Rule ........:
1519
Rew(Y/N)
Rewind the data set to the beginning prior to executing any instructions on this row.
Type ........:string
Default .....:NO
Rule ........:
SEE ALSO
ModuleTDUMP.
AUTHOR
Created on May 23, 2003 By John Stevens
1520
Matrix DICE
MATRIX NAME
DICE -- Coherency-weight table for module DICE
DESCRIPTION
Use this matrix to define a coherency vs. weight table. The coherency is between the signal and the
are exactly the same. The weight will be applied to the signal prior to summing with the original data.
DICE will linearly interpolate weights between defined coherencies. Weights will be held constant prior to
the first defined coherency and after the last defined coherency.
DIMENSIONS
None
VECTORS
Coherency
Type ........:Float
Default .....:
Min .........:-1
Max .........:1
Weight
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
SEE ALSO
Module DICE.
1521
AUTHOR
Created on Feb. 18, 1994 by Bill
1522
Matrix DIPMODEL
MATRIX NAME
DIPMODEL -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:999999
Secondary
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
Time
Default .....:
Min .........:0
Max .........:
Rule ........:
X-Dip (ms/tr)
Default .....:
Min .........:
Max .........:
Rule ........:
1523
Y-Dip (ms/tr)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Jan. 28, 1993 by JohnS
1524
Matrix DISTOFF
MATRIX NAME
DISTOFF - Input custom offset intervals
DESCRIPTION
This matrix is used to describe custom common offset bin intervals for the module DMODIST. The offset
entered will be the center of the offset bin.
DIMENSIONS
None
VECTORS
Offset
Default......:
Min..........:0
Max..........:
AUTHOR
Created on Thu Feb 25 14:18:23 1999 by bill
1525
Matrix DMUX
MATRIX NAME
DMUX - Channel number description
DESCRIPTION
Use this matrix to define channel numbers for the module DEMUX.
Example 120 channel SEG-B

The data channels would be 7,8,9,10, 12,13,14,15,...,152,153,154,155.
The gain channels would be 6,11,16,...,151.
The auxiliary channels would be 1,2,3,4,5
Example 240 channel SEG-D type 44

The data channels would be 3,4,5,6,...242.
No gain channels will be defined but an empty gain matrix is required.
The auxiliary channels would be 1,2, 243,244,...266.
Example 120 channel SEG-D type 15

The data channels would be 9,10,11,12, 14,15,16,17,...154,155,156,157.
The gain channels would be 3,8,13,,,153.
The auxiliary channels would be 1,2, 4,5,6,7
Note that for SEG-D the first two channels are always auxiliary.
DIMENSIONS
None
VECTORS
1526
Channel
For output channel definition, enter the input channel number. The row number will correspond to the
output channel number (FCSN) in the trace header. For the gain, auxiliary, and data channels, enter the
input channel number that corresponds to that particular channel type.
Default .....:
Min .........:1
Max .........:
Rule ........:
AUTHOR
Created on May 2, 1996 by Bill
1527
Matrix DNGBINS
Matrix Description
This matrix does not appear to have ever been used.
Dimensions
none
Vectors
MBIN strt
Default .....:
Min .........:
Max .........:
Rule ........:
MLIN strt
Default .....:
Min .........:
Max .........:
Rule ........:
MBIN end
Default .....:
Min .........:
Max .........:
Rule ........:
1528
MLIN end
Default .....:
Min .........:
Max .........:
Rule ........:
Delta MBIN
Default .....:
Min .........:
Max .........:
Rule ........:
Delta MLIN
Default .....:
Min .........:
Max .........:
Rule ........:
# MBIN grps
Default .....:
Min .........:
Max .........:
Rule ........:
# MLIN grps
Default .....:
Min .........:
Max .........:
Rule ........:
1529
Matrix DSETLIST
MATRIX NAME
DSETLIST -
DESCRIPTION
DIMENSIONS
None
VECTORS
Dataset Name
Default .....:
Rule ........:
AUTHOR
Created on Jun 19, 2004 by David Dunbar
1530
Matrix DUMPLIST
MATRIX NAME
DUMPLIST - User defined header dump list for HDRDUMP
DESCRIPTION
Enter the index of each successive header word to dump for the module HDRDUMP. The row number is
the order in which the headers will be printed. To dump headers OIDN, FCSN and FOLD, one would
code:
Header Word
----------3
4
79
DIMENSIONS
None
VECTORS
Header Word
Default .....:None
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on 12 January, 2006 by John Stevens
1531
Matrix ENSWIN
MATRIX NAME
ENSWIN -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start (ms.)
Default......:
Min..........:
Max..........:
End (ms.)
Default......:
Min..........:
Max..........:
AUTHOR
Created on Tue Mar 21 16:36:49 2000 by jensen
1532
Matrix ETANMO
MATRIX NAME
ETANMO -
DESCRIPTION
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
ETA
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1533
AUTHOR
Created on Jan 19, 2004 by Steve Jensen
1534
Matrix EVEL
MATRIX NAME
EVEL -- Elliptical velocity correction
DESCRIPTION
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Vslow
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1535
Vfast
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Sept 8, 2005 by Placido
1536
Matrix EXTRACT
MATRIX NAME
EXTRACT -- select or extract ids
DESCRIPTION
DIMENSIONS
None
VECTORS
Pri. strt
This is the primary starting id. The default is to pass all primary ids but dependent upon the secondary
and tertiary ids.
Default .....:"All pass"
Min .........:
Max .........:
Rule ........:
Pri. end
This is the primary ending id. The default is the primary starting id.
Default .....:"Pri. strt"
Min .........:
Max .........:
Rule ........:
Delta Pri.
This is the increment added to the starting and ending ids to get the next id to extract or select.
Default .....:0
Min .........:0
Max .........:
1537
Rule ........:
# Pri. grps
This is the number of primary groups to extract. For example, suppose we wish to extract ids 100-102,
200-201, & 300-302. The starting id would be 100, the ending id would be 102, the delta primary would
be 100, and the number of groups would be 3.
Default .....:1
Min .........:1
Max .........:
Rule ........:
Sec. strt
This is the secondary starting id. The default is to pass all secondary ids but dependent upon the primary
and tertiary ids.
Min .........:
Max .........:
Rule ........:
Sec. end
This is the secondary ending id. The default is the secondary starting id.
Default .....:"Sec. strt"
Min .........:
Max .........:
Rule ........:
Delta Sec.
Default .....:0
Min .........:0
Max .........:
Rule ........:
1538
# Sec. grps
This is the number of secondary groups to extract. For example, suppose we wish to extract ids 100-102,
200-201, & 300-302. The starting id would be 100, the ending id would be 102, the delta secondary would
Default .....:1
Min .........:1
Max .........:
Rule ........:
Ter. strt
This is the tertiary starting id. The default is to pass all tertiary ids but dependent upon the primary and
secondary ids.
Min .........:
Max .........:
Rule ........:
Ter. end
This is the tertiary ending id. The default is the tertiary starting id.
Default .....:"Ter. strt"
Min .........:
Max .........:
Rule ........:
Delta Ter.
Default .....:0
Min .........:0
Max .........:
Rule ........:
1539
# Ter. grps
This is the number of tertiary groups to extract. For example, suppose we wish to extract ids 100-102,
200-201, & 300-302. The starting id would be 100, the ending id would be 102, the delta tertiary would be
100, and the number of groups would be 3.
Default .....:1
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module EXTRACT, Module SELECT.
AUTHOR
Created on Jan. 28, 1993 by Bill
1540
Matrix FILEFREQ
MATRIX NAME
FILEFREQ -- Time varying hi-cut frequencies
DESCRIPTION
FILEFREQ matrix type contains time variant frequency information.
VECTORS
Time (ms)
Type ........:Float
Default .....:
Min .........:0
Max .........:
High cut(Hz)
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:Descending order
AUTHOR
Created on November 4, 1998 by David Disher
1541
Matrix FILES
MATRIX NAME
FILES -
DESCRIPTION
DIMENSIONS
None
VECTORS
File Names
Type.........:String
Default......:
Rule.........:
AUTHOR
Created on Tue Apr 23 13:37:57 2002 by jensen
1542
Matrix FILTER
MATRIX NAME
FILTER -- Ormsby filter specification
DESCRIPTION
This matrix is used by the FILTER module to specify the trapezoidal filter specifications.
DIMENSIONS
None
VECTORS
Low Cut
This is the 60 db down frequency point in hz.
Default .....:
Min .........:0
Max .........:
Rule ........:
Low Pass
Default .....:
Min .........:0
Max .........:
Rule ........:
High Pass
Default .....:
Min .........:0
Max .........:
1543
Rule ........:
High Cut
Default .....:
Min .........:0
Max .........:
Rule ........:
Start Header
Specify a time horizon header to add to the start times. Allowable options are NONE for no addition,
TIM1 for the the time horizon 1 in the trace header, and TIM2 for the the time horizon 2.
Default .....:NONE
Rule ........:
End Header
Specify a time horizon header to add to the ending times. Allowable options are NONE for no addition,
Default .....:NONE
Rule ........:
SEE ALSO
Module FILTER, Module HORIZON, Matrix FILTERB.
AUTHOR
1544
Matrix FILTERB
MATRIX NAME
FILTERB -- Butterworth filter specification
DESCRIPTION
This matrix is used by the FILTER module to specify the Butterworth filter specifications.
DIMENSIONS
None
VECTORS
Low Slope
This is the rate of tapering in decibels per octave for frequencies below the low pass.
Default .....:
Min .........:0
Max .........:
Rule ........:
Low Pass
Default .....:
Min .........:0
Max .........:
Rule ........:
High Pass
Default .....:
Min .........:0
Max .........:
1545
Rule ........:
High Slope
This is the rate of tapering in decibels per octave for frequencies below the high pass.
Default .....:
Min .........:0
Max .........:
Rule ........:
Start Header
Default .....:NONE
Rule ........:
End Header
Default .....:NONE
Rule ........:
SEE ALSO
Module FILTER, Module HORIZON, Matrix FILTER.
AUTHOR
1546
Matrix FKFAN
MATRIX NAME
FKFAN -
DESCRIPTION
Matrix FKFAN can contain up to 100 Fan-shaped filters. The user specifies the dip as ms/trace. From slow
(dip) cut to steep (dip) cut the numbers have to be in increasing order. i.e. -100,-70,-1.5,-1 or 1,1.5,70,80.
DIMENSIONS
None
VECTORS
Slow cut (ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Slow pass(ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Steep pass(ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1547
Steep cut(ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on June 1, 1993
1548
Matrix FKFANV
MATRIX NAME
FKFANV -
DESCRIPTION
Matrix FKFANV can contain up to 100 Fan-shaped filters. The user specifies the dip as ms/trace. From
slow (dip) cut to steep (dip) cut the numbers have to be in increasing order. i.e. -100,-70,-1.5,-1 or
1,1.5,70,80.
DIMENSIONS
T Window #
Min .........:
Max .........:
Max # SP ....:5
VECTORS
Slow cut (ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Slow pass(ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1549
Steep pass(ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Steep cut(ms/trc)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1550
Matrix FKPOLY
MATRIX NAME
FKPOLY -
DESCRIPTION
Matrix FKPOLY can contain up to 50 polygon FK filters. Each filter can have up to 100 vertexes. If the
first vertex and the last vertex are the same, only one is used. A minimum of three distinct vertexes have to
be specified. The vertexes have to be either in clockwise or counter-clockwise order. Only convex
polygons are allowed.
DIMENSIONS
FILTER NUMBER
Min .........:
Max .........:
Max # SP ....:50
VECTORS
Frequency (%)
Type ........:Float
Default .....:
Min .........:0
Max .........:100
Rule ........:
Wavenumber (%)
Type ........:Float
Default .....:
Min .........:-100
Max .........:100
Rule ........:
1551
AUTHOR
Created on July 8, 1993
1552
Matrix FKPOLYV
MATRIX NAME
FKPOLYV -
DESCRIPTION
DIMENSIONS
FILTER NUMBER
Min .........:
Max .........:
Max # SP ....:50
T Window #
Min .........:
Max .........:
Max # SP ....:5
VECTORS
Frequency (%)
Type ........:Float
Default .....:
Min .........:0
Max .........:100
Rule ........:
Wavenumber (%)
Type ........:Float
Default .....:
Min .........:-100
Max .........:100
Rule ........:
1553
AUTHOR
1554
Matrix FLEX
MATRIX NAME
FLEX -
DESCRIPTION
DIMENSIONS
SBIN
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
FCSN&pflex&nflex
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on July 15, 1993 by Bill
1555
MATRIX NAME
FLEXOVP -- Offset variant flex overlaps
DESCRIPTION
This matrix is used by the module FLEX to specify offset variant flex overlaps. FLEX will linearly
interpolate the flex overlap at group centers. Overlaps prior to the first defined offset and after the last
defined offset will be constant.
DIMENSIONS
None
VECTORS
Offset
Type ........:Float
Default .....:
Min .........:0
Max .........:
Overlap(%)
This is the percentage of the cross-line interval outside the cell boundary to search for traces to maintain
the minimum fold.
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
SEE ALSO
Module FLEX.
1556
AUTHOR
1557
Matrix FXYFREQ
MATRIX NAME
FXYFREQ -- Time variant frequencies
DESCRIPTION
Matrix type FXYFREQ contains the time variant frequency information for module FXYMIG. Module
FXYMIG will linearly interpret frequencies in time. Only those frequencies within the specified range will
be included in the migration.
DIMENSIONS
None
VECTORS
Time (ms)
Type ........:Float
Default .....:
Min .........:0
Max .........:
Low cut(Hz)
Type ........:Float
Default .....:
Min .........:0
Max .........:
High cut(Hz)
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:Descending order
1558
SEE ALSO
Matrix FXYFREQ.
AUTHOR
Created on Feb 11, 1993
1559
Matrix GAIN
MATRIX NAME
GAIN -- Gain function for module GAIN
DESCRIPTION
This matrix defines the gain curve at specified primary and secondary ids. The Gain values are converted
to scale factors at the Time(ms) times using the following:
scale = rfmt / (2.0 ** (gain / 100.0))
where:
rfmt
is the Reference mean value.
A Reference mean of 1.0 and a Gain of 100.0 will give a scale of 0.5. A Gain of -100.0 will give a scale
of 2.0.
DIMENSIONS
Primary
Min .........:0
Max .........:
Max # SP ....:999999
Secondary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Time(ms)
Default .....:
Min .........:0
1560
Max .........:
Gain
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module GAIN.
AUTHOR
1561
Matrix GCIHDREXT
Matrix Description
Vectors
Name
Default .....:""
Rule ........:
Type
Default .....:"int"
Rule ........:
1562
Matrix GDELAY
MATRIX NAME
GDELAY -
DESCRIPTION
DIMENSIONS
None
VECTORS
SGEN
Default .....:
Min .........:1
Max .........:
Rule ........:
Layer 1
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Layer 2
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
1563
Layer 3
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Layer 4
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Layer 5
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
1564
Matrix GEOMCK
MATRIX NAME
GEOMCK -- Information used to verify shot rollalong position.
DESCRIPTION
This matrix contains data to be displayed by QCVIEW to enable the user to visually identify spread
location errors.
DIMENSIONS
Dimension
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
SGEN
Default .....:
Min .........:0
Max .........:
Rule ........:
RSLN
Default .....:
Min .........:0
Max .........:
Rule ........:
1565
RMS
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
FCSN
Default .....:
Min .........:0
Max .........:
Rule ........:
SEE ALSO
Module GEOMCK.
AUTHOR
Created on March 8, 1996 by David
1566
Matrix GVLAWIN
MATRIX NAME
GVLAWIN - Time variant pick windows
DESCRIPTION
This matrix is used by the module GVLPICK to define a time variant pick window function. Linear
interpolation will be used for times between entered times.
DIMENSIONS
None
VECTORS
Time(ms)
Default .....:
Min .........:0
Max .........:
Min. Delta-T(ms)
This is the minimum difference in time between picked points.
Default .....:100
Min .........:0
Max .........:
Rule ........:
Window Size(ms)
This is the pick window size over which GVLPICK will search for a peak semblance.
Default .....:500
Min .........:0
Max .........:
1567
Rule ........:
AUTHOR
1568
Matrix GVLPREF
MATRIX NAME
GVLPREF - Time variant fairway and weight function
DESCRIPTION
Enter a time variant fairway function defined as a percentage of an reference guide function. For each time
point entered a minimum of two percentage points must be entered to define the minimum and maximum
velocity on the fairway over which to search for a peak semblance. Optionally a weight function may be
defined to weight for instance, velocities away from multiples. At a minimum at least one time must be
entered
To define a constant fairway at 90 and 110% of the reference function:
Time
% of Ref.
Weight
% of Ref.
Weight
90
1.0
110
1.0
To define a weighted fairway with a weight of .8 applied at the minimum velocity ramped up to 1.0 at the
reference function and down to .8 at the maximum velocity:
Time
% of Ref.
Weight
% of Ref.
Weight
% of Ref.
Weight
90
0.8
100
1.0
110
0.8
DIMENSIONS
None
VECTORS
Time(ms)
Enter the time for the weight and percentage of reference guide values entered. The default is to use the
previous time if a time cannot be defined in one row in the spreadsheet.
Default .....:"use prev."
Min .........:0
Max .........:
1569
% of Ref.
This is value will define velocity to use defined as a percentage of the reference function.
Default .....:"none"
Min .........:
Max .........:
Rule ........:
Weight
This is the weight to be applied to the semblance at the percent of reference and time defined.
Type ........:Float
Default .....:1.0
Min .........:0
Max .........:
Rule ........:
% of Ref.
Min .........:
Max .........:
Rule ........:
Weight
Type ........:Float
Default .....:1.0
Min .........:0
Max .........:
Rule ........:
% of Ref.
Min .........:
1570
Max .........:
Rule ........:
Weight
Type ........:Float
Default .....:1.0
Min .........:0
Max .........:
Rule ........:
% of Ref.
Min .........:
Max .........:
Rule ........:
Weight
Type ........:Float
Default .....:1.0
Min .........:0
Max .........:
Rule ........:
AUTHOR
1571
Matrix HMTH
MATRIX NAME
HMTH - Header math equations
DESCRIPTION
The HMTH matrix will define equations for module HMTH. All math is performed with floating point
arithmetic from left to right. Computed values will be rounded to integers if the header in the header
column is of type integer. Note that header words of type floating point can be created with module
ADDHDR. Sample values are saved as floating point. The following operations can be performed:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
Addition (+)
Subtraction (-)
Multiplication (*)
Division (/)
Raise to power (^)
Absolute value (abs(header))
Square root (sqrt(header))
Sine (sin(header))
Cosine (cos(header))
Tangent (tan(header))
Arc Sine (asin(header))
Arc Cosine (acos(header))
Arc Tangent (atan(header))
Renumber an ensemble(renum)
Ensemble Count of all traces in ensemble (count)
Modulo (mod(modulus))
Mean of all traces in ensemble (mean(header))
Each field in an "Operation" column in the matrix must specify an operator and a value. If no operator is
specified, "=" is implied. For example, to accumulate 5, the operation would be specified as +5. Values
can be either integer numbers, trace header locations or trace sample locations. Trace header locations can
be specified by name or by hdr(n) where n is the GCI index into the trace header. Trace sample locations
can be specified by samp(n) where n is the index of the time sample in the trace. The sample index is the
sample time/sample interval +1. Angles for the trig functions are in degrees.
Example usage:
Header Operation Operation Operation Operation
---------------------------------------------OIDN
OIDN
-3
To subtract 3 from all OLINs.
hdr(4) hdr(4)
-1
*2
+1
To make the FCSNs odd.
TRID
1
To make all traces live.
1572
DIST
abs(DIST)
To make offsets positive.

Compute source/receiver azimuth
To compute delta X - HDR(88) is float
To compute slope - ang is float
To compute azimuth - azim in integer
To put sample at time 400ms in header
To create ensemble trace numbers
hdr(88)
ang
azim
tim1
tim1
gx
-sx
gy
-sy
atan(ang)
samp(101)
renum
tim1
tim1
count
mod(180)
To put number traces in ensemble in header

To put remainder of tim1/180 in header
tim1
mean(DIST)
To put the mean of all DIST headers

in this ensemble in header
/hdr(88)
DIMENSIONS
None
VECTORS
Header
Trace header location to place the result into. This may be a GCI header name or a GCI index with hdr(n)
where n is the index into the header.
Default .....:
Rule ........:
Operation
Mathematical operation to perform. Usually this is a number or header location.
Default .....:"nop"
Rule ........:
Operation
Default .....:"nop"
Rule ........:
1573
Operation
Default .....:"nop"
Rule ........:
Operation
Default .....:"nop"
Rule ........:
Operation
Default .....:"nop"
Rule ........:
Operation
Default .....:"nop"
Rule ........:
Operation
Default .....:"nop"
Rule ........:
Operation
1574
Default .....:"nop"
Rule ........:
Operation
Default .....:"nop"
Rule ........:
SEE ALSO
Module HMTH, Data type GCI.
AUTHOR
Created on March 2, 1993 by Bill
1575
Matrix HORIZON
MATRIX NAME
HORIZON
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Time (MS)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1576
Matrix HORIZON3D
MATRIX NAME
HORIZON3D -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:999999
Secondary
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
Third
Default .....:
Min .........:
Max .........:
Rule ........:
Depth(Meters/Feet)
Default .....:
Min .........:
Max .........:
Rule ........:
1577
AUTHOR
Created on Sept. 29, 2010 by David Dunbar
1578
Matrix INTVEL
MATRIX NAME
INTVEL -- Interval velocity
DESCRIPTION
INTVEL matrix type contains time variant interval velocity information.
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Velocity
Default .....:
Min .........:1000
Max .........:99999
1579
Rule ........:
AUTHOR
1580
Matrix IREFVEL
MATRIX NAME
IREFVEL -
DESCRIPTION
DIMENSIONS
None
VECTORS
SSPN
Default .....:
Min .........:1
Max .........:
Rule ........:
V0
Default .....:
Min .........:0
Max .........:
Rule ........:
V1
Default .....:
Min .........:0
Max .........:
Rule ........:
1581
V2
Default .....:
Min .........:0
Max .........:
Rule ........:
V3
Default .....:
Min .........:0
Max .........:
Rule ........:
V4
Default .....:
Min .........:0
Max .........:
Rule ........:
V5
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
1582
Matrix ISOVBINS
MATRIX NAME
ISOVBINS -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start bin
Default .....:
Min .........:0
Max .........:
Rule ........:
Last bin
Default .....:"Start bin"
Min .........:0
Max .........:
Rule ........:
Increment
Default .....:1
Min .........:1
Max .........:
Rule ........:
1583
AUTHOR
1584
Matrix ISOVHORS
MATRIX NAME
ISOVHORS - specify the horizons to plot
DESCRIPTION
Use this matrix to specify the interpreted horizon indexs to plot for the ISOV module.
DIMENSIONS
None
VECTORS
Horizon index
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
Created on Oct. 8, 1998 by Bill
1585
Matrix ISOVLINS
MATRIX NAME
ISOVLINS -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start line
Default .....:
Min .........:0
Max .........:
Rule ........:
Last line
Default .....:"Start line"
Min .........:0
Max .........:
Rule ........:
Increment
Default .....:1
Min .........:1
Max .........:
Rule ........:
1586
AUTHOR
1587
Matrix ISOVTIMS
MATRIX NAME
ISOVTIMS -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start time
Default .....:
Min .........:0
Max .........:
Rule ........:
Last time
Default .....:"Start time"
Min .........:0
Max .........:
Rule ........:
Increment
Default .....:500
Min .........:1
Max .........:
Rule ........:
1588
AUTHOR
1589
Matrix KFIL
MATRIX NAME
KFIL -- Time variant high cut k filter design matrix
DESCRIPTION
This matrix is used by the module KFIL.
DIMENSIONS
None
VECTORS
1000% point
Default .....:
Min .........:0
Max .........:50
Rule ........:
0% point
Default .....:
Min .........:0
Max .........:50
Rule ........:
Start Header
Use this header to add a time horizon to all of the start application times. Available strings are NONE,
TIM1, and TIM2.
Default .....:NONE
Rule ........:
1590
End Header
Use this header to add a time horizon to all of the end application times. Available strings are NONE,
TIM1, and TIM2.
Default .....:NONE
Rule ........:
SEE ALSO
Module KFIL.
AUTHOR
1591
Matrix LASHEADER
MATRIX NAME
LASHEADER -
DESCRIPTION
DIMENSIONS
None
VECTORS
LAS header
Default .....:
Rule ........:
AUTHOR
Created on Aug 15, 2001 by Jensen
1592
Matrix LCKF
MATRIX NAME
LCKF -- Time variant low cut k filter design matrix
DESCRIPTION
This matrix is used by the module LCKF.
DIMENSIONS
None
VECTORS
0% point
Default .....:
Min .........:0
Max .........:50
Rule ........:
100% point
Default .....:
Min .........:0
Max .........:50
Rule ........:
Start Header
Use this header to add a time horizon to all of the start application times. Available strings are NONE,
TIM1, and TIM2.
Default .....:NONE
Rule ........:
1593
End Header
Use this header to add a time horizon to all of the end application times. Available strings are NONE,
TIM1, and TIM2.
Default .....:NONE
Rule ........:
SEE ALSO
Module LCKF.
AUTHOR
1594
Matrix LINAME
MATRIX NAME
LINAME - Custom line number for module LINENAME
DESCRIPTION
Use this matrix to enter start and end trace header values for a user specified line name. Example usage is:
Start
End
Line name
------------------------1
100
line1
101
200
line2
DIMENSIONS
None
VECTORS
Start
Enter the starting trace header value for the given line name.
Default......:
Min..........:
Max..........:
Rule.........:
End
Enter the ending trace header value for the given line name.
Default......:
Min..........:
Max..........:
Rule.........:
1595
Line name
This line name will be applied to all traces between the given start and end trace header values.
Type.........:String
Default......:
Rule.........:
AUTHOR
Created on Fri May 14 17:54:01 1999 by bill
1596
Matrix LINES
MATRIX NAME
LINES -
DESCRIPTION
DIMENSIONS
None
VECTORS
Line name
Default .....:
Rule ........:
AUTHOR
1597
Matrix LMOVEL
MATRIX NAME
LMOVEL -
DESCRIPTION
DIMENSIONS
None
VECTORS
Primary Value
Default .....:
Min .........:
Max .........:
Rule ........:
Secondary Value
Default .....:
Min .........:
Max .........:
Rule ........:
Velocity
Default .....:
Min .........:
Max .........:
Rule ........:
1598
AUTHOR
Created on Nov. 20, 2007 by JS
1599
Matrix MARINEGEOM
MATRIX NAME
MARINEGEOM - Define 2-D marine geometry for a set of lines
DESCRIPTION
This matrix is used by the module MARINE module to define the marine 2-D geometry for each defined
line.
DIMENSIONS
None
VECTORS
Line
To input additional information for this line that cannot fit on a single row, leave this field blank or with
the same name as the previous row. Example:
Line
1234
FirstID
1
Last ID
105
First S.P.
101
Last S.P.
200
1235
99
200
101
Default .....:"Previous"
Rule ........:
First ID
Default .....:"NONE"
Min .........:
Max .........:
Rule ........:
Last ID
This value can be less than the first ID for decreasing IDs.
1600
Skipped IDs Skipped S.P.s

10,20-21
50,60
150
Reel #s
20001
20002
Min .........:
Max .........:
Rule ........:
First S.P.
Min .........:
Max .........:
Rule ........:
Last S.P.
This value can be less than the first shotpoint for decreasing shotpoints.
Min .........:
Max .........:
Rule ........:
Skipped IDs
Enter comma separated IDs or a dash for a range of numbers. For example, 1,4,5-9 expands to the
numbers 1,4,5,6,7,8,9.
Rule ........:
Skipped S.P.s
Enter comma separated shotpoints or a dash for a range of numbers. For example, 1,4,5-9 expands to the
numbers 1,4,5,6,7,8,9.
Rule ........:
1601
Reel #s
Enter comma separated reel numbers or a dash for a range of numbers. For example, 1,4,5-9 expands to
the numbers 1,4,5,6,7,8,9. Comma separated values may include alphabetic characters [A-Z].
Rule ........:
AUTHOR
Created on Oct. 31, 1995 by Bill
1602
Matrix MATCH
MATRIX NAME
MATCH
DESCRIPTION
This is used by the MATCH module.
DIMENSIONS
None
VECTORS
Input
This is the value of the input header. It must be in ascending order.
Type ........:Float
Default .....:
Min .........:
Max .........:
Output
This is the value to be put in the output header.
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on June 16, 2004 by David Dunbar
1603
Matrix MATCH2
MATRIX NAME
MATCH2
DESCRIPTION
This is used by the MATCH2 module.
DIMENSIONS
None
VECTORS
Input1
This is the value of one input header. It must be in ascending order.
Type ........: Float
Default .....:
Min .........:
Max .........:
Input2
This is the value of the other input header.
Default .....:
Min .........:
Max .........:
Rule ........:
Output1
This is the value to be put in one output header.
1604

Default .....:
Min .........:
Max .........:
Rule ........:
Output2
This is the value to be put in the other output header.
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on June 16, 2004 by David Dunbar
1605
Matrix MIDPOINT
MATRIX NAME
MIDPOINT - Define corner coordinates for a 2-D crooked midpoint line.
DESCRIPTION
Use this matrix to define the corner points for a crooked midpoint line. This matrix is used by the module
STATION. The first defined point will correspond to the first midpoint bin. The last point will correspond
to the last midpoint bin. A minimum of two points must be defined.
DIMENSIONS
None
VECTORS
X coord.
Default .....:
Min .........:
Max .........:
Rule ........:
Y coord.
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Aug. 19, 1997 by Bill
1606
Matrix MIX3DWGT
MATRIX NAME
MIX3DWGT - Weight table for MIX3D
DESCRIPTION
Enter a weight to apply for each ensemble and and trace within an ensemble for the module MIX3D. The
Row numbers are the traces within the ensemble. If we are performing a 3x3 mix on a inline sorted (3-D
X-bin stack) data set, the following could be coded:
MLIN-1
MLIN-2
MLIN-3
----------------------------------------------MBIN-1
1
1
1
MBIN-2
1
2
1
MBIN-3
1
1
1
DIMENSIONS
None
VECTORS
Ensemble 1
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
Ensemble 2
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
1607
Ensemble 3
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
Ensemble 4
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
Ensemble 5
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
Ensemble 6
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
Ensemble 7
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
1608
Ensemble 8
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
Ensemble 9
Type ........:Float
Default .....:1
Min .........:
Max .........:
Rule ........:
AUTHOR
1609
Matrix MPISNODES
MATRIX NAME
MPISNODES - Node list
DESCRIPTION
This matrix defines a subset of the node list to use.
DIMENSIONS
None
VECTORS
CPU index
Default .....:
Min .........:
Max .........:99999
Rule ........:
# CPUs
Default .....:All
Min .........:
Max .........:99999
Rule ........:
AUTHOR
Created on Oct. 21, 2003 by David
1610
Matrix MULPPER
MATRIX NAME
MULPPER -- MULP percentage function
DESCRIPTION
This matrix is used by the MULP module to apply a percentage function to input velocities.
DIMENSIONS
Primary
The primary key can be either "MLIN" or "Water bottom time". Water bottom times should be entered in
ms.
Min .........:
Max .........:
Max # SP ....:99999
Secondary
The secondary key can be either "MBIN" for "NONE". For "NONE" enter any value.
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:
1611
Percentage
All points between defined times will be linearly interpolated. Values not defined at time zero or at the
maximum time will use the closest defined percentage.
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
SEE ALSO
Module MULP.
AUTHOR
1612
Matrix MUTE
MATRIX NAME
MUTE -
DESCRIPTION
This matrix used by the MUTE module. Module MUTE will zero the data from the start time to the end
time.
DIMENSIONS
Primary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Start(ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
1613
End(ms)
Default .....:
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module MUTE.
AUTHOR
1614
Matrix MUTECONT
MATRIX NAME
MUTECONT -- Specify a contour type mute
DESCRIPTION
This matrix is used by the MUTE program to create a contour type mute. The primary and secondary
values are used to define the polygon of the contour at the specified time value. The last point in the
polygon will be connected to the first point. Contour lines cannot cross over onto another contour line. The
can however fall on the same point.
DIMENSIONS
Time(ms)
This is the contour line value.
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Primary
This is the primary header id point
Default .....:
Min .........:
Max .........:
Rule ........:
Secondary
This is the secondary header id point
Default .....:
Min .........:
1615
Max .........:
Rule ........:
SEE ALSO
Module MUTE.
AUTHOR
1616
Matrix MXLINE3D
MATRIX NAME
MXLINE3D - Define a line to extract for module LINE3D using midpoints
DESCRIPTION
Use this matrix to define the line(s) to extract for module LINE3D. Enter a MBIN and MLIN value for
each endpoint and corner within the line to extract.
DIMENSIONS
Output line
This is used to define the line number. This number will be placed in the trace header named MLIN.
Multiple lines can be extracted from the 3-D volume.
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
MBIN
Default .....:
Min .........:
Max .........:
Rule ........:
MLIN
Default .....:
Min .........:
Max .........:
Rule ........:
1617
AUTHOR
Created on Mar. 27, 1995 by Bill
1618
Matrix MXLINE3DXY
MATRIX NAME
MXLINE3DXY - Define a line to extract for module LINE3D using coordinates
DESCRIPTION
Use this matrix to define the line(s) to extract for the module LINE3D. Enter an X and Y coordinate for
each endpoint and corner within the line to extract.
DIMENSIONS
Output line
This is used to define the line number. This number will be placed in the trace header named MLIN.
Multiple lines can be extracted from the 3-D volume.
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
X Coordinate
Default .....:
Min .........:
Max .........:
Rule ........:
Y Coordinate
Default .....:
Min .........:
Max .........:
Rule ........:
1619
AUTHOR
Created on Mar 9, 2001 by Bill Starr
1620
Matrix NMOMUTE
MATRIX NAME
NMOMUTE -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:999999
Secondary
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
Offset
Default .....:
Min .........:0
Max .........:
Rule ........:
Time(ms)
Default .....:
Min .........:
Max .........:
Rule ........:
1621
AUTHOR
1622
Matrix NOTCHFIL
MATRIX NAME
NOTCHFIL -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start Reject Hz
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
End Reject Hz
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Bandwidth Hz
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
1623
Floor %
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
Created on Jul 10, 2002 by Steve Jensen
1624
Matrix OFFBDIST
MATRIX NAME
OFFBDIST
DESCRIPTION
This matrix allows variable offbdist values.
DIMENSIONS
None
VECTORS
Offset (DMODIST)
Default .....:
Min .........:
Max .........:
Rule ........:
Maxbdist (dist units)

Type ........:Float
Default .....:All
Min .........:1
Max .........:
Rule ........:
AUTHOR
Created on June 17, 2011 by David
1625
Matrix OMIT
MATRIX NAME
OMIT -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:100000
VECTORS
Secondary
Default .....:"use prev."
Min .........:
Max .........:
Rule ........:
Ter. 1
Min .........:
Max .........:
Rule ........:
Ter. 2
Min .........:
Max .........:
1626
Rule ........:
Ter. 3
Min .........:
Max .........:
Rule ........:
Ter. 4
Min .........:
Max .........:
Rule ........:
Ter. 5
Min .........:
Max .........:
Rule ........:
Ter. 6
Min .........:
Max .........:
Rule ........:
Ter. 7
Min .........:
Max .........:
Rule ........:
1627
Ter. 8
Min .........:
Max .........:
Rule ........:
Ter. 9
Min .........:
Max .........:
Rule ........:
AUTHOR
1628
Matrix OPTDCN
MATRIX NAME
OPTDCN -
DESCRIPTION
DIMENSIONS
None
VECTORS
Lag (ms)
The maximum lag value is used to compute the correlation traces. Diagnostic plots generated by the
OPTDCNPL module help in determining this maximum lag value.
Default .....:260
Min .........:
Max .........:
Rule ........:
Oper (ms)
Note larger the deconvolution operator, the more effective is deconvolution in attaining the desired
bandwidth. However, there is a trade-off. Large operator length may adversely affect the relative
amplitude relationship of seismic events if they are not far apart. To avoid this effect, operator length
should be comparable to the length of the seismic pulse.
Default .....:100
Min .........:
Max .........:
Rule ........:
1629
Freq1(Hz)
This parameter should be chosen from the plot of the signal-to-noise ratio spectra generated by
theOPTDCNPL module.
Type ........:Float
Default .....:0.
Min .........:
Max .........:
Rule ........:
Freq2(Hz)
theOPTDCNPL module.
Type ........:Float
Default .....:5.
Min .........:
Max .........:
Rule ........:
Freq3(Hz)
theOPTDCNPL module.
Type ........:Float
Default .....:50.
Min .........:
Max .........:
Rule ........:
1630
Freq4(Hz)
theOPTDCNPL module.
Type ........:Float
Default .....:70.
Min .........:
Max .........:
Rule ........:
Start Header
Default .....:NONE
Rule ........:
End Header
Default .....:NONE
Rule ........:
AUTHOR
Created on Aug 7, 1996 by Sengupta
1631
Matrix OPTDCNP1
MATRIX NAME
OPTDCNP1 - Matrix for module OPTDCNPL
DESCRIPTION
This matrix is presently used by the moduleOPTDCNPL to describe the maximum lags in time gate
windows
DIMENSIONS
None
VECTORS
Maximum Correlation Lag (ms)
The maximum lags to be used used in calculating the auto and cross-correlation traces. These lags should
be such that no multiples or non-primary events are included within the auto or cross-correlation traces.
Roughly, these lags should be the length of the seismic pulse.
Default .....:100
Min .........:48
Max .........:
Rule ........:
Start Header
Default .....:NONE
Rule ........:
End Header
Default .....:NONE
Rule ........:
1632
AUTHOR
Created on Apr 26, 1996 by Sengupta
1633
Matrix PATREC
MATRIX NAME
PATREC -- Pattern by receiver location
DESCRIPTION
This matrix will define a pattern by receiver numbers for each channel number. The row number
corresponds to the channel number. The receiver coordinates or grid layout must have been defined with
module STATION prior to running SOURCE. DESCRIPTION
DIMENSIONS
Pattern #
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Receiver bin
Enter the receiver bin number for each channel number.
Default .....:"Dead FCSN"
Min .........:
Max .........:
Rule ........:
Receiver line
Enter the receiver line number for each channel number.
Default .....:1
Min .........:
Max .........:
Rule ........:
1634
SEE ALSO
Module SOURCE, Module STATION, Matrix SRCXYREC2, Matrix SRCRECREC2.
AUTHOR
1635
Matrix PATTERN
MATRIX NAME
PATTERN -- Pattern by distance from source
DESCRIPTION
This matrix will define a pattern by the distance from the shot to each channel number. The row number
corresponds to the channel number. Distances will be negative in the negative direction of the line and will
be positive in the positive direction of the line.
DIMENSIONS
Pattern #
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Delta-X
Enter the X direction distance from the source to the channel number. For a receiver offset to the east enter
a positive distance. For a receiver offset to the west enter a negative distance. Leave blank to make the
trace a dead channel.
Type ........:Float
Min .........:
Max .........:
Rule ........:
Delta-Y
Enter the Y direction distance from the source to the channel number. For a receiver offset to the north
enter a positive distance. For a receiver offset to the south enter a negative distance.
Type ........:Float
Default .....:0
Min .........:
1636
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Matrix SOURCE, Matrix SRCRECXY2.
AUTHOR
1637
Matrix PATTERNM
MATRIX NAME
PATTERNM -- Pattern by distance from source
DESCRIPTION
This matrix will define a pattern by the distance from the shot to each channel number and the receiver
depth for marine data. The row number corresponds to the channel number. Distances will be negative in
the negative direction of the line and will be positive in the positive direction of the line.
DIMENSIONS
Pattern #
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Delta-X
Enter the X direction distance from the source to the channel number. For a receiver offset to the east enter
a positive distance. For a receiver offset to the west enter a negative distance. Leave blank to make the
trace a dead channel.
Type ........:Float
Min .........:
Max .........:
Rule ........:
Delta-Y
Enter the Y direction distance from the source to the channel number. For a receiver offset to the north
enter a positive distance. For a receiver offset to the south enter a negative distance.
Type ........:Float
Default .....:0
Min .........:
1638
Max .........:
Rule ........:
Rec-Dep
Enter the Z direction distance from the surface to the receiver at this channel number.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module MSOURCE, Matrix SOURCEM,
AUTHOR
Created on May 14, 1993 by JohnS
1639
Matrix PLOTENTRY
MATRIX NAME
PLOTENTRY -
DESCRIPTION
DIMENSIONS
None
VECTORS
First column
Default .....:
Rule ........:
Second column
Default .....:
Rule ........:
AUTHOR
Created on Apr 17, 1995 by Bill
1640
Matrix PLOTLIST
MATRIX NAME
PLOTLIST -
DESCRIPTION
DIMENSIONS
None
VECTORS
Values
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
AUTHOR
1641
Matrix PLOTLT
MATRIX NAME
PLOTLT -
DESCRIPTION
DIMENSIONS
None
VECTORS
SP
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Line
Default .....:
Rule ........:
SP
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Line
Default .....:
Rule ........:
1642
AUTHOR
1643
Matrix PLOTLTCUS
MATRIX NAME
PLOTLTCUS -
DESCRIPTION
DIMENSIONS
None
VECTORS
Key (SDPN pr MLIN)
Default .....:
Min .........:
Max .........:
Rule ........:
SP
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Line
Default .....:
Rule ........:
1644
AUTHOR
1645
Matrix PLOTNOTETEXT
MATRIX NAME
PLOTNOTETEXT -
DESCRIPTION
DIMENSIONS
None
VECTORS
Key(SDPN or MLIN)
Default .....:""
Min .........:
Max .........:
Rule ........:
Text
Default .....:""
Rule ........:
AUTHOR
1646
Matrix PLOTPRF
MATRIX NAME
PLOTPRF -
DESCRIPTION
DIMENSIONS
None
VECTORS
Key1
Default .....:
Min .........:
Max .........:
Rule ........:
key2
Default .....:
Min .........:
Max .........:
Rule ........:
Value
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
1647
AUTHOR
1648
Matrix PLOTSINGLE
MATRIX NAME
PLOTSINGLE -
DESCRIPTION
DIMENSIONS
None
VECTORS
Information
Default .....:
Rule ........:
AUTHOR
1649
Matrix PLOTSPMX
MATRIX NAME
PLOTSPMX -
DESCRIPTION
DIMENSIONS
None
VECTORS
key(SDPN or MLIN)
Default .....:
Min .........:
Max .........:
Rule ........:
SP Value
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1650
Matrix PLOTSYMBOLS
MATRIX NAME
PLOTSYMBOLS -
DESCRIPTION
DIMENSIONS
None
VECTORS
Key(SDPN or MLIN)
Type .....:Integer
Default ..:
Min ......:
Max ......:
Rule .....:
Code
Type .....:Integer
Default ..:
Min ......:1
Max ......:13
1 ........:Location
2 ........:Dry hole
3 ........:Abandoned well
4 ........:Shut in well
5 ........:Dry hole - oil shows
6 ........:Dry hole - gas shows
7 ........:Dry hole - oil & gas shows
8 ........:Oil well
9 ........:Gas well
10 .......:Oil & gas well
11 .......:Location for directional or deviated well
12 .......:Location rig
13 .......:Offshore platform
1651
Rule .....:
Line1
Type .....:String
Default ..:""
Rule .....:
Line2
Type .....:String
Default ..:""
Rule .....:
AUTHOR
1652
Matrix PLOTTIC
MATRIX NAME
PLOTTIC -
DESCRIPTION
DIMENSIONS
None
VECTORS
Tic point (SDPN or MLIN)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1653
Matrix PLOTTRIP
MATRIX NAME
PLOTTRIP -
DESCRIPTION
DIMENSIONS
None
VECTORS
Sub title
Default .....:
Rule ........:
First column
Default .....:
Rule ........:
Second column
Default .....:
Rule ........:
AUTHOR
1654
Matrix PSMQC
MATRIX NAME
PSMQC -
DESCRIPTION
DIMENSIONS
None
VECTORS
Slice time(ms)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Aug. 4, 1997 by W. Wang
1655
Matrix PSROTANG
MATRIX NAME
PSROTANG -
Description
Dimensions
MLIN
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Attribute
Type ........:Float
Default .....:"No attribute"
Min .........:0
Max .........:
Rule ........:
AUTHOR
Created on Nov 10, 1999 by Claudio DAgosto
1656
Matrix PSROTANG1
MATRIX NAME
PSROTANG1 -
DESCRIPTION
This matrix is an "orphan". It is included in case the development module that used it is released.
DIMENSIONS
SLIN
Min .........:1
Max .........:
Max # SP ....:999999
SBIN
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Angle
Type ........:Float
Min .........:0
Max .........:
Rule ........:
1657
AUTHOR
1658
Matrix QCOMPF
MATRIX NAME
QCOMPF - Matrix for Fixed Q window description
DESCRIPTION
This matrix is used to describe a time variant but not spatially variant Q model. At least one and no more
than five constant Q windows may be entered. For each window (each row), a Q value, start time and
reference frequency may be entered. The start times must increase with increasing window number. Each
window ends at the start of the next window, or at the end of the data.
DIMENSIONS
None
VECTORS
Q value
Default .....:100
Min .........:1
Max .........:
Rule ........:
For each window, enter the Q factor. Large (in the 500-infinity range) Q will have little effect on the data,
while low Q (50-100) will act like a spiking deconvolution filter.
Start Time
Default .....:0
Min .........:0
Max .........:100000
Rule ........:
Enter the times at which each Q window starts. The start time is referenced to the zero time-reference
header (see QCOMP module help).
1659
Reference Freq
Default .....:60
Min .........:1
Max .........:
Rule ........:
The reference frequency is just used in scaling the stretching of frequencies within the program. A typical
choice is the maximum frequency in the data or the Nyquist frequency.
Go to QCOMP for module help
AUTHOR
Created on Aug. 22, 1995 by Barton
1660
Matrix QCOMPS
MATRIX NAME
QCOMPS -
DESCRIPTION
DIMENSIONS
Primary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Start-1 (ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
Start-2 (ms)
Default .....:0
Min .........:
Max .........:
1661
Rule ........:
Start-3 (ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
Start-4 (ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
Start-5 (ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
AUTHOR
1662
Matrix QCOMPV
MATRIX NAME
QCOMPV - Matrix for Q values in multiple windows
DESCRIPTION
This matrix is used to describe the Q values and reference frequencies for multiple windows. It is used for
a fully variable Q model, i.e., both time and space variant. At least one and no more than five constant Q
windows may be entered. For each window (each row), a Q value and reference frequency may be entered.
The start and end times of the windows or gates as a function of spatial position must be given in a
Windows2 matrix, labeled in the parameters as "Q start & end times".
DIMENSIONS
None
VECTORS
Q value
Default .....:100
Min .........:
Max .........:
Rule ........:
For each window, enter the Q factor. Large (in the 500-infinity range) Q will have little effect on the data,
while low Q (50-100) will act like a spiking deconvolution filter.
Reference Freq
Default .....:60
Min .........:
Max .........:
Rule ........:
The reference frequency is just used in scaling the stretching of frequencies within the program. A typical
choice is the maximum frequency in the data or the Nyquist frequency.
1663
Start Header
Rule ........:
A complex Q model may be best described as a set of times at various keys to get the general trend, to
which a header variable is added (perhaps a water bottom, uphole time, etc.) This header must be copied
into either the tim1 or tim2 headers. The tim1 and tim2 headers may also be used as a zero time-reference
header, (see QCOMP module help) so be aware of possible conflicts.
Go to QCOMP for module help
AUTHOR
1664
Matrix QCVELWIN
MATRIX NAME
QCVELWIN -
DESCRIPTION
DIMENSIONS
None
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Velocity
Default .....:
Min .........:0
Max .........:99999
Rule ........:
AUTHOR
Created on Sep 04, 2002 by Steve Jensen
1665
Matrix QMATRIX
Matrix Description
This matrix is presently used by the module AMPCOR to describe a time and space varying Q model for
Q-compensation. The estimate of Q-values within a time and space window could be obtained using the
module QDERIVE. The composition of this matrix is the same as the RMSVEL matrix which is used to
describe the time and space varying VNMO function. However, one would normally need five to six Q
values only, unlike ten to twenty values of VNMO, to describe the time variation part. Our suggestion is to
use Q-values over a two-way time window of at least 1000 milliseconds long.
Note that Q-value should generally be high (say, 10,000 - 20,000) for the water leg in marine data, low (50
- 100) for low-velocity weathered layer in land data, moderately low (100 - 500) for shallow and young
marine sediments, moderately high (500 - 1000) for deep and old marine or land sediments. For
hydrocarbon layers, especially gas sands, Q-values can be as low as 10 - 50. In general, Q-values should
be increasing with time (or, depth) as velocity values do.
Dimensions
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
Vectors
Time (ms)
Default .....:
Min .........:0
Max .........:99999
1666
Q-values
Default .....:
Min .........:0
Max .........:99999
Rule ........:
1667
Matrix QVALUES
MATRIX NAME
QVALUES -
DESCRIPTION
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Q Value
Default .....:
Min .........:0
Max .........:99999
Rule ........:
1668
AUTHOR
Created on Apr. 14, 2000 by Steve Jensen
1669
Matrix RADON
MATRIX NAME
RADON -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:99999
Secondary
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Zero-offset Time (ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Negative Start(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1670
Negative Taper(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Positive Start(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Positive Taper(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Apr 19, 1994
1671
Matrix RADON1
MATRIX NAME
RADON1 -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:99999
Secondary
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Zero-offset Time (ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
1Rule ........:
P1(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1672
P2(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
P3(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
P4(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR Larry Yost

Created on June 11, 2002
1673
Matrix RAS2GEO
MATRIX NAME
RAS2GEO -- Surface consistent geophone statics
DESCRIPTION
Matrix type RAS2GEO contains the surface-consistent geophone statics from module RAS2. The user
may edit the statics before running RAS3. The row number of spreadsheet is used as the geophone station
number.
DIMENSIONS
None
VECTORS
Geophone statics(samples)
Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
SEE ALSO
Matrix RAS2SRC,
AUTHOR
1674
Matrix RAS2SRC
MATRIX NAME
RAS2SRC -- Surface consistent source statics
DESCRIPTION
Matrix type RAS2SRC contains the surface-consistent source statics from module RAS2. The user may
edit the statics before running RAS3. The row number of spreadsheet is used as the source station
number.
DIMENSIONS
None
VECTORS
Source statics(samples)
Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
SEE ALSO
Matrix RAS2GEO,
AUTHOR
1675
Matrix RECMASK
MATRIX NAME
RECMASK -
DESCRIPTION
DIMENSIONS
None
VECTORS
Recmask
Default......:
Min..........:0
Max..........:
Rule.........:
AUTHOR
Created on Dec 06, 1999 by Jensen
1676
Matrix RECVGEOM
MATRIX NAME
RECVGEOM -
DESCRIPTION
DIMENSIONS
Ensemble #
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
sgen
Default .....:
Min .........:
Max .........:
Rule ........:
dist
Default .....:
Min .........:
Max .........:
Rule ........:
rsln
Default .....:
Min .........:
Max .........:
1677
Rule ........:
rsbn
Default .....:
Min .........:
Max .........:
Rule ........:
sx
Default .....:
Min .........:
Max .........:
Rule ........:
sy
Default .....:
Min .........:
Max .........:
Rule ........:
gx
Default .....:
Min .........:
Max .........:
Rule ........:
gy
Default .....:
Min .........:
Max .........:
Rule ........:
1678
eg
Default .....:
Min .........:
Max .........:
Rule ........:
fcsn
Default .....:
Min .........:
Max .........:
Rule ........:
sspn
Default .....:
Min .........:
Max .........:
Rule ........:
origDist
Default .....:
Min .........:
Max .........:
Rule ........:
id
Default .....:
Min .........:
Max .........:
Rule ........:
1679
offset
Default .....:
Min .........:
Max .........:
Rule ........:
Metadata
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1680
Matrix REELS
MATRIX NAME
REELS - Define reel numbers to be used for modules
DESCRIPTION
a Enter reel numbers that are to be used for the module attached to this data set. For SEG-Y data sets, the
reel number will be requested when needed. For input GCI data sets, this matrix can be used to override
the default action to get the input tape numbers from the database. For output GCI data sets, this matrix
can be used to override the default action to assign tapes from the seismic tape inventory package.
DIMENSIONS
None
VECTORS
Reel info
Default .....:
Rule ........:
AUTHOR
Created on Sep. 21, 1995 by Bill
1681
Matrix REGIONS
REGIONS This matrix is used by the NOPERMIT module to define data exclusion regions. A REGIONS
matrix may have multiple spreadsheets. Each spreadsheet in the matrix defines an individual region. Each
spreadsheet takes a coordinate pair in each row. This is limited to 100 pairs.
DIMENSIONS
Region
Min .........:
Max .........:
Max # SP ....:99999
Min .........:
VECTORS
X/BIN
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Y/LIN
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Halo Size
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1682
AUTHOR
Created on Jan 22, 2003 by Michael Beam
1683
Matrix REGIONST
REGIONST This matrix is used by the NOPERMIT module to define data exclusion regions. A
REGIONST matrix may have multiple spreadsheets. Each spreadsheet in the matrix defines an individual
region. Each spreadsheet takes a coordinate pair in each row. This is limited to 100 pairs.
DIMENSIONS
Region
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
X/BIN
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Y/LIN
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
Start Time
Default .....:
Min .........:
Max .........:
Rule ........:
1684
End Time
Default .....:
Min .........:
Max .........:
Rule ........:
Halo Size
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Jun 14, 2013 by David Dunbar.
1685
Matrix RFMT
MATRIX NAME
RFMT - Match GCI headers with other trace sequential header formats
DESCRIPTION
This matrix is used by the RFMT routine to match headers from other trace sequential format headers to a
GCI header.
DIMENSIONS
None
VECTORS
Header
This is the GCI header name. If this header is a coordinate, the value from the other trace sequential
header is multiplied by 10 before placing it int the GCI trace header. The coordinate scale factor in the
GCI trace header is set to -10 for proper scaling.
Default .....:
Rule ........:
Byte
This is the starting byte position in the header for the value to put into the GCI header.
Default .....:
Min .........:0
Max .........:
Rule ........:
# bytes
This is the number of bytes for the value to put into the GCI header.
Default .....:4
Min .........:1
1686
Max .........:
Rule ........:
Type
This is the type of the value to put into the GCI header. The allowable strings are INTEGER, BCD,
ASCII, EBCDIC, FLOAT, IBM, and DOUBLE. The FLOAT and IBM options are 4 byte floating point
numbers that will be truncated to an integer before placing it in the trace header. The FLOAT option is an
IEEE floating point number and the IBM option is an IBM floating point number. The DOUBLE option
is an 8 byte double precision IEEE number that will also be truncated to an integer. For coordinates,
floating point and double precision numbers will be scaled by ten before truncating the number. Only the
first letter for each option needs to be entered except for the IBM option which requires the first two
letters.
Default .....:INT
Rule ........:
Location
This is the header where to get the value to put into the GCI header. The allowable strings are
ATTACHED for the attached trace header and DETACHED for the detached trace header. Only the first
letter for each option needs to be entered.
Default .....:ATTACHED
Rule ........:
SEE ALSO
Module RFMT,
Data type GCI.
AUTHOR
Created on Sep. 21, 1995 by Bill
1687
Matrix RFMTSEGD
MATRIX NAME
RFMTSEGD -- Match GCI headers with SEG-D header
DESCRIPTION
This matrix is used by the RFMT routine to match headers from SEG-D headers to a GCI header.
DIMENSIONS
None
VECTORS
Header
This is the GCI header name. If this header is a coordinate, the value from the SEG-D header is multiplied
by 10 before placing it int the GCI trace header. The coordinate scale factor in the GCI trace header is set
to -10 for proper scaling.
Default .....:
Rule ........:
Byte
This is the starting byte position in the header for the value to put into the GCI header.
Default .....:
Min .........:0
Max .........:
Rule ........:
# bytes
This is the number of bytes for the value to put into the GCI header.
Default .....:4
Min .........:
Max .........:
1688
Rule ........:
Type
This is the type of the value to put into the GCI header. The allowable strings are INTEGER, BCD,
ASCII, EBCDIC, FLOAT, and IBM. The FLOAT and IBM options are 4 byte floating point numbers
that will be truncated to an integer before placing it in the trace header. The FLOAT option is an IEEE
floating point number and the IBM option is an IBM floating point number. For coordinates, floating
point numbers will be scaled by ten before truncating the number. Only the first letter for each option
needs to be entered except for the IBM option which requires the first two letters.
Default .....:INT
Rule ........:
SEE ALSO
Module RFMT,
Data type GCI.
AUTHOR
Created on Nov. 22, 1993 by Bill
1689
Matrix RMOD
MATRIX NAME
RMOD -
DESCRIPTION
DIMENSIONS
None
VECTORS
Offset
Default .....:
Min .........:0
Max .........:
Rule ........:
Time(ms)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Apr 08, 2004 by Steve Jensen
1690
Matrix RMSFCSN
MATRIX NAME
RMSFCSN -- RMS gain for each trace
DESCRIPTION
This matrix is used to represent the gain for each trace within a shot.
DIMENSIONS
SLIN
Min .........:1
Max .........:
Max # SP ....:999999
SBIN
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Amplitude
Type ........:Float
Default .....:"No amplitude"
Min .........:0
Max .........:
Rule ........:
1691
SEE ALSO
Module GNATTR,
Matrix RMSSSPN,
Matrix RMSFCSN.
AUTHOR
Created on Tue Jan. 4, 1994 by Bill
1692
Matrix RMSSSPN
MATRIX NAME
RMSSSPN -- RMS gain for each shot
DESCRIPTION
This matrix is used to represent the average gain within a shot.
DIMENSIONS
SLIN
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Amplitude
Type ........:Float
Default .....:"No amplitude"
Min .........:0
Max .........:
Rule ........:
SEE ALSO
Module GNATTR,
Matrix RMSSSPN,
Matrix RMSFCSN.
1693
AUTHOR
1694
Matrix RMSV3C
MATRIX NAME
RMSV3C -
DESCRIPTION
RMSV3C matrix type contains time variant RMS velocity and dip information. The dips in X and Y
directions are expressed in terms of the corresponding sine values of the angles.
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
1695
Velocity
Default .....:
Min .........:1000
Max .........:99999
Rule ........:
Sin(Dx)
Type ........:Float
Default .....:
Min .........:-90
Max .........:90
Rule ........:
Sin(Dy)
Type ........:Float
Default .....:
Min .........:-90
Max .........:90
Rule ........:
AUTHOR
Created on Jul 20, 1993
1696
Matrix RMSVEL
MATRIX NAME
RMSVEL -- RMS velocity
DESCRIPTION
RMSVEL matrix type contains time variant RMS velocity information. This matrix type is used by many
different modules.
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
1697
Velocity
Default .....:
Min .........:0
Max .........:99999
Rule ........:
AUTHOR
Created on Feb. 11, 1993
1698
Matrix SCDCN1
MATRIX NAME
SCDCN1 -
DESCRIPTION
DIMENSIONS
Primary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Start (ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
End (ms)
Default .....:"Trace length"
Min .........:
Max .........:
1699
Rule ........:
AUTHOR
1700
Matrix SCDECON1
MATRIX NAME
SCDECON1 -
DESCRIPTION
DIMENSIONS
Primary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Start (ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
End (ms)
Default .....:"Trace length"
Min .........:
Max .........:
1701
Rule ........:
AUTHOR
Created on Aug 11, 2004 by Steve Jensen
1702
Matrix SCLDB
MATRIX NAME
SCLDB - Time variant DB scaling
DESCRIPTION
Use this matrix to apply time variant scaling where the user enters time and db scale values. This matrix is
used by the SCALE module.
DIMENSIONS
None
VECTORS
Time(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Scalar(db)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Jan 8, 2001 by Bill Starr
1703
Matrix SCLSCL
MATRIX NAME
SCLSCL - Time variant percentage scaling
DESCRIPTION
Use this matrix to apply time variant scaling where the user enters time and percentage scale values. This
matrix is used by the SCALE module.
DIMENSIONS
None
VECTORS
Time(ms)
Type ........:Float
Default .....:
Min .........:
Max .........:
Scalar(%)
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1704
Matrix SCLWIN
MATRIX NAME
SCLWIN -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start(ms.)
Default .....:
Min .........:
Max .........:
End(ms.)
Default .....:
Min .........:
Max .........:
Center(ms.)
Type ........:Float
Default .....:"Computed"
Min .........:
Max .........:
1705
Ref. Mean
Type ........:Float
Default .....:2500.0
Min .........:0.001
Max .........:
Rule ........:
AUTHOR
1706
Matrix SDELAY
MATRIX NAME
SDELAY -
DESCRIPTION
DIMENSIONS
None
VECTORS
SSPN
Default .....:
Min .........:1
Max .........:
Rule ........:
Layer 1
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Layer 2
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
1707
Layer 3
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Layer 4
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Layer 5
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
1708
Matrix SEGYEBC
MATRIX NAME
SEGYEBC -- SEG-Y EBCDIC reel header input
DESCRIPTION
This matrix is used by SEGYWRIT to manually enter information into the EBCDIC reel header.
DIMENSIONS
None
VECTORS
Real header
Default .....:
Rule ........:
SEE ALSO
Module SEGYWRIT.
AUTHOR
Created on Oct 15, 1993 by Bill
1709
Matrix SEGYLINES
MATRIX NAME
SEGYLINES -
DESCRIPTION
DIMENSIONS
None
VECTORS
File numbers
Default......:
Min..........:
Max..........:
Rule.........:
AUTHOR
Created on Feb 07, 2001 by Jensen
1710
Matrix SEGYREMAP
MATRIX NAME
SEGYREMAP
DESCRIPTION
A trace header re-map option has been added to aid in transferring non-standard SEGY trace header values
to SeisUP trace headers. Modern SEGY files often contains additional information in the SEGY trace
header to support 3D data and geometry. The extended words are written to the empty SEGY trace header
bytes 181-240. The re-mappings are stored in a SeisUP matrix in the global database. Several common
re-mapping matrices are already build for you, including the SeisUP re-mappings. The re-map matrix is
defined as follows:
65.
Column 2: The SEGY word format, 4I, 2I, 1I, 4R, 8R, #A, and #C. These represent 4-byte integer (4I),
2-byte integer (2I), 1-byte integer (1I), 4-byte float (4R), 8-byte double (8R), ASCII string transfer (#A),
and ASCII string conversion (#C). The # with the A and C is a placeholder for the number of
NOTE: The 1I and #C formats are valid only in SEGYREAD.
MCX.
MCX 4R IEEE 181
LINE 8A 233
1711
DIMENSIONS
None
VECTORS
GCI Header
Default .....:
Rule ........:
Format (1I, 2I, 4I, 4R, 8R, #A, #C)

Default .....:
Rule ........:
Type (IEEE,IBM)
Default .....:IEEE
Rule ........:
Start Byte (1-240)

Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Jan 27, 1999 by Jensen
1712
Matrix SGN1
MATRIX NAME
SGN1 -
DESCRIPTION
DIMENSIONS
Primary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Start (Ms)
Default .....:0
Min .........:
Max .........:
Rule ........:
End (MS)
Default .....:"rec len"
Min .........:
Max .........:
1713
Rule ........:
AUTHOR
Created on Jan 29, 1993
1714
Matrix SGN2
MATRIX NAME
SGN2 -
DESCRIPTION
DIMENSIONS
MINOFF
Min .........:
Max .........:
Max # SP ....:1
MAXOFF
Min .........:
Max .........:
Max # SP ....:1
DELTOFF
Min .........:
Max .........:
Max # SP ....:1
VECTORS
Source gain (db)
Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
1715
Geophone gain (db)

Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
CMP gain (db)

Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
Offset gain (db)

Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
AUTHOR
Created on Mar 22, 1993
1716
Matrix SGNE
MATRIX NAME
SGNE -
DESCRIPTION
DIMENSIONS
MLIN
Min .........:0
Max .........:
Max # SP ....:999999
MBIN
Min .........:0
Max .........:
Max # SP ....:999999
Tertiary
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Gain
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1717
AUTHOR
Created on Sep 10, 2003 by Steve Jensen
1718
Matrix SMOOTHHORZ
MATRIX NAME
SMOOTHHORZ
DESCRIPTION
VECTORS
Start Horizon
Default .....:NONE
Rule ........:
End Horizon
Default .....:NONE
Rule ........:
Radius of lines
Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
Radius of bins
Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
1719
Radius of samples
Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
Smoothing degree
Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
SEE ALSO
Module VELSMTH.
AUTHOR
1720
Matrix SNR
MATRIX NAME
SNR
DESCRIPTION
DIMENSIONS
Primary
Default .....:
Min .........:
Max .........:
VECTORS
Secondary
Default .....:
Min .........:
Max .........:
Rule ........:
Start (mw)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1721
Matrix SOURCE
MATRIX NAME
SOURCE -- Source by coordinate and pattern by distance from source
DESCRIPTION
This matrix will define the geometry for the SOURCE program. The source location will be specified by x
and y coordinates. The pattern will be specified by the distance from the source to the channel.
DIMENSIONS
None
VECTORS
Id
This a unique ID for the shot. Usually the field file number.
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
This is the field shot point number corresponding to the Id.
Default .....:
Min .........:
Max .........:
Rule ........:
X coord.
Enter the X coordinate for the shot.
Default .....:
Min .........:
1722
Max .........:
Rule ........:
Y coord.
Enter the Y coordinate for the shot.
Default .....:0
Min .........:
Max .........:
Rule ........:
Pattern #
Default .....:
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Matrix PATTERN.
AUTHOR
1723
Matrix SOURCE2
MATRIX NAME
SOURCE2 -- Source by coordinate and pattern by distance from source.
DESCRIPTION
and y coordinates. The pattern will be specified by the distance from the source to the channel.
DIMENSIONS
None
VECTORS
Id
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
X coord.
Default .....:
Min .........:
1724
Max .........:
Rule ........:
Y coord.
Default .....:0
Min .........:
Max .........:
Rule ........:
Elevation
Enter the shot elevation. The default is to use the receiver elevation closest to the shot.
Type ........:Float
Default .....:"Relev"
Min .........:
Max .........:
Rule ........:
Depth
Enter the shot depth in feet or meters.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Uphole
Enter the uphole time in ms.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1725
Pattern #
Default .....:
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Matrix PATTERN.
AUTHOR
1726
Matrix SOURCEM
MATRIX NAME
SOURCEM -- Source by coordinate and pattern by distance from source with marine source elevation
data.
DESCRIPTION
This matrix will define the geometry for the MSOURCE program. The source location will be specified by
x and y and z coordinates. The pattern will be specified by the distance from the source to the channel.
DIMENSIONS
None
VECTORS
Id
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
X coord.
1727
Default .....:
Min .........:
Max .........:
Rule ........:
Y coord.
Default .....:0
Min .........:
Max .........:
Rule ........:
Sea Level
Enter sea level at the shot.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Gun Depth
Enter the depth of the source. Depths are positive down.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Water Depth
Enter the water depth at the source point. Depths are positive down.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1728
Pattern #
Default .....:
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module MSOURCE, Matrix PATTERNM.
AUTHOR
Created on May 14, 1993 by JohnS
1729
Matrix SRCDXOFF
MATRIX NAME
SRCDXOFF -- Source by distance from previous shot and pattern by offset.
DESCRIPTION
This matrix will define geometry for the source program using relative distances to traces. The receiver
bin spacing (geophone interval) must have been defined with module STATION prior to running
SOURCE. Examples using 48 channels per shot:
---------------> Positive direction of line--------------->
X = Shotpoint location
. = Channel number
XX = User entered value
Shot
Upline trc
Upline dst
Downline dst
-----------------------------------------------------------1
2
3
X
.
.
.
0
XX
1
X
2
.
3
.
4
.
48
.
47
.
46
.
-49
48
X
47
.
46
.
45
.
-48
6
.
47
.
48
.
48
XX
3
.
2
.
1
.
-1
XX
5
.
46
.
47
.
48
X
48
4
.
3
.
2
.
1
X
-1
3
.
24
.
25
.
26
. 24
XX
XX
6
.
25
.
24
.
23
. -25
XX
XX
XX
XX
XX
1730
. Gap Trace=6
Gap size=1
8
.
7
.
6
.
5
. Gap Trace=-7
Gap size=1
DIMENSIONS
None
VECTORS
Id
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
Delta X
This is the distance from the last shotpoint to the current shotpoint in the X direction (inline).
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1731
Perp dist
Enter the distance from the receiver line to the shot location location in the crossline direction. A positive
crossline offset is toward the north and a negative crossline offset is toward the south.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
--> trc
This is the upline trace. The absolute value of the upline near trace is the field channel sequence number
(FCSN) of the trace which lies nearest the shotpoint in the negative direction of the line, or which lies on
the shotpoint. Its sign is positive if the FCSNs increase in the positive direction of the line, but negative if
the FCSNs decrease in the positive direction Zero is regarded positive. This must be defined for the first
shot. Subsequent shots defaults to using the previous geometry.
Default .....:"previous"
Min .........:
Max .........:
Rule ........:
--> dist
This is the upline near trace distance. The distance from the shotpoint to the upline near trace.
Min .........:0
Max .........:
Rule ........:
<-- dist
Downline near trace distance. The downline near trace is the field channel sequence number of the trace
which lies nearest the shotpoint in the positive direction of the line. The downline near trace distance is the
distance from the shotpoint to the down line near trace.
Min .........:0
Max .........:
Rule ........:
1732
Gap trc
Gap near trace. This is coded when there is a gap in the spread and this gap does not contain the shotpoint.
(Of course, there may be a shot gap as well). The absolute value of the gap near trace is the field channel
sequence number of the trace which lies nearest the gap in the negative direction of the line. Its sign must
be coded the same as the Upline trace.
Default .....:"no gap"
Min .........:1
Max .........:
Rule ........:
Gap size
The number of skipped geophones in the gap.
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION.
AUTHOR
1733
Matrix SRCDXOFF2
MATRIX NAME
SRCDXOFF2 -- Source by distance from previous shot and pattern by offset.
DESCRIPTION
This matrix will define geometry for the source program using relative distances to traces. The receiver
bin spacing (geophone interval) must have been defined with module STATION prior to running
SOURCE. Examples using 48 channels per shot:
---------------> Positive direction of line--------------->
X = Shotpoint location
. = Channel number
XX = User entered value
Shot
Upline trc
Upline dst
Downline dst
-----------------------------------------------------------1
2
3
X
.
.
.
0
XX
1
X
2
.
3
.
4
.
48
.
47
.
46
.
-49
48
X
47
.
46
.
45
.
-48
46
.
47
.
48
.
48
XX
3
.
2
.
1
.
-1
XX
45
.
46
.
47
.
48
X
48
4
.
3
.
2
.
1
X
-1
23
.
24
.
25
.
26
. 24
XX
XX
26
.
25
.
24
.
23
. -25
XX
XX
XX
XX
XX
1734
. Gap Trace=6
Gap size=1
8
.
7
.
6
.
5
. Gap Trace=-7
Gap size=1
DIMENSIONS
None
VECTORS
Id
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
Delta X
This is the distance from the last shotpoint to the current shotpoint in the X direction (inline).
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1735
Perp dist
Enter the distance from the receiver line to the shot location location in the crossline direction. A positive
crossline offset is toward the north and a negative crossline offset is toward the south.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Elevation
Type ........:Float
Min .........:
Max .........:
Rule ........:
Depth
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Uphole
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
--> trc
This is the upline trace. The absolute value of the upline near trace is the field channel sequence number
(FCSN) of the trace which lies nearest the shotpoint in the negative direction of the line, or which lies on
the shotpoint. Its sign is positive if the FCSNs increase in the positive direction of the line, but negative if
the FCSNs decrease in the positive direction Zero is regarded positive. This must be defined for the first
1736
shot. Subsequent shots defaults to using the previous geometry.

Default .....:"previous"
Min .........:
Max .........:
Rule ........:
--> dist
This is the upline near trace distance. The distance from the shotpoint to the upline near trace.
Min .........:0
Max .........:
Rule ........:
<-- dist
Downline near trace distance. The downline near trace is the field channel sequence number of the trace
which lies nearest the shotpoint in the positive direction of the line. The downline near trace distance is the
distance from the shotpoint to the down line near trace.
Min .........:0
Max .........:
Rule ........:
Gap trc
Gap near trace. This is coded when there is a gap in the spread and this gap does not contain the shotpoint.
(Of course, there may be a shot gap as well). The absolute value of the gap near trace is the field channel
sequence number of the trace which lies nearest the gap in the negative direction of the line. Its sign must
be coded the same as the Upline trace.
Default .....:"no gap"
Min .........:1
Max .........:
Rule ........:
1737
Gap size
The number of skipped geophones in the gap.
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION.
AUTHOR
1738
Matrix SRCMXLST
MATRIX NAME
SRCMXLST - List of source matrices
DESCRIPTION
Source matrices list here can will be processed in order by module SOURCE.
DIMENSIONS
None
VECTORS
Source Matrix Name
Default .....:
Rule ........:
1739
Matrix SRCRECREC
MATRIX NAME
SRCRECREC -- Source by receiver and pattern by receiver location.
DESCRIPTION
This matrix will define the geometry for the SOURCE program. The source location will be specified by
receiver numbers and a distance from the receiver to the shot. The pattern will be specified by receiver
number. The receiver coordinates or grid layout must have been defined with module STATION prior to
running SOURCE. For receivers not defined in the STATION program, GEOM will automatically kill the
defined channel. For an example on how to define the pattern, see "Source by coordinate and pattern by
receiver location".
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
This is the shot point number corresponding to the Id.
Default .....:
Min .........:
Max .........:
Rule ........:
1740
Rec bin
Enter the receiver bin number closest to the shot.
Default .....:
Min .........:
Max .........:
Rule ........:
Rec line
Enter the receiver line number closest to the shot.
Default .....:1
Min .........:
Max .........:
Rule ........:
Skid
Enter the distance from the defined receiver location to the shot location in the inline direction. A positive
inline offset is toward the next receiver bin and a negative inline offset is toward the previous numbered
receiver bin.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Perp dist
Enter the distance from the defined receiver location to the shot location in the crossline direction. A
positive inline offset is toward the next receiver line and a negative crossline offset is toward the previous
receiver line.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1741
Pattern
Enter the pattern number.
Default .....:
Min .........:1
Max .........:
Rule ........:
Bin @FCSN1
Enter the receiver bin number for the first live channel number closest to channel number one. Since
channel number one on the pattern can be a dead channel, enter the a bin corresponding to the first
non-blank channel. The default will be to bin specified in the pattern.
Default .....:"use pat"
Min .........:
Max .........:
Rule ........:
Lin @FCSN1
Enter the receiver line number for the first live channel number closest to channel number one. The default
will be to line specified in the pattern.
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION, Matrix PATREC, Matrix SRCXYREC2.
AUTHOR
1742
Matrix SRCRECREC2
MATRIX NAME
SRCRECREC2 -- Source by receiver and pattern by receiver location.
DESCRIPTION
receiver numbers and a distance from the receiver to the shot. The pattern will be specified by receiver
number. The receiver coordinates or grid layout must have been defined with module STATION prior to
running SOURCE. For receivers not defined in the STATION program, GEOM will automatically kill the
defined channel. For an example on how to define the pattern, see "Source by coordinate and pattern by
receiver location".
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
1743
Rec bin
Default .....:
Min .........:
Max .........:
Rule ........:
Rec line
Default .....:1
Min .........:
Max .........:
Rule ........:
Skid
receiver bin.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Perp dist
receiver line.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1744
Elevation
Type ........:Float
Min .........:
Max .........:
Rule ........:
Depth
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Uphole
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Pattern
Default .....:
Min .........:1
Max .........:
Rule ........:
Bin @FCSN1
1745
Min .........:
Max .........:
Rule ........:
Lin @FCSN1
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION, Matrix PATREC, Matrix SRCXYREC2.
AUTHOR
1746
Matrix SRCRECSPD
MATRIX NAME
SRCRECSPD -- Source by receiver and pattern by spread
DESCRIPTION
This matrix will define the geometry for the SOURCE program. The source location will be specified by a
receiver bin number and a distance from the receiver to the shot. The pattern will be specified by a spread
specification. The receiver coordinates or grid layout must have been defined with module STATION
prior to running SOURCE. For geophones specified in the spread layout that are not defined in the
STATION program, GEOM will automatically kill the trace. Each spread layout must define a geophone
for every trace in a shot regardless of whether the trace is a live geophone or not.
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
Shot stn
Default .....:
Min .........:
Max .........:
Rule ........:
1747
Skid
receiver bin.
Default .....:0
Min .........:
Max .........:
Rule ........:
Perp dist
receiver line.
Default .....:0
Min .........:
Max .........:
Rule ........:
First geo
Receiver bin number for the first geophone on channel 1. If the cable is reversed, then this value will be
larger than the last trace position.
Default .....:
Min .........:
Max .........:
Rule ........:
Pre gap
Receiver bin number before the gap.
Default .....:
Min .........:
Max .........:
Rule ........:
1748
Post gap
Receiver bin number after the gap.
Default .....:
Min .........:
Max .........:
Rule ........:
last geo
Receiver bin number for the last channel.
Default .....:
Min .........:
Max .........:
Rule ........:
SEE ALSO
Matrix SRCXYSPD2.
AUTHOR
1749
Matrix SRCRECSPD2
MATRIX NAME
SRCRECSPD2 -- Source by receiver and pattern by spread
DESCRIPTION
This matrix will define the geometry for the SOURCE program. The source location will be specified by a
receiver bin number and a distance from the receiver to the shot. The pattern will be specified by a spread
specification. The receiver coordinates or grid layout must have been defined with module STATION
prior to running SOURCE. For geophones specified in the spread layout that are not defined in the
STATION program, GEOM will automatically kill the trace. Each spread layout must define a geophone
for every trace in a shot regardless of whether the trace is a live geophone or not.
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
Shot stn
Default .....:
Min .........:
Max .........:
Rule ........:
1750
Skid
receiver bin.
Default .....:0
Min .........:
Max .........:
Rule ........:
Perp dist
receiver line.
Default .....:0
Min .........:
Max .........:
Rule ........:
Elevation
Type ........:Float
Min .........:
Max .........:
Rule ........:
Depth
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1751
Uphole
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
First geo
Default .....:
Min .........:
Max .........:
Rule ........:
Pre gap
Default .....:
Min .........:
Max .........:
Rule ........:
Post gap
Default .....:
Min .........:
Max .........:
Rule ........:
last geo
1752
Default .....:
Min .........:
Max .........:
Rule ........:
SEE ALSO
Matrix SRCXYSPD2.
AUTHOR
1753
Matrix SRCRECXY
MATRIX NAME
SRCRECXY -- Source by receiver and pattern by distance from source
DESCRIPTION
receiver numbers and a distance from the receiver to the shot. The pattern will be specified by the distance
from the source to the channel. The receiver coordinates or grid layout must have been defined with
module STATION prior to running SOURCE.
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
1754
Rec bin
Default .....:
Min .........:
Max .........:
Rule ........:
Rec line
Default .....:1
Min .........:
Max .........:
Rule ........:
Skid
receiver bin.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Perp dist
receiver line.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1755
Pattern #
Default .....:
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION, Matrix PATTERN.
AUTHOR
1756
Matrix SRCRECXY2
MATRIX NAME
SRCRECXY2 -- Source by receiver and pattern by distance from source
DESCRIPTION
receiver numbers and a distance from the receiver to the shot. The pattern will be specified by the distance
from the source to the channel. The receiver coordinates or grid layout must have been defined with
module STATION prior to running SOURCE.
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
1757
Rec bin
Default .....:
Min .........:
Max .........:
Rule ........:
Rec line
Default .....:1
Min .........:
Max .........:
Rule ........:
Skid
receiver bin.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Perp dist
receiver line.
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
1758
Elevation
Type ........:Float
Min .........:
Max .........:
Rule ........:
Depth
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Uphole
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Pattern #
Default .....:
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION, Matrix PATTERN.
1759
AUTHOR
1760
Matrix SRCXYREC
MATRIX NAME
SRCXYREC -- Source by coordinate and pattern by receiver location
DESCRIPTION
and y coordinates. The pattern will be specified by receiver number. For receivers not defined in the
STATION program, GEOM will automatically kill the defined channel. This matrix allows you to push
the receiver layout by specifying the receiver bin and line number for channel number one on each shot.
For example, for a 2-D line with 48 channels per shot, you could define a pattern with the receiver bins
going from 1 to 48 for channels 1 to 48.
This pattern means that channel 1 is on receiver bin number 1. On a particular shot, if channel number 1 is
on say receiver bin number 50, then by entering 50 in the "Bin @FCSN 1" column, the channels for that
shot would reside at receiver bins 50 to 97.
For a 3-D line, the receiver layout will be pushed according to the sequential geophone number assigned
to the receiver bin and line numbers. For example, if we have 240 channels per shot and 60 receiver bins
for each receiver line, and we define the pattern as follows:
Line
4|
3|
2|
1|
181 182 183 ... 238 239 240

121 122 123 ... 178 179 180
61 62 63 ... 118 119 120
1
2
3 ... 58 59 60
--------------------------------1
2
3 ... 58 59 60
Bin
On a particular shot, if the channel number 1 is on say receiver bin number 3 on receiver line number 10,
then by entering 3 in the "Bin @FCSN 1" column and 10 in the "Line @FCSN 1" column, the channels
for that shot would be as follows:
Line
14|
13|
12|
11|
10|
239 240
179 180 181 ... 236 237 238
119 120 121 ... 176 177 178
59 60 61 ... 116 117 118
1 ... 56 57 58
--------------------------------1
2
3 ... 58 59 60
1761
Bin
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
X coord
Default .....:
Min .........:
Max .........:
Rule ........:
Y coord
Default .....:0
Min .........:
Max .........:
Rule ........:
1762
Pattern
Default .....:
Min .........:1
Max .........:
Rule ........:
Bin @FCSN1
Min .........:
Max .........:
Rule ........:
Lin @FCSN1
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Matrix PATREC.
AUTHOR
1763
Matrix SRCXYREC2
MATRIX NAME
SRCXYREC2 -- Source by coordinate and pattern by receiver location
DESCRIPTION
and y coordinates. The pattern will be specified by receiver number. For receivers not defined in the
STATION program, GEOM will automatically kill the defined channel.
This matrix allows you to push the receiver layout by specifying the receiver bin and line number for
channel number one on each shot. For example, for a 2-D line with 48 channels per shot, you could define
a pattern with the receiver bins going from 1 to 48 for channels 1 to 48. This pattern means that channel 1
is on receiver bin number 1. On a particular shot, if channel number 1 is on say receiver bin number 50,
then by entering 50 in the "Bin @FCSN 1" column, the channels for that shot would reside at receiver bins
50 to 97.
For a 3-D line, the receiver layout will be pushed according to the sequential geophone number assigned
to the receiver bin and line numbers. For example, if we have 240 channels per shot and 60 receiver bins
for each receiver line, and we define the pattern as follows:
Line
4|
3|
2|
1|
181 182 183 ... 238 239 240

121 122 123 ... 178 179 180
61 62 63 ... 118 119 120
1
2
3 ... 58 59 60
--------------------------------1
2
3 ... 58 59 60
Bin
On a particular shot, if the channel number 1 is on say receiver bin number 3 on receiver line number 10,
then by entering 3 in the "Bin @FCSN 1" column and 10 in the "Line @FCSN 1" column, the channels
for that shot would be as follows:
Line
14|
13|
12|
11|
10|
239 240
179 180 181 ... 236 237 238
119 120 121 ... 176 177 178
59 60 61 ... 116 117 118
1 ... 56 57 58
--------------------------------1
2
3 ... 58 59 60
1764
Bin
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
X coord
Default .....:
Min .........:
Max .........:
Rule ........:
Y coord
Default .....:0
Min .........:
Max .........:
Rule ........:
1765
Elevation
Type ........:Float
Min .........:
Max .........:
Rule ........:
Depth
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Uphole
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Pattern
Default .....:
Min .........:1
Max .........:
Rule ........:
Bin @FCSN1
1766
Min .........:
Max .........:
Rule ........:
Lin @FCSN1
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Matrix PATREC.
AUTHOR
1767
Matrix SRCXYSPD
MATRIX NAME
SRCXYSPD -- Source by coordinate and pattern by spread
DESCRIPTION
and y coordinates. The pattern will be specified by a spread specification. The receiver coordinates or grid
layout must have been defined with module STATION prior to running SOURCE. For geophones
specified in the spread layout that are not defined in the STATION program, GEOM will automatically
kill the trace. Each spread layout must define a geophone for every trace in a shot regardless of whether
the trace is a live geophone or not.
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
1768
X coord
Default .....:
Min .........:
Max .........:
Rule ........:
Y coord
Default .....:0
Min .........:
Max .........:
Rule ........:
First geo
Default .....:
Min .........:
Max .........:
Rule ........:
Pre gap
Default .....:
Min .........:
Max .........:
Rule ........:
Post gap
1769
Default .....:
Min .........:
Max .........:
Rule ........:
last geo
Default .....:
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module SOURCE, Module STATION, Matrix SRCRECSPD2.
AUTHOR
1770
Matrix SRCXYSPD2
MATRIX NAME
SRCXYSPD2 -- Source by coordinate and pattern by spread
DESCRIPTION
and y coordinates. The pattern will be specified by a spread specification. The receiver coordinates or grid
layout must have been defined with module STATION prior to running SOURCE. For geophones
specified in the spread layout that are not defined in the STATION program, GEOM will automatically
kill the trace. Each spread layout must define a geophone for every trace in a shot regardless of whether
the trace is a live geophone or not.
DIMENSIONS
None
VECTORS
ID
Default .....:
Min .........:
Max .........:
Rule ........:
FSPN
Default .....:
Min .........:
Max .........:
Rule ........:
1771
X coord
Default .....:
Min .........:
Max .........:
Rule ........:
Y coord
Default .....:0
Min .........:
Max .........:
Rule ........:
Elevation
Type ........:Float
Min .........:
Max .........:
Rule ........:
Depth
Type ........:Float
Default .....:0
Min .........:
Max .........:
Rule ........:
Uphole
Type ........:Float
Default .....:0
Min .........:
1772
Max .........:
Rule ........:
First geo
Default .....:
Min .........:
Max .........:
Rule ........:
Pre gap
Default .....:
Min .........:
Max .........:
Rule ........:
Post gap
Default .....:
Min .........:
Max .........:
Rule ........:
last geo
Default .....:
Min .........:
Max .........:
Rule ........:
1773
SEE ALSO
Module SOURCE, Module STATION, Matrix SRCRECSPD2.
AUTHOR
1774
Matrix SRGMUTE
MATRIX NAME
SRGMUTE -
DESCRIPTION
DIMENSIONS
Primary
Min .........:
Max .........:
Max # SP ....:999999
Secondary
Min .........:
Max .........:
Max # SP ....:999999
VECTORS
Tertiary
Default .....:
Min .........:0
Max .........:
Rule ........:
Start Time(ms)
Default .....:
Min .........:
Max .........:
Rule ........:
1775
End Time(ms)
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1776
Matrix SSDEC
MATRIX NAME
SSDEC -
DESCRIPTION
DIMENSIONS
None
VECTORS
Amplitude
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Nov 27, 2002 by Steve Jensen
1777
Matrix STAELEV
MATRIX NAME
STAELEV -- Receiver elevations if receivers specified by grid
DESCRIPTION
This matrix is used by the module STATION to define the receiver elevation if a receiver grid is used.
Elevations are linearly interpolated between defined locations.
DIMENSIONS
None
VECTORS
Receiver line
Default .....:1
Min .........:
Max .........:
Rule ........:
Receiver bin
Default .....:
Min .........:
Max .........:
Rule ........:
Elevation
Enter the elevation of the receiver in feet or meters.
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
1778
SEE ALSO
Module STATION, Matrix STATION.
AUTHOR
1779
Matrix STATGEO
MATRIX NAME
STATGEO -- Geophone statics matrix
DESCRIPTION
This matrix is used by statics modules to define all of the statics for each geophone. The geophone number
is the SGEN number and can be determined by adding the geophone bias to the row number in the
spreadsheet.
DIMENSIONS
Geophone bias
To define values for ids 1 to some number, enter zero. To define values for say ids 1000 to 2000, enter
999 and enter statics into rows 1 to 1001.
Min .........:
Max .........:
Max # SP ....:1
VECTORS
Geophone static(ms)
Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
SEE ALSO
Module STATIC.
1780
AUTHOR
1781
Matrix STATION
MATRIX NAME
STATION -- Specify receivers by coordinates
DESCRIPTION
This matrix is used by the STATION module to define the coordinates for every live station in the survey.
References to any receiver not specified in this matrix by GEOM or SOURCE will result in a dead trace.
DIMENSIONS
None
VECTORS
Receiver line
Default .....:1
Min .........:
Max .........:
Rule ........:
Receiver bin
Default .....:
Min .........:
Max .........:
Rule ........:
X coord.
Default .....:
Min .........:
Max .........:
Rule ........:
1782
Y coord.
Default .....:0.0
Min .........:
Max .........:
Rule ........:
Elevation
Enter the elevation of the receiver in feet or meters.
Type ........:Float
Default .....:0.0
Min .........:
Max .........:
Rule ........:
SEE ALSO
Module STATION, Matrix STAELEV.
AUTHOR
1783
Matrix STATSEQ
MATRIX NAME
STATSEQ -- Sequential statics matrix
DESCRIPTION
This matrix is used to define sequential using a defined header in the STATIC module. One should define
a static for all possible values for that header.
DIMENSIONS
Seq. # bias
Min .........:
Max .........:
Max # SP ....:1
VECTORS
Sequential static(ms)
Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
SEE ALSO
Module STATIC.
1784
AUTHOR
1785
Matrix STATSRC
MATRIX NAME
STATSRC -- Source statics matrix
DESCRIPTION
This matrix is used by statics modules to define all of the statics for each shot. The shot number is the
SSPN number and can be determined by adding the source bias to the row number in the spreadsheet.
DIMENSIONS
Source # bias
Min .........:
Max .........:
Max # SP ....:1
VECTORS
Source static(ms)
Type ........:Float
Default .....:
Min .........:-9999
Max .........:9999
Rule ........:
SEE ALSO
Module STATIC.
1786
AUTHOR
1787
Matrix SURFACE
MATRIX NAME
SURFACE - Interpreted horizons matrix
DESCRIPTION
This matrix is used to store interpreted horizons for various modules such as VIP, IMPHORZ, and
GEOVEL.
DIMENSIONS
MLIN index
Min .........:1
Max .........:
Max # SP ....:999999
Surface #
This is the surface index number starting from one.
Min .........:1
Max .........:
Max # SP ....:999999
VECTORS
Time
All pick times are in milliseconds.
Type ........:Float
Default .....:"No pick"
Min .........:0
Max .........:
Rule ........:
1788
AUTHOR
Created on Oct.5, 1998 by Bill
1789
Matrix SURFDEF
MATRIX NAME
SURFDEF
DESCRIPTION
DIMENSIONS
None
VECTORS
Name
Default .....:"Horizon#"
Min .........:
Max .........:
Rule ........:
Color
Default .....:
Min .........:0
Max .........:255255255
Rule ........:
Thickness
Default .....:10
Min .........:0
Max .........:10
Rule ........:
1790
Style
Default .....:Solid
Min .........:
Max .........:
Rule ........:
Type
Default .....:0
Min .........:0
Max .........:
Rule ........:
AUTHOR
1791
Matrix SURFSMOOTH
MATRIX NAME
SURFSMOOTH
DESCRIPTION
VECTORS
Horizon #
Default .....:
Min .........:1
Max .........:
Rule ........:
Radius of lines
Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
Radius of bins
Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
Boundary window size

Type ........:Float
Default .....:1.0
Min .........:0.0
Max .........:
Rule ........:
1792
SEE ALSO
Module VELSMTH.
AUTHOR
1793
Matrix SVSHTSHIFT
MATRIX NAME
SVSHTSHIFT -
Description
Dimensions
MLIN
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Attribute
Type ........:Float
Min .........:0
Max .........:
Rule ........:
AUTHOR
1794
Matrix SYNDIFF
MATRIX NAME
SYNDIFF - Synthetic Point Diffractor attributes
DESCRIPTION
This spreadsheet is used by the SYNDIP module to define attributes for all the desired Point Diffractor
events in the output data set.
DIMENSIONS
None
VECTORS
MLIN
Input the midpoint line number (MLIN) where the desired point diffractor will be located. The default is
the middle of the survey.
Default .....:"middle"
Min .........:
Max .........:99999
Rule ........:
MBIN
Input the midpoint bin number (MBIN) where the desired point diffractor will be located. The default is
the middle of the survey.
Min .........:
Max .........:99999
Rule ........:
1795
Time(Sec.)
Input the time in seconds where the desired point diffractor will be located.
Type ........:Float
Default .....:
Min .........:
Max .........:99999
Rule ........:
AUTHOR
1796
Matrix SYNDIPOA
MATRIX NAME
SYNDIPOA - Synthetic CMP offset information
DESCRIPTION
This spreadsheet is used by the SYNDIP module to define attributes for all desired offsets within a CMP
gather.
DIMENSIONS
None
VECTORS
Offset
Input the source to receiver offset distance in feet or meters
Default .....:
Min .........:
Max .........:99999
Rule ........:
S-R Azimuth
Input the source to receiver azimuth in degrees from due North.
Type ........:Float
Default .....:90
Min .........:
Max .........:99999
Rule ........:
1797
AUTHOR
1798
Matrix SYNDIPS
MATRIX NAME
SYNDIPS - Synthetic event attributes for Planar events
DESCRIPTION
This spreadsheet is used by the SYNDIP module to define attributes for all desired Planar events in the
output data set.
DIMENSIONS
None
VECTORS
MLIN
Input the midpoint line number (MLIN) where the desired event will cross at the specified Time. The
default is the middle of the survey.
Min .........:
Max .........:99999
Rule ........:
MBIN
Input the midpoint bin number (MBIN) where the desired event will cross at the specified Time. The
default is the middle of the survey.
Min .........:
Max .........:99999
Rule ........:
1799
Time(Sec.)
Input the time in seconds where the desired event will located in a zero-offset time section at the desired
MLIN and MBIN location
Type ........:Float
Default .....:
Min .........:
Max .........:99999
Rule ........:
Dip
Input the dip for the event in degrees, measured clockwise from the horizontal.
Type ........:Float
Default .....:0
Min .........:
Max .........:99999
Rule ........:
Azimuth
Input the azimuth of the event in degrees, measured clockwise from due North.
Type ........:Float
Default .....:0
Min .........:
Max .........:99999
Rule ........:
Intercept
Input the intercept (P) or the Normal Incidence Reflection Coefficient.
Type ........:Float
Default .....:1
Min .........:
Max .........:99999
Rule ........:
1800
Gradient
Input the gradient (G) for the event.
Type ........:Float
Default .....:0
Min .........:
Max .........:99999
Rule ........:
AUTHOR
1801
Matrix TARGET
MATRIX NAME
TARGET -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start pri.
Default .....:"First ID"
Min .........:
Max .........:
Rule ........:
End pri.
Min .........:
Max .........:
Rule ........:
Start sec.
Min .........:
Max .........:
Rule ........:
1802
End sec.
Min .........:
Max .........:
Rule ........:
Data set
Default .....:
Rule ........:
Path
Default .....:"Current path"
Rule ........:
AUTHOR
1803
Matrix TAUF
MATRIX NAME
TAUF -
DESCRIPTION
DIMENSIONS
PRIMARY
Min .........:
Max .........:
Max # SP ....:99999
SECONDARY
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Low cut dip (ms)

Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1804
Low pass dip (ms)

Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
High pass dip (ms)

Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
High cut dip (ms)

Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
Created on Aug 23, 1993
1805
Matrix TRCPLOT_CMT
MATRIX NAME
TRCPLOT_CMT -
DESCRIPTION
DIMENSIONS
None
VECTORS
Comment
Default .....:
Rule ........:
AUTHOR
1806
Matrix TRCPLOT_GAP
MATRIX NAME
TRCPLOT_GAP -
DESCRIPTION
DIMENSIONS
None
VECTORS
Pre-gap (seckey)
Default .....:
Min .........:0
Max .........:
Rule ........:
Post gap (seckey)

Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
1807
Matrix TSVP
MATRIX NAME
TSVP -
DESCRIPTION
DIMENSIONS
LINE
Min .........:
Max .........:
Max # SP ....:99999
BIN
Min .........:
Max .........:
Max # SP ....:99999
VECTORS
Time (ms)
Default .....:
Min .........:0
Max .........:99999
Percentage
Default .....:
Min .........:0
Max .........:200
Rule ........:
1808
AUTHOR
Created on April 12, 1994
1809
Matrix TVDIP
MATRIX NAME
TVDIP -- Time variant dip
DESCRIPTION
Matrix type TVDIP contain time variant dip data for Kirchhoff migration program PKMIG. Liner
interpolation is used between data points.
DIMENSIONS
None
VECTORS
Time (ms)
Type ........:Float
Default .....:
Min .........:0
Max .........:99999
DIP (degrees)
Type ........:Float
Default .....:
Min .........:0
Max .........:89.9
Rule ........:
TAPER (degrees)
Type ........:Float
Default .....:
Min .........:0
Max .........:80
Rule ........:
1810
AUTHOR
1811
Matrix TVSMOOTH
MATRIX NAME
TVSMOOTH
DESCRIPTION
Time variant smoothing parameters.
DIMENSIONS
None
VECTORS
Time/depth(ms/m/feet)
Type ........:Float
Default .....:20.0
Min .........:0.0
Max .........:
# of bins to smooth
Type ........:Float
Default .....:25.0
Min .........:0.0
Max .........:
Rule ........:
# of lines to smooth
Type ........:Float
Default .....:25.0
Min .........:0.0
Max .........:
Rule ........:
1812
AUTHOR
1813
Matrix TVTVZD
MATRIX NAME
TVTVZD - Time variant filters for the TVZD module
DESCRIPTION
Use this matrix to specify time variant filter parameters to be used by the TVZD module.
DIMENSIONS
None
VECTORS
Start Freq.
For the linear filter option, this is the 100% starting frequency point. A cosine squared taper is applied
before this point. For the geometric filter option, this is the 50% point on the low side of the first
frequency sub-band taper
Default .....:10
Min .........:0
Max .........:
Rule ........:
End Freq.
For the linear filter option, this is the 100% ending frequency point. A cosine squared taper is applied after
this point. For the geometric filter option, this is the 50% point on the high side of the last frequency
sub-band.
Default .....:100
Min .........:0
Max .........:
Rule ........:
1814
# Filters
The trace will be partitioned into this many sub-bands.
Default .....:10
Min .........:3
Max .........:12
Rule ........:
Adaptation
This is the window length used to extract the envelope.
Default .....:500
Min .........:0
Max .........:
Rule ........:
Start Header
TIM1 for the time horizon 1 in the trace header, and TIM2 for the the time horizon 2.
Default .....:NONE
Rule ........:
End Header
Default .....:NONE
Rule ........:
AUTHOR
1815
Matrix TVTVZDC
MATRIX NAME
TVTVZDC - Custom time variant filter specification for the module TVZD
DESCRIPTION
This matrix is used to design time variant custom filters for the module TVZD. The tapers from the pass
points to the cut points will be cosine squared
DIMENSIONS
Filter #
Enter the filter number starting from one to the desired number of time variant filters to be applied. A
maximum of five time variant filters may be specified.
Min .........:1
Max .........:5
Max # SP ....:99999
VECTORS
Low Cut
Enter the low 0% point (Hz.) band pass filter point.
Default .....:
Min .........:0
Max .........:
Rule ........:
Low Pass
Default .....:
Min .........:0
1816
Max .........:
Rule ........:
High Pass
Enter the high 100% point (Hz.) band pass filter point.
Default .....:
Min .........:0
Max .........:
Rule ........:
High Cut
Default .....:
Min .........:0
Max .........:
Rule ........:
Ref. Mean
This sub-band will be equalized to this reference mean if the equalization method is AGC.
Type ........:Float
Default .....:2500.
Min .........:0.001
Max .........:
Rule ........:
AUTHOR
1817
Matrix TVTVZDD
MATRIX NAME
TVTVZDD - Time variant custom filters for the TVZD module
DESCRIPTION
Use this matrix to specify parameters when performing a custom time variant filter for the TVZD module.
If all of the defaults are okay, then simply save the matrix with no changes in it.
DIMENSIONS
None
VECTORS
Adaptation
This is the window length used to extract the envelope.
Default .....:500
Min .........:0
Max .........:
Rule ........:
Start Header
Default .....:NONE
Rule ........:
End Header
1818
Default .....:NONE
Rule ........:
AUTHOR
1819
Matrix TVZD
MATRIX NAME
TVZD - Custom filter specification for the module TVZD.
DESCRIPTION
This matrix is used to design custom filters for the module TVZD that are not time variant. The tapers
from the pass points to the cut points will be cosine squared.
DIMENSIONS
None
VECTORS
Low Cut
Default .....:
Min .........:0
Max .........:
Rule ........:
Low Pass
Default .....:
Min .........:0
Max .........:
Rule ........:
High Pass
1820
Default .....:
Min .........:0
Max .........:
Rule ........:
High Cut
Default .....:
Min .........:0
Max .........:
Rule ........:
Ref. Mean
This sub-band will be equalized to this reference mean if the equalization method is AGC.
Type ........:Float
Default .....:2500.
Min .........:0.001
Max .........:
Rule ........:
AUTHOR
Created on Jan. 28, 1993 by Bill Starr
1821
Matrix USRFCSN
Matrix Description
Dimensions
SLIN
Sequential shot line number
Min .........:1
Max .........:
Max # SP ....:999999
SBIN
Sequential shot bin number. This is the same as the SSPN for 2-D lines.
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Attribute
The row numbers correspond to the channel number (FCSN) within the shot.
Type ........:Float
Min .........:0
Max .........:
Rule ........:
1822
Matrix USRMBIN
Matrix Description
Dimensions
MLIN
Midpoint line number. This should be one for 2-D lines.
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Attribute
The row numbers correspond to the minimum midpoint bin number to the maximum midpoint bin
number. Use the following formulas to calculate the row number and midpoint bin numbers:
row
= MBIN-minMBIN+1MBIN = minMBIN+row-1
The minMBIN is the minimum midpoint bin number as defined in the module STATION. MBIN is the
midpoint bin number.
Type ........:Float
Min .........:0
Max .........:
Rule ........:
1823
Matrix USRSBIN
Matrix Description
Dimensions
SLIN
Sequential shot line number. This should be one for 2-D lines.
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Attribute
The row numbers correspond to the sequential shot bin number (SBIN).
Type ........:Float
Min .........:0
Max .........:
Rule ........:
1824
Matrix USRSGEN
Matrix Description
Dimensions
RSLN
Receiver station line number. This should be one for 2-D lines.
Min .........:1
Max .........:
Max # SP ....:999999
Vectors
Attribute
The row numbers correspond to the minimum receiver bin number to the maximum receiver bin number.
Use the following formulas to calculate the row number and receiver bin numbers:
row
= RSBN-minRSBN+1RSBN = minRSBN+row-1
The minRSBN is the minimum receiver bin number as defined in the module STATION. RSBN is the
receiver bin number.
Type ........:Float
Min .........:0
Max .........:
Rule ........:
1825
Matrix V0
MATRIX NAME
V0 -
DESCRIPTION
DIMENSIONS
None
VECTORS
FSPN
Default .....:
Min .........:1
Max .........:
Rule ........:
V0
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
1826
Matrix VA3CDIP
MATRIX NAME
VA3CDIP -
DESCRIPTION
DIMENSIONS
None
VECTORS
Dips(deg.)
Type ........:Float
Default .....:
Min .........:-180
Max .........:180
Rule ........:
AUTHOR
Created on Jul 20, 1993
1827
Matrix VABINS2D
Matrix Description
Vectors
CMP strt
Default .....:
Min .........:0
Max .........:
Rule ........:
CMP end
Default .....:
Min .........:0
Max .........:
Rule ........:
Delta CMP
Default .....:0
Min .........:0
Max .........:
Rule ........:
# CMP grps
Default .....:1
Min .........:1
Max .........:
Rule ........:
1828
1829
Matrix VABINS3D
Matrix Description
Vectors
X-BIN strt
Default .....:
Min .........:0
Max .........:
Rule ........:
Y-LINE strt
Default .....:
Min .........:0
Max .........:
Rule ........:
X-BIN end
Default .....:
Min .........:0
Max .........:
Rule ........:
Y-LINE end
Default .....:
Min .........:0
Max .........:
Rule ........:
1830
Delta BIN
Default .....:0
Min .........:0
Max .........:
Rule ........:
Delta LINE
Default .....:0
Min .........:0
Max .........:
Rule ........:
# BIN grps
Default .....:1
Min .........:1
Max .........:
Rule ........:
# LINE grps
Default .....:1
Min .........:1
Max .........:
Rule ........:
1831
Matrix VPVSDEN
MATRIX NAME
VPVSDEN -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start Time (ms)
Default .....:
Min .........:0
Max .........:
Avg. Vp
Type ........:Float
Default .....:
Min .........:1
Max .........:
Avg. Vs
Type ........:Float
Default .....:
Min .........:1
Max .........:
1832
Avg. Density
Type ........:Float
Default .....:
Min .........:1
Max .........:
AUTHOR
Created on Jun 07, 2002 by Jensen
1833
Matrix VS2VP2
MATRIX NAME
VS2VP2 -
DESCRIPTION
DIMENSIONS
None
VECTORS
Start Time (ms)
Default .....:
Min .........:
Max .........:
Vs2/Vp2 (K)
Type ........:Float
Default .....:
Min .........:
Max .........:
AUTHOR
Created on Jun 10, 2002 by Jensen
1834
Matrix VSUM
MATRIX NAME
VSUM -- Records to sum
DESCRIPTION
This matrix is used by the VSUM module to specify ids to sum.
DIMENSIONS
None
VECTORS
Pri. strt
This is the primary starting id. This parameter is required if the primary id is not NONE.
Default .....:"depends"
Min .........:
Max .........:
Rule ........:
Pri. end
This is the primary ending id. This parameter is required if the primary id is not NONE.
Default .....:"depends"
Min .........:
Max .........:
Rule ........:
Delta Pri.
This is the increment added to the starting and ending ids to get the next ids to sum.
Default .....:0
Min .........:0
Max .........:
1835
Rule ........:
# Pri. grps
This is the number of primary groups to sum. For example, suppose we wish to sum ids 100-102,
200-201, & 300-302. The starting id would be 100, the ending id would be 102, the delta primary would
Default .....:1
Min .........:1
Max .........:
Rule ........:
Sec. strt
This is the secondary starting id.
Default .....:
Min .........:
Max .........:
Rule ........:
Sec. end
This is the secondary ending id.
Default .....:
Min .........:
Max .........:
Rule ........:
Delta Sec.
This is the increment added to the starting and ending ids to get the next id to sum.
Default .....:0
Min .........:0
Max .........:
Rule ........:
1836
# Sec. grps
This is the number of secondary groups to sum. For example, suppose we wish to sum ids 100-102,
200-201, & 300-302. The starting id would be 100, the ending id would be 102, the delta secondary would
Default .....:1
Min .........:1
Max .........:
Rule ........:
SEE ALSO
Module VSUM.
AUTHOR
1837
Matrix VVSPER
Matrix Description
Use this matrix to define percentage functions to apply to the reference velocity in the module CVA3D
and CVA2D when computing variable velocity stacks.
Dimensions
Line
This is the midpoint line number (MLIN)
Min .........:
Max .........:
Max # SP ....:99999
Bin
This is the midpoint bin number (MBIN)
Min .........:
Max .........:
Max # SP ....:99999
Vectors
Time (ms)
Default .....:
Min .........:0
Max .........:
1838
Min. %
The minimum VVS will be this value times the reference velocity.
Default .....:
Min .........:1
Max .........:200
Rule ........:
Max. %
The maximum VVS will be this value times the reference velocity
Default .....:
Min .........:1
Max .........:200
Rule ........:
1839
Matrix WEIGHTS
MATRIX NAME
WEIGHTS -
DESCRIPTION
DIMENSIONS
None
VECTORS
Weight
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
AUTHOR
1840
Matrix WINDOWS2
Matrix Description
This matrix is used by many modules to describe time gate windows.
Dimensions
Primary
This is the primary Id.
Min .........:0
Max .........:
Max # SP ....:999999
Vectors
Secondary
This is the secondary Id.
Default .....:
Min .........:
Max .........:
Rule ........:
Start-1 (ms)
This is the start time for window number one.
Default .....:0
Min .........:
Max .........:
Rule ........:
1841
End-1 (ms)
This is the end time for window number one.
Min .........:
Max .........:
Rule ........:
Start-2 (ms)
This is the start time for window number two.
Default .....:0
Min .........:
Max .........:
Rule ........:
End-2 (ms)
This is the end time for window number two.
Min .........:
Max .........:
Rule ........:
Start-3 (ms)
This is the start time for window number three.
Default .....:0
Min .........:
Max .........:
Rule ........:
End-3 (ms)
This is the end time for window number three.
Min .........:
1842
Max .........:
Rule ........:
Start-4 (ms)
This is the start time for window number four.
Default .....:0
Min .........:
Max .........:
Rule ........:
End-4 (ms)
This is the end time for window number four.
Min .........:
Max .........:
Rule ........:
Start-5 (ms)
This is the start time for window number five.
Default .....:0
Min .........:
Max .........:
Rule ........:
End-5 (ms)
This is the end time for window number five.
Min .........:
Max .........:
Rule ........:
1843
Matrix X_T
MATRIX NAME
X_T -
DESCRIPTION
DIMENSIONS
None
VECTORS
Offset (distance units)
Type ........:Float
Default .....:
Min .........:0
Max .........:
Rule ........:
Time (ms)
Default .....:
Min .........:0
Max .........:
Rule ........:
AUTHOR
Created on June 1,1998 by W. Wang
1844
Matrix XTTAPER
MATRIX NAME
XTTAPER - Define X-T taper
DESCRIPTION
This matrix is used to define an offset vs. time taper to be applied to the traces prior to stack. This matrix
is used by the module STACK and other CMP stacking modules. This option can be used to attenuate
multiples buy applying a taper to the near offsets. The absolute value of the offset is used. The scalar
values are interpolated between defined values.
DIMENSIONS
Offset
Min .........:0
Max .........:
Max # SP ....:999999
VECTORS
Time (ms.)
Default .....:
Min .........:0
Max .........:
Rule ........:
Scalar (db)
To decrease the amplitude enter a negative value. For example -6 will lower the amplitude two times.
Type ........:Float
Default .....:
Min .........:
Max .........:
Rule ........:
1845
AUTHOR
1846
Matrix XYDIP
MATRIX NAME
XYDIP - Defines time variant dips
DESCRIPTION
XYDIP matrix type contains time variant dip information. Vector X specifies inline dips and vector Y
specifies crossline dips.
DIMENSIONS
None
VECTORS
Time (ms)
Type ........:Float
Default .....:0
Min .........:0
Max .........:
X dip (degrees)
Type ........:Float
Default .....:90
Min .........:0
Max .........:90
Rule ........:
Y dip (degrees)
Type ........:Float
Default .....:90
Min .........:0
Max .........:90
Rule ........:
1847
AUTHOR
Created on Aug. 7, 1997 by W. Wang
1848
Release Notes For

SeisUP 2013
New Programs
BINREAD
Read Madagascars RSF and Stanford Exploration

Projects SEP formats.
CAZM
CAZM is a module for common-azimuth processing. It

can group the input traces into different common-offset
and common-azimuth bins.
DBINQ
Examine DB for matrices, geometry and other data.
DELHORZ
Delete interpreted horizons from the database.
EXPHORZ
Export interpreted horizons from the database to a file.
HDRINTP
HDRINTP can be used to insert dead traces at missing

trace locations that can be used by other modules for
interpolation such as TRIP5D or LRADON.
HORZIMP
Import ASCII format horizons into matrix.
IDLINBIN
IDLINBIN prints MBIN and MLIN numbers associated

with the X coordinates and the Y coordinates values in
the execution status list. It also prints the distance from
point to MBIN/MLIN center.
LRADON
LRADON can be used to attenuate noise using a high

resolution Radon transform.
MNMXAMP
MNMXAMP prints MLIN, MBIN, time and amplitude.
SPRSKID
SPRSKID was designed for the situation where shot

locations were defined but not receiver locations and the
shots were between receivers. Skid all 2D data stations
forward or backward 1/2 station.
SRINTERP
SRINTERP will interpolation source and/or receiver

coordinate locations in a user specified direction.
SYNTH
SYNTH computes a normal incidence synthetic

seismogram from digital well log data.
TRIP5D
TRIP5D can be used to perform 5D interpolation using

inverse distance weighting along the top two dominate
dip directions.
TVSE
Time variant spectral enhancement.
1849
TVSEC
Time variant spectral enhancement - cluster version.
VEXTRACT
Extract a velocity dataset to a matrix.
XYGEOM
XYGEOM is used to apply the geometry transformation

to the trace headers using the existing source and receiver
coordinates in the header. XYGEOM is similar to module
GEOM except that XYGEOM does not need source
information via the SeisUP database.
Updates / Bug Fixes

UTILITIES
Cluster Maintenance Utility (Rutil)
Added a pull down menu for the executable names.

The user can also type the executable name in the
box.
Flow Editor (Geodraw)
Added the grid size option to the Options menu.

Added checks to prevent invalid area / line names.
Matrix Editor (Geosp)
Added code to apply ADD, SUBTRACT,

MULTIPLY and DIVIDE options to multiple sheets.
Turned off some redraws for multiple sheet
operations. Added keyboard codes for multiple sheet
operations. Fixed an import failure. Added code to
sort in descending order.
MPICH2
Added support for using MPICH2 to communicate

with cluster nodes.
MODULES
AZIMVTRY
Fixed a divide by zero.

Fixed an orientation error.
1850
DISPLAY
Added code to toggle toggle spectra in the case of

multiple datasets.
Added error checks.
Added code to save time windows for a
WINDOWS2 matrix for time variant FK picks.
The LMO toggle button was not updating properly.
Added option to delete first break picks in a
region.
Added a pick delete mode option.
ENDIF
Added other header key option.
EQDIST
Added a check for the survey units.
FKMIG
Fixed a memory allocation problem.
GEOM
Process dead traces in case they are used for trace

interpolation.
Added option to insert dead traces for missing
shots or receivers.
GEOVEL
Added ability to use interpolated horizons.
HIP

Added MBIN / MLIN increment parameters.
HORIZON
IMPHORZ
Added interpreted external file format input.

Made the input easier by only having to specify a
column number rather than a column and number
of columns.
ISOV
Added custom color option.

IVEP
Allow the conversion of velocity and ETA

matrices to a HTI velocity matrix.
MPAS
Added a check for an invalid parameter.
1851
NMOA
Fixed an error for HTI velocity matrix import. The

Elliptical velocities parameter was read even if not
used.
NMOR
Fixed an error for HTI velocity matrix import. The

Elliptical velocities parameter was read even if not
used.
NOPERMIT
The CGM plot was a fixed size regardless of the

size of the survey. The Xs and Os were also fixed
size. This made for unreadable plots. The size of
the plot can now be set. Added an option to mute
data in time.
REFST
Fixed reference number assignment.
REFSTPRP
Added a geometry error check.
RFMT
Added support for Fairfield receiver gather format.
RLIV
Added depth variable velocity.
SCDECON2
Fixed a bug in the restore amplitude option. The

high pass and high cut frequencies were set
incorrectly.
SGN1
Added a parameter to flush the first output record

as SGN1 is running. This allows SGN2 to run even
if SGN1 aborts.
SGN2
Added an option to output a single OMIT

spreadsheet instead of multiple spreadsheets.
SPER
Corrected the gain computation for non-raytrace

option.
SURMAT
Bug fix in the phase filter. Allow the user input

number of traces be read.
SYNDIP
Added the ability to output shot records as defined

in the geometry database.
TFDNOISE
Added user defined window times. Allow getting

window times from TIM1 and TIM2.
TRACECAL
Added Kurtosis computation option.
TRACECMB
Added minimum energy subtraction.
VIMPEXP
Added support for a 4THNMO matrix.
1852
WRITE
The WRITE icon is changed when appending to a

dataset.
1853

SeisUP PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SeisUP PDF

Uploaded by

Copyright:

Available Formats

SeisUP Applications Manual

Geosp Matrix Editor Menus .

SeisUP Reference Manual: DBMERGE Module

SeisUP Reference Manual: FKINT Module .

SeisUP Reference Manual: IDLINBIN Module .

SeisUP Reference Manual: NOISE Module .

SeisUP Reference Manual: READ Module .

SeisUP Reference Manual: SMOOTH Module .

SeisUP Reference Manual: TVEQ Module .

FXYDSV data type .

2013 Help Documentation

Applications and Administration

Documentation > SeisUP Applications Manual >

Installation and License issues

Troubleshooting and other odd tools

SeisUP Configuration Files

The maximum number of traces per ensemble to hold in memory if not

Dataset Naming Convention

Dataset is limited to 8 characters for display reasons.

SeisUP Usr Directories

Some files are not located under $QEDTOP. These are:

The process ID of the SeisUP daemon.

Various mostly command line tools.

SeisUP Files Stored in User Home Directories

one of the following:

Additional QEDTOP to check.

Update links in cleanup files

The most used options are space, files and query.

As shown in the example, multiple argument commands should be enclosed in quotes.

An example of a cluster.conf file is:

For example, consider the following invocation and its output:

If specified, kill this program. Otherwise kill everything

<index>: P - PDB; M - MDB; X - MatrixDB; L - ListDB

File tests as good.

This will report the executable name.

gdb executable core

This will report the function calling

SeisUP Data Manager

The Application Main Window

Figure 1: SeisUPs "usr" Directory Tree.

Figure 2: Datasets Table for the Selected Area Folder.

The Menu Bar

File -> Open Backup/Restore Log...

Figure 3: The Dataset Properties Window.

File -> Preferences...

The Status Bar. See figure 4.

Figure 4: The Status Bar.

The Backup Areas Window

Figure 5: A Backup Areas Example.

The Restore Areas Window

Figure 6: A Restore Areas Example.

Shortcut keystroke commands:

Figure 1: The Filesystems Manager Window.

Tape Devices Manager

Figure 1: Tape Devices Table.

The Remote Tape Server

Figure 2: Job Monitors Reply Dialog.

Opening your first flow

Flow Editor Menus

Using the flow editor

Parts of the flow editor

Opening an existing flow

menu icon. When you execute a flow the