Collaboration diagram for Event Backend and I/O:
|
Modules | |
| Offline I/O | |
| Aires reading | |
| Corsika reading | |
| Conex reading | |
| Seneca reading | |
| CDAS I/O | |
| FDAS I/O | |
Detailed Description
The Event backend includes the codes for reading and writing real and simulated data in various formats as well as reading generator-level simulated showers produced by different air shower simulation programs.The event representation in memory is decoupled from the representation on disk. When a request is made to write event contents to file, the data are transferred through a so-called file interface to a data structure which is instrumented with machinery for serialization, and which can be optimized for access speed. Similarly, when data are requested from file, a file interface reads the data and relays it to the appropriate part of the event interface.At present, serialization is implemented using the ROOT, though the design is intended to allow for relatively straightforward changes of serialization machinery.A set of simple-to-use input/output modules are provided to allow users to transfer all or part of the event from memory to a file at any stage in the processing, and to reload the event and continue processing from that point onward. These modules are built upon a set of utilities to support the multi-format reading and writing required to deal with different raw event and monitoring formats as well as the different formats used by the various air shower simulation packages.Here is a diagram of the event input/output mechanism.
