Elec-TDAQ Progress: General Architecture and Trigger Strategies Discussion
Dive into the recent progress in Elec-TDAQ, focusing on the discussion around the general architecture and the two main frameworks - ATLAS-like and CMS-like. Key points include trigger strategies, FEE and BEE roles, trigger decision-making processes, and hardware triggers. The discussions also touched upon Muon R&D and Elec framework compatibility design, as well as potential future directions for Muon FEE compatibility with CAL SiPM readouts. Explore the insights shared during the CEPC TDR meetings and the evolving strategies for efficient data handling in particle physics experiments.
Uploaded on | 0 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Progress in last week of Elec-TDAQ Thursday link https://indico.ihep.ac.cn/event/21711/ Discussed on general architecture of Elec-TDAQ, converged into two main frameworks: ATLAS-like & CMS-like Key point is the trigger strategy: ATLAS-like: FEE participate into the trigger decision, software trigger CMS-like: BEE participate into the trigger decision, FEE only send out all the raw data ( FEE-triggerless ), hardware trigger Tends to prefer CMS-like trigger Simpler FEE & ASIC, higher engineering feasibility within limited time Precondition: FEE can send out all the data Needs to know all the data rate before trigger (plus all the noise & background) of all sub-det Most of the value provided before by sub-det are data rate after trigger For few particular sub-det, like vertex, if needed (very likely), possible to provide a special & simple but fast L0 trigger, with less latency (e.g. 3 us) BEE & Trigger common board possible to each merge into a single board Needs further discussion to clarify the functionality division depending on trigger strategy 05/03/2024 CEPC TDR meeting 1
Progress in last week of Elec-TDAQ Preliminary discussion on Muon R&D Elec CEPC Elec-TDAQ framework compatible design Further Q: what is the real requirement to Muon Elec Further Q: can Muon FEE compatible with CAL SiPM readout? ASIC can be used Initiated Power & Data link subsection work in Elec-TDAQ Power: Jun Hu; Data Link: Di Guo (CCNU); Grounding: Lei Fan 05/03/2024 CEPC TDR meeting 2
ATLAS vs CMS TDAQ framework ATLAS BEE: receive the data after triggered; buffered on FEE; Trigger communicate with FEE CMS BEE: receive the data before trigger; buffered on BEE; Trigger communicate with BEE Note: a special L0-trigger goes to the inner tracker in ATLAS 05/03/2024 CEPC TDR meeting 3
Muon R&D Elec Framework compatible design Muon To CEPC BEE ADC ADC _ch0 _ch0 CSA CSA 2 ADC ADC _ch1 _ch1 CSA CSA Power Power Power Power FPGA Channel 2 Channel . . . . . . 3 . . . . . . . . . . . . Channel 63 Leave the current FEE, remove FPGA board & Power Add FEE Data link, all data go directly to BEE Use common Power module (Pol-based) Further Q: what is the real requirement to Muon Elec Further Q: can Muon FEE compatible with CAL SiPM readout? ASIC can be used 05/03/2024 CEPC TDR meeting 4
Recent plan Define the final framework of Elec-TDAQ Make clear the raw data rate before trigger Cost estimation for TPC & DC, TOF & Si Strip 05/03/2024 CEPC TDR meeting 5
