1 / 12

Actions arising from DCS review TB 23.2.06 L.Jirden

Actions arising from DCS review TB 23.2.06 L.Jirden. Review Held on 14 Nov 05 – full day Referees from ATLAS,CMS, LHCb Review report Questions and comments Most questions answered during the review Most critical points highlighted here. Review agenda. Introduction Architecture

yamin
Download Presentation

Actions arising from DCS review TB 23.2.06 L.Jirden

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. Actions arising from DCS reviewTB 23.2.06 L.Jirden • Review • Held on 14 Nov 05 – full day • Referees from ATLAS,CMS, LHCb • Review report • Questions and comments • Most questions answered during the review • Most critical points highlighted here

  2. Review agenda • Introduction • Architecture • System Components • Functionality & performance • Detector Applications • Services • Full DCS System • Scale, operation, ACR • Performance • Demo • Installation & Commissioning • Responsibilities & Costs • AOB

  3. Context 3. Services ECS 4. ExternalSystems power cooling gas LHC magnets DAQ Ctrl infrastructure Trigger Ctrl safety HLT Ctrl access 1. Back-end • DCS • - Architecture • Components • Global system • - Performance ITS TPC MUON pixel strip drift T T p hv hv hv hv hv lv lv lv lv lv 2. Detectors

  4. Referees: “clarify communication and interactions with External systems” • DCS/DAQ/TRG/HLT/ECS • Communication protocol; DIM & SMI++; defined in the common TDR INTERACTIONS: • Synchronization • Role of ECS • FEE configuration • dBase common to DCS & DAQ; see TDR and presentations June 05 • Data structures: to be provided by detectors; guidelines + examples given • Procedures defined; prototypes implemented • Networks; DCS, DAQ, GPN • Independent sub-nets communicating via application gateways • Trusted services to be defined • Common credentials required • ACR; common facilities • Consoles, displays, alarms; ongoing discussion • Proposal in preparation

  5. Referees: “clarify communication and interactions with External systems” • Offline • Calibration • Discussion on procedures started; workshop at next ALICE week • DCS archival & conditions data • dBase defined (Oracle) • Data structures being defined • Interface to offline implemented (AMANDA) • Temporary solution until Oracle dB is ready (July 06) • LHC • Communication protocol; DIP defined and implemented INTERACTIONS: • Specification available • Basic solution defined; to be implemented

  6. Data exchange with LHC Offline condition LHC display archival DIP Store Send/receive ECS DCS synchronize Collect • - Background • ZDC position • etc

  7. agreed with detectors Referees: “what is the estimated start-up time?” • DCS is extremely modular • Can be configured according to performance needs • Number of sub-systems per PVSS • Number of PC’s per sub-system • Critical issues • Switch-on of many channels • Configuration of many channels

  8. archival config PC PC PC PC PC … PVSS TMON VHV PVSS HV PVSS LV1 PVSS LV2 PVSS LV3 … TMON HW VHV HW HV HW LV1 HW LV2 HW LV3 HW DCS system configuration Each PVSS system work in parallel !!

  9. Referees: “what is the estimated start-up time?” (II) • Switch-on of many channels: • Test: Total switch-on for 180 CAEN HV channels: 7 sec • SDD: 520 Caen HV channels: ~15 sec • TRD: 1080 = 180 Iseg channels * 6 via DCS board: 7 + ? Sec • TOF: 3600 = 180 Caen channels * 20 fanout: 7 sec NOTE: to becompared with ramping times of minutes !! • Configuration: normally done outside physics time !! • Test: Configuration of a full Caen crate 192 ch: 20 sec • SDD: 520 Caen HV channels: <54 sec • Test: DB retrieval of FEE 150MB BLOB’s: 15 – 50 sec • SPD: 3 sec • TPC:10*10kB/DCS board: 25 sec • TRD: 10*10KB/DCS board: 50 sec • if required: Oracle tuning and Cashing will improve

  10. Referees: “is the response time adequate in case of alert avalanches” • Answer: YES • Tests have shown that PVSS copes with • an alert avalanche of at least 10 000 alerts per PVSS system • ~ 60 PVSS systems in ALICE: 600 000 alerts acceptable • a sustained alert rate of ~200 alerts/sec per PVSS system • ~ 60 PVSS systems in ALICE: 12 000 alerts per second acceptable • all alerts from a full CAEN crate displayed within 2 sec • Max 6 crates on one PVSS system: all alerts displayed within 12 sec • Many means to limit alert avalanches • Scattering of PVSS systems • Correct configuration of • Alert limits for each channel • Summary alerts & filtering • Verified by ACC at installation time

  11. Referees: “Check the planning and status of each detector DCS” • Major status and planning request has been launched • detectors asked to provide precise status and plans • for each of their ~100 DCS sub-systems • report in next DCS workshop (March 13- 14)

  12. Review report conclusion “Referees see no major problem to achieve the goal of monitoring and control of the ALICE detector”

More Related