| Section | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Steps in depth conversion
| Section | ||
|---|---|---|
| Column | ||
| ||
| Note | ||
| ||
|
The folders used to save data in this project are of type Generic and renamed to indicated their contents. The various datasets will also be set to their proper schema type so that only relevant command objects are shown.
The documentation follows a specific dataset and is thus close to a case study. This implies that other dataset may apply slightly different display options due to size and attribute saving in scalar or field data. The general principles for depth conversion should however be the same in all cases when using the method of a velocity cube.
...
| width | 40% |
|---|
Example of velocity cube holding stacking velocity data
Reading stacking velocities
...
| width | 60% |
|---|
Geocap provides import command objects (CO) for reading stacking velocities organized in ASCII column data.
If the file is large, keep the input as low as possible. To generate a velocity cube only x y time velocity are needed.
Example input: stacking velocities in ASCII columns, size ~ 400MB.
| Info | ||
|---|---|---|
| ||
Column | | width | 40%
Geocap project for stacking velocity data and velocity cubes
The actual project was generated the standard way by opening a new project and gradually populate it with folders when needed. The stacking velocities was imported into a generic folder given the name All points in line cells, just to indicate that the stacking velocities are organized as vertical lines, called line cells in Geocap syntax. The schema setting of the dataset is Stacking Velocities.
...
The command menu Cube gridding from stacking velocities can be activated for data with schema Stacking Velocities. Stacking velocities have the format: x y two_way_time velocity. Two_way_time is used because time is recorded after having traveled down to the reflector and up again.
| Info | ||
|---|---|---|
| ||
Initially, set the correct attribute to tell whether stacking velocities are in scalar or field data velocities or have some other name. Press Set when the correct attribute selection is done. |
The cube gridding command menu allows the user to set a proper origin, set the cube increments, use Adjust (gridding window) to Increments to align the cube at increment values. Be sure to set the gridding window correct before gridding. Pressing Window Frame will display the coordinates written in the grid window as a frame. Also check the zmin zmax values to see that the vertical extent is correct.
| Tip | ||
|---|---|---|
| ||
An option that might be useful is to expand the cube gridding window a few grid cells to ensure that the cube is gridded outside the min and max area of the time grids in case the cube gridding window is first taken from the xy window of the time grids. Press Expand to increase the cube gridding window. |
When the increments of the cube are correct hit Calculate to get the number of rows, columns and layers in the cube.
...
Testing cube gridding using a manipilator manipulator plane
After testing the gridding at a few planes and securing all parameters are properly set, the overall gridding of the stacking velocities into a velocity cube can take place. The resulting cube can then be visualized with various display techniques.
...
Checking the cube visually
...
The velocity cube is displayed by dedicated commands available through the Cube schema.
Upper left viewport shows surface contours for the cube using the commands Cube contours.
Upper right shows planes in the cube colored and contoured with velocity using Cube views->Map X Y Z planes at cursor position. That command requires a cursor position inside the cube frame which can be set hitting the keyboard letter p or y while pointing at the screen.
...
...
Displaying velocity cube with three planes and transparent surface boundary
...
| width | 50% |
|---|
Bottom left is a cube overview contoured as a boundary surface using Cube contours.
Bottom right is cube layer at level 4400 displayed as terrain using Display selected cube layers. This menu allows for displaying single cube layers or arranges multiple layers in viewports if this option is checked in on the Viewport display setup page.
Displaying individual layers in a cube is important for checking the cube contents and also for presentation purposes.
...
...
| width | 50% |
|---|
Various ways to display cube information
Depth conversion using a dedicated command object
...
| Info | ||
|---|---|---|
| ||
|
The central command in depth conversion is the pro command which does the probing of the time grid into the velocity cube. The time grid must be converted to polydata in order have a scalar part: x y time scalar. After probing this dataset into the velocity cube, the scalars are assigned values from the cube at their positions and the whole dataset is now transferred into x y time velocity.
...
A time-velocity cube can be smoothed and recalculated to other forms like an RMS (Root Mean Square) or an Interval Velocity cube or even a depth-velocity cube. Read more about theese these options in Creating RMS cube, Interval cube and Depth-Velocity cube