Triggerlines for the study of the tracking efficiency
relies on Rec merge request Rec!2496 (merged) and Phys merge request Phys!969 (merged), LHCb!3246 (merged)
cc @peilian
-
DiMuonTrackEfficiency.py
selects events with a tag and a probe track with the Tagging lines, and events where the probe machtes a long track with the Matching lines, for two different charges of the probe and for the SciFiUT line (VeloMuon probe) and Velo line (SciFiUT probe). Further lines will be added. The specific cuts can be adaptes and are currently being optimised (credit also goes to @gifrau) -
probe_muons.py
is called by DiMuonTrackEfficiency.py,hlt2_probetracks.py
is called by probe_muons.py,protoparticles.py
is called by hlt2_probetracks.py - these set up the necessary standalone reconstruction sequence for the probe tracks using the algorithms in Rec!2496 (merged) (credit also goes to @gifrau) -
truth_matching.py
change to include muon hits in the truth matching -
particle_moving.py
: lines to raise ValueError("Could not find unique LHCb::Particle outputs of {}". commented out -
__init__.py
needs to register the multiple use of MuonIDAlgLite by hand due to this error: ERROR LHCb::Hlt::PackedData::Writer:: Requested to persist link to /Event/HLT2/MuonIDAlgLite#1/MuonTrackLocation but no ID is registered for it in the ANNSvc! StatusCode=FAILURE -
hlt2_trackeff_test.py
is used to test the lines and create a dst file containing the information about events that passed either of the trigger lines. This doubles as a test for Rec!2496 (merged)