Staff at Equipoise Towers are working hard to bring you the latest Velit/VelPAK 2.6 update later this year. So, what’s new and what’s improved? Here is a sneaky peak at some of the new and improved features!
Gridding using Natural Neighbours 3 < 2500 points hangs – Fixed
A bug that crept into the “Natural Neighbors 3” gridding routine caused the routine to hang indefinitely. The Natural Neighbor interpolation algorithm uses a weighted average of the neighboring observations, where the weights are proportional to the “borrowed area” and is used increasingly in the stochastic modelling for depth uncertainty.
Abort button did not work in some modules – Fixed
Doing a direct depth conversion in the wizard for the velocity modelling routines found that the abort button would not work. A third party cancel function has been implemented.
Petrel Depth Conversion and velocity modelling in Petrel is aided by using the link to Velit. The link has been redeveloped to produce a dedicated area for Velit projects.
Layer Definition is now selected in the link. But go into VelPAK/Velit and Model Layer list is now displayed in the Layer Definition for reference.
Hidden/Inactive points on the graph are now excluded when the AoI is recalculated.
3D Module is a useful QC for checking the grids have come across from Kingdom or Petrel correctly before depth conversion and velocity modelling. New enhancements make it easier to use with an instant display of the time grids being on show.
- When a curve is generated, a bug made it that an image of the curve displayed rather than the graph itself. This added to confusion when trying to select and de-select wells on the ‘dead’ image. The image now moves to the back tab and the ‘live’ graph is available for selection.
- In the Wizard there is now a button to say ‘For this event ignore the wizard set up and run the current depth model method set-up from within the main VelPAK/Velit depth conversion set-up’ this means that a complex depth conversion for one layer with methods unavailable in the wizard can be incorporated into an all-event wizard workflow.