Introducing Visual MODFLOW Flex 6.0

/Introducing Visual MODFLOW Flex 6.0
Introducing Visual MODFLOW Flex 6.02019-03-07T13:42:36-05:00

Experience the power of Visual MODFLOW Flex 6.0

Visual MODFLOW Flex brings together industry-standard codes for groundwater flow and contaminant transport, essential analysis and calibration tools, and stunning 3D visualization capabilities in a single, easy-to-use environment.

Enhancements include:
1. Build your unstructured MODFLOW-USG model using the same workflow steps as in a structured Finite Difference model:

  • Define Modeling Objectives
  • Specify model properties (such as Conductivities, Initial Heads, etc.) using the same tools as in Finite Difference models
  • Add Boundary Conditions
  • Define ZoneBudget Zones
  • Add Particles

2. Define Quadtree Grids (Q-Grids)

3. Refine vertical layers when creating unstructured grids

4. Make use of advanced translation settings providing greater flexibility in how your model simulations are formulated

5. Support for the MODFLOW-USG Ghost Node Correction (GNC) package

6. Flex is now packaged with MODFLOW-USG v1.4, the latest official USGS version as of the release date of Flex 6.0

Enhancements include:
1. Support for mod-PATH3DUv3.0*, which enables particle tracking in unstructured grid (MODFLOW-USG) models

2. Enhanced particle tracking capabilities allowing you to define:

  • Groups of particles that can be tracked and visualized separately
  • Separate particle release times for each particle group
  • Locations of particles based on existing or drawn point, polyline, polygon, or well features
  • Particles in cross-section views (i.e. row and column views) of a finite difference model
  • Particle elevations based on layer(s), surface(s), or a constant elevation

*mod-PATH3DU is a free utility developed by SSPA that must be downloaded and installed separately from the SSPA website.

Enhancements include:
1. ZoneBudget is now supported in unstructured MODFLOW-USG models

2. You can use point, polyline, or polygon features to define Zone Budget zones and zones can be specified directly using feature attributes from a data field

Enhancements include:
1. Visualize velocity vectors in finite difference and unstructured grids. View:

  • In-plane velocity vectors
  • Color maps of out-of-plane velocities
  • Display average or Darcy velocities (total or in-plane) or by direction

2. Specify a line feature along which to show cross-sectional color maps of unstructured grid model properties and outputs
3. Cell Inspector now includes Layer/Model Top and Bottom elevations, and the magnitude and X-, Y-, and Z-components of the average/Darcy groundwater velocity
4. When creating horizons, you can preview how the rules will be enforced in the 3D Viewer rather than viewing the raw surfaces

Enhancements include:
1. Field calculator/expression builder includes

  • cell geometry variables: Cell Bottom ($BOT), Model Bottom ($MBOT), Cell Thickness ($DZ), Cell Width ($DX), and Cell Length($DY) and additional functions: LOG, LOG10, NOT, ABS, DOT

2. Copy Model (Flow/Transport) Properties and Boundary Conditions to form one Layer, Row, or Column to other Layers/Rows/Columns

3. Edit cells (active/inactive, zone budget) in row/column views.

Enhancements include:
1. Import distributed property values from Classic Models
2. Use a source data field to map feature elevations when importing point, polyline, and polygon data
3. Model outputs including groundwater heads, drawdown, velocity, and concentrations can be exported to text files
4. Export contours as polyline shapefiles

Enhancements include:
1. Observation Wells can be specified as separate groups
2. Performance improvements on project open and close operations for larger projects
3. Output Control file translation supports keywords or codes and the standard or compact budget formats to provide support of             MODPATH and mod-PATH3Du.
4. Added MT3D-MS and RT3D summary output (.OT) files to the open files dialog at the model run step

  • Intermittent unhelpful translation error “Vmac is running in the task bar, please close it and try again”.
  • Deleting particles by drawing a box does not actually delete particles
  • Well schedule not translated correctly if the project time unit is not in days
  • In some cases, particularly if the whole output water table exceeds the model ground surface it was rendered at Elevation=1
  • Modifications to a pumping well boundary condition propagate to all runs under the same grid
  • Concentration observations contained incorrect column names
  • Project Clean-up/Remove orphan objects from model
  • If all boundary conditions of a given type were deleted, they would still run in the model due to advanced run settings. You are now prompted to remove the translated file or back-it up so that it no longer runs in the model
  • In some cases, the schedule for pumping wells with relative times does not import correctly
  • In some cases, assigning a schedule to a conceptual boundary condition results in an error message that the schedule occurs before the model start date even if this is not true
  • Concentration observations incorrectly handled for simulations with multiple species
  • Transient Fluxes (Model Results) are not shown or exported, only Flux from first time step.
  • Fluxes not displaying properly in 3D Viewer
  • Cells remain active if boundary condition is applied to ‘Top’ of model domain
  • MODFLOW-USG, BCF package fails to translate if property values are edited
  • When using a uniform grid, the CM->NM conversion does not add conceptual BCs assigned to model top to Layer 1 rather than the upper-most active layer
  • When importing heads file as 3D gridded data to a Rotated Grid Project, error “Object reference not set to instance of object appears”
  • Inconsistent/compound units are not correctly converted for certain RT3D reaction parameters
  • Water table for USG does not take ponding into account
  • Reinstalling Visual MODFLOW Flex does not replace MODFLOW-SURFACT with the demo version in the engines folder
  • Flex does not always cleanly delete elements from the Model Explorer, resulting in large file sizes
  • In some cases, MODFLOW-USG conceptual model conversion results in incorrect parameter values, and causes parameter editing to fail
  • Out of memory error when attempting to display certain DXF files in 2D view of Flex viewer or standalone 2D viewer
  • Multiple Lake BCs result in a multiple key error upon translation

For a full version history, click here to review the Visual MODFLOW Flex Readme documentation.