|
OpenZGY/Python API and Internals (ALPHA)
Access seismic data stored in ZGY format.
|
Decimation algorithms to output low resolution bricks. More...
Classes | |
| class | DecimationType |
| Possible algorithms to generate LOD bricks. More... | |
Functions | |
| def | decimate (brick, algo, **kwargs) |
| def | decimate8 (bricks, algo, **kwargs) |
Decimation algorithms to output low resolution bricks.
Decimation algorithms to output low resolution bricks.
| def openzgy.impl.lodalgo.decimate | ( | brick, | |
| algo, | |||
| ** | kwargs | ||
| ) |
Decimate a single input brick to produce one smaller output brick.
| def openzgy.impl.lodalgo.decimate8 | ( | bricks, | |
| algo, | |||
| ** | kwargs | ||
| ) |
Decimate 8 equal-sized input bricks to produce one output. Currently not used in production code. Only in the unit test. The genlod module prefers to split up and paste its data itself. This function shold perhaps be moved to the unit test module. Most of the decimation algorithms operate om a local 2x2x2 region for each output sample. So it makes no difference whether we decimate each input brick and then combine them, or the other way around. Combining last *might* use less memory if lazy evaluation works. Combining first might help the algorithm perform better (LowPass) or faster (WeightedAverage?)
1.8.17