It sounds like using a HorizonCube might be the approach you're looking for. This creates a dense collection of horizons, each representing a paleosurface. You can then examine your data by either slicing through it using a 3D HorizonCube slider or by flattening the seismic data based on all the horizons within the HorizonCube. This flattened view is known as the Wheeler domain, where the vertical axis represents Relative Geologic Time. Consequently, time-slicing within the Wheeler domain allows you to analyze your data in terms of (relative) geologic time.
To generate a HorizonCube, the initial step involves mapping a framework of key horizons. This is typically done using one of OpendTect's inversion-based horizon trackers. These trackers are efficient, offer full user control, and can track multiple horizons concurrently by minimizing the discrepancy between the horizon dip and the seismic dip. After defining the framework horizons, the intervals between them are filled with a dense set of additional horizons. This infilling process can be guided by a model (e.g., proportional, parallel to upper, parallel to lower horizons) or driven by the data itself (inversion-based, or tracking the dip-field).
Please note that to utilize these functionalities, you will need licenses for OpendTect Pro, the Dip-Steering plugin, the HorizonCube plugin, and the SSIS plugin. The SSIS plugin is specifically required if you intend to analyze your data within the Wheeler domain.
You can find helpful training videos and webinars on our website that demonstrate these workflows. For instance, this
training video illustrates how to track horizons using inversion-based algorithms.
I hope this explanation is helpful.
Best regards,
Paul