Manual Page for Command >>>> EXECUTABLE


Syntax
>>>> EXECUTABLE: FILE (BEFORE/AFTER)

Parent Command
>>> PEST

Subcommand
-

Description
iTOUGH2 capabilities can be applied to non-TOUGH2 models using the PEST interface. The user-supplied model must be an executable that can be run from a system command prompt. The system command can also be a script of batch file, in which multiple models can be combined. The model must be able to be executed without user interference. It must get its input through one or multiple ASCII text files, and write its output to one or multiple ASCII text files. Communication between itough2 and the model's input and output occurs through PEST-style template and instruction files, respectively.

The user-supplied model can be run by itself, before (default) or after (keyword AFTER) a TOUGH2 run. The latter two options are useful for estimating parameters that relate to pre- or postprocessors of TOUGH2, respectively. The name of the executable, script, or batch file is provided following the colon. If the executable name contains spaces, the command line must be in quotes. Under Unix, it is recommended to add the keyword FILE to the command line or on a separate line, so the executable is automatically copied to the temporary directory. Examples include:


>>>> EXECUTABLE : myModel.exe
>>>> EXECUTABLE : Run-ModelA-and-ModelB.bat
>>>> EXECUTABLE FILE : UnixScript.sh
>>>> EXECUTABLE : "a.out < input > output"
>>>> EXECUTABLE : "octave myMatlabCode.m"
>>>> EXECUTABLE : "nohup matlab -r -nodesktop -nosplash -nojava < myMatlabCode.m"

Example
> COMPUTATION
>> OPTION
>>> PEST
>>>> EXECUTABLE FILE : this-is-not-TOUGH.exe
>>>> TEMPLATE : 1
input.tpl input.txt
>>>> INSTRUCTION : 1
output.ins output.txt
<<<<
on Unix systems, add following statements for all input files:
FILE: input.tpl
FILE: output.ins
FILE: a.out
<<<
<<

See Also
>>>> INSTRUCTION, >>>> TEMPLATE


Back to Command Index

Page updated: April 15, 2010