GMS:Saving and Reading a MODFLOW Simulation: Difference between revisions

From XMS Wiki
Jump to navigationJump to search
Line 2: Line 2:
=== Saving a MODFLOW Simulation ===
=== Saving a MODFLOW Simulation ===


Once a MODFLOW simulation has been created and checked for potential problems with the [[GMS:Model Checker|Model Checker]], the next step is to save the simulation to disk and run MODFLOW.  MODFLOW simulations are saved using the '''''Save''''' and '''''Save As''''' commands in the ''File'' menu.
Once a MODFLOW simulation has been created and checked for potential problems with the [[GMS:Model Checker|Model Checker]], the next step is to save the simulation to disk and run MODFLOW.  MODFLOW simulations are saved using the '''Save''' and '''Save As''' commands in the ''File'' menu.


Selecting the '''''Save''''' command saves the GMS project including the model simulation.  By default the model simulation will be saved to the same location as the GMS project.  However, in the Save dialog the path for the model simulation can be specified.
Selecting the '''Save''' command saves the GMS project including the model simulation.  By default the model simulation will be saved to the same location as the GMS project.  However, in the Save dialog the path for the model simulation can be specified.


A MODFLOW simulation is actually saved to a set of input files.  The MODFLOW super file is used to store extra data used by GMS but not used by MODFLOW.  The super file also contains the path to the name file.  The names of all of the input and output files associated with a simulation are saved in the name file.  When MODFLOW is launched, the name of the super file is automatically passed to the MODFLOW executable.
A MODFLOW simulation is actually saved to a set of input files.  The MODFLOW super file is used to store extra data used by GMS but not used by MODFLOW.  The super file also contains the path to the name file.  The names of all of the input and output files associated with a simulation are saved in the name file.  When MODFLOW is launched, the name of the super file is automatically passed to the MODFLOW executable.

Revision as of 14:48, 21 July 2014

MODFLOW
Pre-processing
MODFLOW Commands
Building a MODFLOW Model
Map to MODFLOW
Calibration
Packages Supported in GMS
Saving a MODFLOW Simulation
Importing MODFLOW Files
Unsupported MODFLOW Features
Run MODFLOW
Post-processing
MODFLOW Display Options
MODFLOW Post-Processing Viewing Options
Reading a MODFLOW Simulation
Tutorials
Packages
Flow: BCF6, HUF, LPF, UPW
Solvers:

DE4, GMG, NWT, PCG,

PCGN, LMG, SIP, SOR,

SMS
Other:

BAS6, BFH, CHD1, CLN,

DRN1, DRT1, EVT1, ETS1,

GAGE, GHB1, GNC, HFB1,

HUF, LAK3, MNW1, MNW2,

OUT1, RCH1, RIV1, SFR2,

STR1, SUB1, SWI2, WEL1,

UZF1
v • e

Saving a MODFLOW Simulation

Once a MODFLOW simulation has been created and checked for potential problems with the Model Checker, the next step is to save the simulation to disk and run MODFLOW. MODFLOW simulations are saved using the Save and Save As commands in the File menu.

Selecting the Save command saves the GMS project including the model simulation. By default the model simulation will be saved to the same location as the GMS project. However, in the Save dialog the path for the model simulation can be specified.

A MODFLOW simulation is actually saved to a set of input files. The MODFLOW super file is used to store extra data used by GMS but not used by MODFLOW. The super file also contains the path to the name file. The names of all of the input and output files associated with a simulation are saved in the name file. When MODFLOW is launched, the name of the super file is automatically passed to the MODFLOW executable.

When a MODFLOW simulation is saved, the names of the other MODFLOW input files are automatically patterned after the name of the super file. For example, if the super file is named sampmod.mfs, the other files are named sampmod.bas, sampmod.bcf, etc.

The user can adjust the output options in the Output Control dialog

The version of MODFLOW 2000 that ships with the GMS software has been modified to be able to read and write input data stored in HDF5 files. For more information see MODFLOW with HDF5.

Reading a MODFLOW Simulation

Once a MODFLOW simulation has been saved by GMS using the Save command in File menu, the entire simulation can be read back into GMS using the Open command in the File menu.

MODFLOW simulations can be read in individually (*.mfs) or as part of a project (*.gpr). They can also be imported by using the MODFLOW name file. The extension for the name file must be changed to *.mfn.

Reading a Completed MODFLOW Solution

When you are using the Model Wrapper to control your MODFLOW run, you can use the Read MODFLOW solution toggle at the bottom of the dialog to automatically read in the corresponding solution.

You can also read in solution files generated by MODFLOW using the Read Solution command in the MODFLOW menu. This command brings up the a file browser and prompts you to choose a MODFLOW super file (pre GMS 7.0) or a MODFLOW name file (GMS 7.0+).


Retrieved from "https://www.xmswiki.com/index.php?title=GMS:Saving_and_Reading_a_MODFLOW_Simulation&oldid=74073"