GMS

Tips for MODFLOW 6 in GMS 10.5 Beta

By aquaveo on June 10, 2020

Have you had a chance to use MODFLOW 6 in the GMS 10.5 Beta? If you have, you may have noticed that MODFLOW 6 operates a little differently than other versions of MODFLOW. This is to allow for some additional tools and options.

When using MODFLOW 6 in GMS 10.5 Beta, here are a couple tricks to try out.

Having Multiple MODFLOW 6 Simulations in the Same Project

You can create multiple simulations in the same project by using the simulation workflow in GMS 10.5 beta. This is particularly useful when attempting to calibrate your project. The way this is done is by doing the following:

  1. Right-click on the simulation in the Project Explorer and select the Duplicate command. This will create a duplicate of the simulation that includes all the same parameters and uses the same grid.
  2. On the new simulation, change the parameter that needs to be calibrated, such as the head values or the pump values of the wells. It is generally best to only focus on one parameter change when calibrating the model.
  3. Run the new simulation and compare the results between the different simulations.
  4. Repeat this process with additional simulations to calibrate the model.
Duplicate command in the simulation menu
Running Multiple Simulations at the Same Time

After you have created multiple MODFLOW 6 simulations, you can run all of the simulations at once. This is done by doing the following:

  1. Right-click on the simulation folder and select the Save All and Run command.

The Simulation Run Queue dialog will display all of the simulation model runs. While the simulations are running, the Simulation Run Queue can be moved aside or minimized to allow you to keep using GMS. The results can be loaded into the project for you to review when the simulations have finished.

Sae All and Run command in the simulation folder menu

Additional features for MODFLOW 6 are still being added to GMS and will appear in future versions of the software. For now, check out MODFLOW 6 in GMS 10.5 beta today!

Blog tags: 
GMS

Tips for Using MODPATH in GMS

By aquaveo on May 20, 2020

MODPATH is designed to work with MOFLOW to show particle tracking information. Using MODPATH can provide valuable information to your groundwater model. With that in mind, here are a couple tips for using MODPATH.

Seeing the Breakdown of Position vs Time

After running MODPATH, you can use GMS to see the breakdown of position vs time.

  • Duplicate your particle set and change the duration for each to correspond to the end of a different time step. This will help visualize when the particles traveled along their pathlines.
  • View the Pathline Report by right-clicking on a particle set in the Project Explorer and selecting the View Pathline Report command.
MODPATH Pathline Report
MODPATH Crashing During a Transient MODFLOW-NWT/UPW Simulation

While MODPATH is quite stable, it can crash when used with some MODFLOW-NWT models. To avoid this, look at the following:

  • When the water level is below the bottom of the cell in MODFLOW-NWT, making the cell dry but not inactive, MODPATH calculations give bad values. Check the cell thickness to see if it is above the water level. Then, inactivate cells above the water level.
  • The alternative workflow, which is not appropriate for every model, would be to change your MODFLOW-NWT model so that either the cells do not go dry, or are set to be inactive from the beginning, which is what this user on this forum post chose to do.
Importing Old Versions of Particle Coordinate Files

GMS has the capability to read in older particle coordinate files. Old versions of the endpoint, pathline, and time series files are automatically detected and read by MODPATH-PLOT. When old particle coordinate files are read, all time step values are automatically set equal to 1 and the particle release time is set equal to 0. The discharge code (IDCODE) for all particles is set to 1 (normally terminated).

Using these tips can increase your MODPATH expertise. Try out MODPATH using GMS today!

Blog tags: 
GMS

Sharing GMS Project Files

By aquaveo on April 29, 2020

As many of us work in a collaborative environment, sharing projects becomes essential. When sharing a GMS project, it is not as simple as sending over just the GMS project group file (*.gpr) project file. GMS projects are stored in multiple separate files that work together. When sharing a GMS project, it is important to include all of the necessary files.

GMS projects are saved as a project group file (*.gpr). This file saves feature objects, projection data, data objects and other general settings. However, it only references many other aspects of a project that are contained in separate files. It will reference the location of all external files such as shapefiles (*.shp, *.dbf, *.prj, etc.), images, CAD files, grid files, etc. When sharing a GPR file, the file needs to be able to locate these external files. Ideally, these files should be located in the same folder as the GPR file. This is why it is recommended to zip all the project files together before you send it out to be shared.

GMS project files

When your project contains a MODFLOW model, it is important to know that GMS saves the MODFLOW project in separate files. For example, each package saved as a different file. Rivers (*.riv), drains (*.drn), wells (*.wel), streams (*.str), recharge (.rch), etc. are all different packages with different file extensions. Sending over just the package file, such as only sending a wells file, is not much use as GMS will likely be unable to open it.

Along with the MODFLOW package files, GMS will need the MODFLOW name file (*.mfn). This file allows GMS to build the MODFLOW project when it is imported. All other input and output MODFLOW files should be included when sharing your GMS project.

Note that many files will be saved in a folder created next to the GPR file. Files in the folder should be left there and the entire folder should be moved with the GPR file. GMS saves the relative location of files included in the project.

When sharing your GMS project, keeping all of the necessary files together can save the person receiving the project a lot of frustration. For more about GMS file formats, be sure to check out the GMS articles on the XMSWiki and start sharing your GMS projects today!

Blog tags: 
GMS

Tips for Exporting a MODPATH Project

By aquaveo on April 8, 2020

MODPATH works with MODFLOW to show particle tracking information. Once you have successfully completed a MODFLOW project, you may want to share that information collected through MODPATH with your other colleagues. Exporting the MODPATH data can allow you to share specific information with them.

Typically, the Save As command in the File menu and the right-click Export command in the Project Explorer are used to export MODPATH data from GMS. When using these commands, there are some tips for getting the most out of them.

Exportin MODFLOW
Exporting MODPATH Flowlines to a KMZ File

The flowlines from a successful MODPATH run can be exported as a KMZ file using the Save As command. When doing this, pay attention to the following:

  • Use the Display Options to make the flowline more visible before exporting to a KMZ file.
  • Make certain that the projection/coordinate system of your MODPATH project has been set correctly. KMZ files require that a coordinate system be set therefore GMS cannot create a file if there is no projection.
  • Objects in the Project Explorer can be set to different projections. Be certain to review the projections of all objects when exporting a KMZ file.
Exporting Points

Using the Save As command, the particle points of the MODPATH project can be exported to a shapefile.

  • When exporting particle points from MODPATH it is important to note that endpoints will need to be exported with intermediate points.
  • Another option is to use the Text Tab Delimited Pathline File option, which prints out the location and could be quickly parsed to pull the X and Y locations for the last time step of each particle.
  • MODPATH output can be exported to a shapefile or text delimited file by right-clicking on your MODPATH particle set in the Project Explorer and selecting "Export".
  • In the "Export Particle Sets" dialog that comes up, you can then change the "Save as type" option at the bottom to the type (pathlines, points, vectors), and format (shapefile, text delimited file) you prefer.

Many of these tips apply to exporting other numeric modeling data in GMS. Try out the different export functionalities in GMS today!

Blog tags: 
GMS

Pages