Velocity analysis software
A highly interactive velocity workflow for 2D and 3D: tunable semblance, super-gathers and constant-velocity mini-stacks, vertical picking down the trace and horizontal picking along a horizon, and the model tools that turn a set of picks into a field NMO, migration and depth conversion can use.
Every view you need to trust a pick.
A semblance panel on its own hides as much as it shows. The picking session pairs it with the gather, the mini-stacks, the offset panels and the section being built, so a decision can be checked against the data it came from.
A field of picks is not yet a model.
Picks have to be converted, cleaned and stored before the rest of the chain can use them. These are the modules that do it — and the ones that make the next picking session faster than the last.
Turns gathers, a SEG-Y handle, an internal picks collection, an ASCII picking file, a constant velocity or a third-party format — Geocluster, CGG 3D, ProMAX table — into the internal velocity model that NMO, Kirchhoff PreSTM and the depth chain consume.
Manual correction of a 2D or 3D model in time or depth: smoothing, spike removal, removal of unrealistic inversions, interpolation across edited areas, replacement with a constant inside a region, and polygon-based surgical editing on vertical sections and 3D volumes.
Computes the velocity analysis for the whole volume once and stores it on disk, so picking on a large survey reads from storage instead of recalculating semblance each time.
Removes the offset-dependent travel-time delay so a gather can be stacked, with a form of the equation that accounts for source, receiver and bin elevations against the replacement velocity.
When flat gathers need more than one velocity.
NMO assumes hyperbolic moveout, which holds for horizontally layered ground and moderate offsets. Long offsets, fractures and anisotropic sequences break that assumption, and residual curvature survives even a perfect isotropic pick. Three routes address it.
Six steps to a velocity field you can hand on.
Velocity is the input everything else depends on.
The same project, the same batch processing and the same cluster carry a survey from field tape through to depth. These are the other topics in the g-Platform workflow.
Questions, answered.
Where does velocity analysis happen in g-Platform?
Is picking manual or automatic?
What is horizontal velocity analysis?
How do picks become a velocity model?

Pick a velocity field on your own gathers.
From a first manual pass through corridor-guided auto-picking to an edited model ready for migration — take g-Platform for a trial run, or talk to Geomage about your survey.





