User:Jcreer/GMS:MODFLOW Model Wrapper: Difference between revisions
From XMS Wiki
Jump to navigationJump to search
No edit summary |
m (Protected "User:Jcreer/GMS:MODFLOW Model Wrapper" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOINDEX__ | __NOINDEX__ | ||
Running MODFLOW can be done a couple ways: | |||
*In the Project Explorer, right-click on MODLOW simulation and select the '''Run MODFLOW''' command. | |||
*Select the ''MODFLOW'' | '''Run MODFLOW''' command. | |||
* Click the '''Run MODFLOW''' [[File:Map to MODFLOW Macro.svg|16 px]] macro. | |||
The MODFLOW run will launch the ''MDOFLOW'' model wrapper dialog. | |||
==MODFLOW Model Wrapper== | |||
[[File:MODFLOW Wrapper.png|thumb|400 px|Example of the MODFLOW model wrapper]] | [[File:MODFLOW Wrapper.png|thumb|400 px|Example of the MODFLOW model wrapper]] | ||
The MODLOW model wrapper dialog will appear when running MODFLOW. This model wrapper dialog displays information about the MODFLOW run. Information displayed includes the following: | The MODLOW model wrapper dialog will appear when running MODFLOW. This model wrapper dialog displays information about the MODFLOW run. Information displayed includes the following: | ||
| Line 8: | Line 14: | ||
The model wrapper also has the following options: | The model wrapper also has the following options: | ||
* ''Read solution on exit'' – Turning on this option will cause the solution data to automatically be imported into GMS. | * ''Read solution on exit'' – Turning on this option will cause the solution data to automatically be imported into GMS. | ||
* ''Turn on contours (if not on already) – If the project does not have contour display options turned on, this option will cause the contour display to be activated. | * ''Turn on contours (if not on already)'' – If the project does not have contour display options turned on, this option will cause the contour display to be activated. | ||
==Error vs. Iteration== | ===Error vs. Iteration=== | ||
The Error vs. Iteration plot will show iterations of the MODFLOW run. The plot is hard wired to only show 25 iterations. The Error vs. Iteration is usually showing the maximum head change, but this can vary as follows: | The Error vs. Iteration plot will show iterations of the MODFLOW run. The plot is hard wired to only show 25 iterations. The Error vs. Iteration is usually showing the maximum head change, but this can vary as follows: | ||
*SAMG prints end_res - <!--not positive if this is--> head <!--or budget--> residual | *SAMG prints end_res - <!--not positive if this is--> head <!--or budget--> residual | ||
Latest revision as of 22:33, 3 August 2022
Running MODFLOW can be done a couple ways:
- In the Project Explorer, right-click on MODLOW simulation and select the Run MODFLOW command.
- Select the MODFLOW | Run MODFLOW command.
- Click the Run MODFLOW
macro.
The MODFLOW run will launch the MDOFLOW model wrapper dialog.
MODFLOW Model Wrapper
The MODLOW model wrapper dialog will appear when running MODFLOW. This model wrapper dialog displays information about the MODFLOW run. Information displayed includes the following:
- The file path to MODFLOW executable being used in the model run. If the executable being used is incorrect, go to the Preferences dialog to change this path.
- The file path to where the solution files will be generated. This will correspond to the location where the project has been saved.
- The Error vs. Iteration graph. See below for more details.
- The command line display. This will display any errors or warnings that MODFLOW encounters during the model run.
The model wrapper also has the following options:
- Read solution on exit – Turning on this option will cause the solution data to automatically be imported into GMS.
- Turn on contours (if not on already) – If the project does not have contour display options turned on, this option will cause the contour display to be activated.
Error vs. Iteration
The Error vs. Iteration plot will show iterations of the MODFLOW run. The plot is hard wired to only show 25 iterations. The Error vs. Iteration is usually showing the maximum head change, but this can vary as follows:
- SAMG prints end_res - head residual
- PCG prints BIGH - max head change
- PCGN prints MXHCH - max head change
- SIP prints BIG - max head change
- SSOR prints BIG - max head change
- DE4 prints BIG - max head change
- GMG prints BIGH - max head change
- NWT prints Fheadsave - max head change
- SMS solver prints ABIGCH - max head change
