CMS ECAL Prompt Feedback Group Toyoko J. Orimoto, California Institute of Technology A Brief...
1
CMS ECAL Prompt Feedback Group Toyoko J. Orimoto, California Institute of Technology A Brief History: From GRUMM to First Beam GRUMM ~5M evt 32 SMs Mar Apr May June July Aug Sep Oct Nov CRUZET1 ~40M evt 36 SMs CRUZET2 ~30M evt 35 SMs CRUZET3 ~70M evt 36 SMs CRUZET4 ~62M evt 36 SMs + EE First LHC Data ~50 splash evts 36 SMs + EE CRAFT ~380M evt ~35 SMs + EE PFG is born! Continuing local and global commissioning activities throughout 2009 The Future of the ECAL PFG • Offline Analyses: PFG has sparked several offline studies, as a natural and necessary continuation of prompt observations • ECAL DPG Offline Analyses:Cosmics Analysis, Trigger, Noise/Problematic Channels, Timing, Stability • Data Quality Monitoring: We have worked with the ECAL DQM team to incorporate our studies into the official CMS DQM GUI. • Physics Validation Team: We will work with the new PVT to guarantee good data quality of data and Monte Carlo for physics analysis. • Commissioning Activities: The most important activities of this year are the commissioning of the ECAL endcap trigger and preshower detector, in addition to preparation for first collisions later this year. • Readiness for First Collisions: We have already started developing diagnostic tools for beam data and will continue our preparation to understand the detector with first collisions. ECAL PFG People • We started in March 2008, as a loose collection of ~5 people with a wide range of skills and experiences • Grew by summer 2008 to reach > 20 people, many expert by that time • Now we are ~15 active members with: 40% students, 20% postdocs, 40% more senior members • Many students have started their ECAL work with our group • Have at least one member “on duty” every day that data taking is planned, with increased support during global runs • Each normal working day, we typically had one shifter on duty, with more (~2 to 5) during global running periods ECAL Performance with Cosmics Data CRAFT ECAL Occupancy and Timing TOP BOTTOM CRAFT ECAL Energy Spectrum • High Energy Events from Bremsstrahlun g CRUZET event with 290 GeV cluster DT EB EE HCAL CRUZET4 Muon Showering in EB & EE • Throughout 2008, we have commissioned the detector with cosmic ray muon events. We have used the large cosmics dataset to understand problematic channels, debug the DAQ and trigger systems, synchronize ECAL with the rest of CMS, and have even sparked analyses studying photons from muon bremsstrahlung events. • Occupancy (left): higher occupancy in the top/bottom regions and also in EB- region where P5 shaft exists • Timing (right): measured in clock units (25 ns) wrt the settings for collisions; Clusters in the bottom are seen later wrt the top as a result of the time of flightl of the cosmic rays. TOP BOTTOM T i m i n g ( 1 U n i t = 2 5 n s ) ECAL Performance with First LHC Beam CMS 146 m TAN TCTV TCTH TCLP • In Sep 2008, CMS recorded first LHC beam events. The most interesting events for ECAL were the beam splash events, in which the beam was sent to closed collimators ~150m upstream of CMS. Beam Splash Event: ECAL Energy T i m i n g ( 1 U n i t = 2 5 n s ) Beam Splash ECAL Energy and Timing • More than 99% of ECAL active • ~200 TeV energy in EB+EE • Data is being used for understanding problematic channels, validation of intercalibration constants, and timing synchronization Beam Splash Correlations • Correlation between ECAL energy and measurements from beam loss monitors near CMS • The PFG members are in charge of: • Performing fast analyses to check properties of the data and assist with specific goals of technical or physics runs • Diagnosing and characterizing problems when they arise and answering requests from the experts at P5 • Deploying tools to achieve all of the above, in a coherent and documented fashion • Compiling a list of known problems and solutions Introduction to the ECAL Prompt Feedback Group • The ECAL PFG was formed in early 2008 with the aim of providing a close link between the commissioning, data acquisition, and data quality monitoring teams and the ECAL analysis community • The PFG works ~every day: not just during global runs but also during day- to-day ECAL operations
-
date post
23-Jan-2016 -
Category
Documents
-
view
215 -
download
0
Transcript of CMS ECAL Prompt Feedback Group Toyoko J. Orimoto, California Institute of Technology A Brief...
CMS ECAL Prompt Feedback GroupToyoko J. Orimoto, California Institute of Technology
A Brief History: From GRUMM to First Beam
GRUMM~5M evt32 SMs
QuickTime™ and a decompressor
are needed to see this picture.
Mar Apr May June July Aug Sep Oct Nov
CRUZET1~40M evt36 SMs
CRUZET2~30M evt35 SMs
CRUZET3~70M evt36 SMs
CRUZET4~62M evt
36 SMs + EE
First LHC Data~50 splash evts
36 SMs + EE
CRAFT~380M evt
~35 SMs + EE
PFG isborn!
Continuinglocal and
globalcommissioning
activitiesthroughout
2009
The Future of the ECAL PFG
• Offline Analyses: PFG has sparked several offline studies, as a natural and necessary continuation of prompt observations
• ECAL DPG Offline Analyses:Cosmics Analysis, Trigger, Noise/Problematic Channels, Timing, Stability
• Data Quality Monitoring: We have worked with the ECAL DQM team to incorporate our studies into the official CMS DQM GUI.
• Physics Validation Team: We will work with the new PVT to guarantee good data quality of data and Monte Carlo for physics analysis.
• Commissioning Activities: The most important activities of this year are the commissioning of the ECAL endcap trigger and preshower detector, in addition to preparation for first collisions later this year.
• Readiness for First Collisions: We have already started developing diagnostic tools for beam data and will continue our preparation to understand the detector with first collisions.
ECAL PFG People
• We started in March 2008, as a loose collection of ~5 people with a wide range of skills and experiences
• Grew by summer 2008 to reach > 20 people, many expert by that time
• Now we are ~15 active members with: 40% students, 20% postdocs, 40% more senior members
• Many students have started their ECAL work with our group
• Have at least one member “on duty” every day that data taking is planned, with increased support during global runs
• Each normal working day, we typically had one shifter on duty, with more (~2 to 5) during global running periods
ECAL Performance with Cosmics Data
CRAFT ECAL Occupancy and Timing
TOP BOTTOM
CRAFT ECAL Energy Spectrum
• High Energy Events from Bremsstrahlung
CRUZET event with 290 GeV cluster
DTDT
EBEB
EEEE
HCALHCAL
CRUZET4
Muon Showering in EB & EE• Throughout 2008, we have commissioned the detector with cosmic ray muon events. We have used the large cosmics dataset to understand problematic channels, debug the DAQ and trigger systems, synchronize ECAL with the rest of CMS, and have even sparked analyses studying photons from muon bremsstrahlung events.
• Occupancy (left): higher occupancy in the top/bottom regions and also in EB- region where P5 shaft exists
• Timing (right): measured in clock units (25 ns) wrt the settings for collisions; Clusters in the bottom are seen later wrt the top as a result of the time of flightl of the cosmic rays.
TOP BOTTOM
Tim
ing (1 U
nit =
25 n
s)
ECAL Performance with First LHC Beam
CMSCMS
146 m
TANTAN
TCTVTCTV
TCTHTCTH
TCLPTCLP
• In Sep 2008, CMS recorded first LHC beam events. The most interesting events for ECAL were the beam splash events, in which the beam was sent to closed collimators ~150m upstream of CMS.
Beam Splash Event: ECAL Energy
Tim
ing (1 U
nit =
25 n
s)
Beam Splash ECAL Energy and Timing
• More than 99% of ECAL active
• ~200 TeV energy in EB+EE
• Data is being used for understanding problematic channels, validation of intercalibration constants, and timing synchronization
Beam Splash Correlations
• Correlation between ECAL energy and measurements from beam loss monitors near CMS
• The PFG members are in charge of:
• Performing fast analyses to check properties of the data and assist with specific goals of technical or physics runs
• Diagnosing and characterizing problems when they arise and answering requests from the experts at P5
• Deploying tools to achieve all of the above, in a coherent and documented fashion
• Compiling a list of known problems and solutions
Introduction to the ECAL Prompt Feedback Group• The ECAL PFG was formed in early 2008 with the aim of providing a
close link between the commissioning, data acquisition, and data quality monitoring teams and the ECAL analysis community
• The PFG works ~every day: not just during global runs but also during day-to-day ECAL operations
