4/98
SED2D-WES Version 4.3 Beta
and output files. A SED2D-WES run control file is always required, and its name will be requested first. This is
the card image input for SED2D-WES described in this document. There are many other files that may or may not
be required. The user specifies which ones will be required for a particular run within the run control file (see the
description of the $L cards). Once the $L cards have been read, the program will continue to query the user for the
names of the other requested files. To run SED2D-WES in batch mode, the user may create a master file
containing the answers to the screen queries in the order that they are normally supplied when running in
interactive mode. The master file is redirected to the program in place of the standard input file (the screen). For
more information on file redirection refer to the operating system manual for your computer If the files specified
are not in the directory from which the program was launched, then the full path to the files must be specified.
Otherwise, the program will abort on input file reads.
Files created by the user (such as the SED2D-WES run control file) are usually created with an editor and
consequently use the ASCII character set. These files can be transferred back and forth from one computer to
another. This is handy when a "front end" computer is being used to create files that will eventually be passed to a
batch processing computer. On the other hand, files that are referred to as "binary" or "unformatted" files are
specific to the computer on which they were generated. These files cannot be transferred arbitrarily between
computing platforms. Since SED2D-WES requires binary solution files created by GFGEN and RMA2-WES, the
user should be aware that same type of computer should be used to run each of the models. This will ensure that
the binary files are compatible between runs.
18
WORKING DRAFT
Previous Page
