1 / 25

Preparazione analisi Global Runs

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)

stamos
Download Presentation

Preparazione analisi Global Runs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation 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 triggers Triggering Sectors: 3,4,5 & 9, 10,11 Sector 3 Sector 4 Sector 5 Sector 9 Sector 10 Sector 11

  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. Trigger checks: DT vs RPC DT in RPC-triggered Events: [ Run 30333 ;14804 RPC Triggers in Sectors 9,10,11 & 3)

  8. Correlation between DTTF & TDC data position plot shifted for MB2 (understood) MB1 Trigger position No bending angle in MB3 MB2 MB3 MB4 Track position Track angle

  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 ~20% (~8 Hz) Run 30514 ~40% Extrapolation used in HLT streams

  12. DT↔ HCAL correlations Usage of DT info from other detectors Run 30205, 8,000 Hcal mip triggers DT Eta tower prediction DT Phi tower prediction HCAL Phi tower index HCAL Eta tower index “Analysis of HCAL-mip triggers using DT tracks “, P.De Barbaro et al.

  13. GREx- sw documentation 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 https: //twiki.cern.ch/twiki/bin/view/CMS/DTanalysisGR ….

  14. Dati: trasferiti e registrati a Legnaro prompt Calib + reco checks here Output to CMS Orcoff (in a non-authomatized way) ~10 h latency Prompt “official” reco @ CAF then Reco, DTEcal/DTHcal streams ect.. to others T1/T2 tiers 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 produced from Santander Group (P.Martinez et al.) From commissioning & Quality Control Check data http: //cmsdoc.cern.ch/cms/MUON/ alignment/DTinternal/main.html [ YB0 Sectors: 3, 9, 10 & 11; not all chambers available at moment ] Some **very** preliminary Results (Alicia, U.G.) (next slides)

  17. “Internal Alignment”: GREN Run 30625 MB2 MB1 MB4 MB3 Nominal position Using alignment DB YB0, Sect 3 MB4: no correction available

  18. Internal alignment YB0, Sect 9

  19. Internal alignment YB0, Sect 10

  20. Internal alignment YB0, Sect 11

  21. Checks of survey data: alignm.between chambers • - Observed • relative mis-alignments • between chambers • w.r.t. nominal geometry • Correlate with survey measurements (to be done) • Insert data in DB; needed for • correct trigger DTTF behaviour as soon as we want to • implement pointing LUT’s (e.g. to Tracker) for next Global Runs (next slides)

  22. Alignment between chambers YB0, all sectors ( GREN Run 30625) : Extrapolations: MB1 MB2 MB1 MB3 MB1 MB4 MB2 MB1

  23. Alignment : YB0 Sect 3,4 & 5 Extrapolations: MB1 MB2 MB1 MB3 MB1 MB4 MB2 MB1

  24. Alignment : YB0 Sect 9, 10 & 11 Extrapolations: MB1 MB2 MB1 MB3 MB1 MB4 MB2 MB1

  25. Confronto dati -MC  Ripetere le analisi di MTCC (su tutto il detector!) Muon spectra & mu+/mu- ratio

More Related