Fname — is the name of the flow-transport link file produced by MODFLOW-2000 through the LMT6 Package for use by the MT3DMS transport model. Directory path names may be specified as part of Fname as in D:\MF2K\DATA\TWRI\TWRI.FTL. The convention for the file extension of the LMT6 Package produced output file is designated as ‘FTL’ for ‘Flow-Transport Link’. If Fname is not specified (left blank) after the keyword ‘OUTPUT_FILE_NAME’, or if the entire record including the keyword is missing, the output file is assigned the default name RootName.FTL where RootName is whatever file name is assigned to the LMT6 Package input file. For example, if the input file to the LMT6 Package is named TEST1.LMT , then the name for the LMT6 Package produced output file is TEST1.FTL by default.

INFTL — is the unit number on which the LMT6 Package produced output file will be saved. A positive, unique integer must be used that has not been associated with any other file. If an invalid input is entered, an error message is written to the MODFLOW-2000 LIST output file and the program execution is terminated. If INFTL is not specified by the user, or if the entire record including the keyword is missing, the output file will be saved on the default unit number of 333.

Fheader — a character value that specifies the header structure of the LMT6 Package produced flow-transport link file. Only two input values are allowed (in either uppercase or lowercase):

•Standard – the standard header is saved, compatible with all versions of MT3D and MT3DMS since 1996. The flow-transport link file with the standard header supports those sink/source packages that have been part of MODFLOW since 1988 (MODFLOW-88), namely, Well, Drain, River, General Head Boundary, Recharge, Evapotranspiration. Note that the Time-Variant Specified Head (CHD) Package (Leake and Prudic, 1991) is automatically supported since its functionality is implemented through an internal flow package such as the Block-Centered Flow (BCF) Package. In addition, the Stream-Routing (STR) Package (Prudic, 1989) is supported if it is not used concurrently with the River Package in the same simulation. The standard format is not supported in MODFLOW-2005. If "Standard" is specified, MODFLOW-2005 will print a warning message and then use the Extended format.

•Extended – an extended header is saved, only recognized by MT3DMS Version 4.0 or later. The flow-transport link file with the extended header is capable of supporting most sink/source packages that have been added to MODFLOW-96 and MODFLOW-2000, such as the Specified Flow and Head Boundary (FHB) Package (Leake and Lilly, 1997) and the Reservoir (RES) Package (Fenske and others, 1996). In addition, the Stream-Routing (STR) Package can be supported along with the River Package in the same simulation.

If Fheader is not specified by the user, or if the entire record including the keyword is missing, Fheader will be assigned to Standard by default. Note that if the standard header is specified and a sink/source package that is not supported by the standard header is used in the flow simulation, an error message is written to the MODFLOW-2000 LIST output file and the program execution is terminated.

Fformat — is a character value that specifies the form of the LMT6 Package produced flow-transport link file. Only two input values are allowed (in either uppercase or lowercase):

•Unformatted – the flow-transport link file is saved as an unformatted (binary) file, compatible with all versions of MT3D and MT3DMS.

•Formatted – the flow-transport link file is saved as an ASCII (text) file with list-directed (free) format, which can only be read by MT3DMS Version 4.0 or later.

The default value is Unformatted if Fformat is not specified by the user or if the entire record including the keyword is missing. The unformatted file is preferable because it is much smaller in size than an equivalent ASCII text file. The ASCII text file should be used only when the user needs to check the contents of the file. An ASCII text file also may be necessary when the unformatted file produced by the MODFLOW-2000 executable code is not compatible with that of the MT3DMS executable code. This can happen in two cases: (a) when the MODFLOW-2000 and MT3DMS codes are compiled by two FORTRAN compilers that use incompatible styles for their unformatted files, or (b) when the two codes are run on different computer platforms such as UNIX based workstations and Microsoft Windows based personal computers. Whereas a file designated as ‘unformatted’ consists of binary characters, it differs from the so-called ‘true’ binary file available as a nonstandard extension in certain FORTRAN compilers such as Compaq Visual FORTRAN. The ‘true’ binary file format is somewhat more transportable between different compilers. The nonstandard binary file format is supported by MODFLOW-2000 since version 1.2 and MT3DMS since version 4.0.

For the new optional item PACKAGE_FLOWS, acceptable arguments to follow are either ALL or some combination of UZF, SFR, or LAK.  The order of UZF, SFR, or LAK does not matter.  When specified, flows associated with the respective package (e.g., UZF, etc.) will be written to the Flow-Transport Link file.  Otherwise, only those fluxes interacting with the groundwater (saturated) system are written, which in the case of UZF include recharge, groundwater ET, and spring discharge.