NAME
hdr2xsdpick - create xsd pickfile segments from user
defined entries in USP trace header with optional horizon
colour assignment.
SYNOPSIS
hdr2xsdpick [ -Nntap ] [ -Ootap ] [ -rsnrst ] [ -renred ] [
-nsnstr ] [ -nenetr ] [ -nullnull ] [ -label ] [ -hwhwd ] [
-hchwc ] [ -V ] [ -? or -h or -help ]
DESCRIPTION
hdr2xsdpick : allows the user to specify up to 100 valid USP
trace header mnemonics from which to generate xsd pick seg-
ments for display in xsd. Each horizon will be displayed as
a different segment on each record of the input dataset.
Single point segments will appear as dots. You may select
from a list of valid xsd pick colours a colour to associate
with your horizon data.
hdr2xsdpick gets both its data and its parameters from com-
mand line arguments. These arguments specify the input,
output, the start and end traces, start and end records, the
horizon null value, horizon mnemonics, horizon colours and
verbose printout, if desired.
Command line arguments
-N ntap [default: stdin]
Enter the input data set name or file immediately after
typing -N unless the input is from a pipe in which case
the -N entry must be omitted. This input file should
include the complete path name if the file resides in a
different directory. Example -N/b/vsp/dummy tells the
program to look for file 'dummy' in directory '/b/vsp'.
-O otap [default: stdout]
Enter the output data set name or file immediately
after typing -O. This output file is not required when
piping the output to another process. The output data
set also requires the full path name (see above). Note
that the output is an xsd pickfile NOT a USP dataset.
-rs nrst [default: 1]
Enter start record number.
-re nred [default: last record]
Enter end record number.
-ns nstr [default: 1]
Enter the start trace number.
-ne netr [default: last trace of record]
Enter the end trace number.
-null null [default: -30000.0]
Enter the horizon null value used to flag that the hor-
izon does not exist at any point in the volume. No
pick will be output at locations whose header contains
this value.
-label
If present on the command line the Mnemonic used for
the pick segment will also be used as a segment lable
in the xsd pick file. The default is to use unlabeled
segments.
-hw horizon [default: no default, entry required]
Enter the trace header mnemonic associate with the hor-
izon that you wish to convert to an xsd pickfile seg-
ment. If you have more than a single horizon to con-
vert simply put as many [up to 100] -hw entries on the
command line as you require. When associating colours
with these horizons the colors will be assigned in the
order that they appear on the command line. For
instance the first colour entry will go with the first
horizon entry and so on.
-hcw colour [default: yellow]
Enter the colour that you wish to associate with you
input horizon pick in the output xsd pickfile. If you
have more than a single horizon to convert simply put
as many [up to 100] -hw entries on the command line as
you require. When associating colours with these hor-
izons simply put an equal number of -hc entries. The
colors will be assigned in the order that they appear
on the command line. For instance the first colour
entry will go with the first horizon entry and so on.
Valid colours are
white
black
0
1
2
3
4
5
6
7
8
9
which correspond to the pick colour table entries in your
.xsd_defaults file. If you look at the pick colour assign-
ment in your xsd display you will see that there are 12
entries with Black and White on the leftmost column. The
remaining colours are assigned column-wise starting with
offset 0. The entries 0 - 9 above correspond to those 10
colours.
-V Enter the command line argument '-V' to get additional
printout.
-? or -h or -help
Enter the command line argument '-?' or -h or -
help to get online help. The program terminates after
the help screen is printed.
DISCUSSION
This routine assumes that the TmMsFs [ time in milliseconds
of first sample] entry in your input dataset is correct. If
not you may find your picks do not match your horizons.
Also in USP [as in DISCO and ProMax] sample 1 is assumed to
be time zero unless otherwise indicated, i.e. TmMsFS =
nonzero. If you notice that your picks are not exactly on
your horizon [maybe off by a sample for instance] you may
have a problem in this area. Make sure you know the assump-
tions made in timing your input dataset. If you have any
trouble with the association feel free to call the USP help
line and thrash out your problem.
BUGS
Unknown but sure to exist.
SEE ALSO
lm3dvtosis(1) lm3dhrztosis(1) lmhorizon(1)
AUTHOR
[Paul G. A. Garossino: socon 422-3932]
COPYRIGHT
copyright 2001, Amoco Production Company
All Rights Reserved
an affiliate of BP America Inc.
Man(1) output converted with
man2html