Reflection PDF
Reflection PDF
Reflection PDF
In the following the complete processing of seismic reflection data is described including import of the
seismic data (chap. I), crosscorrelation (optional for vibration data, chap.II), setting the geometry
(chap. III), filtering the shot data (chap. IV), performing the velocity analysis and stacking (chap. V).
Please use in addition to this user‘s guide the handbook and the online help.
The guide describes both the processing of “normal” shot data and of horizontal vibration data. The
processing of horizontal vibration data needs some more steps which are highlighted by red.
Plotmode: Wigglemode
XYScaledPlot activated
Scale: setting depends on the amplitude values of the data.
The amplitude values multiplied with scale gives the
wiggles size in pixels. The value must be adapted to the
original data values.
O p t i o n a l l y yo u al s o m ay act i v a t e t h e o p t i o n
Tracenormalize. Then the option Scale directly gives you
the wigglesize in pixels.
a.. choose the datafiles from the openfile dialog (multiple choice using the shift or str-key) : all
choosen original data files are sorted with ascending order of the filenames. Problems may occur if the
files don't have the same length (e.g. file1, file2,..., file11). In this case a warning message appears. In
order to avoid this the filenames should be chosen in such a way: file001, file002, ... file125.
After having chosen all the wanted datafiles the combined datafile including all the shots is displayed
using the actual plot settings. Because of the normally huge number of traces and the choosen
plotmode (Wigglemode, XYScaledPlot) the screen display resolution may be too small to plot the data
correctly (XScale too small). In this case choose the Zoom-option in order to only display a small part
of the data in x-direction. The plot option point mode allows y higher resolution but it is not so useful
for the further processing, e.g velocity analysis.
NOTE: The standard display within the 2D-dataanalysis uses the product of the given traceincrement
and the actual tracenumber for the axis display. Therefore this display does not represent the correct
coordinates for the combined shot data and you may ignore them. But you don’t have to worry about
them because the subsequent sorting and stacking is always done based on the traceheader coordinates
(see chap. III). The coordinates of resulting stacked section (see chap. V) however are displayed
correctly within the
standard display.
If the data have been acquired using a vibrator the data must be first crosscorreltated with the sweep
signal before these can be interpreted. The vibrosource emits a long sinusoidal signal with varying
frequency over several seconds (in this case 10 s). The recorded signal is a mixture of many
time-delayed copies of the signal. Cross-correlation is then used as a trace compression using the
original signal and the observed data to unravel all of this.
The processing flow:
The resulting
crosscorrelated
traces now are
comparible to
“normal” shot
data (e.g. using
a hammer or an
explosive
source).
If the geometries have been already entered during the data acquisition and REFLEXW allows to
automatically take over these geometries the geometry is shown in a tabella with shot number, shot
position and receiver line position. If the geometry is okay you may leave the geometry settings by
deactivating the option CMP and go on with chapter IV.
If the geometry is not correct you must proceed with the following steps:
3. There are different possibilities to define the geometry. The most convenient way is to use a
standard geometry (option moving line and option fixed line) for a selectable number of traces. Apart
from the standard geometry it is also possible to edit the geometry of single traces (option edit single
traces) or to load the geometry from an ASCII-file (option read from ASCII-file).
a. Activating fixed line allows you to define the geometry for a fixed geophone line for different shot
points. An example of the input parameters is shown on the next figure. Nr.of channels is the number
of channels per shot. First and last trace define the range on the profile for which the standard
geometry should be valid. This gives you the opportunity to declare standard geometries for different
ranges of the profile. Instead of the first and last trace it is also possible to define the range using the
original field record numbers. Shotstart is the position of the shot of the first ensemble, shot increment
is the distance between successive shots and shot offset is the distance between a shot and the profile
in perpendicular direction. Receiver increment is the distance between successive receivers and
receiver offset is the distance between a geophone and the profile in perpendicular direction. First
receiver and last receiver define the position of the geophones with respect to the shot. These are the
absolute coordinates in contrast to moving line where relative coordinates (to the shot) are used.
c. The option read from ascii-file allows you to read the geometry from an
ASCII-file. The ASCII file must exist under the path ASCII and must have the extension DST. Each
line of the ASCII file contains the following 6 informations:
tracenumber distance Shot-X-Pos Shot-Y-Pos receiver-X-Pos receiver-YPos
Defining the tracenumber gives you the opportunity to read the geometry only for a distinct part of the
data.
d. The option edit single traces allows you to change the geometry of each trace individually. When
activating this option the trace header Edit menu will be opened where you can edit the shot and
receiver coordinates for each trace separately.
4. If you want to apply a standard geometry (3.a or 3.b) you must activate the option
apply std. geometry in addition.
5. If necessary enter an additional standard geometry and apply it onto the profile or choose one of the
other geometry edit possibilities.
6. If the geometry setting is finished choose the option save geometry in order to save the geometry
within the traceheader coordinates of the file.
The aim of the pre-stack filtering is to prepare the dataset for the subsequent stacking. Therefore the
most important processing steps are:
- energy normalization
- elimination or suppression of the surface waves and other non desired waves
The energy normalization should be the first filter step especially if you are using multi-channel filters
(e.g. FK-filter) for the suppression of non desired waves.. This filter step is applied to correct for the
amplitude effects of wavefront divergence and damping. It is also necessary if a subsequent filter shall
be applied for eliminating the surface waves.
The easiest way would be a manual gain function, e.g. manual gain (y). In the case of strong surface
waves this gain recovery function is not very suitable. In this case the filter scaled windowgain(x) may
be a good choice.
To bo considered: Filtering and stacking are always done on the true amplitude data. The option
tracenormalize within the plotoptions is only a plotoption and does not effect the filtering/stacking
process. Therefore the option tracenormalize within the plotoptions should be deactivated because
otherwise the effect of the energy normalization may not be controlled correctly.
The second filter step consists of the elimination of the surface waves and other non desired waves.
For that purpose you may distinguish between editing and 2D-filter steps.
Editing may be used for muting (set to zero) special data parts or to delete single traces or trace ranges.
2D-filters may be used to suppress unwanted signals. A FK-filter may be a good choice.
In the following the processing using a scaled windowgain(x) and a FK-filter is described:
1. load the wanted raw data for which the geometry has already been defined (all shots are stored
within one file, see chap. I and II).
4. The filtered data have been plotted into the secondary window (depending on the settings of the
screen splitting within the plot option menu). Whereas in the original data only the surface waves and
the very first arrivals are visible due to the non normalized display the filtered data show clear
refracted waves for all distancies and some reflections. Now close the filter window and you must
enter the option File/ChangeSecondToPrimary in order to use the filtered dataset for the next desired
filter step.
Surface waves normally differ from the body waves in two siginifant characteristics. These properties
involve the frequency and the apparent velocity. Both are often significantly lower than those of the
body waves.
If a lower frequency content is inherent a high pass bandpassfiltering is the best choice.
If the bandpass filtering is not sufficient a fk-filtering might be useful. Here it must be considered that
no spatial aliasing occurs. This may happen if very low velocities are present together with a too high
receiver increment. Then after applying the fk-filter some energy of the surface waves will remain.
5.3 muting
1. load the wanted raw data for which a crosscorrelation has been done and the geometry has already
been defined (all shots are stored within one file, see chap. I to III).
2. enter the first filter bandpassfrequency within Processing/1D-filter, in this case a frequency range
between 40 and 150 Hz and a butterworth taper of order 3 has been used. The tracenormalize
plotoption has been activated in order to view the filter effects.
3. Enter the second filter step div. compensation under processing/gain which compensate for the
geometrcial divergence losses
5. Enter the fourth filter step spectrum spikes under processing/1D-filter which is suitable for
suppressing nearly mono-frequency noise which is not restricted to a special frequency but may vary
from trace to trace.
Now the data are ready for stacking (see chap. V).
Within this chapter we have discussed two example of a possible pre-processing. It is not possible to
give some general rules for the processing because of the huge different problems involved with the
datafiles. In any case a gain recovery (energy normalization) and a suppression of the unwanted onsets
must be performed.
3. click on CMP-sorting/stack
7. the mean traceincrement for the ensembles is asked for. This increment is used for the equidistant
display of the CMP or shot-ensembles.
11. set the left mouse button at the wanted positions within the semblance analysis window in order to
create a velocity model. The velocity model on the left is automatically updated.
15. The last velocity model remains and you may refine the model using the interactive adaptation or
may create a completely new model using the semblance or unnormalized corr. (see point 9).
17. Repeat step 14 until 16 until the last wanted CMP (shot) is reached
19. create a new 2D-model - after having activated the option create you are asked for the wanted 1-
dimensional velocity model. Choose the wanted models from the open file dialog (multiple choice
using the shift or str-key), enter a filename of the 2D-model and the interpolated 2D-model is plotted
into the right window.
21. Choose NMO-stack and load the wanted 2D-model using the option load 2D-model.
22. Enter the wanted sorting ensemble (e.g. CMP) and enter the ensemble range for the stacking (e.g.:
1. CMP and last CMP and increment whereby the increment should be set to 1). Start the stacking
using the option stack. Enter a filename for the stacked data and enter the traceincrement (a calculated
value based on the fileheader traceincrement of the original file is given by default). The stacked
section is stored under the path procdata using the processing label 0 and is shown in an additional
window. To be considered for the stack section: The default value of the trace increment is given by
the number of stack traces and the coordinate range. If this mean traceincrement does not equal any
increment between successive stack traces the resulting stack traces are obviously not equidistant. This
may happen for example if the shot interval is not equidistant for all shots. In this case the program
(from version 3.03) gives a warning message and asks if equidistant traces based on the mean
traceincrement shall be made from the non equidistant stack section. If this procedure is cancelled the
resulting stack section not equidistant and you must activate the plotoption TraceHeaderDistancies
(only enabled for the wiggle
mode) or you must make the
s t a c k s e c t i o n eq u i d i s t an t
afterwards.
The prestack migration is an alternative possibility for getting a stacked section. The resulting section
is automatically migrated and converted to depth.