1 / 11

RCS Discussion

RCS Discussion. RCS Layout – I. Security Service. UserDB. ConfDB. Resource Service. UI. Info&Mon Service. LogDB. UI. Services Connection. Session Manager. UI. Run Bkkpng. Job Ctrl. Problem Solver. Sub-System Controller. RCMS. Sub-System (Daq)Resources. RCS Layout – II.

belva
Download Presentation

RCS Discussion

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. RCS Discussion

  2. RCS Layout – I Security Service UserDB ConfDB Resource Service UI Info&Mon Service LogDB UI Services Connection Session Manager UI Run Bkkpng Job Ctrl Problem Solver Sub-System Controller RCMS Sub-System (Daq)Resources

  3. RCS Layout – II UI UI UI Session Manager Services RCMS Services Services Connection EVB Ctrl TRG Ctrl CS Ctrl DCS Ctrl EVF Ctrl FED Builder Mu Cal Glbl RU Builder EVF Sub-System TRG Sub-System EVB Sub-System DCS Sub- System CS Sub- System

  4. Open Issues • DCS (PVSS) • components under control • DBs to store information (e.g. HV default values, etc.) • interface to RCS • Run mode and Conditions DB • Problem Solver and aTTS • Monitor Procedures

  5. Example: Configuring a DTR column(present understanding) • HV • P • FE Thr DT Chmbr PVSS/EXT DB • TDC • Time Wdw • oper mode • TRG BRD Mini Crate DCS Ctrl ROS • Merge MCs • buffer setup • en/dis chnls PVSS/EXT DB • Merge ROSs • en/dis chnls • link setup FED • D2S • links setup • en/dis links Session Manager FRLC FEDB Ctrl FED Builder • switch setup EVB Ctrl RU • RU setup RUB Ctrl • EVM setup • switch setup EVM RU Bld Resource Service • switch setup BU • EVF setup • geometry • trigger tbls • calibrations EVF Ctrl EVF Conditions DB

  6. PVSS Access b) to dump conditions a) to monitor conditions RCS RCS • Partition • DCS partition definition is a PVSS task • RCS can ask the partition list and select one • Monitor • RCS asks params to be monitored • dump conditions • RCS subscribe (?) the receiving of pvss alarms • PVSS-GTW propagates the alarms to RCS when they occured • Any global dump on request (e.g. before and after a run)? May be to the conditions DB? subscribe alarms Time, alarm par x get par x PVSS GTW PVSS GTW get par x par x PVSS NET PVSS NET

  7. Running DT C • Allarms on • det condts • Trends • Statistics Run Condition errors, status, parameters over/under thrs, etc. DT Chmbr Mini Crate • TDC errs • chip T • buff ovfl DCS Ctrl Time Stamp Condition • resolution time ? • Condition versions (Babar) ? ROS • alignment • buff ovfl. PVSS/EXT DB • alignment • links status • rates FED detector conditions • rates • links status • appl status Session Manager FRLC Off-line DB FEDB Ctrl ? Conditions DB conditions + monitor FED Builder • perf x port • error rate EVB Ctrl daq&trigger conditions • rates • error rates • buffer occup • appl status RU RUB Ctrl • rate • error rate • bufff occup • appl status EVM RU Bld Information Service calibration constants geometry • perf x port • error rate BU • rates • rej rate • appl status EVF Ctrl EVF trigger conditions + monitor

  8. Conditions DB • Usually (e.g. Babar) Conditions DB is meant to store: • detector alignments • calibration constants • time dependent parameters, under which the experimental events are taken and that are necessary for the reconstruction and analysis of the raw data • the stored conditions are time based (time stamp) • Babar has a resolution time of 1 second • If we agree on the general principle that • all changes in any detector, daq or trigger components are logged at all times • only severe errors lead to stop the system (e.g. system efficiency less than 50%) • Then, the Conditions DB should also contains (at least logically) parameters describing the time behavior of the daq and the trigger systems • off-liners should be able to easily extract the needed view (detectors, daq, triggers) to reconstruct properly a given set of events, possibly using same API and same query languages

  9. DAQ Run Conditions ( varie ) • General DAQ Run Conditions are (referred to a given daq application): • Performances (input, output). Up/Low thresholds should be set to identify under/over-performances situations. Under/over performances situation to report to RCS • Buffer occupancy. Over threshold situations to report to RCS • Status. Status change to report to RCS • . • Independent applications heartbeat is necessary to have the map of the “still alive” applications. This could avoid dead locks. Applications crash to report to RCS • Hardware (e.g. PC) hosting daq applications should also be pinged by an heartbeat to have the map of the “still alive” PCs (farm components, etc.). PCs crash to report to RCS • PCs hosting daq applications should be also controlled/monitored both from the hardware point of view (T, Fans, etc.) and OS point of view (memory used, CPU used, disks, etc.). Critical situations to report to RCS Heartbeat App. DAQ Appl. Heartbeat Hardware Appl. Conditions PC/OS Conditions DAQ Appl. PC

  10. Problem Solver • Some examples to understand how this could work • How to implement it? • tools ? It is a sort of expert system • languages? • Atlas experience on their problem solver? They use CLIPS , a tool to build expert systems • Jess (Java expert system). Does it fit our needs? • Recovering actions • recovering could involve to reset a daq component • reset could impose to • block the system for a while (aTTS) • reset (fast) the electronics • reset the failed component • align its status to system statud • restart the component • restart the system (aTTS) Information Service alarms malfunctioning Problem Solver recovering actions fast reset aTTS

  11. RCS plans • Complete the prototype based on Tomcat and delivery it to: • Small daq systems • Small test environment • Setup a testbed with a dedicated 16x16 cluster to figure out: • Performances in command propagation • Performances in collecting information into IMS • Investigation on new native XML DB (in particular Oracle 9i vers. 2) • Start to play with Web Services

More Related