The mod-PATH3DU model is a particle tracking program similar to MODPATH but designed to work with MODFLOW-USG. GMS includes an interface that makes it easy to create mod-PATH3DU simulations, run them, and view the results.
Much of the mod-PATH3DU interface in GMS is similar to the MODPATH interface, but the mod-PATH3DU interface is not yet as fully developed. For example, mod-PATH3DU works more like other models in GMS in that the simulation must be saved and run and then the results are read and displayed, whereas in MODPATH this typically happens automatically whenever a change is made. In the future, more functionality will be added to the mod-PATH3DU interface in GMS.
Creating a Model
Creating a mod-PATH3DU model is taught in the mod-PATH3DU tutorial.
There are three requirements for creating a mod-PATH3DU model:
- The MP3DU component must be enabled.
- A MODFLOW-USG model must exist. mod-PATH3DU only works with MODFLOW-USG (in GMS).
- The MODFLOW-USG model must use the Save native text copy option.
Importing an Existing Model
GMS can import an existing mod-PATH3DU model. Open (or drag and drop) the *.mpsim file into GMS and the model will be imported. For mod-PATH3DU v2.0, this file is the primary file which may have a *.mpsim, *.p3p, or *.json extension.
Creating a New Model
To create a mod-PATH3DU simulation, right-click on a UGrid containing a MODFLOW-USG model and select the New mod-PATH3DU command. A mod-PATH3DU model icon will appear in the Project Explorer. Multiple mod-PATH3DU simulations can be created, with different starting locations and options.
Right-clicking the mod-PATH3DU model and selecting the Options command opens the mod-PATH3DU Options dialog. This dialog can be used to set various options such as the direction.
mod-PATH3DU Options Dialog
The variables in the mod-PATH3DU Options dialog are explained in the following table.
|TrackingDirection||1 - Forward tracking,
2 - Backward tracking
|A flag indicating the direction of the particle tracking computation.|
|Option to let GMS pick the reference time based on the TrackingDirection. If true, ReferenceTimeOption is set to 1 and, for forward tracking, the reference time will be 0.0. For backward tracking, the reference time will be the end time of the model.|
|ReferenceTimeOption||1 - Specify a value for reference time
2 - Specify stress period, time step and relative time position within the time step to use to compute the reference time
|A flag indicating how reference time will be specified. Reference time is the starting time for the particle-tracking with respect to the start of the MODFLOW-USG simulation.|
|StressPeriod||Stress period||If ReferenceTimeOption = 2|
|TimeStep||Time step||If ReferenceTimeOption = 2|
|RelativeTime||Relative time (between 0 and 1)||If ReferenceTimeOption = 2|
|StopOption||1 - Stop at the end (forward tracking) or beginning (backward tracking) of the MODFLOW-USG simulation
2 - Track until all particles reach their termination points
3 - Specify a value of tracking time at which to stop
|A flag indicating how the particle tracking simulation should be terminated.|
|StopTime||Stop time||If StopOption = 3|
|Tracking method. Default is "RK4"|
|UseStepError||STEP_ERROR is set to 1e6 if not being used.|
|STEP_ERROR||Adaptive stepsize error term, ɛ, in equation 2-17. Default is 1.00E-06. Larger values will result in a faster runtime with, potentially, less accurate paths. To turn-off the adaptive step size option make STEPERROR large (1.00E+06).|
|DT_INIT||Initial step size. Default is 10.|
|DT_MAX||Maximum step size. Default is 1.00E+06|
|WELL_CAPTURE_RADIUS||When FORWARD tracking using the adaptive time step option (STEP_ERROR < 1), WELL_CAPTURE_RADIUS is the radial distance from the well, within which, a particle is considered captured.|
|TemporalOption||1 - A single ReleaseTime will be used for all particles
2 - Particles will be released ReleaseEventCount times every ReleasePeriodLength
3 - Particles will be released ReleaseEventCount times at the specified ReleaseTimes
|A flag indicating whether a single or multiple release events will be used for particles.|
|ReleaseTime||Greater than 0.0||Release time of particles relative to mod-PATH3DU tracking time.|
|ReleaseEventCount||Greater than 0||If TemporalOption = 2 or 3. The number of release events.|
|ReleasePeriodLength||Greater than 0.0||If TemporalOption = 2. The time interval between particle release events.|
Adding Starting Locations
To add starting locations to the simulation, there are three methods:
- Select cells and use the Create mod-PATH3DU Particles command from the right-click menu.
- Right-click the mod-PATH3DU simulation and select the Create Particles at Wells command.
- Creating starting locations from another UGrid's points or cells (starting at GMS 10.3).
See MODPATH Particle Tracking, Generating Particles for more information on these commands.
Prior to running mod-PATH3DU, it is a good idea to run the Model Checker by right-clicking the mod-PATH3DU simulation and selecting the Check Simulation command. The Model Checker looks for obvious problems in model setup and reports them as warnings or errors.
Saving and Running the Model
Unlike MODPATH, mod-PATH3DU does not have an option to run automatically in GMS when changes are made to the model. The user must save and run the model manually.
mod-PATH3DU cannot read the MODFLOW-USG files that use the GMS modified input format. The user must use the Save native text copy option for MODFLOW-USG, and a solution must be generated for the native text copy of the MODFLOW-USG model. This can be done by using the MODFLOW | Advanced | Run MODFLOW Dialog command. Running MODFLOW-USG normally will not generate a solution for the native text copy.
When the project is saved, the mod-PATH3DU input files are saved with the MODFLOW-USG native text input files.
To run mod-PATH3DU, right-click the mod-PATH3DU model icon in the Project Explorer and select the Run mod-PATH3DU command. In GMS 10.2, the Run Model dialog appears and let's the user choose the mod-PATH3DU model executable to run and the *.mpsim file to pass to it. mod-PATH3DU runs in a console window—there is no model wrapper dialog for mod-PATH3DU like with other models. Starting at GMS 10.3, a model wrapper dialog is used to display the model progress and when the model finishes, the solution will be read automatically if the "Read solution on exit" option is checked.
mod-PATH3DU version 1.1.0 and 2.0 uses a modified grid specification file (GSF). A utility called writep3dgsf.exe creates the modified *GSF given the standard GSF and is included with mod-PATH3DU version 1.1.0 and 2.0. GMS runs this utility automatically just before mod-PATH3DU is run from GMS and the new file is given a .gsf2 extension.
Reading the Solution
After running mod-PATH3DU, a solution is generated consisting of a pathline (*.ptl) file and a listing file (*.mplist). Starting at GMS 10.3, the model wrapper will import the solution automatically. In GMS 10.2, import the solution by right-clicking the mod-PATH3DU model in the Project Explorer and selecting the Read Solution command. The user is prompted to open a *.ptl file. Upon doing so, the solution is displayed in the Project Explorer and the pathlines are drawn on the UGrid.
The mod-PATH3DU model data can be exported in a few different ways for processing in other programs if desired. The Export command can be used to export a shapefile of the pathline solution. Three different types of shapefiles can be exported: a point shapefile containing pathline points, a line shapefile containing the pathlines, and a polygon shapefile containing capture zone polygons. A tab delimited file containing the pathline points can also be exported.
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 • MODAEM • MODFLOW • MODPATH • mod-PATH3DU • MT3DMS • MT3D-USGS • PEST • PHT3D • RT3D • SEAM3D • SEAWAT • SEEP2D • T-PROGS • ZONEBUDGET|
- ^ Cite error: Invalid
<ref>tag; no text was provided for refs named