Azimuthal NMO Scanner

Description Scan a range of ellipticity and fast-direction values to help determine the azimuthal anisotropy parameters used by Azimuthal Anisotropic NMO.
Module(s) Quantitative Interpretation (QI)
Requirements Gathers, Velocity Model
Related Normal Moveout Correction, Creating an Angle Mute
Works with 2D, 3D Gathers


The Azimuthal NMO Scanner applies azimuthal anisotropic NMO correction across a range of ellipticity and fast-direction values, producing a family of corrected gathers — one for every combination of the two — rather than a single output.

Scan through the resulting gathers to find the combination that best flattens the data, or use them as input to the HTI Auto Picker to derive ellipticity and fast-direction volumes automatically. Either way, the picked values can then be used as constant or volume inputs to the Azimuthal Anisotropic NMO mode of Normal Moveout Correction.

Create an Azimuthal NMO Scanner Process

Create an Azimuthal NMO Scanner process
  1. In the Control Panel, open the Process tab.
  2. At the tab header, click the Add icon and select New Process.
  3. Search for or scroll down, and select Azimuthal NMO Scanner > Add.
  4. Type a name for the process and click OK and Close.

Define the scan parameters

Azimuthal NMO Scanner details panel
  1. Input: Select the migrated input gathers to be scanned. You must manually remove NMO correction from this volume prior to using this process.
  2. Ellipticities (%): The sequence of ellipticity percentage values (0–20%) to scan.
  3. Fast directions (degrees): The sequence of fast-direction azimuth values (0–179.99°) to scan.
  4. Model: Choose Azimuthal 2nd-order or Azimuthal 4th-order for the NMO equation.
  5. Offset source: Whether offset should be taken from the OFFSET header, or calculated from the source and receiver positions (SX/SY/GX/GY headers).
  6. Azimuth source: Available for 2D volumes only. Selects whether the Azimuth value should be calculated from the source and receiver positions (SX/SY/GX/GY headers), or taken from the OTRAV header. 3D volumes will always use OTRAV.
  7. Velocity: Select a velocity model, as a constant value or a volume.
  8. Velocity type: Select the type and unit of the velocity volume. The types and units available depend on whether the input gathers are in the time or depth domain:
    • For time-domain gathers:
      1. Interval Velocity in Time (m/s, km/s, or ft/s)
      2. RMS Velocity (m/s, km/s, or ft/s)
      3. Depth values sampled in Time (ZT) (m, km, or ft)
      4. Average Velocity in Time (m/s, km/s, or ft/s)
    • For depth-domain gathers:
      1. Interval Velocity in Depth (m/s, km/s, or ft/s)
      2. Average Velocity converted to Depth (m/s, km/s, or ft/s)
      3. Time values sampled in Depth (TZ) (ms or s)
  9. Effective η (eta): Available when Model is set to Azimuthal 4th-order. Either a volume or a constant value for the anisotropic parameter.
  10. Input azimuthal range: Narrow or Rich, depending on the azimuthal content of the data used to derive the velocity model (see Normal Moveout Correction for details on this choice).
    • Picking azimuth (degrees): Available when Input azimuthal range is set to Narrow. The velocity picking azimuth, as a constant or a volume. For Rich azimuthal coverage, the picking azimuth is instead derived automatically, halfway between the fast and slow directions.
  11. Stretch Method: Choose the stretch processing for the scanned gathers — no stretch processing, or use a stretch mute with a Cut-off and Ramp values.

Angle mute options

Angle mute options

An angle mute, as used by Creating an Angle Mute, is applied to each scanned gather:

  1. Inner/outer angles (degrees): Input the angle for the inner and outer mutes, with acceptable values ranging between 0 and 360 degrees.
  2. (Optional) specify an Inner angle protection and/or Outer angle protection to apply offset-domain mutes.
  3. Velocity smoothing length (ms): Additional smoothing can be applied to the velocities before use.
  4. Use vertical ramp: When checked, taper the mute with a Vertical ramp distance instead of a Ramp distance.