File: READ.ME FGETS Food and Gill Exchange of Toxic Substances Version 3.0.18 U.S. EPA Release, September 1994 Center for Exposure Assessment Modeling (CEAM) U.S. Environmental Protection Agency (U.S. EPA) Office of Research and Development (ORD) Athens Environmental Research Laboratory (AERL) 960 College Station Road Athens, Georgia 30605-2700 706/546-3549 _________________________________________________________________ CONTENTS Introduction Abstract Documentation Distribution Diskette File Name and Content Development System Routine Execution Run Time and Performance Minimum File Configuration Modification Technical Help Contact Disclaimer _________________________________________________________________ INTRODUCTION FGETS (Food and Gill Exchange of Toxic Substances) is a FORTRAN simulation model that predicts temporal dynamics of a fish's whole body concentration (ug chemical/(g live weight fish)) of nonionic, nonmetabolized, organic chemicals that are bioaccumulated from either: (a) water only - which is the predominant route of exchange during acute exposures, or (b) water and food jointly - which is more characteristic of chronic exposures. FGETS also calculates the time to reach the chemical's lethal activity by assuming that the chemical elicits its pharmacological response through a narcotic mode of action. For a list of modifications since the last release of the FGETS model system, refer to the files RELEASE.TXT and UPDATE.TXT (refer to FILE NAME AND CONTENT section). NOTE: For convenience, the terms "FGETS model system" or "FGETS" will be used in this document to refer to the FGETS model and all associated support files and programs as a single unit. Therefore, the term "FGETS" is synonymous with "FGETS model system" for purposes of this document. _________________________________________________________________ ABSTRACT Summary FGETS (Food and Gill Exchange of Toxic Substances) is a FORTRAN simulation model that predicts temporal dynamics of a fish's whole body concentration (ug chemical/(g live weight fish)) of nonionic, nonmetabolized, organic chemicals that are bioaccumulated from either: (a) water only - which is the predominant route of exchange during acute exposures, or (b) water and food jointly - which is more characteristic of chronic exposures (1,2). FGETS also calculates the time to reach the chemical's lethal activity by assuming that the chemical elicits its pharmacological response through a narcotic mode of action. FGETS considers both the biological attributes of the fish and the physico-chemical properties of the chemical that determine diffusive exchange across gill membranes and intestinal mucosa. Important biological characteristics addressed by the model are the fish's gill and intestinal morphometry, the body weight of the fish, and the fractional aqueous, lipid, and structural organic composition. Relevant physico-chemical properties are the chemical's aqueous diffusivity, molar volume, and the n-octanol/water partition coefficient (logP), that is used as a surrogate to quantify chemical partitioning to the fish's lipid and structural organic fractions. The chemical's logP is used in calculating the fish's bioconcentration factor. Its molecular volume is used to estimate the chemical's aqueous diffusivity, and its melting point is used in conjunction with logP to calculate the chemical's activity within the fish. FGETS is parameterized for a particular fish species by means of two morphological/physiological databases that delineate the fish's gill morphometry, feeding and metabolic demands, and body composition. Presently, joint water and food exposure is parameterized for salmonids, centrarchids, cyprinids, percids, and ictalurids. References 1. Barber, M.C., L.A. Suarez, and R.R. Lassiter. 1991. Modeling Bioaccumulation Organic Pollutants in Fish with an application to PCBs in the Great Lakes salmonids. Can. J. Fish. Aquat. Sci., 48: 318-337. 2. Barber, M.C., L.A. Suarez, and R.R. Lassiter. 1988. Modeling Bioconcentration of Nonpolar Organic Pollutants by Fish. Environ. Toxicol. Chem., 7: 545-558. _________________________________________________________________ DOCUMENTATION It is recommended that the user obtain and reference the documents listed below to operate and apply the FGETS model system. Copies of the following documents are included on the distribution diskette and within the electronic bulletin board system (BBS)/Internet distribution file INSTALFG.EXE. Refer to FILE NAME AND CONTENT and MINIMUM FILE CONFIGURATION sections for further information. Document Name(s) File Name(s) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~ FGETS model system general execution and READ.ME user support guide FGETS Model System Release Notes RELEASE.TXT FGETS Model System Update Notes UPDATE.TXT (Enhancements/updates/additions not covered in user's manual) CEAM Software Product User Response Form RESPONSE.TXT FGETS Version 3.0.18 User's Manual USERSMAN.DOC These documents should be retained by the requester for future reference. NOTE: The files READ.ME, RELEASE.TXT, UPDATE.TXT, and RESPONSE.TXT are ASCII text (non-binary) files that can be displayed on the monitor screen by using the DOS TYPE command (e.g., TYPE READ.ME) or printed using the DOS PRINT command (e.g., PRINT READ.ME). File names with a file name extension of ".DOC" are WordPerfect (binary) document files that can only be viewed and/or printed within WordPerfect. _________________________________________________________________ DISTRIBUTION DISKETTE NOTE: k=1,024; m=1,048,576; b=1 byte Included is 1, 3.5 inch (1.44mb, DS/HD) DOS (Disk Operating System) formatted diskette containing the Food and Gill Exchange of Toxic Substances model system (FGETS, Version 3.0.18), dated September 1994. This model system is designed for the IBM PC family of microcomputer or compatible systems running under version 3.30 or higher of the Microsoft or PC Disk Operating Systems (PC or MS DOS--refer to DEVELOPMENT SYSTEM section). Properly configured, this model system and its support files and programs can be executed under PC DOS or MS DOS 3.30 and later versions, DOS 4.0x, DOS 5.0x, or DOS 6.x. To install the FGETS model system and/or related support files and programs on a hard disk, insert the distribution diskette in a compatible diskette drive. Type A:\INSTALL or B:\INSTALL at the DOS system prompt and press the key. Then follow instructions and respond to the prompts presented on the monitor screen by the interactive installation program. This is a compressed, self-extracting, interactive installation program with on-line, context sensitive help that contains the Food and Gill Exchange of Toxic Substances model (FGETS, Version 3.0.18), dated September 1994. NOTE: If the FGETS model system is being installed from the FGETS installation file (INSTALFG.EXE) downloaded from the CEAM electronic bulletin board system (BBS) or the Internet, then the user should type INSTALFG at the DOS system prompt and press the key. This command assumes that the current default drive and sub-directory is the same drive and sub-directory that contain the file INSTALFG.EXE. For further information on the CEAM BBS and access to CEAM software products through the Internet, refer to the TECHNICAL HELP CONTACT section. NOTE: The content of the distribution diskette can be copied to another "backup" diskette using the DOS DISKCOPY command. Refer to the DOS Reference Manual for command application and use. The "backup" diskette must be the same size and storage density as the original source diskette. The following FILE NAME AND CONTENT section provides a brief functional description of each file by name or file name extension type. Other sections in this document contain information about o system development tools used to build the microcomputer release of the FGETS model system o recommended hardware and software configuration for the execution of the model system and all support programs o program execution o sample run times o minimum file configuration o program modification o technical support _________________________________________________________________ FILE NAME AND CONTENT The self-extracting, interactive executable program file exists in a compressed format to save disk space and file transfer time. This section contains a description of each file that can be decompressed from the compressed distribution diskette and/or file. Follow the instructions shown on the interactive installation program screens and menus to install, decompress (extract), and restore file(s) to their original name and size in order to place the FGETS model system in a usable format on a hard or virtual disk. For comparison purposes, the original date and time of creation are also restored with each file. NOTE: Execution of the INSTALL or INSTALFG command can extract one or more FGETS model system files. These files are automatically stored into DOS sub-directories on the hard disk. The sub-directory structure, under which the sub-directories shown below are stored, is selected by the user during execution of the INSTALL or INSTALFG program. The string "InstallationDirectory" will be used to denote the highest level default installation directory structure chosen by the user during execution of INSTALL or INSTALFG. Below the installation directory, all files are grouped and listed by the appropriate DOS sub-directory name into which they will be automatically stored. ** Sub-directory InstallationDirectory\README: READ.ME - FGETS model system execution and general support guide. This is an ASCII text (non-binary) file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. RELEASE.TXT - Summary of corrections and/or changes between release versions. This is an ASCII text (non- binary) file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. UPDATE.TXT - Summary of enhancements, updates, and additions not covered in the current user's manual. This is an ASCII text (non-binary) file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. RESPONSE.TXT - CEAM Software Product User Response Form. This is an ASCII text (non-binary) file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. ** Sub-directory InstallationDirectory\DOCUMENT NOTE: The following file(s) are NOT required to execute and/or test any model, program, or associated run time support file as provided on the distribution diskette or electronic bulletin board/Internet installation file. For further information, refer to the MINIMUM FILE CONFIGURATION section. File names with a file name extension of ".DOC" are WordPerfect (binary) document files that can only be viewed and/or printed within WordPerfect. USERSMAN.DOC - FGETS Version 3.0.18 User's Manual. ** Sub-directory InstallationDirectory: F77L3.EER - Run time error message library file for Lahey FORTRAN (F77L3) (refer to DEVELOPMENT SYSTEM section). This file is read automatically during execution of the FGETS model system executable task image file (*.EXE) if an error is detected during execution. RETURN1.ANS - An empty file containing a single carriage return character used to provide an key or null response to an input prompt in selected DOS batch command files. FGETS.BAT - DOS batch command file used to execute the FGETS model. To execute, type FGETS at the DOS system prompt, press the key, then respond to the information screens and/or prompts displayed on the monitor screen. For further information on executing FGETS, refer to the ROUTINE EXECUTION section. NOTE: To execute the FGETS.BAT batch command file, and hence the FGETS model, from any sub-directory located on a hard or virtual disk drive, add the FGETS installation sub-directory (e.g., C:\FGETS) to the DOS search PATH. One way to accomplish this is to add or modify the PATH statement in the system start-up file, AUTOEXEC.BAT (located in the root directory on the start-up or boot drive). For example PATH C:\;C:\DOS;C:\UTIL;C:\WP51;C:\FGETS Refer to the DOS Reference Manual for PATH command and AUTOEXEC.BAT file application and use. FGETOPEN.SCR - Initial welcome and CEAM information screen displayed before the execution of the FGETS model by the DOS batch command file FGETS.BAT. This is an ASCII text (non-binary) file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. FGETS3.DB - FGETS version 3.0.18 data base file. This file is read automatically during the execution of the FGETS executable task image file (XFGETSX.EXE). XFGETSX.EXE - Executable task image file for the FGETS model. WARNING: This task image file (XFGETSX.EXE) should only be executed using the DOS batch command file provided (FGETS.BAT). ATEST.IN - Example input data file to test the installation and demonstrate application of the FGETS model. This data file is also furnished to provide instruction by example and can be used as a template for the preparation of new input files. To test installation, execute the FGETS model using this file as the name of an input file. The model interactively prompts the user for an input file name or the user can provide this file name on the DOS command line (e.g., C:\FGETS> FGETS ATEST.IN). This is an ASCII (non-binary) text file that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. This file can also be viewed or edited using any editor program that can read and save a file to disk in ASCII text (non-binary) format. NOTE: A file name path specification and/or file name, as typed by the user, must be a unique and valid DOS path and/or file name. An input file name must also be a valid FGETS input data file name -- either furnished with the distribution package or created, designated, and named by the user. A file name used as input data for the FGETS model will be processed and executed in the run of the model. Remember, a DOS file name can be from 1 to 8 characters and can have an optional 1 to 3 character file name extension. NOTE: Refer to the explanation of the ATEST.FGZ file for a procedure to compare the contents of an output file produced on the users system to an output file provided with the distribution release. ** Sub-directory InstallationDirectory\OUTPUT: ATEST.FGZ - Output listing file produced by the FGETS model using the test input data file ATEST.IN that is provided with the distribution release. After executing the FGETS model with this test data file, compare the contents of the output file produced (i.e., ATEST.FGZ) with the corresponding output file provided within the sub-directory OUTPUT (e.g., OUTPUT/ATEST.FGZ). To compare file contents, use the COMP (PC DOS) or FC (MS DOS) file compare command, or print both files then compare contents by hand. For further information on executing the FGETS model, refer to file FGETS.BAT in this section or to the ROUTINE EXECUTION section. NOTE: The symbol "" represents pressing the or carriage return key. Responses and key strokes that can be typed by the user are underlined with the hyphen character (-) and/or enclosed by the angle bracket characters (<>). Example FGETS interactive (non-batch) execution and file comparison sequence: 1) Set the default drive to the disk containing the FGETS model system sub-directory: A:\> C: -- 2) Change the DOS default sub-directory to the sub-directory designated by the user during the installation program as the installation sub-directory (e.g., FGETS). Use the DOS CD (change directory) command at the DOS system prompt: C:\> CD \FGETS --------- 3) Execute the FGETS model with a selected test input data file: C:\FGETS> FGETS ----- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (FGETS banner/registration screen displayed here...press the key to clear screen and continue model execution...) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (The following screen is displayed next while the FGETS program is loaded into memory.) # # ## Loading FGETS task image file...wait. # #------------------------# ## FGETS run beginning. #------------------------# # ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» º 32-bit Power for Lahey Computer Systems º º Phar Lap's 386|DOS-Extender(tm) Version 4.1L º º Copyright (C) 1986-92 Phar Lap Software, Inc. º º Available Memory = xxxxx Kb º ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (Where xxxxx is a number that represents the available RAM memory on the host system, expressed in K bytes (K=1,024), that will be filled in automatically by the FGETS executable task image file. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ program: FGETS 3.0.18 [12-sep-1994] parameter file name (or press "Enter" to exit): ATEST.IN input file: e:\fgets3\atest.in -------- output file: e:\fgets3\atest.fgz date: 14:27:04.10 09/22/94 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (FGETS run time diagnostic and information status messages displayed here while the model executes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ## accessing database. physiological database: E:\FGETS3\Fgets3.db ## laboratory FGETS 3.0.18 # # ## FGETS program execution complete. # # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (Compare the output file produced to the one supplied.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ C:\FGETS> COMP ATEST.FGZ OUTPUT\ATEST.FGZ ------------------------------- or, C:\FGETS> FC ATEST.FGZ OUTPUT\ATEST.FGZ ----------------------------- NOTE: The FGETS output file contains a date and time stamp. Therefore, the only difference between the output file produced to the one supplied should be the date and time of the run as noted and printed in the output file. ** Sub-directory InstallationDirectory\TESTDATA: NOTE: The following file(s) are NOT required to document, execute and/or test any model, program, or associated run time support file as provided on the distribution diskette or the electronic bulletin board/Internet installation file. For further information, refer to the MINIMUM FILE CONFIGURATION section. *.DAT - Eleven additional sample input data files to test the installation and demonstrate application of the FGETS model. These data files are also furnished to provide instruction by example. To further test the installation, copy these files to the InstallationDirectory (e.g. COPY C:\FGETS\TESTDATA\*.* C:\FGETS\*.*) then execute the FGETS model using each file individually as input data. The test input data files provide examples of the input for most sections and capabilities of the FGETS model. For further information on executing FGETS refer to file FGETS.BAT in this section or to the ROUTINE EXECUTION section. These are ASCII (non-binary) text files that can be displayed on the monitor screen with the DOS TYPE command or printed using the DOS PRINT command. These files can also be viewed or edited using any editor program that can read and save a file to disk in ASCII text format. NOTE: A file name path specification and/or file name, as typed by the user, must be a unique and valid DOS path and/or file name. An input file name must also be a valid FGETS model input data file name -- either furnished with the distribution package or created, designated, and named by the user. A file name used as input data for the FGETS model will be processed and executed in the run of that model. Remember, a DOS file name can be from 1 to 8 characters and can have an optional 1 to 3 character file name extension. NOTE: Refer to the explanation of the file ATEST.FGZ for a procedure to compare the contents of an output file produced on the users system to an output file provided with the distribution release. FGETSCMD.XMS - FGETS version 3.0.18 input files. These files are FGETSEXP.XMS read automatically during the execution of the FGETS executable task image file (XFGETSX.EXE) when the file PONDXMS.DAT is used as the user input file. ** Sub-directory InstallationDirectory\FGETCODE: NOTE: The following file(s) are NOT required to document, execute and/or test any model, program, or associated run time support file as provided on the distribution diskette or the electronic bulletin board/Internet installation file. For further information, refer to the MINIMUM FILE CONFIGURATION section. MAKEFILE - Lahey make file that can be used to compile and/or link edit the FGETS model FORTRAN source code files (*.BLK, *.H, *.INC, *.PAR, *.SFN, *.DEF, *.FOR) to incorporate changes made in the source code files by the user. Refer to the program listing for in-code documentation. The execution of this command can produce a new executable task image file (XFGETSX.EXE) for the FGETS model. This command file only needs to be executed if changes have been made in the FORTRAN source code, not input data files. To execute, type MAKE at the DOS system prompt, then press the key. *.BLK - FORTRAN source code "include" files containing *.H FORTRAN COMMON block declarations for the FGETS *.INC model. These files are automatically included or *.PAR "copied" into the FGETS FORTRAN source code file *.SFN (FGET3018.FOR) during compilation. *.DEF FGET3018.FOR - FORTRAN source code file for the FGETS model, version 3.0.18. ** Sub-directory InstallationDirectory: Special Run Time File NOTE: The following file(s) are not distributed with the distribution release. They are created automatically when the user executes the FGETS model. FGETSRUN.LOG - Run time log file that contains a beginning and ending date and time stamp for each execution of the model. The file name of the input data file will also be listed if the name of the input file is given on the DOS command line. Refer to the ROUTINE EXECUTION section for further information. This file can be cleaned up (i.e., deleted) at any time by the user. _________________________________________________________________ DEVELOPMENT SYSTEM The following list describes the language and program development tools used by the Center for Exposure Assessment Modeling to build version 3.0.18 of the microcomputer implementation of the FGETS model system. Also shown are the recommended minimum hardware and software configuration and the recommended \CONFIG.SYS configuration/environment file statements for the implementation and execution of this model and all related support files and programs. Make sure that the IBM PC or compatible system has these statements in the \CONFIG.SYS file, and re-boot the system to implement these changes before attempting to install or use the FGETS model system. Development System: Hardware System: Fully IBM compatible 80386, 80486, or 80586 Language: FORTRAN 77 Operating System: DOS version 3.30 or higher. Properly configured, this model system should also work on hardware platforms with PC DOS or MS DOS versions 4.0x, 5.0x, or 6.x DOS Extender: Phar Lap 386/DOS-extender; bound into application EXE file with automatic virtual memory management; distributed royalty free Memory Manager: Compatible with VDISK.SYS, QEMM386, HIMEM.SYS, RAMDRIVE.SYS, EMM386, CEMM, 386Max; compatible with DPMI, VCPI, and XMS standards Compiler: Lahey FORTRAN, F77L-EM/32 version 5.01 Link Editor: Phar Lap 386LINK version 4.1L Overlay Structure: None - linked as flat memory model Storage Requirements: (k=1,024; m=1,048,576) Random Access Memory: (approximate minimum free bytes needed to execute EXE file) 640k base (low end) memory, plus 1.1m bytes of free extended (XMS) memory and 2.1m bytes of free disk space; or, 1m byte of free extended (XMS) memory and 3.2m bytes disk space Diskette Drive: Required for installation only. Hard Disk Drive: 20m byte drive recommended (minimum) with 3.5m bytes free (minimum) Installation Size: Run Time: Approx. 1.1m bytes max. Document: Approx. .3m bytes max. FOR Code: Approx. 1.0m bytes max. ~~~~~ Total 2.4m bytes (Total does not include *.OBJ if all source code files are compiled and linked.) Run time size: Up to approximately 1m bytes plus space for user input data files, output, and temporary files produced by model (refer to MINIMUM FILE CONFIGURATION section). Numerical Coprocessor: Required. \CONFIG.SYS Statements: BREAK=ON BUFFERS=20 or BUFFERS=32 FILES=20 DEVICE=C:\ANSI.SYS DEVICE=extended memory manager - and - SHELL=C:\COMMAND.COM C:\ /e:512 /p Printer: For *.DOC file only, HP LaserJet III PostScript or compatible printer. Printer Software: For *.DOC file only, WordPerfect version 5.1 or greater. _________________________________________________________________ ROUTINE EXECUTION NOTE: The symbol "" represents pressing the or carriage return key. Responses and key strokes that can be typed by the user are underlined with the hyphen character (-) and/or enclosed by the angle bracket characters (<>). NOTE: It is possible that the FGETS model system could be incompatible with MS DOS and Windows software cache files SMARTDRV.SYS or SMARTDRV.EXE loaded from the system configuration files \CONFIG.SYS and/or \AUTOEXEC.BAT on the boot drive. If any portion of the FGETS model system prematurely halts, produces unusual results, and/or causes the host system to halt or hang, remove any SMARTDRV statements on the boot drive \CONFIG.SYS and/or \AUTOEXEC.BAT files, then re-boot the system to implement these changes before attempting to reuse any portion the FGETS model system. Introduction ~~~~~~~~~~~~ Complete the installation process to make the full or any portion of the FGETS model system and related files resident on a hard (usually designated as "C:") or virtual disk drive. Then modify the \CONFIG.SYS system environment file and restart the microcomputer system. This needs to be completed only once for a given installation of the FGETS model system. DOS Storage Path ~~~~~~~~~~~~~~~~ Verify that the FGETS model and support program executable task image and DOS batch command files (*.EXE, *.BAT) and user defined input data file(s) are in the current default DOS sub-directory. It is convenient but not required to have these files in the same sub-directory. NOTE: To execute the FGETS model system from any sub-directory located on a hard or virtual disk drive, add the FGETS installation sub-directory (e.g., C:\FGETS) to the DOS search PATH statement. One way to accomplish this is to add or modify the PATH statement in the system start-up file, AUTOEXEC.BAT (located in the root directory on the start-up or boot drive). For example PATH C:\;C:\DOS;C:\UTIL;C:\WP51;C:\FGETS Refer to the DOS Reference Manual for PATH command and AUTOEXEC.BAT file application and use. Routine Execution Steps ~~~~~~~~~~~~~~~~~~~~~~~ Step Description/Action ~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1) Set the default drive to the disk containing the FGETS model system sub-directory. For example: A:\> C: -- 2) Change the DOS default sub-directory to the sub-directory designated by the user during the installation program as the installation sub-directory (e.g., FGETS). Use the DOS CD (change directory) command at the DOS system prompt: C:\> CD \FGETS --------- NOTE: A common problem is for a DOS executable or batch command file (*.EXE. *.BAT) to be unable to locate a file because it assumes the file is on the default drive and/or sub-directory when it is not. If input and/or other run time support file(s) are not on the default drive and sub-directory, the user can type a drive and/or path name ahead of the file name. For further information refer to the "File Name and Path Specifications" sub-section later in this document or the DOS Reference Manual. 4) To execute the FGETS model, type: C:\FGETS> FGETS ----- After an opening banner/registration screen is displayed on the monitor, press the key to clear the screen and continue model execution. The model will begin prompting the user for information needed for this run of the model. The user should respond to any information screens, menus, and/or prompts displayed on the monitor screen. The DOS command line syntax to execute the FGETS model is FGETS [input-file-name] where input-file-name is an optional command line argument for the FGETS model input file name that must be specified by the user. If the input file name is not specified on the FGETS command line, then the following prompt will be displayed on the monitor after the opening banner/registration screen: parameter file name (or press "Enter" to exit): The response to this prompt can include an optional drive and/or path for the file name entered (e.g., C:\FGETS\TESTDATA\MYDATA.INP). Viewing Output Results ~~~~~~~~~~~~~~~~~~~~~~ After executing the FGETS model executable task image file (*.EXE), the user can view an output file, if any, produced by the execution of the model if and only if that file is in ASCII text (non-binary) format. Results can be viewed by scrolling through the output file that was (1) a result of model execution and (2) named by the user. A word processor or text editor is convenient for this purpose, or the command TYPE filename.ext | MORE can be used where "filename.ext" is the name of the output file (e.g., filename.FGZ). However, the TYPE command is awkward for output files that exceeds the 80-column screen width. Alternatively, the output file can be printed. A compressed print mode (132 column) should be used to avoid awkward--wrapped around--output from lines that exceed 80 columns. The DOS MODE command can be used for this purpose. For a parallel printer assigned to LPT1, the DOS command MODE LPT1: 132 will cause most printers to print in compressed mode. For further information, refer to the DOS Reference Manual. File Name and Path Specifications ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A file name, path specification, and/or the parameter file name argument "filename.ext" must be a unique and valid DOS path and/or file name. The user response "filename.ext" must also be a valid FGETS model system input or output file name -- either furnished with the distribution package (refer to FILE NAME AND CONTENT section) or created, designated, and named by the user. A file name used as input data for any program and/or model in the FGETS model system will be processed and executed in that run of the program or model. File names used for the input data and/or output listing files (except for the test input and example output cases provided) are arbitrary, but must follow the rules for DOS file names. A file name should assist the user with identifying the contents or purpose of a file (e.g., INPUT.DAT, OUTPUT.LST). Any file name can be from 1 to 8 characters and can have an optional 1 to 3 character file name extension. Any characters beyond 8 in the file name or beyond 3 in the file name extension will be truncated and ignored by the DOS operating system. Refer to the DOS Reference Manual for further information on file names and disk file input/output procedures, rules, and commands. NOTE: Refer to the explanation of the *.FGZ file in the FILE NAME AND CONTENT section for a procedure to compare the contents of an output file produced on the users system to an output file provided with the distribution release. _________________________________________________________________ RUN TIME AND PERFORMANCE The following run times (approximate) were observed using the test data files furnished with the distribution version of the FGETS model system. Remember that these times were obtained using test data files that may not be representative of a "real world" problem and/or data. The test data files have been furnished for testing the installation of the FGETS model system and for instruction by example. In general, these input test data files are not intended to be representative of full scale model simulations. They were developed to test the installation of significant sections of model code. The run times listed in the table below were produced on a Microway 80486 B2T EISA class microcomputer running under MS DOS 5.0 and using 640k bytes of random access (low end) memory (RAM), 32 megabytes of extended memory, a 32 megabyte virtual (RAM) disk, Microp 1624-15 SCSI 765 megabyte DPT EISA hard disk with 512K byte cache SCSI controller, a 256K byte memory cache, a 50 megahertz clock, a Number Smasher-860 40 megahertz, 32 megabyte math numerical coprocessor, and an ATI Ultra Graphics 1 megabyte video card. Input File Name Approx. Run Time (hr:min:sec) ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~ ATEST.IN 00:00:14 TANK.DAT 00:00:09 TANK2.DAT 00:00:11 CJFAST1.DAT 00:00:31 CJFAST2.DAT 00:00:30 CJFASF1.DAT 00:00:20 CJFASF2.DAT 00:00:21 FWF1.DAT 00:00:40 FWF2.DAT 00:00:40 CLF1.DAT 00:00:40 CLF2.DAT 00:00:40 PONDXMS.DAT 00:01:04 Program run time and performance can be affected by many microcomputer system and program parameters including o available disk space o available memory o CONFIG.SYS and AUTOEXEC.BAT file options and parameter values o disk and/or file storage and/or fragmentation _________________________________________________________________ MINIMUM FILE CONFIGURATION The following list describes the absolute minimum file configuration needed within the application sub-directory to execute the FGETS model system and all support command files and programs. This list assumes that o the FGETS model system and all support files and programs have been successfully installed from the distribution release o the user has defined and stored all application specific run time files NOTE: Files other than those listed below can be deleted if the user needs to recover disk space. ** Sub-directory InstallationDirectory\README: READ.ME - FGETS model system execution and general support guide. RELEASE.TXT - Summary of corrections and/or changes between release versions. UPDATE.TXT - Summary of enhancements, updates, and additions not covered in the current user's manual. ** Sub-directory InstallationDirectory: F77L3.EER - Run time error message library file for Lahey FORTRAN (F77L3). RETURN1.ANS - An empty file containing a single carriage return character. FGETS.BAT - DOS batch command file used to execute the FGETS model. FGETOPEN.SCR - Initial welcome and CEAM information screen. FGETS3.DB - FGETS version 3.0.18 data base file. XFGETSX.EXE - Executable task image file for the FGETS model. WARNING: This task image file (XFGETSX.EXE) should only be executed using the DOS batch command file provided (FGETS.BAT). ** Sub-directory InstallationDirectory\DOCUMENT USERSMAN.DOC - FGETS Version 3.0.18 User's Manual. _________________________________________________________________ MODIFICATION Included with the distribution release are o executable task image file for the FGETS model system o FORTRAN source code files for IBM PC and compatible microcomputer systems (refer to DEVELOPMENT SYSTEM section) A FORTRAN compiler and link editor are NOT required to execute any portion of the FGETS model system. If the user wishes to modify any portion of the FGETS model system, it will be up to the user to supply and/or obtain o an appropriate text editor that saves files in ASCII text (non-binary) format o FORTRAN program development tools to recompile and link edit any model and/or program The U.S. EPA CEAM cannot support, maintain, and/or be responsible for modifications that change the function of any executable task image file (*.EXE) or DOS batch command file (*.BAT) supplied with this model package. _________________________________________________________________ TECHNICAL HELP CONTACT NOTE: This section assumes that the user has successfully completed the installation process to make the full or any portion of the FGETS model system and related files resident and fully operational on a hard (usually designated as "C:") or virtual disk drive. For further information on installation and execution, refer to the DISTRIBUTION DISKETTE and ROUTINE EXECUTION sections. For questions and/or information concerning o installation and/or testing of the FGETS model system and/or support programs or files, call 706/546-3590 for assistance or send mail via Internet to ceam@athens.ath.epa.gov o model content, theory and/or application, call 503/867- 2301 for assistance o use of the CEAM electronic bulletin board system (BBS) or the Internet, contact the BBS system operator (SYSOP) at 706/546-3590 o other environmental software products and documentation distributed through CEAM, contact the Model Distribution Coordinator at 706/546-3549 o other support available through CEAM, contact Mr. Dermont Bouchard, CEAM Manager - by mail at the following address Center for Exposure Assessment Modeling (CEAM) Athens Environmental Research Laboratory U.S. Environmental Protection Agency 960 College Station Road Athens, Georgia 30605-2700 - by telephone at 706/546-3130 - by fax at 706/546-3340 - by email or Internet at ceam@athens.ath.epa.gov - through the CEAM BBS message menu and commands. The CEAM BBS communication parameters and telephone number are listed below. To help technical staff provide better assistance, write down a response to the following topics before calling or writing. If calling, be at the computer, with the computer on, and in the proper sub-directory (e.g., C:\FGETS) when the call is placed. o program information: - describe the problem, including the exact wording of any error and/or warning message(s) - list the exact steps, command(s), and/or keyboard key sequence that will reproduce the problem o machine information: - list computer brand and model - list available RAM (as reported by DOS CHKDSK or MEM command) - list extended memory present and free (XMS) - list name and version of extended memory (XMS) manager (i.e., HIMEM, VDISK, RAMDRIVE, etc.) - list available hard disk space (as reported by DOS CHKDSK command) - list the brand and version of DOS (as reported by DOS VER command) - list the name of any memory resident (TSR) program(s) installed - printer brand and model - monitor brand and model NOTE: If contacting CEAM by mail, fax, or BBS, include responses to the above information in correspondence. To check the status of the latest release of this model system or any other CEAM software product, call the CEAM BBS 24 hours a day, 7 days a week. To access the BBS, a computer with a modem and communication software are needed. The phone number for the BBS is 706/546-3402. Communication parameters for the BBS are o 1200-14400 baud o 8 data bits o no parity o 1 stop bit The user can also check the status of this model system or any other CEAM software product through Internet node earth1.epa.gov The FGETS model system and selected other CEAM software products for microcomputer (i.e., DOS, NOT Unix) installation and application can be down loaded through Internet from the above node via "anonymous" ftp (File Transfer Protocol) log in and file transfer commands and options. For further information on this Internet node and ftp, refer to document files USERINFO.TXT, QREF_WWW.TXT, and QUICKREF.TXT that are included in the file INTERNET.ZIP that can be down loaded from the Internet or the CEAM BBS through the file INTERNET.ZIP. To access DOS releases of selected CEAM software products via Internet, start the ftp program from the user's Internet node system (type 'ftp'), establish earth1 connection (type 'open earth1.epa.gov'), log onto earth1 using anonymous account (type 'anonymous'). Respond to password prompt with users e-mail or Internet address. Then, upon log in completion, type 'cd epa_ceam', read CEAM Internet Welcome Screen, then type 'get CEAMNEWS.TXT -' to view latest news and list of CEAM software products available on the Internet. The same selected CEAM software products as mentioned above are also available through the World Wide Web (WWW). If the user has access to the World Wide Web, selected CEAM software products, including FGETS, can be accessed at the following Universal Resource Locator (URL): file://earth1.epa.gov/epa_ceam/wwwhtml/ceam_home.html _________________________________________________________________ DISCLAIMER Mention of trade names or use of commercial products does not constitute endorsement or recommendation for use by the United States Environmental Protection Agency. Execution of any portion of the FGETS model system, and modification to the DOS system configuration files (i.e., \CONFIG.SYS and \AUTOEXEC.BAT) must be used and/or made at the user's own risk. Neither the U.S. EPA nor the program author(s) can assume responsibility for model and/or program modification, content, output, interpretation, or usage. The FGETS program and files have been extensively tested and verified. However, as for all complex software products, the programs herein may not be completely free of errors and may not be applicable for all cases. In no event will the U.S. EPA be liable for direct, indirect, special, incidental, or consequential damages arising out of the use of the programs and/or associated documentation. CEAM software products are built using FORTRAN-77, assembler, and operating system interface command languages. The code structure and logic of these products is designed for single-user, single-tasking, non-LAN environment and operating platform for microcomputer installations (i.e., single user on dedicated system). A user will be on their own if he/she attempts to install a CEAM product on a multi-user, multi-tasking, and/or LAN based system (i.e., Windows, DESQview, any LAN). CEAM cannot provide installation, operation, and/or general user support under any combination of these configurations. Instructions and conditions for proper installation and testing are provided with the product in a READ.ME file. While multiuser/multitasking/LAN installations could work, none of the CEAM products have been thoroughly tested under all possible conditions. CEAM can provide selected and/or limited scientific and/or application support for selected products if the user proves that a given product is installed and working correctly. o WordPerfect is a registered trademark of WordPerfect Corporation o Microway and Number Smasher are registered trademarks of Microway, Inc. o Intel, 386, 486, and 860 are registered trademarks of Intel Corporation. o F77L is a registered trademark of Lahey Computer Systems, Inc. All other Lahey products are trademarks of Lahey Computer Systems, Inc. o IBM, Personal Computer/XT (PC/XT), Personal Computer/AT (PC/AT), PC DOS, VDISK, and Personal System/2 (PS/2) are registered trademarks of International Business Machines Corporation o PKZIP, PKUNZIP, and PKSFX are registered trademarks and/or trademarks of PKWARE, Incorporated. o DESQview is a trademark of Quarterdeck Office Systems, Inc. o Sun and SunOS are registered trademarks of Sun Microsystems, Inc. o SPARC is a registered trademark of SPARC International, Inc. o UNIX is a registered trademark of American Telephone and Telegraph o SVS FORTRAN-77 is a trademark of Silicon Valley Software o PRIME and PRIMOS are trademarks of Prime Computers, Inc. o Microsoft, RAMDRIVE, HIMEM, MS, and MS-DOS are registered trademarks of Microsoft Corporation o Windows is a trademark of Microsoft Corporation o RM/FORTRAN is a trademark of Language Processors, Inc. o DEC, VAX, VMS, and DCL are trademarks of Digital Equipment Corporation o US Robotics is a registered trademark and Courier HST is a trademark of U.S. Robotics, Inc. o VP-Expert is a registered trade mark of WordTech Systems, Inc. ######################### DWD/dwd - September 1994 - E:\FGETS3\README\READ.ME