1 / 3

CMS Trigger and Clock Distribution System Upgrade Concerns

Summary of concerns and tasks related to the consolidation of trigger and control systems into the Trigger and Clock Distribution System (TCDS) for CMS. Issues include transparency, scheduling delays, and expertise gaps needing resolution. Meeting notes, action lists, and coordination tasks are detailed, with links to valuable resources and schedules. Email automation for information dissemination and monitoring system developments are key priorities.

cruz-harmon
Télécharger la présentation

CMS Trigger and Clock Distribution System Upgrade Concerns

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. Various • Recall: LS1 plan to consolidate trigger control, throttling, and distribution systems into one Trigger and Clock Distribution System (TCDS) • Subsystem input at meeting 1 April (https://indico.cern.ch/event/310364/) • Summary of concerns from subsystems • 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) • Need to sit with TCDS experts to hash these things out… • Assembled “to do” list for Run Coord. team based on mtgs w/subsystems • https://twiki.cern.ch/twiki/bin/view/CMS/CMSRucoP2PSummary • My list of things to do is on the last page… • Assembling info for CMS input to LHC Beam Operations Workshop • CMS input = statements on bunch spacing, pileup limitations, levelingmethods, special runs, beam energy, bunch length, non-colliding bunches… • Initial chat w/ATLAS Run Coordinator: ATLAS input similar to CMS • To be discussed and made official at CMS XC meeting on Friday 11 April G. Rakness (UCLA)

  2. Not just attending meetings and making lists… I wrote a script! • Script to generate emails to institution leaders (e.g., Jay and Bob) about # of central shifts expected and # performed • Gets input from few web pages… • Number of authors per institute (this was not easy to find!) • Name of Collaboration Board representatives • Name(s) of deputies • Number of credits already performed • Need input from Paris Sphicas to “personalize” the email… • Jay said Paris did a nice job in the Publications Committee to personalize their emails • Don’t want it to look like an automatically generated email, if possible • Need to run the email past Spokespeople to give it the “OK” • I expect an email of facts should be relatively easy to get the “OK” G. Rakness (UCLA)

  3. To do • April Global Run: 7 – 11 April • https://twiki.cern.ch/twiki/bin/viewauth/CMS/AprilGlobalRun2014 • Sort out what is happening with shift administration • Andrea won’t be extended past October… then what? • 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