1 / 17

DOOCS DAQ software for the EUDET prototype

DOOCS DAQ software for the EUDET prototype. Valeria B artsch (UCL) Andrzej M isiejuk (RHUL) Tao W u (RHUL). Overview over the task - DOOCS software -. http://tesla.desy.de/doocs/doocs.html. User Interface Program Interface Middle Layer Hardware interface. hardware.

kevinlane
Télécharger la présentation

DOOCS DAQ software for the EUDET prototype

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. DOOCS DAQ software for the EUDET prototype Valeria Bartsch (UCL) Andrzej Misiejuk (RHUL) Tao Wu (RHUL)

  2. Overview over the task - DOOCS software - http://tesla.desy.de/doocs/doocs.html User Interface Program Interface Middle Layer Hardware interface hardware

  3. Overview over the task- ENS naming service - User Interface Program Interface Middle Layer Hardware interface provided by DOOCS and already in use for RPC communication between client and server hardware

  4. ENS Naming Service Screenshot of the rpc_util GUI • Naming convention is already specified (similar for LDA, DIF and ASICS) • Properties need input from hardware programmers

  5. Overview over the task User Interface Program Interface Middle Layer Hardware interface Hardware interface most important at this stage hardware

  6. e.g. ECAL Slab Hardware interface DIF • Concentrating on the ODR interface: • because it is the first hardware layer to talk to • the device is close to be ready • easy communication with colleagues at UCL and RHUL • Plan: • start with the LDA and DIF in September • have the interfaces ready about end of the year LDA Opto ODR Opto PC Driver DOOCS hardware interface DOOCS

  7. Overview over the ODR interface DAQ PC • communication between different parts of DOOCS by RPCs • configuration files used to find different parts of the system ODR ODR Control Interface store to disk Sockets DOOCS device server RPC Control Room PC GUIs ENS naming service RPC

  8. Overview over the ODR interface • one device server can have many instance all connecting to different ports and hostnames • using 2 threads: one for receiving, one for sending on the socket • sockets format chosen to build an interface to the ODR and the LDA ODR ODR Control Interface store to disk ENS naming service Sockets RPC DOOCS device server Build Socket Stream Send configuration Recv data Send & Recv in 2 threads

  9. ODR interface at work- screenshot - Check out our demonstrator

  10. ODR interface at work- screenshot - Check out our demonstrator

  11. Overview over the task User Interface Program Interface Middle Layer Hardware interface • important • ramps the whole DAQ system up and down • will be started after the hardware interfaces are ready • (Jan-Mar 2009) hardware

  12. Overview over the task • DAQ: • Event collection • Event building • LCIO conversion • (to be implemented) • Importance: low, can be done at the end of the software project; • Alternatively this can be done offline User Interface Program Interface Middle Layer Hardware interface hardware

  13. suggested timeline 2009 Sept Oct Nov Dec Jan Feb Mar event building, etc. LDA and DIF interface State Machine Configuration database ODR, LDA, DIF test bench at UCL GUI, alarm handling, logging

  14. backup slides

  15. State Analysis State = Dead suceed failed Transition = PowerUp Transition = PowerDown State = Ready Transition = StartRun Transition = EndRun State = Running Transition = StartConfiguration Transition = EndConfiguration State = Configured Transition = BunchTrainStart Transition = BunchTrainEnd State = InBunchTrain

  16. DAQ system FC/SC: Fast/Slow Collector BM: Buffer Manager EVB: Event Builder Example with dummy data has been successfully tested

  17. Alarm handling

More Related