60 likes | 205 Views
MuonIdentification Present Status. Athena implementation : Inputs from Moore, Calo Reco and iPat Athena modules: MuidInit : gets tracks from Muon Reconstruction (Moore) and associates the truth from KINE bank MuidStandAlone : muon tracks are propagated to the vertex
E N D
MuonIdentification Present Status • Athena implementation : Inputs from Moore, Calo Reco and iPat • Athena modules: • MuidInit : • gets tracks from Muon Reconstruction (Moore) and associates the truth from KINE bank • MuidStandAlone: • muon tracks are propagated to the vertex • multiple scattering parameterised as scattering planes in calorimeters • energy loss from truth and/or from Calo Reconstruction (Tile, HECLAr and EMLAr CaloCells from CaloUtils/CaloEvent packages) • refit at vertex • MuidComb: • gets MuidTracks from previous step and ID reconstructed tracks (iPat) • Muon/ID tracks matches with a c2 cut-off • Combined fit
Reconstructed Object Flow Algorithms TDS Moore Tracks MuidInit MuidTracks status muon CaloClusters MuidStandAlone MuidTracks status standalone ID iPatTracks MuidComb MuidTracks status combined
MuonIdentification reorganisation (Alan) • Motivation –The work in progress on low energy muons identification (Natasha, Monica, Theodota) needs to get into the repository release structure. • MuID now contains already 27 classes! Athena algorithms with different features/goals muidAlgs In the ID there is a splitting between xxxAlgs and xxxUtils muidStatistics muidEvent Events for reconstruction
Possible solutions (Alan) under Reconstruction/MuonIdentification muidAlgs muidRec softMuRec muidRec softMuRec muidStatistics muidStatistics muidEvent muidEvent
Third possibility under Reconstruction muidAlgs muidRec softMuRec muidRec softMuRec muidStatistics muidStatistics muidEvent muidEvent
Keeping muidUtils ? Probably too complicated! muidAlgs muidUtils muidRec softMuRec muidUtils muidAlgs softMuAlgs muidStatistics muidStatistics muidEvent muidEvent