PtLUT
Run Analized
66615 |
66637 |
66676 |
66692 |
66703 |
66706 |
66711 |
66714 |
66716 |
66720 |
66722 |
66733 |
66739 |
66740 |
66746 |
66748 |
66783 |
67122 |
67126 |
67128 |
67139 |
67141 |
67147 |
67173 |
67225 |
67534 |
67539 |
67541 |
67548 |
67810 |
67818 |
68124 |
68141 |
68264 |
68273 |
68276 |
68279 |
68288 |
68665 |
68926 |
68949 |
|
|
|
|
|
|
|
|
|
For more details, please have a look at
Yuriy's run registry
Reco'd events
- Sample: /Cosmics/Commissioning08_CRAFT_V3P_SuperPointing_v3/RECO
Reco'd events |
225036 |
Total Number of Muons |
431566 |
Number of Global Muons |
250872 |
Number of Tracker Muons |
324888 |
Number of Standalone Muons |
405107 |
Total Number of Muons (in CSC) |
15766 |
Number of Global Muons (in CSC) |
5067 |
Number of Tracker Muons (in CSC) |
7067 |
Number of Standalone Muons (in CSC) |
15766 |
- Basic plots on reconstructed muons:
- LEGENDA
- PINK: ALL RECO'd EVENTS
RED: MUONS IN THE CSC ETA WINDOW (0.9 < ETA < 2.4)
BLUE: MUONS ALSO RECO'd IN THE TRACKER
- Observations
- - By zooming into the Z distribution, one can observe that the events with eta in the CSC region are not peaking at zero, but are a bit displaced
* Inner X vs Y:
* outer X vs Y:
* Inner R vs Z:
* outer R vs Z:
Raw events
- From the associated Raw Digi in the reco'd sample
- Basic plots on raw tracks:
Pt Raw CSCTF vs Pt Reco'd muons
In order to match the information coming from the CSCTF to the correspondent reconstructed track, I have been using the phi and eta coming from the rechits.
Given a reco'd track, the information of the rechit closest to the key station and key layer is accessed and used as phi and eta for the muon.
For the CSCTF track the phi and eta coming out from the LUT are used. As observed in plot phiRaw-chain.png the phi variable ranges from 0->62 degrees and
it is defined inside a sector. To convert the CSCTF phi, PhiTF, in a range from [0,2Pi], I used the following formula:
fmod( PhiTF + ((sector-1)*PI/3) + (PI/12), 2*PI)
- More detail about the conversion are given in
PhiTest Twiki page.
Observations:
- The peak centered at 0 come from the matching between the reco'd track and correct CSCTF track ("signal").
- The spread bumps on the sides comes from the matching between the reco'd track and the wrong CSCTF tracks ("background")
- Eta has a better resolution than Phi. Possible issues with ME 1/1. Producing the scatter plot of Delta Phi vs Eta (from CSCTF) the resolution of Delta Phi worsen as the eta increases.
- As windows for the selection of the final events I used [EtaRechit-EtaTF < 0.5] and [PhiRechit-PhiTF < 0.5]. With this selection applied, I produced the scatter plot, Pt Raw (from the CSCTF) Vs Pt Reco'd muon. To better visualize the outcome, the profile along the Pt Raw is also depicted (right plot).
- Observation
- - While the definition of Pt LUT validation has not been established yet, one can observe, in particular from the profile plot, that the CSCTF seems to pick the "correct" transverse momentum range, i.e. for small value of reco'd muon Pt, the CSCTF assigns small value of Pt in the correct range for the correspondent raw track. Remember that the output of the CSCTF for Pt (as well as for Eta and Phi) is binned and not a continuous distribution.
- Remark
- - No additional cuts on the quality of the raw track or on direction of the track have been applied.
- Remark
- - Since the charge from the CSCTF and the from the reconstructed muons does not always agree, as charge value I have been using the one returned from the reconstructed muons
PtReco dependencies
In order to parametrize the Pt coming out from the LUT, we plan to use the data from the CRAFT run and we need to look at the PtReco dependence of all possible variables we measure from the SP.
- PtReco as a function of DeltaPhi12:
- PtReco as a function of DeltaPhi23:
- Remark
- - DeltaPhi12 and DeltaPhi23 are reported in bit values (respectively 8 bits and 4 bits)
--
GianPieroDiGiovanni - 18 Nov 2008