Larson Book

Contents1
Unisec User Guide
Unisec User Guide Contents

Unisec User Guide Contents 1
Introduction 5
Unisec Plotting Overview 6
Data Flow 7
Output Display 8
Allocating Display Space
Increasing allocated space
Display Framing
Other Docs
Known Problems
Contents2
Unisec User Guide
Input Parameter File 11

Overview 12
Entities
Entity Lists
Entity List Logic
General Parameters (PARMS) 16
Trace Plotting Instructions 24
Plotting Traces (TRACE)
Skipping Traces (SKIP)
Killing Traces (KILL)
Gapping Between Traces (GAP)
Padding Space Between Traces (PAD)
Timing Lines (TIMING)
Timing Line Annotation (TIMEA)

Side Timing marks (SIDETIC)
Timing Marks (TIC)
Down Lines (DOWN)
Plot Gap (PGAP)
Automatic Scaling (AUTOSC)
Trace Related Annotation 32

Trace Labels (LABEL, LABELV, LABELB, LABEBV)
User-Specified Trace Labels (LABEL)
Line Ties (LTIE,LTIEV)
Symbols (SYMBOL)
Text Statements (TEXT)
Distance Scale (LEGEND)
Time-Velocity Lists (TVLIST)
User-Specified Time-Velocity Lists (TVLIST)
Block Boundaries (BLKBND)
Side Annotation (SIDEA)
Profiles (PROFILE PROFBOT) 44

Profile Scaling
User Specified Profiles
Multiple Profile Curves (PRODAT)
Annotation of Profile Graphs (PROFAN)
Labeling Profiles (PROLAB)
Side Label Display 53
Side Label Control
Direction Arrow
Logo
Logo Scaling
Office Box (OFFICE)
Title Box (TITLE)
Other Docs
Known Problems
Contents3
Unisec User Guide
Field Information Box (FIELD)

Land or Marine Diagram
Processing Sequence Box (PROCESS)
Display Parameters Box (FILM)
Orientation Map (ORMAP)
Side Label Text Editing
Types of formats
Side Label Text Formatting
Editing Entity Values (EVALS)
Replacement Symbols (&) in Side Label Text
Horizon and Fault Display (HORIZON) 65

Horizon Color Table
Input/Output Specifications 67
Input Tape Specifications (TAPE)
Defining Entity Specifications (DEFINE)
Plotter Specifications
Electrostatic plotter attributes (ESP)
LASERDOT Plotter Attributes (LSR)
CGM (Computer Graphics Metafile) File Specifications
Identification Banner (BANNER) 75

Subend (SUBEND) 76
End Statement (END) 82
Color Plotting 83
Color display modes
Color Trace Data Scaling (CCLASS)
Color Scale
Color Scale Annotation
Color Tables
Defining Colors (DEFINE, COLORS)
Color Table File
Trace Data Color Input
Color Input Modes
Trace Color Data Format
Data Specifications 91
Statement Summary 92
Parameter Range Checks And Default Values 93
Other Docs
Known Problems
Contents4
Unisec User Guide
Appendix A 95
Default Side Label Presentation
Default
Default
Default
Default
Default
Office Box Presentation

Title Box Presentation
Field Information Box Presentation
Processing Sequence Box Presentation
Display Parameters Box Presentation
Appendix B 99
Orientation Map Input Format and Capabilities
General Notes on the Input Format
Notes on the Seismic Line Input Format and Display
Notes on Latitude - Longitude Lines
Notes on Geographical or Political Boundaries
Examples of the Orientation Map Input Format
Appendix C 107
Reserved Entity Names
Used by Side Label
Used by Trace Plotting
Used by T/V Lists (If from trace headers):
Appendix D 109
How To Plot Depth Sections
Appendix E 111
Tape Format Definition File
Appendix F 114
TYPE Default File
Appendix G 116
Symbol Table
Appendix H 117
UNISEC Fortran Logical Units
Other Docs
Known Problems
Unisec User Guide
Introduction
This document describes the Unisec software package for
seismic plotting. Unisec produces plotter independent
output.
In This Chapter
Unisec Plotting Overview

Data Flow
Output
Other Docs
Known Problems
Unisec Plotting Overview6
Unisec User Guide
Unisec Plotting Overview

Unisec is a seismic plotting software package producing
plotter independent output. You input seismic trace data
from a magnetic tape, or a disk and parameter file and output
seismic traces, trace related annotation, profiles, and side
label. This flexible package allows you to redefine the content
and format of the display.
Other Docs
Known Problems
Data Flow7
Unisec User Guide
Data Flow
You must first create a parameter file on the host computer
before plotting seismic trace data. This file and the
appropriate tape information allows Unisec to run
interactively or in the batch mode. Output produced by
Unisec is in CGM (Computer Graphics Metafile) format which
is based on the Metafile standard. This machine-independent
format is easily transported across computer systems and
can be sent to a CGM compatible plotting system for
subsequent plotting.
Other Docs
Known Problems
Output Display8
Unisec User Guide
Output Display
The output display is divided into seven levels. The following
describes the contents of each level of the display:
Level
Contents
Profiles up to 2" in height, with 0.25" of space

between each profile.
Time-velocity lists up to 2.5". Size based on the

value for VMAX
Trace symbols, line-ties, text, and distance

scale. Additional space is allocated using
dummy statements as described in the next
section.
Trace labels, if requested.
Seismic traces, timing lines and annotation,

timing marks, and down lines.
Trace labels, if requested.
Profiles up to 2" in height with 0.25" of space

between each profile.
Allocating Display Space

