Aquaveo & Water Resources Engineering News
- Fixed three bugs
- modflow.org complete
- UGrids added to Display Themes
- Double-click on UGrid cell opens Properties dialog
- TINs and Rasters added for SFR2 elevations
- PEST 13 support added
- Qt interface progress
- Posted GMS 10.0 beta
- 2D UGrid from 3D UGrid
- UGrid lighting now works
- UGrid mouse tracking now works
- Switched from "node" to "point" terminology with UGrids
- Designed MODFLOW SWI interface
- UGrid from imported .gsf file
- PEST-ASP now treated as a MODFLOW package
- Interpolate from scatter points to UGrid
- CLN interface started
- Fixed 32 bugs
- Tutorial: UGrid Creation
- Tutorial: MODFLOW-USG - Complex Stratigraphy
- Tutorial: MODFLOW-USG - Regional to Local
- Tutorial: Saving Native Text
- Warning about unsupported packages when converting to MODFLOW-USG
- Updated third party licence info
- Warning when attempting to create 3D Grid or UGrid with lots of cells
- Much work on modflow.org
- Qt interface progress
- Custom ASSERT for testing
- Posted a beta of GMS 10.0
- Wiki documentation on UGrids, Map to MODFLOW, MT3D starting conc.
- Draft MT3DMS page on Wikipedia
- Select by data set value feature
The model checker has been a feature of GMS from the beginning. The purpose of the model checker is to analyze the input data currently defined for a model simulation and report any obvious errors or potential problems. Running the Model Checker successfully does not guarantee that a solution will be correct. It simply serves as an initial check on the input data and can save a considerable amount of time that would otherwise be lost tracking down input errors.
In version 10 the model checker has been updated to make reading its results much easier (see the images below). If GMS does not find any obvious errors or warnings then a message highlighted in Green will appear at the top of the dialog letting you know that the input data is free from obvious errors. If your model contains warnings then a Yellow highlighted message will appear at the top of the dialog telling you that warnings were detected. Then as you scroll through the model checker output the warnings will be highlighted in Yellow. Finally, if your model has errors then a message highlighted in Red appears at the top of the dialog and as you scroll through the output the errors will be highlighted in Red. While these features may not be technological breakthroughs they make using the model checker even easier than previous version of GMS.
MODFLOW–USG (for UnStructured Grid), was developed to support a wide variety of structured and unstructured grid types, including nested grids and grids based on prismatic triangles, rectangles, hexagons, and other cell shapes. Flexibility in grid design can be used to focus resolution along rivers and around wells, for example, or to subdiscretize individual layers to better represent hydrostratigraphic units.
MODFLOW-USG’s subdiscretization capability to better represent hydrostratigraphic units is an extremely powerful feature. Traditional MODFLOW requires that grid layers be continuous throughout the model domain even if the particular stratigraphic unit ends or pinches out.
Complex unstructured grids can be created in GMS by using the horizons approach.
GMS uses a modified version of MODFLOW that can read data from HDF5 files. HDF5 is a binary, cross-platform file format for storing data. Large portions of the MODFLOW inputs are stored in an HDF5 file when creating a MODFLOW model in GMS. Large MODFLOW models are stored much more efficiently using HDF5 (compression ratios of 95% when compared to text files are common). Also, the read/write times are much faster with the binary HDF5 file when compared to text files.
Even though it has been shown that HDF5 with MODFLOW is extremely efficient, many users would also like to have their MODFLOW simulations in the native MODFLOW format. This is particularly true when completing a modeling project and the user needs to archive the project.
Native MODFLOW text files can be saved from GMS. Beginning with version 10.0, these text files also contain documentation comments that more clearly identify the contents of each line in the MODFLOW input file. Further, parameter definitions are also included in the text files.