1 Preparazione analisi Global Runs ienza dal “November Global Run” (“GREN”): ~ 2 settimane di data taking => running conditions (non sempre stabili con : DT (whole YB0), RPC (baseline: YB0/+1/+2 Sect4/5/10/11), CSC (YE+2, ME2+ME3) HCAL, ECAL DTTF,CSCF trigger & readout ] azione/schedula prossimi Global runs: - ~fine Febbraio (3 wheels? Alcuni moduli del Tracker?) - Aprile (full Tracker?) - Maggio: CMS chiuso, 4 weeks data taking, B on
25
Embed
1 Preparazione analisi Global Runs Esperienza dal November Global Run (GREN): ~ 2 settimane di data taking [ => running conditions (non sempre stabili.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
Preparazione analisi Global Runs
Esperienza dal “November Global Run” (“GREN”): ~ 2 settimane di data taking [ => running conditions (non sempre stabili con : DT (whole YB0), RPC (baseline: YB0/+1/+2 Sect4/5/10/11), CSC (YE+2, ME2+ME3) HCAL, ECAL
DTTF,CSCF trigger & readout ]
Preparazione/schedula prossimi Global runs: - ~fine Febbraio (3 wheels? Alcuni moduli del Tracker?) - Aprile (full Tracker?) - Maggio: CMS chiuso, 4 weeks data taking, B on
2
Next Global Runs Tentative schedule
(Acosta/Camporesi, Dec.CMSweek)
3
“GREN” ~20 M triggers very useful for - syncronization, calibration, alignment - reconstruction optimization: local/global - trigger` studies - correlation between different detectors
In generale, e’ stata una ottima “palestra”per le DT
Alcuni esempi…
4
Synchronization: BX id for HH triggersTriggering Sectors: 3,4,5 & 9, 10,11
Sector 11
Sector 10
Sector 3
Sector 4 Sector 5
Sector 9
5
Prompt-Offline time calibration (DT+RPC+HCAL triggers)
-MB1-MB2-MB3-MB4
6
Prompt- Local Reconstruction checks:Hit residuals (dominated by uncertainty due to muon time of arrival within the BX window):
Run30625
-MB1-MB2-MB3-MB4
7
DT in RPC-triggered Events:[ Run 30333 ;14804 RPC Triggers in Sectors 9,10,11 & 3)
Trigger checks: DT vs RPC
8
Correlation between DTTF & TDC data
No bending angle in MB3
Track angleTrack position
Tri
gg
er p
osi
tio
n MB1
MB2
MB3
MB4
position plot shiftedfor MB2 (understood)
9
Global reconstruction Multiplicity of associated hits to global tracks (linking 2 or more stations):
Run 30625
10
Global reconstruction
Run 30514, ~ 107,000 triggers, ~45’ data taking, ~ 40 Hz
11
Extrapolations to calos
Run 30514
~20% (~8 Hz)
~40%
Extrapolation used in HLT streams
12
DT↔ HCAL correlations
“Analysis of HCAL-mip triggers using DT tracks “, P.De Barbaro et al.
GREx documentation (sw, config files, db info…) pages will be regularly linked from the general DT-DPG twiki: https: //twiki.cern.ch/twiki/bin/view/CMS/MuonDPGDT
14
Dati: trasferiti e registrati a Legnaro
promptCalib +reco checks here
Output to CMSOrcoff (in anon-authomatizedway)
Prompt “official” reco@ CAF then Reco, DTEcal/DTHcal
streams ect.. to others T1/T2 tiers
~10 h latency
Dati analizzabili dal cluster lxcmssrvN (N=4,6) di Padova:‘working example’ su : /raid3/share/GRENanalysis/DTAnalyzer_GREN_YB0_Frontier_LNL.cfg
15
Preparazione Global Runs futuri
- Utilizzo dati di allineamento (survey + allineamenti ‘interni’ alle camere)
tests sui dati gia’ esistenti del GREN inserimento in DB ufficiale letto da CMSSW (analogamente a quanto gia’ fatto per i test pulse di calibrazione temporale)
- Studio sui dati esistenti delle estrapolazioni al tracker (rates, possibili selezioni di triggers); studio delle estrapolazioni ‘sopra-sotto’;
- Essere pronti a “inglobare” i dati del Tracker nell’ analisi contatto/collaborazione col gruppo di ricostruzione del Tracker (Patrizia?/ Boris? / altri…?)
16
Alignment checks on GREN data
Using data producedfrom Santander Group(P.Martinez et al.)From commissioning &Quality Control Check data