Input formatting is described for each of the cards for each operational mode of STOMP. However, the following information and associated graphic (Figure 1) provide general guidelines for building a STOMP input file.
The principal input file is a text file which must be named input for proper execution. (1)
The input file can be created or modified with any text editor.
Unit inputs can be any combination of the recognized units; where spaces between units imply multiplication of units and only a single division symbol can be used within the character string. The “^” is used to represent exponential notation in the input file (e.g., m^2 = m2).
Figure 1. Input File Formatting Example
Internally, STOMP uses the International System of Units (SI); where, the base units are length in meters (m), time in seconds (s), mass in kilograms (kg), temperature in degrees Celsius (˚C), and molar mass in kilomole (kmol). However, unit inputs can be any combination of the recognized units and need not be consistent within an input file. The user may specify output units that are different from those used for input, and they need not be consistent (for example, one may request output for length in meters and pressure in psi).
Some cards are required and others are optional or unused. The number of required cards depends on the operational mode. If an attempt is made to execute the simulator using an input file with an incomplete set of required cards, an error message will be generated and the code execution will stop.
Optional cards are used to specify STOMP capabilities that may be required to execute a particular problem or generate desired output data. These cards are considered optional, because the capabilities accessed through these cards are not needed to execute the code. Execution of the simulator with input files that have an incomplete set of optional cards yields warning messages, which will note the missing optional cards but allow the execution to continue.
Input file card descriptions, syntax, and examples are provided for each card and each operational mode of STOMP. To determine which operational model to apply to a specific problem, please see the section on governing equations and operational modes.