NAME
bdnmo - module to apply/remove t(x,v) nmo correction
SYNOPSIS
bdnmo [ -Nntap ] [ -Ootap ] [ -vvtap ] [ -cvcvel ] [ -vsvscl
] [ -Hwhdrwrd ] [ -rsirs ] [ -reire ] [ -svvrs ] [ -evvre ]
[ -nsns ] [ -nene ] [ -S ] [ -R ] [ -T ] [ -E ] [ -B ] [ -V
] [ -XYrace ] [ -debug ] [ -? -h -help ]
DESCRIPTION
bdnmo takes a set of input traces and applies the dynamic
correction given by the t(x,v) moveout equation. Velocity
is a function of time and is read in from a velocity disk
file as created by velin, vomit or vi3d. Cubic spline
interpolation is used in the application / removal of the
NMO correction. The user may choose to output data from
before or after the velocity cross-over point in the moveout
map. The default is to output data from after the cross-over
point only. Should more than a single velocity cross-over
exist for a given trace only the last will be used. An
optional xgraph output dataset of the nmo map at a user
defined trace location is available.
bdnmo gets processing controls from the command line. Rea-
sonable defaults are set up. In addition, if no input file
name is given, the binary trace data are expected to be on
the standard input. However, a velocity model must be speci-
fied.
Command line arguments
-N ntap
Enter the full path of the file containing the data
set. If not specified, input is expected to be stan-
dard input. If standard input is not specified and
there is no input, e.g., program run in background,
expect a termination. (default standard input )
-O otap
Enter the full path of the output file. If not speci-
fied, output is expected to be standard output.
(default standard output )
-v vtap
Enter the full path of the file containing the velocity
model. This file is in USP format of RMS velocity
versus two way travel time. The velocity model must
have the same sample interval and number of samples per
trace as the attached seismic data. For 2D data there
should be one velocity trace per input seismic record.
Should the number of traces be less than the number of
associated seismic records, the last velocity trace
will be used for all remaining records. For 3D data
there should be as many velocity traces as there are
bins being corrected. Should there be less velocity
data than required, the last velocity trace in the
model will be used to correct all remaining bins.
(default none ).
-cv cvel
Optional constant velocity value. If this value is
nonzero the all other velocity options will be ignored
and no velocity file need be entered.
-vs vscl
Enter the scale factor to apply to all velocities.
(default = 1.0 ).
-Hw hdrwrd
Enter the trace header word mnemonic to extract signed
trace distance. Default = DstSgn
-ns ns
First trace in record to process (default = 1 )
-ne ne
Last trace in record to process (default = all )
-rs irs
First record to process (default = 1 )
-re ire
Last record to process (default = all )
-sv vrs
First velocity record to process (default = 1 ). If
attaching a 3D velocity cube containing N records of M
traces [i.e. N li's and Mdi's as output by vi3d ] enter
the appropriate start li number. If you have utop'd
the velocity cube to be N x M single trace records then
enter the appropriate start bin number.
-ev vre
Last velocity record to process (default = all )If
attaching a 3D velocity cube containing N records of M
traces [i.e. N li's and Mdi's as output by vi3d ] enter
the appropriate end li number. If you have utop'd the
velocity cube to be N x M single trace records then
enter the appropriate end bin number.
-E If present data associated with the portion of the
moveout map below the last sample cross-over will be
output.
-T If present data associated with the portion of the
moveout map above the last sample cross-over will be
output.(note: strange things could occur when applying
nmo, filtering, then removing nmo should more than one
sample cross-over be present)
-S If present apply internal trace header statics (before
nmo).
-R If present remove normal moveout
-B If present input velocity function is expected in
decreasing shot order.
-XY trace
If present the normal moveout sample map for the trace
requested will be output to a file name bdnmo_fcn.
This file may be accessed by xgraph for a plot of the
function. (i.e. xgraph -fg black -bg white -zg black -t
"Moveout Sample Map" -y "sample in" -x "sample out"
bdnmo_fcn)
-V Verbose mode. List command line and lineheader input
parameters.
-debug
Very Verbose mode. List RecNum, TrcNum for each velo-
city trace and RecNum, TrcNum, sequential record and
sequential trace for each seismic trace read. This is
useful to make certain that the correct velocity from
your velocity volume is being applied at a given record
of interest. Warning however, this will result in a
very large printout file and should be used for debug-
ging problems only [as the name suggests].
-? -h -help
Query mode. With this flag, bdnmo will give a descrip-
tion of the command line arguments and stop the pro-
gram.
BUGS
Unknown
AUTHOR
P. G. A. Garossino, EPTG Tulsa [pgarossino@amoco.com Socon
422-3932]
COPYRIGHT
copyright 2001, Amoco Production Company
All Rights Reserved
an affiliate of BP America Inc.
Man(1) output converted with
man2html