next up previous print clean
Next: Discussion Up: Brown and Clapp: Integrated Previous: Estimating and Handling Correlated

Real Data Results

Figure 2 illustrates the experiment. A VSP, donated by Schlumberger, is overlain by first break picks, obtained by picking from the first trace and crosscorrelating. Layer boundaries are shown as horizontal lines. Most layers contain more than three time/depth pairs. In some regions, the waveform is quite crisp, and the picks predictably appear accurate. In other regions, notably after 1.8 seconds, the wavelet coherency and amplitude are degraded, and the picks appear ``jittery''. Nonetheless, we assume a variance of 0.006 seconds in the picked VSP traveltimes, and compute the equivalent depth uncertainty from equation (9). The inverse of the depth uncertainty is directly input as the residual weight to equation (10).

 
showvsp
showvsp
Figure 2
Left: Schlumberger VSP, with first break picks (-) and layer boundaries (horizontal lines). Right: Residual weight associated with first break picks.
view burn build edit restore

Figures 3-6 illustrate the scheme we proposed earlier for simultaneously inverting VSP and surface seismic time/depth pairs for interval velocity.

Figure 3 is the ``proof of concept''. We simply add a positive correlated depth error, corresponding to ``anisotropy'' in layers 2-4, to the VSP time/depth pairs to simulate surface seismic data. The topmost panel contains the known (solid line) and the estimated (+) velocity perturbations. Our algorithm has reconstructed the known velocity perturbation quite well. The second panel from top shows the depth error produced by backprojecting the known (solid line) and estimated (+) velocity perturbations. The center panel contains the VSP (v) and seismic (s) time/depth pairs. The solid line shows the modeled depth, or the backprojected final estimated velocity. The second panel from bottom shows the estimated velocity function. Notice that we have declared 4 of the 26 layer boundaries as ``hard rock'' boundaries, per equation (6), in order to suppress large residual errors from occuring across the obviously high-velocity-contrast layer boundaries. Inspecting the bottom panel, we see that the residual appears uncorrelated.

Figure 4 illustrates that failure to account for correlated errors leads to an undesirable result. In this case, we add the same correlated depth error as in Figure 3 to simulate seismic data. Additionally, we add to the seismic data random errors with a standard deviation of 0.024 seconds, four times the assumed standard deviation of the VSP data. Finally, we add random errors with the same standard deviation (0.024 sec) to the VSP data, in the interval [1.25 1.46] seconds, to simulate a region of poor geophone coupling. We do not perform the correlated data error iteration outlined above, but instead simply solve equation (10). The most important panel to view is the residual panel; without explictly modeling the correlated errors, least squares optimization simply ``splits the difference'' between VSP and seismic error, causing bias in both. The v's correspond to VSP errors, the s's to seismic errors.

Figure 5 shows the application of our algorithm to the data of Figure 4. Instantly, we see that the estimated velocity perturbation and correlated depth error match the known curves reasonably well. The estimated perturbations don't match as well as in Figure 3 because of the random errors. The residual is random, though it appears to be poorly scaled in the region where we added random noise to the VSP. In fact, we have used the same residual weight as shown in Figure 2. If we know that we have bad data, we should reduce the residual weight accordingly. Additionally, we see that the final velocity function doesn't look as much like the ``known'' result of Figure 3, which had no additive random noise.

Figure 6 is the same as Figure 5, save for a change to the residual weight. We reduce the residual weight in the [1.25 1.46] sec. interval by a factor of 4. We notice first that the residual is both random and well-balanced. Also note that the estimated final velocity function much more resembles that of Figure 3, which is good. The modeled data, in the center panel, is nearly halfway in between the VSP and seismic data in the region of poor VSP data quality, which makes sense, since we have reduced the residual weight.

The last example underscores an important philosophical point, which we emphasized in the introduction and in Figure 1. All too often, when different data types fail to match, the differences are chalked up to the inaccuracy of the ``soft data''. In effect, by failing to account for correlated error, they assume that the soft data has a much larger variance than it really does. Our algorithm effectively adjusts the mean of the seismic pdf to match the mean of the VSP pdf.

In this example, we see that after removing the correlated error, the soft data (seismic) has in fact improved the final result, because the velocity more closely resembles that in Figure 3. Don't throw away the data! Use physics to model correlated errors and remove them from the data. It may not be as soft as you think.

 
misfit1
misfit1
Figure 3
Proof-of-concept plot. Positive depth perturbation (but no random errors) added to seismic time/depth pairs.


view burn build edit restore

 
misfit2
misfit2
Figure 4
Random errors added to VSP and seismic data of Figure 3. Correlated errors not handled. Residual is biased.
view burn build edit restore

 
misfit3
misfit3
Figure 5
Application of our algorithm to data of Figure 4. Residual is random, but poorly scaled in region where VSP random errors are larger.
view burn build edit restore

 
misfit4
misfit4
Figure 6
Same data as in Figure 5, residual weight reduced in region where VSP random errors are larger. Here, the ``soft'' seismic data has actually improved the velocity estimate, as it more closely resembles Figure 3.
view burn build edit restore


next up previous print clean
Next: Discussion Up: Brown and Clapp: Integrated Previous: Estimating and Handling Correlated
Stanford Exploration Project
4/29/2001