1. 22 May 2007G. Rakness (UCLA) 1 At minus-side slice test… Complete description of how to bring back slice test all the way from (power=off) to (local run=physics data on CASTOR) available at: https://twiki.cern.ch/twiki/bin/view/CMS/CSCSliceProcedures Reduced logbook of runs available at: https://twiki.cern.ch/twiki/bin/view/CMS/CSCReducedMinusSideLog Micro-summary of runs taken since last week… scan comp_delay = “delay before comparison of comparators” = (1, 2, 3) scan triad_persistence = 6, 5, 4, 3, 2

2. 22 May 2007G. Rakness (UCLA) 2 Timing with “Current” Version of TMB Firmware Check timing with one chamber (ME-2/2/17) upgraded to 30 April 2007 version of TMB firmware… Single chamber trigger rate  60Hz = no change from 9 April 2007 version ALCT/CFEB clock phases change by 6-7bx alct_tx_clock_delay = 8  1 alct_rx_clock_delay = 11  4 cfeb[0-4]delay = 10  4 MPC winner bit: no change Following changes are consistent with CLCT being 1bx faster and ALCT being 2bx faster: match_trig_alct_delay increase by 1bx 1bx added to LTC to preserve constant difference between Active FEB Flag and L1A at DMB 1bx added to tmb_l1a_delay to match LTC addition No change to alct_l1a_delay, even after LTC addition ALCT DAV delay reduced by 1bx (time of L1A at DMB  ALCT DAV at DMB)  30 April 2007 version 1bx faster than 9 April 2007 version, as expected…

3. 22 May 2007G. Rakness (UCLA) 3 ALCT within CLCT matching window First 10k events of each run analyzed… details, plots available at… https://twiki.cern.ch/twiki/bin/view/CMS/CSCAlctInClctMatchingWindow Some details regarding these plots… Matching window “0” defined by CLCT pattern trigger Matching window width set to 7bx Delay of ALCT signal set to 6bx for all chambers (i.e., tuned to equalize arrival at SP, not tuned to minimize latency) Increase of average value  CLCT faster Decrease of RMS  less time jitter in CLCT An important number to quantify (related to RMS): fraction of ALCT within 3bx matching window

4. 22 May 2007G. Rakness (UCLA) 4 Runs scanning over comparator threshold: average ALCT position in matching window Conclusions: CLCT (1/2-strip/di-strip/pattern) threshold = (3/3/1) is faster than (4/4/1) Comparator thresholds have significant effect on speed of CLCT Effect of the comparator threshold is less noticeable for (3/3/1) than (4/4/1) CLCT=(3/3/1), faster by 0.033bx/mV decrease in comparator threshold CLCT=(4/4/1), faster by 0.04bx/mV decrease in comparator threshold CLCT faster MTCC threshold

5. 22 May 2007G. Rakness (UCLA) 5 Fraction in 3bx window constant trigger rate increasing trigger rate Comparator threshold (V) “Goal” 4/4/1 threshold 3/3/1 threshold Runs scanning over comparator threshold: fraction of events within 3bx matching window Conclusions: Trigger rate constant down to threshold = 14mV (11mV) for 3/3/1 (4/4/1), and increases below increase of “rate” correspond to noisy comparators observed in TMB counters Above noise threshold, fraction of data in 3bx window anti-correlated with layer threshold and comparator threshold To achieve ALCT-CLCT matching > 99%, the thresholds should be pushed as low as possible for: CLCT pretrigger layer comparator threshold

6. 22 May 2007G. Rakness (UCLA) 6 Next plans… 1.Implement timing shifts measured at Sector Processor (D. Wang, Florida) 2.Download ALCT firmware for CMS-official B-Go command sequences  Try B-Go commands by hand. Does everybody respond correctly?  Try official CMS LTC configuration file for standard running. Are we in compliance? 3.Software to analyze DMB timing values 4.Software for online determination of match_trig_alct_delay 5.Add CLCT-only trigger (clct_trig_enable)