280 likes | 451 Views
Controls in the CMS Experiment. Overview Controls in CMS DCS Project Planning. J. Varela, LIP-Lisbon. JCOP Review 10-12 March 2003. DAQ and Controls Requirements. Detectors. Crossing rate 40 MHz Event size ~ 1 Mbyte Detector Channels Control Ev. Data (bytes)
E N D
Controls in the CMS Experiment Overview Controls in CMS DCS Project Planning J. Varela, LIP-Lisbon JCOP Review 10-12 March 2003
DAQ and Controls Requirements Detectors Crossing rate 40 MHz Event size ~ 1 Mbyte Detector Channels Control Ev. Data (bytes) Pixel 60000000 1 GB 50000 Tracker 10000000 1 GB 750000 Preshower 145000 10 MB 50000 ECAL 85000 10 MB 100000 HCAL 14000 .1 MB 50000 Muon DT 200000 10 MB 10000 Muon RPC 200000 10 MB 5000 Muon CSC 400000 10 MB 90000 Trigger 1 GB 16000 Max LV1 Trigger 100 kHz Readout network 1 Terabit/s High Level Trigger ~ 5 TeraFlop Online rejection 99.9997% System dead time ~ %
Experiment Controls Run Controls (RCS): Configure and operate all local/global data taking sessions Monitor and protect the measurements and the data flow Based on the CMS online software framework (XDAQ, RCS) and commercial products (DBs, SOAP, XML, e-tools etc.) Detector Controls (DCS): Setup and monitor the detectors and the environment Monitor and protect the apparatus equipment Based on industry standards (PLC, field buses, PVSS and JCOP tools)
8-fold DAQ system Data to Surface DAQ slice
Trigger, DAQ and Control Subsystems Trigger & Data Flow TPG Trigger Primitive Generator RTP Regional Trigger Processor LV1 Level-1 Trigger Processor GTP Global Trigger Processor TTC Timing, Trigger Control sTTS synchronous Trigger Throttle System aTTS asynchronous Trigger Throttle System EVM Event Manager RCN Readout Control Network BCN Builder Control Network Data to Surface DAQ column FES FrontEnd System FED FrontEnd Driver D2S Data to Surface RU Readout Unit BDN Builder Data Network BU Builder Unit FU Filter Unit CSN Computing Service Network RU Builder Control column FEC FrontEnd Controller DCN Detector Control network DSN DAQ Service Network DCS Detector Control System RCS Run Control System Filter Farms
DAQ partitioning TTC and Trigger partitions: The TTC system consists of 32 partitions accessing 32 unconnected sets of FEDs The GTP can handle concurrently up to 8 different combinations of the 32 TTC partitions (DAQ partitions) Mode 1) FED-RU builder partition The EVM of each DAQ slice, using the trigger type contained in the GTP record, broadcasts the read command only to the RUs associated to that trigger type. All active DAQ slices result partitioned in the same way. Mode 2) FED-DAQ slice partition Each set of FED-FRLs associated to a given TTC partition (trigger type) is programmed to send the event fragments always to the same DAQ slice.
Trigger Fast Control DAQ Event Managers TTCmi Global Trigger LHC GPS aTTS Central Control Partition Control Partition Control Partition Control L1A Control Front-end Emulators, Trigger Rules Trigger Throttling System (sTTS and aTTS) Calibration and Test Triggers Dedicated runs, Special triggers during runs Synchronization Control Timing signals, Resync procedures Partitioning 8 independent partition groups, 8 independent triggers Local Triggers Local Control Local Control Local Control TTC sTTS TTC sTTS TTC sTTS FrontEnd FrontEnd FrontEnd TTCrx TTCrx TTCrx
TTC/TTS Partitions Subdetector Number Partitions Pixels 2 Barrel, Forward Si-Tracker 4 Disk+, Disk-, Inner barrel, Outer barrel ECAL 6 EB+, EB-, EE+, EE-, SE+, SE- HCAL 6 HB+, HB-, HE+, HE-, HF+, HF- RPC 4 Endcap+, Endcap-, Barrel+, Barrel- DT 2 Barrel+, Barrel- CSC 2 Endcap+, Endcap- Calorimeter Trigger 1 Calorimeter trigger Muon Trigger 2 CSC and DT trigger Global Trigger 1 Global trigger + Global Muon trigger
Detector Data Taking (DAQ systems) GLOBAL Slink-64 • Local DAQ • VME/PCI FED data acquisition • Test beam DAQ systems • Test and Calibration readout • Online passive readout • Global DAQ • Main DAQ data stream • Run Control and Monitor • Supervision of all data taking operations • DAQ resource and partition handling • Readout subsystems configuration • Data flow monitoring • DCS communication LOCAL (VME)
FrontEnd Configuration and Monitor • Detector specific systems • Access to the inner readout electronics, the power regulators, the programmable logics, the sensors to read currents, temperatures etc.. • Special requirements imposed detector specific solutions. • Data links and interfaces • Programmable Logic (FPGA,..) controls • Sensors readout • Calibration and test procedures • The configuration data set are often very large. • The collected data (temperature and currents) are data complementary of the measurement instead of control parameters. • All Detector Safety Units make use of dedicated and wired sensors
Detector Control (DCS systems) • Detector subsystems • HV/LV • Fluids and environment • Cooling • Racks/Crates • Temperatures • Infrastructures • Test systems (Laser, LED, alignment camera etc..) • Detector safety (DSS) • Temperature • Gas • Radiation • Experiment supervision • DCS Resources handling • Alarm and loggings • History data base • External systems communication. TPG Trigger Primitive Generator RTP Regional Trigger Processor LV1 Level-1 Trigger Processor GTP Global Trigger Processor TTC Timing, Trigger Control sTTS synchronous Trigger Throttle System aTTS asynchronous Trigger Throttle System FES FrontEnd System FED FrontEnd Driver FEC FrontEnd Controller D2S Data to Surface RU Readout Unit BU Builder Unit FS Filter Subfarm EVM Event Manager RM Readout Manager BM Builder Manager EVB Event Builder RCN Readout Control Network BCN Builder Control Network CSN Computing Service Network DCN Dtector Control network DSN DAQ Service Network DCS Detector Control System RCS Run Control System Supervisor structure etc.
Common FrontEnd Control Used by: Pixels, Tracker, ECAL, RPC Front End Controller (FEC) VME module Controls and monitors frontend electronics Distributes master clock and L1A triggers Reads monitoring data Digital optical links at 40MHz Communication and Control Unit (CCU) Token ring architecture with redundancy Distribution of clock, trigger, commands and monitoring data inside detector Detector Control Unit (DCU) Interface to monitor slowly varying parameters CCU Block Diagram
HCAL DCS Layout Laser, RBXs, Sources HCAL host HF radiation monitoring HV,LV Private system servers (PVSS systems) User PCs (PVSS Uis) Industrial PC, Linux Industrial PC, Linux PCI interface Counting room RS485 HV power supplies RS422 fan-out RS422 fan-out HV power supplies Drivers for tmp srcs 14 permanent drivers 200m RS422 RS485 To temporary sources To sources Hub-18 RS/RS Hub-18 RS/RS Truncated CCM RS422 Cavern CCM RBX LV power supply RBX LV power supply RBX FE boards, LED calibration module, Monitoring modules LV power supply 18 RBXs
MuonCSC DCS Layout DAQ Mother Board Trigger Mother Board Clock Control Board Muon Port Card DCS PC(s) Ethernet 10-Base-FL 48 peripheral crates SCADA PVSS II VME Dynatem TMB DMB CCB MPC DB Crate PS Skewclear Cathode Front End Board LV CFEB HV gas ALCT Anode LCT Board cooling Low Voltage Mezzanine Board LVMB alignment Endcap Muon Chamber Calibration local DAQ LVDB Low Voltage Distribution Board
MuonDT DCS Layout • SLOW CONTROL MASTER • Sits in the counting room • 250 RS232 optical connections • Houses the DCS interface • SERIAL LINKS • One direct link from each control board to counting room • One direct link from half wheel control board to counting room • One daisy chained link from sector collector to control boards (half wheel) • One local link for maintenance
RCS and DCS Domains • RCS: Data Acquisition Systems • Based on the CMS online software framework (XDAQ, RCS) and commercial products (DBs, SOAP, XML, e-tools etc.) • Run Control and Monitor • Local/Global DAQ systems • FrontEnd Electronics Configuration • Readout Electronics Configuration • PC clusters and applications control • Local/Remote Data Archive • Run Condition Data Base • Configuration Data Base • DCS: Classic Control • Based on industry standards (PLC, field buses, PVSS and JCOP tools) • Racks/Crates power • HV/LV supplies • Cooling and environment • Gas and fluids • Central supervision • Alarms, history data base • External system communication • Detector Safety • Detector specific monitoring and calibration tasks • User applications mainly based on XDAQ with direct interfaces with local/central DCS systems • On detector electronics sensors (temperatures, currents, …) • FrontEnd electronics test and commissioning procedures • Calibration (source, LED, Laser) sessions
Calibration Runs Pixels Calibration run ECAL Calibration data Monitoring run Slow control run Test pattern run Laser run Synchronization run MUON DT Threshold run Relative t0 calibration Rates Alignment run Gap tests Absolute synchronization Silicon Tracker Pedestal run Test pulse run Synchronization run Optical link special run Linearity run Alignment run MIP calibration MUON CSC Test Pulse Run Pedestals Trigger thresholds Trigger patterns Test pulse run Synchronization run Alignment run HCAL Radioactive source Laser calibration LED calibration Charge injection Preshower Pedestal run Test pulse run Synchronization run MIP calibration Calibration with electrons MUON RPC Test patterns runs Synchronization runs
RCS and DCS Frameworks • Online software framework (CMS XDAQ and RCMS) • Local/Global DAQ systems • Local/Global Run Control • Detector specific electronics system configuration and monitoring • Job&Application control • Data taking monitoring and calibration • Local/Remote mass storage and data bases • DCS subsystem and supervision (PVSS and JCOP supported tools) • Classic detector slow control (Racks/Crates, HV/LV, Cooling, Gas, Security) • Generic DCS framework (exploiting industrial H/S implementations) • Experiment detector controls supervisory levels • Centralized functions (Alarms, History, Security) • Common features between the two systems: • XDAQ-PVSS interface (based on native PVSS API) • Access to external data bases for run conditions and experiment configuration both from XDAQ and PVSS
Executive XDAQ Application User Application Module XDAQ Framework A collection of packages to - Directly manipulate VME/PCI devices - Perform network communicationTCP, Ethernet, HTTP, Myrinet - Execute user applications in a well controlled environment - Provide control and configuration commands for applications and devices - Provide access to configuration dataXML files (disk or network) databases
user defined Application modules user defined Application modules user defined Application modules user defined Application modules XDAQ Interfaces XDAQ Hardware abstraction layer (PCI to VME, direct VME, direct PCI) Data store (Oracle, mySQL, XML files) communication interfaces (PVSS, TCP, HTTP, Myrinet, raw Ethernet)
DCS Project Planning Central DCS Work Packages • FSM hierarchy and JCOP framework setup • DataBases • Interface RCS-DCS • Integration with Dedicated Control Systems • Environmental Measurements • Hardware Infrastructure • Machine Interface ~ 60 Subdetector Work Packages: SubDetectors: Pixels, Tracker, ECAL, HCAL, CSC, DT, RPC, Alignment
Subdetector DCS Milestones First Prototype using PVSS framework First Integration with Central DCS Final System
Central DCS Milestones DCS Conventions and Interfaces Q2 03Naming scheme, Commands, States Data Bases Specification Q3 03 Configuration, Conditions, Assets, Archive Prototype Central DCS Q4 03 Including scaling tests First prototype of complete DCS system Q4 04Integration of subdetectors (Slice test) Configuration DataBase DAQ interface Integration with Dedicated Systems Gas, Cooling, Racks, DSS Q1 05Magnet, Technical servicesQ1 06
Requirements to JCOP Hierarchy Control (2Q 2003) Configuration Tools (2Q 2003) HV Control (2Q 2003) Detector Safety System (1Q 2004) Data visualisation (1Q 2004) Crate Control (1Q 2004) Rack Control (1Q 2004) Interface to Conditions Data Base (2Q 2004) Large scale distribution system (2Q 2004) Gas Control (4Q 2004) Cooling and Ventilation Control (4Q 2004) Web Access (4Q 2005) Interface to Technical Services (1Q 2006) Interface to LHC Accelerator (2Q 2006)