User's guide of Proceessing Modflow 5.0

152 Processing Modflow
- Perform PESTCHEK prior to running PEST: PESTCHEK reads the PEST input files
generated by PMWIN, making sure that every item is consistent with every other item
and writes errors to the file PEST.CHK. It is recommended to use PESTCHEK, as
PMWIN and PEST do not carry out consistency checks of all user-specified control data
and parameters.
- Check the model data: Before creating data files for MODFLOW, PMWIN will check
the geometry of the model and the consistency of the model data given in table 3.5, if this
option is checked. The errors (if any) are saved in the file CHECK.LST located in the
same folder as your model data.
< OK: Click OK to start the generation of the MODFLOW and PEST input files. In addition,
PMWIN generates two batch files PEST.BAT and MODELRUN.BAT in your model folder.
When all necessary files are generated, PMWIN automatically runs PEST.BAT in a DOS-
window. The other batch file MODELRUN.BAT will be called by PEST. After completing
the parameter estimation process, PEST prints the optimized parameter values to the run
record file PESTCTL.REC in your model folder and writes the optimized parameter values
to the corresponding input files of MODFLOW (BCF.DAT, WEL.DAT,... , etc.). The
simulation results of MODFLOW are updated by using these parameter values.
Note that PMWIN does not retrieve the optimized parameter values into the data
matrices. Your (PMWIN) model data will not be modified in any way. This provides more
security for the model data, because an automatic calibration process does not necessarily
lead to success. If you want to operate on a calibrated model, you can import the calibrated
MODFLOW model by choosing Convert Model... from the File menu.
3.6.5 PEST (Inverse Modeling)
Fig. 3.54 The Run PEST dialog box