Hi,
We are setting up an experiment which involves conduting time-correlations using the Timepix3. We ran into issues which we suspect is related to data acquisition. Feedbacks are greatly appreciated. Below is a detailed description of our situation:
After seeing the signals using SoPhy, we closed it and started running the following command in .../SPIDR/trunk/Release/
/. Tpx3daq -i 100 -b 40 -m -s filename_ -t 5
The acquired .dat file is then loaded on to ROOT with DRGUI to pre-process. This is the part where we notice the problem - it is running slow from the very beginning, when printing
File 0/N count xxxxx
Since I have used Timepix in an earlier experiment in another lab. I transfered some .dat files I took from the earlier experiments to the PC in this new setup and ran ROOT DRGUI again, the old data can be processed at a normal speed. So I think the problem is not with the ROOT program but with the raw data and the data acquisition process. I have experienced slowdowns when I had missing packages during the data acquisition stage, but this is not the case here, the data acquisition program runs smoothly with no missing packages or error.
After a long pre-processing, we did get *cent*.csv files and a ToT file. But they result in a strange coincidence profile (see attached image). Again, if I process the old data using the same program, the *cent*.csv and ToT file gives reasonable coincidence results. That is why we started questioning the time-tagging during data-acquisition.
We would greatly appreciate any insights or ideas on how to troubleshoot our new system. Thank you!
