Hi @ZhangGang00 , I don't exactly understand your question. I assume you refer to EUDAQ1.

EUDAQ just records the raw data defined by the individual "producer" (https://github.com/eudaq/eudaq/tree/v1.x-dev/producers)
For the Online Monitor or for a conversion to other data formats, the data has to be interpreted which is defined by the "converter plugins" (https://github.com/eudaq/eudaq/tree/v1.x-dev/main/lib/plugins).

For the RD53A and YARR, @arummler or @DavidLP can probably answer your specific answer as being the experts for these user integrations. At least, I found quickly in the BDAQ converter a 25x100 option: https://github.com/eudaq/eudaq/blob/v1.x-dev/main/lib/plugins/BDAQ53ConverterPlugin.cc#L69

Are there any news?

Dear developers,

I didn't hear more reply from you. So we just modified the YarrConverterPlugin.cc in hard-code way. YarrConverterPlugin.cc now returns different row and column index of pixel according to the different "ProdId" of 50*50 and 25*100 modules. And it works.

Cheers,
Gang

Hi @ZhangGang00 ,

good to hear that you found a solution, but I am a bit confused since I cannot find the YarrConverterPlugin.cc in the main EUDAQ repo? Can you please create a pull request that we can merge it to the main repo?

Cheers,
Jan

Hi @ZhangGang00 I am sorry for not having answered your question but in the moment there is very little time and the focus of the ITK pixel test beam community is currently on preparation of the MS test beams. By the way, I think we met at the BTTB and discussed YARR and the converter plugins. For clarification: The converter plugins are written and maintained by the DAQ developers although they are by default included in this repository as they have to be compiled into the library. The YARR converter plugin has been written by Timon Heim who is main developer of YARR. In the moment it is still only available in the YARR producer repository:
https://gitlab.cern.ch/YARR/YarrEudaqProducer/blob/master/YarrConverterPlugin.cc

I guess this is where you had found it otherwise it would not have worked. I will contact Timon again about inclusion in the main repository. In the moment we are using mostly BDAQ at ITK pixel test beams and that converter plugin can use either pixel sizes defined during data taking in the config file or load a separate config file during analysis time which overwrites the values for individual DUTs. That enables to mix different pixel sizes in one batch as well as change them without recompiling the whole system.

I am currently looking into consolidating out data taking and analysis chain together with our ITK pixel reco experts: BDAQ, EUDAQ, EUTELESCOPE, TBMON2. One point is to have proper tags, but also to look beyond, e.g.:

• usage of separate collection name
• check whether this setting of the pixel size is the best approach, I had also once written a generic config file loader for eutelescope
• we also do not have a geometry description yet in eutelescope which will be necessary for multi chip modules

In general I would prefer if we could have the same approaches/configurations both for BDAQ and YARR as they are reading the same chips and modules.

Dear developers,

I am using Eutelescope to analyze testbeam data. Yes, I got the YarrConverterPlugin.cc from https://gitlab.cern.ch/YARR/YarrEudaqProducer/blob/master/YarrConverterPlugin.cc . As I am at LBNL now, I also got some help from Timon in person. Looking forward to a more powerful EUDAQ. :)

Cheers,
Gang

Dear developers,

I used EUTelescope to get some testbeam results which shows much worse space resolution than we expeted. So I requested some other testbeam dataset which seems to use BDAQ. When I converted the raw file, some errors happeded(see output.txt). The raw file I used is in /afs/cern.ch/user/j/jbeyer/public/TB_GangZhang/run001568.raw (or https://drive.google.com/file/d/1nA4QIfnGSIjvuo5MYyJ9dClcpB47K1sF/view?usp=sharing). The geometry is Mimosa26, Mimosa26, Mimosa26, RD53A 100*25, FE-I4, Mimosa26, Mimosa26, Mimosa26. Te version of EUDAQ I am using is branch v1.x-dev, tag: v1.9.1 . Could you please take a look?

Cheers,
Gang

output.txt

Dear developers,

Anyone has some idea about above issue?

Cheers,
Gang