Contact Name

Sue Kasahara + Mark Messier.


The IoModules package provides the interface classes to the user to configure the job input/output. With the exception of the read of data from the MC reroot files, the actual I/O work is done by the underlying Persistency package.

See IoModules Overviews for a more complete overview.

Database Access


Configuring & Running

The input and output job modules are executed as part of a job path. One input job module is automatically loaded into the job path as part of every job. Therefore the user never has to add this to the job path explicitly. There can be only one input module, although it can be configured to read multiple streams in parallel from multiple input data files.

The input module configuration is described in the Input module section of the User Manual and in the Data Model and I/O chapter.

In contrast to the input module, the output module is optional, and is added to the job path as "Output::Put". For example:

    JobC j;
defines a job path whose only instruction is to execute the IoOutputModule "Put" method.

The output module is configured as described in the Data Model and I/O chapter of the User Manual. The most commonly used configuration options are to specify the data streams (TTrees) to be filled in the output file, and the name of the output file itself. For example:

loon[0] JobC j;
loon[1] j.Path.Create("Demo","Output::Put");
loon[2] j.Path("Demo").Mod("Output").Set("Streams=DaqSnarl,Cand");
loon[3] j.Path("Demo").Mod("Output").Set("FileName=recons.root");

Further Links

Sue Kasahara Last Modified: $Date: 2008/04/13 19:38:15 $