Exploring Data Issues and Tests at IHEP Experimental Center
"Discover the latest data issues and testing results at IHEP Experimental Center, along with ongoing efforts to address interrupt and buffer empty problems. Stay updated on the progress of the BESIII system commissioning in the experiment hall." (Maximum 500 characters)
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
Data issues found and tests Tingxuan Zeng TDAQ Group, Experimental Center, IHEP 2024.08.12 1
Issues found during last data taking 1. GEMDC packet L1 count not increasing when working with dummy GEMROC data. 2. The first GEMDC packet length is wrong. 3. The GEMROC data format in the first GEMDC data packet is wrong. 4. Found DC buffer pile up, multiple DC packets has been read out in one DMARun. 5. GEMROC L1 counter not start from 0. 6. GEMROC L1 counter is increasing by 4 most time, sometimes by 3 or 5. 7. DAQ software is able to acquire data for 2 minutes, after that, no interrupts happened. 8. Sometimes data format of GEMROC 5 is wrong.(new found) 9. Link NO in DC packet is not corresponding to the GEMROC ID.(new found) Our Analysis: 1. 1 maybe cause to 2 different GEMROC data formats: confirming with Pawel if the DC firmware support two GEMROC data format . 2. 2,3,5 maybe due to the same problem. 3. 4 is correct according to current design of DC firmware. 4. 6 7 still need to research. 2
What I have tested in Hall 3 106 Feedback to Pawel to solve Not yet solved Buffer empty happens, can not recover No interrupt issue When no interrupt happens, test DC buffer status and check if it can recover Buffer not empty, can recover Data taking and testing Check buffer status, if buffer not empty, then read out Buffer empty happens quickly Maybe high buffer register access frequency or small read out length has side effects in the FEE firmware implement? Test without interrupt to see if it can work out Buffer empty also happens, but improved (can run for longer time, 1 hour). Reduce buffer register access and read out frequency 3
Test in experiment hall STEP 1: Test Trigger signals Network of Angelo s PC is connected in the experiment hall. Make BESIII DAQ system worked with ZDD system. The L1/CHK/CLK signals in the MTI/MCC module are already seen in the Oscilloscope. Michela is testing the signals with the GEMROC (TO DO)STEP 2: Data taking with BESIII Global trigger 2 DC boards in DAQ lab need to be flashed by Pawel The GEMROC in DAQ lab , firmware need to change by Angelo. 4
Summary The interrupt issue / buffer empty issue still exist and I have done more tests to explore it. New found 2 issues, 8 issues in total. We have prepared the BESIII system for commissioning in the experiment hall. The first step is ongoing. 5
