1. Collisions… … with “non-stable beams” maybe on Thursday –Got experts to converge on goal and how to do it … to check timing, using L1 = zero-bias seeding HLT Activity triggers –Included: HCAL, RPC, and CSC –Not included Tracker + Pixel will not be on (not-stable beams) ECAL is not stable and, from what we can tell, will not be ready… (Joao is now in the loop about this) … with “stable beams” maybe by this weekend –Initial plan located here: https://twiki.cern.ch/twiki/bin/view/CMS/CollisionsMar2012#Fill_b y_fill_program https://twiki.cern.ch/twiki/bin/view/CMS/CollisionsMar2012#Fill_b y_fill_program –Will have 1 st meeting Wednesday morning after the daily Run Meeting to discuss details on goals and how to achieve them (2 nd meeting on Thursday, if needed) 27 Mar 2012G. Rakness (UCLA)1

2. Other Run Coordination hoo-hah Am developing a CMS-wide plan for how to test a change in latency of +5bx –Next page (can be skipped) –Technical details of how to do this for CSC are here… https://twiki.cern.ch/twiki/bin/view/CMS/CSCsynchronizationDoc uments#Change_in_L1A_latencyhttps://twiki.cern.ch/twiki/bin/view/CMS/CSCsynchronizationDoc uments#Change_in_L1A_latency –Misha and Evaldas have gone over these technical details and claim to understand them Working to deconvolute sources of deadtime –Information from Trigger and DAQ info need to be combined, to go into Web Based Monitoring –To include software and hardware SEU recovery actions… –To perform a 100% absolutely correct accounting, firmware changes are needed (not needed now) 27 Mar 2012G. Rakness (UCLA) 2

3. How to test +5bx latency 1.Do nothing until a Technical stop… With collision data now… –ES monitor the rate of empty events  “smoking gun” of buffer full –Subsystems figure out how to make the change and the time it takes… 2.At the beginning of Technical Stop, take cosmic ray data overnight triggering on bottom only… –Muon systems are self-triggering  should be “easy” to see –Tracker, pixels should be able to see muons with good signal/noise… –HCAL should be able to see muons ~in time… 3.Change the latency everywhere –Time how long it takes 4.Take cosmic ray data, triggering on bottom-only overnight… –Should look exactly the same as run in step 2... 5.Take data with 1 st fill after Machine Checkout (L1A rate =100kHz) –Measure rate of empty events in ECAL/ES 6.Roll back 27 Mar 2012G. Rakness (UCLA) 3

4. To do (some) CMS Run Coordination stuff –Take collision data –Define algorithm to split deadtime among sources CSC –Put firmware into SVN –Document ALCT/CLCT muonic timing –RAT firmware loading As well… –Make neutron skims 27 Mar 2012G. Rakness (UCLA)4