acton-sparks
Uploaded by
9 SLIDES
224 VUES
90LIKES

DIM as a Communication Layer in FEE Control and Monitoring at ALICE

DESCRIPTION

The Distributed Information Management (DIM) system serves as a crucial communication layer between the TPC/TRD and the FEE control and monitoring application at the ALICE experiment. This paper outlines the principles of DIM, its client-server architecture, and communication protocols over TCP/IP, specifically focusing on service registration, data command handling, and real-time data transfer. It emphasizes how the DIM client subscribes to services and retrieves data using callback functions, enabling efficient control and monitoring of functionalities across the FEE.

1 / 9

Télécharger la présentation

DIM as a Communication Layer in FEE Control and Monitoring at ALICE

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. FEE Control DIM (Distributed Information Management) as communication layer between TPC/TRD and FEE control/monitoring application at ALICE.

  2. Topics • DIM principle and DIM in FEE Control • DIM Communication • DIM Server / Service • DIM Client • DIM – Data • FEE Command (DIM – Command)

  3. DIM @ ALICE (overTCP/IP) FEE-Controler - DIM-Client Request Service Name-Server - DIM_DNS_NODE Service Info Register Service Subscribe to Service Service Data Commands RCU with µClinux - DIM-Server

  4. DIM - Communication The client subscribes to a service once and gets back the corresponding data via a callback-function (timed and/or monitored)

  5. Server • DIM - Server: • the server is represented by servername (must be unique) - the server can offer several services • DIM - Service: • data (base or complex), the server provides to clients - the service is specified by the servername combined with the servicename (e.g. servername/servicename|type|).

  6. Client DIM - Client: - is represented by PID@hostname - has to know servername and servicename to ask DIM – Nameserver for connection point to server. - can send commands to server as base-data-types (like int, char, long, short, float or double) or complex types (like strings or struct-like-objects).

  7. DIM – Data (overTCP/IP) Ethernet-Header IP-Header TCP-Header DIM-Header DIM-Data (Service or Command)

  8. Command Command as character-string of variable length: 0 31 Bits ID Payload - Size Flags (Verify - Flag, ACK - Flag) ACK - ID Payload . . .

  9. Command With the Command you can do: • Huffman coding to minimize traffic • use payload to transfer data from client to server • use payload to send instructions to server - use to reinstall certain settings after reboot of RCU

More Related