Event Data Model Generic relationship between reconstructed data

Event Data Model Generic relationship between reconstructed data and MC Hits n n Navigation always via associator Data model could be optimised later by introduction of additional navigation classes l Transparent to applications 2. . N Tr. Track MCParticle Attributes Operations 1 Tr. Measurement Attributes Operations OTHit Tr. Track. MCParticle. Associator MCHit. Base MCTracking. Hit 1 Attributes Operations 1 OTDigi Attributes Operations MCOTDigi

Spillover events u Definitions: n Pileup: several events from same beam crossing Combination done by simply adding MC Hits of underlying events to the physics event l Requires no changes to digitisation code l Implemented in both Brunel and SICB l n Spillover: events from previous or subsequent beam crossing Combination must preserve 25 ns timing offset l Digitisation must know what to do with hits that are 25 nd early/late l Ø Sub-detector specific l Not implemented in SICB or Brunel Ø I/O for additional events trivial with Gaudi Ø Sub-detector digitisation code must be rewritten (if spillover is relevant)

Spillover events in Gaudi Event. Selector /Event /MCNext Spillover Selector. Next 2 Spillover Selector. Prev 2 /MCNext /MCPrev /Raw /Rec Transient Event Data Spillover. Selector. Next. Time. Offset = 25*ns; Spillover. Selector. Next 2. Time. Offset = 50*ns; Spillover. Selector. Prev. Time. Offset = -25*ns; Spillover. Selector. Prev 2. Time. Offset = -50*ns; xx. Digi