Crucial for first beam:

Technical:

  • EE-trigger commissioning and availability of ECAL experts and central systems to do so.
  • Trigger masking single crystals and L1T DQM plots to know which.
  • ES/ECAL completely configured from DB.
  • EB TCC synchronization loss: must be fast to detect.
  • Detail the conditions under which the DCC produces backpressure (CRC errors, Stuck in Warning, Maximum rate)
  • Reviewers recommend to have an additional person to support Jose and to look at the DCC design and its integration in its environment (Slink/cDAQ/TTC on one side and TCC/SRP/FE on other).

Organizational:

  • Need to have someone responsible for ECAL DBs on-site.
  • Commissioning of components with offsite expertise (Saclay): more extensive onsite presence will facilitate the task and increase efficiency, especially due to erratic and tight commissioning schedule.
  • In order to complete ECAL Trigger commissioning and be ready to respond to beam conditions, they should have additional competent manpower, under Pascal's supervision.

High Priority:

  • SR tests at high rate.
  • DCU/L1A contention: mFEC firmware may need revision but designer retired 2 years ago, follow-up with Kostas in due time.
  • Software merging: unification of tools for ES and EB/EE (Non-Event Data monitoring, database editors, confmagik, DuckCAD MySQL, etc).

Important:

  • The need for 904 or a TIF-like facility: P5 will soon not be open to development or bug-hunting.
  • Have non-P5 PCs for software development and some testing.
  • Masking should be the next priority of the database editing tools team.
  • SLB monitoring (not the accumulators) is unmanned but needed for understanding in which end of the SLB-RCT cables the problems are.
  • Investigate the possibility of masking Trigger Towers from Trigger at the SLB level (instead of at the input of the TCC) in order to have the TP in the data; keep in mind consequences for RCT emulation.
  • Trigger masking: if it is not a crystal the problem, envisage tool/procedure to easily diagnose if a trigger tower noise is low-E and change its LUT instead of masking completely.
  • Improve automation of masking tools, but shift crew should still consult with expert before masking.
  • Documentation: how to release RPMs, other expert procedures, expert tool manuals, left bar index for shifters to navigate information, focus on functionality and clearly not doxygen, developers description of code structure and functionality.
  • Teaching and improving competence of shift crew.

Lower priority and long-term:

  • Firmware management: sources and backups, documentation of firmware programming procedures
  • The alarming system should incorporate alarms from LED controller, Laser controller, etc. by injecting monitoring data into XMAS.
  • Software merging: FecSoftware (ES, EB/EE, and possibly TK) in the longer term desirable, waiting too long will complicate the task due to continuing software development.

Notes for ECAL DAQ and Trigger

  • Noted good integration of ES team.
  • Noted good communication with cDAQ team.

Notes for ECAL DCS

  • DCU data must have counterpart alarms/actions in DCS/ESS.

Notes for ECAL Run Coordination

  • There are huge benefits in having shifters take blocks of shifts.

Notes for ECAL Calibration group

  • LED-EMTC commissioning must be finished.

ECAL should decide internally on these proposals

  • Request SRP to read back the values programmed in the boards. This has been seen of value in other VME boards such as the TCC or DCC.
  • Revive ECAL DAQ and Trigger weekly meetings, focusing on the expert tools: DB editors and Non-event data monitoring.
  • Make each component have long (1-hour) presentations (in 2010) about the architecture, software, connections, dependencies, behaviour, procedures, etc. This would be the basis for the documentation of the component.

-- AlessandroThea - 08-Jan-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-01-08 - AlessandroThea
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback