50 likes | 131 Views
Raw Event : ByteStream implementation. Muon Workshop, 17-19 April 2002 A. Nisati, for the Muon Trigger group. During data taking detector data are provided by the Readout electronics, up to the ROD, and then by TDAQ up to the event storage.
E N D
Raw Event: ByteStream implementation Muon Workshop, 17-19 April 2002 A. Nisati, for the Muon Trigger group
During data taking detector data are provided by the Readout electronics, up to the ROD, and then by TDAQ up to the event storage. • Data decoding/encoding in software may be provided by software developers.
For each muon detector (MDT, CSC, RPC and TGC) a contact person exists in the ROD working group; this people should provide the description of the raw data format up to ROD/ROB level; • In addition, the format of the event as provided by the DAQ is also documented.
The task of 1) defining the raw data format, 2) data decoding and 3) raw data simulation (encoding) involves the DIG, the TDAQ and the Muon software communities; • We need to monitor the status of all needed documents, and identify a set of people available to perform the software task of data decoding (online: monitoring and HLT algorithms; offline: reconstruction packages) and encoding (raw data simulation).
What is available today for the 4 muon detectors: • MDT many groups involved; detailed documentation on TDC/CSM/MROD/DAQ formats available; experience already exists in the Roma1/Roma3 thanks to the H8 Readout/DAQ activity. • CSC: see Brookhaven group; • RPC: Roma1 and Napoli groups involved; detailed documentation on the final data format is ready and it will be available to the community very soon; • TGC: see Japan/Israel groups; also in this case a detailed documentation is available.