User's guide of Proceessing Modflow 5.0

52 Processing Modflow
3. The Modeling Environment
PMWIN requires the use of consistent units throughout the modeling process. For example, if
you are using length [L] units of meters and time [T] units of seconds, hydraulic conductivity will
3
be expressed in units of [m/s], pumping rates will be in units of [m /s] and dispersivity will be
in units of [m].
A toolbar with buttons representing PMWIN operations or commands is displayed below
the menus. The toolbar is a shortcut for the pull-down menus. To execute one of these shortcuts,
move the mouse cursor over the toolbar button and click on it. In the following sections, the use
of the respective menus will be described in detail. Some of this information has already been
given in Chapter 2, however, this chapter is a complete reference of all menus and dialogs in
PMWIN, therefore some repetitions may occur.
PMWIN contains the following menus File, Grid, Parameters, Models, Tools, Value,
Options and Help. The Value and Options menus are available only in the Grid Editor and
Data Editor environment. PMWIN uses an intelligent menu system to help you control the
modeling process. If you have specified a model data set, the corresponding item of the Grid,
Parameters and Models menus will be checked. To deactivate a selected item in the Models
menu, just seleted the item again. If you do not know which model data still need to be specified,
you may try to run your model by selecting the menu item Run... from the corresponding model
in the Models menu. PMWIN will then tell you what parameters or model data are necessary
to run your model, if unspecified. An overview of the menus in PMWIN is given in table 3.1.
Most of the user-specified data are saved in binary files. A list of the internal data files of
PMWIN is given in Appendix 4. Prior to running the supported models MODFLOW, MT3D,
MT3DMS, MOC3D or the inverse models PEST and UCODE, PMWIN will generate the
required ASCII input files. The names of the ASCII input files are given in Appendix 3. The
formats of the input files of MODFLOW and MT3D, MT3DMS and MOC3D can be found in
the user’s guide the corresponding software on the companion CD-ROM. The particle tracking
model PMPATH retrieves the binary data files of PMWIN directly, thus no ASCII input file is
required by PMPATH.
3. The Modeling Environment