Online DAQ for SCT

1. Online DAQ for SCT Magali GRUWÉ CERN CERN, 15 February 2002

2. Basic components: RC: Run control DB: Configuration database MRS: Message reporting system IS: Information Service IGUI: Integrated Graphical User Interface Others: Online Histogram Monitoring Diagnostics Event sampler Online DAQ components Magali GRUWÉ CERN

3. Run Controller • Controls DAQ configuration and data taking operations • In practice: Controller hierarchy: • The general Run Controller • Specific controllers for the system(s): • General SCT controller • SCT-Crate controller • Beam-Crate controller • etc… • Run control is based on Finite State Machine Transitions • Skeleton for controllers is provided • We have to map actions to the Finite State Machine Transitions Magali GRUWÉ CERN

4. Initial Loaded Configured Running Paused Unload Unconfig Stop Resume Load Config Start Pause Finite State Transitions (I) • Initial: • The controller is visible to and can communicate with the Run Control • Loaded: • The component under control has read any configuration data needed for initialization • Configured: • The component under control has executed all its initialization phases and is ready to operate • Running: • The component under control is running Magali GRUWÉ CERN

5. Initial Loaded Configured Running Paused Unload Unconfig Stop Resume Load Config Start Pause Finite State Transitions (II) • Actions can be defined at three levels: • Transition action • Entry action • Exit action (gives some flexibility) • Pause action could also be used for • Doing some analysis • Changing some parameters • etc… before resuming run Magali GRUWÉ CERN

6. Mapping SCT actions to Transitions (I) • “Initial” transition: • Start the SCT controller • Start the SCT-crate controllers • “Load” transition: • Read in database information: • Which ROD crates are available • Addresses to reach them • Which ROD modules are available in each crate • How to access them (slot number, base address) • Which channels on each ROD are active • Which module do they correspond to (serial number and geographical location) • Where to find the TIM module (slot number, base address) Magali GRUWÉ CERN

7. Mapping SCT actions to Transitions (II) • “Configure” transition: • Load specific DSP programs • Set ROD register values and FE parameters (read from Configuration Database or more likely from files pointed at by the Configuration Database) • Set TIM register values • … Magali GRUWÉ CERN

8. Information Service • General purpose information exchange • Persistent information storage available for all the DAQ applications, and all processes which subscribe to it • There are various servers (currently 5) • It can be used to make parameter values available to various application (FE parameters, DCS parameters, etc…) • This functionality could be used in the characterization or calibration modes for passing parameter values to, or getting parameter values from, the applications driving the RODs. Magali GRUWÉ CERN

9. IGUI • Integrated Graphical User Interface: • Shows the current status and allows control by the operator • Various panels are available: • For driving the Run Controller • For monitoring • For checking the execution of applications • For fixing basic run parameter values • Run number • Run mode (physics, calibration, characterization) • etc… • etc… • Extra panels can be added: • For example, if selecting characterization mode: • Define specific parameters • Execute a series of predefined commands Magali GRUWÉ CERN

10. Configuration Database • Defines all the aspects of the configuration: • Hardware available • Workstations, SBC, etc… • Crates, modules, etc… • Software • Applications, controllers • Relationships • Which application runs on which workstation or CPU • Which parameters correspond to which hardware module • Parent/Children relationship between applications • Parameters requested by applications • Pointers to files/databases for each hardware module • etc… • Configuration Database is based on some defined schemes. These can be extended if required. Magali GRUWÉ CERN

11. Configuration Database (I) Whole partition: Magali GRUWÉ CERN

12. Configuration Database (II) Hardware: Magali GRUWÉ CERN

13. Configuration Database (III) Software: Magali GRUWÉ CERN

14. “Storage” “Monitoring” DAQ for SCT: structure (elements) FE “Slow control” SBC B O C R O D T I M VME Crate S L “Online” PC Magali GRUWÉ CERN

15. “Storage” “Monitoring” DAQ for SCT: structure (links) FE “Slow control” SBC B O C R O D T I M VME Crate S L “Online” PC Magali GRUWÉ CERN

16. “Storage” “Monitoring” DAQ for SCT: structure (software) FE “Slow control” OPTO VME PVSS SBC B O C Ethernet R O D T I M IOM RC ES DDC VME Crate S L “Online” RC DB IGUI MRS MS PC Magali GRUWÉ CERN

17. VME SBC Ethernet R O D T I M “Online” RC RC DB IGUI MRS VME Crate PC Test setup • Tests performed in Cambridge, end of January 2002: • Online DAQ running on PC • Run Controller running on PC • SCT-crate controller running on SBC • Communication between the controller and the TIM module (using John’s C TIM libraries) Successful Magali GRUWÉ CERN

18. Future • We need to map the actions of the “Action List Handler” with the DAQ-1 Finite State Transitions: • What do we want the system to do, at which stage? • Investigate how to make all relevant parameters available to all relevant applications • Use of the Information Service? Is it feasible for so many parameters? Is it appropriate for all types of parameters? • Do we want to make use of the “pause” state to perform actions/analysis between different steps • in the calibration mode? (done in TileCal) • in the characterization mode? (probably not) • Is a “characterization” panel at all realistic? Useful? • That would use a predefined actions Magali GRUWÉ CERN