CSC New Year’s Resolutions for 2011

1. CSC New Year’s Resolutions for 2011  We had a terrific 2010, but Less than 0.01 of a “reasonable” Higgs discovery sample has been collected • Looking forward: • We can do better • We must not do worse • We should understand our common priorities • Out of priorities come action

2. Proposed top CSC priorities for 2011 CSC-TF improvements needed Withstand 2 more years of running Moving upgrades into production Optimize our contributions to DPG

3. 1. CSC-TF Improvements • Current efficiency plot: We will be losing 10% of events at high PT 1.2 < η < 2.1 A. Kropivnitskaya (UF) ~5% efficiency at low pT gives L1 rates ~8 kHz at L=1033 (up to 20 GeV threshold forecast) NB overlap region performance is worse

4. 2. Withstand 2 more years running • 98.5%96% slowly is the best scenario • Hardware • HV (auto resets, training?) • TMB 3.3v (fuses being replaced) • Water leaks (rack detection being upgraded) • Operations manpower • Fixes  almost problem-free detector? • Increasing use of automation, e.g. reset HV trips • Spread the load from (Greg, Misha, Armando, …)

5. 3. Moving upgrades into Production • Schedules are very tight – focus is required! • Building 904 factory by July 1? • Set up personnel plans “now” • Machine setup starts mid-Jan • Prototype + preproduction round • Additional parts procurement • Readiness Review • ME1/1 electronics repair • DCFEB prototype coming out ~weeks. Testing will be next challenge! • Dubna working on cabling, mechanical plans for shutdown

6. 4. Optimizing DPG Contributions • Numerous areas of need • L1 and HLT trigger performance, simulation improvements, code release validation, … • People are leaving (graduating etc.) • Tie DPG work strongly to physics analyses, e.g. • NB that CMS authorship now requires significant service work

7. Conclusions • It will have been an outstanding 2011 if a year from now we have accomplished these goals: • CSC trigger efficiency is high, L1 rates are acceptable • Detector is still in good shape, operations on an even keel • Upgrades are steadily producing ME4/2 chambers and ME1/1 electronics • Detector monitoring and software (DPG) have all the bases covered • Detailed to-do lists and some references are in the backup slides

8. Backup slides

9. References • Latest CSC-TF status report (7-Dec-2010) at http://indico.cern.ch/conferenceDisplay.py?confId=115477 • Richard Loveless and Darien Wood latest updates on the ME4/2 and ME1/1 upgrades (7-Dec-2010) at http://indico.cern.ch/conferenceDisplay.py?confId=115519 • My debriefing from Zurich (10-Nov-2010) at http://indico.cern.ch/conferenceDisplay.py?confId=113118 • Tim Cox DPG overview (14-Jun-2010) at http://indico.cern.ch/conferenceDisplay.py?confId=97906 • Ivan Mikulec muon trigger rates (18-Nov-2010 TSG) athttp://indico.cern.ch/conferenceDisplay.py?confId=79127

10. Greg/Misha detailed list • HV trips: • Handling automation • Gradually move from common HV for all CSCs (3600 V) to individual chamber HV working point,   then to individual HV channel working point. • Improve the interface to the Configuration database • masking problem boards • global timing shifts • who is masked?" button • I have a list of other improvements I'd like to see on this interface... • Define what needs to come out of online databases into offline.  Apparently the use cases must be defined before the tools can be developed... • Implement tools to pull online database information into offline. • Develop analysis of data in Expert System data warehouse • First use of automated action based on analysis of data in the "warehouse" of the Expert System • Implement "correct" power-up procedure (crates, then chambers), using different channels of Maratons • Debug and fix CSC failures to change states in Run Control • Maintain vigilance to access to address faulty boards • can we help Misha to identify what the problems are? (replacement is not always the answer) • Begin use of firmware repository • Can we create redundancy to my position?  Tim's position?  Armando's position? • Can we move from CSC DQM shifts -> CMS Offline shifts? • Is it possible to have a tool ("automate") looking at the time dependence of things • Be more regular about calibration runs.  Time dependence of these things... • At the beginning of a run identify ALCTs with wrong configuration. • If it is related to AFEBs lost LV - fix it, if it is "hot chamber" (test strip problem) - find a way to get rid of hot strips.

11. Tim 1 of 3

12. Tim 2 of 3

13. Tim 3 of 3

14. Armando detailed list • Perform systematic and quantitative studies of system performance and allocate appropriate resources • Form dedicated teams to investigate all issues concerning with system “stability and aging” and in charge of proposing “consolidation” actions for further running. Are we happy with what we have? I personally think we can/should do better and this should be done before we have the opportunity to access disks and do repairs. • electronics, • mechanics and infrastructure, • luminosity, backgrounds, neutrons, PU, SEU • Review/redefine roles (with level of priority) and responsibilities within Operations and DPG • at institute level (more efficient) or individuals (easier) • formalize mandatory participation of new comers • Maintain/reinforce focus on physics (best way to strengthen links with POG/PAG) • to get grad students more interested/involved • biweekly/montly report on CMS publication? • ME4/2 and ME1/1 upgrades are a great opportunity for students to work on hardware. Promote/advertize a sizeable “physicists component” in such projects.

15. Jay detailed list • Ops: • Find a sidekick for Greg (computers &software, CEO training, etc.) • Improve data monitoring shift procedure and training • How to continually monitor pre- and post-firing of L1 muon trigger? • Configuration database additions (bad/hot channels,…) • Implement CLCT muonic timing, narrow ALCT-CLCT coincidence • Implement duplication of events in TMB for closely spaced L1As • Improve local muon trigger efficiency in ME1/1 for high luminosity • DPG • Improve CSC-TF patterns for high efficiency at plateau, low efficiency at threshold • Find someone to take on some of Tim’s jobs • Code release validation • Simulation improvements, e.g. chamber gains • Add to and review the performance paper • HLT contact person. How efficient is the muon HLT?? • Study local trigger CLCT patterns and improve them by station • Trigger bit-wise emulation - put into L1 trigger DQM • Neutron runs compare hit rates versus simulation • dE/dX reconstruction and gain tracking • Improve poor “muon jets” performance • Upgrade • Identify all key factory personnel • Parts flow for ME4/2 chambers • Create software for testing of new cathode electronics • LVMB modifications • Alignment • Use boosted Z’s to investigate high Pt muon systematics and position shifts

16. Muons From Ivan Mikulec, 18-Nov-2010 TSG Rates in kHz I. Mikulec Might need to go to L1_SingleMu20 at 5e33 Probably can use L1_DoubleMu5 at 5e33 (see Zoltans talk) but careful about pile-up! See next slide for some other possibilities 16

18. New Year’s Resolutions