GMS:Mod-PATH3DU: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
===Requirements=== | ===Requirements=== | ||
There are three requirements for creating a mod-PATH3DU model: | There are three requirements for creating a mod-PATH3DU model: | ||
#The MP3DU component must be enabled | #The MP3DU component must be enabled. | ||
#A MODFLOW-USG model must exist. mod-PATH3DU only works with MODFLOW-USG (in GMS). | #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 | #The MODFLOW-USG model must use the '''Save native text copy''' option. | ||
===Importing an Existing Model=== | ===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. | GMS can import an existing mod-PATH3DU model. Open (or drag and drop) the *.mpsim file into GMS and the model will be imported. | ||
===Creating a New Model=== | ===Creating a New Model=== | ||
| Line 30: | Line 30: | ||
===Setting Options=== | ===Setting 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 tracking direction. Some options are not yet supported, such as the DefaultIFACE. | 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 tracking direction. Some options are not yet supported, such as the DefaultIFACE. | ||
===Adding Starting Locations=== | ===Adding Starting Locations=== | ||
To add starting locations to the simulation, there are two methods: | To add starting locations to the simulation, there are two methods: | ||
#Select cells and use the '''Create mod-PATH3DU Particles''' command from the right-click menu | #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 | #Right-click the mod-PATH3DU simulation and select the '''Create Particles at Wells''' command. | ||
See [[GMS:MODPATH_Particle_Tracking#Generating_Particles|MODPATH Particle Tracking, Generating Particles]] for more information on these commands. | See [[GMS:MODPATH_Particle_Tracking#Generating_Particles|MODPATH Particle Tracking, Generating Particles]] for more information on these commands. | ||
| Line 44: | Line 44: | ||
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. | 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:MODFLOW_with_HDF5|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. | mod-PATH3DU cannot read the MODFLOW-USG files that use the [[GMS:MODFLOW_with_HDF5|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. | 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. 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 | To run mod-PATH3DU, right-click the mod-PATH3DU model icon in the Project Explorer and select the '''Run mod-PATH3DU''' command. 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. | |||
==Reading the Solution== | ==Reading the Solution== | ||
After running mod-PATH3DU, a solution is generated consisting of a pathline (.ptl) file and a listing file (.mplist). The user must read 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. | After running mod-PATH3DU, a solution is generated consisting of a pathline (*.ptl) file and a listing file (*.mplist). The user must read 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. | ||
==Display Options== | ==Display Options== | ||
Revision as of 14:16, 8 September 2015
 |
This contains information about a future release of GMS. The content may not apply to other versions. |
 |
