README March 2, 2018 MODFLOW-GUI - Version: 4.36.0.0 2018/3/2 Preprocessor and postprocessor graphical-user interfaces for preparing MODFLOW-2005, MODFLOW-2000, MODFLOW-96, MODFLOW-GWT, MODFLOW-GWM, MOC3D, MODPATH, ZONEBDGT, MT3DMS, and SEAWAT-2000 input data and viewing model output for use within Argus Open Numerical Environments (Argus ONE) For assistance, enhancement requests, or bug reports contact the Hydrologic Analysis Software Support Team via e-mail sent to h2osoft@usgs.gov. See the file doc\mfgui.txt for descriptions, references, and additional contacts for this software. Instructions for installation and execution of this software are provided below. MODFLOW-GUI is implemented as plug-in extensions (PIEs) for use with Argus ONE version 4.2, revision w or later. Although Argus ONE runs on a variety of computing platforms, the PIEs are only available for systems running Microsoft Windows 9x, NT, ME, 2000, XE, Vistas, 7, or 8. This software has been approved for release by the U.S. Geological Survey (USGS). Although the software has been subjected to rigorous review, the USGS reserves the right to update the software as needed pursuant to further analysis and review. No warranty, expressed or implied, is made by the USGS or the U.S. Government as to the functionality of the software and related material nor shall the fact of release constitute any such warranty. Furthermore, the software is released on condition that neither the USGS nor the U.S. Government shall be held liable for any damages resulting from its authorized or unauthorized use. Also refer to the USGS Water Resources Software User Rights Notice for complete use, copyright, and distribution information. TABLE OF CONTENTS A. DISTRIBUTION FILES B. INSTALLING C. USING MODFLOW-GUI D. SAMPLE PROBLEM DATA E. COMPILING A. DISTRIBUTION FILES The following distribution files (containing the software and information files) are currently available. mfgui40_4_36.zip - Compiled using Borland Delphi 2006. mfgui40_4_36s.zip - Source code only Included in directory mfgui4.0\doc are Portable Document Format (PDF) versions 1, 2, 3, and 4 of the MODFLOW-GUI documentation (mfgui.pdf, moc3dgui.pdf, Mfgui_30.pdf, Mfgui_40.pdf). PDF files are readable and printable on various computer platforms using Acrobat Reader from Adobe. The Acrobat Reader is freely available from the following World Wide Web site: http://www.adobe.com/ B. INSTALLING The MODFLOW GUI is a plug-in extension for the program Argus ONE. Argus ONE must be installed before the MODFLOW GUI is installed. Argus ONE can be purchased from its developer Argus Interware. Demonstration versions of Argus ONE can be downloaded fromt he Argus Interware web site (http://www.argusone.com). First uninstall any previous version of the MODFLOW GUI. In particular, you should remove or delete mcpost10.dll, mfgui_20.dll, mfpost20.dll, and MFGUI_30.dll. Version 4 of the MODFLOW GUI will not function correctly if these files remain in the Argus PIE directory. You should also remove any of the following PIEs if they are installed because they conflict with and are replaced by the Utility PIE: EditContoursPie.dll, EditDataLayer.dll, GriddedImport.dll, JoinContoursPie.dll, MoreConversions.dll, EvalAtXY.dll, and RotateCells.dll. Extract the files from the MODFLOW-GUI distribution file into the existing installation of Argus ONE, specifically into the directory \Program Files\Argus Interware\ArgusPIE or \Program Files (x86)\Argus Interware\ArgusPIE, being sure to set any options necessary to restore the directory structure stored in the distribution file. Upon successful extraction of the files contained in the zip file, the following directory structure will be created under the \Program Files\Argus Interware\ArgusPIE or \Program Files (x86)\Argus Interware\ArgusPIE directory (the contents of each directory are shown to the right): BlockList ; BlockList plug-in extension GetMyDirectory ; GetMyDirectory plug-in extension; WaitForMe and SelectChar programs and readme.txt file JoinFiles ; JoinFiles plug-in extension List ; List plug-in extension mfgui4.0 ; plug-in extensions, copy of this README file, export templates, Help files and ctl3d32.dll. `-----doc ; documentation files `-----data ; geospatial data file for sample problems ProgressBar ; ProgressBar plug-in extension ReadFileValue ; ReadFileValue plug-in extension and readme.txt file Utility ; Utility plug-in extension and help file, and `-----doc ; documentation file This same directory structure is created by the installation program. You should also download and extract Lf90wiod.zip from the web page. Extract the files from Lf90wiod.zip into the directory in which your operating system is installed (such as c:\Windows), another directory on the PATH of your operating system (such as c:\Windows\System32) or the directory in which the MODFLOW GUI is installed (\Program Files\Argus Interware\ArgusPIE\mfgui4.0). The export templates required for the MODFLOW GUI are as follows: MF_BAS.met MF_BCF.met MF_CacheData.met MF_CheckPIEs.met MF_DefineVariables.met MF_DIS.met MF_DRN.met MF_Err.met MF_EVT.met MF_FHB.met MF_GHB.met MF_HFB.met MF_IBS.met MF_InitializeProgressBar.met MF_LAK.met MF_MOC3D.met MF_MOC_ini.met MF_ModelViewerElev.met MF_Modflow2000.met MF_Name.met MF_OC.met MF_RCH.met MF_RES.met MF_RIV.met MF_SetCalcElev.met MF_SetOutputBudget.met MF_SetVariables.met MF_SOL.met MF_STR.met MF_TLK.met MF_WEL.met MODFLOW.met MODPATH.met MT3DMS.met ZoneBud.met Three additional export templates are placed in the mfgui4.0 directory contour2data.met statistics.met ContourExport.met The use of the first two of these export templates is explained in the documentation for version 3 of the MODFLOW GUI documentation and in the online help. The use of the third is described under "Known Issues" on the help system. C. USING MODFLOW-GUI After MODFLOW-GUI is properly installed (see INSTALLING, above), the plug-in extensions will be automatically loaded when Argus ONE is launched. The preprocessor is utilized by selecting the New MODFLOW Project menu item from the PIEs menu. The postprocessors are utilized by selecting the MODFLOW/MOC3D Post Processing or MODPATH Post Processing menu items from the PIEs menu. The postprocessors use information from the layer MODFLOW FD Grid. Therefore, it is necessary to have a project file open with the finite-difference grid that was used to generate the files Rootname.FHD and Rootname.FDN (for MODFLOW), Rootname.CNA and Rootname.VLA (for MOC3D), AND Rootname.end and Rootname.lin (for MODPATH) where Rootname is the data-set name provided by the user. D. SAMPLE PROBLEM DATA The mfgui4.0\data directory contains the geospatial data file, rma_map.dxf, used in the MOC3D sample problem presented in the report describing the addition of MOC3D capability to MODFLOW-GUI (mfgui4.0\doc\moc3dgui.pdf). It is also used in the sample problem described in the documentation for version 3 of the MODFLOW-GUI (mfgui4.0\doc\Mfgui_30.pdf). E. COMPILING The MODFLOW PIE may be compiled with Borland Delphi Professional versions 2006. However, it uses a number of freeware components that are not distributed with Borland Delphi 2006. These include: TArgusDataEntry by Richard B. Winston, TRBWZoomBox by Richard B. Winston, TRBWDataGrid3d by Richard B. Winston, TRBWStringGrid3d by Richard B. Winston, TRbwDataGrid by Richard B. Winston, TRbwDataGrid2 by Richard B. Winston, TRbwDataGrid4 by Richard B. Winston, TASLink copyright Andrey Abakumov, TDataGrid 2.0 copyright EC Software, and TALSTipDlg TCheckBox95, TRadioButton95 Copyright PA van Lonkhuyzen http://home.global.co.za/~peterv/index.htm Various files from the Jedi-Jvcl components: http://jvcl.delphi-jedi.org/ Except for the Jedi-Jvcl components, the source code for these components is distributed along with the source code for the MODFLOW GUI with permission of the copyright owners. These components must be installed before attempting to open or compile the MODFLOW GUI. In some cases, the components have been modified to work better with the MODFLOW GUI. The help files for the MODFLOW GUI were compiled with Help Scribble. http://www.jgsoft.com/