This program automatically allocates space for each of the
seven levels of the display. The amount of allocated space
varies depending on the parameters in the parameter file. No
space is allocated if a level is empty and adequate space is
allocated if data exists for the level. The following table shows
the algorithm used for automatic space allocation.
Other Docs
Level
Algorithm
Sum (profile height + 0.25") N = the number of

profiles to be plotted
Known Problems
Output Display9
Unisec User Guide
Level
Algorithm
(1.2 * tvlist annotation size) * (VMAX + 2) * max.

space for T/V boxes
1.2 * [largest symbol size + largest text size +

legend size + height of vertical line-ties +
(space for max. no. of line-ties * largest line tiesize)] + (space for max. no. of block boundaries
* (block boundary annotation size + 0.25))
0.25" + 0.15" * (number of entity labels + 1)
(IPS * RECL) / 1000 + 0.1"
0.25" + 0.15" * (number of entity labels + 1)
Sum (profile height + 0.25") N = the number of

profiles to be plotted
Increasing allocated space

You might have to increase allocated space for Level 3 which
can contain moderate-to-large amounts of annotation that is
closely spaced, (more than three tiers of line ties) or has
multiple distance scales.
To allocate additional space, include one or both of the
following dummy statements in the parameter file:
SYMBOL, DP=32767(32,1.0)
TEXT,DP=32767('D',1.0)
Note: Input one statement for one inch of space and both
statements for two inches of space.
You can use smaller values for the symbol or text size if you
want to allocate less than one inch of space. A shorter text
string results in less computation for the program. We chose
a depth point location of 32767 so that the symbol and/or
text is not plotted under almost any circumstance. In reality,
any location that is not present on the seismic data can be
used.
Other Docs
Known Problems
Output Display10
Unisec User Guide
Display Framing
The display is divided into a number of frames based on the
dimensions for the plotter's frame height and width. Frames
are generated by continuously plotting vertical slices of data
from the top to the bottom of the frame until the entire frame
is filled. The program continues plotting data, with a three
trace horizontal overlap between frames, until all the
requested data is displayed. If data overflows the frame in the
vertical dimension, the input tape is rewound and the data is
replotted on the next frame.
The side label is always plotted within one frame, regardless
of its location or size.
Other Docs
Known Problems
11
Unisec User Guide
Input Parameter File

This chapter includes a description of the input parameter
file, general parameters, and the permissible statements,
format, keywords and parameters for specific functions.
In This Chapter
Other Docs
Overview
General Parameters (PARMS)
Trace Plotting Instructions
Trace Related Annotation
Profiles (Profile PROBOT)
Side Label Display
Horizon and Fault Display (Horizon)
Input/Output Specifications
Identification Banner (Banner)
SUBEND (SUBEND)
End Statement (END)
Color Plotting
Known Problems
Overview12
Unisec User Guide
Overview
The input parameter file must be a non-numbered file on the
host computer. Each statement (line or input record) must
begin with a statement identification, unless the record
contains user-specified data values, and can be up to 80
characters in length. Each statement has associated
keywords and/or parameters that specify the plotting and
display of the data. A summary of permissible statements,
their format, and associated keywords and parameters, is
located in the Data Specifications chapter.
Theoretically, there is no program limit on the number of
lines or input records allowed per parameter file. It depends
on the computer system being used. While there is also no
limit to the number of PARMS statements, a limit of 1000
statements that are not PARMS statements, T-cards, or usersupplied data values are permitted. If your job exceeds these
limits, an error will occur.
Throughout this manual, capital letters will be used to
indicate statements, keywords, or parameters defined to the
program, while lower case letters will be used to indicate
parameters that are to be specified by you.
Entities
Entities are data identifications that specify the location and
attributes of data values or entries that will be used by the
program. Several entities are defined to the program by the
tape format definition file (see Appendix E), while others may
be specified by the user in the parameter file. Some common
entities include:
SP: shot point values
DP: depth point values
CDP: common depth point values (synonymous with DP)
TRN: trace numbers
TRC: an internal trace counter, which begins with a
value of zero and increments by one each time a trace is
plotted. When gapping occurs, TRC is automatically
reset to zero.
Other Docs
Known Problems
Overview13
Unisec User Guide
Entity Lists
When it is necessary to specify a list of values for an entity,
two formats can be used: an element list, with each entry
separated by a comma, or a loop, which will imply a list of
values.
Format for an Element List
entity = (value 1, value 2, value 3,...,value n)
Format for a Loop List

entity = (s TO e BY i, s TO e BY i, ....., s TO e BY i)
Where:
s = the starting value for the generating loop. The word FIRST
may be used, in which case the first value on the input tape
will be used.
e = the ending value for the generating loop. The word LAST
may be used, in which case the program will continue until
no more data exists on the input tape. If this value is omitted,
it will default to the value for s.
i = the value used to increment from s to e when generating
the values for the list. If this value is omitted, it will default to
one (1).
In addition, a program calculated value named TINC can be
used for the starting value, ending value, or the increment in
an entity list. The value of TINC is defined as follows:
If TPI < 5, then TINC = 5
If TPI >= 5, then TINC = 10 * INT((TPI + 5) / 10)
Where:
TPI = the number of traces per inch.
INT = the greatest integer function that takes the largest
integer that is less than or equal to the value in parentheses.
Both the element list and loop formats may be used together
to specify an entity list.
Examples
General Structure:
Statement ID, entity=(list)
Element List:
KILL, DP=(1,11,21,31,41,51)
Loop Generated List: KILL,DP=(1 TO 51 BY 10)
Other Docs
Known Problems
Overview14
Unisec User Guide
Combination List:
KILL,DP=(1,11 TO 31 BY 10,41,51)
These examples show how the two formats, or a

combination of the two formats, can be used to generate
the same list of values for the entity DP within the KILL
statement.
Entity List Logic

Statements that require an entity list also contain a logic
feature. If more than one entity list condition is specified on a
statement, all of the conditions on that statement must be
satisfied before the appropriate action will be taken. If several
statements with entity list conditions and the same
statement identification are specified, and the conditions are
satisfied by any one of the statements, the appropriate action
will be taken. (In other words, more than one entity list
condition per statement results in an "and" logical
relationship, while several statements with entity list
conditions and identical statement identifications, results in
an "or" logical relationship.)
Example 1
KILL,DP=(1 TO LAST BY 2),DP=(1 TO LAST BY 5)
Condition #1
Condition #2
will kill only traces that are common to Condition #1 and

Condition #2 since both conditions are on the same
statement.
Traces common to Condition #1 are depth points
1,3,5,7,9,11,13,15,17,19, ...
1,6,11,16,21,...
Traces common to both conditions are depth points
1,11,21,31,... and these traces would be killed.
Example 2
KILL,DP=(1 TO LAST BY 2)
KILL,DP=(1 TO LAST BY 5)
Condition #2
Condition #2
will kill traces that are common to Condition #1 or

Condition #2, since the conditions are located on different
statements.
Other Docs
Known Problems
Overview15
Unisec User Guide
1,3,5,7,9,11,13,15,17,19,...
1,6,11,16,21,...
Traces common to either condition are
1,3,5,6,7,9,11,13,15,... and these traces would be killed.
Other Docs
Known Problems
General Parameters (PARMS)16
Unisec User Guide
General Parameters (PARMS)

This group of keywords, and its associated statement ID
PARMS, control the format of the plot to be produced. The
format for these keywords is as follows:
PARMS,keyword l=value l,keyword 2=value 2,...,keyword n=value n
PARMS,keyword n+1=value n+1,keyword n+2=value n+2,...
Since PARMS is the statement ID, it must be the first entry

on each line. All keywords are optional, and may be input in
any order.
Identifying abbreviations for each keyword:
a: denotes alphanumeric
r: denotes real numbers
i: denotes integer values
l: denotes logical values. Choices are ON or OFF,
corresponding to the keyword being present or
absent.
Keyword definitions
ADDR = a The address of the user producing the plot. A
maximum of 8 characters are permitted for this keyword. Default is the entry for ADDR on the input tape
header.
BIAS = r This keyword adds a constant number of trace
spacings of dc shift to each trace before plotting. Positive
bias values result in more variable area shading, and
negative bias values result in less variable area shading,
regardless of the display mode or polarity of the data.
Acceptable values are real numbers such that: -1.5 <=
BIAS <= 6.0. Default is 0.0.
BLANK = r The number of trace spacings from the zero
reference line at which the wiggle side of the trace will be
clipped. Permissible values are real numbers such that
0 < BLANK <= 6.0. Default is 6.0 trace spacings.
BLKDOT = l This keyword controls drawing of the dotted lines from the block boundaries down to the seismic
data. Default is ON.
Other Docs
Known Problems
Unisec User Guide
CBPOS = l Controls position of the color (calibration)

bar on either side of the seismic section. The allowable
values for both keywords, denoting which side to draw
on, are: L, R, or NO.
where:
L = Left
R = Right
NO = No color bar is plotted
Default is LR, plot color bar on both sides.
CDNAME = a Specifies color. A definition name of up to
6 characters is used to select a color table from the color
tables file (COLTAB.TXT). Default is none.
CSPOS = l Controls position of the color scale (legend)
on either side of the seismic section. The allowable values for both keywords, denoting which side to draw on,
are: L, R, or NO.
where:
L = Left
R = Right
NO = No color bar is plotted.
Default is LR, plot color scale on both sides.
DEBUG = l This keyword controls, to a limited extent,
the information included in the execution printout. The
presence of this keyword will result in the printing of
several diagnostic messages, while its absence will cause
the program to refrain from printing these messages.
Default is DEBUG absent.
DISP = a The display mode to be used when plotting the
seismic data. Available display modes include:
Monochrome modes:
W: wiggle trace
VA: variable area shading to the right of the zero
reference line when viewing the trace with the first
sample (normally time zero) at the top and the last
sample at the bottom.
VAN: variable area shading to the left of the zero
Other Docs
Known Problems
Unisec User Guide
reference line when viewing the trace as specified.

Valid Monochrome display modes are: W, WVA, WVAN,
VA, VAN
Color Modes (may be used in combination with
monochrome display modes):
CB: background color fill
CIN: interpolated background color fill
CPT: color fill VA peaks and troughs
CP: color fill VA peaks only
CT: color fill VA troughs only
Examples of a combination with monochrome display
modes:
WCB: black wiggle with color background
WCPT: black wiggle with color VA fill of peaks and
troughs
CB: color background only, no wiggles
Default is WVA.
EDIT = l This keyword will invoke an EDIT only run. The
input parameters will be listed, decoded and error messages displayed, if any, but no plot will be produced.
Default is OFF.
ENDSPC = r Controls the amount of blank space, in
inches, at the end of a plot. Range is 0.0 <= ENDSPC <=
12.0. Default is 2.0.
GAIN = r The gain, in dB, to be applied to the data
before plotting. Acceptable values are real numbers such
that -999.9 <= GAIN <= 999.9.
At 0 dB, a sample amplitude of 16384 (see REFAMP
keyword) will result in a deflection of 1.0 trace spacings .
An increase of 6.0 dB will double the amount of trace
deflection, while a decrease of 6.0 dB will result in one
half the amount of trace deflection, for a given amplitude
on tape. (For LEVELED data, a value of 6.0 - 10.0 dB will
generally yield acceptable results.) Default is 0.0.
INPUT= a The input tape format. Possible entries
include:
Other Docs
Known Problems
Unisec User Guide
SEGY - SEGY tapes

any 8 character name defined in the tape format
definition file
Default is the first format in the tape format definition
file.
INV = l This keyword controls the polarity of the plot.
The absence of this keyword causes positive numbers on
tape to be plotted as a deflection to the right when viewing the trace with the first sample (normally time zero) at
the top and the last sample at the bottom. The polarity of
such a plot, as specified in the Display Parameters Box
of the side label, is "normal".
The presence of this keyword causes negative numbers
on tape to be plotted as a deflection to the right when
viewing the trace as specified above. This would yield the
same result as multiplying each sample on tape by -1
and plotting without the INV keyword being present. The
polarity of such a plot, as specified in the Display
Parameters Box of the side label, would be "inverse".
Default is INV absent.
IPS = r The number of inches per second for the trace
display. Acceptable values are real numbers such that
0.001 < IPS <= 50.0. Default is 3.0.
LINE = a The line number.
LSTDOT = l This keyword controls drawing of the dotted
lines from line ties and symbols down to the seismic
data. Default is ON.
MAN = a The name of the user producing the plot. A
maximum of 16 characters may be entered for this keyword. Default is the entry for MAN on the input tape
header.
MAXTVB = i This allocates space for multiple levels of
T/V boxes to be drawn. Range is 1 <= MAXTVB <= 3.
Default is 1.
METRIC = l This keyword indicates that the horizontal
and vertical plot scales will be interpreted as centimeters
instead of inches. All other spatial parameters such as
annotation size, thickness and plotter resolution will
continue to be input in inches. Default is OFF.
Other Docs
Known Problems
Unisec User Guide
MXBLKS = i This allocates space for the maximum

number of block boundaries per location. Range is 0 <=
MXBLKS <= 20. Default is 3.
MXLTIE = i This allocates space for the maximum number of line-ties per location. Range is 0 <= MXLTIE <= 20.
Default is 3.
NOVLP = i Frame overlap in traces. Range is 1 <=
NOVLP <= 50. Default is 3.
OUTPUT = a This keyword specifies the output display
device. Permissible entries are:
E: Electrostatic, Inkjet or Thermal plotter (Fixed
resolution)
L: Laserdot (Variable resolution devices)
Default is E.
PANEL = l If the entire section will not fit on the target
plotter, the section will be paneled by fitting as much
data as possible in the available space on each panel
until the entirety of the seismic data, and side labels if
applicable, are displayed. This feature may be suppressed (PANEL = OFF) by truncation of the seismic data
to fit on one panel. Default is ON.
PDIR = a The direction in which to plot successive
traces. Permissible entries include:
L: Left to right
R: Right to left
Default is L.
PEAK = r The number of trace spacings from the zero
reference line at which the variable area shaded side of
the trace will be clipped. Permissible values are real
numbers such that 0 < PEAK <= 6.0.
Default is 1.5 trace spacings.
PROS = a The prospect number used to identify the
data.
RDERR = a Occasionally, an error is encountered while
the input tape or disk file is being read. You can employ
this keyword to surmount the problem and plot a substi-
Other Docs
Known Problems
Unisec User Guide
tute trace in place of the defective trace. Permissible

entries include:
KILL: outputs a trace with all sample amplitudes equal
to zero (a "dead trace").
LAST: replots the last trace that was plotted
successfully.
Default is no corrective action will be taken if an error
occurs while reading the input tape.
RECL = i The record length of the trace to be plotted, in
milliseconds. Acceptable values are integers such that 1
<= RECL <= 32767. A maximum of 6000 samples per
trace may be plotted. Default is (NUMBER OF SAMPLES)
* (SAMPLE RATE) -- START.
REFAMP = r Controls the scaling of the data in terms of
absolute amplitude. REFAMP is the absolute amplitude
that will be scaled to one trace width at 0 dB.
If REFAMP = 0 is specified, the absolute average times
two is used to scale the data to one trace width. However,
take note that this requires more compute time. Default
is 16384.
SIDEL = a This keyword controls the presence and location of the side label. Permissible entries are:
L: left of trace data
R: right of traces data
LR: both left and right
NO: no side label is to be plotted
ONLY: only the side label is to be plotted
Default is R.
SR = r The sample rate of the seismic data, in milliseconds. Permissible values are real numbers such that
0.25 <= SR <= 100.0. Default is the sample rate in the
tape header.
START = i The start time of the trace data, in milliseconds. Acceptable values are integers such that - 32767
<= START <= 32767. Default is 0.
Other Docs
Known Problems
Unisec User Guide
TPI = r The number of traces per inch for the trace display. Acceptable values are real numbers such that 2 <=
TPI <= 200. Default is 12.0.
TRCMOD = a The number of traces to be displayed at
each trace location. Default is1.
TVHEAD = a The headings for the time-velocity lists.
Default is TIME RMSV INT DEP.
TVLDOT = l Controls the drawing of the dotted lines
from the T/V lists down to the seismic data. Default is
ON.
TVLFMT = a The display format for the time-velocity
lists. The permissible entries are:
INT: annotate time, RMS velocity, and interval velocity.
INTDEP: annotate depth in addition to time, RMS and
interval velocity
Default is no entry. This will result in only time and
RMS velocities being displayed if time-velocity lists are
requested using the TVLIST statement.
TYPE = a The type of data to be plotted. The TYPE keyword causes a group of default statements, which may
control the labeling and annotation on the plot, to be
included from the TYPE file. Absence of this keyword will
require you to input all labeling and annotation parameters, as there is no default.
Appendix F contains a typical list of the default
statements created by each TYPE keyword entry.
Default is None.
VACOL = i Specifies the color index used for VA color fill
when DISP=WVAC. Default is Black.
VMAX = i This keyword allocates space for plotting
time-velocity lists above the seismic data. Normally, the
value should be equal to the number of time-velocity
pairs within the longest list to be plotted. If the value is
too small, some time-velocity pairs may overlap with
other annotation in the display or be truncated. If the
value is larger than necessary, blank space will result at
a rate of one inch for each 10 pairs that are missing. Permissible values are integers such that 1 <= VMAX <=
200.0 Default is 12.
Other Docs
Known Problems
Unisec User Guide
WIGMOD = i Wiggle trace display modulus. This parameter can be used to turn on the wiggle trace display at a
regular interval. This is useful at very high trace densities. A value of 5 for example would turn the wiggle on
every fifth trace. The VA display is unaffected by this
control. Permissible values are integers between 1 and
100 inclusive. Default is 1.
WIGTHICK = r Wiggle thickness in inches. Permissible
values are between .001 and .01 inclusive. Default is
.005.
Other Docs
Known Problems
Trace Plotting Instructions24
Unisec User Guide
Trace Plotting Instructions

This group of statements specifies the conditions for plotting,
skipping, killing, gapping, and padding traces. In addition,
you can overlay timing lines, timing marks, and down lines
on the trace data.
Plotting Traces (TRACE)

The TRACE statement determines the traces on the tape that
will be plotted. There is no capability to plot traces out of
sequence. If no TRACE statement is present, all traces on the
input tape will be plotted. The program does not have the
capability to process more than one TRACE statement per
job.
Format
TRACE,entity=(list),entity=(list),...
Where:
entity = specifies the entity in the trace header used to
control the plotting of traces.
list = specifies those values which the entity must equal in
order for the trace to be plotted.
Examples
TRACE,DP=(FIRST TO LAST) plots all depth points on the tape.
TRACE,SP=(1 TO 10) plots shotpoints 1 through 10.
TRACE,DP=(1 TO 100 BY 2) plots every other depth point beginning
with depth point 1, until depth point 100 is encountered.
TRACE,DP=(1 TO 10,15 TO 20) plots depth points 1-10 and 15-20.
TRACE,DP=(1,18,33) plots depth points 1,18,33.
TRACE,DP=(1,18,20 TO 50 BY 2,99) plots depth points
1,18,20,22,24,...,48,50,99.
TRACE,SP=(1 TO 100 BY 2),SP=(1 TO 100 BY 3) plots shotpoints
1,7,13,19,...,91,97.
Other Docs
Known Problems
Unisec User Guide
Skipping Traces (SKIP)

The SKIP statement allows you to suppress the plotting of
certain traces.
Format
SKIP,entity=(list),entity=(list),...
Where:
entity = specifies the entity in the trace header which
controls skipping.
list = specifies the entity values to be skipped.
Examples
SKIP,DP=(FIRST TO LAST BY 2) skips (not plot) every other depth
point on the input tape.
SKIP,SP=(FIRST TO LAST),TRN=(l) skips trace #1 for all shotpoints on
the line.
Killing Traces (KILL)

Use of the KILL statement will set the amplitude of all
samples of a trace equal to zero (i.e. a dead trace).
Format
KILL,entity=(list),entity=(list),...
Where:
control the killing of traces.
list = specifies the traces to be killed.
Examples
KILL,SP=(1,5,l0 TO 100 BY 10) kills all traces with a shotpoint value of
1, 5, 10, 20, 30, ..., 90 or 100.
KILL,DP=(100 TO 200) kills depth points 100 through 200.
Gapping Between Traces (GAP)

The GAP statement controls gapping, or the amount of blank
space between groups of traces. Timing lines will not be
plotted across the blank space.
Other Docs
Known Problems
Unisec User Guide
Format
GAP,entity=(list),size
Where:
entity = specifies the entity in the trace header which
controls gapping.
list = specifies the traces which will be preceded by a gap; if
omitted, gapping occurs whenever the entity value changes.
size = the width of the gap in trace spacings. Acceptable
values are 1 <= size <= 50. Default is 3 trace spacings.
Examples
GAP,SP,5 produces a 5 trace gap immediately before the SP value
changes.
GAP,DP=(48 TO LAST BY 48) produces a 1 trace gap before each
trace with a DP value which is specified in the entity list. A gap would
occur between depth points, such as 47 and 48, 95 and 96.
Padding Space Between Traces (PAD)

Space can be inserted in the display where missing traces are
detected. This is useful when doing hand correlations with
shot or geophone gathers, when attempting to overlay
shotpoint gathers on the seismic section to check the
contribution of the gather to the total stack, or when the
seismic section is missing traces due to skipped shotpoints.
Timing lines will be plotted across the space that is padded.
Format
PAD,entity=(BY i)
Where:
entity = specifies the entity to be checked for continuity.
i = the increment expected between adjacent traces for the
entity specified. If this increment is not encountered, then m
traces of blank space are inserted using the following
equation:
m=
(entity n) - (entity n-1)

INT( ---------------------------
1)
Other Docs
Known Problems
Unisec User Guide
Where INT is the greatest integer function that takes the

largest integer less than or equal to the expression in
parentheses.
Examples
PAD,GR=(BY 2) inserts blank space whenever the group index is
incremented by a value greater than two.
PAD,DP=(BY 1) inserts blank space whenever the depth point index is
incremented by a value greater than one.
Timing Lines (TIMING)

TIMING controls the plotting of timing lines that overlay the
trace data and the corresponding timing line annotation that
appears at the ends of the timing lines.
Format
TIMING,(heavy,medium,light,doted,hthick,mthick,lthick,dthick)
Heavy, medium, light, and dotted specify the interval in

milliseconds for timing lines of respective thickness' and their
appropriate annotation. Positive values will draw timing lines
of the respective thickness' at the indicated time intervals
with appropriate annotation. A negative value will draw a
timing line of appropriate thickness, but will suppress the
annotation for the indicated time. A value of zero will result in
neither a timing line of that thickness nor an annotation
being plotted.
hthick, mthick, and lthick specify the relative thickness of
the heavy, medium and light timing line intervals. dthick
specifies the dot spacing of the dotted timing lines. All four
parameters are integers which are multiplied by .005 to
determine the thickness of the heavy, medium and light
timing line intervals or the dot spacing for the dotted line.
Default is TIMING,(1000,500,100,0,3,2,1,4).
Examples
TIMING,(1000,500,100,0) causes heavy, medium, and light timing lines
and annotation every 1000, 500, and 100 ms respectively. No dotted
timing lines will be generated.
TIMING,(1000,500,0,-50) results in the plotting of heavy timing lines at
1000 ms intervals, medium timing lines at 500 ms intervals, no light
timing lines, and dotted lines at 50 ms intervals. The timing line
annotation would appear at 500 ms intervals, but would be suppressed
Other Docs
Known Problems
Unisec User Guide
at 50 ms intervals.
Timing Line Annotation (TIMEA)

The size and thickness of the timing line annotation can be
controlled using the TIMEA statement.
Format
TIMEA,(size1,thick1,size2,thick2,size3,thick3,size4,thick4)
Where:
size = the character size in inches used to annotate the
corresponding level of timing lines. Default is .1.
thick = the thickness in inches of the characters used to
annotate the corresponding level of timing lines. Default =
.005.
Up to four sets of size and thickness pairs may be specified
where set 1 corresponds to heavy, 2 to medium, 3 to light,
and 4 to dotted.
Examples
TIMEA,(.2,.01,.1,.005,.1,.005,.1,.005) causes a size and thickness of .2
inch and .01 inch respectively for the heavy timing lines and a size and
thickness of .1 inch and .005 inch respectively for the medium, light and
dotted timing lines.
TIMEA,(,,,,.05,.005) causes a size and thickness of .05 and .005
respectively for the light timing lines and a default size and thickness of .1
and .005 respectively for the heavy, medium and dotted timing lines.
Side Timing marks (SIDETIC)

SIDETIC controls the plotting of timing marks whose width is
proportional to the thickness of each interval along the side
between the timing line annotation and the trace data.
Format
SIDETIC,(heavy,medium,light,lighter)
Heavy, medium, light and lighter specify the interval in

milliseconds for the side tick marks. The widths of each
interval are .12, .09, .06 and .03 inch respectively. Default is
no side tick marks.
Other Docs
Known Problems
Unisec User Guide
Example
SIDETIC,(1000,500,100,0) causes heavy, medium, and light tick marks
every 1000, 500, and 100 ms respectively.
Timing Marks (TIC)

TIC controls the placement of timing marks. These marks are
centered at the specified locations and have a width of one
trace spacing. Application of timing marks to the first trace of
gathers to be correlated may result in a considerable savings
of time when attempting to correlate data by hand.
Format
TIC,entity=(list),increment
Where:
control the placement of timing marks.
list = specifies the traces on which to center timing marks.
increment = the increment, in milliseconds, for the timing
marks. Acceptable values are integers such that 0 <
increment <= 1000. Default = 10.
Examples
TIC,DP=(1 TO 100 BY 40),50 centers a set of timing marks on depth
points 1, 41, and 81. The timing marks would appear at 50 ms intervals.
TIC,TRC=(1) centers 10 ms timing marks on the first trace of the plot
and the first trace after each occurrence of a gap.
Down Lines (DOWN)

DOWN controls the placement of vertical lines over the wiggle
trace data. These lines are approximately twice the thickness
of the normal wiggle trace and are centered on the zero
reference (base) line for the entire length of the trace.
Format
DOWN,entity=(list),entity=(list),...
Where:
control the placement of down lines.
Other Docs
Known Problems
Unisec User Guide
list = specifies the traces on which to place down lines.

Examples
DOWN,DP=(1 TO LAST BY 40) places down lines on depth points
1,41,81,...
DOWN,TRC=(1) places a down line on the first trace of the plot and
the first trace after each gap occurs.
Plot Gap (PGAP)

The PGAP statement allows you to insert gaps in plots at
data- defined points. Unlike GAP, which only inserts blank
space between traces, PGAP inserts side labels, timing line
annotation, and any other side annotation that normally
occurs at the end of the plot.
Format
PGAP,entity=(list),entity=(list),...
Where:
entity = specifies the entity in the trace header which will
control gapping.
list = specifies the values that the entity must equal in order
for the gap to occur. The gap will precede the trace on which
the condition occurs. If the list is omitted, a gap will occur
whenever the entity value changes.
Examples
PGAP,DP=(10 TO LAST BY 10) gaps between depth points 9 and 10,
19 and 20, etc.
PGAP,TRC=(200) gaps every 200 traces.
PGAP,TIME gaps every time the entity TIME changes.
Automatic Scaling (AUTOSC)

AUTOSC invokes automatic trace scaling based on the
absolute average of the data. The user specifies a group of
traces and a time interval that is scanned to find the absolute
average. This value is then used to set the REFAMP
parameter automatically to two (2) times the absolute
average. The GAIN parameter can still be used to apply
additional gain.
Other Docs
Known Problems
Unisec User Guide
The program derived REFAMP is displayed so that you can

plug this into the REFAMP parameter in subsequent plots of
the same data to reduce the processing time required to scan
traces. If the entity MUTE is available then the mute zone will
be excluded from the absolute average calculations.
AUTOSC can also be used when there is no TRACE statement
specified in the parameter file.
If the AUTOSC statement is absent, automatic scaling is not
performed and user GAIN is used.
Format
AUTOSC, (start trace, N traces, start, length)
Where:
start trace = starting sequential trace number for window
beginning with one. This trace number is after the TRACE
statement has been applied. Default = 1.
N traces = number of traces for window. Default = 50.
start = starting time for window in ms. Default = START.
length = length of time for window in ms. Default = RECL.
Example
TRACE, DP= (100 TO 5000)
AUTOSC, (100,200,1000,2000) causes depth points 200 through 400 to
be scanned and a gain derived from the data from 1000 to 3000
milliseconds.
Other Docs
Known Problems
Trace Related Annotation32
Unisec User Guide
Trace Related Annotation

This group of statements controls the various types of
annotation that can be created, such as trace labels, line ties,
symbols, text, a distance scale, and time-velocity lists. These
statements are necessary only if default statements are not
included by the use of PARMS keyword TYPE, or if you want
to specify additional annotation.
Trace labels are located within Levels four and six of the
display, immediately above and below the seismic traces.
Line ties, symbols, text, and a distance scale may be plotted
within Level three. Level two is reserved for time-velocity lists.
The order in which the statements for annotation within Level
three are entered in the parameter file influences the
appearance of the display. When positioning annotation for a
specific trace, the program locates the annotation for the first
statement at the lowest position available and annotation for
succeeding statements at progressively higher positions. In
addition, all Level three annotation for an individual trace is
grouped together as one piece of information for positioning
purposes in order to prevent related information, such as
well symbols and text information, from being split up.
The program will attempt to position all of the annotation
located within Level three so as to prevent overlapping. If this
is not possible, some annotation may be edited from the
display due to lack of space. To allocate additional space,
please refer to Space Allocation Algorithm for the
Display in the Output section of the Introduction.
Trace Labels (LABEL, LABELV, LABELB, LABEBV)

These statements specify the traces that are to be annotated
with labeling information from the trace headers. The
annotation is normally horizontal (parallel to the zero second
timing line), but can be made vertical (perpendicular to the
zero second timing line) by specifying LABELV. To turn on
labeling at the bottom of the section simply add the letter B to
the keyword to make it LABELB. The keyword for vertical
labeling at the bottom of the section is LABEBV. It is
recommended that only one (1) of each type of vertical label
statement (LABELV and LABEBV) be used per job, but
Other Docs
Known Problems
Unisec User Guide
multiple label patterns may be created by using the

(horizontal) LABEL statement up to five (5) times per job.
A maximum of five (5) entities may appear on each LABEL or
LABELV statement. The order in which the entities are listed
from left to right on the LABEL statement is the same order in
which they are written from top to bottom (highest to lowest
position) within Level 4 of the display. A horizontal or vertical
label will be automatically edited if it comes closer than 0.1
inch to any other label on the display.
To generate a blank line of space between two rows of
horizontal labels, add a NULL entity at the appropriate
location. For example:
LABEL,DP=(1,25 TO LAST BY 50),NULL,SP generates a blank space
between the labels DP and SP.
If desired, it is possible to plot a small vertical line without

the corresponding trace label above selected traces. This
feature, which is useful when successive trace labels are to
be located a considerable number of traces apart, is
illustrated in the fourth example listed below.
Format
statement name, entity1 = (list),....,entity 5 = (list), (size,thickness, offset)
Where:
statement name = LABEL, LABELV, LABELB, or LABEBV.
entity = specifies the entity which controls the labeling
locations, and which entities are to be labeled at those
locations. If preceded by a pound sign (#), the entity acts only
as a control for the annotation locations, but will not itself be
annotated.
list = specifies the traces to be labeled.
size = the character size in inches used for trace annotation.
Default is .1 for horizontal, 0.05 for vertical.
thickness = the thickness in inches of the annotation tick
mark. Default is .005.
offset = offset in trace widths (+ or -). Default is 0 (no offset).
Examples
LABEL,#DP=(1 TO LAST BY 5),SP causes the SP values to be labeled
Other Docs
Known Problems
Unisec User Guide
above every fifth depth point (1,6,11,16,...).

LABEL,#TRC=(1),SP,DP labels 2 rows of annotation (SP and DP from
top to bottom) above the first trace of the plot and the first trace after
each occurrence of a gap.
LABEL,DP=(FIRST TO LAST BY TINC),SP labels the first trace on
tape, and each TINC trace after the first trace, with the values for DP and
SP.
LABEL,#DP=(31 TO LAST BY 10)
LABEL,#DP=(31 TO LAST BY 50),SP this combination places a short
vertical line above depth points 31, 41, 51, ... but would only label the
shotpoint number at DP s 31 ,81, 131,...
These examples apply to LABELV, LABELB, and LABEBV as

well as to LABEL (substitute the word below for above when
bottom labeling is used.)
Alternate format for coding labeling lists
If the list required to specify the labeling conditions is
extensive and will not fit on a single line, an alternate form
similar to user-specified lists may be used.
Example
LABEL, DP+, SP
DP DATA
1, 15, 23, 35, 41, 55, 73, 88, 95, 102, 120, 135, 149, 150, 171, 190, 211,
230, 245,260, 277
will cause 2 rows (DP and SP) to appear above the traces
where DP = 1, 15, 23, 35, .......... 277.
User-Specified Trace Labels (LABEL)
This feature allows trace labeling information that is not
stored in the trace headers to be annotated by specifying a
list of values to be labeled at the appropriate traces. A
maximum of five (5) entities and new entities may appear on
each LABEL statement.
Format
LABEL,entity=(list),...,new entity
new entity DATA=(list)
LABEL,entity=(list),...,new entity
new entity DATA
User specified label values
Where:
Other Docs
Known Problems
Unisec User Guide
entity = specifies the entity that controls the labeling

locations and the entities to be labeled at those locations. If
preceded by a pound sign (#), the entity acts only as a control
for the annotation locations, but will not itself be annotated.
list = specifies the traces to be labeled.
new entity = an entity name for the user-supplied label
values. A maximum of six alphanumeric characters are
permitted. Entities in the tape format definition file
(Appendix E) should not be used in order to avoid confusion
with program defined entities.
Data values may be specified in one of the following input
formats:
A loop that will generate a list of label values in a manner similar to that for entity lists.
An element list in the free form entry format, with each
entry separated by a comma.
An element list in the fixed field entry format, with ten
columns per entry starting in Column 1.
When the program is reading label entries from an element
list, it terminates an entry upon encountering a comma or
when a total of 10 columns have been read, whichever occurs
first. Therefore, if the free form entry format is used, a label
entry should not be started after Column 71, otherwise an
error will occur. The occurrence of the next statement with an
alphabetic character in Column one will terminate the list.
Examples
LABEL,#DP=(7 TO 507 BY 20),EXT
EXT DATA=(10 TO 260 BY 10) plots user input EXT values at depth
points 7,27,47,67,... The corresponding EXT values at those depth
points are: 10,20,30,40,...
LABEL,DP=(13 TO 73 BY 10,85 TO 205 BY 12),EXT
EXT DATA
2R1,1R1,0-1,1-1,2-1,3-1,4-1,6-1,8-1,10-1,12-1
14-1,16-1,18-1,20-1,22-1,24-1,26-1 plots the DP and user input EXT
labels above depth points 13,23,33,43,53,63,73,85,97,109,...
The corresponding EXT values at these depth points are:

2R1,1R1,0-1,1-1,2-1,3-1,4-1,6-1,8-1,10-1,...
LABEL,DP=(1 TO LAST BY 20),GRID-X,GRID-Y
GRID-X DATA
100
120
140
160
180
200
220
Other Docs
Known Problems
Unisec User Guide
240
260
280
GRID-Y DATA
1000 1020 1040
1140 1160 1180
300
320
340
360
1060
1200
1080
1220
1100
1240
1120
1260
This example will plot trace labels above depth points

1,21,41,61,... as follows:
DP
1
GRID-X100
GRID-Y1000
21
120
1020
41
140
1040
61
160
1060
81
180
1080
101
200
1100
121
220
1120
141...
240...
1140...
Line Ties (LTIE,LTIEV)

LTIE specifies the location of line tie symbols and related
annotation. The annotation is centered above the specified
trace within Level 3. LTIEV causes the line ties to be plotted
vertically. Two line tie annotation options are currently
available:
Format 1
LTIE{V},entity=value(text,size,thickness),entity=
value(text,size,thickness),...
This option annotates the text in parentheses above the trace

for which the named entity has the given value.
Where:
entity = specifies the entity to be referenced in the trace
header.
value = the entity value for the trace above which the line tie
is to be centered.
text = the text string to be printed above the specified trace.
Any text which contains commas, parentheses, or leading
blank spaces must be completely enclosed in single quotes.
size = the text height in inches. Acceptable values are real
numbers between 0.05 and 1.0.
thickness = the thickness in inches of line tie symbol.
Acceptable values are real numbers between 0.0025 and 0.1.
Examples
LTIE,DP=214(F1626/101 SP. 49)
LTIE,DP=357('F1626, LINE 101, SP. 62')
Other Docs
Known Problems
Unisec User Guide
Format 2
LTIE{V},entity name 1,entity name 2,...,entity name n
This option annotates a line tie above each trace in which the
concatenated string extracted from entity 1 through entity n
is non-blank. This string will be used as annotation for the
trace and the entities from which the string is extracted may
be of mixed data types, such as characters and integers.
Symbols (SYMBOL)
SYMBOL specifies the location of symbols on the display
within Level 3.
Format
SYMBOL,entity=value(symbol,size,thickness),...,
entity=value(symbol,size,thickness)
Where:
header.
value = the entity value for the trace above which the symbol
is to be centered.
symbol = the symbol number for the symbol to be plotted. A
list of available symbols and their corresponding symbol
numbers is located in Appendix F.
size = the symbol size in inches. Acceptable values are real
numbers such that: 0.05 <= size <= 1.0. Default is 0.25,
thickness = the thickness of the line used to draw the
symbol, in inches. Acceptable values are real numbers such
that: 0.0025 <= thickness <= 0.1. In general, optimal results
will be achieved if the ratio of size to thickness is equal to 10
or less. Default is 0.025.
Examples
SYMBOL,DP=156(50,0.30,0.03)
SYMBOL,DP=263(32)
Text Statements (TEXT)

TEXT specifies the location of annotation that is to be
centered above a seismic trace within Level 3.
Other Docs
Known Problems
Unisec User Guide
Format
TEXT,entity=value(text,size),...,
entity = value(text,size)
Where:
header.
value = the entity value for the trace above which the text is
to be centered.
text = the text string to be printed above the specified trace.
If the text string contains commas, parentheses, or leading
blank spaces, then the string must be completely enclosed in
single quotes.
numbers such that: 0.05 <= size <= 1.0. Default is 0.1.
Examples
TEXT,DP=50(THIS IS A SPECIAL MESSAGE)
TEXT,DP=200('ANTHONY #1, TD 6325 FT. ',0.15,0.01)
Distance Scale (LEGEND)

The LEGEND statement will produce a scale and the
appropriate annotation indicating a distance of one mile or
one kilometer. The edge of the scale will begin at the specified
trace, with the scale elongated in the direction of plotting.
The word mile or kilometer will be centered above the scale.
Format
LEGEND,entity=value(scale,trdist,thickness)
Where:
header.
value = the entity value above which the edge of the scale will
begin. The scale will be elongated in the direction of plotting.
scale = the distance to be plotted:
M = Mile. Default is M if UNIT=E in the tape header.
K = Kilometer. Default is K if UNIT=M in the tape header.
Other Docs
Known Problems
Unisec User Guide
trdist = the distance between adjacent traces. This value

should be in units of feet if scale=M, and meters if scale=K.
Default is the depth point spacing value located in the tape
header. You should check to make certain that this value is
in units consistent with the choice for scale, as no check will
be made by the program.
thickness = the thickness in inches of the line used to draw
the scale. Acceptable values are: 0.0025 <= thickness <= 0.1.
Default is 0.015.
Note: The parentheses must be present after the entity value,
even if all of the parameters within the parentheses are to be
defaulted, otherwise an error will occur.
Examples
LEGEND,DP=51(K,25,0.01) draws a kilometer scale from depth point
51 to depth point 91 using a line 0.01 inches in thickness.
LEGEND,DP=16(,,) draws a distance scale beginning at depth point 16
based on the default values in the tape header.
Time-Velocity Lists (TVLIST)

TVLIST specifies the locations where time-velocity lists are to
be annotated. The time-velocity lists can be read from the
corresponding trace headers if they are stored there, or from
a user-supplied list. See User-Specified Time-Velocity Lists
in the following section. Automatic editing of these lists will
occur to prevent overlapping. Any successive list that is
closer than 0.1 inch in ascending plotting order will be
edited; however, a marker will be displayed at that location.
Format 1
TVLIST,entity=(list),(size,thickness,entval)
entity = specifies the entity in the trace header that will

control the plotting of time-velocity lists. The word VCASE is
permissible if you desire to annotate time- velocity lists at
velocity control locations.
list = specifies the entity values of traces for which timevelocity lists in the trace headers are to be plotted.
size = the character size in inches used in the annotation of
the TV data. Default is 0.1.
Other Docs
Known Problems
Unisec User Guide
thickness = the thickness of the line used to draw T/V box.

Default is .005.
entval = specifies the entity whose name and value at that
location will be printed above the T/V box. Default is no
heading.
Examples
TVLIST,VCASE results in time-velocity lists being annotated at velocity
control locations. These lists are copied from the appropriate trace
headers.
TVLIST,DP=(l TO 100 BY 40),(.05,.01,SP) causes time-velocity lists
stored in the trace headers for depth points 1, 41, and 81 to be annotated
above the corresponding traces with a character height of 1/20 of an
inch. It would also annotate each T/V box with the SP value at that
location.
Format 2
TVLIST,VCASE,entity name,size,thickness,entval)
This format is used when the TV data to be annotated is

stored in a trace header prior to the trace above which it is to
be plotted. Each time the entity VCASE is non-zero, it is
saved, along with the TV data for that header for subsequent
display when the named entity equals the value of the saved
VCASE.
Example
TVLIST,VCASE,DP the entity DP controls the location of the TV list to
be plotted. When the value of DP is equal to the saved value VCASE, the
list is displayed.
User-Specified Time-Velocity Lists (TVLIST)

You can input time-velocity lists if they are not present in the
trace headers or if you want to annotate the velocities
manually. The time-velocity lists may be entered in either the
fixed field entry format, with 5 columns per time-velocity
entry beginning in Column 1 or in the free form entry format,
with each entry separated by a comma. For either format, a
maximum of 200 time-velocity pairs per TVTD DATA control
card and 250 TVTD DATA control statements per parameter
file are permitted.
When the program is reading the time and velocity entries
from a user-supplied list, it terminates a time or velocity
entry upon encountering a comma, or when a total of 5
Other Docs
Known Problems
Unisec User Guide
columns have been read, whichever occurs first. Therefore, if

the free form entry format is utilized, an entry should not be
started after Column 76, otherwise an error will occur. The
occurrence of the next statement with an alphabetic
character in Column one will terminate the list.
Format
TVLIST,TVTD
TVTD DATA,DP=n
Time-velocity pairs
TVLIST,TVTD
TVTD DATA,CDP=n
Time-velocity pairs
Examples
TVLIST,TVTD
TVTD DATA,CDP=10
100 1500 650 1850 1150 2350 1500 2800 2100 3200
3000 3600 illustrates the fixed field entry format.
TVLIST,TVTD
TVTD DATA,SP=120
100,1500,650,1850,1150,2350,1500,2800,2100,3200,
3000,3600 illustrates the free form entry format.
Note: The format for labeling the entity heading above the TV
box is the same as before:
TVLIST,TVTD,(size,thickness,entval)
TVTD DATA,DP=n
Time-velocity pairs
Block Boundaries (BLKBND)

BLKBND specifies the location of the block boundary
annotation that is to be centered above a seismic trace. The
two text strings specified will be printed with three spaces
between them and underlined. A t-bar and dotted line will
proceed downwards from this to the trace at which it is to be
centered.
Format
BLKBND,entity=value(text 1,text 2,size,thickness),...,
entity=value(text 3,text 4,size,thickness)
Where:
header.
Other Docs
Known Problems
Unisec User Guide
value = the entity value for the trace above which the block
boundary is to be centered.
text 1, text 2 = the text strings to be annotated above the
specified trace.
numbers such that 0.05 <= size <= 1.0. Default is 0.1.
thickness = the thickness of the line used to draw block
boundary symbol in inches. Acceptable values are real
numbers such that 0.0025 <= thickness <= 0.1. Default is
0.005.
Example
BLKBND,DP=32('BLK 1','BLK 2',0.15,0.01) causes the following to be
annotated with text size 0.15 inch and thickness 0.01 inch, and centered
above depth point 32:
BLK 1
BLK 2_
|
|
|
|
|
Side Annotation (SIDEA)

The SIDEA statement allows you to place text strings in the
area just outside the zone in which the timing line annotation
is displayed. You specify text strings, their size and thickness
(optional), the time at which the strings are to be plotted, and
a title, which will be plotted vertically outside the side
annotation.
Format
SIDEA,title (size)
time 1,text 1,time 2,text 2,...,time n,text n
Where:
title = title string, plotted vertically outside side annotation.
The size of the text is (1.5 * size).
size = size of text 1, text 2 ,... text n. Range is 0.05 to 0.2
inch. Default is 0.1 inch.
Other Docs
Known Problems
Unisec User Guide
time = time in milliseconds at which to annotate the

corresponding text.
text = text to be plotted at the specified time.
Example
SIDEA,APPROXIMATE DEPTH
500,1056,800,1984,1100,2525,1400,3624,1700,4832,1950
5989,2200,6707,2500,7776,2650,8838,2800,9650 annotates
approximate depth values for certain times as an aid to interpretation of
the section. The title APPROXIMATE DEPTH is plotted vertically outside
the side annotation.
Note: Any line of an input parameter file that immediately

follows a SIDEA statement and has a numeric value in
Column 1 is interpreted by the program as a continuation of
the SIDEA statement.
Other Docs
Known Problems
Profiles (PROFILE PROFBOT)44
Unisec User Guide
Profiles (PROFILE PROFBOT)

You can profile one or more variables above, below, or
overlaying the seismic traces. The variables and their values
originate from one of the following sources:
Trace Headers
Time-Velocity Lists (from Trace Headers)
Equations such as Datum Static Corrections
ED + DC - EL
ET = 2000 * (-----------------------) - UT
VD
(To be used when calculating datum static corrections
without weathering information.)
User Input Data
Format
PROFILE,profile code(parameters)=(singles list),profile code... draws
the profile box above the seismic data display in Level one.
PROFBOT,profile code(parameters)=(singles list),profile code... draws
the profile box below the seismic data display in Level seven.
Where:
profile code = entity name for the variable to be profiled.
Note: Use of a # (pound sign) in front of the profile code will
suppress the space allocation for the profile above the
seismic data and attempt to overlay the profile on the seismic
data using the time scale for reference. For example, #ET will
cause the datum static correction times to be plotted over the
seismic traces. In a similar manner, #ISO will overlay the
section with iso-velocities.
parameters = an optional list of parameters used to specify
the format of the profile display. The format for this list is:
(text,orientation,ainc,thickness,height,min,max)
The list may be terminated at any point causing default

values to be used for unspecified parameters. Alternatively,
successive commas may be used to allow one or more
parameters to be defaulted, after which the list of values may
Other Docs
Known Problems
Unisec User Guide
be resumed. If the profile is to be overlaid on the seismic

data, only the thickness parameter will be significant, and all
other parameter values will be ignored.
Where:
text = A profile title or identification to be displayed at the
ends of the profile box. Default is the profile code.
orientation = The direction to plot profile values.
Acceptable entries are:
I: increasing values upward.
D: decreasing values upward (increasing values
downward).
B: bar graph instead of a profile line display.
Valid combinations for this parameter are: I, D, B, IB,
DB. Default is I.
ainc = The increment for scale annotation. The value
should be an integer. (A good value for ainc would be one
such that (min/ainc) = an integer and (max/ainc) = an
integer.). Default is the smallest integer in the following
such that: (max - min) <= 5 * (ainc). The ainc default list is
1,2,5,10,20,50,100,200,500, 1000 ...
thickness = The thickness of the profile value line.
Acceptable values are 0.01 <= thickness <= 0.10 inches.
Default is 0.02.
height = The profile height in inches. Acceptable values
are: 0.5 <= height <= 2.0 inches. Default is 2.0.
min = The minimum data value you want to profile. It is
recommended that a value be chosen such that (min/ainc)
= an integer. There is no default unless an input is userlist. Then a program derived value less than or equal to
the minimum data value to profile is used.
max = The maximum data value you want to profile. It is
recommended that a value be chosen such that
(max/ainc) = an integer. There is no default unless an
input is user-list. Then a program derived value greater
than or equal to the maximum data value to profile is
used.
Note: If the profile values originate from a user-input data
list, min and max are not required parameters, and can be
Other Docs
Known Problems
Unisec User Guide
defaulted. If the profile values originate from trace headers

(including time-velocity lists) or the Elevation Time Equation,
you must input min and max. The only exception is when the
profile will be displayed overlaying the seismic data, in which
case min and max are not used. Please refer to the discussion
on Profile Scaling under the following section as it relates to
requirements for the parameters min and max.
singles list = A list of values to profile when the profiling
variable has more than one value per trace. At present, this
only applies when profiling iso-velocities. Since there are
several velocity values for each trace, it is necessary to specify
the iso-velocity values you want to profile.
The format for the singles list is similar to that used to
specify an entity list. A list of values, a loop that will generate
a list of values, or a combination of a loop and a list may be
used.
Examples
PROFILE,#ET,EL causes the Elevation Time profile values to be plotted
on the seismic data and the location elevations to be profiled above the
seismic data. Values for min and max for profile ET have been omitted
since the profile will be drawn over the seismic data.
PROFILE,UT,DPFOLD(FOLD,I,10,0.03,1.0,0,50) generates two
profiles, uphole times from the statistics vectors, and the fold of the data
from the trace headers. The uphole time profile would be plotted with the
default parameter values. The fold profile would be one inch in height,
with values increasing upward. The minimum value profiled would be 0,
the maximum 50, with a scale increment of 10. Finally, the profile line
would have a thickness of 0.03 inches.
PROFILE,ISO(ISO VEL,D,,,,0,5000)=(10000 TO 16000 BY 2000)
profiles iso-velocities above the section, with lines corresponding to
velocities of 10000, 12000, 14000, and 16000 feet per second. Note that
the values for ainc, thickness and height have been defaulted, while
those for min and max have been specified because iso-velocities are
calculated from the trace headers. The profile would be oriented with
time decreasing upward (increasing downward), that is, with the same
orientation that increasing time demonstrates on the seismic section.
Profile Scaling
If the profile values originate from a user input data list, and
the default profile scaling presentation is chosen by
defaulting the parameters min, max, and ainc, the program
will select appropriate values for the limits of the profile,
divide the profile into five equal vertical areas, and annotate
the profile with the corresponding values. The default profile
Other Docs
Known Problems
Unisec User Guide
scaling presentation can be overridden by specifying values

for the parameters min, max, and ainc at your discretion.
If the profile values originate from trace headers (including
time-velocity lists) or the Elevation Time Equations, then the
default profile scaling presentation is not available and you
must supply values for the profile parameters min and max.
The only exception is when the profile will be displayed
overlaying the seismic data, in which case the vertical time
scale of the plot is used to scale the data. The number of
profile divisions and the annotation increment can be
selected by specifying a value for the parameter ainc. If ainc
is defaulted, the profile will be divided into five equal vertical
areas and the annotation labeled appropriately.
Suggestions:
If you want to have the same scaling on more than one
profile, for example when profiling both residual shot
and receiver static corrections, it is recommended that
identical values for min and max be specified for each
profile in order to override the defaulted values, which
may not be identical. A value for the parameter ainc can
also be specified, in which case it should also be identical for each profile.
For a CDP fold profile, appropriate values for min and
max can be found as follows:
A. Use a value of zero (0) for min.
B. Use a value that is equal to or greater than the
maximum fold of the data along the seismic line should
be used for max.
For the ISO profile, appropriate values for min, max, and
ainc are as follows:
A. Use a value of zero (0) for min.
B. Set max equal to (START + RECL) .
C. Set ainc = 1000 if (START + RECL) is < 8000 ms.
Set ainc = 2000 if (START + RECL) is >= 8000 ms.
User Specified Profiles

You can input a data list to be profiled. The data structure is
comprised of two parts. Part one specifies the entity to
reference in the trace header. The second part contains the
Other Docs
Known Problems
Unisec User Guide
location and data values in either the free form entry format,
with each value separated by a comma, or the fixed field
entry format with five columns per value starting in column
one. Multiple location and data value cards may be input.
The program linearly interpolates data values between
locations if a value is not specified for every location. In
addition, the first location's data value will be used for all
traces before the first location that do not have an assigned
value, and the last location's data value will be used for all
traces after the last location that do not have an assigned
value.
When the program is reading the location and data values, it
terminates a value upon encountering a comma or when a
total of 10 columns have been read, whichever occurs first.
Therefore, if the free form entry format is used, a location or
data value should not be started after Column 71, otherwise
an error will occur. The occurrence of the next statement with
an alphabetic character in Column one will terminate the list.
Format
PROFILE,profile code(parameters)
profile code DATA, entity
location 1 value 1 location 2 value 2 ... location n value n
PROFBOT,profile code(parameters)
profile code DATA, entity
location 1 value 1 location 2 value 2 ... location n value n
Where:
profile code = code for the variable to be profiled. Entities in
the tape format definition file (Appendix E) should not be
used, otherwise an error will occur.
parameters = an optional list of parameters used to specify
the format of the profile display. The format for this list is:
(text,orientation,ainc,thickness,height,min,max)
Where:
text = A profile title or identification to be displayed at the
ends of the profile box. Default is the profile code.
orientation = The direction to plot profile values.
Acceptable entries are:
I: increasing values upward.
Other Docs
Known Problems
Unisec User Guide
D: decreasing values upward (increasing values

downward).
B: bar graph instead of a profile line display.
Valid combinations for this parameter are: I, D, B, IB,
DB. Default is I.
ainc = The increment for scale annotation. The value
should be an integer. (A good value for ainc would be one
such that (min/ainc) = an integer and (max/ainc) = an
integer.). Default is the smallest integer in the following
such that: (max - min) <= 5 * (ainc). The ainc default list is
1,2,5,10,20,50,100,200,500, 1000 ...
thickness = The thickness of the profile value line.
Acceptable values are 0.01 <= thickness <= 0.10 inches.
Default is 0.02.
height = The profile height in inches. Acceptable values
are: 0.5 <= height <= 2.0 inches. Default is 2.0.
min = The minimum data value you want to profile. It is
recommended that a value be chosen such that (min/ainc)
= an integer. There is no default unless an input is userlist. Then a program derived value less than or equal to
the minimum data value to profile is used.
max = The maximum data value you want to profile. It is
recommended that a value be chosen such that
(max/ainc) = an integer. There is no default unless an
input is user-list. Then a program derived value greater
than or equal to the maximum data value to profile is
used.
entity = the entity to be referenced in the trace header.
location n = the location value for the entity specified.
value n = the value to be profiled at location n.
Examples
PROFILE,ELEV
ELEV DATA,DP
15,100,28,150,38,280,60,195,85,120
is a free form entry format that will profile ELEV, with the
depth point location (DP) as the entity specifying locations
at which the data values are to be assigned and profiled.
PROFILE,ELEV
Other Docs
Known Problems
Unisec User Guide
ELEV DATA, DP
15 100 28 150 38 280 60 195 85 120
is the identical example as above, but in the fixed field

entry format.
Multiple Profile Curves (PRODAT)

Normally profiles are displayed as a single solid line on a
profile grid above or below the seismic trace data. In some
cases, you may want to plot two or more profiles within the
same grid for comparison or simply to conserve space on the
plot by not plotting a separate profile for entities that fall
within the same range of values as a previous profile. An
example of this would be a case in which you want profiles of
a number of elevation values, such as group elevation, shot
elevation, and reference elevation, which fall in the same
general range of values. You could plot them all on separate
profiles, but this would make it difficult to compare the
various values and would take up a lot of plotting space. The
PRODAT statement allows you to superimpose the display of
one entity on a previous profile grid. The PRODAT statement
must always immediately follow a PROFILE or PROFBOT
statement.
Format
PRODAT,profile code1(text,ltype),profile code 2(text,ltype)...
Where:
profile code = entity name for the variable to be profiled
text = profile title to be annotated at the end of the profile
along with a sample of the line type used to plot the variable.
ltype = line type to be used to profile this variable. Valid line
types are:
1 = dotted..........
2 = dashed---------3 = dashed - dotted_ . _ . _ . _ . _ .
4 = dashed interspersed with 2 dots_ .. _ .. _ .. _
Default is a unique line type for each profile curve.
Other Docs
Known Problems
Unisec User Guide
Example
PROFILE,EL(SHOT ELEVATION,I,10,.03,2,0,20)
PRODAT,EG(GROUP ELEVATION),ER(REFERENCE ELEVATION)
causes a profile 2 inches high with 3 curves. The first (EL) would be a
solid line, the second (EG) would be a dotted line and the third (ER)
would be a dashed line. The annotation for this example is shown in the
diagram below.
Diagram of PRODAT annotation

SHOT ELEVATION___________
20.0
___________
10.0
GROUP ELEVATION...............
0.0
(profiles)
-10.0
REFERENCE ELEVATION------
-20.0 ___________
Annotation of Profile Graphs (PROFAN)

Once you have setup a profile using the PROFILE, PROFBOT
or PRODAT statements, you can annotate values along a
graph line by using the PROFAN statement.
Format
PROFAN, entity name 1(parameters)=(list),.......entity name
n(parameters)
Where:
parameters = an optional list of annotation parameters
annotated along the profile. The format for this list is:
(title,symbol,size,thickness)
Where:
title = a title to be displayed at the ends of the profile box
along with the identifying symbol. Default is the entity
name.
symbol = a single character such as +, -, or X which is
used as an identifying symbol and will be displayed
following the title and each value that is annotated along
the graph line. Default is blank.
size = annotation size in inches. Acceptable values are
real numbers such that: .05 <= size <= 1.0. Default is .1.
Other Docs
Known Problems
Unisec User Guide
thickness = annotation thickness in inches. Acceptable

values are real numbers such that: .0025 <= size <= 0.1.
Default is 0.005.
The list may be terminated at any point causing default
values to be used for unspecified parameters. Alternatively,
successive commas may be used to allow one or more
parameters to be defaulted, after which the list of values may
be resumed.
list = a list specifying the locations to be annotated. The
format is similar to that used to specify an entity list. A list of
values, a loop that will generate a list of values, or a
combination of a loop and a list may be used. Only one list
may be specified on each PROFAN statement.
Example
PROFILE,RFEL(REFRACTOR ELEVATION,I,600,.03,1,900,3600)
PRODAT,GPEL(GROUP ELEVATION)
PROFAN,WVEL(WEATHER VEL,X)=(2000 BY 50),RVEL(REFR VEL,+)
causes the graph lines represented by RFEL and GPEL to be annotated
using the values of WVEL and RVEL respectively at SP locations 2000,
2050, 2100 .....
Note that the order of the entity names on the PROFAN

statement is important in that the first name is associated
with the first profile code, the second is associated with the
second profile code, and so on. If more entity names are
specified on the PROFAN statement than there are profile
codes, an error will occur when the parameters are being
validated.
Labeling Profiles (PROLAB)

The profile box can be labeled along the top by the use of this
statement. PROLAB follows the same rules as the trace
labeling (LABEL) statement. PROLAB also causes a vertical
grid line to be drawn each time a location is labeled. The
PROLAB statement must follow the PROFILE or PRODAT
statement that is meant to be labeled.
Example
PROFILE,EL(ELEVATION IN FT,I,10,,,10,200)
PROLAB,SP=(2000,2040 TO LAST BY 10) causes the values 2000,
2040, 2050 ...etc. to be annotated across the top of the profile box.
Other Docs
Known Problems
Side Label Display53
Unisec User Guide
Side Label Display

The side label is generated by the inclusion of the PARMS
keyword SIDEL with an appropriate entry (see SIDEL under
General Parameters). The majority of the information for the
default side label presentation originates from the input tape
header. If formatting is performed on any area or box, then
all areas/boxes must be formatted.
The width of the side label has a default of 6 inches, while
the length is dynamically allocated based on the information
to be included. The maximum length of the side label,
however, is the greater of 40 inches or the sum of the space
allocated for the seven levels of the seismic display. If the
side label will be longer than the maximum permissible
length, then the program will automatically truncate it at that
maximum length.
The side label is divided into 9 areas or boxes. Only 8 fields
may be used at any given time and in any order (see) ORD
keyword). The 9 areas or boxes supported which are listed
below:
Direction Arrow
Logo (primary)
Office Box
Title Box
Field Information Box
Processing Sequence Box
Display Parameters Box
Orientation Map
Logo (secondary)
Side Label Control

The SIDEL statement (not to be confused with the PARMS
keyword SIDEL) and associated keywords give the user
control over the Side Label scaling, default annotation size
and other parameters for the side label.
Other Docs
Known Problems
Unisec User Guide
Format
SIDEL, keyword l=value l,keyword 2=value 2,...,keyword n=value n
Example
SIDEL,SIZE=0.1,SCALE=1.0,SDLWID=6.0
SIDEL,LOGO1=LMK.cgm,LOGO2=LST.cgm,DIRA=ON
SIDEL,TABLOC=3.0,ORD=AOTFPD
SIDEL,AUTOHT=OFF,SHOOT=OFF
Since SIDEL is the statement ID, it must be the first entry on

each line. All keywords are optional, and may be input in
any order.
The following abbreviations will be used to identify the
necessary input for each keyword:
a denotes alphanumeric
r denotes real numbers
i denotes integer values
l denotes logical values. Choices are 'ON' or 'OFF',
corresponding to the keyword being present or absent,
respectively.
Below are the keywords definitions:
LOGO1 =a
The filename of the CGM picture to be inserted
in the primary (1)
LOGO2 =a or secondary (2) side label box respectively. This
CGM filename must reside in the $LSTHOME/larson/lstbin
directory or the $PROMAX_HOME/sys/exe/larson/lstbin
directory.
LG1HT = r
height in inches of picture used for logo 1 or 2
picture in inches
LG2HT = r
default = 1.5 inches
LG1WID = r width in inches of picture used for logo 1 or 2

picture in inches
LG2WID = r
default = 6.0 inches
LG1MARG =r
margin in inches added to logo 1 or 2
picture i.e. extra
LG2MARG =r
default = 0.0
Other Docs
extra white space added around the picture.
Known Problems
Unisec User Guide
TABLOC =r The location in inches from left edge of sidel

label for the first tab setting within text strings.A second tab
in the same text string, if found, will tab to the right 2 x
TABLOC (2 times).
Default = 3.0
ORD =a The order of the areas or boxes that makeup the
side label. A string which may be any combination and
sequence of the following:
A =Direction Arrow
L =Logo 1
T =Title Box
F =Field Information Box
P =Processing Sequence Box
D =Display Parameter Box
S =Logo 2
O =Office Box
M =Orientation Map
Format
To display the Direction Arrow, Logo 1, Office Box, and Field
Information Box in this order, the ORD keyword would be:
ORD=ALOF
Default=ALOTFPDM
Where:
SIZE =r Default text size in inches. Range is from
0.0005 to 1.0. Default = 0.1
SCALE =r
A real number between .25 and 2 inclusive
which will be used as a multiplier to scale all text and lines
that comprise the side label including the logo and diagrams.
For example a scale factor of .5 would produce a 1/2 scale
side label and a scale factor of .25 would yield a 1/4 scale
side label. Default = 1.0
SDLWID =r
side label width in inches. Range is from 6.0
to 12.0. Default = 6.0
DIRA = 1 controls the drawing of the direction arrow in the
side label. Default = ON
Other Docs
Known Problems
Unisec User Guide
DIAG = 1 controls the drawing of the diagram (land or

marine) in the side label. Default = ON
AUTOHT =1 enables automatic scaling of the side label
height. This will limit the height of the side label to that of the
section. Default = OFF
SHOOT =l causes the direction arrow to be annotated with
SHOOTING DIRECTION and will point in that direction (same
as PDIR). Default = OFF
Example
SIDEL,SIZE=.075, SCALE=.75
This example will yield a 3/4 scale side label with a text size
of 0.075 inch.
Direction Arrow
A direction arrow is automatically plotted within the side
label to indicate the orientation of the plot. The arrow always
points to the right, and the accompanying information
specifies the angle in degrees (measured clockwise from
North) and the corresponding octant
(N,NE,E,SE,S,SW,W,NW). The angle and octant are
calculated based on the values for the line direction and the
plotting direction. Users may override the value for the angle
by specifying the correct line direction using the EVALS
keyword LDIR (see Appendix C).
Logo
The logo is centered vertically and horizontally within a box.
The choice of which logo to plot is specified by the SIDEL
keywords LOGO1 and LOGO2. The size of this box will
depend of the dimensions of the picture inserted. The default
height and width of the logo box is 1.5 by 6.0 (or specified
side label width) inches.
Preparing Logos for Unisec
Unisec will accept any standard CGM picture file for the Side
Label display. This CGM can be prepared on a PC or UNIX
workstation and then moved to the workstation where Unisec
will run and placed in the "larson/lstbin" directory. That
CGM file name is referred to in the Unisec parameter file with
the LOGO1 and LOGO2 keywords.
Other Docs
Known Problems
Unisec User Guide
There are number of popular illustration PC packages like

Corel or Canvas, which can be used to make a CGM picture.
The CGM support of these PC packages is not very robust
however. This restricts what CGM elements can be used.
Below are peculiarities experienced with these packages.
Software products such as PlotShop from Larson Software
Technology are designed to handle complex CGM files and
have less compatibly problems. PlotShop can be used to draw
logos composed of geometric shapes. Or it may be used to
Import raster images such as scanned data or clip art, add
annotation and export the whole as a CGM picture. PlotShop
may also be used in conjunction which PC graphics software
since PlotShop can import a number of image formats. This
is useful for example, to use a PC package to massage a
scanned image and then import it into PlotShop adding to it
to produce the final CGM picture for Side Label.
There are other robust CGM based products such as SDI
Montage capable of producing a proper CGM compatible
with Unisec.
Notes on Corel 7: Corel does not work with raster images
imported as TIFF or BMP into to Corel such as scanned data
or clip art.
Another peculiarity is that artifacts appear in the CGM
picture after it is displayed by Unisec. This is caused by
white rectangles or shapes not appearing in Corel but shown
up in the CGM picture when plotted outside of Corel. These
artifacts can be sometimes identified and deleted in Corel.
A third problem is Fill area (polygon) borders are incorrect
sometimes. The CGM produced by is "Metric" scale mode
which means that actual dimensions are carried in the CGM
when exported.
Notes on Canvas 3.53: Canvas unlike Corel, works well with
raster images. Be sure to select "Painted Objects as Cell
Arrays" in Save dialogue box when the CGM is exported.
Text can not be used since the text size is not carried along in
the CGM and appear much to large in the final display.
Canvas CGMs are "Abstract" scaling mode which means they
have no specific. This is OK however, as the CGM picture is
scaled by Unisec to the desired size according to the Logo
height and width parameters.
Other Docs
Known Problems
Unisec User Guide
Logo Scaling
If the dimensions of the CGM picture do not have as aspect
ratio of 1:4 (default) then the desired height and width of the
picture can be specified with the SIDEL keywords LG1HT,
LG1WID. This does not have to be the exact dimensions
contained in the CGM picture as Unisec will scale the CGM
picture, stretching it both horizontally and vertically to fit the
allocated space.
Example
A CGM named lst.cgm with an aspect ratio of 1:1 will be
scaled to 2 X 2 inches. White space of .1 inches will surround
(in addition to white inherent to the picture) the picture
which will be placed in the primary logo box of side label.
SIDEL, LOGO1=lst.cgm, LG1HT=2.0, LG1WID=2.0 LG1MARG=.1
Office Box (OFFICE)

The OFFICE statement is used to replace, insert, or remove
information in the Office Box of the side label. The Office Box
should contain the identity of the office producing the plot.
The default Office Box presentation is located in Appendix A.
Default size = 0.15 inches
Title Box (TITLE)

The TITLE statement is used to replace, insert, or remove
information in the Title Box of the side label. The Title Box
typically contains information which identifies the seismic
trace data. This information usually includes the following:
The line number and/or name.
The type of data displayed (time section, migrated
depth section, etc.)
The range of shotpoints displayed.
The prospect name.
The geographical location where the data was acquired.
The date the processing (or redisplay) was completed.
The default Title Box presentation is located in Appendix A.
Other Docs
Known Problems
Unisec User Guide
Field Information Box (FIELD)

The FIELD statement is used to replace, insert, or remove
information in the Field Information Box of the side label.
The Field Information Box should contain information which
describes the data acquisition parameters and shooting
geometry.
Three default presentations exist for the Field Information
Box, and each is illustrated in Appendix A. The particular
default presentation which is used is based on the entries in
the tape header for the shooting surface (SURF=L or M) and
the energy source ((SOURCE=(VIBROSEIS or DINOSEIS)), or
(all other sources)).
Land or Marine Diagram
A geophone spread or boat diagram will be displayed by
default at the top of the Field Information box depending on
whether the surface is land or marine ('SURF' = 'L' or 'M').
This diagram may suppressed by using the SIDEL keyword
DIAG.
Example
SIDEL,DIAG=OFF
would suppress the diagram.
Processing Sequence Box (PROCESS)

The PROCESS statement is used to replace, insert, or remove
information in the Processing Sequence Box of the side label.
The processing sequence must be specified by the user, as
there is no capability at the present time to have this
included automatically. The default Processing Sequence
Box is located in Appendix A.
Display Parameters Box (FILM)

The FILM statement is used to replace, insert, or remove
information in the Display Parameters Box of the side label.
The Display Parameters Box consists of information
Other Docs
Known Problems
Unisec User Guide
concerning the parameters which control the display of the

seismic data. The default presentation is located in
Appendix A.
Orientation Map (ORMAP)

The Orientation Map permits the user to generate a small
map at the bottom of the side label which is designed to
illustrate the major features of a prospect area. The map
may contain one or more of the following elements:
Seismic Lines
Latitude - Longitude Lines
Geographical or Political Boundaries
The program will automatically scale and center the map so
that it fits proportionately within the width of the side label.
The Orientation Map is generated by the inclusion of an
ORMAP statement in the input parameter file. The elements
to be plotted within the map are specified using a T-card
format, which is outlined in Appendix B.
Format
ORMAP
T-cards
Examples: See Appendix B
Side Label Text Editing

The Office, Title, Field Information, Processing Sequence, and
Display Parameters Boxes have default presentations which
may be edited by making additions (INSert), changes
(REPlace), or deletions (REMove). Note only the first three
characters are required.
Inserted lines will be placed after the designated line number
of the default presentation. If the designated line number
has been removed, the line to be inserted will not be added.
There is no limit to the number of lines which may be
inserted. When several lines are inserted after a specified
line, such as in the Processing Sequence Box, they will
Other Docs
Known Problems
Unisec User Guide
appear in the same order in which they occur in the input

parameter file.
Centering of text within the Office Box is performed
automatically by the program. Centering of text in the Title,
Field Information, Processing Sequence, and Display
Parameters Boxes is at the discretion of the user.
Types of formats
The operations INSert and REPlace have two formats. In the
short format, the command is specified only once with the
range of line numbers to act on. In the long format, the
command is specified once for each line to be modified. The
short format is easier to use and more efficient but the choice
of format is left to the user.
Format to INSERT after line n with following line(s)
box, INS = n
(text, size)
(...
(...
Where:
box =Side label box id-- OFFICE, TITLE, FIELD, PROCESS
or FILM.
n =referenced line number in the default side label
presentation. Default = none
text =the text string to be written with reference to the
specified line. If the text string contains commas,
parentheses or leading blank spaces, then it must be
completely enclosed in single quotes. Default = none.
size = the height of the characters in inches. Default =
varies for each 'box'.
These references are the same for all boxes of the side label.
or
box, INS = n(text 1, size)
sequence after line n.
Other Docs
would insert lines text 1, text 2 and text 3 in
Known Problems
Unisec User Guide
Format to REPLACE lines n through m with following

lines
box, REP = n (,m)
(text,size)
.
....
)
(...
)
or
box, REP = n(text, size)
box, REP = n+1(text, size)
box, REP = m(text, size)
Format to REMOVE lines n through m

box, REM = (n TO m) or (list)
Where:
list = specifies a list of line numbers to be removed.
The format for this list is identical to that used for entity lists.
Examples
PROCESS,INS = 1
( FIRING SWITCH CORRECTION -51 MS)
( FOLD : 52 DATUM: SEA LEVEL)
or
PROCESS,INS = 1( FIRING SWITCH CORRECTION -51MS)
PROCESS,INS = 1( FOLD : 52 DATUM: SEA LEVEL) will insert the
specified lines after line 1 in the PROCESS box.
FIELD,REP = 1,5
( RECORDING PARAMETERS ,0.12)
( INSTRUMENTS <tab> DFS V)
or
FIELD,REP = 1( RECORDING PARAMETERS ,0.12)
FIELD,REP = 2 INSTRUMENTS <tab> DFS V)
FIELD,REM = (3 TO 5) will replace lines 1 through 5 in the FIELD box
with the specified lines.
FILM,REM = (3 TO 6)
or
FILM,REM = (3,4,5,6) will remove lines 3 through 6 of the FILM box.
Other Docs
Known Problems
Unisec User Guide
Side Label Text Formatting

The side label contents may be formatted with respect to
fonts, text size, tabbing, and justifcation. This section
provides instructions as well as examples of formatted side
label text.
Format
(<justify><font%><
text
>, size)
where:
justify =! (exclamation mark) to indicate centered text
font% =desired font index number followed by % (percent
symbol). Font index 20 would be coded as 20%. See section
CGM File Specifications in the Input/Output Specification
section for the supported font list.
Text =desired text string with embedded tabs.
size = desired text size in inches.
Examples
For the Title Box, the following information and formatting is
desired:
LARSON SOFTWARE TECHNOLOGY
11111 Wilcrest Green Drive
Suite 225
Houston, Texas 77042
PROJECT
Western Kentucky Seismic Zone
would be coded as:
TITLE,REPLACE=1,999
(!19%LARSON SOFTWARE TECHNOLOGY,.2)
(!19%11111 Wilcrest Green Drive,.15)
(!19%Suite 225,.15)
(!19%Houston Texas 77042,.15)
(!19%,.15) <-------------Inserts a Blank Line
(!19%PROJECT,.2)
(!19%Western Kentucky Seismic Zone,.15)
(22%,.05)<---------------Inserts Blank Line, sets font index and text
size all text to follow unless text is formatted.
Other Docs
Known Problems
Unisec User Guide
Editing Entity Values (EVALS)

Entity values used by the side label for the boat or spread
diagrams may be specified with the EVALS statement. Most
of these entities are used to generate the default side label
presentation, but some are also used in other areas of the
display presentation or in program calculations. Editing of
these entity values is global in the sense that if an entity to be
edited is used more than once in the display, the value for
that entity will be changed for each occurrence of the entity,
regardless of where it is used in the display. A list of entity
names which can be edited is located in Appendix C.
Format
EVALS,entity l=value 1,entity 2=value 2,...,entity n=value n
Examples
EVALS,LDIR=180,CLIE=TEXAS OIL CO.,DPSP=110
EVALS,SPAN=77.9,SPTR=224.2,NRTR=96,LOGO=TEXAS
Replacement Symbols (&) in Side Label Text

A replacement symbol (&) may be used in any of the side
label statements such as OFFICE, TITLE and FIELD to allow
for automatic extraction of variables from the input tape or
parameter file. This is a very powerful feature for generating
custom text strings to be inserted into the side label where
part of the text string is constant and part is specific to the
input data. The replacement symbol is the ampersand (&)
followed by a predefined entity name followed by one blank
space. If the ampersand is followed immediately by a space it
is interpreted literally.
Example
TITLE,REP=1(PROSPECT &PROS LINE &LINE)
If the entities PROS and LINE were 'HOT' and 'A1' in a

specific run then the text string displayed would be:
PROSPECT HOT LINE A1
Other Docs
Known Problems
Horizon and Fault Display (HORIZON)65
Unisec User Guide
Horizon and Fault Display (HORIZON)

Horizon or fault lines can be displayed overlaying the data
using this statement. The data values are either extracted
from the trace headers or supplied as user data lists. If
present in the trace header, an entity definition must exist in
the tape format definition file or be present in the parameter
file. If not available in the trace header, they can be input as a
user-supplied list of location and time pairs. The format is
the same as profiles with the end of a horizon line indicated
by negative time value. When plotting from trace headers, the
entity name HZNULL is used to specify a null horizon value.
When a null horizon value is encountered, it will not be
drawn.
Format
HORIZON,entity name 1(text,ltype,thickness,color index),entity name
2(text,ltype,thickness,color index)...
Where:
entity name = entity name for horizon data.
text = horizon title to be annotated at end of horizon.
ltype = line type to be used to draw this horizon. Valid line
types are:
blank: solid (default)
_________
1: dotted
.......................
2: dashed
______
3: dashed - dotted
_._._._.
4: dashed interspersed
with 2 dots
_ .. _.. _ .. _
thickness = line thickness in inches. Default = .02.

color index = Color index, valid numbers are from one to the
maximum color index in the color table. Default = black.
Examples
HORIZON,HORZ1,HORZ2,HORZ3,HORZ4 causes 4 horizons to be
drawn using a solid black line. The data values would be extracted from
Other Docs
Known Problems
Horizon and Fault Display (HORIZON)66
Unisec User Guide
the trace headers.

HORIZON,H1(HORIZON 1,,.03,1)
H1 DATA, DP
5,100,16,110,25,120,27,125,33,132
HORIZON,H2(HORIZON 2,,.03,2)
H2 DATA, DP
5,200,16,210,25,220,27,225,33,-232,40,240,45,238,50,235 causes 2
horizons to be displayed from the supplied location and time lists using
solid lines in two different colors.
Horizon Color Table

The PARMS keyword named HCDNAME is used to specify a
separate color table for horizons. Color numbers specified on
the HORIZON statement now reference that color table rather
than the seismic color table specified by the CDNAME
keyword. This also causes a separate color scale to be plotted
just below the seismic color scale and annotated from the
horizon titles that are assigned by the user. If they are not
present then the entity name is used.
Other Docs
Known Problems
Input/Output Specifications67
Unisec User Guide
Input/Output Specifications
This group of keywords defines the input tape format and the
output plotter specifications. Details concerning the tape
format definition file may be found in Appendix E.
Input Tape Specifications (TAPE)

The TAPE statement defines the input tape specifications. It
will usually be present in the tape format definition file, but
may also appear in the input parameter file. The format for
these keywords is as follows:
TAPE,keyword 1=value l,keyword 2=value 2,...,keyword n=value n
Keywords
RECTYP = V, F or H. Denotes if the seismic data consists of variable length (V), fixed length (F) or header (H)
records. The number of reel headers with the exact byte
count of each is to be specified. The H format implies
that the byte count for the record is available only in the
header and not in both the header and the footer, as in
the F format. Note that this is a system feature and is
not available on some systems. Default is V.
NRH = i Number of reel headers of length TPEHL. Range
is integers such that 0 <= NRH <= 9. Default is 0 (none).
NRH(I) = i Number of reel headers of length TPEHL(I) for
2 <= I <= 5. Range is integers such that 0 <= TPEHL(I) <=
20. Default is 0.
TPEHL = i The length of the first NRH reel headers in
bytes. Range is integers such that 80 <= TPEHL <= 8192.
Default is 0.
TPEHL(I) = i The length of NRH(I) reel headers in bytes.
Range is integers such that 80 <= TPEHL(I) <= 8192.
Default is 0.
TRHL = i The trace header length in bytes. Range is 0
<= TRHL <= 1024. Default is 240.
TRID = a Trace header ID. This value which may be
from 1 to 8 characters is matched against the entity
name HCODE to identify a trace. If blank then any
Other Docs
Known Problems
Unisec User Guide
record following the reel headers is assumed to be a

trace.
CTRID = a Color trace header ID. This value which may
also be from 1 to 8 characters is matched against the
entity name HCODE to identify a trace. It is applied
before the TRACE statement to select which traces are to
be considered for processing. This keyword is applicable
only for the dual trace color input mode and must be
used with TRID.
STYPE = a Sample type. The options are:
I: integer
R: real
C: color (Interleaved samples)
Default is R.
RCODE = a Real number (floating point) format. The
options are:
blank: IBM
N: native to host CPU
Default is blank.
BPS = r The number of bytes per sample. Range is real
numbers such that 0.5 <= BPS <= 4. Default is 4.
ACODE = a The format for the alphanumeric characters. The options are:
E: EBCDIC (IBM tapes)
A: ASCII (most non-IBM tapes)
Default is E.
RHID = a Reel header ID. This value which may be from
1 to 8 characters is matched against the entity RHCODE
to identify a reel header. If blank then the first record on
tape is assumed to be a reel header.
VAXFILE indicates that the input file is in VAX byte
order.
CINPMODE = a Indicates color trace data input mode.
The options are:
T: dual trace color input mode
F: dual file color input mode
blank: single trace color input mode
Other Docs
Known Problems
Unisec User Guide
Default is single trace color input mode.

Examples
TAPE,NRH=2,TRHL=320,STYPE=R,BPS=4,ACODE=E specifies 2 reel
headers, trace header length is 320 bytes, sample format is real and the
alpha information is in EBCDIC.
TAPE,NRH=1,TPEHL=3200,NRH(2)=1,TPEHL(2)=400,TRHL=240,
STYPE = R
TAPE,BPS=4,ACODE=E,RCODE=N,VAXFILE is for a SEGY-like tape
format except that the floating point values would be native to host cpu,
and the byte order is VAX, which means if the host is a VAX then the
floating point values will be expected in VAX FP and the byte order will be
VAX.
TAPE,RECTYP=F
TAPE,NRH=1,TPEHL=4976,NRH(2)=1,TPEHL(2)=1419 denotes that
in the fixed record type format, there is one record of length 4976 bytes
and one record of length 1419 bytes.
Defining Entity Specifications (DEFINE)

DEFINE is used to specify the location and attributes of
entities. The tape format definition file contains a DEFINE
statement for each entity. You can override entries in the tape
format definition file by specifying the appropriate entity and
its new definition in the input parameter deck. In addition,
you can temporarily add definitions to the library file for the
specific data being plotted by including the new entity
definition in the input parameter deck.
Format
DEFINE,entity=(type,position,length,source,record)=(expression)
Where:
entity = entity name to be defined.
type = data type:
I: integer
R: real
A: alphanumeric
position = starting byte position beginning with byte one.
length = length in bytes.
source = source location of the data:
Other Docs
Known Problems
Unisec User Guide
R: Reel Header
S: Auxiliary Reel Header (Statistics Vector)
T: Trace Header
F: User-Defined Function
C: Program Calculated Function (The position within the
program contains the function.)
U: User-Specified Values Using EVALS Statements
record = reel header record number beginning with one. This
is applicable only when there are multiple reel headers.
Default is 1.
expression = optional arithmetic expression for user-defined
functions. These functions may contain other entity names,
constants, and operators. If other entity names are used in
the expression, they must be previously defined to the
program. The method for evaluation of the expression follows
FORTRAN programming language rules. The valid operators
are:
^ = exponentiation, * = multiplication,
/ = division, + = addition,
- = subtraction, ( ) = nesting,
% = modulus function
Examples
DEFINE,DP=(I,15,4,T) defines an entity name called DP starting at byte
location 15 in the trace header, and having a length of 4 bytes. The entity
value is an integer.
DEFINE,ET=(R,1,4,F)=2000*(ED+DC-EL)/VD-VT defines an entity
name called ET, which is a real number 4 bytes in length and is
calculated as a function of other entities. These entities, ED, DC, EL, VD,
and UT must have been previously defined to the program or an error will
occur.
Plotter Specifications
The following statements and their associated keywords are
used to specify the output plotter attributes.
Other Docs
Known Problems
Unisec User Guide
Electrostatic plotter attributes (ESP)

Format
ESP,keyword l=value l,keyword 2=value 2,...,keyword n=value n
Keywords
DPI = r The number of dots per inch. Permissible values
are real numbers such that 80 <= DPI <= 400.
Note that this value must match the actual dots per inch
of the target plotter otherwise the plot will not be true to
scale. For example, specifying DPI = 400 when the
plotter is actually 200 dots per inch will double the size
of the plot. Default is 200.
FRMHT = r Frame height in inches. This is the same as
the effective plotting width. Permissible values are real
numbers such that 10.24 <= FRMHT <= 40.96. Care
should be taken not to specify a value greater than the
width of the paper you are plotting with, otherwise the
data may wrap around on the plot, yielding undesirable
results. Default is 20.48.
LASERDOT Plotter Attributes (LSR)
Format
LSR,keyword 1=value 1,keyword 2=value 2,...,keyword n=value n
Keywords
VDPI = r The number of dots per inch in the vertical
direction. Permissible values are real numbers such that
100 <= VDPI <= 800. Default is None.
HDPI = r The number of dots per inch in the horizontal
direction. Permissible values are real numbers such that
100 <= VDPI <= 800. It is recommended that HDPI/TPI =
an integer, otherwise gaps will appear between the seismic traces. Default is None.
RES = a The generic resolution level to be used.
FRMHT = r Frame height in inches. This is the same as
the film width. Permissible values are real numbers such
that 10.24 <= FRMHT <= 42.0. Default is 40.96.
Other Docs
Known Problems
Unisec User Guide
CGM (Computer Graphics Metafile) File Specifications

The CGM is a standard for graphical database specification
designed to serve a wide range of applications. It sets the
standard for the syntax of graphical elements, such as lines,
characters, fill areas, points, colors, and markers. Since the
CGM output in Unisec conforms to this standard, it makes
the output very portable. For example, the CGM can be
created on any computer system and ported to another for
plotting.
The following keywords control the output of the CGM files.
The default values will produce an output as before.
Format
CGM,keyword 1 =value 1,keyword 2 =value 2,...,keyword n = value n
Keywords
PACKSAM = i Sets the number of bytes per sample in
the CGM. Values are 1 (8-bit) or 2 (16-bit). Default is 2.
DRWMDE = a Causes the drawing mode in the CGM to
be opaque or transparent. Values are OPQ or TRN.
Default is TRN.
FONTINX = i Font index for section annotation. Permitted values are any font number from the following table
Default is 1.
FONTINX2 = i Font index for default side label annotation. Permitted values are any font number from the following table. Default is 2.
Note: You need to determine the fonts available to you in
the rasterizing software.
Other Docs
Known Problems
Font Number
Other Docs
Unisec User Guide
Font Name
1.
HERSHEY:SIMPLEX_ROMAN
2.
HERSHEY:GOTHIC_ITALIAN
3.
HERSHEY:GOTHIC_ENGLISH
4.
HERSHEY:GOTHIC_GERMAN
5.
HERSHEY:TRIPLEX_ITALIC
6.
HERSHEY:TRIPLEX_ROMAN
7.
HESHEY:COMPLEX_CYRILLIC
8.
HERSHEY:COMPLEX_ITALIC
9.
HERSHEY:COMPLEX_GREEK
10.
HERSHEY:COMPLEX_SCRIPT
11.
HERSHEY:COMPLEX_ROMAN
12.
HERSHEY:DUPLEX_ROMAN
13.
HERSHEY:SIMPLEX_GREEK
14.
HERSHEY:SIMPLEX_SCRIPT
15.
PipMonoSansSerif
16.
HERSHEY:CARTOGRAPHIC_GREEK
17.
HERSHEY:CARTOGRAPHIC_ROMAN
18.
Times-Roman
19.
Times-Italic
20.
Times-Bold
21.
Times-Bold-Italic
22.
Helvetica
23.
Helvetica-Italic
24.
Helvetica-Bold
25.
Helvetica-Bold-Italic
26.
Courier
27.
Courier-Bold
28.
Courier-Italic
29.
Courier-Bold-Italic
Known Problems
Other Docs
Unisec User Guide
Known Problems
Identification Banner (BANNER)75
Unisec User Guide
Identification Banner (BANNER)

The BANNER statement allows you to display a vertical
identification strip at both ends of a plot to facilitate
recognition. The banner consists of a text string, which may
include embedded replacement symbols to allow access to
entity values from the tape headers and other sources. The
size and thickness of the BANNER text can also be specified
optionally.
Format
BANNER,(size),text
Where:
size = size (height) of BANNER text. Default is 0.1 inch.
text = a text string, with or without embedded replacement
symbols. The first character in the text string should not be a
left parenthesis. The replacement symbol is the ampersand
(&) and must be followed by a predefined entity name
followed by one blank space. Text may continue past 80
columns by placing a plus sign (+) at the end of a line and
continuing on the next line in column 2.
Example
BANNER,FINAL STACK &PROS PROSPECT HOUSTON PROCESS
C+
ENTER REEL: &REEL CREATED: &CDATE &CTIME PROCESSOR:
JOHN Q. DOE PLOTTED: &DATE &TIME
Multi-line banners can be created by using multiple BANNER

statements.
Other Docs
Known Problems
Subend (SUBEND)76
Unisec User Guide
Subend (SUBEND)
The SUBEND option permits multiple plots to be generated
from the same input tape using one parameter file and job
execution. The input parameter file used to generate n plots
consists of one MAIN deck and n SUBEND decks (see
illustration). The parameters used to generate the first plot
consist of the MAIN deck plus the first SUBEND deck.
Parameters for the second plot consist of the MAIN deck and
the second SUBEND deck. In a similar manner, the
parameters for the nth plot consist of the MAIN deck plus the
nth SUBEND deck. Therefore, it is recommended that the
MAIN deck consist of those keywords and parameters that
will be common to all the plots, while each SUBEND deck
should contain those keywords and parameters that are
unique to each individual plot.
___________________________
|
|
|___________________________
MAIN DECK
SUBEND
____________________________
|
|
|____________________________
1st SUBEND DECK
SUBEND
____________________________
|
|
|____________________________
2nd SUBEND DECK
SUBEND
.
.
.
SUBEND
Other Docs
Known Problems
Subend (SUBEND)77
Unisec User Guide
____________________________
|
|
|____________________________
nth SUBEND DECK
END
When the MAIN deck and each SUBEND deck are combined,
a number of rules are followed by the program to construct
each of the n parameter files. If the same PARMS keyword
appears in both the MAIN and SUBEND decks, the value in
the SUBEND deck will take precedence and override the
value in the MAIN deck. All non-PARMS statements are
additive when the MAIN and SUBEND decks are combined.
Each statement will specify a separate set of conditions,
which, if satisfied, will result in the appropriate action being
taken. This additive feature of non-PARMS statements,
therefore, results in an "or" logical relationship (see Entity
List Logic in General Notes on the Input Parameter File); that
is, if either the condition on the first or subsequent
statements is satisfied, then the appropriate action will be
taken. Some examples of the SUBEND option appear on the
following pages.
Example 1
PARMS,PROS=F1624,LINE=GP81#65
PARMS,TPI=10,IPS=5.00,GAIN=8.0,DISP=WVA
PARMS,START=0,SIDEL=R,PDIR=L
SUBEND
TIC,DP=(l05 TO LAST BY 20)
LABEL,DP=(105 TO LAST BY 20),EX
TITLE,REPLACE=1('LINE 65 ',.2,.02)
TITLE,REPLACE=2('BRUTE STACK',.2,.02)
TITLE,REPLACE=3('ANY PROSPECT',.2,.02)
TITLE,REPLACE=4('A1624',.2,.02)
TITLE,REPLACE=5('GULF OF MEXICO',.2,.02)
SUBEND
PARMS,TYPE=DP
TITLE,REPLACE=1('LINE 65',.2,.02)
TITLE,REPLACE=2('NMO CORRECTED DP GATHERS',.2,.02)
END illustrates the structure of a parameter file containing the SUBEND
feature. This parameter file would generate two plots consisting of the
following parameters:
Plot 1
PARMS,PROS=F1624,LINE=GP81 #65
Other Docs
Known Problems
Subend (SUBEND)78
Unisec User Guide
PARMS,START=0,SIDEL=R,PDIR=R
TIMING,(1000,500,100,0)
LABEL,DP=(105 TO LAST BY 20),EX
TITLE,REPLACE=l('LINE 65',.2,.02)
TITLE,REPLACE=2('BRUTE STACK',.2,.02)
END
Plot 2
PARMS,PROS=F1624,LINE=GP81#65
PARMS,START=0,SIDEL=R,PDIR=L
TIMING,(1000,500,100,0)
TITLE,REPLACE=1('LINE 65',.2,.02)
TITLE,REPLACE=2('NMO CORRECTED DP GATHERS',.2,.02)
END
Example 2
PARMS,TYPE=SECTION,TPI=12,IPS=3.0,GAIN=6.4
SUBEND
SUBEND
PARMS,INV
END is an example of a SUBEND option used to plot both polarities of
the seismic data.
Example 3
PARMS,TYPE=SECTION,GAIN=4.7
SUBEND
PARMS,TPI=25,IPS=2.5
SUBEND
PARMS,TPI=12.5,IPS=5.0
END is an example of a SUBEND option used to plot seismic data at
different scales.
Example 4
PARMS,TPI=10,IPS=3.0
TRACE,DP=(200 TO 400 BY 1)
SUBEND
PARMS,GAIN=4.0
SUBEND
PARMS,GAIN=5.0
SUBEND
PARMS,GAIN=6.0
SUBEND
PARMS,GAIN=7.0
Other Docs
Known Problems
Subend (SUBEND)79
Unisec User Guide
SUBEND
PARMS,GAIN=8.0
END shows how SUBEND can be used to perform a gain scan to
determine the optimum gain for a plot.
Example 5
PARMS,TYPE=SECTION,TPI=10,IPS=4.0,GAIN=8.0,PEAK=2.0
PARMS,SIDEL=R,PDIR=R,VMA=14
TVLIST,VCASE
PROFILE,#ISO=(2000 TO 5000 BY 1000)
TRACE,DP=(FIRST TO LAST)
SUBEND
SUBEND
SUBEND
END shows how SUBEND can be used to generate multiple copies of
the same plot. Three copies will be generated. (An easy rule to
remember is that n SUBEND decks will generate n plots.)
Example 6
PARMS,PROS=F6329,LINE=ST3DAPI
PARMS,TPI=l0,IPS=5.00,GAIN=8.0,DISP=WVA
PARMS,START=0,SIDEL=R,PDIR=R
TIMING,(1000,500,100,0)
FIELD,REPLACE= 1 (,17)
('SHOT BY
HOUSTON CONTRACTOR')
('SHOT FOR
TEXAS OIL')
('RECORDING SYSTEM
DFS V
')
(' FIELD FILTERS
OUT/OUT
')
(' PARAMETERS
2MS. SAMP RT FOR 4 SEC')
(' TAPE FORMAT
SEG-Y
')
(' POLARITY
COMPRESSION=NEGATIVE ')
('SOURCE
DYNAMITE
')
(' PATTERN
SINGLE 160 FT. HOLE ')
(' CHARGE SIZE
10 LBS.
')
(' SP SPACING
330 FT.
')
('GEOPHONES
MARK PRODUCTS L-15B ')
(' ARRAY
12 PHONES INLINE
')
(' STATION SPACING 330 FT.
')
('SPREAD
END-ON
')
(' DIMENSIONS
SP-330-7920 FT.
')
(' DIRECTION
WEST TO EAST
')
FIELD,REMOVE=(18)
PROCESS,REPLACE=1(' 1 FIELD TAPE COPIED 1600 BPI TO 6250
BPI')
PROCESS, INSERT=1
(' 2 DEPHASING OPERATOR GEOPHONES
')
(' 3 DEPHASING OPERATOR INSTRUMENT
')
(' 4 LEVEL
')
(' 5 TIME-VARIANT DECON
')
(' PREWHITENING
5%
')
(' OPERATOR LENGTHS 80 MS.
')
(' PREDICTION DISTANCES
')
Other Docs
Known Problems
Subend (SUBEND)80
Unisec User Guide
('
0 TO 1949 MS. ALPHA = 2 MS. ')
('
1950 TO 2699 MS. ALPHA = 6 MS. ')
('
2700 TO 4000 MS. ALPHA = 12 MS. ')
(' 6 FILTER
10-15-55-65 HZ ')
(' 7 VELOCITY ANALYSIS 24 TRACE V-PLOTS ')
('
REFERENCED TO CHARGE')
(' 8 NMO CORRECTION
FROM CHARGE
')
(' 9 ELEVATION CORRECTION
')
(' DATUM
3200 FT.
')
(' VCD
6000 FT./SEC. ')
('10 RESIDUAL STATICS
')
(' SURFACE CONSISTENT COMP OF 5095 RUNS ')
(' STRUCTURE CURVE
AVG OF 25 STATIONS')
(' CORRELATION WINDOW 600-1200 MS. ')
(' AUTOMATIC CDP TYPE ENHANCE; RUN #322 ')
(' REFERENCE TRACE
9 CMP MIX
')
(' MAXIMUM SHIFT
+ OR - 8 MS. ')
('11 VDP STACK
RUN #322X
')
(' SCALING FACTOR
1/SQRT N
')
('12 FILTER
10-15-55-65 HZ ')
('14 POST STACK GAIN
APPGAIN FUNCTION ')
('15 DISPLAY
')
(' COMPRESSION RATIO 3 TO 5 AT 1000 MS.')
(' POLARITY
COMPRESSION=WHITE ')
(' SCALE
32 TRACES/MILE ')
(' DATE
5/83
')
SUBEND
TRACE,DP=(114 TO 226)
TIC,DP=(117 TO 217 BY 10,226)
LABEL,#DP=(117 TO 217 BY 10,226),GRID-Y
GRID-Y DATA=(110 TO 10 BY -10,1)
TITLE,REPLACE=1 (,5)
(' PERMIAN BASIN ',.2,.02)
(' FINAL STACK ',.2,.02)
(' 3D INLINE 2',.2,.02)
(' TEXAS CO., TX. ',.2,.02)
('G6329',.2,.02)
SUBEND
TIC,DP=(343 TO 443 BY 10,452)
('PERMIAN BASIN',.2,.02)
('FINAL STACK',.2,.02)
('3D INLINE 4',.2,.02)
('TEXAS CO., TX.',.2,.02)
('G6329',.2,.02)
SUBEND
TIC,DP=(569 TO 669 BY 10,678)
Other Docs
Known Problems
Subend (SUBEND)81
Unisec User Guide

(' 3D INLINE 6',.2,.02)
(' TEXAS CO., TX.',.2,.02)
SUBEND
TIC,DP=(795 TO 895 BY 10,904)
GRID-Y DATA=(ll0 TO 10 BY -10,1)
(' 3D INLINE 8 ',.2,.02)
(' TEXAS CO., TX. ',.2,.02)
SUBEND
TRACE,DP=(1018 TO 1130)
TIC,DP=(1021 TO 1121 BY 10,1130)
(' 3D INLINE 10',.2,.02)
(' TEXAS CO., TX. ',.2,.02)
SUBEND
TRACE,DP=(1244 TO 1356)
TIC,DP=(1247 TO 1347 BY 10,1356)
(' 3D INLINE 12',.2,.02)
(' TEXAS CO., TX.',.2,.02)
END is an example of a parameter file using SUBEND to plot several
lines of a 3D file that is stored on one tape.
Other Docs
Known Problems
End Statement (END)82
Unisec User Guide
End Statement (END)

The last line in every input parameter file must be an END
statement with the letter E in column one. Additional
statements may be present after the END statement, but they
will be ignored.
Other Docs
Known Problems
Color Plotting83
Unisec User Guide
Color Plotting
Color display modes
There are two color display modes for seismic traces:
Color Background: a color trace is displayed behind the
wiggle trace. The color trace data is either derived from
the same trace data used to draw the wiggle or a second
source. Each sample is colored with a rectangle equal to
one trace in width and one sample in height. This mode
is sometimes referred to as Variable Density color.
Color VA fill: the wiggle trace is color VA filled in either/
or peaks and troughs. Like background color fill, the
color trace data is either derived from the same trace
data used to draw the wiggle or a second source.
In both modes the wiggle is displayed in black as a
conventional wiggle trace. The color display modes are
controlled by the DISP keyword on the PARMS statement:
Examples
PARMS, DISP=WCB produces a black wiggle with color background.
PARMS, DISP=WCPT produces a black wiggle with color VA fill of the
peaks and troughs.
PARMS, DISP=CB produces a color background only, no wiggles.
Color Trace Data Scaling (CCLASS)

The CCLASS allows you to specify a relationship between
ranges of trace data values and colors plotted. The class
intervals are automatically annotated on the color scale.
CCLASS is optional when the auto scaling (AUTOSC) function
is used. In this case, if the CCLASS is omitted, the minimum
and maximum is automatically derived from the trace data.
Format
CCLASS, title = (min TO max [BY interval])
Where:
title = color scale title (maximum 40 characters).
min = minimum data value.
Other Docs
Known Problems
Color Plotting84
Unisec User Guide
max = maximum data value.

interval = optional increment for interval data values from
min to max, if increment is not specified then range of
values is evenly distributed over the number of colors
available in the selected color table.
Example
CCLASS, COLOR AMPLITUDE = (500 TO 3500) causes the following
colors to be assigned to trace data values:
Color Number
Range
< 500
500 - 1000
1000 - 1500
1500 - 2000
2000 - 2500
2500 - 3000
3000 - 3500
> 3500
This example assumes that the number of colors in the

selected color table is 8.
Color Scale
On both sides of the seismic display a color scale (legend) is
displayed showing the color table selected. The scale begins
at the top with color number 1 and continues downward until
all the colors (up to 64) have been displayed.
Color Scale Annotation
If the CCLASS is used, the COLOR SCALE is automatically
annotated using the title and list values from the CCLASS
statement. Otherwise, the title and values will be accessed via
the entity name CSCLT (title) and CSCLA (values). In this
way, they may be extracted from tape or manually entered as
follows:
Format
EVALS, CSCLT = title, CSCLA
Other Docs
Known Problems
Color Plotting85
Unisec User Guide
CSCLA DATA
text 1, text 2, ............ text n
Where:
title = title string (maximum 40 characters), plotted
vertical alongside the color scale.
text = text (maximum 40 characters) to be placed by each
color square.
Example
EVALS, CSCLT = COLOR AMPLITUDE, CSCLA
1000, 2000, 3000, 4000, 5000, 7500, 9000, 10500, 14000
Color Tables
Defining Colors (DEFINE, COLORS)
UNISEC requires a color table to translate color numbers to
combinations of the primary colors. In this table, each color
is defined in terms of the mix of primary colors used to create
each color.
Format
DEFINE, COLORS[, COLSYS=CMY]
c1,m1,y1, c2,m2,y2 .......................................................
...............................................cn,mn,yn
Where:
cn = shade of cyan to be used to create color n.
mn = shade of magenta to be used to create color n.
yn = shade of yellow to be used to create color n.
Shades range from 0 to 16 with 0 normally being the lightest
and 16 the darkest.
OR
DEFINE, COLORS, COLSYS=B
b1,b2, ..............bn
Where:
bn = shade of black, from 0 to 16.
Other Docs
Known Problems
Color Plotting86
Unisec User Guide
or
DEFINE, COLORS, COLSYS=BCMY
bl,cl,ml,yl, bl,c2,m2,y2..............................................
..............................................bn,cn,mn,yn
Where:
bn = shade of black to be used to create color n.
cn = shade of cyan to be used to create color n.
mn = shade of magenta to be used to create color n.
yn = shade of yellow to be used to create color n.
or
DEFINE, COLORS, COLSYS=RGB
r1,g1,b1, r2,g2,b2 .........................................................
.................................................rn,gn,bn
Where:
rn = intensity of red be used to create color n.
gn = intensity of green to be used to create color n.
bn = intensity of blue to be used to create color n.
Intensities of RGB range from 0 to 100 with 0 normally being
the lightest and 100 the darkest.
There may be up to 64 colors in each color table. If one line
fills up, the numbers may spill over into the next line until all
the colors are defined.
Example
1, 5, 9, 13 defines a color table of 4 colors. Note that each color is
comprised of a black component only. This type of color table is useful for
monochrome plotting and using gray scale VA fill.
DEFINE, COLORS, COLSYS=CMY
0,0,0, 0,16,0, 0,15,0, 0,13,0, 0,11,0, 0,9,0, 0,7,1,
0,16,16, 0,12,15, 0,9,14, 0,7,12, 0,5,10, 0,3,10, 0,2,10,
0,1,10, 0,0,11, 1,0,11, 2,0,10, 4,0,10, 6,0,9, 8,0,10,
10,0,11, 12,0,11, 14,0,11, 13,0,6, 11,0,4, 9,0,1, 7,0,0,
5,0,0, 3,0,0, 1,0,0
defines a color table of 31 colors. Color number 1 is
comprised of shade values of 0 for cyan, magenta and yellow, color
number 2 is comprised of shade values of 0, 16 and 0 for cyan, magenta
and yellow, color number 3 is comprised of shade values of 0, 15 and 0
for cyan, magenta and yellow and so on.
Other Docs
Known Problems
Color Plotting87
Unisec User Guide
Color Table File

This file which is normally named COLTAB.TXT is comprised
of 80 character lines, which may be created and edited by the
text editor. The file can contain several color tables, one for
each scheme to be used. For instance one scheme may be
used for colored frequency displays while another may be for
colored amplitude displays; however, only one table may be
specified per display job. Each record (line) is 80 columns
and begins in column one and may extend to column 80.
Format
***color definition name 1
DEFINE, COLORS
.
.
(color table 1)
.
.
***color definition name 2
.
.
(color table 2)
.
.
***color definition name m
.
.
(color table m)
.
.
Example
***AMP
DEFINE, COLORS=
0,0,0, 0,16,0, 0,15,0, 0,13,0, 0,11,0, 0,9,0, 0,7,1,
0,16,16, 0,12,15, 0,9,14, 0,7,12, 0,5,10, 0,3,10, 0,2,10,
0,1,10, 0,0,11, 1,0,11, 2,0,10, 4,0,10, 6,0,9, 8,0,10,
10,0,11, 12,0,11, 14,0,11, 13,0,6, 11,0,4, 9,0,1, 7,0,0,
5,0,0, 3,0,0, 1,0,0
***POLAR
DEFINE, COLORS=
0,0,0, 0,13,0, 0,9,0, 0,6,0, 0,3,0, 0,1,0, 0,0,0,
1,0,0, 3,0,0, 6,0,0, 9,0,0, 13,0,0
***GREY
1, 5, 9, 13
END defines two color tables, the first named AMP is comprised of 31
colors and the last named POLAR of 12.
Other Docs
Known Problems
Color Plotting88
Unisec User Guide
Trace Data Color Input

Color Input Modes
UNISEC allows color trace data to be specified in one of three
modes. They are single trace, dual trace, or dual file mode,
where:
T = dual trace color input mode
F = dual file color input mode
blank = single trace color input mode (default)
Example
TAPE, STYPE=R, BPS=4, CINPMODE=F indicates the seismic color
input is in the dual file mode i.e., 1 file for seismic amplitude and 1 for
color, and that the samples are in real*4 format.
Single Trace Mode

In this mode the amplitude and color information are
contained in a single trace. STYPE may be either C
(multiplexed samples) or I or R in which case conversion of
amplitude to color indices is controlled by the CCLASS
statement.
Dual Trace Mode
In this mode the amplitude is contained in one trace followed
by a second trace representing color. The conversion of
sample to colors of the second trace is controlled by the
CCLASS statement.
Dual File Mode
UNISEC allows a second file to be specified as the source of
the color trace data to be used for background and VA color
fill. The first or primary input file represents amplitude which
can be plotted as wiggle and/or VA and the second file which
is read concurrently to the first is plotted in color. Conversion
of the samples to color indices is controlled by the CCLASS
statement. The second input file must be formatted as
follows:
The file and record structure of the secondary input file
must be the same as the primary seismic input file.
Other Docs
Known Problems
Color Plotting89
Unisec User Guide
The reel and trace headers must be of the same length

and content. In other words, the values in the second
must be identical to the values in the first.
Sample formats must be the same in both files, such as
16 integer, 32 IBM real.
Trace Color Data Format
The format, length and content of the Reel and Trace headers
for color plotting is determined by the DEF.TXT file just as it
is for black and white plotting. The format of the samples is
specified by the STYPE keyword on the TAPE statement. For
color plotting, STYPE may be one of the following:
I: integer (BPS = 1 or BPS = 2)
R: real (BPS = 4)
C: color (BPS = 2 or 4)
Example
TAPE,.........STYPE = I, BPS = 2 specifies the sample format to be 16 bit
integer.
Single Trace Data Color Format (STYPE=C)

This trace data format, which can only be used in the single
trace input mode, allows for color trace data to be input
where the amplitude and color data samples are multiplexed.
The number of bytes per sample can be either 2 or 4. The 2
byte data format is as follows:
bytes 1 - m = trace header data, where m is the trace
header length
bytes m + 1 = amplitude of sample 1
bytes m + 2 = color of sample 1
bytes m + 3 = amplitude of sample 2
bytes m + 4 = color of sample 2
.
.
.
bytes m + 2n-1 = amplitude of sample n
bytes m + 2n = color of sample n
The amplitudes are signed 8 bit integers in the range of plus

or minus 256 and the colors are integers in the range of 1 to
64. These amplitudes will be plotted as a conventional black
wiggle trace with color superimposed on the wiggle trace
Other Docs
Known Problems
Color Plotting90
Unisec User Guide
either as a background fill or VA fill as specified by the

display mode (DISP) parameter.
Other Docs
Known Problems
91
Unisec User Guide
Data Specifications
This chapter contains a summary of permissible statements,
their format, and their associated keywords and parameters.
In This Chapter
Statement Summary
Unisec Parameter Range Checks and Default Values
Other Docs
Known Problems
Statement Summary92
Unisec User Guide
Statement Summary
PARMS,keyword 1=value 1,keyword 2=value 2,...,keyword n=value n
TRACE,entity=(list),entity=(list),...
SKIP,entity=(list),entity=(list),...
KILL,entity=(list),entity=(list),...
GAP,entity=(list),size
PAD,entity=(BY i)
TIMING,(heavy,medium,light,dotted)
TIMEA,(size1,thickness1),....(size4,thickness4)
SIDETIC,(heavy,medium,light,dotted)
DOWN,entity=(list),entity=(list),...
LABEL,entity=(list),entity=(list),...,(size,thickness)
LABELV,entity=(list),entity=(list),...,(size,thickness)
LABELB,entity=(list),entity=(list),...,(size,thickness)
LABEBV,entity=(list),entity=(list),...,(size,thickness)
LTIE,entity=value(text),entity=value(text),...
LTIEV,entity=value(text),entity=value(text),...
SIDEA,title,time 1,text 1,time 2,text 2,...
SYMBOL,entity=value(symbol,size,thickness),...
TEXT,entity=value(text,size,thickness),...
LEGEND,entity=value(scale,trdist,thickness)
TVLIST,entity=(list),...,(size,thickness)
TVLIST,VCASE
TVLIST,TVTD
PROFILE,profile code(parameters)=(singles list),profile code...
PROFBOT,profile code(parameters)=(singles list),profile code...
OFFICE,REPLACE=line(text,size,thickness)
OFFICE,INSERT=line(text,size,thickness)
OFFICE,REMOVE=(list)
ORMAP
EVALS,entity l=value l,entity 2=value 2,...,entity n=value n
TAPE,keyword l=value l,keyword 2=value 2,...,keyword n=value n
DEFINE,entity=(type,position,length,source)=(expression)
ESP,keyword l=value l,keyword 2=value 2,... ,keyword n=value n
LSR,keyword 1=value 1,keyword 2=value 2,...,keyword n=value n
SUBEND
END
Note: The TITLE, FIELD, PROCESS and FILM statements

have formats identical to that for OFFICE.
Other Docs
Known Problems
Parameter Range Checks And Default Values93
Unisec User Guide
Parameter Range Checks And Default Values
Other Docs
PARMS
Keyword
Data
Type
ADDR
BIAS
BLANK
BLKDOT
DEBUG
DISP
EDIT
ENDSPC
GAIN
INPUT
A
R
R
L
L
A
L
R
R
A
INV
IPS
LINE
LSTDOT
MAN
MAXTVB
METRIC
MIRROR
MXBLKS
MXLTIE
NOVLP
OUTPUT
PANEL
PDIR
PEAK
PROS
RDERR
RECL
REFAMP
SIDEL
SR
START
TPI
TRCMOD
TVHEAD
TVLDOT
TVLFMT
TYPE
L
R
A
L
A
I
L
L
I
I
I
A
L
A
R
A
A
I
R
A
R
I
R
I
A
L
A
A
VMAX
VSCALE
WIGMOD
WIGTHICK
Range of
Permissible
Values
Default
Value
From Tape Header
0.0
6.0
ON
OFF
WVA
OFF
2.0
0.0
First entry
in DEF" file
OFF
3.0
None
ON
From Tape Header
1
OFF
OFF
3
3
3
E
ON
L
1.5
None
None
NSAM*SR-START
16384
R
SR in Tape Header
0
12.0
1
TIME RMSV INT DEP
ON
None
None
I
R
I
Any Alphanumeric Entry

-1.5 <= BIAS <= 6.0
0.0 <= BLANK <= 6.0
ON or OFF
ON or OFF
W, WVA, WVAN, VA, VAN
ON or OFF
0.0 <= ENDSPC <= 12.0
-999.9 <= GAIN <= 999.9
Defined in "DEF" File
ON or OFF
0.001 <= IPS <= 50.0
ON or OFF
1 <= MAXTVB <= 3
ON or OFF
ON or OFF
0 <= MXBLKS <= 20
0 <= MXLTIE <= 20
1 <= NOVLP <= 50
E, G, L, P, S
ON or OFF
L, R
0.0 <= PEAK <= 6.0
KILL, LAST
1 <= RECL <= 50000
0 <= REFAMP <= 1000000
L, R, LR, NO, ONLY
0.25 <= SR <= 100.0
-32767 <= START <= 32767
2.0 <= TPI <= 200.0
Any integer
ON or OFF
INT, DEP
Defined by "TYPE" File
1 <= VMAX <= 200
1 <= VSCALE <= 10000
1 <= WIGMOD <= 100
.001 <= WIGTHICK <= .01
.005
12
0
1
Known Problems
Parameter Range Checks And Default Values94
Note:
A = Alphanumeric
I = Integer
L = Logical ON/OFF
R= Real Number
Statement
Data
Type
Range of Permissible
Entries for Parameters
TIMING
GAP
PAD
TIC
I
I
I
-32767 <=
-32767 <=
-32767 <=
-32767 <=
1 <=
1 <=
1 <=
ESP
Keyword
Data
Type
Range of Permissible Values
DPI
FRMHT
R
R
80.0 <= DPI <= 400.0

8.0 <= FRMHT <= 71.6820.48
LSR
Keyword
Data
Type
Range of Permissible Values
Default
Value
VDPI
HDPI
RES
FRMHT
R
R
A
R
100 <= VDPI <= 800

100 <= HDPI <= 800
LO, MED, HI, HY
10.24 <= FRMHT <= 42.0
None
None
MED
42.0
CGM
Keyword
Data
Type
Range of permissible Values
Default
Value
PREC
PACKSAM
DRWMDE
TYPE
I
I
A
A
16 or 32
1 or 2
OPQ or TRN
ZEH or VERS
16
2
TRN
ZEH
Note:
Other Docs
Unisec User Guide
HEAVY <=
MEDIUM <=
LIGHT
<=
DOTTED <=
SIZE
<=
i
<=
increment <=
Default
Value
32767
32767
32767
32767
50
50
1000
1000
500
100
1
10
Default
Value
200
A = Alphanumeric
I = Integer
L = Logical ON/OFF
R = Real Number
Known Problems
95
Unisec User Guide
Appendix A
Default Side Label Presentation
The side label is divided into a number of different boxes,
each of which contains information related to the acquisition
or processing of the data, or to the prospect itself. A default
side label presentation has been designed to provide a
minimum amount of this information. Users may modify the
default presentation by using an EVALS statement to override
values and information which are read from the input tape
header. In addition, the statements OFFICE, TITLE, FIELD,
PROCESS, and FILM may be used to edit individual lines of
text within the side label.
Note: Entries in parentheses are taken from the input tape
header or from EVALS statements in the input parameter file.
Default Office Box Presentation
Line #
Text
Size
HOUSTON
0.15
Default Title Box Presentation

Line #
Text
Size
1
2
PROS = (Prospect)
LINE = (Line Number)
0.20
0.20
Default Field Information Box Presentation

The three default Field Information Box Presentations are as
follows:
Case 1: SURF = M (Marine Data)
Line
#
Text
1
2
3
4
5
6
7
Other Docs
SHOT BY
(SDAT)
SHOT FOR
RECORDING SYSTEM
FIELD FILTERS
TAPE FORMAT
PARAMETERS
Size
(CONT) (CREW)
.01
(CLIE)
(RSYS)
(FILT)
(TFMT)
(SR) MS FOR SECONDS SEC
.01
.01
.01
.01
.01
.01
Known Problems
96
Unisec User Guide
8
9
10
11
12
13
14
15
16
SOURCE
SP SPACING
GEOPHONES
CONFIGURATION
STATION SPACING
SPREAD
DIMENSIONS
DIRECTION
MARINE (SOUR)
(SPSP) DIST
(GTYP)
(GCHA) PHONES OVER (TRSP)DIST
(TRSP) DIST
(CHAN) TRACE TYPE SPREAD
(SPTR) DIST SP TO NEAR TRACE
(CABL) DIST NEAR TO FAR TRACE
LINE TO OCTANT, TRACE 1 TO (TDIR)
.01
.01
.01
.01
.01
.01
.01
.01
.01
Where:
SECONDS
ROUND (NSAM * SR / 1000)
DIST
=
=
FT if UNIT = E
M if UNIT = M
TYPE
=
=
=
STRADDLE if STYP = S
FRONT if STYP = F
BACK
if STYP = B
OCTANT
=
=
=
=
=
=
=
=
N if 337.5 <= LDIR < 22.5

NE if 22.5 <= LDIR < 67.5
E if 67.5 <= LDIR < 112.5
SE if 112.5 <= LDIR < 157.5
S if 157.5 <= LDIR < 202.5
SW if 202.5 <= LDIR < 247.5
W if 247.5 <= LDIR < 292.5
NW if 292.5 <= LDIR < 337.5
List of entity names to be defined for the MARINE diagram

NRTR
SPAN
SPTR
CABL
DCHG
DCAB
SPNRP
=
=
=
=
=
=
=
Near trace
Shotpoint to antenna spacing
Shotpoint to near trace
Spread between first and last channel
Depth of charge
Depth of cable
Shotpoint to navigation reference point
Case 2: SURF = L (Land), SOUR = VIBROSEIS or DINOSEIS

Line
#
Text
1
2
3
4
5
6
7
8
9
10
11
Other Docs
SHOT BY
SHOT FOR
RECORDING SYSTEM
FIELD FILTERS
TAPE FORMAT
PARAMETERS
SOURCE
SWEEP PARAMETERS
PATTERN
Size
(CONT) (CREW)
(SDAT)
(CLIE)
(RSYS)
(FILT)
(TFMT)
LAND (SOUR)
(NSWE) SWEEPS FOR (LSWE) SEC
AT (SWEE) HZ
(VIBR)
.01
.01
.01
.01
.01
.01
.01
.01
.01
.01
.01
Known Problems
97
Unisec User Guide
12
13
14
15
16
17
18
19
SP SPACING
GEOPHONES
CONFIGURATION
STATION SPACING
SPREAD
DIMENSIONS
DIRECTION
(SPSP) DIST
(GTYP)
(GCHA) PHONES OVER (TRSP) DIST
(TRSP) DIST
LINE TO OCTANT,TRACE 1 TO (TDIR)
.01
.01
.01
.01
.01
.01
.01
.01
Where:
SECONDS
DIST
=
=
FT if UNIT = E
M if UNIT = M
TYPE
=
=
=
STRADDLE if STYP = S
FRONT if STYP = F
BACK if STYP = B
OCTANT
=
=
=
=
=
=
=
=
N if 337.5 <= LDIR < 22.5

NE if 22.5 <= LDIR < 67.5
E if 67.5 <= LDIR < 112.5
SE if 112.5 <= LDIR < 157.5
S if 157.5 <= LDIR < 202.5
SW if 202.5 <= LDIR < 247.5
W if 247.5 <= LDIR < 292.5
NW if 292.5 <= LDIR < 337.5
(use NRTR to locate split)
List of entity names to be defined for the LAND diagram:

NRTR
SPTR
CABL
STYP
=
=
=
=
Near trace
Offset from source to near trace
Spread between first and last channel
Spread type
Case 3: SURF = L (Land), SOUR <> VIBROSEIS or

DINOSEIS
Line
#
Text
1
2
3
4
5
6
7
8
9
10
11
12
13
Other Docs
SHOT BY
SHOT FOR
RECORDING SYSTEM
FIELD FILTERS
TAPE FORMAT
PARAMETERS
SOURCE
CHARGE SIZE
PATTERN
SP SPACING
GEOPHONES
CONFIGURATION
Size
(CONT) (CREW)
(SDAT)
(CLIE)
(RSYS)
(FILT)
(TFMT)
LAND (SOUR)
(CHAR) LB. AT (DCHG) DIST
(VIBR)
(SPSP) DIST
(GTYP)
(GCHA) PHONES OVER
.01
.01
.01
.01
.01
.01
.01
.01
.01
.01
.01
.01
Known Problems
98
Unisec User Guide
14
15
16
17
18
STATION SPACING
SPREAD
DIMENSIONS
DIRECTION
(TRSP) DIST
(TRSP) DIST
LINE TO OCTANT,TRACE 1 TO (TDIR)
.01
.01
.01
.01
.01
.01
Where:
SECONDS
DIST
=
=
FT if UNIT = E
M if UNIT = M
TYPE
=
=
=
STRADDLEif STYP = S
FRONTif STYP = F
BACKif STYP = B
OCTANT
=
=
=
=
=
=
=
=
N if 337.5 <= LDIR < 22.5

NE if 22.5 <= LDIR < 67.5
E if 67.5 <= LDIR < 112.5
SE if 112.5 <= LDIR < 157.5
S if 157.5 <= LDIR < 202.5
SW if 202.5 <= LDIR < 247.5
W if 247.5 <= LDIR < 292.5
NW if 292.5 <= LDIR < 337.5
(use NRTR to locate split)
Default Processing Sequence Box Presentation

Line #
Text
Size
(Blank line)
0.10
Default Display Parameters Box Presentation
Other Docs
Line #
Text
Size
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
HORIZONTAL SCALE
VERTICAL SCALE
GAIN
POLARITY
DISPLAY MODE
PLOT DIRECTION
BIAS
ENLARGEMENT FACTOR
0.075
0.075
0.075
0.075
0.075
0.075
0.075
0.075
0.075
0.075
0.075
0.075
0.005
0.075
0.075
PROSPECT NAME
LINE
INPUT REEL
OUTPUT REEL
DATE AND TIME CREATED
Known Problems
99
Unisec User Guide
Appendix B
Orientation Map Input Format and Capabilities
The Orientation Map permits you to generate a small map at
the bottom of the side label, which is designed to illustrate
the major features of a prospect area. The map can contain
one or more of the following elements:
Seismic Lines
Latitude - Longitude Lines
Geographical or Political Boundaries
The program utilizes an equirectangular projection to correct
for the curvature of the earth's surface. The result of this
correction is that a distance of one mile or kilometer of
latitude on the map will be the same as a distance of one mile
or kilometer of longitude. This correction is exact only at the
center of the map, but for small maps (less than 30 miles of
latitude or longitude), the error at the edges of the map will
be negligible.
In addition, the program automatically scales the data so
that it fits proportionately within the width of the side label.
Optionally, seismic lines can be annotated at their ends with
the line number only, the line number and shotpoint number,
or no annotation.
The line number text can be controlled by using
ORMAP,SIZE=n, where n is in inches.
The Orientation Map is generated by the inclusion of an
ORMAP statement in the input parameter file. The elements
to be plotted within the map are specified using the T-card
format outlined below:
Columns
Description
1
2
3 - 18
20 - 26
27
Letter "T".
Blank, or may contain 1, 2, or 3 (for T1, T2, or T3 cards).
Seismic line numbe.r
Shotpoint number.
Symbol: X - to plot dashed grid lines at the specified latitude and
longitude. L - to label the seismic line number and shotpoint
number.
Longitude in decimal degrees. An implied decimal point is located
between Columns 30 and 31.
28 - 35
Other Docs
Known Problems
100
Unisec User Guide
36
37 - 43
44
45 - 80
E (East) or W (West) longitude.

Latitude in decimal degrees. An implied decimal point is located
between Columns 38 and 39.
N (North) or S (South) latitude.
Not used. Entries or data values in these columns will be ignored.
General Notes on the Input Format

1. The ORMAP statement must immediately precede the Tcards.
2. The T-card input is terminated by the occurrence of the
next statement with an alphabetic character other than the
letter T in Column one (1).
3. In order to avoid confusion with other statements, it is
strongly recommended that the ORMAP statement and Tcards be the last entries in the input deck before the END
statement.
Notes on the Seismic Line Input Format and Display

1. The program draws a straight line between all consecutive
entries that have identical line numbers. Therefore, you
should enter, at a minimum, the latitude and longitude
coordinates for the first and last shotpoints and any
inflection points along the seismic line. To prevent the
annotation from overlapping onto the seismic line, it is
necessary to enter the T-cards for an individual line with the
most northerly coordinates on the first card and more
southerly coordinates on succeeding cards.
2. The program annotates one or both ends of the seismic line
if the letter L is present in Column 27 of the first and/or last
T- cards for the line. If a shotpoint number is present in
Columns 20-26, it is annotated in addition to the line
number. If the shotpoint number is absent, only the line
number is annotated. There is no capability to annotate
locations other than the endpoints of the seismic line.
3. If there is a space conflict between two pieces of
annotation, the program edits (i.e. removes) the second piece
of annotation. This problem can be avoided to some extent by
carefully choosing which ends of the seismic lines to
annotate.
4. The program thickens a seismic line being displayed within
the map if the line number entry in Columns 3 - 19 matches
Other Docs
Known Problems
101
Unisec User Guide
exactly with the entry for the PARMS keyword LINE in the
input parameter file.
5. You may want to include the prospect number as well as
the line number in the seismic line field (Columns 3 - 19) if
two lines have the same line number, or if two vintages of
shooting are to be displayed. If you want the line being filmed
to be thickened within the map, however, you must omit the
prospect number in order for the program to make an exact
match with the LINE keyword.
Notes on Latitude - Longitude Lines

1. The required input consists of the letter X in Column 27
and the latitude and longitude values that you want to
illustrate.
2. The program draws a dashed horizontal line for the
specified latitude, and a dashed vertical line for the specified
longitude. The ends of these latitude and longitude lines are
automatically annotated with the coordinates in degrees and
minutes, rounded to the nearest minute.
Notes on Geographical or Political Boundaries

1. The only entries that are required are the latitude and
longitude coordinates in Columns 20 through 44.
2. The program connects the latitude and longitude
coordinates specified on the T-cards with straight lines in the
order in which the cards are listed in the input deck.
Therefore, you should include the beginning and ending
coordinates, as well as coordinates of locations where
inflection points occur, in the boundary that is to be drawn.
3. The program can draw multiple boundaries, but the group
of T-cards that defines each boundary must be separated by
a group of T-cards for a seismic line and/or latitudelongitude lines. This is necessary so that the program
recognizes the need to finish drawing one boundary line, "lift
the pen" so to speak, and begin drawing a new boundary line.
Other Docs
Known Problems
102
Unisec User Guide
Examples of the Orientation Map Input Format

PARMS,PROS=P4469,LINE=2
ORMAP
T
T
T 1
T 1
T 2
T 2
T 3
T 3
T 4
T 4
T 8
T 8
T 22
T 22
END
1
120
1
120
1
120
1
180
1
55
80
140
X10380
X10390
L10384
L10384
L10386
L10386
L10389
L10389
L10392
L10379
L10384
L10392
L10388
L10388
W3390
W3400
W3399
W3392
W3392
W3399
W3399
W3392
W3394
W3394
W3395
W3395
W3392
W3399
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Latitude-Longitude lines at
103.80 and 103.90 degrees
west, and 33.90 and 34.00
degrees north.
Seismic lines to be drawn
and annotated at their ends
with the line number and
shot point number.
PARMS,PROS=X02043lS,LINE=ST3D001
ORMAP
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
Other Docs
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
10
11B
11B
12A
12A
13
13
14B
X
X
X
L
L
L
L
L
L
L
L
L
L
L
L
150000E5816667N
166667E5816667N
183333E5800000N
175955E5818336N
163313E5815461N
178577E5818577N
163505E5815238N
176352E5817916N
163663E5815042N
176480E5817713N
163841E5814840N
176652E5817491N
164038E5814639N
176802E5817311N
164205E5814443N
174630E5816564N
159216E5813078N
174827E5816378N
159449E5812841N
174980E5816142N
159605E5812629N
177491E5816513N
162130E5812950N
177669E5816300N
162274E5812780N
175477E5815539N
160130E5812030N
178019E5815878N
162630E5812364N
175830E5815142N
This is a collection of T-cards

which were used to draw a map
of a 3D seismic survey. In
addition, latitude and longitude
lines have been drawn at 10
minute intervals. In many cases,
only one end of the seismic
line has been annotated
with the line number so that
the annotation will not be
llegible due to crowding.
Known Problems
103
Unisec User Guide
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
Other Docs
14B
15
15
16B
16B
17B
17B
18
18
19
19
20A
20A
21
21
22
22
23
23
24
24
25
25
26
26
27
27
28
28
29
29
30
30
31A
31A
32
32
33
33
34
34
35
35
35A
36
36
39
39
40
40
41
41
41
41
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
525
520
515
160469E5811622N
176069E5814929N
160633E5811401N
178533E5815266N
163083E5811763N
178677E5815075N
163299E5811553N
176530E5814326N
154824E5809375N
176691E5814111N
161299E5810603N
176877E5813890N
155116E5809027N
179366E5814242N
163941E5810725N
179527E5814062N
157866E5809086N
179705E5813829N
164305E5810325N
177555E5813102N
155883E5808137N
177683E5812904N
162319E5809387N
177874E5812705N
156205E5807728N
178030E5812503N
162655E5808978N
178180E5812289N
156583E5807312N
180680E5812626N
165388E5809092N
180849E5812460N
159258E5807417N
178713E5811679N
163405E5808128N
181177E5812036N
159630E5807014N
179041E5811267N
163713E5807748N
171574E5809304N
159927E5806553N
173927E5816766N
166880E5810153N
161583E5805165N
185505E5812025N
158941E5798817N
187591E5804753N
177980E5793623N
166841E5806141N
185030E5795506N
150069E5816114N
166719E5808326N
166880E5808250N
167033E5808180N
Known Problems
104
Unisec User Guide
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
510
505
500
495
490
485
480
475
470
465
460
455
450
445
440
435
430
425
420
415
410
405
400
395
390
385
167194E5808103N
167355E5808029N
167524E5807951N
167683E5807875N
167838E5807801N
167991E5807728N
168152E5807653N
168305E5807579N
168463E5807507N
168619E5807429N
168780E5807353N
168938E5807273N
169088E5807197N
169230E5807118N
169377E5807040N
169530E5806954N
169666E5806878N
169805E5806791N
169941E5806712N
170080E5806623N
170227E5806530N
170358E5806449N
170499E5806364N
170633E5806277N
170766E5806199N
170913E5806105N
These T-cards represent an inflection point whose location is not precisely known.
Therefore several shot point coordinates have been included to ensure that the
inflection is properly located on the map.
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
Other Docs
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
41
42
42
43
380
375
370
365
360
355
350
345
340
335
330
325
320
315
310
305
300
295
290
L
L
L
L
171049E5806022N
171180E5805938N
171313E5805856N
171452E5805772N
171591E5805688N
171727E5805603N
171866E5805513N
172008E5805429N
172155E5805335N
172291E5805249N
172424E5805165N
172555E5805081N
172694E5804998N
172827E5804914N
172963E5804827N
173094E5804748N
173230E5804661N
173369E5804574N
173508E5804486N
181433E5799552N
178380E5806613N
186138E5797589N
166366E5817623N
Known Problems
105
Unisec User Guide
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
T
Other Docs
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43
43A
43A
43A
43A
43A
44
44
45
45
46
46
47
47
48
48
49
49
57
330
335
340
345
350
355
360
365
370
375
380
385
390
395
400
405
410
415
420
425
430
435
440
445
450
455
460
465
470
475
480
485
490
495
499
715
600
595
590
L
L
L
L
L
L
L
L
L
L
L
L
L
L
171980E5810850N
172066E5810748N
172152E5810641N
172238E5810539N
172330E5810429N
172416E5810328N
172502E5810227N
172588E5810122N
172674E5810023N
172755E5809922N
172841E5809822N
172919E5809722N
173005E5809614N
173091E5809513N
173180E5809402N
173266E5809304N
173349E5809204N
173433E5809097N
173516E5808988N
173605E5808889N
173691E5808787N
173774E5808680N
173858E5808581N
173941E5808482N
174024E5808387N
174108E5808280N
174194E5808180N
174283E5808076N
174374E5807965N
174463E5807861N
174541E5807762N
174630E5807656N
174713E5807556N
174794E5807456N
174858E5807379N
172780E5809832N
174855E5807489N
174938E5807398N
175024E5807298N
185630E5795326N
161877E5816610N
169380E5807582N
163630E5818438N
172141E5808226N
169294E5819752N
177794E5809513N
167174E5819274N
174813E5808856N
168183E5819380N
170213E5807804N
169394E5818336N
176402E5807714N
159430E5814347N
Known Problems
106
Unisec User Guide
T 57
END
Other Docs
180366E5811814N
Known Problems
107
Unisec User Guide
Appendix C
Reserved Entity Names
The following list contains the entity names used by UNISEC
to access values that can be either on the input tape or
entered via the EVALS statement. A corresponding entry will
appear in the DEF file which will determine the actual source
of each entity.
Used by Side Label
Maximum
Entity Number of
Name Characters
ADDR
CABL
CDAT
CHAN
CHAR
CLIE
CONT
CREW
DCAB
DCHG
DPSP
FILT
GCHA
GTYP
LDIR
LINE
LOGO
LSWE
MAN
MAXS
NRTR
NSAM
NSWE
OCTANT
PROS
RSYS
SDAT
SOUR
SPAN
SPNRP
SPSP
SPTR
SPTR2
Other Docs
8
8
8
16
12
12
8
8
12
8
4
16
4
8
8
8
12
8
Type of
Characters Description
A
R
A
I
A
A
A
A
I
I
R
A
I
A
R
A
A
A
A
I
I
I
R
A
A
A
A
A
R
R
R
R
R
User's address
Cable length (near to far trace)
Tape creation date
Number of channels recording data
Charge size
Client who contracted for the data
Contractor who shot the data
Crew name or number
Depth of cable
Depth of charge
Depth point spacing
Field filters
Number of geophones per channel
Geophone type and frequency
Line direction, in degrees
Line Number
Logo name
Length of the sweep, in seconds
User's name
Maximum fold of the data
Near trace number
Maximum no. of samples per trace
Number of sweeps per shotpoint
Octant
Prospect
Recording system
Shooting date (MM/DD/YY)
Energy source
Shotpoint to antenna distance
Shotpoint to navigation point
Shotpoint spacing
Shotpoint to near trace distance
Second value for SP to near trace
distance if the SPTR distance is not
Known Problems
108
Unisec User Guide
SR
STAT
STYP
8
1
I
A
A
SURF
SWEE
TDIR
TFMT
TRSP
UNIT
8
1
8
1
A
A
A
R
A
16
equal on both sides of the shot for a

straddle spread.
Sample rate, in milliseconds
State or Country of survey
Spread (S=Straddle,B=Back,
F=Front)
Shooting surface (L=Land,
M=Marine)
Sweep frequencies
Direction of trace #1 (N, S, E, W)
Tape data format
Trace spacing
Measurement Units(E=English,
M=Metric)
Energy source pattern
A
A
A
I
A
A
I
I
I
A
A
I
I
I
I
Seismic color definition name

Seismic color scale annotation
Seismic color scale title
Group location number
Horizon color definition name
Trace header identification
Mute time in ms.
Maximum number of samples
Number of samples in each trace
Input tape name
Reel header identification
Shotpoint location
Trace status
Time of first sample in ms.
Trace header length in bytes
VIBR
Used by Trace Plotting

CDNAME
CSCLA
CSCLT
GP
HCDNAME
HCODE
MUTE
NSAM
NSAMP
REEL
RHCODE
SP
STATUS
TIME1
TRHL
8
6
40
8
8
8
8
Used by T/V Lists (If from trace headers):

NTVP
TIM1
VEL0
VEL1
I
I
I
I
Number of T/V pairs

2 through nth times
First velocity
2 through nth velocities
Note: A denotes alphanumeric entries.

R denotes real number entries.
I denotes integer entries.
Other Docs
Known Problems
109
Unisec User Guide
Appendix D
How To Plot Depth Sections
The program is written in such a way as to allow depth
sections to be plotted with the correct vertical scale
annotation. The only necessary modifications are a few
changes in the definitions for some of the keywords and
statements in the input parameter file and, therefore,
changes to the value for the corresponding keywords and
parameters.
For depth sections, it is necessary to redefine the vertical
scale from units of time to units of distance. Therefore,
milliseconds are redefined to mean feet or meters, and
seconds are redefined to mean one thousand feet or meters.
The choice of feet or meters is dependent on the units
(English or Metric) specified on the input tape and used for
the definition of the keyword SR listed below. The following
keywords or statements are affected by these changes:
SR: the sample rate of the data in feet or meters (i.e. the
distance corresponding to one sample interval). This keyword must be specified, the default value is in units of
milliseconds and will not yield correct or lucid results.
IPS: the number of inches per one thousand (1000) feet
or meters for the final plot. Acceptable values are 0 < IPS
<= 20.0, with decimal values permitted.
START: the depth at which to begin plotting trace data,
in feet or meters. Acceptable values are integers such
that 0 <= START <= 32767.
RECL: the amount of depth, in feet or meters, to be plotted. Acceptable values are 1 <= RECL <= 32767, with
only integer values permitted. This keyword must be
specified, as the default value is in units of milliseconds,
and will therefore probably not yield the desired results.
TIMING (heavy,medium,light,dotted): the interval, in feet
or meters, for timing lines of respective thicknesses and
appropriate annotation. A positive value will draw timing
lines of the appropriate thicknesses with corresponding
annotation at the indicated depth interval. A negative
value will draw a timing line of the appropriate thickness
at the indicated depth interval, but will suppress the cor-
Other Docs
Known Problems
110
Unisec User Guide
responding annotation. A value of zero will result in neither timing lines nor an annotation of that thickness
being plotted. The timing line annotation will appear in
units of kilofeet or kilometers (one thousand feet or
meters).
increment = the timing mark increment, in feet or
meters.
Default = 10
Other Docs
Known Problems
111
Unisec User Guide
Appendix E
Tape Format Definition File
The tape format definition file is stored in a library on the
host computer and consists of TAPE and DEFINE statements
grouped by tape formats corresponding to the permissible
entries for the PARMS keyword INPUT. The file is normally
created by the programmer or analyst as part of the
installation procedure, and updated by the programmer or
analyst as needed. Each line in this file can also contain user
comments/explanations for the entities after a semi-colon
(';'). The structure of the file is as follows:
***tape format name 1
TAPE
(tape statement for tape format 1)
DEFINE ; comment line 1
DEFINE; comment line 2
.
.
(entity definitions for tape format 1)
.
DEFINE
TAPE
DEFINE
.
.
.
DEFINE
TAPE
DEFINE
.
.
.
END
During program execution, the INPUT keyword entry is used

to search the tape format definition file for a match with the
tape format names. If no match is found, an error occurs and
the program terminates execution. If a match is found, the
corresponding tape format specifications and entity
definitions are used to read the input tape and assign values
to all of the defined entities. If there is no entry for the INPUT
keyword in the parameter file, the program assumes that the
default tape format is to be selected, which is the first tape
format listed in the file.
Other Docs
Known Problems
112
Unisec User Guide
Any Category 1 statement placed before the first tape format

name is considered a system default statement to be used
during each execution of the program. Category 1 statements
are statements that use a keyword input format only, and
include PARMS, TAPE, ESP, GSP, PHOTO, SCP, and HSR.
Any such system default statement can be overridden by
simply including the statement in your own parameter file.
An example tape format definition file appears on the
following pages for reference. This file, def.txt, can be found
in the directory $PROMAX_HOME/sys/exe/larson/lstbin.
HSR,HSRMEM=256
***SEGY
TAPE,NRH=2,TPEHL=400,TRHL=240,STYPE=R,BPS=4,ACO
E=E
DEF,EG =(I,41,4,T)
DEF,EL =(I,45,4,T)
DEF,ED =(I,57,4,T)
DEF,DC =(I,49,4,T)
DEF,UT =(I,95,4,T)
DEF,VD =(I,91,2,T)
DEF,DPFOLD=(I,33,2,T)
DEF,MUTE =(I,lll,2,T)
DEF,ET =(R,l,4,F)=2000*(ED+DC-EL)/VD-UT
DEF,DP =(I,21,4,T)
DEF,CDP =(I,21,4,T)
DEF,DIST =(I,37,4,T)
DEF,TRN =(I,25,4,T)
DEF,TRC =(I,2,4,C)
DEF,TINC =(I,3,4,C)
DEF,REEL =(I,9,4,R,2)
DEF,RUN =(I,0,2,U)
DEF,CDAT =(A,0,8,U)
DEF,SAMINT=(I,l7,2,R,2)
DEF,SR =(I,l,4,F)=SAMINT/1000
DEF,TIMEl =(I,109,2,T)
DEF,NSAM =(I,21,2,R,2)
DEF,NSAMP =(I,115,2,T)
DEF,STATUS=(I,29,2,T)
DEF,PROS =(A,0,8,U)
DEF,LINE =(A,0,12,U)
DEF,STAT =(A,0,8,U)
DEF,CLIE =(A,0,16,U)
DEF,CREW =(A,0,12,U)
DEF,CONT =(A,0,12,U)
DEF,SDAT =(A,0,8,U)
DEF,LDIR =(R,0,4,U)
DEF,TDIR =(A,0,2,U)
DEF,SURF =(A,0,2,U)
DEF,SPSP =(R,0,4,U)
DEF,TRSP =(R,0,4,U)
DEF,DPSP =(R,0,4,U)
Other Docs
Known Problems
113
Unisec User Guide
DEF,CHAN =(I,13,2,R,2)
DEF,GCHA =(I,0,2,U)
DEF,GTYP =(A,0,12,U)
DEF,RSYS =(A,0,8,U)
DEF,TFMT =(A,0,8,U)
DEF,SOUR =(A,0,12,U)
DEF,CHAR =(A,0,8,U)
DEF,FILT =(A,0,8,U)
DEF,SWEE =(I,0,8,U)
DEF,LSWE =(I,37,2,R,2)
DEF,NSWE =(R,0,4,U)
DEF,VIBR =(A,0,16,U)
DEF,STYP =(A,0,4,U)
DEF,DCHG =(I,0,2,U)
DEF,DCAB =(I,0,2,U)
DEF,UNIT =(A,0,2,U)
DEF,MAN =(A,0,16,U)
DEF,ADDR =(A,0,8,U)
DEF,MAXS =(I,27,2,R,2)
DEF,SPAN =(R,0,4,U)
DEF,SPTR =(R,0,4,U)
DEF,CABL =(R,0,4,U)
DEF,SPTR2 =(R,0,4,U)
DEF,NRTR =(I,0,4,U)
END
Other Docs
Known Problems
114
Unisec User Guide
Appendix F
TYPE Default File
The TYPE default file consists of groups of parameter
statements that can be automatically included in a plot job
by specifying the TYPE keyword. All rules that apply to these
statements when they appear in the input parameter file also
apply when they are used in the TYPE default file. The name
of this file is implementation-dependent but is often
something like type.txt or typetxt. The file structure is as
follows:
***type name 1
.
. (parameter statements for type 1)
.
***type name 2
.
.
***type name 3
.
.
***type name n
.
. (parameter statements for type n)
.
END
Whenever the UNISEC program encounters the TYPE
keyword, it refers to the TYPE default file to include those
parameter statements associated with the specified type
name. This occurs after processing of the user's own
parameter statements. If a TYPE is specified and the TYPE
default file has not been created or does not contain a type
name matching the one specified, an error will occur.
Example:
Other Docs
***SECTION
LABEL,DP=(TINC TO LAST BY TINC),SP
TIC,DP=(TINC TO LAST BY TINC)
***SP
LABEL,#TRC=(1 TO LAST BY TINC),SP,DP
TIC,TRC=(1)
Known Problems
115
Unisec User Guide
GAP,SP,3
***DP
LABEL,#TRC=(1),EX
LABEL,#TRC=(1 TO LAST BY TINC),SP,DP
TIC,TRC=(1)
GAP,DP,3
Other Docs
Known Problems
116
Unisec User Guide
Appendix G
Symbol Table
Other Docs
Known Problems
117
Unisec User Guide
Appendix H
UNISEC Fortran Logical Units
Other Docs
Unit Number
Function
Record Length
in bytes
5
6
7
8
9
10
11
12
15
16
17
18
19
20
22
25
26-28
29
Parameter Input
Listing output
temporary
temporary
Seismic input
temporary
temporary
Graphic output (HSR)
Offline or CGM output
Tape format definitions 'DEF'
Types 'TYPE'
Logos 'LOGO'
temporary
Color tables 'COLTAB'
Montage file output
CGM parameter file output
temporary for color raster data
Optional color seismic input
80
120
80
80
variable
6168
24400
variable
variable
80
80
4000
24400
80
4608
80
5120
variable
Known Problems
Unisec
User Guide Index
A
absolute amplitude
absolute average
ACODE
addition
ADDR
ainc
allocate space
alphanumeric
amplitude
and
annotation
centered
data type
depth
interval velocity
line ties
overlapping
positioning
profile graphs
RMS velocity
side
side label
statement order
time
types
attributes
Auxiliary Reel Header
B
background color
BANNER
BIAS
black
BLANK
blank space
BLKBND
BLKDOT
block boundaries
Other Docs
BPS
byte order
bytes per sample
C
CBPOS
CCLASS
CDNAME
CGM
CINPMODE
color
background
bar
class intervals
definition name
display modes
fill VA
index
number
plotting
scale
shades
specification keyword
table
table file
trace
trace data
trace data scaling
VA fill
COLTAB.TXT
common depth point
Condition
continuity
CPU
CSCLA
CSCLT
CSPOS
CTRID
cyan
Known Problems
Index119
D
data list
data values
Datum Static Corrections
dead trace
DEBUG
DEF.TXT
default statements
DEFINE
definitions
depth point
diagnostic messages
direction
DISP
display
format
framing
mode
distance scale
division
dot spacing
dots per inch
dotted lines
down lines
DPI
DRWMDE
Dual File Mode
Dual Trace Mode
dummy statements
E
editing
automatic
EDIT statement
Electrostatic
element list
Elevation Time
END
ending value
ENDSPC
entity
definition
list
name
Other Docs
ProMAX Reference
specifications
Equations
ESP
EVALS
exponentiation
expression
F
fault lines
font index
frame
height
overlap
FRMHT
G
GAIN
GAP statement
gapping
gaps
geophone
gathers
graphical elements
H
HCDNAME
HCODE
HDPI
height
HORIZON
host computer
HZNULL
I
IBM
ID PARMS
inches per second
increment
Inkjet
input
INPUT statement
parameter deck
record
Known Problems
Index120
tape
tape format
INT
integer values
internal trace counter
interpolated background color
interval
INV
inverse
IPS
K
keywords
KILL
L
LABEBV
LABEL
LABELB
labeling
default statement
horizontal
lists format
maximum
statements
vertical
LABELV
Laserdot
LAST
LEGEND
LEVELED
levels
limit
line
LINE statement
number
line ties
annotation
format options
keyword
symbols
list
location
logical values
Other Docs
ProMAX Reference
loop
formats
value list
lower case
LSTDOT
LTIE
LTIEV
ltype
M
magenta
MAIN
MAN
max
maximum
MAXTVB
METRIC
min
minimum
missing traces
modulus function
multiple plots
multiplication
MXBLKS
MXLTIE
N
nesting
normal
NOVLP
NRH
NULL
O
OFF
ON
or
orientation
OUTPUT
output display device
overlapping
override
Known Problems
Index121
P
PACKSAM
PAD
PANEL
paneled
parameters
PARMS
PDIR
PEAK
permissible statements
format
summary
plot scales
plot traces
plotter attributes
plotting
polarity
pound sign
printout
PRODAT
PROFAN
PROFBOT
profile
box
code
graphs
grid
height
PROFILE statement
scaling
profile height
Program Calculated Function
PROLAB
PROS
prospect
R
RCODE
RDERR
real numbers
RECL
record
length
parameter
Other Docs
ProMAX Reference
RECTYP
reel header
ID
length
source location
REFAMP
RES
resolution
RHID
S
sample rate
scale
distance
second file
section annotation
SEGY
seismic color
shot point
shotpoint gathers
side label
keyword
side tick marks
SIDEA
SIDEL
single trace
singles list
SKIP
skipped shotpoints
slices
source
SP
space allocation
SR
START
start time
starting value
statement
entity list logic
identification
STYPE
SUBEND
substitute trace
subtraction
superimpose
Known Problems
Index122
suppress
symbols
T
T/V lists
TAPE
tape format definition file
t-bar
text
annotation
parameter
size
string
TEXT statement
Thermal
thickness
time-velocity lists
time-velocity pairs
timing line
annotation
dotted
interval
plotting
size
thickness
timing lines
timing marks
TINC
Title
color scale
string
TPEHL
TPI
trace
data
data format
display modulus
labeling
labels
location
numbers
scaling
spacings
TRACE statement
Trace Header
Other Docs
ProMAX Reference
traces per inch

TRCMOD
TRHL
TRID
truncation
TVHEAD
TVLDOT
TVLFMT
TVLIST
TVTD DATA
TYPE
type
U
User-Defined Function
User-Specified Values
V
VA color fill
VACOL
variable area
clipped
shading
variables
VAXFILE
VDPI
velocities
vertical lines
VMAX
W
wiggle
thickness
trace
trace data
WIGMOD
WIGTHICK
window
Y
yellow
Known Problems
Index123
ProMAX Reference
Z
zero reference
Other Docs
Known Problems

Larson Book

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

Larson Book

Uploaded by

Copyright:

Available Formats

Contents1

Unisec User Guide

Unisec User Guide Contents

Unisec User Guide

Input Parameter File 11

Timing Line Annotation (TIMEA)

Trace Related Annotation 32

Profiles (PROFILE PROFBOT) 44

Unisec User Guide

Field Information Box (FIELD)

Horizon and Fault Display (HORIZON) 65

Identification Banner (BANNER) 75

Unisec User Guide

Office Box Presentation

Unisec User Guide

Unisec Plotting Overview

Unisec Plotting Overview6

Unisec User Guide

Unisec Plotting Overview

Unisec User Guide

Unisec User Guide

Profiles up to 2" in height, with 0.25" of space

Time-velocity lists up to 2.5". Size based on the

Trace symbols, line-ties, text, and distance

Trace labels, if requested.

Seismic traces, timing lines and annotation,

Trace labels, if requested.

Profiles up to 2" in height with 0.25" of space

Allocating Display Space

Sum (profile height + 0.25") N = the number of

Unisec User Guide

(1.2 * tvlist annotation size) * (VMAX + 2) * max.

1.2 * [largest symbol size + largest text size +

0.25" + 0.15" * (number of entity labels + 1)

(IPS * RECL) / 1000 + 0.1"

0.25" + 0.15" * (number of entity labels + 1)

Sum (profile height + 0.25") N = the number of

Increasing allocated space

Unisec User Guide

Unisec User Guide

Input Parameter File

Unisec User Guide

Unisec User Guide

Format for a Loop List

Statement ID, entity=(list)

Unisec User Guide

These examples show how the two formats, or a

Entity List Logic

will kill only traces that are common to Condition #1 and

will kill traces that are common to Condition #1 or

Unisec User Guide

General Parameters (PARMS)16

Unisec User Guide

General Parameters (PARMS)

Since PARMS is the statement ID, it must be the first entry

General Parameters (PARMS)17

Unisec User Guide

CBPOS = l Controls position of the color (calibration)

General Parameters (PARMS)18

Unisec User Guide

reference line when viewing the trace as specified.

General Parameters (PARMS)19

Unisec User Guide