EF wrappers

for new Moore/Muid
status and plans

The Muon EF group

people currently involved:

Sergio Grancagnolo, Stefania Spagnolo

EF wrappers for new Moore/Muid
status

A new package just setup: Trigger/TrigAlgorithms/TrigMuonEF (still empty)

it will host 4 HLTalgorithms:

TrigMuonEFSegmentFinder wrapper for the offline tool MooSegmentCombinationFinder (invoqued with vector of pointers to prd collections) DONE

TrigMuonEFTrackFinder wrapper for the offline tool MuonCombiTrackMaker (invoqued with vector of pointers to segment combination) DONE (for the moment in a unique Hltalgo handling segments)

TrigMuonEFExtrapolator wrapper TO BE DONE for MuidBackTracker

TrigMuonEFCombiner wrapper TO BE DONE for the main tool of MuidCB (COMING SOON ?)

Most work is just in configuration - This will be simplified by a proposal by Martin (under implementation) that will allow to clone the offline configuration of the many tools used by the basic tools

A few problems observed and reported to the offline community (still some recording to StoreGate of intermediate objects to be disabled for the HLT) - Good cooperation, that will improve as soon as 14.0.0 is out !

The reconstruction up to MS Tracks works (tried on single muons produced with 12.x.x or Higgs to 4 leptons with 13.0.40.1

checking roughly the performance: some problem in the EC (reconstructed pt crazy, while standard TrigMoore and LVL2 seed are ok) ... any configuration problem ? to be sorted out with offline group

EF wrappers for new Moore/Muid
plans

Define new Trigger Elements and Sequences in the trigger menu in order to run concurrently old and new (even before full implementation) EF

we'll deliver a minimal running version soon in the 14.x.0 nightlies

Implement in the first step (segment finding) of the new chain an optimal data access schema:

linked to the undergoing discussion on EF/offline converters and/or conversion tools

Write AOD for exchange between the HLTalgorithms in the new chain and for recording of the trigger result (revise the current muon EF AOD)

related discussion started also in the context of the trigger EDM workshop of ~1month ago

Implement new (almost dummy) hypothesis algorithms to allow decision(rejection or the RoI) at each step

Build minimal validation tools for the migration phase (to be superseeded by the appropriate/standard procedures later on)

monitor performance

monitor cpu time

2008-02-07T11:01:11