You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We believe that this override does not require modification. Unit tests pass.
NonBinned
Input Parameters
List of non-binned dimensions
Chunk size of new dimension
Behavior
From the template, we will:
Drop all dimensions contained in the list of non-binned dimensions
Add a new dimension trace to the N-1 position
The size of this dimension will be the product of all unique elements in the list of non-binned dimensions
Add one new coordinate per element in the list of non-binned dimensions
These coordinates will have the dimensions up to trace
Example
Template with [shot_point, cable, channel, azimuth, offset, sample] and non-binned [azimuth, offset].
The new template will have dimensions [shot_point, cable, channel, trace, sample] and new coordinates azimuth and offset with dimensions [shot_point, cable, channel, trace]
The chunk size of sample will be equal to the input parameter.
DuplicateIndex
Input Parameters
Just a flag (TBD).
Behavior
We will add a new dimension called trace to the provided template at the N-1 position. This dimension must have a chunk size of 1. Coordinates will not be modified.
ChannelWrap
We believe this can be safely removed as it is superseded by AutoChannelWrap.
Looks good. The discussed priorities are:
P1 - AutoChannelWrap
P2 - NonBinned
P3 - DuplicateIndex
P98 - ChannelWrap, CalculateCable (no need to hurry with removal)
P99 - AutoShotwrap - not a standard operation and will require a custom template
coordinate that is dependent on some those dimensions. e.g., "source_coord_x" -> ["shot_point", "cable", "channel"]
what should happen to the coordinate (e.g., "source_coord_x") if declare the dimension "channel" NonBinned and remove the "channel" coordinate?
Is there a reason we are no longer indexing on shot_line and are not using AutoShotWrap. We exclusively use this when ingesting pre-stack data for ML training.
Activity
dmitriyrepin commentedon Aug 22, 2025
Looks good. The discussed priorities are:
P1 - AutoChannelWrap
P2 - NonBinned
P3 - DuplicateIndex
P98 - ChannelWrap, CalculateCable (no need to hurry with removal)
P99 - AutoShotwrap - not a standard operation and will require a custom template
dmitriyrepin commentedon Aug 31, 2025
@tasansal , @BrianMichell
For 'NonBinned':
If the original template had the following
what should happen to the coordinate (e.g., "source_coord_x") if declare the dimension "channel" NonBinned and remove the "channel" coordinate?
markspec commentedon Sep 3, 2025
Is there a reason we are no longer indexing on shot_line and are not using AutoShotWrap. We exclusively use this when ingesting pre-stack data for ML training.
markspec commentedon Sep 3, 2025
Also gun!
tasansal commentedon Sep 5, 2025
AutoChannelWrapis merged via v1 implementation of AutoChannelWrap grid override #632NonBinnedandDuplicateIndexwere attempted via Grid overrides: NonBinned & HasDuplicates - over UPDATED v1 #633 however the implementation is wrong, needs to be redone.CalculateCableandChannelWrapwill be removed per reason @BrianMichell definedAutoShotwrapwill be done but post 1.0.0 stable release, we need to get all of the above resolved.