NAME
vomit - module to convert velocity function set format.
Velocity Output Multiple Input Types - Tom Chaimov
SYNOPSIS
vomit [ -Nntap ] [ -Ootap ] [ -fiitype ] [ -footype ] [
-sinsin ] [ -soutsout ] [ -vinvin ] [ -voutvout ] [ -eta ] [
-rnmo ] [ -force ] [ -linear ] [ -V ] [ -hwiwd ] [
-d2tmaxtmax ] [ -t2dmaxdmax ] [ -nrecnr ] [ -ntrcnt ] [
-nsampnsamp ] [ -nsiisi ] [ -osiosi ] [ -safisaf ] [
-UnitScuscalar ] [ -UnitSc_outuscalaro ] [ -velstvel0 ] [
-veledveln ] [ -nhorn ] [ -vmaxvmax ] [ -nelemn ] [
-watvelwatvel ] [ -oacoac ] [ -linewline ] [ -commentchar14
] [ -E1top ] [ -E2bot ] [ -ew1topWrd ] [ -ew2botWrd ] [
-reshotwshot ] [ -unitsfm ] [ -uxsd_u] [ -v0xsd_v0 ] [
-dvxsd_dv ] [ -xhwxiwd ] [ -dxmbs_dx ] [ -dymbs_dy ] [
-dzmbs_dz ] [ -tdq_unitstdq_c_units ] [ -tdq_datumtdq_datum
] [ -velocity ] [ -vref ] [ -TD ] [ -DT ] [ -h ] [ -help ] [
-? ]
DESCRIPTION
vomit reads in velocity function set information in one of a
variety of formats and converts that function set to a user
defined output format. Not all conversion types are compa-
tible. A conversion check is run to verify that what you
are trying to accomplish is in fact possible using the rou-
tine. If not, execution will be terminated. If you feel
that the conversion should be possible please call in and
request additional functionality. A good rule of thumb is
to call into the USP shop as soon as you start having trou-
ble. No sense you wasting your time figuring it all out
when you can get us to do it for you. During the format
conversion the velocity and sample types may be converted if
desired.
vomit gets both its data and its parameters from command
line arguments. You may use sticky or non-sticky arguments
as you wish.
Command line arguments
-N ntap [Default: stdin]
Enter the fully qualified path name to the file con-
taining your input velocity function set. Unless the
input format is usp or charisma then you may NOT
pipe into this routine. In all other cases it is
necessary to back up on the input file which cannot be
done on a piped dataset.
-O otap [Default: stdout]
Enter the fully qualified path name to the file to con-
tain your output velocity function set.
-fi ifi [Default: none]
Enter the format of the input velocity function set.
-fo ifo [Default: none]
Enter the format of the output velocity function set.
Legal format entries are:
agip --> agip format file
charisma --> Charisma format [this is valid
ONLY for input. Output format MUST
be usp (defaults if -fo not input)]
digicon --> Digicon format file [this is valid
ONLY for input. Output format MUST
be usp (defaults if -fo not input)]
disco --> DISCO HANDVEL deck
disco3d --> DISCO HANDVEL deck with LI, DI
entries [ala Tensor in Cairo]
disco3dxy --> DISCO HANDVEL deck with CDP,X,Y,LI,
DI
entries [Alan Poole UTG - valid for
input only]
disco3d1 --> DISCO HANDVEL deck with LI, DI
entries [ala CGG in Stavanger]
disco3d2 --> DISCO HANDVEL deck with LI, DI
entries [ala GeoDepth in Stavanger]
valid for output only.
essov2 --> essov2 format file [this is valid
ONLY for input. Output format MUST
be usp (defaults if -fo not input)]
ev3d --> Earth Vision 3D ascii grid format.
[See Discussion Below]
flat --> velin flat file format
flat3d --> free format 3D flat file format
[LI, DI, Unit, Velocity]
flat3d1 --> free format 3D flat file format
[LI, DI, Unit, Velocity, Unit,
Velocity, ..., Unit, Velocity]
geco --> geco velocity file format.
[See Discussion Below]
kelman --> kelman velocity file format.
[See Discussion Below]
landmark --> landmark ascii horizon file, no
header, blank space between
function entries must use
-nhor, -nrec, -ntrc, with this
entry, -vmax, -osi, -nsamp are
optional
[See Discussion Below]
landmark2 --> landmark ascii horizon file, no
header, blank space between
function entries must use
-nhor, -nrec, -ntrc, with this
entry, -vmax, -osi, -watvel, -nsamp
are optional
[See Discussion Below]
omnivel --> Amoco Oracle Velocity Database
format (valid ONLY for input.
Output format must be usp.)
promax --> promax ascii function output
tdfn --> Amoco TDFN deck
tdq --> Landmark TDQ format (valid only for
output)
ukooa --> UKOOA velocity format [9.1]
ukooa1 --> UKOOA velocity format [8.3.1]
ukooa2 --> UKOOA P1/1990 format (valid for
input only)
usp --> USP format
vxos --> vxos pick file [must use -dv and
-v0 with this input]
vds3d --> VDS 3D card format
[See Discussion Below]
vip --> VIP output card format
[See Discussion Below]
western3d --> Western Geophysical 3D ascii card
format. [See Discussion Below]
western3d1 --> another Western Geophysical 3D
ascii card format. [See Discussion
Below]
xsd --> xsd pick file
xsdheader --> xsd header value at pick location
file [select DstSgn]
zmap --> zmap input flat file format [output
only]
-sin sin [Default: T]
Enter the type of the input velocity function set sam-
ple units
T --> time
D --> depth
-sout sout [Default: T]
Enter the type of the output velocity dataset sample
units
T --> time
D --> depth
-vin vin [Default: R ; Default for charisma input: A]
Enter the velocity type of the input velocity function
set
I --> interval velocity
R --> rms velocity
A --> average velocity
-vout vout [Default: R ; Default for charisma input: I]
Enter the velocity type of the output velocity dataset
I --> interval velocity
R --> rms velocity
A --> average velocity
-eta If present on the command line then instead of velo-
city, the input function is made up of eta values [see
vtispec, vtinmo].
-rnmo
If present on the command line then instead of velo-
city, the input function is made up of rnmo values [see
rnmospec].
-force
If present any time an RMS velocity inversion is
encountered when converting to interval velocity,
vomit will use that last calculated interval velocity.
This flag will enable one to convert such datasets to
interval velocity in the face of a negative value
inside the square root in the Dix calculation.
-linear
If present on the command line and you are, for what
ever reason, building a USP format output interval
velocity trace, you will not get the traditional blocky
interval velocity output. In this case a linear inter-
polation between the interval velocity control, in time
or depth, will be used to generate the output trace.
The result will be a smoothly varying interval velocity
but of course DO YOU REALLY WANT THIS?????? For other
velocity types linear interpolation will take the place
of the default cubic spline interpolation if interpola-
tion is required.
-velocity
If present on the command line and you are using an
input format of charisma the TVPVnn entries are taken
to be velocity instead of depth.
-vref
Enter the Kelman reference velocity used to create your
input time,rms velocity function. If you are using
kelman input format this is a manditory command line
entry. There is no default.
-TD If present on the command line your output will be
time,depth curves. It is assumed that your input data
has units of time. Whichever velocity type you enter,
it will be converted to average prior to depth calcula-
tion.
-DT If present on the command line your output will be
depth, 2-way time, curves. It is assumed that your
input data has units of depth. Whichever velocity type
you enter, it will be converted to average prior to
depth calculation.
-V Verbose printout mode. Recommended for quality control
of vomit operation.
usp parameters
-hw iwd [Default: RecNum ]
Enter the USP trace header mnemonic corresponding to
velocity function set index [eg, -hw SGRDat ].
-d2tmax n [Default: not used]
Enter the maximum time to output when using usp input
and output format and doing a depth to time conversion.
The default is to use the same number of samples as the
input dataset and the output sample interval specified
by -osi . The units of this entry must match those of
-osi.
-t2dmax n [Default: not used]
Enter the maximum depth to output when using usp
input and output format and doing a time to depth
conversion. The default is to use the same number of
samples as the input dataset and the output sample
interval specified by -osi .
-nrec nr [Default: number of input functions]
This entry is useful when outputting an xsd pickfile
to overlay on a velocity spectra. In this case xsd
will require the number of records to be filled out in
the pick file line header. If your input format does
not contain this information or if you wish to override
the input information for the output file this entry
will enable you to do that.
-ntrc nt [Default: 1]
This entry is useful when outputting an xsd pickfile
to overlay on a velocity spectra. In this case xsd
will require the number of traces to be filled out in
the pick file line header. If your input format does
not contain this information or if you wish to override
the input information for the output file this entry
will enable you to do that.
-nsamp nsamp [Default: none]
This entry is useful when outputting an xsd pickfile
to overlay on a velocity spectra. In this case xsd
will require the number of samples to be filled out in
the pick file line header. If your input format does
not contain this information or if you wish to override
the input information for the output file this entry
will enable you to do that. If you are converting to a
usp formatted velocity dataset you MUST include this
entry. Failure to do so will result in a program abort
as vomit will not know how many samples to generate.
This entry is also used for charisma input format. In
this case, you may input a decimated input dataset of 1
sample per trace. The program does not use the input
data samples to build the velocity output. Therefore,
the program needs to know how many samples per trace to
output. You should enter the number of samples you
will need to use the output velocity volume with your
real data. If the input dataset has the same number of
samples you need on the output, you may omit this
parameter.
-nsi isi [ Default: USP: from line header, others none]
Enter the sample interval in milliseconds to use when
converting to usp formatted velocity data. If your
input is usp format and you wish to change the output
sample interval see -osi below.
-osi osi [Default: none]
Enter the output sample interval in milliseconds to use
when converting to usp formatted velocity data. If
your input is usp format a cubic spline interpolation
will be used. There is NO alias protection here.
This option also works with most other input formats
but not all output formats allow for use of this
option. If you want a particular sample interval out
and vomit will not comply please give us a call.
-saf saf [Default: 1% for -voutI, 0.1% percent otherwise]
When the input velocity function set is a USP velo-
city dataset of either RMS or AVERAGE velocity and a
velocity type or format conversion is required, the
slope adjustment factor, entered as a percentage, is
used to glean the input velocity function set. Vomit
keeps track of the slope changes between samples and
should the slope change be greater than this percentage
an output function will be flagged. The smaller the
number, the smaller the slope break required to detect
another function element and the greater the number of
samples in the output function. Useful in varying the
spatial smoothness of the output velocity dataset
and/or the number of entries in each output function.
This parameter affects the sensitivity of the routine
to slope changes between input samples. Small values
of -saf will output more function values as smaller
slope breaks will trigger the output of a function.
The effect on the number of output elements of the size
of this entry is really data dependant. You may have
to make a few tests to dial it in for your dataset. If
you are using -osi a -saf entry is meaninless and will
not be used.
-UnitSc uscalar [Default 0.0]
In USP the default UnitSc [see scan] line header entry
is 0.001 [for milliseconds]. If you have units differ-
ing from milliseconds and you do not want to utop the
line header correctly you may enter the appropriate
scalar as an override here. 1.0 implies units of
seconds. If not used then the UnitSc from the input
line header will be used. If that value is 0.0 it will
be set to 0.001 assuming input sample interval of mil-
liseconds
-UnitSc_out uscalaro [Default 0.0]
In USP format, If your output dataset requires a UnitSc
different from your input you may enter it here. This
is often the case when both input and output formats
are USP and you are converting between depth and time.
-velst vel0 [Default 0.0]
Input the velocity to be used at time zero in the units
of the dataset. If nothing is entered this option is
ignored.
-veled veln [Default 0.0]
Input the velocity to be used at the maximum time of
the dataset. If not included on the command line this
option is ignored.
landmark / landmark2 parameters
-nhor n [Default: 0]
Enter the number of horizons output to the Landmark
ASCII horizon file. If you are using an input format
of landmark this is required. If your -nhor[] value
is 1 then vomit will expect that you are trying to
create a gradient based velocity function where the max
unit is defined by the unit value of the single velo-
city entry specified in the input. The gradient in
this case will be formed between time/depth zero and
that value.
-vmax n [Default: not used]
Enter the maximum velocity to occur at D(0) when using
landmark input format.
-watvel n [Default: 1500.0]
Enter the velocity of the first layer. This parameter
is used only with landmark2 input format. The default
is roughly water velocity in metric units.
flat3d1 parameters
-nelem n [Default: 0]
Enter the number of horizons used to build your flat3d1
format input file. This is required only if using
flat3d1 format input.
vds3d parameters
-oac oac [Default: blank]
Enter the Operations Activity Code and Line Number to
be used with the vds3d format. This entry is not
required if you are reading vds3d format, but may be
used if you are creating vds3d output and require
this entry for the VDS system.
geco parameters
-linewline fR
Enter the Western Geophysical alph-numeric line name
for this run. The default is a blank and you may enter
up to a 7 character variable. If you are creating
GECO format output you may use this entry to input the
GECO line name. In this case a maximum of 10 charac-
ters may be used.
-commentchar14 fR
Enter up to a 14 character comment to appear on the
GECO format output. This only affects the output. Any
comment on the GECO input will over-ride this entry.
ev3d parameters
-E1top fR
Enter the file name of the Earth Vision 2D ascii file
containing the upper control surface if used. These
values will be stored in the trace header entry pro-
vided by -ew1 below.
-E2bottom fR
Enter the file name of the Earth Vision 2D ascii file
containing the lower control surface if used. These
values will be stored in the trace header entry pro-
vided by -ew2 below.
-ew1topWrd fR
Enter the mnemonic of the trace header entry in which
to store the top reference horizon values.
-ew2botWrd fR
Enter the mnemonic of the trace header entry in which
to store the bottom reference horizon values.
western parameters
-linewline fR
Enter the Western Geophysical alph-numeric line name
for this run. The default is a blank and you may enter
up to a 7 character variable. If you are creating
GECO format output you may use this entry to input the
GECO line name. In this case a maximum of 10 charac-
ters may be used. [not used with western3d1 format]
-reshotwshot fR
Enter the Western Geophysical reshot symbol for this
line if appropriate. The default is a blank and you
may enter up to a 1 character variable. [not used with
western3d1 format]
-unitsfm fR
Enter the Western Geophysical units code for this
line. The default is a blank, enter F for feet, M for
meters. [not used with western3d1 format]
xsd parameters
-u unit [Default: not used]
if the input format is xsd, xsdheader or vxos a
time/depth units multiplier may be provided which will
override that found in the pick file header. This is
useful if the pickfile header value is incorrect for
whatever reason.
-v0 v0 [Default: not used]
if the input format is xsd or vxos a velocity start-
ing value for the picked spectrum may be provided which
will define the velocity to use at trace one on the
input pick file. This value will supersede that found
in the pickfile header.
-dv dv [Default: not used]
if the input format is xsd or vxos a velocity incre-
ment for the picked spectrum may be provided which will
define the velocity increment to use between traces on
the input pick file. This value will supersede that
found in the pickfile header.
-xhw xiwd [Default: Record]
if the input format is xsdheader a mnemonic reference
to use as the velocity function record index may be
entered. If not used the mnemonic 'Recored' will be
used.
MBS parameters
-dx mbs_dx [Default: 0]
Enter horizontal trace spacing (ft, m). This value is
multiplied by 1000 then written into the line header of
the output USP velocity dataset in a slot used by the
MBS migration codes.
-dy mbs_dy [Default: 0]
Enter horizontal record spacing (ft, m). This value is
multiplied by 1000 then written into the line header of
the output USP velocity dataset in a slot used by the
MBS migration codes.
-dz mbs_dz [Default: 0]
Enter vertical depth interval (ft, m). This value is
multiplied by 1000 then written into the line header of
the output USP velocity dataset in a slot used by the
MBS migration codes.
-tdq_units tdq_c_units [Default: METERS]
Enter the units designation of your Landmark TDQ format
output. Valid entries are METERS [the default] or
FEET. Yes, they must be upper case. This entry is used
only for the TDQ header entries in your output file and
will have no effect on velocity conversions within this
routine.
-tdq_datum tdq_datum [Default: 0.0]
Enter the Landmark TDQ datum to be supplied as your
output DATUM header entry. The default is 0.0 and any
real number is valid.
-? or -h or -help
Query mode. With this flag vomit will execute its'
internal help subroutine yielding information concern-
ing its' command line arguments then exit.
DISCUSSION
vomit accepts velocity function set input in a variety of
formats. Not all of the formats are compatible with each
other. In general the 3D formats cannot be converted to 2D
formats due to the lack of available indices. This of
course does not apply to usp format. There is a conver-
sion check routine in vomit that is supposed to prevent you
from attempting conversions that the program cannot perform.
Here are examples of the the various input formats:
agip
EGYPT TEMSAH3D I.E.O.C WESTERN GEO 1196MDO
NOT SUBTRACT CORR. MTV21
888.0 3200 738168. 989664.
VDMOM 73*
4. 1610. 104. 1611. 204.
1636. 304. 1675.
404. 1720. 504. 1765. 604.
1809. 704. 1847.
804. 1884. 904. 1923. 1004.
1966. 1104. 2008.
1204. 2038. 1304. 2060. 1404.
2080. 1504. 2104.
1604. 2139. 1704. 2174. 1804.
2209. 1904. 2226.
2004. 2241. 2104. 2256. 2204.
2273. 2304. 2292.
2404. 2311. 2504. 2323. 2604.
2330. 2704. 2337.
2804. 2343. 2904. 2350. 3004.
2359. 3104. 2369.
3204. 2380. 3304. 2390. 3404.
2402. 3504. 2421.
3604. 2441. 3704. 2462. 3804.
2482. 3904. 2503.
4004. 2523. 4104. 2544. 4204.
2565. 4304. 2586.
4404. 2607. 4504. 2632. 4604.
2667. 4704. 2702.
4804. 2737. 4904. 2761. 5004.
2778. 5104. 2795.
5204. 2813. 5304. 2830. 5404.
2847. 5504. 2865.
5604. 2881. 5704. 2898. 5804.
2915. 5904. 2932.
6004. 2951. 6104. 2969. 6204.
2987. 6304. 3005.
6404. 3023. 6504. 3041. 6604.
3058. 6704. 3076.
6804. 3094. 6904. 3111. 7004.
3124. 7104. 3124.
7164. 3124.
NOTE: The first card in this format is informational, and
is not used in the conversion. the first card of each func-
tion contains LI, DI, ICX, ICY, ???, and number of entries
in the function. This card is terminated by and '*' in
cc80. The rest of the function consists of card images with
4 pairs of time/velocity. The time is expected to be in
milliseconds. A blank entry for velocity signals the end of
the function.
disco
HANDVEL 400
824.0 4034.0 1400.0 4328.0 2160.0 6194.0
3584.0 6881.0
4488.0 8353.0 5848.0 9924.0
HANDVEL 401
648.0 3150.0 1064.0 3445.0 1432.0 3936.0
2344.0 4917.0
4256.0 6979.0 4472.0 7961.0 5336.0 8746.0
5864.0 9433.0
HANDVEL 402
656.0 3052.0 1064.0 3543.0 1464.0 4525.0
2408.0 6095.0
4736.0 9041.0 5520.0 9728.0 5768.0 9924.0
HANDVEL 403
624.0 3445.0 1432.0 5212.0 2216.0 6586.0
4344.0 8157.0
5664.0 9630.0
disco3d
HANDVEL 846040
1024 40
27 1504 1258 1700 1660 1790 2289
1994
3009 2133 3785 2312 4332 2419 4861
2688
5819 3317 7050 3906
HANDVEL 846080
1024 80
63 1422 483 1504 802 1659 1386
1814
2070 2010 2909 2092 3493 2329 4788
2517
5828 2795 6676 3130 7087 3415
HANDVEL 846120
1024 120
36 1446 456 1536 1140 1642 1532
1790
2106 2018 2964 2116 3429 2272 3912
2255
4688 2304 5718 2566 6840 3064
disco3dxy
HANDVEL 429800 796513.4 970315.4
1020 400
0 1489 200 1526 400 1646 600
1766
800 1861 1000 1926 1200 1964 1400
2033
1600 2085 1800 2114 2000 2146 2200
2191
2400 2237 2600 2262 2800 2265 3000
2268
HANDVEL 429880 795541.7 970551.6
1020 480
0 1481 200 1519 400 1643 600
1766
800 1842 1000 1903 1200 1960 1400
2014
1600 2062 1800 2083 2000 2135 2200
2202
2400 2269 2600 2298 2800 2295 3000
2299
disco3d1
HANDVEL 48001760
150 1466 341 1677 675 1833 825
1931
950 1973 1300 2033 1575 2126 1775
2223
2025 2306 2125 2457 2300 2529 2448
2581
2950 2996 3375 3358 3700 3554 4025
3705
4250 3768 5550 4322 7550 4502 8000
4530
HANDVEL 48001800
150 1472 370 1693 525 1785 913
1939
1116 1989 1200 1994 1456 2037 1525
2064
1875 2278 2300 2497 2575 2600 2775
2879
2975 3017 3125 3161 3250 3235 3425
3337
3625 3498 3925 3678 4725 4025 5550
4312
7550 4494 8000 4523
disco3d2
HANDVEL 1290 1549
134.0 1481.0 228.0 1541.0 361.0 1635.0
452.0 1669.0
551.0 1756.0 726.0 1796.0 786.0 1837.0
833.0 1837.0
923.0 1857.0 967.0 1884.0 1111.0 1891.0
1228.0 1910.0
1481.0 1936.0 1684.0 1961.0 1969.0 1984.0
2072.0 1991.0
2287.0 1999.0 2524.0 2031.0 2723.0 2072.0
2791.0 2078.0
2833.0 2092.0 2965.0 2199.0 3024.0 2226.0
3077.0 2314.0
3147.0 2441.0 3205.0 2589.0 3299.0 2650.0
3405.0 2737.0
3467.0 2811.0 3523.0 2824.0 3570.0 2858.0
3709.0 2979.0
3839.0 3073.0 4188.0 3308.0 4501.0 3489.0
5499.0 3946.0
digicon
888 3200 738168 989664 4. 1610.
888 3200 738168 989664 104. 1611.
888 3200 738168 989664 204. 1636.
888 3200 738168 989664 304. 1675.
888 3200 738168 989664 404. 1720.
888 3200 738168 989664 504. 1765.
888 3200 738168 989664 604. 1809.
888 3200 738168 989664 704. 1847.
888 3200 738168 989664 804. 1884.
888 3200 738168 989664 904. 1923.
888 3200 738168 989664 1004. 1966.
essov2
V2 958 901 88 1532
V2 958 901 521 1779
V2 958 901 1234 1955
V2 958 901 1630 2085
V2 958 901 2093 2115
V2 958 901 2548 2412
V2 958 901 3290 2541
V2 958 901 4561 2893
V2 958 901 5053 2998
NOTE: This format consists of V2, inline index,
crossline index, time, velocity. When the format is
converted to USP format, the crossline index is divided
by 2 before storing in the USP header word DphInd.
ev3d
Stands for Earth Vision 3D grid format. The format is
very Boutique and used exclusively by GUPCO at the
moment. If you need to know the exact format please
call as it is too confusing to bother listing here.
flat
824, 4034, 400
1400, 4328, 400
2160, 6194, 400
3584, 6881, 400
4488, 8353, 400
5848, 9924, 400
-1, 0, 400
648, 3150, 401
1064, 3445, 401
1432, 3936, 401
2344, 4917, 401
4256, 6979, 401
4472, 7961, 401
5336, 8746, 401
5864, 9433, 401
-1, 0, 401
656, 3052, 402
1064, 3543, 402
1464, 4525, 402
2408, 6095, 402
4736, 9041, 402
5520, 9728, 402
5768, 9924, 402
-1, 0, 402
624, 3445, 403
1432, 5212, 403
2216, 6586, 403
4344, 8157, 403
5664, 9630, 403
-1, 0, 403
NOTE: Columns are ( time, velocity, index )
flat3d
422.000 767.000 3400.00 8633.00
422.000 767.000 4400.00 9232.00
422.000 767.000 6000.00 9954.00
422.000 767.000 8000.00 10716.0
422.000 896.000 10.00000 5016.00
422.000 896.000 500.000 5774.00
422.000 896.000 700.000 6022.00
422.000 896.000 1000.000 6320.00
NOTE: The above are LI, DI, Unit, Velocity free format
entries. This format was requested by the OBU and will not
be changed without consultation with our esteemed colleagues
in New Orleans.
flat3d1
1 1470 0 1480 500 1756 1000 1926 1500 2070
2000 2179 2500 2311 3000 2375 3500 2410 4000 2446 5000
2557 6000 2702 7000 2834
1 1510 0 1480 500 1757 1000 1930 1500 2070
2000 2180 2500 2311 3000 2373 3500 2409 4000 2448 5000
2559 6000 2705 7000 2836
1 1550 0 1480 500 1758 1000 1934 1500 2071
2000 2182 2500 2312 3000 2371 3500 2406 4000 2448 5000
2560 6000 2707 7000 2838
1 1590 0 1480 500 1759 1000 1938 1500 2072
2000 2184 2500 2313 3000 2367 3500 2403 4000 2449 5000
2562 6000 2709 7000 2839
1 1630 0 1480 500 1759 1000 1943 1500 2072
2000 2186 2500 2313 3000 2364 3500 2398 4000 2448 5000
2565 6000 2710 7000 2839
NOTE: The above are LI, DI, Unit, Velocity free format
entries. This format was requested by GUPCO and will not be
changed without consultation with the Cairo joint venture
office.
geco
v231nor 1 1 pdadstckjan95 0 2
1480
v231nor 1 1 pdadstckjan95 100 2
1480
v231nor 1 1 pdadstckjan95 150 2
1480
v231nor 1 1 pdadstckjan95 200 2
1726
v231nor 1 1 pdadstckjan95 300 2
1971
v231nor 1 1 pdadstckjan95 400 2
1971
v231nor 1 1 pdadstckjan95 500 2
1971
v231nor 1 1 pdadstckjan95 600 2
1971
v231nor 1 1 pdadstckjan95 700 2
1971
v231nor 1 1 pdadstckjan95 800 2
1971
landmark
2 2 2.2 897 2577 1386 3309 1873 3501 3040 4550
6 2 2.2 898 2581 1388 3308 1876 3501 3041 4549
10 2 2.2 899 2586 1394 3303 1882 3500 3041 4545
14 2 2.2 900 2589 1396 3302 1886 3500 3042 4544
18 2 2.2 901 2589 1400 3295 1894 3498 3042 4538
22 2 2.2 903 2591 1402 3292 1901 3498 3045 4535
The above entries are TrcNum, RecNum, k, then, in this exam-
ple, 4 sets of (unit,velocity) pairs. To access this par-
ticular example a -nhor entry of 4 must be used. The first
pair of (unit,velocity) entries define a D,V(0) for the
first layer. The velocity used at D will be calculated
using the expression V(D) = V(0) + k * D, where k is the
velocity gradient used in the first layer. Velocity entries
between D(0) and D are calculated using the above expres-
sion. There is an optional command line entry -vmax which
defines the maximum velocity to use at D. If the calculated
velocity exceeds the specified maximum then the maximum
velocity will be used instead. If no -vmax is entered on
the command line the result of the gradient calculation will
be used. The command line entries -nrec, -ntrc and -osi are
required for this input format. The -osi entry is used in
the generation of instantaneous interval velocity entries
above D(0). In addition, If you are outputting usp format
data -nsamp is also required. This format was requested by
GUPCO and will not be changed without consultation with the
guys in Cairo. Malesh.
Here is an example where the user wanted to form a gradient
based velocity function down to 6000 meters with a sample
interval of 10 meters. The input landmark format functions
looked like:
1081.000000 1101.000000 0.762500 6000.000000 356.000000
1082.000000 1101.000000 0.761900 6000.000000 358.330000
1083.000000 1101.000000 0.761300 6000.000000 360.660000
1084.000000 1101.000000 0.760700 6000.000000 362.990000
1085.000000 1101.000000 0.760200 6000.000000 364.850000
1086.000000 1101.000000 0.759700 6000.000000 366.710000
1087.000000 1101.000000 0.759300 6000.000000 368.570000
1088.000000 1101.000000 0.758800 6000.000000 370.440000
1089.000000 1101.000000 0.757800 6000.000000 374.120000
Notice that each velocity function has only a single hor-
izon. The command line looked like:
vomit -nsamp 601 -fi landmark -fo usp -nhor 1 -nrec 2603
-ntrc 1157 -osi 10 -V -vmax 10000 -UnitSc_out 1.0
landmark2
uses the exact format specified for landmark [above].
The assumptions are different however. In the landmark
format the initial (unit,velocity) pair defined a
D,V(0) for the first layer. In this version of the
format the initial pair defines the base of layer 1 as
well as the initial velocity for layer 2. In the
landmark format the gradient calculation was applied to
the first layer. In this format it is applied to the
second layer. This first layer is assumed to have con-
stant velocity. The velocity for the first layer is
taken from the command line entry -watvel[] [default
1500.0]. The identical gradient calculation is used
and all other constraints [ -vmax[], -nhor[], -nrec[],
-ntrc[], -osi[]] need to be satisfied. The -osi entry
is used in the generation of instantaneous interval
velocity entries throughout layer 2. If you are output-
ting usp format data -nsamp is also required. This for-
mat was requested by GUPCO and will not be changed
without consultation with the guys in Cairo.
omnivel
**Example of 2D file**
VLDB0YETJ AMOCO 488 183 91
VLDB1J NONE NONE 96 19960404 G
VLDB200 000 0 0 122 1500 27.34678 -89.97854
VLDB3 1861725 3978657 NAD27 QX16
VLDB5COMMENTS GO HERE
VLDB6 0 1500
VLDB6 687 1522
VLDB6 858 1617
VLDB6 1038 1836
VLDB6 1294 2143
VLDB6 1412 2455
VLDB6 1755 2708
VLDB6 2013 3031
VLDB6 2210 3282
VLDB6 2438 3545
VLDB6 2905 3927
VLDB6 3419 4150
VLDB6 3946 4322
VLDB6 4574 4519
VLDB6 5430 4769
VLDB6 6256 4967
VLDB6 7165 5158
VLDB6 8165 5329
**Example of 3D file**
VLDB0YABC AMOCO 1 102 1235
VLDB1J NONE NONE 96 960404 G
VLDB200 100 0 0 122 1500 27.34678 -89.97854
VLDB3 1861725 3978657 NAD27 QX16
VLDB5COMMENTS GO HERE
VLDB6 0 1500
VLDB6 687 1522
VLDB6 858 1617
VLDB6 1038 1836
VLDB6 1294 2143
VLDB6 1412 2455
VLDB6 1755 2708
VLDB6 2013 3031
VLDB6 2210 3282
VLDB6 2438 3545
VLDB6 2905 3927
VLDB6 3419 4150
VLDB6 3946 4322
VLDB6 4574 4519
VLDB6 5430 4769
VLDB6 6256 4967
VLDB6 7165 5158
VLDB6 8165 5329
As of right now, we only convert omnivel to usp format.
Modifications are being made to the database loading program
to recognize usp format. For that reason, we have a new
line header entry (VelTyp) that specifies the velocity for-
mat the usp dataset contains, so that usp format may be
entered into the database.
promax
ProMAX Data Export
CDP TIME SEMB_VEL
---------------------------------------------------------------------------------
100.0 274.5 1485.0
1672.2 1866.4
2626.6 1913.1
3493.3 2058.6
150.0 244.9 1476.6
1672.5 1824.0
3151.0 1913.1
6341.3 2233.1
200.0 237.3 1484.0
1624.2 1830.3
3055.2 1956.1
5449.1 2252.0
tdfn
9TDFN 824 40341400 43282160 61943584 68814488 83535848
9924 400
1TDFN 648 31501064 34451432 39362344 49174256 69794472
79615336 8746 401
9TDFN5864 9433
401
9TDFN 656 30521064 35431464 45252408 60954736 90415520
97285768 9924 402
9TDFN 624 34451432 52122216 65864344 81575664 9630
403
NOTE: As many TDFN cards as desired may be used per func-
tion location. The last card in the function must begin
with 9TDFN. vomit does not read the number associated with
any other TDFN card so you may repeat the 1TDFN card as many
times as you wish for ease of function construction. You
may also repeat the sequence 1TDFN through 8TDFN as may
times as you wish. The only card that ends a function read
is the 9TDFN card.
tdq
# FUNCTION_TYPE = TVave
comment (not part of Format) Available options here
include
comment TVave =time, average vel
comment TVint =time, interval velocity
comment TVrms =time, rms vel
comment TD =time, depth
comment DVave =Depth, average vel
comment DVint =Depth, interval velocity
comment DVrms =Depth, rms vel
comment DT =Depth, two-way time
# LINEAR_UNITS = METERS
# DATUM = 0.0
#---------------------------------------------
1 441814.0 6484017.0 114.00 1495.00
comment (not part of Format)
comment 1 is sequential function number, next two
values are geog X,Y
comment then function pairs
comment
201.00 1612.41
456.00 1773.04
769.00 1909.53
1042.00 1979.37
1327.00 2015.83
1815.00 2095.72
1990.00 2118.55
2274.00 2174.26
2441.00 2288.60
2871.00 2555.78
3161.00 2752.26
3753.00 3081.76
4389.00 3384.34
5030.00 3647.79
5462.00 3829.42
2 441821.0 6484517.0 110.00 1489.00
299.00 1691.93
591.00 1830.35
809.00 1920.29
1090.00 1984.60
1414.00 2038.08
1687.00 2078.95
2073.00 2130.51
2359.00 2209.97
2449.00 2287.47
2915.00 2593.86
3330.00 2858.34
3981.00 3188.78
4467.00 3420.75
5375.00 3792.38
In the Landmark TDQ manual it stiuplates that whatever
columns are used on the first function card define the
output for the rest of the file. If you start messing
with your output be certain to not change the column
registry throughout the file.
ukooa
-999999999999999-999999999999999
11 70 TRIDR10100052.8N0603247.2W 566850 59893
0
200 5091 400 5427 600 5746
800 6014
1000 6256 1200 6458 1400 6655
1600 6857
1800 7155 2000 7448 2200 7696
2400 7979
2600 8287 2800 8680 3000 8963
3200 9151
3400 9339 3600 9527 3800 9717
4000 9907
420010097 440010211 460010299
480010388
500010476 520010564 540010649
560010723
580010797 600010871 620010945
640011044
660011216 680011388 700011559
720011731
740011903 -1 -1 -1 -1
-1 -1
END
EOF
ukooa1
UKOOA 8.3.1 Ascii Card Format
From OmniVel, by Priemere GeoTechnology LLC
30OCT98(Fri) 4:29p by David Greenwood (zdgg01)
Time/Vrms pairs (feet)
1001 17250100418.7N0600633.5W 724007 81131
0
600 5001 800 5053 1000 5129
1200 5242
1400 5369 1600 5478 1800 5575
2000 5740
2200 5940 2400 6181 2600 6440
2800 6711
3000 6869 3200 7019 3400 7193
3600 7358
3800 7510 4000 7713 4200 7875
4400 7975
4600 8041 4800 8095 5000 8138
5200 8174
5400 8207 5600 8242 5800 8283
6000 8325
6200 8363 6400 8403 6600 8444
6800 8484
7000 8523
END
EOF
ukooa2
H0100 SURVEY AREA BLOCK 22/17 AND 18
H0200 SURVEY YEAR 1993
H0201 TAPE DATE 08.12.98
H0202 TAPE VERSION UKOOA P1/1990
H0300 CLIENT AMOCO U.K.
H0400 GEOPHYSICAL CONTRACTOR WESTERN GEOPHYSICAL
H0500 POSITIONING CONTRACTOR GEOTEAM EXPLORATION
H0600 POSITIONING PROCESSING
H0700 POSITIONING SYSTEM VARIOUS
H0800 COORDINATE LOCATION BIN CENTRE
H0900 OFFSET ANTENNA-CENTRE SRCE
H1000 CLOCK TIME GMT
H1100 RECEIVER GROUPS PER SHOT 6X288
H1400 SURVEY DATUM
H1500 POST PLOT DATUM
H1600 DATUM SHIFT: N/A
H1601 SHIFT CONSTANTS: N/A
H1700 VERTICAL DATUM: MEAN SEA LEVEL
H1800 PROJECTION TYPE: TM
H1900 PROJECTION ZONE: N/A
H2000 GRID UNITS: METRE
H2200 CENTRAL MERIDIAN: 0E
H2600 AMOCO VELOCITY DATA
H2600 AREA: BLOCK 22/17 AND 18
H2600 NAME: NORTH SEA MONTROSE/ARBROATH
H2600 LINES: INLINES MC93-1290 TO 2970
H2600 POINT NUMBER: CROSSLINE
H2600 PICKED STACKING RMS VELOCITIES
H2600 (POST COMMON OFFSET MIG)
H2600 TWO WAY TRAVEL TIME
H2600 NOTE: VELOCITIES WERE RE-GRIDDED PRIOR TO OUTPUT
H2600 GRID DETAILS:
H2600 X1 430291.63 Y1 6328563.37 LINE 0 XL 0
H2600 X2 431956.73 Y2 6409796.31 LINE 0 XL 6500
H2600 X3 374053.44 Y3 6329716.14 LINE 4500 XL 0
H2600 X4 375718.55 Y4 6410949.08 LINE 4500 XL 6500
C1289.99 1549.157 358.85N 65124.55E
414567.06348253.0
U 1 134 1481 2 228 1541 3
361 1635
U 4 452 1669 5 551 1756 6
726 1796
U 7 786 1837 8 833 1837 9
923 1857
U 10 967 1884 11 1111 1891 12
1228 1910
U 13 1481 1936 14 1684 1961 15
1969 1984
U 16 2072 1991 17 2287 1999 18
2524 2031
U 19 2723 2072 20 2791 2078 21
2833 2092
U 22 2965 2199 23 3024 2226 24
3077 2314
U 25 3147 2441 26 3205 2589 27
3299 2650
U 28 3405 2737 29 3467 2811 30
3523 2824
U 31 3570 2858 32 3709 2979 33
3839 3073
U 34 4188 3308 35 4501 3489 36
5499 3946
C1290.01 1589.057 414.83N 65128.10E
414577.06348752.0
U 1 135 1481 2 243 1548 3
359 1635
U 4 473 1716 5 554 1763 6
783 1816
U 7 929 1853 8 1106 1866 9
1319 1879
U 10 1501 1955 11 1676 1978 12
1888 1984
U 13 1988 1986 14 2196 1991 15
2279 1991
U 16 2581 2038 17 2805 2085 18
2936 2166
U 19 3008 2233 20 3071 2394 21
3196 2562
U 22 3266 2683 23 3326 2740 24
3387 2797
U 25 3473 2861 26 3587 3012 27
3779 3086
U 28 3990 3178 29 4198 3266 30
4725 3510
U 31 5499 3866
usp
Here the input is a standard USP velocity dataset composed
of single trace records. A scan of a legal dataset looks
like
scan -NCdpVelin
line header values after default check
# of bytes in line header= 1548 1548
# of bytes in line header= 1548 1548
# of bytes in output line header= 1565
# of samples/trace = 750
sample interval = 8
traces per record = 1
records per line = 4
format of data = 3
luin = 2
input data set name = CdpVelin
ns (starting trace) = 1
ne (ending trace ) = 1
rs (starting record) = 1
re (ending record) = 4
Group interval =
OAC Line =
Number ampl. histogrm bins= 10
NOTE: a bin = (trcmax-trcmin)/nbin
verbose output = F
rec trc gi di si_x10 src_pt sp/di li
dist static
RecNum TrcNum RecInd DphInd SrcLoc SoPtNm SrcPnt LinInd
DstSgn StaCor
801 1 0 801 0 0 0 0
0 0
802 1 0 802 0 0 0 0
0 0
803 1 0 803 0 0 0 0
0 0
804 1 0 804 0 0 0 0
0 0
Spread Summary:
Least positive distance = 0.
Most positive distance = 0.
STOP: 0
charisma
Here the input is the same format as a standard USP
dataset, with the additional requirement: up to 21
time/depth pairs must be entered into the trace headers
in the TVPTxx/TVPVxx locations, where xx ranges from 1
to 21. A zero time entry in TVPTxx location for xx
from 2 to 21 signals the end of the pairs. Time must
be 2-way time, in the units of the data; depth is in
feet or meters. An excerpt from a scan of some valid
charisma-format data, using the -V option in scan,
looks like:
TRACEHEADER
......
TVPT01 1522 51(I2) TVPV01 1517 52(I2)
TVPT02 2261 53(I2) TVPV02 2189 54(I2)
TVPT03 2577 55(I2) TVPV03 2507 56(I2)
TVPT04 2768 57(I2) TVPV04 2814 58(I2)
TVPT05 3040 59(I2) TVPV05 3223 60(I2)
TVPT06 0 61(I2) TVPV06 0 62(I2)
TVPT07 0 63(I2) TVPV07 0 64(I2)
TVPT08 0 65(I2) TVPV08 0 66(I2)
TVPT09 0 67(I2) TVPV09 0 68(I2)
TVPT10 0 69(I2) TVPV10 0 70(I2)
TVPT11 0 71(I2) TVPV11 0 72(I2)
TVPT12 0 73(I2) TVPV12 0 74(I2)
TVPT13 0 75(I2) TVPV13 0 76(I2)
TVPT14 0 77(I2) TVPV14 0 78(I2)
TVPT15 0 79(I2) TVPV15 0 80(I2)
TVPT16 0 81(I2) TVPV16 0 82(I2)
TVPT17 0 83(I2) TVPV17 0 84(I2)
TVPT18 0 85(I2) TVPV18 0 86(I2)
TVPT19 0 87(I2) TVPV19 0 88(I2)
TVPT20 0 89(I2) TVPV20 0 90(I2)
TVPT21 0 91(I2) TVPV21 0 92(I2)
......
In this example, there are 5 valid time/depth pairs;
TVPT06 being zero signals the end of the valid pairs
for this trace. There is no requirement that each
trace must have the same number of time/depth pairs.
vxos
Offset 0.000000 402.272736 -8.000000 Count 4 6
Units 1.000000 97.727272 8.000000 4 220 750
Segment = 1 Name NO_PICK_NAME_HERE color =
-43 picks = 6
1.000000 3627.272705 848.000000
1.000000 4018.181885 1432.000000
1.000000 4702.272461 2152.000000
1.000000 6265.909180 3568.000000
1.000000 7634.090820 4872.000000
1.000000 8611.363281 5888.000000
Segment = 2 Name NO_PICK_NAME_HERE color =
-43 picks = 4
2.000000 3236.363525 616.000000
2.000000 5190.909180 1856.000000
2.000000 7243.181641 4368.000000
2.000000 8806.818359 5840.000000
Segment = 3 Name NO_PICK_NAME_HERE color =
-43 picks = 6
3.000000 3040.909180 600.000000
3.000000 3627.272705 1008.000000
3.000000 5190.909180 1432.000000
3.000000 7145.454590 3352.000000
3.000000 8122.727051 5248.000000
3.000000 9295.454102 5800.000000
Segment = 4 Name NO_PICK_NAME_HERE color =
-43 picks = 5
4.000000 3040.909180 616.000000
4.000000 4800.000000 1640.000000
4.000000 7047.727051 2344.000000
4.000000 8611.363281 4320.000000
4.000000 9588.636719 5792.000000
vds3d
1MC3D1 404 650 680 1255 1 1 40
41.0365.65 1
0TDFN 422 767
U4H0000
1TDFN 10 5015 500 5743 700 60151000 63441300 66651700
70992000 7415U4H0000
9TDFN2400 79153000 83883400 86334400 92326000
9954800010716 U4H0000
0TDFN 422 896
U4H0000
1TDFN 10 5016 500 5774 700 60221000 63201300 66191700
70782000 7393U4H0000
9TDFN2400 79553000 84063400 86144400 91006000
9797800010585 U4H0000
NOTE: The entries on the OTDFN card are LinInd and DphInd
as used in USP. Also as many TDFN cards as desired may be
used per function location. The last card in the function
must begin with 9TDFN. vomit does not read the number
associated with any other TDFN card so you may repeat the
1TDFN card as many times as you wish for ease of function
construction. You may also repeat the sequence 1TDFN
through 8TDFN as may times as you wish. The only card that
ends a function read is the 9TDFN card. It remains to be
seen how this will interact with the VDS. The OBU has
requested this option and it will NOT be changed without
consultation with the gals and guys in New Orleans.
western3d
byte: format: description:
1 - 7 A7 Line number (left justified)
8 - 12 I5 Shotpoint number
13 A1 Reshot symbol
14 - 26 A13 Blank
27 - 34 F8.3 Longitude
35 - 42 F8.3 Latitide
43 - 55 A13 Blank
56 A1 Units F -feet M - meters
57 - 60 I4 Number of time-velocity
pairs
61 - 65 I5 Time 1 (ms)
66 - 70 I5 Time 2
71 - 75 I5 Time 3
(M) - (M+4) I5 Time N where M = 56+5*N
(M+5) - (M+9) I5 Velocity 1 ( ft/sec or
m/sec)
(M+10) - (M+14) I5 Velocity 2
.
.
.
(P) - (P+4) I5 Velocity N where P= 56=10*N
(P+5) - 400 A?? Blank
Max of 34 time-velocity pairs per location, missing
pairs will be blank.
Here is an example:
1339 2495 -90.100 28.113
F 28 0 420 740 860 1140 1260 1460 1620 1820 1980
2180 2380 2500 2620 2980 3180 3500 4460 4860 5260 6060
6740 7300 7800 8300 8800 9060 9100 4900 5020 5100 5170
5340 5410 5480 5580 5660 5740 5830 5920 6110 6290 6690
7050 7150 7750 7980 8330 8710 8840 8960 9050 9140 9210
9240 9260
western3d1
CONT V6M
LINE
AREA
INFO
COM1 V6M SHAHDENIZ-3D-production
COM2 VELOCITIES OUTPUT FROM IVP
PNMO
SPNT 307920 2280.0 436222 4428793
102
VELF 307920 0 126 1454 236 1521 381 1565
686 1632 850 1681
VELF 1106 1729 1261 1802 1625 1896
1743 1956 1905 1997
VELF 2023 2021 2205 2097 2302 2152
2437 2228 2531 2233
VELF 2654 2286 2819 2334 3133 2421
3528 2553 3657 2581
VELF 3829 2646 4022 2764 4298 2818
4587 2871 4936 2999
VELF 5059 3031 5267 3089 5426 3118
5710 3153 6021 3205
VELF 6721 3355 8495 3581
SPNT 307960 2320.0 436671 4429012
102
VELF 307960 0 86 1454 265 1545 560 1623
748 1666 1145 1729
VELF 1290 1797 1527 1850 1629 1889
1754 1956 1866 1991
VELF 2045 2044 2195 2092 2325 2174
2501 2214 2664 2271
VELF 2808 2339 2969 2392 3136 2444
3264 2496 3453 2577
VELF 3668 2617 3895 2703 4319 2852
4720 2924 4957 3002
VELF 5044 3016 5242 3069 5361 3109
5753 3182 5968 3222
VELF 6796 3383 8500 3561
xsd Units 1.000000 97.727272 8.000000 4
220 750 Offset 0.000000 402.272736 -8.000000
Count 4 6
Segment = 1 Name NO_PICK_NAME_HERE color =
-43 picks = 6
1.000000 3627.272705 848.000000
1.000000 4018.181885 1432.000000
1.000000 4702.272461 2152.000000
1.000000 6265.909180 3568.000000
1.000000 7634.090820 4872.000000
1.000000 8611.363281 5888.000000
Segment = 2 Name NO_PICK_NAME_HERE color =
-43 picks = 4
2.000000 3236.363525 616.000000
2.000000 5190.909180 1856.000000
2.000000 7243.181641 4368.000000
2.000000 8806.818359 5840.000000
Segment = 3 Name NO_PICK_NAME_HERE color =
-43 picks = 6
3.000000 3040.909180 600.000000
3.000000 3627.272705 1008.000000
3.000000 5190.909180 1432.000000
3.000000 7145.454590 3352.000000
3.000000 8122.727051 5248.000000
3.000000 9295.454102 5800.000000
Segment = 4 Name NO_PICK_NAME_HERE color =
-43 picks = 5
4.000000 3040.909180 616.000000
4.000000 4800.000000 1640.000000
4.000000 7047.727051 2344.000000
4.000000 8611.363281 4320.000000
4.000000 9588.636719 5792.000000
xsdheader
No_Seg 4.000000
Max_Pick 6.000000
UnitRec 1.000000
UnitTrc 1.000000
UnitSmp 8.000000
OffsetRec 0.000000
OffsetTrc 0.000000
OffsetSmp -8.000000
NumRec 4.000000
NumTrc 220.000000
NumSmp 750.000000
Segment 1.000000
Name NO_PICK_NAME_HERE
Color -43.000000
Picks 6.000000
Pick
Record 1.000000
Trace 33.000000
Sample 107.000000
RasValue 0.673367
DstSgn 3641.000000
.
. picks deleted for brevity
.
.
Segment 2.000000
Name NO_PICK_NAME_HERE
Color -43.000000
Picks 4.000000
Pick
Record 2.000000
Trace 29.000000
Sample 78.000000
RasValue 0.783920
DstSgn 3248.000000
.
. picks deleted for brevity
.
.
Pick
Record 4.000000
Trace 94.000000
Sample 725.000000
RasValue 0.371859
DstSgn 9630.000000
vip **Coordinates:
**axis1 time orig1 0 inc1 100 n1 119 d1 0.000000
**axis2 time orig2 1 inc2 10 n2 69 d2 1.000000
**axis3 time orig3 1 inc3 10 n3 50 d3 1.000000
**min/max: 7878 13352
**location 20 1
HANDVEL 10020
1949 10000 4450 10522 5570 10559
8890 11338
11140 11338
**location 120 1
HANDVEL 10120
1949 10000 2260 10021 3230 11078
4920 11671
5580 10893 6400 10874 7180 11300
8890 11338
11140 11338
zmap
1 436222.00 4428793.00 0.00
1454.00
1 436222.00 4428793.00 126.00
1454.00
1 436222.00 4428793.00 236.00
1594.29
1 436222.00 4428793.00 381.00
1634.08
1 436222.00 4428793.00 686.00
1712.02
1 436222.00 4428793.00 850.00
1872.11
1 436222.00 4428793.00 6021.00
4042.55
1 436222.00 4428793.00 6721.00
4440.70
1 436222.00 4428793.00 8495.00
4331.55
2 436671.00 4429012.00 0.00
1454.00
2 436671.00 4429012.00 86.00
1454.00
2 436671.00 4429012.00 265.00
1586.87
2 436671.00 4429012.00 560.00
1690.00
BUGS
Unknown but CERTAIN to exist. If this routine does some-
thing unexpected [like work] don't waste a lot of your time
trying to figure it out, just call me right away and I will
get on it. I constantly test this routine with a battery of
input matrices, converting between every type of format and
doing every type of velocity and sample unit conversion.
However as more datasets and conversions get used I expect
something will break.
SEE ALSO
anmo(1), bdnmo(1), velin(1) velspec(1) vtispec(1) vtinmo(1)
rnmospec(1)
AUTHOR
P.G.A. Garossino, August 96 [APR: 3932]
M.A. Miller [ATTC: 3593]
COPYRIGHT
copyright 2001, Amoco Production Company
All Rights Reserved
an affiliate of BP America Inc.
Man(1) output converted with
man2html