GMS

Avoiding Grid Over Refinement in GMS

When building a grid for your groundwater model, it can certainly be tempting to make a really refined grid. While this temptation is understandable, there are certain pitfalls that can result from having a grid that is overly refined. This post will go over some of the reasons to avoid overrefining your grid in GMS.

There are, of course, legitimate reasons to refine portions of your grid. Portions of the grid that are key areas should be refined. This should be done only in areas around wells or other structures that are important to the model. By refining key areas, important areas of the grid will receive more attention during the model run. However, over refining your grid can cause some issues, including some of the following ones listed here.

Example of Grid Refinement

When you are refining, you are creating more grid cells in your grid. Each of these cells will be used in the model run calculation. A grid that has been over refined generally has a lot of cells that need to be used in the model calculations, many of which are unnecessary. This will cause the model run to go slower and take longer than the same model without the over refinement.

Because an over refined grid contains refined cells in unimportant areas of the project, the data from these areas can sometimes skew the results. The model run does not generally discriminate between important and unimportant parts of the grid. When it encounters a portion of the grid that has a lot of cells, it gathers all the data it can for that area. In an over refined grid, this can mean it gathers more data than the model needs, which sometimes can skew the results.

The biggest issue we most often see is when over refined grids cause the model to fail to converge. Once again, an over refined grid will have too many cells and be collecting too much nonessential data. All of this can overwhelm the model and can cause the model run to diverge. To resolve this, you will need to simplify the grid so that the model run stays focused on the key areas of the model.

Try out some of these tips while refining grids in GMS 10.5 today!

Blog tags: 

Using the Axes Display in GMS

Have you tried using plotted axes to help orient the display of your models in the Graphics Window for your groundwater modeling projects in GMS? Within the Display Options in GMS, there is a set of options that will allow users to activate this and modify how it will display. This post will review how to utilize the Plot Axes functionality found in the Display Options dialog within GMS.

To locate the Axes options in GMS, open up the Display Options dialog by doing the following:

  1. Click the Display Options macro or go to the Display | Display Options... command.
  2. Select the Axes option on the left.
  3. Turn on the checkbox labeled "Enable axes" to activate the plot axes.

By default, the axes are turned off, and all the other options below it grayed out as a result. This is why axes are not usually visible on their own in the Graphics Window. Turning this option on will generate axes within the Graphics Window. The axes will naturally be sized to contain the entirety of the model within it. If the Graphics Window is currently set to Plan, Front, or Side View, rotation might be required for all of the axes to be visible.

Example of the Axes Display Options

The Axes display options allow you to control the different aspects of the axes display, such as:

  • Fly modes to set where in space the axes will be placed.
  • Tick location options to set which direction tick lines along the axes will be drawn pointing to, either inward or outward.
  • Grid line location options to set which surfaces grid lines are actually drawn on, which can help in visualizing the grid.
  • A spreadsheet containing options for editing each individual axis, as well as a row for editing all of them at once.

Try out experimenting with Axes display options in GMS 10.5 today!

Blog tags: 

Performing a Silent Install for ALS

Are you an IT administrator needing to perform a silent install of GMS, SMS, or WMS in a classroom or office? We have gone over the process to do this in the past. However, our licensing methods have changed since those instructions were first written. Because of this, we have felt it would be useful to update our users on the new method of configuration so they will be able to properly set up their silent installs. This post will review registration for the new licensing method and how to perform silent installs with it.

This silent install (or quiet install) workaround requires each user to have the rights to modify the registry. If registry access is restricted, a network administrator can do this by opening the Group Policy Management Editor and creating a startup script that automatically runs the batch file whenever the computer is restarted.

Note: Editing the Registry in Windows is a very advanced administration step. Please always create a backup of the Registry before making changes.

It can be a burden to manually update the local code in HKEY_CURRENT_USER for each user on each computer. The silent install process is simplified by creating a Windows Registry file that contains the license information and a batch file that can be executed to insert the registry information and launch WMS. The batch file automatically updates the registry for the user and then opens the WMS application. This is the safest way to edit the registry key, as well. The batch file can then be placed on each computer that needs to be updated, and the individual users can execute it as needed.

This workaround uses WMS as an example. This information also applies to GMS and SMS. You can see an example of a registry file in step 1 and the batch file in step 2, below.

  1. Create a file, "Netenble.001.reg", as follows:
    Windows Registry Editor Version 5.00M
    "ALS"="1"
    "ALSHost"="127.0.0.1"
    "ALSPort"="56789"

    ALS = 1 specifies the new registration wizard, with new "Local" codes beginning with L, F, or E, instead of 0 for the old network lock. ALSHost = 127.0.0.1 because the code is being located on the local machine. And ALSPort = 56789 should be the default - you can alternatively specify your own port if you would like. You could also specify an ALSCode (license code) as well if you don’t want registration to be required when first launching WMS.
    Note: This information was created using Windows 10. Because different Windows versions can have different REG file formats, we recommend you install WMS on one machine, register it to the correct local code, then export the registry key. Open the registry file in the text editor and remove every line except those similar to those shown in the image above, and save the file as "Netenble.001.reg".
  2. Create a file, "wms11.bat", that will update the registry and start WMS:
    reg import Netenble.001.reg
    wms.exe
  3. Place these two files in the WMS folder in the image that will be distributed to the affected computers. For example, for the 64-bit version of WMS 11.1, the default location for the folder is “C:\Program Files\WMS 11.1 64-bit\”.
  4. Create a desktop shortcut to the batch file for the convenience of the user. If doing this via a startup script in the Group Policy Management Editor, this step can be skipped.

This silent install workaround can save you significant time as a network administrator. If you experience issues while performing a silent install, feel free to contact Aquaveo for assistance.

Incorporating Transport Observation Points into a MT3DMS Model

Have you wanted to incorporate the TOB package while running MT3DMS in GMS? We have a workflow that can help with this, as part of building an MT3DMS model in GMS with a conceptual model approach. This post will review how to incorporate transport observation points into your MT3DMS model in GMS.

To do so, use the following steps:

Transport Observatin Package
  1. With your MT3DMS model already open in GMS, right-click the conceptual model and select New Coverage... to create a new coverage and bring up the Coverage Setup dialog.
  2. While in the Coverage Setup dialog, turn on whichever options you want to be observing for in the Obs. Data column of the Observation Points section.
  3. Once done with the Coverage Setup dialog and with a new coverage created, create some points within the coverage.
  4. Using the Select Points\Nodes tool, select the points you have just created, right-click on one of them, and select Attribute Table… to bring up the Attribute Table dialog.
  5. Set the Type drop-down in the All row to obs. pt in the Attribute Table dialog to set the BC type to Observation Points for the points.
  6. Once done with the Attribute Table dialog and with the points set as observation points, right-click the new coverage and select Map To | MODFLOW/MODPATH to map the new coverage to MODFLOW.
  7. Now select MT3DMS | Basic Transport Package… to bring up the Basic Transport Package dialog.
  8. Select the Packages... button to bring up the MT3DMS/RT3D Packages dialog.
  9. Turn on the option for Transport observation package.
  10. Now select MT3DMS | Transport Observation Package... to bring up the Transport Observation Package dialog.
  11. Now you will have the ability to turn on the option to Compute concentrations at observation points and select coverages with concentration observations to be used.

Try out incorporating transport observation points into MT3DMS models in GMS 10.5 today!

Blog tags: 

Pages