MODFLOW-2005 - Version: 1.11.00 Three-dimensional finite-difference ground-water flow modelNOTE: Any use of trade, product or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.This version of MODFLOW is referred to as MODFLOW-2005 in order to distinguishit from older versions of the code. This version of MODFLOW-2005 is packaged for personal computers using the Microsoft Windows XP or 7 operatingsystems. Executable files for personal computers are provided as well as thesource code. The source code can be compiled to run on other computers.IMPORTANT: Users should review the file mf2005.txt for a description of, andreferences for, this software. Users should also review the file release.txt,which describes changes that have been introduced into MODFLOW-2005 with eachofficial release; these changes may substantially affect users.Instructions for installation, execution, and testing of MODFLOW-2005 areprovided below. TABLE OF CONTENTS A. DISTRIBUTION FILE B. INSTALLING C. EXECUTING MODFLOW-2005 D. TESTING E. COMPILINGA. DISTRIBUTION FILEThe following distribution file is for use on personal computers: mf2005v1_11_00.zipThe distribution file contains: Compiled runfiles and source code for MODFLOW-2005. Supplementary MODFLOW-2005 documentation in PDF and text files. Test data sets.The distribution file is a compressed zip file. The following directorystructure is incorporated in the zip file: | |--mf2005.1_11 |--bin ; MODFLOW-2005 executables for personal computers |--doc ; Documentation files |MF2005convert ; Documentation of package conversions for MODFLOW-2005 |Updates ; Revisions and enhancements to MODFLOW-2005 |--src ; MODFLOW-2005 source code for use on any computer |hydprograms ; Source for hydrograph post processing program |mnw1to2 ; Source for program to convert MNW1 data files to MNW2 |--test-run ; Input data to run verification tests |--test-out ; Output files from running the testsThe installation instructions assume that the files have been extracted fromthe zip file into directory C:\WRDAPP, maintaining the above structure.It is recommended that no user files are kept in the mf2005.1_11 directorystructure. If you do plan to put your own files in the mf2005.1_11directory structure, do so only by creating additional subdirectories.Included in directory mf2005.1_11\doc are various documentation files. Someof them are Portable Document Format (PDF) files. The PDF files are readableand printable on various computer platforms using Acrobat Reader from Adobe.The Acrobat Reader is freely available from the following World Wide Website: http://www.adobe.com/B. INSTALLINGTo make the executable versions of MODFLOW-2005 accessible from anydirectory, the directory containing the executables (mf2005.1_11\bin)should be included in the PATH environment variable. Also, if aprior release of MODFLOW-2005 is installed on your system, thedirectory containing the executables for the prior release shouldbe removed from the PATH environment variable.As an alternative, the executable files, mf2005.exe and mf2005dbl.exe,in the mf2005.1_11\bin directory can be copied into a directory alreadyincluded in the PATH environment variable. HOW TO ADD TO THE PATH ENVIRONMENT VARIABLE WINDOWS 7 SYSTEMS From the Start menu, select Control Panel. Select System and Security,and within that screen choose the System option. Then select the AdvancedSystem Settings option. Select the Environment Variables button. In theSystem Variables pane, select the PATH variable followed by Edit. In theEdit window, add ";C:\WRDAPP\mf2005.1_11\bin" to the end of the VariableValue (ensure that the current contents of the User Value are not deleted)and click OK. Click OK in the Environment Variables window and then exitfrom the control panel windows. Initiate and use a new Windows Commandwindow. HOW TO ADD TO THE PATH ENVIRONMENT VARIABLE WINDOWS XP SYSTEMS From the Start menu, select Settings and then Control Panel. Double clickSystem and select the Advanced tab. Click on Environment Variables. Ifa PATH user variable already is defined, click on it in the User Variablespane, then click Edit. In the Edit User Variable window, add";C:\WRDAPP\mf2005.1_11\bin" to the end of the Variable Value (ensure thatthe current contents of the User Value are not deleted) and click OK. Ifa PATH user variable is not already defined in the User variables pane ofthe Environment Variables window, click New. In the New User Variablewindow, define a new variable PATH as shown above. Click OK. Click OKin the Environment Variables window and again in the System Propertieswindow. Initiate and use a new Windows Command window. HOW TO ADD TO THE PATH ENVIRONMENT VARIABLE WINDOWS VISTA SYSTEMS From the Start menu, select Settings and then Control Panel. SelectSystem & Maintenance followed by System. Choose the Advanced Systemoption. Select the Settings Task, and then select the EnvironmentalVariables button. In the System Variables pane, select the PATHvariable followed by Edit. In the Edit window, add";C:\WRDAPP\mf2005.1_11\bin" to the end of the Variable Value (ensurethat the current contents of the User Value are not deleted) and clickOK. Click OK in the Environment Variables window and then exit from thecontrol panel windows. Initiate and use a new Windows Command window.C. EXECUTING MODFLOW-2005Two MODFLOW-2005 runfiles for use on personal computers are provided. mf2005.exe is like the version that has been provided in all priorversions of MODFLOW-2005. It uses mixed single and double precision forcomputations and internal data storage, which was determined to be usefulfor a wide range of simulations. There are situations in which the mixedprecision is inadequate, which can be indicated by difficulty attainingsolver convergence or poor budget error. Accordingly, a runfile thatuses full double precision is provided -- mf2005dbl.exe. If mixedprecision is suspected of causing problems in a simulation, the samesimulation can be run using the full double precision runfile. Input forthe two runfiles is the same. In fact the source code is identical forboth. The double precision runfile is created by using a compiler optionthat raises the precision of single precision numbers to double precision.The penalty for using full double precision is additional computer memory,longer run times (depending on the computer), and unformatted (binary) filesthat are doubled in size. (Binary files are used for saving head, drawdown,and budget data.) This penalty is frequently not very significant. Typicalcomputers have adequate memory to run most double precision simulations, arenearly as fast performing double precision as mixed precision, and haveabundant disk space for storing binary output files.After the executable files in the mf2005.1_11\bin directory are installedin a directory that is included in your PATH, MODFLOW-2005 is initiated ina Windows Command-Prompt window using one of the following commands: mf2005 [Fname]or mf2005dbl [Fname]The optional Fname argument is the name file. If no argument is used,the user is prompted to enter the name file. If the name file ends in".nam", then the file name can be specified without including ".nam". For example, if the name file is named abc.nam, then the simulation canbe run using mixed precision by entering: mf2005 abcThe data arrays in MODFLOW-2005 are dynamically allocated, so modelsare not limited by hard-coded array limits. However, it is best to haveenough random-access memory (RAM) available to hold all of the requireddata. If there is less available RAM than this, the program will usevirtual memory, but this slows computations significantly.Some of the files written by MODFLOW are unformatted files. The structureof these files depends on the precision of the data in the program,the compiler, and options in the Fortran write statement. Any programthat use the unformatted files produced by MODFLOW must read the filesin the same way they were written. For example, Zonebudget and Modpathuse unformatted budget files produced by MODFLOW. Current versions ofZonebudget and Modpath automatically detect the precision of the data inunformatted files and the runfiles provided by the USGS are compatiblewith the structure of the unformatted files produced by this release ofMODFLOW-2005.Another example of unformatted files is head files that are generated byone MODFLOW simulation and used in a following simulation as initialheads. Both simulations must be run using an executable version ofMODFLOW that uses the same unformatted file structure. MODFLOW doesnot automatically detect precision of the data in these files, so bothsimulations must be run using a runfile having the same precision.This issue of unformatted files is described here so that users willbe aware of the possibility of problems caused by unformatted files. Older versions of MODFLOW executables provided by the U.S. GeologicalSurvey (USGS) may produce unformatted files with a different structure.The current form of unformatted file has been used in USGS MODFLOWexecutables starting with version 1.2 of MODFLOW-2000.D. TESTINGTest data sets are provided to verify that MODFLOW-2005 is correctlyinstalled and running on the system. The tests may also be lookedat as examples of how to use the program. The directoryMF2005.1_11\test-run contains the input data for running each test. Directory MF2005.1_11\test-out contains the output files from runningeach test. The tests are described in the file problems.txt.The directory MF2005.1_11\test-run can be used to conveniently run thetests without destroying the original results in the MF2005.1_11\test-outdirectory. The test-run directory contains MODFLOW name files, which endwith ".nam", for running the tests. Each test can be run by entering thename file for the test when executing MODFLOW-2005. MODFLOW-2005 shouldbe run in a command-prompt window with the current directory being thetest-run directory. The output files that are created in the test-rundirectory can then be compared to those in MF2005.1_11\test-out.E. COMPILINGThe executable files provided in MF2005.1_11\bin were created using the IntelVisual Fortran 13.1 and Microsoft Visual C++ .NET compilers. Althoughexecutable versions of the program are provided, the source code is providedin the mf2005.1_11\src directory so that MODFLOW can be recompiled ifnecessary. However, the USGS cannot provide assistance to those compilingMODFLOW. In general, the requirements are a Fortran compiler, a compatibleC compiler, and the knowledge of using the compilers.The C compiler is used for the GMG solver. If a compatible C compiler isnot available, the GMG solver can be removed so that only a Fortran compileris required. File Nogmg.txt in the src directory contains instructions forremoving GMG from MODFLOW.