1 / 17

ECAL Configuration DB

ECAL Configuration DB. Content: Configuration Types Dynamic Software Configuration: 2.1. Partition Configuration 2.2. Run Type Configuration Present Status Equipment Management database; is everything we need there? 5. Conclusions. 1. Configuration Types.

michaelpatrick
Download Presentation

ECAL Configuration DB

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. ECAL Configuration DB • Content: • Configuration Types • Dynamic Software Configuration: • 2.1. Partition Configuration • 2.2. Run Type Configuration • Present Status • Equipment Management database; is everything • we need there? • 5. Conclusions R. Alemany (LIP) Session 2: Database

  2. 1. Configuration Types • - System Software (OS, Kernel…) • - On-Line Software - Static Software Configuration - DAQkit - ECAL software CVS (only versions will be stored in DB) • DCS Software: PVSS, OPC, • DIM Software - RSX (XDAQ nodes configuration) - RS2 (FM, Job Control, etc) - Partition Configuration - RUN_TYPE (Physics, Pedestals, Pedestal scan, etc) - Dynamic Software Configuration Configuration Types - On-Detector Electronics Configuration - Off-Detector Electronics Configuration - DCS Configuration: ELMBs, PLC, HV/LV crates - Firmware (FPGA) • - HAL Address Tables • - Item Builder Tables • Device Configuration Tables • Compression Tables • Encoding Tables (includes TPG configuration) Hardware ECAL software: ECALSupervisor, DeviceSupervisor, LaserSupervisor, etc Device: CCS (Clock&Control System) DCC (Data Concentrator Card) TCC (Trigger Concentrator Card) SLB (Synchronization&Link Board) SRP (Selective Readout Processor) TTC (Trigger&Timing Control) LTC (Local Trigger Controller) DAQkit: OS: Operating System DCS: Detector Control System RS: Resource Service FM: Function Manager TPG: Trigger Primitive Generator FPGA: Field Programmable Gate Array PVSS : Prozess Visualisierungs- und Steuerungssystem OPC: OLE for Process Control DIM: Distributed Information System

  3. SM1 SM2 SM3 RCMS2 KEY RSX RS2 Job Control ECALFM http://pclip1:40000 ECALSupervisor CCSSupervisor DCCSupervisor TCCSupervisor DBManager SpyEvents http://pclip2:40000 CCSSupervisor DCCSupervisor TCCSupervisor SpyEvent SM4 SM5 SM6 C A E N C A E N D C C D C C D C C D C C D C C D C C C C S C C S C C S C C S C C S C C S T C C T C C T C C T C C T C C T C C ECALFM KEY ECALSupervisor KEY KEY Partition Configuration Run Type 2. Dynamic Software Configuration R. Alemany (LIP) Session 2: Database

  4. 2. Dynamic Software Configuration: Partition Configuration EMDB KEY (FROM RCMS2) View KEY ECAL Configuration DB ITEMBUILDERTABLE ITEMBUILDERTABLE_ID R. Alemany (LIP) Session 2: Database

  5. C A E N C A E N D C C D C C D C C D C C D C C D C C C C S C C S C C S C C S C C S C C S T C C T C C T C C T C C T C C T C C 2. Dynamic Software Configuration: Partition Configuration SM1 SM2 SM3 http://pclip1:40000 ECALSupervisor CCSSupervisor DCCSupervisor TCCSupervisor DBManager SpyEvents http://pclip2:40000 CCSSupervisor DCCSupervisor TCCSupervisor SpyEvent SM4 SM5 SM6 R. Alemany (LIP) Session 2: Database

  6. 2. Dynamic Software Configuration: Run Type Configuration TTC & LTC Configuration Tables Schemas will be defined centrally; filling/update of the content is sub-detector responsibility. R. Alemany (LIP) Session 2: Database

  7. TRIGGER_ CONFIG_ID … … … … … … … … … … 2. Dynamic Software Configuration:Run Type Configuration

  8. 2. Dynamic software configuration:Run Type Definition OFF-Detector Electronics Configuration (DCC) (TO GET A DEFAULT CONFIGURATION) TO MODIFY THE CURRENT CONFIGURATION FOR A GIVEN SEQUENCE/CYCLE CONFIGURATION_ITEM_NAME = SREADOUT_0 CONFIGURATION_ITEM_VALUE = 0 R. Alemany (LIP) Session 2: Database

  9. 3. Present Status Only versions will be stored in DB, the System Software is in IT, the On-line Software is/will be in CVS - Static Software configuration Versions to be stored in DB. Online Software:Permanent location to be discussed. - DCS Software Software On going - Dynamic Software Configuration Configuration Types On going - On-Detector Electronics Configuration - Off-Detector Electronics Configuration - DCS Configuration soon to be tested : PVSS - ConfigurationDB interface - Firmware (FPGA) to be discussed where/how to store the files (includes TPG configuration) Done for DCC&SLB, on going for TCC&CCS, tbd for SRP, TTC & LTC Hardware

  10. 4. Equipment Management DB

  11. EMDB

  12. EMDB

  13. EMDB R. Alemany (LIP) Session 2: Database

  14. EMDB According to the OD back plane, the order is TCC, CCS, DCC R. Alemany (LIP) Session 2: Database

  15. 4. Equipment Management database; is everything we need there? • Board: Power supplied? • Board: Connectors on the back are missing  Slink receiver cards • Board: How mezzanine boards, like SLB on the TCC, are represented? • Crate: How special back planes, like the OD back plane, are represented? • Boards and crates: would be usefull to know the power supplies the boards need and currents (ƳV - 1A, 3V3 - 6 A) .... • Where is the information regarding the firmware files?

  16. 5. Conclusions • We have already identified all ECAL configuration types. • The proposed Dynamic Configuration scheme, Partition Configuration (PC) and Run Type (RT), are flexible enough to take into account all the different PCs and RTs we could think of. • It also allows to keep all the Configuration knowledge in the database, therefore nothing is hardcode in the software. • It also allows to perform automatic calibration procedures. • ECAL databases are not an issue any more. • An important document is being prepared: “ECAL database requirements” to compile in a single place all the ECAL requirements/needs in terms of databases. • Lets profit a.m.a.p. of this session to identify pending issues, and bring solutions.

  17. NAME NAME 2. Dynamic Software Configuration:Partition Configuration: Item Builder Tables R. Alemany (LIP) Session 2: Database

More Related