Download
1 / 20
210 likes | 324 Views
The Experiment Control System for ITS Beam Test. General Architecture (1). ECS. DCS. TRG. DAQ. HLT. The ECS is a layer of software on top of the ‘online systems’ controlling DCS, TRG, DAQ, and HLT
E N D
General Architecture (1) ECS DCS TRG DAQ HLT • The ECS is a layer of software on top of the ‘online systems’ controlling DCS, TRG, DAQ, and HLT • The integration of the four ‘online systems’ with the ECS is based on interfaces made of SMI objects
General Architecture (2) • The ECS • Gets information from the ‘online systems’ • Sends coordinated commands to the ‘online systems’ • The ‘online systems’ • Execute the received commands • Can also be operated in ‘manual mode’ by experts • The current interface definitions are the following: • DCS: one object per detector representing the detector from the hardware point of view • DAQ: objects representing RunControl processes • TRG: one object per detector representing the Local Trigger Unit (LTU) and one object for every partition (Trigger Partition Agent) • HLT: a single object representing the HLT as a whole
For the ITS Beam Test • ECS/DCS interface OK • ECS/DAQ interface OK • ECS/Trigger special interface • cabling order defined in a file • A special LTU process (provided by Trigger people) accepts special commands • GOTOGLOBAL(ROLE,BUSY2_OPT) • A special TPA (provided by ECS people) handles the correlations between the three LTUs (master/slave1/slave2; BUSY2 enabled/disabled) • No HLT
ECS components • The major software components of the ECS are: • The Partition Control Agent (PCA) • The Detector Control Agent (DCA) • The PCA Human Interface (PCAHI) • The DCA Human Interface (DCAHI) • For the ITS Beam Test the following components have been modified: • The PCA • The PCAHI
PCA and PCAHI PCA There is one PCA for the ITS partition Controls the running of the ITS partition as a whole Coordinates calibration and configuration procedures (if necessary) Provides information to operators watching the partition Accepts commands from one operator (partition master operator) PCAHI Many PCAHI can be associated to a PCA and provide information to operators Only one PCAHI can get the mastership over the PCA. The operator using it (Partition master operator) can send commands to the PCA PCAHI Master Operator PCAHI PCA
DCA and DCAHI DCA There is one DCA per detector Controls the running of a detector in standalone mode Provides information to operators watching the detector Accepts commands from the PCA or an operator (detector master operator) DCAHI Many DCAHI can be associated to a DCA and show information to operators Only one DCAHI can get mastership over a DCA not controlled by the PCA. The operator using it (detector master operator) can send commands to the DCA PCAHI Master Operator DCAHI DCAHI Master Operator DCAHI PCA DCA DCA
DCA operations • The smallest entity that can be controlled by an operator is a detector in standalone mode • An operator controlling a detector can: • Issue all the commands accepted by its DCA • The list of valid command is (in principle) different from one detector to another • Send manual commands to the ‘online systems’ controlling DCS, DAQ, and TRG • This possibility serves mainly for debugging purposes • Reduce or extend control rights using the access control mechanism contained in the interfaces with the ‘online systems’ • The operator uses this possibility to avoid access conflicts when experts needs to use directly the ‘online systems’
PCA operations • The largest entity that can be controlled by an operator is the ITS partition • An operator controlling the partition can: • Run the partition as a whole • Perform calibrations and tests on individual detectors when the partition is not running as a whole • Exclude detectors from the partition or re-include them in the partition • Send manual commands to the ‘online systems’ for debugging purposes • Reduce or extend operator control rights using the access control mechanism contained in the interfaces with the ‘online systems’
