Normally, the number of filter coefficients is many fewer than the number of data points, but here we have very many more. Indeed, there are na times more. Variable filters require na times more memory than the data itself. To make the nonstationary helix code more practical, we now require the filters to be constant in patches. The data type for nonstationary filters (which are constant in patches) is introduced in module nhelix, which is a simple modification of module helix . nhelixnon-stationary convolution What is new is the integer valued vector pch(nd) the size of the one-dimensional (helix) output data space. Every filter output point is to be assigned to a patch. All filters of a given patch number will be the same filter. Nonstationary helixes are created with createnhelixmod, which is a simple modification of module createhelixmod . createnhelixmodcreate non-stationary helix Notice that the user must define the pch(product(nd)) vector before creating a nonstationary helix. For a simple 1-D time-variable filter, presumably pch would be something like .For multidimensional patching we need to think a little more.
Finally, we are ready for the convolution operator. The operator nhconest allows for a different filter in each patch. nhconestnon-stationary convolution A filter output y(iy) has its filter from the patch ip=aa%pch(iy). The line t=a(ip,:) extracts the filter for the ipth patch. If you are confused (as I am) about the difference between aa and a, maybe now is the time to have a look at beyond Loptran to the Fortran version.
Because of the massive increase in the number of filter coefficients, allowing these many filters takes us from overdetermined to very undetermined. We can estimate all these filter coefficients by the usual deconvolution fitting goal ()
(21) |
(22) |
Experience with missing data in Chapter shows that when the roughening operator is a differential operator, the number of iterations can be large. We can speed the calculation immensely by ``preconditioning''. Define a new variable by and insert it into (22) to get the equivalent preconditioned system of goals.
(23) | ||
(24) |
The fitting (23) uses the operator .For we can use subroutine nhconest() ; for the smoothing operator we can use nonstationary polynomial division with operator npolydiv(): npolydivnon-stationary polynomial division Now we have all the pieces we need. As we previously estimated stationary filters with the module pef , now we can estimate nonstationary PEFs with the module npef . The steps are hardly any different. npefnon-stationary PEF Near the end of module npef is a filter reshape from a 1-D array to a 2-D array. If you find it troublesome that nhconest was using the filter during the optimization as already multidimensional, perhaps again, it is time to examine the Fortran code. The answer is that there has been a conversion back and forth partially hidden by Loptran.
Figure shows a synthetic data example using these programs. As we hope for deconvolution, events are compressed. The compression is fairly good, even though each event has a different spectrum. What is especially pleasing is that satisfactory results are obtained in truly small numbers of iterations (about three). The example is for two free filter coefficients (1,a1,a2) per output point. The roughening operator was taken to be (1,-2,1) which was factored into causal and anticausal finite difference.
I hope also to find a test case with field data, but experience in seismology is that spectral changes are slow, which implies unexciting results. Many interesting examples should exist in two- and three-dimensional filtering, however, because reflector dip is always changing and that changes the spatial spectrum.
In multidimensional space, the smoothing filter can be chosen with interesting directional properties.
Sergey, Bob, Sean and I have joked about this code being
the ``double helix'' program because there are two multidimensional
helixes in it, one the smoothing filter, the other the deconvolution filter.
Unlike the biological helixes, however, these two helixes
do not seem to form a symmetrical pair.