1 / 5

1 st global run in LS1: Global Run In November (GRIN)

1 st global run in LS1: Global Run In November (GRIN). https:// twiki.cern.ch/twiki/bin/view/CMS/GlobalRunInNovember2013. 4 – 8 November Technical run to verify we can still run after 9 months Some of the goals… Offline: test new Tier-0 hardware & exercise data flow

didier
Download Presentation

1 st global run in LS1: Global Run In November (GRIN)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 1st global run in LS1: Global Run In November (GRIN) https://twiki.cern.ch/twiki/bin/view/CMS/GlobalRunInNovember2013 • 4 – 8 November • Technical run to verify we can still run after 9 months • Some of the goals… • Offline: test new Tier-0 hardware & exercise data flow • HCAL: look at new hardware w/cosmics Monday • CSC: run with ME+2 and ME+3  Wednesday • L1: increase trigger latency +12bx  Thursday • DT: test new sector collector Friday G. Rakness (UCLA)

  2. Status at noon today… http://cmsonline.cern.ch/daqStatusSCX/aDAQmon/DAQstatusGre.jpg This is especially impressive, given that there was a power cut on Saturday…  We can still run and send data to Tier-0… G. Rakness (UCLA)

  3. ME4/2 commissioning Spent a couple hours with Misha, Evaldas, Karoly, and Eric to discuss what they are seeing • CSC team is running STEP tests on ME+4/2 back chambers • Most of them are functioning OK • Main issue they were asking me about… • Timing of Data AVailable bit (bits that tell DMB that TMB, ALCT, and/or CFEB are sending data) • Recall: delay values depend ~only on the cable length (is fixed value for TMB since DMB is just next to it) G. Rakness (UCLA)

  4. DAV problems • Problems… • The ALCT and CFEB values changed for the ME+4/2 chambers that were already working in Run 1 • The TMB data is not being seen by DMB at all • Suggestion: for the moment, change ALCT and CFEB values as needed, and ask OSU about the TMB DAV • Will allow them to press on to run most STEP tests on most chambers, and to think a bit about the CFEB+ALCT DAVs… • Will return again to TMB DAV tomorrow… hopefully Stan and Ben have some ideas in the meantime… G. Rakness (UCLA)

  5. To do • 12 – 14 Nov: Trigger EDR • 15 Nov: HCAL review • Run Coordination hoo-hah • Finish job description (almost there!) • Inquire about subsystem DCS status • Settle on shifts for 2014 • Control room: talk to CMS Safety (details), sysadmins(infrastructure), Austin (schedule), Frans (underground control room) • Follow up question on lumi section length • How to improve 2015 operations? • Pick up neutron note • Read it again… what all is left to be done? • Chad’s analysis documented here: http://cern.ch/rakness/internal/log/1111/log.html G. Rakness (UCLA)

More Related