GMS:Importing an MT3DMS Simulation: Difference between revisions
m (Jcreer moved page GMS:Importing an MT3D Simulation to GMS:Importing an MT3DMS Simulation) |
No edit summary |
||
| Line 13: | Line 13: | ||
{{Navbox GMS}} | {{Navbox GMS}} | ||
[[Category:MT3DMS]] | [[Category:MT3DMS]] | ||
[[Category:Importing Data]] | [[Category:Importing Data|MT3D]] | ||
Revision as of 15:24, 29 August 2016
It is often necessary to import an MT3DMS simulation that was not generated by GMS. Since GMS uses the standard MT3DMS file format, this is not a problem in most cases. However, there are a few steps and precautions that should be taken.
File Formats
GMS uses the standard MT3DMS file formats described in the MT3DMS documentation (Zheng, 1998). The files being imported must match these formats exactly. If the files were generated for a version of MT3DMS that uses a different set of file formats, the files will need to be edited before they can be successfully imported to GMS.
CON File
The source code of MT3DMS was changed to create a *.con file instead of the default *.ucn file. GMS can read either the *.con or *.ucn file. The *.con file is written in the GMS binary dataset format.
Importing Super Files
GMS uses an MT3DMS super file to organize the files used by an MT3DMS simulation. This file is not a standard MT3DMS file. One approach to importing an externally defined simulation is to create an MT3DMS super file containing the names of the files used in the simulation using a text editor.
GMS – Groundwater Modeling System | ||
|---|---|---|
| Modules: | 2D Grid • 2D Mesh • 2D Scatter Point • 3D Grid • 3D Mesh • 3D Scatter Point • Boreholes • GIS • Map • Solid • TINs • UGrids |  |
| Models: | FEFLOW • FEMWATER • HydroGeoSphere • MODAEM • MODFLOW • MODPATH • mod-PATH3DU • MT3DMS • MT3D-USGS • PEST • PHT3D • RT3D • SEAM3D • SEAWAT • SEEP2D • T-PROGS • ZONEBUDGET | |
| Aquaveo | ||
