Seismic data conversion (stretching) from Depth domain to Time domain.
The seismic data conversion module from depth domain to time domain is used to transform seismic time data (such as arrival times of seismic waves) into time-related data corresponding to the Earth's subsurface layers. This process is essential for accurate modeling and analysis of geological structures, such as oil and gas reservoirs, and for conducting seismic exploration. The module works based on two input datasets: interval velocity data for each layer and the seismic time data. The conversion is performed by integrating the interval velocity with the time data, using a velocity-depth relationship, to translate the measured depth into the corresponding time.
Input DataItem
Input SEG-Y data handle - SEGY handle / link to seismic data file in depth domain. If Input mode - By trace vector is selected.
Input trace headers - input trace header data vector from the seismic data file in depth domain. If Input mode - By trace vector is selected.
Input gather - input gather seismic data file in depth domain. If Input mode - By gather is selected.
Input mode { By trace vector, By gather } - Input modes: By trace vector (trace vector + SEGY handler) or By gather (entire gather).
Depth velocity - input gather interval velocity file (depth domain).
Output file name - output file name for resulting seismic data in time domain.
Output time ratio - define an output sample interval for time domain.
Output time length - define the trace length in time domain.
V0 - replacement velocity m/s.
Determine output time - enable or disable an automatic output time definition.
Auto-connection - module is connected with previous (and next) modules in the workflow by default.
Bad data values option:
There are 3 options for corrupted (NaN) samples in trace:
Fix - fix corrupted samples.
Notify - notify and stop calculations.
Continue - continue calculations without fixing.
SegyReadParams - parameters for setting advanced parameters of reading seismic traces from disk:
Thread count (for SSD) - amount of treads for reading seismic traces from disk.
Bulk size (traces) - size of a chunk (data portion) for reading seismic traces from disk.
Bulk size - chunk size is RAM in megabytes that is required for each machine on the server (find this information in the Information, also need to click on action menu button for getting this statistics):
Number of threads - limit number of threads on main machine.
Skip - switch-off this module (do not use in the workflow).
Output DataItem - switch
Time tables - switch
Workflow example:
YouTube video lesson, click here to open [VIDEO IN PROCESS...]
Yilmaz. O., 1987, Seismic data processing: Society of Exploration Geophysicist
* * * If you have any questions, please send an e-mail to: support@geomage.com * * *