Abstract
Because conventional time‐migration algorithms are founded on the implicit assumption of locally lateral homogeneity, they leave events mispositioned when overburden velocity varies laterally. The ray‐theoretical depth migration procedure of Hubral often can provide adequate first‐order corrections for such position errors. Complex geologic structure, however, can so severely distort wavefronts that resulting time‐migrated sections may be barely interpretable and thus not readily correctable. A more accurate, wave‐theoretical approach to depth migration then becomes essential to image the subsurface properly. This approach, which transforms an unmigrated time section directly into migrated depth, more completely honors the wave equation for a medium in which variations in interval velocity and details of structural shape govern wave propagation. Where geologic structure is complicated, however, we usually lack an accurate velocity model. It is important, therefore, to understand the sensitivity of depth migration to velocity errors and, in particular, to assess whether it is justified to go to the added effort of doing depth migration. We show a synthetic data example in which the wave‐theoretical approach to depth migration properly images deep reflections that are poorly resolved and left distorted by either time migration or ray‐theoretical depth migration. These imaging results are, moreover, surprisingly insensitive to errors introduced into the velocity model. Application to one field data example demonstrates the superior treatment of amplitude and waveform by wave‐theoretical depth migration. In a second data example, deep reflections are so influenced by anomalous overburden structure that the only valid alternative to performing wave‐theoretical depth migration is simply to convert the unmigrated data to depth. When the overburden is laterally variable, conventional time migration of unstacked data can be as destructive to steeply dipping reflections as is CDP stacking prior to migration. A schematic example illustrates that when migration of unstacked data is judged necessary, it should normally be performed as a depth migration.
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have