NAME

     binstk - stack within cdp bins

SYNOPSIS

     binstk [ -Nntap ] [ -Ootap ] [ -S ] [ -A ] [ -3d ] [  -xffar
     ] [ -xddx ] [ -V ] [ -? ]

DESCRIPTION

     binstk takes each input cdp record and  arranges  the  input
     traces  into  bins based on an input spread model and stacks
     the traces with whatever has  been  accumulated  there.  The
     final  output  will have each trace normalized by the number
     of live traces that went into  creating  it.  Currently  the
     user  should run bdnmo with a single brute velocity function
     (i.e. single velocity trace) on the  data  before  input  to
     binstk  to  minimize NMO variations within bins.  The output
     data must of course then be run through bdnmo  -R  with  the
     same velocity function.

     Currently the only indexing information  that  will  survive
     intact  will be the CDP or DI number, the LI or line number,
     and the trace distance (which will be  equal  to  the  model
     spread distances).

     binstk gets both its data and its  parameters  from  command
     line  arguments.  These arguments specify the input, output,
     and the spread parameters, and verbose printout, if desired.

  Command line arguments
     -N ntap
          Enter the input data set name or file immediately after
          typing -N.  This may be an input pipe.  This input file
          should include the  complete  path  name  if  the  file
          resides in a different directory. Example -N1/vsp/dummy
          tells the program to look for file 'dummy' in directory
          'vsp'.

     -O otap
          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).

     -S   Enter the command line argument '-S' for bin option  if
          spread  is  split.  This  option  obviates  the -A flag
          below.

     -A   Enter the command line argument '-A'  to  use  absolute
          trace distances.  This is useful when processing 2-boat
          marine data and 3-d data where sign specifies whether a
          shot ocurred before or after a group.

     -3d  Enter the command line argument '-3d' to tell the  pro-
          gram  the  input  is  3D CDP data.  This allows reading
          more info from the line header,  i.e.  MnLnIn,  MxLnIn,
          MnDpIn, MxDpIn, CDPFld.

     -xf far
          Enter the far  (maximum)  offset  (ft,m).   For  single
          ender  with negative trace distances this will be nega-
          tive; for positive trace distances this will  be  posi-
          tive.  For split spreads this value will be negative.

     -xd dx
          Enter the bin size  (ft,m)  for  the  input  cdp  data.
          Note: the bin option could easily result in a different
          number of traces per record on output.   In  fact  this
          will  be  equal to the number of bins determined by the
          spread geometry.

     -V   Enter the command line argument '-V' to get  additional
          printout.

     -?   Enter the command line  argument  '-?'  to  get  online
          help.   The program terminates after the help screen is
          printed.

EXAMPLE

     Given a single velocity trace  (created  from  one  velocity
     function using velin) a typical flow might be:

     bdnmo -Nincdps -vvel_trc |

     binstk -xd100 -xf15000 -A |

     bdnmo -Obincdps -vvel_trc -R

     where the spread has been  modeled  as  a  single  ender  of
     15000' with bin size 100' (resulting in 151 output traces).

COPYRIGHT

     copyright 2001, Amoco Production Company
               All Rights Reserved
          an affiliate of BP America Inc.