1 / 8

Abbreviated list of April Global Run (AGR) achievements

Abbreviated list of April Global Run (AGR) achievements. A lot of new equipment successfully participated in this AGR. All: clock frequency scan ECAL/RCT/L1: test (28 of 500) new oSLB  oRM links Strips: r un with all FEDs & calibration constants at  15°C

mateo
Download Presentation

Abbreviated list of April Global Run (AGR) achievements

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. Abbreviated list of April Global Run (AGR) achievements A lot of new equipment successfully participated in this AGR • All: clock frequency scan • ECAL/RCT/L1: test (28 of 500) new oSLBoRMlinks • Strips: run with all FEDs & calibration constants at 15°C • HCAL: Commission new HO SiPMswith self- and DT-triggers in bottom-only and top-only configurations • DT: Commission relocated sector collectors • RPC: First global run with new RE4 chambers • CSC: First global run with new ME4/2 chambers • PPD: First run with Prompt Calibration Loop on cosmics G. Rakness (UCLA)

  2. Some issues encountered (1/2) • Communication is hard… • Shift crew  DOCs • Actions performed without telling the experts • DOCs talk directly to DAQ, DCS or Trigger shifter (skip Shift Leader) • Shift crew  shift crew • DCS shifter not always aware what should be on • DAQ/DCS shifter had parts of detectors in run but powered off • DOCs  DOCs • Trigger key did not always match the detector state/key • Management  Shift crew/DOCs • Actions performed without telling Run Field Managers • DTs removed from an overnight run • RC did not inform Tier-0 that run was continuing over the weekend G. Rakness (UCLA)

  3. Some issues encountered (2/2) • New hardware needs commissioning… • Shifters were busy overnights to keep runs going • Why did we keep going out of sync? • Timing between control signals need tuning since FPGAs on new CSCs need longer time to load (bigger) • Spikes in upper trigger sectors which had not been run since collisions • Old problems show up (and fixed) again… • Cables unplugged at Global Trigger • L1MuOpen triggers not included in Express Stream • miniDAQ data with bad menu caused crashes at Tier-0 G. Rakness (UCLA)

  4. Power/cooling/elevator • Sunday evening: power cut affected the cooling at p5 • Although water was still flowing, it was no longer being cooled… and eventually initiated temperature alarms/automatic switch-off for several subsystems... • An elogwhich sort of describes what happened can be found at http://cmsonline.cern.ch/cms-elog/816435 • Discovered that technical incidents are kept track of in TECOPA, not elog… see page 12 of https://twiki.cern.ch/twiki/pub/CMS/AprilGlobalRun2014/TECOPA_slides_20140411.pdf • Elevator going underground cavern stopped… twice... • Wed: relay that tells door where it is w.r.t. opening broke • Thu: piece guiding the door fell out G. Rakness (UCLA)

  5. Action items • Make communication the procedure in the control room • Between & within shift crews, DOCs, and management • Follow up issue with gas • On both CERN gas group side and RPC side… • Test out every new thing which is installed, even if it doesn't give good cosmic rays • E.g., DT links on top-half and calorimeter trigger • Make sure monitoring paths have what we need • E.g., muons in cosmic rays, single objects w/beam • Why do we keep going out of sync? • These are not difficult data taking conditions… G. Rakness (UCLA)

  6. 2014 Mid-Week Global Run (MWGR) schedule https://twiki.cern.ch/twiki/bin/view/CMS/CentralShifts2014#Global_run_planning  Intend to officially announce the dates for the MWGRs soon  G. Rakness (UCLA)

  7. Regarding worries about Trigger and Clock Distribution System (TCDS) • Summary of concerns from subsystems about TCDS… • Upgrade not as transparent as they were led to believe (some work involved) • The time schedule is late (installation in August) • It’s not going to work out of the box (little expertise left in subsystems to commission) • https://indico.cern.ch/event/310364/ • Have discussed w/TCDS & HCAL, and will sit in when they interface at 904 to get a sense of what it takes G. Rakness (UCLA)

  8. To do • Sort out what is happening with shift administration • Andrea won’t be extended past October… Tiziano has someone in mind to replace him but Austin doesn’t think that is a good job for him (I agree with Austin) • Work out LHC/CMS handshake schedule • Technical Coordination, BRIL, … • My items from RC to-do list • Clean up sources to "action list" from the meetings • Make sure that HF is fine as min-bias trigger for low lumi • Come up with best guess-timates for integrated and instantaneous luminosity during LHC startup • Monitor TCDS developments/scheduling • Follow up problems w/ECAL laser calibration data xferto Tier-0 • Follow up SCAL FED G. Rakness (UCLA)

More Related