Σχόλια 0

Το κείμενο του εγγράφου

Upgrade to MODFLOW-GUI: Addition ofMODPATH, ZONEBDGT, and additionalMODFLOW packages to the U.S. GeologicalSurvey MODFLOW-96 Graphical-User InterfaceBy Richard B. WinstonU.S. GEOLOGICAL SURVEYOpen-File Report 99-184Reston, Virginia1999U.S. DEPARTMENT OF THE INTERIORBRUCE BABBITT, SecretaryU.S. GEOLOGICAL SURVEYCharles G. Groat, DirectorAlthough the computer program described in this report has been tested and used by theU.S. Geological Survey (USGS), no warranty, expressed or implied, is made by the USGS as tothe accuracy of the functioning of the program and related material. The code may be updatedand revised periodically.Any use of trade, product, or firm names in this publication is for descriptive purposesonly and does not imply endorsement by the U.S. Government.For additional information Copies of this report can bewrite to: purchased from:Office of Ground Water U.S. Geological SurveyU.S. Geological Survey Branch of Information Services411 National Center Box 25286Reston, VA 20192 Denver, Colorado 80225-0286ContentsPageAbstract............................................................................................................................!Introduction.....................................................................................................................^System Requirements......................................................................................................4Installation.......................................................................................................................^Starting the Preprocessor...............................................................................................^Entering Non-spatial Data................................................................................................6Changes to Existing Features....................................................................................................... 6Overall Appearance..................................................................................................................6Geology Tab............................................................................................................................. 6Stresses 1 Tab...........................................................................................................................?Output Files Tab....................................................................................................................... 7Time Tab.................................................................................................................................. 7Sovers/Other Packages Tab .....................................................................................................8MOC3D Tab............................................................................................................................ 8MOC3D Particles Tab..............................................................................................................9MOC3D Output + Dipsersivities Tab.................................................................................... 10New Features............................................................................................................................. 10Context-sensitive help............................................................................................................ 10Deactivating Packages without Deleting the Data for the Package....................................... 11Specifying Transmissivity, Vertical Conductance, and Confined Storage Coefficient......... 11Saving Default Values ........................................................................................................... 12Specifying Initial Head Formula............................................................................................ 13Use Binary Head File for Initial Heads.................................................................................. 13Using Alternative Export Templates...................................................................................... 13Explicitly specify recharge or evapotranspiration layer........................................................ 14Stream Package...................................................................................................................... 14Flow and Head Boundary Package........................................................................................ 15Horizontal-Flow Barrier Package.......................................................................................... 15MODPATH............................................................................................................................16ZONEBDGT..........................................................................................................................20Entering Spatial Data.....................................................................................................21Renamed Layers and Parameters............................................................................................... 21Locked Recharge Elevation parameter...................................................................................... 22Importing Well Data.................................................................................................................. 22'MOC3D Transport Subgrid....................................................................................................... 22IFACE[i] ....................................................................................................................................23MODPATH information layers................................................................................................. 23ZONEBDGT..............................................................................................................................24Stream Package.......................................................................................................................... 24Flow and Head Boundary Package............................................................................................ 26Horizontal Flow Barrier Package.............................................................................................. 28Running MODFLOW, MOC3D, MODPATH, or ZONEBDGT.........................................30Creating Input Files................................................................................................................... 30Processing the Export Template................................................................................................ 31inRunning MODFLOW, MOC3D, MODPATH, or ZONEBDGT-ContinuedUsing the MODFLOW PIE with Calibration Programs............................................................ 32Running independent templates with the MODFLOW PIE.............................................33Converting contours on information layers to data points on data layers................................. 33Preparing Calibration Statistics.................................................................................................33Files Created for MODFLOW-96, MODPATH, and ZONEBDGT Simulations ...............34Files Created by Executing MODFLOW-96, MODPATH, and ZONEBDGT...................36Visualizing Results.........................................................................................................37Visualizing results from MODFLOW or MOC3D.................................................................... 37Visualizing Results from MODPATH ...................................................................................... 40Visualizing Results from ZONEBDGT..................................................................................... 40Example.........................................................................................................................41Problem Description.................................................................................................................. 41Create a New Model.................................................................................................................. 42Define the Study Area............................................................................................................... 43Defining Specified-Head Boundaries........................................................................................ 44Choosing the Stream Package................................................................................................... 44Changing the Number of Geologic Units.................................................................................. 44Accessing Context-Sensitive Help............................................................................................44Finish Changing the Number of Geologic Units.......................................................................45Defining a Stream Boundary..................................................................................................... 45Define No-Flow Boundaries...................................................................................................... 46Other Packages and Options...................................................................................................... 47Save the Project......................................................................................................................... 47Setting the Top Elevation.......................................................................................................... 47Set Aquifer Properties................................................................................................................47Create Pumping Wells............................................................................................................... 48Create Specified-Flow Boundary ..............................................................................................48Run MODFLOW....................................................................................................................... 49Plot Heads Generated by MODFLOW...................................................................................... 49Define MODPATH Particle Starting Points.............................................................................. 50Run MODPATH........................................................................................................................ 51Plot MODPATH Results........................................................................................................... 51Define Horizontal-Flow Barrier and Rerun MODFLOW......................................................... 52Use ZONEBDGT....................................................................................................................... 53View ZONEBDT Results..........................................................................................................55Customizing the MODFLOW PIE...................................................................................56Conclusions...................................................................................................................56References ....................................................................................................................57Appendix 1: Edit Contours PIE ......................................................................................59Appendix 2: Budgeteer ..................................................................................................60Appendix 3: RotateCells ................................................................................................60Appendix 4: MODFLOW_ReadFileValue.......................................................................61Appendix 5: GetMyDirectory, SelectChar.exe, and WaitForMe.exe ..............................62Appendix6: HydrographExtractor.exe..........................................................................-63Appendix 7: Web-Based Tutorial ...................................................................................64IVFiguresPageFigure 1. Revised Appearance of the Geology Tab....................................................................... 7Figure 2. Revised Appearance of the Time Tab............................................................................. 8Figure 3. Revised Appearance of the MOC3D Tab (formerly Transport Subgrid Tab)................ 9Figure 4. Revised Appearance of the MOC3D Particles Tab (formerly Particles Tab)............... 10Figure 5. Example of context-sensitive help................................................................................ 11Figure 6. Geology tabs with columns used to choose whether to specify Transmissivity(Specify T), Vertical Conductivity (Specify Vcont), and Confined Storage Coefficient(Specify sfl)...............................................................................................................Figure 7. Stresses 2 tab used for selecting the Stream Package and Flow and Head BoundaryPackages................................................................................................................................ 15Figure 8. Solvers/Other Packages Tab......................................................................................... 16Figure 9. MODPATH Tab........................................................................................................... 17Figure 10. MODPATH Options Tab............................................................................................ 18Figure 11. MODPATH Times Tab..............................................................................................20Figure 12. ZONEBDGTTab........................................................................................................21Figure 13. Interpretation of IFACE[i] = 1 to 6............................................................................. 23Figure 14. Illustration of the linkage among stream segments.................................................... 25Figure 15. Two models that differ only in the orientation of the area surrounded by ahorizontal-flow barrier..........................................................................................................28Figure 16. Close up of a section of the horizontal-flow barrier in model 2................................. 29Figure 17. Method to calculate the reduction of HYDCHR when horizontal-flow barriers areat an angle to the grid............................................................................................................ 29Figure 18. Revised Run MODFLOW/MOC3D Dialog box. In this example, MOC3D is notinstalled at the location specified in the MOC3D Path edit-box so the background of thestatus bar, would appear red.................................................................................................. 31Figure 19. PIE-Generated Progress Bar with error messages...................................................... 32Figure 20. Dialog box to select type of data set for post-processing........................................... 38Figure 21. MODFLOW Post-Processing Dialog Box.................................................................. 39Figure 22. The "Layer Already Exists" Dialog Box.................................................................... 39Figure 23. Plot MODPATH Results Dialog box after reading a set of pathlines........................ 40Figure 24. Base map for a two-dimensional sample problem...................................................... 42Figure 25. Domain Outline........................................................................................................... 44Figure 26. The label of the stream segment indicates the stream flows from right to left........... 45Figure 27. Heads Generated by MODFLOW Simulation............................................................50Figure 28. Contours on "MODPATH Particles Unitl" layer....................................................... 51Figure 29. MODPATH Pathlines................................................................................................. 52Figure 30. Slurry wall connecting the two, internal, bedrock outcrops....................................... 53Figure 31. Pathlines and head contours in the vicinity of the horizontal-flow barrier................. 53Figure 32. ZONEBDGT Primary zones....................................................................................... 55Figure 33. Budgeteer: Bar Chart of an Individual Zone.............................................................. 56TablesPageTable 1. System Requirements.......................................................................................................4Table 2. New Files Created for MODFLOW Simulations..........................................................35Table 3. Files Created for MODPATH........................................................................................ 36Table 4. Files Created for ZONEBDGT...................................................................................... 36Table 5. Files Created by MODFLOW........................................................................................ 37Table 6. Files Created by MODPATH and ZONEBDGT........................................................... 37Table 7. Parameter values for two-dimensional sample problem................................................ 41VIUpgrade to MODFLOW-GUI: Addition ofMODPATH, ZONEBDGT, and additionalMODFLOW packages to the U.S. GeologicalSurvey MODFLOW-96 Graphical-User InterfaceRichard B. WinstonAbstractThis report describes enhancements to a Graphical-User Interface (GUI) forMODFLOW-96, the U.S. Geological Survey (USGS) modular, three-dimensional, finite-difference ground-water flow model, and MOC3D, the USGS three-dimensional, method-of-characteristics solute-transport model. The GUI is a plug-in extension (PIE) for the commercialprogram Argus ONE . The GUI has been modified to support MODPATH (a particle trackingpost-processing package for MODFLOW), ZONEBDGT (a computer program for calculatingsubregional water budgets), and the Stream, Horizontal-Flow Barrier, and Flow and HeadBoundary packages in MODFLOW. Context-sensitive help has been added to make the GUIeasier to use and to understand. In large part, the help consists of quotations from the relevantsections of this report and its predecessors. The revised interface includes automatic creation ofgeospatial information layers required for the added programs and packages, and menus anddialog boxes for input of parameters for simulation control. The GUI creates formatted ASCIIfiles that can be read by MODFLOW-96, MOC3D, MODPATH, and ZONEBDGT. All fourprograms can be executed within the Argus ONE application (Argus Interware, Inc., 1997).Spatial results of MODFLOW-96, MOC3D, and MODPATH can be visualized within ArgusONE . Results from ZONEBDGT can be visualized in an independent program that can also beused to view budget data from MODFLOW, MOC3D, and SUTRA. Another independentprogram extracts hydrographs of head or drawdown at individual cells from formattedMODFLOW head and drawdown files. A web-based tutorial on the use of MODFLOW withArgus ONE has also been updated. The internal structure of the GUI has been modified to makeit possible for advanced users to easily customize the GUI. Two additional, independent PIE'swere developed to allow users to edit the positions of nodes and to facilitate exporting the gridgeometry to external programs.IntroductionThe purpose of this report is to describe enhancements to the USGS MODFLOWGraphical-User Interface (GUI) Version 2 (Hornberger and Konikow, 1998; Shapiro and others,1997). Major changes introduced in this revision of the GUI include addition of context-sensitive help and incorporation of interfaces for the following programs or packages:MODP ATH (Pollock, 1994),ZONEBDGT (Harbaugh, 1990),Stream Package (Prudic, 1989),Horizontal-Flow Barrier Package (Hsieh and Freckleton, 1993), andFlow and Head Boundary Package (Leake and Lilly, 1997).In addition, a variety of less significant changes have been made to the GUI. Theseinclude the following.It is now possible to specify transmissivity, vertical conductance, and the confined storageparameter directly rather than having them calculated from other parameters.It is now possible to specify that a unit be convertible between confined and unconfinedconditions but with a constant transmissivity (LAYCON = 2).It is now possible to deactivate a package without deleting the layers and parameters for thatpackage.The Modify buttons previously used to make changes to text in tables have been eliminated.Changes are now made directly in the table.An option has been added to allow users to choose among several expressions for definingthe initial head and IBOUND parameters on the MODFLOW FD Grid layer.An option has been added to allow the user to use alternative export templates for the River,Drain, or General-Head Boundary packages. The alternative templates allow for moreflexible specification of the river parameters but do not permit more than a single boundaryof a given type in a cell.An About tab has been added to the Edit Project Info dialog box. The About tab includesthe USGS identifier, bibliographic citations of the documentation of the GUI, the version ofthe GUI, a hypertext link to the URL where the GUI may be downloaded, and a link to emailaddress for technical support.The edit-box for the WSEED parameter on the SIP tab is disabled unless the WSEEDparameter is used by MODFLOW.The title of the PCG tab has been changed to PCG2 to reflect the version of PCG currentlyused by the USGS.On the PCG2 tab, the parameter IPCGCD has been replaced by DAMP because IPCGCDhas been replaced by DAMP in the PCG2 package.The GUI no longer imposes any restriction on the number of geologic units or stress periods.However, if the number of MODFLOW layers exceeds 200, the limit in the standard releaseof MODFLOW-96, a warning message will be displayed.The dialog boxes provided by the GUI can now be resized.A variety of non-spatial data are now entered in different locations than previously to makedata entry more intuitive.If any layers or parameters that should be present are missing, they will be added whenclicking on the OK button in the Edit Project Info dialog box. A layer or parameter may beabsent because it was not used in a previous version of the GUI or because a user hasmistakenly deleted it manually. By restoring missing layers or parameters, a model isreturned to a useable state despite user-errors.The method for specifying the extent of the transport subgrid for MOC3D has been changed.Previously, users would enter the first and last row and column numbers of the transportsubgrid. Now users define the subgrid boundary on an information layer. The change makesit possible to modify the grid without need to re-enter values of ISROW1, ISROW2,ISCOL1, and ISCOL2. To update old models, the user may need to open and then close theEdit Project Info dialog-box so that the MOC3D Transport Subgrid layer can be created.The user will be prompted to open it, if required, when reading a data set prepared with anolder version of the GUI.A method of importing well information has been added that makes it simpler to import welldata from spreadsheets than previously.It is now possible to specify the location of an executable file without needing to modify theexport template.During the export process, a dialog-box appears. It displays the progress of the exportprocess and the estimated time remaining for the export process to finish. It also displayserror and warning messages.The speed of the export process has been increased especially for models with multiple stressperiods.More extensive error checking is done during the export process.In post-processing charts, inactive cells are skipped. Because the inactive cells may varyamong MODFLOW layers, it is no longer possible to make post-processing charts ofdifferent MODFLOW layers using the same data layer. Thus, the Post-processing PIE mustbe called separately for each MODFLOW layer for which a post-processing plot will bemade.The language in which the GUI is written has been changed from C++ to Object Pascal.The internal structure of the GUI has been altered to make it possible for advanced users tocustomize the GUI. If the customization is done properly, it will be possible to incorporatefuture changes to the USGS version of the GUI into a customized version of the GUI withrelatively little effort.In addition to changes in the GUI a number of independent programs were created tofacilitate various tasks that do not require integration with Argus ONE (Argus Interware, Inc.,1997). One program, Budgeteer (Appendix 2), extracts, water budget data from files created byMODFLOW (McDonald and Harbaugh, 1988; Harbaugh and McDonald, 1996), MOC3D(Konikow and others, 1996), ZONEBDGT (Harbaugh, 1990), or SUTRA (Voss, 1984) and plotsit. The data can be saved in a form suitable for import into commercial spreadsheet programs.Another program, Hydrograph Extractor (Appendix 6), reads head or drawdown for individualcells from the formatted head or drawdown files produced by MODFLOW. It also plots the dataand allows it to be saved in a form suitable for import into commercial spreadsheet programs.A web-based tutorial on the use of MODFLOW with Argus ONE is available fordownloading together with version 3 of the MODFLOW GUI (Appendix 7). The tutorial wasoriginally prepared by Argus Interware for use with version 1 of the MODFLOW GUI.I appreciate the suggestions for improvements made by USGS colleagues A.M. Shapiro,L.F. Konikow, G.Z. Hornberger, Earl Greene, and numerous users of previous versions of theMODFLOW-GUI. I wish to thank S. Dolev and J. Margolin of Argus Interware for theirtechnical assistance. I would also like to thank all those who provided "bug-reports" or otheradvice while the revised GUI was under development.I would like to thank Argus Interware for granting permission to update theirMODFLOW tutorial.System RequirementsThe revised MODFLOW-GUI has been tested on personal computers with Windows 95and Windows NT 4.0. It has not been tested extensively on Windows 98. The user must havethe Windows version of Argus Open Numerical Environments (Argus ONE ). Argus ONElargely determines hardware requirements. At the time this was written, the requirements forArgus ONE were the following:CPU Pentium, Pentium Pro recommendedMouse RequiredRAM 32 MB or more recommendedDISK 7 MBDisplay VGA/SVGA Display, 65,000 colorsIn addition, the MODFLOW-GUI requires a display with a resolution of at least 632x590.InstallationTable 1. System Requirements.Files required for installation Location to installMFGUI_30.dll <Argus directory>\ArgusPffi\MODFLOWMODFLOW.cnt <Argus directory>\ArgusPffi\MODFLOWMODFLOW.hlp <Argus directory>\ArgusPffi\MODFLOW*.met (see readme.txt file for <Argus directory>\ArgusPIE\MODFLOWdetails)MODFLOW_JoinFiles.dll <Argus directory>\ArgusPIE\JoinFilesMODFLOW_BlockList.dll <Argus directory>\ArgusPffi\BlockListMODFLOW_ReadFileValue.dll <Argusdirectory>\ArgusPffi\ReadFileValueMODFLOWJListdll <Argus directory>\ArgusPIE\List ,GetMyDirectory.dll <Argus directory>\ArgusPIE\GetMyDirectorySelectChar.exe <Argus directory>\ArgusPIE\GetMyDirectoryWaitForMe.exe <Argus directory>\ArgusPIE\GetMyDirectoryMODFLOW_ProgressBarPIE.dll <Argus directory>\ArgusPIE\ ProgressBarPIECtl3d32.dll (Windows NT 3.51) <Windows directory>\System32__________Except for ctl3d32.dll, all the files used by the PIE should be placed in the ArgusPIEdirectory or in subdirectories under the ArgusPIE directory. Unless otherwise noted, it isgenerally a good idea to place each PIE in its own subdirectories under the ArgusPIE directory.The export templates used by the PIE (*.met), and the help system files (modflow.hlp andmodflow.cnt) should be placed in the same directory as the MODFLOW PIE (MFGUI_30.dll).Ctl3d32.dll is only required for Windows NT 3.51. If required, it should be placed in theSystem32 directory under the main directory for the operating system (normally WinNT).Many, but not all, users will already have Ctl3d32.dll on their computer and in such cases theygenerally should not replace the existing version with the one distributed with the PIE. Exporttemplates that are meant to be modified and executed manually by the user may be placed in anyconvenient location. These include contour2data.met and statistics.met. All the files comprisingthe PIE are available from the U.S. Geological Survey, but they require an executable version ofArgus ONE (version 4.20i or higher) to operate. Although not required to operate theMODFLOW PIE, the EditContours, RotateCells, MODFLOW_ReadFileValue, andGetMyDirectory PIE's and the Budgeteer, SelectChar, WaitForMe, Extract Hydrographprograms and MODFLOW tutorial (see Appendices 1-7) were designed for use with models inthe MODFLOW PIE and are thus distributed with the MODFLOW PIE. The may also be usefulfor other purposes.Previous versions of the GUI (Shapiro and others, 1997; Hornberger and Konikow, 1998)used a number of array PIE's that are not used by the current version of the PIE(Chk_BlockArray.dll, Chk_LayArray.dll). If those files are present, they may be deleted withoutaffecting the new version of the MODFLOW-GUI. Previous versions of the MODFLOW-GUIand post-processing PIE's (mfgui_20.dll, mfpost20.dll, mcpostl0.dll) should be deleted from theArgus PIE directory because they will interfere with the new version of the PIE. The functionsperformed by all three of these older PIE's have been incorporated into the new GUI.Executable versions of MOC3D (Version 1.2 or later), MODFLOW-96, MODPATH, andZONEBDGT must be installed to run these models from the Argus ONE environment. TheMODFLOW-96 code and the MOC3D code are integrated into one code (MOC3D).MODFLOW-96 (without MOC3D) is executed when using the GUI to simulate ground-waterflow only, without transport; MOC3D is executed when simulating ground-water flow withtransport. Although it does not matter what compiler was used to create the executable versionsof the models, it is important that they all be compiled with compatible compilers. This isbecause ZONEBDGT and MODPATH read binary files created by MOC3D and MODFLOW-96. The format of the binary files is compiler-dependent. The versions of these programs on theUSGS software web site are all compatible with one another.The MODFLOW-GUI consists of a dynamic-link library (MFGUI_30.DLL) thatprovides the core functionality. It provides the Edit Project Info, Run MODFLOW, and avariety of other dialog boxes. It is responsible for creating and destroying MODFLOW-relatedlayers and parameters in the Argus ONE project and for accessing its context-sensitive help. Itprocesses the model-related export templates and prepares them for execution by Argus ONE .It also provides a number of hidden PIE functions that are called when the export templates areexecuted. The model-related export templates are the files MODFLOW.met, ZoneBud.met, andMODPATH.met. These files contain the instructions for creating the input files forMODFLOW, MOC3D, ZONEBDGT, and MODPATH. When they are executed, the exporttemplates use PIE functions provided by the following dll's: List.dll, BlockList.dll,ProgressBar.dll, and JoinFiles.dll. Of these, only ProgressBar.dll will be visible to the user. Itdisplays a progress bar during the execution of export templates and provides an estimate of thetime required until execution of the export template is complete. It also displays error andwarning messages. Modflow.hlp and Modflow.cnt provide the online help for the PIE. Finally,ctl3d32.dll, a dynamic-link library from Microsoft Corporation , provides the three-dimensionalappearance of the certain portions of the dialog boxes when the PIE is operated on computersusing the Windows NT 3.51 operating system.Starting the PreprocessorThe user can start a new model or open an existing model in the same way as in previousversions of the MODFLOW-GUI. To start a new model, start Argus ONE and selectPIEs|New MODFLOW Project. To open an existing model, start Argus ONE and selectFile|Open... and then select the file to open. In some cases, if the user opens a model created bythe previous version of the MODFLOW/MOC3D PIE, the PIE will need to update the data forspecifying the transport subgrid. If this is the case, a message will notify the user that he willneed to open the Edit Project Info dialog box and close it again. The data will be automaticallyupdated when the user clicks OK after opening the Edit Project Info dialog box. Other layers,such as group layers for each geological unit may also be created at the same time. (The grouplayers provide a convenient mechanism for organizing Argus ONE layers but are not requiredfor the model to operate.)Entering Non-spatial DataNon-spatial data are entered in the Edit Project Info dialog box. The user can display itby selecting PIEsjEdit Project Info... Most of the non-spatial data are the same as in previousversions of the MODFLOW-GUI (Shapiro and others, 1997; Hornberger and Konikow, 1998).Only those portions of the Edit Project Info dialog box that have changed or are new will bedescribed here. Complete explanations of all items in the Edit Project Info dialog box areincluded in the online help.Changes to Existing FeaturesOverall AppearanceThe tabs in the Edit Project Info dialog box now appear on multiple rows and all tabscurrently in use are always visible. In the previous versions, the tabs were on a single row andthe user would sometimes need to scroll to the right or left to select another tab.The Misc. Controls tab has been removed. The data that were formerly entered in thistab are now entered on the Wetting, Geology, or Output Files tabs.The SIP, SOR, PCG, and PCG tabs have been removed. The data formerly displayedon those tabs is now displayed in the new Solvers/Other Packages tab.Geology TabOn the Geology tab (figure 1), the edit-boxes and modify button from version 2 havebeen removed. The user should now enter data directly in the table. For Simulated, InterblockTransmissivity, Aquifer Type, Specify T, Specify Vcont and Specify spl select a cell and thenclick in it or press the Enter key on the keyboard to display a list of choices. For the othercolumns, just select the cell and type the data. A new button, Add can be used to add a newgeologic unit to the end of the list of geologic units. The GUI now supports LAYCON = 2 in theBlock-Centered-Flow package (convertible layers with constant transmissivity). You can resizethe columns on this or other tables. To ensure that the title of a column is always legibleregardless of the size of a column, the title of the column over which the mouse is positioned willbe displayed in the status bar at the bottom of the dialog box.On the Geology Tab, IAPART is now automatically set to the correct value and disabledif the Interblock Transmissivity is set to Arithmetic & Logarithmic in any geological unit.IAPART was formerly on the Misc. Controls tab.h MODFLOW DalaSelsRHS occupy same space (0) Jj^^l^ilFigure 1. Revised Appearance of the Geology Tab.Stresses 1 TabThe Stresses/Solvers tab has been replaced by three new tabs Stresses 1, Stresses 2, andSolvers/Other Packages. The choice of solvers has been moved to the Solvers/OtherPackages tab. The check box for selecting MOC3D and the radio buttons for selecting theMOC3D solver have been moved to the MOC3D tab.Output Files TabOn the Output Files Tab, CHTOCH is automatically set to the proper value if theMOC3D checkbox on the MOC3D tab is checked. The control is also disabled if the MOC3Dcheckbox is checked so that it can not be changed to an incorrect value. CHTOCH wasformerly set with a combo-box. It is now set with a check-box. The root name is now limited toeight characters and will be converted to lower case. The latter facilitates using the MODFLOWinput files on computers with UNIX operating systems. The eight-character limitation isimposed because the current version of MODFLOW-96 for the DOS operating systemdistributed by the USGS does not support long file names. Combo boxes have been added toallow the user to specify the format in which to print heads and drawdowns.Time TabOn the Time tab (figure 2), the edit-boxes and Modify button have been removed. Theuser now enters data directly into the table. A new Add button can be used to add a new stressperiod to the end of the list of stress periods. The user now can change the number of stressperiods by entering a number in the Number of stress periods edit-box. The change takes effectas soon as the user clicks outside the edit-box. A new field has been added to the table. Itdisplays the length of the first time step in the stress period. This number can not be editeddirectly. Instead it is calculated based on the length of the stress period, the number of time stepsand the time step multiplier. It is displayed as a convenience to the user but is not exported tothe MODFLOW input files.H MODFLOW Data SetsFigure 2. Revised Appearance of the Time Tab.Severs/Other Packages TabOn the new Sovers/Other Packages tab, the IPCGCD parameter of the PCG2 packagehas been replaced by DAMP. DAMP replaces IPCGCD in the most recent version of the PCG2solver. In setting data for the SIP solver, it is now only possible to specify WSEED if IPCALCis set to 0. This is because MODFLOW will only use WSEED if IPCALC is set to 0.MOC3D TabThe Transport Subgrid tab has been renamed the MOC3D tab (figure 3). On theMOC3D tab, the user no longer specifies the rows and columns in the transport subgrid. This isnow done on the information layer named MOC3D Transport Subgrid. In addition the Helpbutton next to INCRCH has been eliminated. The help for INCRCH has been incorporated intothe new context-sensitive help for the PIE. The check box for selecting MOC3D and the radiobuttons for selecting the MOC3D solver have been moved from the Stresses/Solvers tab to theMOC3D tab.Eg MODFLOW Data SetsI^^^I^^Jffiifpa^^il^'l^t^A^iH | lElliBD^ffFigure 3. Revised Appearance of the MOC3D Tab (formerly Transport SubgridTab).MOC3D Particles TabThe Particles tab has been renamed the MOC3D Particles tab (figure 4). On it, thethree help buttons have been eliminated. The help that they formerly provided has beenincorporated into the new context-sensitive help for the PIE. The edit fields and Modify buttonhave also been eliminated. Instead, enter values directly into the table.B MODFLOW Data Sets^^a^^Optlgtts^ ]; MOC3D:{5i^C^XlMife3iJbo^Be-$5J:ftlntf ":| :;iJi%uJ#aesifs^y^M^-MfeBic^Maximum Sact»m efceB tosSskns p«r movjO.5|0.051(FZHd)(HFTPNC)Position in RawL_Position in CohatmFigure 4. Revised Appearance of the MOC3D Particles Tab (formerly ParticlesTab).MOC3D Output + Dipsersivities TabA pair of radio buttons has been added to the MOC3D Output + Dipsersivities tab toallow the user to choose to the format in which in which concentration will be printed in if theconcentrations are printed in a separate output file (file type CNCA).New FeaturesContext-sensitive helpContext-sensitive help (figure 5) is available for the major dialog boxes created by theMODFLOW-GUI. These include the Edit Project Info, Run MODFLOW, MODFLOW PostProcessing, and Display Horizontal Flow Barriers dialog boxes. To access the help on any ofthese dialog boxes, click on the Help button on the dialog box or click on a control (combo-box,check-box, etc.). Then press the Fl key. Another way to access the help is to click on thequestion-mark icon in the upper right corner of the dialog box and then click on a control such asa check box.10Adding Geologic UnitsGeology TabTo add a geologic unit, move the cursor to the table listingthe geologic units and select a row by clicking on it.Clicking the Insert button adds a geologic unit above thehighlighted geologic unit. Attributes associated with theselected geologic unit are copied to the new geologic unit.The geologic units are then renumbered to reflect theaddition of the new geologic unit.Clicking the Add button adds a geologic unit at the end ofthe list of geologic units. Attributes associated with the lastgeologic unit are copied to the new geologic unit.Figure 5. Example of context-sensitive help.Help is also available for all the layers and parameters created by the PIE although thishelp is not context-sensitive. To access the help file, select PIEs|MODFLOW Help. It ispossible to access the MODFLOW help without starting a MODFLOW project.Deactivating Packages without Deleting the Data for the Package.If the Use checkbox next to the check box for a package is not checked, the layers andparameters for that package will be retained in the Argus ONE project but the package will notbe used in the model. You can check on uncheck these checkboxes to enable or disable apackage without deleting the information you have entered for those packages.Specifying Transmissivity, Vertical Conductance, and Confined Storage Coefficient.The geology data table on the Geology tab has three new columns labeled Specify T,Specify Vcont, and Specify sfl (figure 6). It may be necessary to resize the Edit Project InfoDialog box or to use the scroll bar under the Geology data table to see these new columns. Theseare used to decide whether to specify transmissivity, vertical conductance, and the confinedstorage coefficient respectively. If the user selects a cell in any of these three columns, a drop-down menu will appear. Select Yes to specify any of the three parameters directly. Select No tocalculate these parameters from other parameters. If the user selects Yes, the appropriateinformation layers and parameters will be created.11H MQDFLQW Data SetsI'letesal-fUpgrStoeages ;] BUFF, RHS occupy same space (0)rFigure 6. Geology tabs with columns used to choose whether to specifyTransmissivity (Specify T), Vertical Conductivity (Specify Vcont), and ConfinedStorage Coefficient (Specify sf1).Saving Default ValuesFiles with the extension ".val" are text files that are used to set defaults for all options inthe Edit Project Info dialog box. If the user clicks the Save Val File button on the AdvancedOptions tab and accept the default file name and location, a ".val" file will be created that willbe used for all new MODFLOW projects. The default file name is "modflow.val". The defaultlocation is the directory in which the MODFLOW-GUI is installed. The ".val" file will save allthe information in the Edit Project Info dialog box. If the user saves it with a different filename or location, a ".val" file will be created that can be opened later by clicking the Open ValFile button. Opening a ".val" file will cause the options specified in the ".val" file to override allthe data in the Edit Project Info dialog box.Files with the extension ".val" files created for versions 1 and 2 of the MODFLOW-GUIare not used by the current version of the MODFLOW-GUI. Users who have not edited the"modflow.val" file to specify default values, should delete the modflow.val file. Users who haveedited the modflow.val file, should replace it with a new version created in the method describedabove. If an old version of a ".val" file is read by the MODFLOW-GUI, a warning message willbe displayed.12Specifying Initial Head FormulaThe combo-box labeled Method for assigning the EBOUND parameter and prescribedheads in the initial head MODFLOW FD Grid parameter on the Advanced Options tab givesthree choices for how initial head will be determined:Method from MF-GUI versions 1 and 2Average Points and Open ContoursUse Point Contours FirstThese options affect how prescribed head boundaries will be treated especially when opencontours or point contours are used. For Method from MF-GUI versions 1 and 2, the initialhead in a cell containing a contour on the Prescribed Head Unit[i] layer will be interpolated fromall the contours on the layer. This was the method used in versions 1 and 2 of the MODFLOW-GUI. For Average Points and Open Contours, any cells that have both point and opencontours on the Prescribed Head Unit[i] layer will be assigned the average of the point andopen contours on that layer. Locations inside closed contours will have the value of that contourunless the cell also contains a point or open contour. For Use Point Contours First, any cellsthat have both point and open contours on the Prescribed Head Unit[i] layer will be assignedthe average of the point contours on that layer. If the cell contains no point contours but doescontain an open contour, it will be assigned the average of the open contours on that layer.Locations inside closed contours will have the value of that contour.These options also affect which cells are inactive. If Method from MF-GUI versions 1and 2 is selected, all cells whose centers are outside the domain outline will be inactive. For theother choices, any cell on the domain outline will be either an active cell or a prescribed headcell even if its center is outside the domain outline.Use Binary Head File for Initial HeadsIf the Use MODFLOW binary head file as source of initial heads checkbox ischecked, MODFLOW will read the initial heads directly from the file specified in the File Nameedit box rather than from values entered in the GUI. This affects the heads at all cells includingthe prescribed head cells. Any changes in the grid will make this method invalid.Using Alternative Export TemplatesIf the Use alternate River package export template, Use alternate Drain package exporttemplate, or Use Alternate GHB package export template check box is checked an alternativeexport template is used for the River Drain, or General-Head Boundary package. Thisalternative template allows you to set the value of all parameters in the river layers usingexpressions.On the Line River Unit[i], Line Drain Unit[i], or Line GHB Unit[i], layers, there willbe one boundary created in each cell in which there is an open contour. The bottom and stagestress will be evaluated at the block center. The conductance exported to MODFLOW will bethe conductance parameter evaluated at the cell center multiplied by the lengths of all thecontours in the block.On the Area River Unit[i], Area Drain Unit[i], or Area GHB Unit[i] layers, there willbe one boundary created in each cell in which the conductance parameter is a number (ratherthan $N/A) at the block center. The bottom and stage stress will be evaluated at the block center.The conductance exported to MODFLOW will be the conductance parameter evaluated at thecell center multiplied by the area of the block.13Explicitly specify recharge or evapotranspiration layerIf the Explicitly specify recharge layer or Explicitly specify evapotranspiration layercheck box is checked, parameters will be added to the Recharge or Evapotranspiration layerthat can be used to specify the MODFLOW layer to which recharge or evapotranspiration willapply instead of calculating the layer from the Elevation parameter.Stream PackageThree additional MODFLOW Packages have been added to the interface; the StreamPackage (Prudic, 1989), the Horizontal-Flow Barrier Package (Hsieh and Freckleton, 1993), andthe Flow and Head Boundary Package (Leake and Lilly, 1997). To activate the stream package,go to the Stresses 2 tab (figure 7) in the Edit Project Info dialog box and check the STR check­box. This will activate the other stream-related controls on the Stresses 2 tab. If the userattempts to activate both the stream package and MOC3D, a warning message will be displayed.If the user selects Steady Stress for the stream package, all the variables that are specified forthe first stress period will apply to the remaining stress periods. However, there will still beparameters created for the other stress periods. This allows the user to switch between time-variable stress and steady stress without loss of information. If the user chooses to calculateflow, specify both the length and time units for the model. The length units are specified on theStresses 2 tab. The time units are specified on the Time tab. If the user does not specify thetime units, a warning message will appear when the Edit Project Info dialog box is closed or theinput files for MODFLOW are exported. The user can choose whether or not to simulate streamtributaries and diversions. Depending on the choices made, parameters related to tributaries,diversions, and calculating flow will be created on the Stream Unit[i] information layers whenthe Edit Project Info dialog box is closed. See Prudic (1989) for more information about theStream package.14Figure 7. Stresses 2 tab used for selecting the Stream Package and Flow andHead Boundary Packages.Flow and Head Boundary PackageTo activate the Flow and Head Boundary package, change to the Stresses 2 tab (figure 7)of the Edit Project Info dialog box and select the Flow and Head Boundary check-box. Thiswill activate some or all of the other controls related to the Flow and Head Boundary package.The controls that are activated depend on the current set-up of the model. In all cases, the usercan set the number of Flow and Head Boundary times. This will change the number of Flowand Head Boundary times that can be edited. The first such time must always be zero. It can notbe edited. All subsequent times must be larger than or equal to their predecessors. If invalidtimes are specified, a warning message will appear when the Edit Project Info dialog box isclosed. The steady-state option for Flow and Head boundaries is only available for steady-statemodels with multiple stress periods. Weighting factor for concentration at specified flux celland Weighting factor for concentration at specified head cell will only be available formodels in which MOC3D is selected. More information about the Flow and Head BoundaryPackage is in Leake and Lilly (1997).Horizontal-Flow Barrier PackageTo activate the Horizontal-Flow Barrier package, change to the Solvers/Other Packagestab (figure 8) of the Edit Project Info dialog box and select the Horizontal-Flow Barriercheck-box. There are no time-dependent parameters for the Horizontal-Flow Barrier package so15there is no steady state option. See Hsieh and Freckleton (1993) for more information about theHorizontal-Flow Barrier package.20NEBDOT.'%( "liojeel ;j| Geotegy j17 UseFigure 8. Solvers/Other Packages Tab.MODPATHTo activate MODPATH, change to the MODPATH tab (figure 9) and select theMODPATH check-box. A new tab will appear labeled MODPATH Options (figure 10). Inaddition, if the user selects Compute locations at specific points in time and specify timesindividually on the MODPATH Options tab, another new tab will appear labeled MODPATHTimes (figure 11). The descriptions for the MODPATH options below are largely quoted orparaphrased from those in the MODPATH 3.0 manual (Pollock, 1994).16H MDDFLOW Data Setsevapotranspirations is assigned to top face (1)Figures. MODPATH Tab.If the Use COMPACT Option check-box box is checked, MODPATH will generateendpoint, pathline, or time series files as text files using the global node number to indicate celllocation. If it isnY checked, the cell locations will be designated using the row-column-layer gridindices (as in previous versions of MODPATH).If the Use BINARY Option check-box is checked, endpoint, pathline, and time seriesfiles will be generated by MODPATH in binary form. If the BINARY option is used, it will alsoneed to be used with MODPATH-PLOT to correctly read binary versions of these files. TheMODFLOW-GUI does not read binary MODPATH output files so this option should not be usedif the user intends to use the MODFLOW-GUI to display MODPATH results.The Maximum Number of Release Times edit-box controls the maximum number ofrelease times that can be specified for any object on MODPATH Particles Unit[i] layers.MAXSIZ is the maximum allowed size (in bytes) of the Composite Budget File. If MAXSIZ =0, the program uses a default value that is set in the MODPATH main program.NPART is the maximum number of particles allowed for a MODPATH run. If NPARTis set equal to 0, MODPATH automatically resets NPART to a default value that is defined inthe MODPATH main program.TBEGIN is the time value assigned to the beginning of the MODFLOW simulation.Any convenient value may be specified, including values less than zero.BeginPeriod, BeginStep, EndPeriod, and EndStep specify the beginning and endingstress period and time-step numbers that will be processed by MODPATH. The interface willnot allow the user to specify values that are beyond the range specified in the model.17The Recharge ITOP parameter indicates whether the recharge is assigned to the top faceof the cell. If ITOP = 0, recharge is treated as an internal source. If ITOP = 1, recharge isassigned as a vertical component of flow to the top face.The Evapotranspiration ITOP parameter indicates whether the evapotranspiration isassigned to the top face of the cell. If ITOP = 0, evapotranspiration is treated as an internal sink.If ITOP = 1, evapotranspiration is assigned as a vertical component of flow to the top face.a MODFLOW Data SetsStresses! | 5 S) MQBPATHFioject j GeolbgjrOutput Files | Advanced Options* 4 *strcssjenodandtnne step jrjCompute bostons atin tine' (Constant time interval (1)Time.iatervBlJFonvard in the direction of flow (1) jj sjPass thrcragh weak sink cells (1)UHS! of ftactbnpfItewFigure 10. MODPATH Options Tab.In steady-state models, the user can stop computing paths after a specified time, bychecking the Stop computing paths after a specified time check-box. The user will then beable to enter the stopping time in the Time to stop computing paths check-box. In transientmodels, the user can stop computing paths after a specified time is reached by checking the Stopcomputing paths after a specified value of tracking time check-box. The user will then beable to enter a time in the Maximum tracking time edit-box.The reference time for releasing particles is the time from which all other times aremeasured. It need not be the starting time of the model (although that is the default). The usermay enter the reference time using either stress period, time step and relative time within atime step or the user can specify the reference time directly as measured from the beginning ofthe model. This option is only available for transient models.Use the Output mode combo-box to select the type of data generated by MODPATH.The type of data can be one of the following: End points (1): (initial and final locations of18particles.), Pathlines (2): (locations are recorded where a particle crosses a cell boundary, at theend of each time step and at user-specified times.), or Time Series (3): (locations are recorded atuser-specified times.)If the user wishes to specify times at which MODPATH will generate output, check theCompute locations at specific points in time check-box and the Method of specifying timesfor output combo-box will become enabled. The user can choose this option only if the Outputmode is Pathlines.If the user checks the Stop particles if they enter a specific zone check-box, the Zonein which particles will stop edit-box will become enabled allowing the user to specify whichzone particles will stop in. If the user chooses to have only endpoints in the output and choosesto have particles stop in a specific zone, the user can also decide whether to have Recordendpoints for all particles or Record endpoints only for particles in a specific zone.A weak sink is a cell that contains a boundary condition that removes water from themodel but which also allows some water to flow to one or more adjacent active cells. BecauseMODFLOW does not define the precise location of sinks within cells, it is impossible forMODPATH to unambiguously determine whether a particle that enters a weak sink should beremoved from the model or should enter an adjacent active cell. The user must decide what isthe best option. MODPATH gives three choices; particles pass through weak sink cells,particles stop at weak sink cells, or particles can stop at weak sink cells that exceed aspecified strength. If the treatment of particles that enter weak sinks is to Stop at weak sinkcells that exceed a specified strength, specify the fraction of the flow discharged that willcause particles to stop. For example, if 70 per cent of the water that enters a cell is dischargedthrough a well and the user specifies a fraction of 0.5 (50 per cent) then any particles entering thecell will be stopped. However, if only 30 per cent of the water entering the cell was dischargedthrough the well, particles entering the cell would not stop at the cell but instead would be free toflow into adjacent cells.The Compute volumetric budgets for all cells, Check data cell by cell, andSummarize final status of particles in summary.pth file check-boxes cause MODPATH toperform those functions. In the case of the volumetric budget, you must also specify apercentage Error tolerance in the Error tolerance (%) edit-box.19MODFLOW Data SetsFigure 11. MODPATH Times Tab.Depending on the Output mode, the user may have a choice about whether to computelocations at specific points in time. To specify output at specific points in time, the user musteither specify a time interval for output or specify the times individually. In the latter case, theMODPATH Times tab (figure 11) will become visible and the user will be able to specify thenumber of times at which output from MODPATH is desired (Nvalues) and the times atwhich data will be generated (Modpath Time (Tvalue)). For more information aboutMODPATH, see Pollock (1994).ZONEBDGTIf the ZONEBDGT check-box is checked on the ZONEBDGT tab (figure 12),information layers for ZONEBDGT will be created and options relating to ZONEBDGT in theEdit Project Info dialog box will become enabled.20H MODFLOW Data SetsStresses Ls'|ZONEBDGT TitleoFigure 12. ZONEBDGTTab.ZONEBDGT Title is the title that will be printed on the ZONEBDGT output.To use composite zones in ZONEBDGT, set Number of ZONEBDGT composite zonesto a number greater than 0 and then enter the zone numbers in the ZONEBDGT CompositeZones table. The zones must match the primary zones in the ZONEBDGT information layers.The user may generate budgets for all times for which cell-by-cell flows are saved or specify upto ten times at which budgets will be generated. To do the latter, the user must enter the stressperiods and time steps in the ZONEBDGT Specified output times table.Entering Spatial DataTo provide an interface for the additional MODFLOW packages as well as MODPATHand ZONEBDGT, several new parameters and information layers have been added. Other layersand parameters have been renamed to better reflect their function. Finally, a new method ofimporting well data has been added. These changes are described here.Renamed Layers and ParametersThe MODFLOW Grid Density layer has been renamed the MODFLOW GridRefinement layer to better reflect what the layer controls. The Density parameters on that layerand the MODFLOW Domain Outline layer have both been renamed to MODFLOW GridRefinement and MODFLOW Cell Size respectively. The Maps Unitl layer has been renamedthe Maps layer because it is not associated with a specific geologic unit. On Line River Unit[i]21and Area River Unit[i] layers, the Bottom parameter has been renamed Bottom Elevation forgreater clarity. When opening files created by previous versions of the MODFLOW GUI, theselayers and parameters are automatically changed to their new names. If any layers or parametersare renamed while opening a file, a dialog box will appear that informs the user about therenamed layers or parameters. In some cases, users may need to update expressions that theyhave created to reflect the new names.Locked Recharge Elevation parameterThe Elevation parameter on the Recharge layer now has the Dont Override, Dont EvalColor, and Lock Def Val parameter locks set when that parameter is not used. The parameter isused only if recharge option (NRCHOP) on the Stress 1 tab of the Edit Project Info dialog boxis set to Vert distribution in IRCH (2). This prevents users from entering data for thisparameter unless the data will be used.Importing Well DataThe MODFLOW GUI has a special mechanism for importing Well data. To import thewell data do the following.1. Select PIEs|Import Wells.2. Enter the correct geologic unit in the edit box labeled "Geologic Unit" or click the"Use Multiple Units" checkbox. (If the "Use Multiple Units" checkbox is checked, the usermust specify the geologic unit for each well individually.)3. A dialog box will appear with a table with spaces for all the data defining the well.You may type the required information into the table. However, it is usually easier to import thedata from a spreadsheet or from a tab-delimited text file.To import the data from a spreadsheet, arrange the spreadsheet so that it has all the samedata shown in the table headers and in the same order. Then select the block of data that youwish to import and copy it to the clipboard. Make Argus ONE active and click on the Pastefrom clipboard button. The data will be pasted from the clipboard.To import the data from a tab-delimited text file, make a file containing the data. Anyline that begins with a # will be treated as a comment and ignored. Every other line must containdata for a single well. The data for each well must be in the same order as shown in the WellData table. Each item in the line must be separated from the next item by a single tab character.Then click on the Read from file button and select the file from which you wish to read data.You don\ need to set the number of wells before pasting data into the table or reading itfrom a file; the number of wells will be set automatically when the data is read.The data to be imported may be delimited by tab-characters or by commas, spaces, andtab-characters. If the latter option is used, the well name either must not include any spaces, tabsor commas or it must be enclosed in single or double quotation marks. For example, "A WellName" and 'A Well Name'would both be acceptable. If you copied data to the clipboard from aspreadsheet and wish to paste it into the Well Data table, use the tab-delimited format.4. Click on the OK button and the data will be imported into the correct Wells Unit[i]layer or layers.MOC3D Transport SubgridThe MOC3D subgrid boundary is now specified using an information layer namedMOC3D Transport Subgrid. If there are no contours on the MOC3D Transport Subgrid22layer, the MOC3D Subgrid will encompass the entire grid. If there are contours on the MOC3DTransport Subgrid layer, the location of each vertex of each contour on the layer will becompared to the row and column locations. The subgrid will extend from the lowest row andcolumn adjacent to any vertex to the highest row and column adjacent to any vertex. The valueassigned to the parameter on the MOC3D Transport Subgrid layer has no effect. The transportsubgrid can be visualized with a new parameter on the MODFLOW FD Grid layer namedSubgrid Boundary. (Previously there were separate parameters for each geologic unit namedSubgrid Boundary[i].)IFACEfi]On a number of layers, there will now be an IFACE[i] parameter added if MODPATHis selected. The layers on which this parameter is present include Wells Unit[i], Line RiverUnit[iJ, Area River UnitfiJ, Line Drain Unit[i], Area Drain UnitfiJ, Point Gen HeadBoundary Unit[i], Line Gen Head UnitfiJ, Area Gen Head UnitfiJ, and Stream UnitfiJ.IF ACE [i] is used to specify how MODPATH will treat the flow to or from a cell for stressperiod i. However, if steady stress has been chosen for the relevant package in the Edit ProjectInfo dialog box, only IF ACE 1 will be used for the entire duration of the model. The otherIFACE[i] parameters will be ignored. If IF ACE [i] is from 1 to 6, the flow is assigned to a cellface according to the diagram below. If IFACE[i] < 0, the source/sink flow term is distributeduniformly across any of the faces 1 through 4 that form boundaries with inactive cells. IfIFACE[i] = 0 or IFACE[i] > 6, the flow is treated as an internal source. If IFACE[i] is from 1to 6, the flow is assigned to a cell face according to the figure 13.Figure 13. Interpretation of IFACE[i] = 1 to 6.MODPATH information layersIn addition to the IF ACE parameter, two new information layers will be added for eachgeologic unit when MODPATH is selected: MODPATH Zone Unit[i], and MODPATH23Particles Unit[i]. The Porosity Unit[i] layers will also be created if MODPATH is selected.This layer is also used with MOC3D.MODPATH Zone Unit[i] represents the zone code used by MODPATH-PLOT todetermine the color of pathlines and particle points. MODPATH requires that the zone code liebetween 1 and 999 inclusive. Under rare circumstances the user may wish to override the defaultvalue of MODPATH Zone Unit[i]. If so the user must first unlock the default value. See theArgus ONE documentation for version 4.10m for how to unlock parameter values.MODPATH Zone Unit[i] is multiplied by MODFLOW FD Grid.IBOUND Unit[i] todetermine the value exported to MODPATH.MODPATH Particles Unit[i] contains several parameters that determine where within acell particles are created. If IF ACE < 0, the particles are distributed uniformly across all of thefaces 1 through 4. If IF ACE = 0, the particles are placed within the cell. If IFACE is from 1 to6, the particles are assigned to a cell face according to figure 13. X Particle Count, Y ParticleCount, and Z Particle Count set the number of particles within or on the face of a cell in the X,Y, and Z directions respectively. For example, if X Particle Count = 2, Y Particle Count = 3,and IFACE = 6 there would be 2 x 3 = 6 particles on the top face of the cell. Release Time[i] isa release time for the particles specified by the contour. The release time is measured relative tothe reference time specified for MODPATH.ZONEBDGTOne layer for each geologic unit is created for ZONEBDGT: ZONDBDGT Unit[i]. Itssingle parameter is Primary Zone. ZONDBDGT Unit[i] layers are used to enter zones forwhich water budgets will be determined. Zone numbers may range from 1 to 25.Stream PackageOne layer for each geologic unit is used to enter data for the stream package: StreamUnit[i]. Streams are drawn on this layer using open contours. Stream direction is determined bythe order in which the user draws the contour representing the stream. The place where the userbegins drawing the contour is the upstream end. The last vertex in the contour is at thedownstream end. For contours with 3 or more vertices, the upstream end can be determined bythe position of the label on the contour. The label is between the first and second vertices and isthus at the upstream end of the contour. If there are only two vertices, copy the contour to theclipboard and paste it in a text editor. Look at the coordinates of each vertex to determine whichend is which. The upstream end will be the first vertex. The EditContours PIE (see Appendix 1)can be used to reverse the order of the vertices in a contour.Each open contour on a Stream Unit[i] layer represents a stream segment. SegmentNumber must be a unique, positive integer to identify each open contour. Any segment whichreceives flow from another segment must have a higher segment number than the segment fromwhich it receives flow.The GUI renumbers segments in consecutive order as required by the Stream packageduring the export process. A segment can not branch nor can two contours have the samesegment number. Where a stream branches, a new segment must begin. The branches can eitherbe tributaries or diversions. Two or more tributaries can join to form a new segment or asegment can split into one or more diversionary segments and a mainstem. The mainstem isdesignated using Downstream Segment Number. Listing the upstream segment as its source inUpstream Diversion Segment Number designates the diversion.24Downstream Segment Number is the segment number of a stream segment that receivesflow from the current segment. This is illustrated in figure 14 where three segments (shown ingreen) all have a Downstream Segment Number of 201. The Segment Number of theremaining segment (shown in black) is 201 so it receives flow from the other three segments. Upto ten segments can join together to contribute flow to a single downstream segment. The flowfrom the current segment will be routed to the downstream segment. The Flow[i] in thedownstream segment should be set to -1. The number of a downstream segment must always belarger than the number of the segment from which it receives flow. If no segment is downstreamof the current segment, leave Downstream Segment Number equal to 0.Figure 14. Illustration of the linkage among stream segments.Upstream Diversion Segment Number is the segment number of a stream segmentfrom which flow is diverted into the current segment. The segment number of the segment fromwhich flow is diverted must always be less than the segment number of the segment that receivesthe diverted flow. If the current segment does not divert flow from another segment, leaveUpstream Diversion Segment Number set to 0.Flow[i] is the streamflow into the upstream end of the current segment in stressperiodji]. However, if steady stress has been chosen for the stream package in the Edit ProjectInfo dialog box, only Flowl will be used for the entire duration of the model. Other Flow[i]parameters will be ignored. In general, whenever there is a time-related parameter, only the firstparameter will be used if steady stress has been chosen. If the flow in the segment will be thesum of the flows from its tributaries, set Flow[i] to -1. If the segment is a diversion, the value ofFlow[i] is the amount that will be diverted.Upstream Stage fi] is the stream stage at the upstream end of the current segment instress period[i]. If Downstream Stage[i] is $N/A, Upstream Stage fi] will be the stage for theentire length of the segment. If Downstream Stage [i] is not $N/A, the stage at each cell will be25determined by linear interpolation along the open contour from the upstream end to thedownstream end. In general, whenever there is both an "upstream" and "downstream"parameter, setting the "downstream" parameter to $N/A will cause the "downstream" parameterto be ignored. When Argus ONE uses an expression to set the value of a parameter for acontour, it always evaluates that expression at the same spot: the location of the first vertex.Thus an expression for a "downstream" parameter is evaluated at the upstream end. The currentversion of Argus ONE doesn't have any way of recognizing that a particular parameter should beevaluated anywhere other than the default location.Streambed hydraulic conductivity is the hydraulic conductivity of the streambedmaterial. Streambed hydraulic conductivity has units of (length/time). In the Stream package,"Cond" is the streambed hydraulic conductance. It is equal to KLW/M whereK = the hydraulic conductivity of the streambed material, (units = Length/time)L = the length of the reach, (units = Length)W = the width of the stream (units = Length), andM = the thickness of the streambed material (units = Length).The MODFLOW-GUI measures the length of each open contour in a cell and multipliesthe length by Streambed hydraulic conductivity, and Width [i], and divides by the streambedthickness to determine "Cond". The streambed thickness is determined from the parametersUpstream bottom elevationfi], Upstream top elevationfi], Downstream bottom elevationfi],Downstream top elevation [i].Upstream bottom elevation[i] is the elevation of the bottom of the streambed at theupstream end of the current segment in stress period[i].Upstream top elevation [i] is the elevation of the top of the streambed at the upstreamend of the current segment in stress period[i].Upstream Width [i] is the channel width at the upstream end of the current segment inStress Period[i]. Upstream Width [i] has units of length.Slope[i] is the channel slope in stress period[i]. Slope[i] has units of length/length(dimensionless). Slope is used in calculating the stage of the river from the discharge.Mannings roughness [i] is the Manning's roughness coefficient in stress period[i].Manning's roughness is used in calculating the stage of the river from the discharge. Tables ofManning's roughness coefficient are present in most introductory surface-water-hydrologytextbooks.Flow and Head Boundary PackageThe Point FHB Unit[i] layers are used to define Flow and Head boundaries with pointcontours. Only point contours should be used on Point FHB Unit[i] layers. The Line FHBUnit[i] layers are used to define Flow and Head boundaries with open contours. Only opencontours should be used on Line FHB Unit[i] layers. The Area FHB Unit[i] layers are used todefine Flow and Head boundaries with closed contours. Only closed contours should be used onArea FHB Unit[i] layers.The Top Elev and Bottom Elev parameters on the Point FHB Unit[i] and Line FHBUnit[i] layers are compared with Elev Top Unit[i], Elev Bot Unit[i] and the verticaldiscretization of a unit to determine in which layer or layers a flow or head boundary shouldoccur within the geologic unit. If the top and bottom elevation of the Flow and head boundaryare outside the unit as specified in Elev Top Unit[i] and Elev Bot Unit[i] the boundary will be26placed in either the uppermost or lowermost layer in the unit. For flow boundaries that will besplit among several layers the flow will also be divided among those layers.Head Time[i] on the Point FHB Unit[i] and Area FHB Unit[i] layers is the specifiedhead at Time i. The "Time i" values are specified on the Stresses 2 Tab. Values at all timesother than the specified times will be determined by linear interpolation among the specifiedtimes. (See Leake and Lilly, 1997.) If Head Time[i] is left at the default value of $N/A, thecontour represents a flux boundary rather than a head boundary. In the Area FHB Unit[i] layer,the head boundaries will be assigned to every layer within the geologic unit. MODFLOW doesnot allow both a specified flux and a specified head boundary at a single cell. If both arespecified for a single cell, the specified flux boundary will be ignored.Flux Time[i] on the Point FHB Unit[i] layers is the specified flux rate at Time i. The"Time i" values are specified on the Stresses 2 tab of the Edit Project Info dialog box. Thetotal flux for a time step will be determined by taking the integral of the flux rate versus timefunction for the time step. (See Leake and Lilly, 1997.) If Flux Time[i] is left at the defaultvalue of $N/A, the contour represents a specified head boundary rather than a specified fluxboundary.Head Concentration Time[i] on the Point FHB Unit[i], Line FHB Unit[i], and Area FHBUnit[i] layers is the solute concentration at the specified head cell at Time i. Flux ConcentrationTime[i] on the Point FHB Unit[i], Line FHB Unit[i], and Area FHB Unit[i] layers is the soluteconcentration at the specified flux cell at Time i. For both types of boundaries, values at alltimes other than the specified times will be determined by linear interpolation among thespecified times.Start_Line Head Time[i] on the Line FHB Unit[i] layers is the specified head at thestart of an open contour at Time i. Values at all times other than the specified times will bedetermined by linear interpolation among the specified times. If Start_Line Head Time[i] isleft at the default value of $N/A, the contour represents a flux boundary rather than a headboundary. If Start_Line Head Time[i] is a number but End_Line Head Time[i] is $N/A, Thevalue of StartJLine Head Time[i] will be used all along the contour. If both Start_Line HeadTime[i] and End_Line Head Time[i] are numbers, the starting head at intermediate cells will bedetermined by linear interpolation between Start_Line Head Time[i] and End_Line HeadTime[i]. The direction of a contour can be determined by the methods described under thesection entitled Stream Package.Flux per Length Time[i] on the Line FHB Unit[i] layers and the Flux per AreaTime[i] on the Area FHB Unit[i] layers are the specified flux rate per unit length at Time i.The Flux per Length Time[i] will be multiplied by the length of the contour within a cell todetermine the total flux rate for that cell. The Flux per Area Time[i] will be multiplied by thearea of the contour within a cell to determine the total flux rate for that cell. The total flux for aparticular time step will be determined by taking the integral of the flux rate versus time functionfor the time step. If Flux per Length Time[i] or Flux per Area Time[i] are left at the defaultvalue of $N/A, the contour represents a specified head boundary rather than a specified fluxboundary. In the Area FHB Unit[i] layer, the flux boundaries will be assigned to every layerwithin the geologic unit. The flux will be divided among the layers.27Horizontal Flow Barrier PackageTo define horizontal flow barriers use open or closed contours on the Horizontal FlowBarrier Unit[i] layers. These layers have two parameters: Barrier Hydraulic Conductivityand Barrier Thickness.Barrier Hydraulic Conductivity represents the hydraulic conductivity of the horizontalflow barrier. Barrier Thickness represents the thickness of the horizontal flow barrier. BarrierHydraulic Conductivity is divided by the Barrier Thickness to obtain the hydrauliccharacteristic of the conceptual model. The hydraulic characteristic of the conceptual model isthen adjusted by the angle of the barrier to obtain the hydraulic characteristic of the numericalmodel.To visualize the location of the horizontal flow barriers in the numerical model, selectPIEsjDisplay Horizontal Flow Barriers. This will display a dialog box in which the horizontalflow barriers can be displayed. Enter the unit number in the Unit Number edit-box and click onthe Display button to display the horizontal flow barriers for that unit. If there are barriers on theselected unit, they will be displayed. If not, a warning message will appear. The grid is shownin this dialog box without any rotation. Use the check-boxes in the dialog box to indicate thecorrect coordinate direction. At present there is no zooming capability on this dialog box but itcan be resized to make the grid larger. Click on the Close button to close this dialog box.The GUI must adjust the hydraulic characteristic exported to MODFLOW based on thegrid angle because the length of the flow barriers differs between the conceptual and numericalmodels. For example, the only difference between the two models in figure 15 is that in one thearea surrounded by the horizontal-flow barrier is rotated 36 degrees. However, when the modelswere run, the leakage through the flow barrier in model 2 was much higher than it was in model1.Horizontal Flow Barriers\Model 1 Model 2Figure 15. Two models that differ only in the orientation of the area surroundedby a horizontal-flow barrier.A close-up of Model 2 reveals the problem (figure 16). In MODFLOW it is impossibleto specify a flow barrier that is at an angle to the grid. Instead a zigzag line of flow barriersalong the cell boundaries must approximate the actual flow barrier. The total length of the flowbarriers in the numerical model is longer than the angled flow barrier they represent in the28conceptual model. Thus, there is more area through which flow could occur in the numericalmodel than in the conceptual model...........Figure 16. Close up of a section of the horizontal-flow barrier in model 2.To compensate for the excessive flow barrier length in the numerical model, thehydraulic characteristic of the barriers (HYDCHR) must be reduced. The method used to reducethe hydraulic conductivity in the MODFLOW-GUI is shown in figure 17.Flow barrier in conceptualmodelFlow barriers innumerical modelII <00II XUUQQHYDCHRnummod =HYDCHRcon;mod xCOSaFigure 17. Method to calculate the reduction of HYDCHR when horizontal-flow barriers are at anangle to the grid.HYDCHRnum mod = Hydraulic characteristic of numerical model.HYDCHRconc_mod = Hydraulic characteristic of conceptual model.29Running MODFLOW, MOC3D, MODPATH, or ZONEBDGTCreating Input FilesSelecting Run MODFLOW/MOC3D, Run MODPATH, or Run ZONEBDGT from thePIEs menu accesses the Run MODFLOW/MOC3D dialog box (figure 18). These menu itemsare only present if the MODFLOW FD Grid layer is the active layer. Use the radio buttons toselect which model to run and whether or not to run the model or just create the input files for themodel. For MOC3D models, users can choose to either run MODFLOW (without solutetransport) or MOC3D (with solute transport) by checking or unchecking the Run MOC3D tosimulate solute transport check-box. If the input files for a model have already been createdand the data for one or more packages have not changed since the last time the model was run,there is no need to create a new copy of that input file. Instead, the user can save time during theprocess of exporting the MODFLOW input files by not exporting a new copy of the input file forthe package. All those packages whose check-boxes are both checked and enabled will beexported to the MODFLOW input files.In some special cases, the user may elect to develop their own export template for one ormore MODFLOW Packages. In such cases, there is no need for the usual export template tocreate the input files for those packages so the user may elect not to create them with the usualexport template.The full paths to the executables should be displayed in edit-boxes on the Model Pathstab of the Run MODFLOW/MOC3D dialog box. If the executable for the chosen model is notat the location specified in the edit-box, the background of the edit-box and the status bar willchange to red and a warning message will be displayed in the status bar to indicate that the pathis incorrect (figure 18). Normally, the user should correct the path before attempting to createthe input files. Although it is possible to export the input files using an incorrect path, ArgusONE will not be able to start the model if the path is incorrect. Type the correct path or clickon the Browse button to set the correct path. When a model is saved, the paths for all of themodels will be saved in a file named modflow.ini in the directory containing the MODFLOWPIE. Modflow.ini will be read whenever a new MODFLOW project is created or an old one isread so that the model paths do not need to be reset frequently.30Run MODFLOW/MOC3Di{>&|H^^' , ...w8nuqgiW9Hips9,-Warru«g: If thfMODFLOWFD Grid layerr&t-i^gii.Figure 18. Revised Run MODFLOW/MOC3D Dialog box. In this example, MOC3Dis not installed at the location specified in the MOC3D Path edit-box so thebackground of the status bar, would appear red.If any of the non-spatial data for the model need to be edited, click the Edit Project Infobutton to show the Edit Project Info dialog box. Click on the OK button in the RunMODFLOW/MOC3D dialog box to begin exporting the input files for the selected program.Click on the Cancel button to close the Run MODFLOW/MOC3D dialog box withoutexporting input files for any program.Because MODPATH and ZONEBDGT use the output from MODFLOW (or MOC3D) aspart of their input, the user must ensure that the required output files are in the directory in whichMODPATH or ZONEBDGT will be run. Normally, this is most easily accomplished by runningMODPATH or ZONEBDGT in the same directory in which the model was run.Processing the Export TemplateWhen the user clicks on the OK button, the PIE modifies the export template(modflow.met) before passing it on to Argus ONE . When the export template has beenprocessed and passed to Argus ONE , a dialog box is displayed for selecting the directory inwhich the input files for the model should be generated. (The model will generate its output filesin this same directory.) The file name (MODFLOW_FD_Grid.exp) in the dialog box may beignored. If a file by that name already exists, Argus ONE will generate a warning messagestating that MODFLOW_FD_Grid.exp will be overwritten. This warning message may beignored. Click OK to ignore the warning message.Two progress bars will then appear. Argus ONE generates one and a PIE generates theother (figure 19). The progress bar generated by Argus ONE contains a "barbershop" progressbar. One way to abort the export process by selecting the window containing the "barbershop"progress bar and pressing Ctrl-C. A PIE generates the other progress bar. It shows how much ofthe export template has been processed by Argus ONE . It also displays warning and errorabout inconsistencies or errors in the input specified by the user. These warnings can be31suppressed by unchecking the Show Error and Warning Messages check box in the RunMODFLOW/MOC3D dialog box. prior to starting the export process. An Abort Simulationon this second progress bar and may also be used to stop the export process.Export ProgressNegative or zero unit thickness at Unit 1; Column: 109; Row: 74Negative or zero unit thickness at Unit 1; Column: 110; Row: 74Negative or zero unit thickness at Unit 1; Column: 111; Row: 74Negative or zero unit thickness at Unit 1; Column: 112; Row: 74Negative or zero unit thickness at Unit 1; Column: 113; Row: 74Negative or zero unit thickness at Unit 1; Column: 114; Row: 74Negative or zero unit thickness at Unit 1; Column: 115; Row: 74Negative or zero unit thickness at Unit 1; Column: 116; Row: 74Estimated Jkne Remanbig: 00:01:18Figure 19. PIE-Generated Progress Bar with error messages.Using the MODFLOW PIE with Calibration ProgramsThe MODFLOW PIE has been designed to allow calibration programs such as UCODE(Poeter and Hill, 1998) to use it to create MODFLOW input files and run MODFLOW. If thecheckbox labeled External Calibration Program running Argus ONE is checked, the DOSwindow in which MODFLOW runs will close as soon as MODFLOW finishes running. Inaddition, the batch file used to run MODFLOW will have a command to try to start a copy ofWaitForMe.exe (see Appendix 5). If the calibration program starts another copy ofWaitForMe.exe before exporting the MODFLOW input files, that copy will continue runninguntil the batch file attempts to start the new copy. Attempting to start a new copy will cause bothcopies to close. The calibration program can detect the closure of the first copy of WaitForMEbefore attempting to process the MODFLOW output files. The SelectChar program (seeAppendix 5) may be useful in writing a batch file that will start Argus ONE exporting theMODFLOW input files. The following is an example of such a batch file.UcodeTest.mmbd:\PROGRA~l\ARGUSI-l\ArgusPIE\GETMYD~l\SelectChar.exealt-Pd:\PROGRA~l\ARGUSI~l\ArgusPffi\GETMYD~l\SelectChar.exe M O chr-13d:\PROGRA~l\ARGUSI~l\ArgusPIE\GETMYD~l\WaitForMe.exeThis batch files makes UcodeTest the active program. If the MODFLOW FD Grid layeris the active layer, it will then activate the PIE's menu and start running MODFLOW. Finally itstarts a copy of WaitForMe which will be closed when a second copy starts after MODFLOWhas finished executing.32Another PIE, MODFLOW_ReadFileValue, is useful in defining parameters to becalibrated by the calibration program (See Appendix 4). It can be used to read the current valueof a calibration parameter from a text file and use that value to define the value of an Argus ONEparameter or contour.