|
<< Click to Display Table of Contents >> Navigation: Statics > Apply static shifts |
The Apply static shifts module applies pre-computed statics corrections to seismic gathers, shifting each trace in time to compensate for near-surface velocity variations, elevation differences, or residual moveout errors. The module accepts one or more static correction datasets (surface-consistent statics, trim statics, and structural factor statics) and combines them into a single composite shift applied trace by trace across the input gather.
Use this module after running a statics estimation procedure (such as refraction statics or surface-consistent statics) to apply the resulting corrections to your seismic data. It supports both forward application (correcting the data) and reverse application (removing previously applied corrections), making it suitable for iterative statics workflows. Multiple statics correction inputs can be connected simultaneously, and the module will sum all contributions before applying the final shift.
The main seismic data item flowing through the processing sequence. This carries the seismic traces to which static corrections will be applied.
An optional SEG-Y file handle for reading or writing seismic data in SEG-Y format within the processing flow.
The set of trace header values associated with the input gather. Header information (such as shot and receiver indices) is used to look up the appropriate static correction for each trace. If the Update trace headers parameter is enabled, the applied shift values are also written back into these headers.
The seismic gather (a collection of traces, e.g., a shot gather or CMP gather) to which the static shifts will be applied. Each trace in the gather is shifted individually according to its corresponding correction value.
An optional 2D stacked line associated with the processing flow, used when operating on post-stack or stacked-line data.
An optional crooked 2D line geometry descriptor. Used when the acquisition line is not straight and geometry-aware processing is required.
An optional 3D bin grid defining the CMP binning geometry. Used in 3D workflows to associate traces with their correct spatial positions for static correction lookup.
A sorted index of trace headers, enabling efficient gather-by-gather processing when the data is accessed in a sorted order (e.g., sorted by CMP or shot number).
The primary statics correction dataset to apply. This is typically the output of a statics estimation module (such as refraction statics, surface-consistent statics, or residual statics). The correction values are stored per trace identifier (shot and receiver) and are looked up for each trace in the input gather.
An expandable collection of additional statics correction datasets. Each connected dataset is summed together with the primary statics correction and any other additional corrections before the total shift is applied. This allows you to combine multiple statics solutions — for example, adding a residual statics correction on top of a refraction statics solution — in a single application step.
An expandable collection of azimuthal statics correction datasets, typically produced by azimuthal refraction statics analysis. These corrections account for directional near-surface variations and are added to the total static shift alongside any standard corrections. Connect one or more azimuthal correction items here when working with wide-azimuth 3D data where directional near-surface effects are significant.
Sets the maximum allowable static shift that will be applied to any trace, in milliseconds. If the computed correction for a trace exceeds this threshold in absolute value, the correction is suppressed (set to zero) for that trace, protecting against spuriously large shifts that may result from incorrect statics solutions or noisy input data. The default value is 0 ms, which disables the limit so that all computed corrections are applied without restriction. Set this to a positive value (for example, 50 ms or 100 ms) when you want to guard against erroneous large shifts corrupting your data.
When enabled, the total static shift applied to each trace is written into the corresponding trace header field. This records the applied correction for later reference or for use by downstream modules that read static shifts from headers. The default value is disabled. Enable this option when you need a permanent record of applied statics in the trace headers, for example before exporting data in SEG-Y format.
Controls whether the surface-consistent component of the statics correction is included in the applied shift. Surface-consistent statics decompose the total correction into a shot term and a receiver term, both of which are independent of offset and reflection time. The default is enabled. Disable this option only if you want to apply trim statics or structural factor corrections in isolation, without including the surface-consistent component. At least one of Apply surface consistent statics, Apply trim statics, or Apply structural factor statics must be enabled.
When enabled, applies the surface-consistent phase correction in addition to the time-shift correction. Phase corrections address sub-sample time shifts that cannot be represented as integer sample delays, improving statics accuracy at high frequencies. The default is enabled. This option is relevant only when Apply surface consistent statics is also enabled. Disable it if the statics solution does not include a phase component or if you observe phase distortions in the output.
Controls whether the trim statics component is included in the applied shift. Trim statics are short-wavelength, trace-by-trace residual corrections computed to maximize trace-to-trace correlation within each gather after the main statics have been applied. The default is enabled. Disable this option if you want to apply only the surface-consistent or structural factor corrections without the additional trim component.
Controls whether the structural factor component of the statics correction is applied. The structural factor correction accounts for the effect of dipping reflectors on the computed statics, helping to separate true near-surface statics from apparent shifts caused by geological structure. The default is disabled. Enable this option when working in areas with significant structural dip and when the statics solution includes a structural factor term.
Selects the direction in which the static corrections are applied. Forward applies the corrections as computed — shifting traces to remove near-surface time delays. Reverse applies the inverse of the computed corrections, which is used to undo previously applied statics (for example, when you need to remove a first-pass statics solution before applying an updated one). The default is Forward.
When enabled, the module automatically connects to compatible upstream and downstream modules in the processing flow, reducing the need for manual wiring of data items.
Specifies how the module handles traces containing bad or NaN amplitude values. Fix replaces bad values with zeros before processing. Notify logs a warning and halts. Continue silently skips the affected traces and proceeds with the remaining data.
Selects the compute device for processing. CPU uses standard multi-threaded processing. GPU offloads computation to a compatible graphics card for accelerated throughput on large datasets.
Options for distributing the processing workload across multiple computation nodes in a cluster environment. Configure the node list and communication settings here when running large-scale jobs.
Sets the minimum number of gathers processed in each work chunk when using distributed or multi-threaded execution. Larger values reduce scheduling overhead but increase memory usage per thread. Adjust this parameter to balance throughput and memory consumption for your dataset size.
When using distributed execution, this option limits the number of parallel threads used on each remote compute node, preventing the module from monopolizing node resources that may be shared with other jobs.
An optional text label appended to the distributed job name. Use this to distinguish concurrent jobs from one another when monitoring distributed execution on a cluster.
When enabled, allows you to manually specify which CPU cores the module may use, overriding the default system-assigned affinity. Enable this when you need to pin processing to specific cores for performance or isolation reasons.
Specifies the CPU core mask or list to use when custom affinity is enabled. This setting is active only when Set custom affinity is turned on.
Sets the number of parallel CPU threads used during processing. Increasing this value speeds up processing on multi-core systems. The optimal value is typically equal to the number of available physical cores on the machine.
When enabled, this module is bypassed and input data is passed through unchanged. Use this setting to temporarily disable statics application for QC purposes without removing the module from the processing flow.
The main seismic data item passed to the next module in the processing sequence, containing the static-corrected traces.
An optional SEG-Y file handle carrying the static-corrected data for writing to a SEG-Y output file.
The updated trace headers associated with the output gather. When Update trace headers is enabled, these headers contain the applied static shift values for each trace.
The gather with static corrections applied. Each trace has been time-shifted according to the combined static correction computed from all connected statics inputs. This output is the primary result of the module and is typically connected to the next processing step (for example, velocity analysis, NMO correction, or stacking).
The output stack line with statics corrections applied, passed to downstream modules in workflows that operate on stacked data.
The output crooked line geometry descriptor, passed through unchanged to downstream modules.
The output 3D bin grid geometry, passed through unchanged to downstream modules for use in geometry-aware processing steps.
The sorted header index passed to downstream modules, preserving the gather sort order established upstream.
The combined statics correction dataset produced by this module. When the Combine all statics into one custom action is executed, all connected input statics (including azimuthal corrections) are merged into a single correction stored in this output item. This can be used for QC visualization, archiving the total applied correction, or passing it to subsequent modules.
Executes the combination of all connected statics correction inputs — including the primary statics item, all additional statics items, and all azimuthal statics items — into a single merged correction stored in the Output statics correction item. Run this action when you want to produce a single unified statics dataset for QC, export, or use by a downstream module that expects a single correction item. This action does not re-apply the statics to the seismic data; it only merges the correction datasets.