The concept of an output mode in EOSGX is tied to the behavior of the run modes. Unlike the input modes, which are more or less independent of the choice of run mode, the output mode is really an integral part of the run mode functionality. With two important exceptions, the output modes are explicitly tied to the run mode assignment, and are more descriptive than indicative of new program behavior.
In practice, the choice of an output mode is only of importance in the DSIM and FSIM run modes. These are the two modes that produce simulated TAS event output from GEANT; i.e. these modes cause certain data analysis tables such as the HITS table to be filled by the GEANT part of the simulation code. The data tables filled by GEANT then become the input for other data analysis routines, such as the TPC tracker. A standalone simulation (NORM run mode) does not write TAS table output at all, and is automatically assigned to the NORM output mode. In READ run mode, the output is always (and only) to the GEANT_TRACKS table, so that READ run mode ignores an output mode assignment.
However, two choices are available in the DSIM and FSIM run modes, which output to TAS data tables (the HITS or DTS_RAW tables) or to a *.BDF data file, in the case of FSIM mode. These choices are: