3d streamlines The 3d streamlines module is used to produce streamlines or stream-ribbons of a field which is a 2 or 3 element vector data component on any type of mesh. Streamlines, which are simply 3D polylines, represent the pathways particles would travel based on the gradient of the vector field. At least one of the nodal data components input to streamlines must be a vector. The direction of travel of streamlines can be specified to be forwards (toward high vector magnitudes) or backwards (toward low vector magnitudes) with respect to the vector field. Streamlines are produced by integrating a velocity field using the Runge-Kutte method of specified order with adaptive time steps.
surface streamlines The surface streamlines module is used to produce streamlines on any surface based on its slopes. Streamlines are 3D polylines representing the paths particles would travel based on the slopes of the input surface. The direction of travel of streamlines can be specified to be downhill or uphill for the slope case. A physics simulation option is also available which employs a full physics simulation including friction and gravity terms to compute streamlines on the surface.
The create drill path module allows you to interactively create a complex drill path with multiple segments.
modpath The modpath module uses the cell by cell flow values generated from a MODFLOW project along with head values and other MODFLOW parameters to trace the path of a particle of water as it moves through the ground. The paths are calculated using the same algorithms used by U.S. Geological Survey MODPATH and the results should be similar.
scalars to vector The scalars to vector module is used to create an n-length vector by combining n selected scalar data components. The vector length is determined by the Vector Type selector (2D or 3D). Once the required number of components has been selected, any other data components are grayed out and not selectable. To change selections, first deselect one of the vector components and then select a new component. If no components are selected, then all components are selectable. The order in which the components are selected will determine in which order they occur in the vector.
The vector to scalars module converts all vector nodal data components into individual scalars. For example, a vector data component named 'velocity'
vector magnitude The vector magnitude module calculates the vector magnitude of a vector field data component at every node in a mesh. Input to vector magnitude must contain a mesh of any type and nodal data. Nodal data components can be scalar or vector with up to 3 vector subcomponents. Module Input Ports Input Field [Field] Accepts a vector data field Module Output Ports
gradient The gradient module calculates the vector gradient field of a scalar data component at every node in a mesh. Input to gradient must contain a mesh of any type and nodal data, with at least one scalar nodal data component. Gradient uses a finite-difference method based on central differencing to calculate the gradient on structured (rectilinear) meshes. Shape functions and their derivatives are used to calculate the gradient on unstructured meshes.
capture_zone The capture_zone module utilizes 3d streamlines technology to determine the volumetric regions of your model for which groundwater flow will be captured by one or more extraction wells. Module Input Ports Z Scale [Number] Accepts Z Scale (vertical exaggeration). Input Field [Field] Accepts a field with vector data. Well Nodes [Field] Accepts a field of points representing the well locations Module Output Ports
seepage_velocity The seepage_velocity module is used to compute the vector groundwater flow field visualizations of the vector field. The input data requirements for the seepage_velocity module are: A data component representing head (can have any name). A Geo_Layer data component. A Material_ID data component. If there is no Material_ID, we treat each layer as a separate material. Layer 0 becomes material -1 Layer 1 becomes material -2 Layer 2 becomes material -3, etc. Note: If you use 3d estimation to krige head data with geologic input (in Version 6.0 or later) your output will meet these criteria (provided you toggle on these data components under Kriging Parameters).
regional_averages The regional_average module averages nodal data values from the input field that fall into the input polygon regions. It then outputs a point for each region that contains the average x, y coordinates and the average of each selected nodal data component. These polygons must contain at least 1 cell data component representing the regional ID.