The Cube prepare module converts a velocity gather into a multi-threaded cube data item for use in downstream processing steps. It takes a post-stack velocity gather — typically the output of FXY Deconvolution, RTM 3D, or a Finite Difference model — and packages it into a cube structure that can be efficiently distributed across multiple processing threads. The output cube item is then available for connection to modules that require a cube-format input.

This module is a preparatory connector step and performs no modification to the amplitude or time content of the input data. Its sole purpose is to repackage the gather into a cube item so that subsequent modules in the workflow can access the data in the correct format. Pre-stack gathers are not supported — only post-stack velocity gathers should be connected to this module.

Theory

This module is used for velocity gather transformation. The input data must be a velocity gather; pre-stack data is not supported. It is designed for use with FXY Deconvolution, RTM 3D, and Finite Difference models only.

Input data

GGatherItem_IN

connect/reference to the Output Gather. It takes the output data from FXY Deconvolution, RTM 3D & Finite difference model

Connect this input to the output gather of the upstream module whose result you wish to repackage as a cube. Supported upstream sources include FXY Deconvolution, RTM 3D migration, and Finite Difference modeling modules. The gather must be a post-stack velocity gather (not a pre-stack common-midpoint gather). If no valid gather is connected when the module executes, processing will halt with an error. The gather axes are expected to be Trace-by-Trace with a Time sample axis.

Parameters

Number of threads

One less than total no of nodes/threads to execute a job in multi-thread mode. Limit number of threads on main machine.

Sets the number of parallel CPU threads used when splitting the input gather into the output cube. Internally, the gather is divided into segments — one per thread — so that downstream modules can process them concurrently. Increasing the thread count can reduce wall-clock processing time on multi-core machines, but setting it higher than the number of available CPU cores will not provide additional benefit and may degrade performance. The effective number of processing threads is this value plus one (the main thread). For most workstations, the default system value is appropriate.

Skip

By default, FALSE (Unchecked). This option helps to bypass the module from the workflow.

When set to TRUE, the Cube prepare module is bypassed entirely and the workflow continues without executing this step. This is useful for temporarily disabling the cube packaging step during testing or workflow development without removing the module from the processing chain. By default this option is FALSE (unchecked), meaning the module executes normally.

Output data

Cube item

the user can save the output gather as a cube item.

The output of this module is a Cube item — a thread-partitioned container holding the entire input velocity gather divided into segments for parallel processing. Connect this output to any downstream module that accepts a cube-format input. The cube item does not alter sample values; it simply reorganizes the gather data into a format suitable for multi-threaded cube-based processing workflows.

Information

There are no additional settings available for this module beyond the parameters listed above.

Examples

Actions

There are no action items available for this module

Video lesson

YouTube video lesson, click here to open [VIDEO IN PROCESS...]

Related articles

Yilmaz. O., 1987, Seismic data processing: Society of Exploration Geophysicist

* * *   If you have any questions, please send an e-mail to: support@geomage.com  * * *