GMS

Converting a 3D Dataset to a 2D Dataset

By aquaveo on August 21, 2019

It sometimes happen where you have a fully developed 3D model in GMS and need to transfer a dataset from the 3D model to a 2D model. GMS provides a way to convert a dataset on a 3D grid to a 2D grid. From there the dataset can be exported as 2D data for use in a 2D model.

To acquire a 2D dataset from a 3D dataset, you need the following:

3D grid
2D grid
3D dataset

To convert a 3D dataset to a 2D dataset, do the following:

In the Project Explorer, select a dataset under a 3D Grid.
Use the Grid menu to select the 3D Data → 2D Data command.
Select option in the 3D Dataset → 2D Dataset dialog.

The 3D Dataset → 2D Dataset dialog allows choosing which dataset to converted. By default, the dialog will use whichever 3D dataset is active in the Project Explorer. If another dataset is desired, from a MODFLOW simulation for example, you can make the change in the dialog..

The dialog also allows creating the new 2D dataset using one of the following parameters:

Maximum value in ij column
Minimum value in ij column
Average value in ij column
Sum of values in ij column
Highest active value in ij column
Value from k layer

K represents the layer number with 1 being the surface layer, and J and I representing the x and y locations of a cell (or column of cells) in the grid.

Keep in mind that one of the grids could be covering the other so if you want to observe specific data, you may need to turn off other data.

Additional additional information about converting 3D grids to other data can be found on our wiki.

Try out converting 3D datasets to 2D datasets in GMS today!

Blog tags:

GMS

Common Installation Issues with XMS

By aquaveo on August 14, 2019

Are you having trouble installing GMS, SMS, or WMS? Here are three common installation issues, and how to overcome them.

Virtual Machines

The main issues when using virtual machines is selecting the correct type of installation. Single-user locks are not compatible with virtual environments. If you are trying to install XMS with a single-user lock and a virtual machine is detected, XMS will not install. You will need a network lock to get around this issue. Network locks are designed to be used with virtual machines. Single-user locks are not capable of being used as a network lock.

Firewalls and User Permissions

Sometimes, a good password will fail to install XMS, This is because your computer actually needs to contact our servers to verify the authenticity of the password. When an internet error comes up, it's typically related to a firewall, user permissions, or antivirus software blocking the connection to our servers.

Try one of these solutions to resolve this issue:

Whitelist which ever XMS program you are trying to install and the registration wizard.
Temporarily disable the firewall/antivirus software.

Note that firewalls are typically something each company's IT department handles.

If you are running Windows 8 or 10, and you are not running in a virtual environment, then the issue could be caused by a Windows feature called Hyper-V. Disabling Hyper-V can resolve the problem. You can find instructions on how to disable Hyper-V by reading this article.

Hardware locks

When installing a hardware lock, be sure to have your drivers installed and running before attempting to register the lock. Additionally, please also ensure that the lock is plugged into the computer at the time you are attempting to register. (Note that as a security measure, the reburn cannot take place remotely.) For instructions on how to install your specific type of hardware lock please visit our page here.

Feel free to contact our technical support team at support@aquaveo.com for more individual help in troubleshooting any of these problems. Please recognize that Aquaveo technical support can only help troubleshoot individual machine issues to a certain point.

Blog tags:

GMS

SMS

WMS

Changing an Existing Model to be a Predictive Model

By aquaveo on July 31, 2019

When you have a completed GMS model, you can use that same model to create a predictive model. A predictive model is used to make predictions based on hypothetical future scenarios. For example, you may need to create a model that predicts if an aquifer will experience strain with an increased population drawing from the aquifer in the model area.

In general, a predictive model is created by using an existing model, then altering an aspect of that model based on the hypothesis. You then run the model again and compare your results with your prediction. Any version of MODFLOW, or any of the other available numeric models in GMS, can be used to create a predictive model.

One method of setting up a predictive model might be as follows:

Create and run a steady state model
Calibrate the model to reduce error in the predictive model
Set the transient settings to a future date
Run the transient model

It is important for you to have an expectation of the outcome of the model run so that you can compare the results with that expectation. When the model run is completed, carefully review the model run results to determine the accuracy of the predictions. When creating a predictive model, you can make use of stochastic analyses.

If the predictive model seems to be far outside of your expectations, then you will need to troubleshoot the existing model before running the predictive model. Using a poorly developed existing model often leads to issues in the predictive model. Make certain the existing model has been well calibrated to closely match the field-observed values. If possible, calibrate the existing model to multiple sets of observation data before creating a predictive model.

Now that you know some of the principles in developing a predictive model, creating your own predictive model in GMS today!

Blog tags:

GMS

Using MODFLOW Native Files

By aquaveo on July 10, 2019

If you have been using MODFLOW with GMS for any amount of time, you have likely noticed that GMS uses a modified version of the MODFLOW files. This is so that the MODFLOW files can be used more efficiently by the GMS interface.

However, there are times when a project may require using the native MODFLOW files. This is often necessary when opening a MODFLOW project that was not originally created in GMS, or when sharing a project with someone who does not have access to GMS.

When importing native MODFLOW files into GMS, there are some important concepts to keep in mind:

You will need to start by importing either the NAM file or MFN file. These files contain a directory for the other files in the MODFLOW project and how they should be opened.
It is important to keep all of the MODFLOW files together in the same directory. Having only the NAME or MFN file will not be enough to open the MODLOW project.
Files for the packages used with the project will typically have a file extension that matches the package. For example, the Wells package will have the extension "*.wel".
All native MODFLOW files can be opened and reviewed using a text editor if needed. See the MODFLOW user guide for information on the file format.

Native MODFLOW files can be exported from GMS by turning on the Save Native Text Copy option in the MODFLOW Global/Basic Package dialog. When exporting native MODFLOW files, keep the following in mind:

GMS will create a separate directory with the native MODFLOW files. This directory will typically be the project name with "_text" appended to it. For example, if the project is named "Aquifer", the directory will be named "Aquifer_text".
All files in this directory should be kept together.
As mentioned before, the files can be reviewed using a text editor.

With GMS 10.4, MODFLOW 6 native files can be imported and exported.

Being able to use native MODFLOW files can greatly enhance collaboration with projects. Try out importing and exporting native MODFLOW files in GMS today!

Blog tags:

GMS