904 Status Recall last Group Meeting RAID crash

  • Slides: 9
Download presentation
904 Status • Recall last Group Meeting… – RAID crash on main computer had

904 Status • Recall last Group Meeting… – RAID crash on main computer had rendered 904 unusable… – Lots of work by lots of people almost got it to work… • Why “almost? ” Well, just before I went on vacation… – Track Finder software bugs stopped TF from working (N. B. this was the same set of bugs which caused problems in running at point 5 at the beginning of the 4 th of July weekend…) • Then, while I was on vacation… – Cooling water temperature setting was lowered to 15. 6ºC – Hot weather + high humidity (= low dew points) = water collected on 904 crates – Increased temp. setting to 18. 5ºC (given the continued hot/humid weather, this may still not be enough, Petr is trying to find out what to do about this) • And finally, yesterday and today… – Cooling maintenance ongoing. They are supposed to be finished by tomorrow 13 July 2010 G. Rakness (UCLA) 1

Things to do at 904 1. TMB firmware test (that’s right, this still hasn’t

Things to do at 904 1. TMB firmware test (that’s right, this still hasn’t been done! ) – Includes associated counter + register + configuration updates in online software – Need to get (miniscope) data to CSCUnpacker + CSCExaminer folks 2. SP firmware test – Mostly will be pattern tests, since a lot of their firmware upgrade is regarding DT CSC trigger primitive exchange… 3. ALCT firmware test – Need to get (zero-suppressed) data to CSCUnpacker + CSCExaminer folks So my plan is… IF the cooling work is finished – I am going to spend Wednesday at 904, and will be calling people to bug them to get things going IF the cooling work is not finished – I will push on Thursday, then on Friday… – This fact will simply be pushing us closer to spending the technical stop in "904 -mode" 13 July 2010 G. Rakness (UCLA) 2

Updated CSC “To Do” at Technical Stop • TMB firmware update, includes… – –

Updated CSC “To Do” at Technical Stop • TMB firmware update, includes… – – Close-in-time CLCT readout bug-fix (i. e. TMB “out-of-sync”) Miniscope readout Prioritized TMB readout Sync Error bug-fix • SP firmware update – Singles: Improved phi and p. T assignment – DT-CSC matching issues, including timing adjustment and quality • Online Software upgrade (EMUlib v 9. 10), includes… – – – PCManager Emu. TStore XMAS X 2 P & PVSS DIM data structure DCS GUI 13 July 2010 G. Rakness (UCLA) 3

Other things to do during Technical Stop • SP test of online-computer replacement –

Other things to do during Technical Stop • SP test of online-computer replacement – Procedure of how to replace an online computer is vague – Needs coordination with CMS DAQ folks, since it is their domain… • CLCT muonic timing – Ensure that all CFEB readout timing is OK … and don’t forget when beam comes back after the technical stop… (see next page) 13 July 2010 G. Rakness (UCLA) 4

With Beam, after the Technical Stop • Remove singles from trigger? – Rumor is

With Beam, after the Technical Stop • Remove singles from trigger? – Rumor is that -Onia physics isn’t using it? • High-luminosity timing scan – Previously, ~30 K min bias/point in ~20 minutes, with current instantaneous luminosities, this takes ~1 sec at L=0. 5 x 1030 • Neutron rate runs – Need to triggering on filled bx – Need to triggering on non-filled bx 13 July 2010 G. Rakness (UCLA) 5

Looking at CSC Activity Trigger Offline for Run 137028 • Min-bias triggers from collisions

Looking at CSC Activity Trigger Offline for Run 137028 • Min-bias triggers from collisions at 7 Te. V: Examine 257700 “/Zero. Bias/Run 2010 Av 1/RAW” events from this run … I don’t pretend to understand this number, since this run had… • 135 M Physics L 1 As • 193 k “HLT_Zero. Bias” triggers 13 July 2010 G. Rakness (UCLA) 6

CSC Activity Trigger Breakdown The CSC Activity Trigger goes through the following steps: 1.

CSC Activity Trigger Breakdown The CSC Activity Trigger goes through the following steps: 1. HLTBegin. Sequence. BPTX = Selects triggers within ± 1 bx of BPTX (and finds an [offline] beam spot) – 2. hlt. L 1 s. L 1 Bsc. Min. Bias. ORBptx. Plus. ORMinus = L 1 seed for this HLT path (see previous page) – 3. 19632/257700 events pass (7. 6%) hlt. Pre. Activity. CSC = “Smart prescales” = vector of prescales used depending on the luminosity [“ 4 E 29”, “ 2 E 29”, “ 1 E 29”] – – 4. 5. All 257700 events pass (100%) I set this to 1 by hand for this study (100%) NOTE: this was set to 30 for the previous study, and is an easy way to get a smaller number of “pass” events… hlt. Muon. CSCDigis = Process CSC Digis for this run hlt. CSCActivity. Filter = Select events with any CSC having at least one strip with ADC value > 20 counts above “pedestal” – – With ME 1/1 A enabled 402/19632 events pass (2. 0%) With ME 1/1 A disabled 239/19632 events pass (1. 2%) 13 July 2010 G. Rakness (UCLA) 7

Which chambers fire the activity trigger? Ring 1 Ring 2 No “hot chambers” seen

Which chambers fire the activity trigger? Ring 1 Ring 2 No “hot chambers” seen (i. e. , ~evenly distributed in phi) 13 July 2010 G. Rakness (UCLA) Ring Nchambers (total– both endcaps) ME 1/1 124 ME 1/2 9 ME 1/3 0 ME 2/1 55 ME 2/2 4 ME 3/1 14 ME 3/2 4 ME 4/1 27 ME 4/2 2 8

To do Tomorrow • TMB firmware + software at 904 • Make sure instructions

To do Tomorrow • TMB firmware + software at 904 • Make sure instructions are absolutely clear for unmanned CSC day shifts Analysis • Look at AFEB time bins ON for timing scan runs Documentation • Look at/input transitions into Tri. DAS/emu/doc/html/Emu. FSM. 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 13 July 2010 G. Rakness (UCLA) 9