70 likes | 191 Views
New organization of Muon run coordination during the shut down. General statement and responsibilities of Muon run coordinator during LS1 P roposal of term of office Open discussion. Polini , S. Zimmermann, Z . Yan January 28 th 2012. General statement.
E N D
New organization of Muon run coordination during the shut down • General statement and responsibilities of Muon run coordinator during LS1 • Proposal of term of office • Open discussion Polini, S. Zimmermann, Z. Yan January 28th 2012
General statement • Current term of Muon run coordinator will end at middle of Feb, 2013 when the data taking period finish. • Alessandro would like to step down • Zhen could continue for another term or more • We proposal to keep two persons as previously
Responsibilities of Muon RC • Considering to coordinate the various(parallel/independent) activities in all Muon sub-detectors, we would like to keep the Muon run coordinator during LS1 with below responsibilities. • Follow the Muon overall shutdown activities, tightly connect with ATLAS run coordinator and ATLAS Technical coordinator etc. • Organize/Call meeting with DAQ/DCS/DETECTOR experts of 4 subsystems with certain time interval(Bi-weekly or more), update and broadcast the working progress/status to whole community. • Summarize the experiences of MUON 2012 ACR operation, drive the improvement of shifter tools and shifter documents, optimize the schema of shifter training and quality control for next run period
Term of Office for the Muon System Run Coordinator ... • So far we had no well defined length of office for the muon run coordinator job ... • Both in 2011 and 2012 wek had both system coordinator and deputy in place/known only very shortly before data taking started, or even after .... • The same was the case mid 2011 whe n Enrico left .... • The same is the case now where we discuss 2 weeks before start of LS1 and change of organisation .... • Experience has shown that „leaving things to the last minute is not the most efficient, also since some decisions on tools, strategies, shifts, .... Are not taken if there is a vacuum. In addition, it seemed to have become more and more difficult to find coordinators. Proposal: Introduce a fixed length of office, with a defined rotation scheme and with the 2 system coordinators’ term of office staggered. (6 + 6 months or so, start now with this scheme) • Advantages: • It should help in finding people willing to take this job if the length of „duty“ is known • Having staggered terms of duty, shifted by ~6 months, as in ATLAS, helps passing knowledge • Moving to a scheme where the coordinators regularly change should help „taking the muon collaboration into their responsibility to find/provide people“ and avoid the „last minute“ situation we had so far.
Open discussion • OTP class 2 and class 3 shifts • Find what was not going well and address tasks • Muon general • Expert checklists for reverting special configuration • Shifter tools • CSC • DQMD, DQ flagging • MDT • Online histogram update • DQMD, DQ flagging • RPC • Detailed information from LVL1 DCS • DAQ misalignment • DCS (alarms wrt luminosity running). • TGC • LVL1 mismatches, busy and dropped chambers • LS-1 Planning (next page)
LS-1 Planning • Technical Coordination Schedule: • Master schedule: • https://edms.cern.ch/document/1219817/1 • OPM promised to compile more readable list of infrastructure interventions with impact on detectors/DCS and implications • Two main infrastructure interventions with detector/power downtime: • February 2013: roughly 1 month no cooling in USA • September 2013: P1 UPS installation