Since last meeting, no collisions LHC has been working towards increasing the intensity in single bunches towards achieving the 2011 integrated luminosity goal of 1/fb… Next fill most likely to have 3x3 bunches filled (2x2 colliding in CMS) –Wednesday night or Thursday? Expect bunch intensity to saturate minimum bias triggers –~ 4 – 5x10 29 /cm 2 /sec in 2 bx’s –Zero-bias = Minimum-bias –Issue to face: luminosity determination more complicated since it will not be proportional to minimum-bias trigger rate… 22 June 2010G. Rakness (UCLA)1

CSC  CSCTF  DTTF exchange Bug found in “Link 2” counter in DTTF firmware CSC  CSCTF  DTTF timing determined using cosmic ray data –ME1/3 data are 1 bx early at DTTF –DTTF reduced latency of all DT stubs by 1bx –GMT added 1bx to DTTF triggers to compensate Latest news from Jorge: –“I have indeed observed CSC  DT coincidences in this [cosmic-ray] run, and the data-emulator agreement at the extrapolation level is virtually 100% (with closed extrapolation LUTs!)” –In events with just one DT-segment and one CSC-segment, the data p T differs from the emulator p T by one unit… Maybe using a different p T LUT than assumed (affects 10% of the data) –“Now the idea is to continue taking data with this new timing and to check what happens in collision runs.” N.B. DT  DTTF  CSCTF timing (knob at CSCTF) is measurable with CSCTF data and is OK… 22 June 2010G. Rakness (UCLA)2 Took the time during LHC commissioning to work on the exchange of trigger primitives at the CSC and DT track finders…

Recall: CSC Activity Trigger was approved 17 June 2010: CSC Activity Trigger Enabled in the second implementation of the HLT menu for 4x10 29 –From configuration file, it is possible to remove one ring from consideration in the Activity trigger… The default is to disable ME1/1A Menu in ConfDB: /online/collisions/2010/week24/HLT/V12 Primary Dataset = CommissioningNoBeam Problem… – –“CSCActivityFilter selects about 1 out of 1000 min-bias events”  Onia people think this number is more like 1 out of 70… Looking back at the source of this statement, it was based on a ratio of 96 events out of events passing the filter  This is suspect from given that there are only 9659 bit-40 triggers in run … 322 June 2010G. Rakness (UCLA)

Following up the CSC Activity Trigger… Laria is going to explain in an where that number came from… (tonight) Regarding “Automatic validation” ( from Andrea Bocci)… Once a path is in the menu it is validated along with the rest of the menu. However, this only checks that the path is not crashing, the timing is ok and that the rates are fine on high pt physics objects. To make sure that the path is working correctly you should re-run the HLT menu on some recent data, and check that the accepted events look “right,” both in terms of rates and of correctness. Andrea has given me a recipe to run the menu… I was planning to run it tomorrow… 22 June 2010G. Rakness (UCLA)4

DCC FMM During Halo Muon Trigger spike G. Rakness (UCLA)5 Plot by C. Vuosalo (OSU) Run Lumi Section 544 Some questions… 1.Warnings were sent from various DCC’s over several orbits: Why were the triggers not stopped? (C. Schwick) 2.If FIFO fills up, the response should be Out- Of-Sync: Why are DCC’s going into ERROR? (J. Gilmore) 3.What are the DDU’s doing? (C. Vuosalo) 4.What about the software “bug”? (unrelated—P. Killewald) 22 June 2010

Summary of Discussion on CSC Header Extraction In the CSC system, we have… A large amount of debug information packed into headers The need to be able to access any and all information from the header from DCC, DDU, TMB, ALCT, etc. in order to debug problems Inability to define what exactly we need to access for any particular problem The need to be able to change header information from firmware version to firmware version We came to the conclusion that the most useful thing we could have is a generic “getter” to be able to get, for example, DCC header 2 bits or TMB header26 bit 6… This would allow… Users not to have to define his/her own unpacker of “status digis” Firmware writers flexibility to change debug information in the headers and trailers CMSSW software releases not to be tied to a specific firmware version for status digis. 22 June Discussion between Tim Cox, Carl Vuosalo, Rob Harr, Sasha Sakharov, and me Sasha Sakharov is working on it…

Consolidation of TTCci Configuration? The current state of TTCci configurations were summarized, with the idea to consolidate the five separate configuration files into one for use in all running situations… –CFEB calibrations –ALCT calibrations –Local runs –Global Runs Summary: it probably can be done, but will require development at 904 (and point 5—probably at the next technical stop [19 – 23 July]…) 22 June 2010G. Rakness (UCLA)7

Impact “Update”… Impact v10.1 is finally running on my new laptop Can create.xsvf files from.mcs files (to load TMB firmware at the experiment) without having to boot my old laptop… Only difference between.xsvf files created by v10.1 and files created by v6.1 (on old laptop) is... –10.1: PROM ID is read and checked just prior to programming –6.1: All 4 PROM ID’s are read and checked at the beginning  Important: make sure to check “parallel mode” Checking this box changes a single bit in three XSIR's from 0  1, and makes the difference between a programmed TMB and a not-programmed TMB… 22 June 2010G. Rakness (UCLA)8

CSC Expert Operators Now have enough CEO candidates to make it through January 2011 Chris is included in the next round of CEO shifts –Chris’ first shift = 4 – 10 August Training information can be found at… – At the moment, the training includes a lot of my talking to candidates one-on-one. What am I looking for? –Are they involved? Do they ask good questions? How do they communicate? Are they self-motivated? –I think this kind of “evalutation” will remain for quite some time… Depending on the candidate, some of the time is spent by me explaining the system from the operations point of view… –This should probably be made into a “class,” or at least a powerpoint presentation… –(Although given the different levels of different students, such a presentation might not be appropriate for everybody…) 22 June 2010G. Rakness (UCLA)9

Greg vacation I will be in Fort Collins, Colorado 1 – 9 July –Family reunion –Class reunion Misha has agreed to take over task of CSC Operations Manager during this time 22 June 2010G. Rakness (UCLA)10

To do Tomorrow CSC Activity Trigger –Run Andrea’s prescription to check CSC Activity trigger… –Find out where Laria’s number comes from Send “Expert system” analysis for CFEB and ALCT reloading to Misha, Evaldas, and Jinghua… Analysis Look at AFEB time bins ON for timing scan runs Documentation Look at/input transitions into TriDAS/emu/doc/html/EmuFSM.xhtml To do at 904 TTCci consolidation with Calibration Runs Online software –Put ALCT firmware database check into ALCT firmware write routine –Resurrect ALCT self-test –ALCT hot-channel mask in xml file/config DB –Expert config check –Configuration check with separated DMB and CFEB 22 June 2010G. Rakness (UCLA)11