Aquaveo & Water Resources Engineering News

Exporting Map Coverages in SMS

Do you have a map coverage with specific defined attributes in an SMS project that you would like to add to another project? There is a solution: starting in SMS 13.2 you can export your map coverage as a DMC file that you can import into another project.

For exmaple, say that you have defined a weir structure on an SRH-2D boundary condition coverage for your project. You could, conceivably, have a massive project with many different coverages, meshes, and simulations. If you, or a coworker, would like to use that weir with its defined attributes in another project, recreating the same weir would be inefficient. Instead, exporting just the weir coverage as a DMC file allows you to import the weir coverage with its feature objects and attributes into another project. This will save time for everyone involved in the project, streamlining the process.

There are three steps to export a map DMC:

  1. Right-click on a coverage of your choice in the Project Explorer and select the Export command.
  2. In the Export Coverage dialog, change Save as type to be "SMS model coverage (*.dmc)".
  3. Save the DMC file.
Example of Exporting a Map Coverage as DMC File

The DMC file can now be imported into another project. Importing the DMC file will create a new map coverage in the project with all of the feature objects and attributes that were saved with the file.

It should be noted: Nearly all attributes in the coverage will be exported. The exception to this rule is that external files referenced by the coverage are not embedded in the model coverage file. An example of this would be an external tidal WSE source in a CMS-Flow BC coverage. The attribute would include the link to the file, but if the DMC file is read into a project on a different machine, the external file would not be in the same location, and therefore the association is automatically maintained.

It should also be noted that not all map coverage types can be exported as a DMC file. Certain older map coverage types do not have this option at this time.

Try exporting a DMC file and importing it into an SMS 13.2 project today!

Blog tags: 

Using the MODFLOW 6 Run Queue

Have you noticed that in GMS MODFLOW 6 uses a different model wrapper than other MODFLOW versions? This model wrapper is the SImulation Run Queue and it has a few new options. Since MOFLOW 6 in GMS allows having multiple simulations run, the Simulation Run Queue helps you manage the different simulation runs.

The new Simulation Run Queue dialog functions a little differently from the Model Wrapper dialog. Some of the changes include:

  • You must click Load Solution to load the desired simulation solution into the project. This does not happen automatically when you click close as it does with the MODFLOW model wrapper.
  • If you try to run a simulation already in the queue, you will be prompted to remove the simulation from the run queue before it can be run again.
  • If changing an active simulation’s settings, renaming the active simulation, or taking any action that affects a simulation currently in the queue, you will be asked to remove the simulation from the queue prior to making the changes.
  • The maximum number of concurrent processes allowed can be as many as you want. However, it should be noted that the more complicated the simulations the longer it may take for the processes to complete. Therefore, allowing a large number of processes to run concurrently may slow down processing time if you are running multiple complex simulations.
  • Turning on the Monitoring data will allow you to see the command line run for each process. This can be used to troubleshoot issues that may have occurred during the simulation run. If the simulation encounters an error look to the Command line to see what has caused the error. If there are no errors then your simulation should show 100% in green instead of red (denoting an error).
  • Another important note is that you can still work while the simulation is running. You can move the Simulation Run Queue to the side and continue to work on your project while it runs. Right-clicking on the simulation folder in the Project Explorer provides a command for opening the Simulation Run Queue if you accidentally close it.
Example an error in the MODFLOW 6 simualtion in the Simulation Run Queue

Now that you know a little more about the Simulation Run Queue dialog in GMS 10.6 try it out today!

Blog tags: 

Tips for Working with Virtual Machines

Have you installed GMS, SMS, or WMS (collectively referred to as XMS) on a virtual machine in your office? Using a virtual machine is often done in order to run multiple operating systems, consolidate computing resources, provide integrated disaster recovery, or a number of other reasons. XMS software can be installed on a virtual machine in order to fit your needs. Here are some tips for working with XMS when using a virtual machine.

Virutal machine

First, make certain that your XMS license is compatible with a virtual machine. Both local and flex license codes can be used with a virtual machine. However, local codes will not allow the software to be used by other machines. Older single-user locks cannot be used with a virtual machine.

When using a flex license, the virtual machine will need to have access to the local network in order for other machines to access the XMS license and use the software. Both the XMS application and the Aquaveo License manager need to be installed on the virtual machine.

When sharing files between a virtual machine and a host machine, pay attention to where XMS is running. XMS requires that all files be placed where XMS is installed. Therefore, you cannot save your project on the host machine and run them from the virtual machine if XMS is installed on the virtual machine. You will need to move the files to the virtual machine where XMS and XMS license is installed.

It should also be noted that some simulation runs and application processes in XMS will run slower on a virtual machine than running the same process directly on a physical machine. This is due to the nature of using a virtual machine. If there is a process that is taking an unusually long time, it is recommended that you try running the application on a physical machine.

If you are experiencing issues running XMS on a virtual machine, contact our technical support team and they will be happy to assist you.

Blog tags: