Moore reconstruction and MuonID

Download Report

Transcript Moore reconstruction and MuonID

and the HLT
Michela Biglietti (Universita’ di Napoli-Federico II)
Gabriella Cataldi (INFN Lecce)
1
Standard Moore flow

MooAlgs
RPC/TGC digits
MooMakePhiSegments
PhiSegments

MooMakeRZSegments
MDT digits
MooMakeRoads
CrudeRZSegments 
MooRoads
MooMakeiPatTracks
MooStatistics
MooiPatTracks
MooMakeNtuples
Ntuples
2
Each step is
driven by an
Athena topalgorithm
Transient
objects are
passed via
TDS/StoreGate
Independent
algorithms, the
only coupling is
through the
transient objects
Reconstruction
Strategy
 Searches for  regions of
activity
 From the RPC/TGC 
measurements “- Segments” are
created
 Searches for R-Z regions of
activity
 For each “-Segment”, the
associated MDTs is found
and a “crude” RZ Segments
is built
(essentially collections of z hits) .
3
Reconstruction Strategy
 Pattern recognition and
outer Roads

4
–
Inside MDTs the drift distance is calculated
from the drift time, by applying various
corrections on it (TOF, second coordinate,
propagation along the wire, Lorenz effect).
From the 4 tangential lines the best one is
found.
–
All the “MDT segments” of the O station are
combined with those of the M layer. The MDT
hits of each combination are added to the phihits of the “Phi Segment”, forming “outer”
track candidates. All the successfully fitted MDT mutilayer
candidates are kept for further processing.
Final tracks
associate inner station MDT hits. A “final” track is
defined
 The successful “outer” track is subsequently used to
 as a successfully fitted collection of trigger hits and
of MDT hits from at least two layers.
Moore structure
Athena algorithms with
different features/goals
Moore is a container
run-time
plug in differents algos in order
to build the reconstruction chain.
MooLVL2Algs
MooAlgs
MooStatistics
MooAlgs_n
MooEvent
5
 MooAlgs contains the standard
sequence of Algorithms:
MooMakePhiSegments
MooMakeRZSegments
MooMakeRoads
MooMakeTracks
 MooLVL2Algs contain a possible
seeding approach
MooMakePhiSegmentLVL2
MooMakeRZSegmentLVL2
Events for reconstruction
MooLVL2Algs strategy
run atrig
only on barrel
trigout10GeV.txt
ASCI files
trigout20GeV.txt
…..
…..
…..
Set-up the logic link:
TestRelease/… /run/Persint.out … /… /trigoutxxx.txt
run athena with the appropriate jobOptions.txt
RPC digits
MooMakePhiSegmentLVL2
PhiSegment
MooMakeRZSegmentLVL2
MDT digits
RZSegmentMap
How to run Moore and MooLVL2Algs Documentation in:
http://people.na.infn.it/~bigliett/moore/MooreDoc/MooreDoc/
6
 MooLVL2Algs
outputs are:
PhiSegments
RZSegments
 In order to perform a
fit the standard Algorithms
MooAlgs must be plugged
in the sequence
MooMakePhiSegmentLVL2
MooMakeRZSegmentLVL2
MooMakeRoads
MooMakeTracks
7
First need:
 If we want to have the seeded Moore in the HLT
environment we need:
 MooAlgs
 MooLVL2Algs
in HLT
First step:
 MooAlgs in HLT assuming that the sequence is always
valid, and accessing to all the event, i.e Standard Moore running.
No use of TriggerElements.
8
First step: MooAlgs in HLT
 Creation of a new subpackage
 In MuonSpectrometer/Moore ( Is this the right place ?)
 MooEFAlgs
In MooEFAlgs the
selection/seeding
algorithms will also
be included
MooTopAlg.cxx
MooTopAlg.h
...
private:
// Pointers to sub-algoritms
MooMakePhiSegments * m_MooMakePhiSegmentsAlgs;
MooMakeCrudeRZSegments * m_MooMakeCrudeRZSegmentsAlgs;
MooMakeRoads * m_MooMakeRoadsAlgs;
MooMakeiPatTracks * m_MooMakeiPatTracksAlgs;
// initialize and execute methods for subalgs
template<class T> StatusCode initializeAlgs(std::string, T* );
template<class T> void executeAlgs(T*);
...
bool MooTopAlg::execHLTAlgorithm(TriggerElement* TEout){
executeAlgs(&m_MooMakePhiSegmentsAlgs);
executeAlgs(&m_MooMakeCrudeRZSegmentsAlgs);
executeAlgs(&m_MooMakeRoadsAlgs);
executeAlgs(&m_MooMakeiPatTracksAlgs);
9
//Let's suppose Moore always validates the sequence...
log << MSG::INFO << "Trigger Element is active : " << TEout->label() << endreq;
TEout->SetActive(true);
return true; }
How to proceed ?
 Our understanding is that NOW we can access the Offline
Identifiers of RPC selected by LVL1 Trigger.
 Keeping in mind that in future we will use LVL2 output, can we
access RoI in terms of Offline Identifiers from the LVL1 ? If
yes, how?
10
How to seed MooLVL2Algs.
 As it is now
 MooLVL2Algs are seeded with the list of HitsOnTrack from LVL2.
RPC hits
MDT hits
 MooLVL2Algs work with Old EDM layout M geometry.
 In the future (personal opinion)
 MooLVL2Algs for HLT should use as input the RoI (eta, phi) and the
pt from LVL2 (in order to confirm or reject their estimate),
opening a Region of Interest around the track, and performing the
PhiSegment, RZSegment search, as for standard Moore, in a limited
region.
 MooLVL2Algs seeded with list of HitsOnTrack will be useful for
comparison of results.
11
10GeV
m-
MooLVL2Algs
 Same dataset used for MooAlgs MooLVL2Algs
 The 2 different sets of algos are chained together
 Fit results from the same sample of events are
directly compared
counts
counts
Hits comparison
10GeV
m-
MooLVL2Algs
MooAlgs
MooAlgs
N associated (MDT hits)
Plans for testing a more general hit addition
procedure
12
N associated (RPC hits)
counts
c2
1TeV
m-
counts
MooLVL2Algs
10GeV
m-
MooLVL2Algs
c2
MooAlgs
c2
13
counts
pull
10GeV
counts
1/pT
10GeV
m-
mMooLVL2Algs
MooAlgs
1/pT pull
1/pT pull
14
counts
resolution
10GeV
counts
pT
m-
10GeV
m-
MooLVL2Algs
MooAlgs
pT resolution
pT resolution
15
16