TB25 simulation analysis files

[AndreaPareti]

Added analysis files for tb25 simulations (analysis/tb25_analysis). These include channel mapping, FERS logic activation and noise.
Updated scripts for HTCondor submission.
Improved coordinate plotting in main analysis file (analysis/HidraAna.C)

Included (but currently commented out) geometry for 2026 test beam with SiPMs arranged in two columns with 6+4 configuration.

Separated horizontal and vertical rotations into two separate rotation matrices, in order to better describe platform rotation and calorimeter tilting.

[lopezzot]

Hi Andrea, just a few questions:

• Have you rebased your branch on this main branch?
• Have you run a global search for overlaps on the 2025 and 2026 geometries?
• Why do you run the digitization directly in the simulation? Wouldn't it be better to save the time-of-arrival information from the simulation and then perform the SiPM digitization as a separate step?

[AndreaPareti]

Ciao Lorenzo,
I tested the overlaps in previous versions on the geometry with the original hidra geometry. To be sure, I just run a global search with the TB25 geometry and all ancillaries, and did not find any overlap warning.

I have not rebased my own branch on the main repository one yet, as I did some other changes for my own studies. I preferred to keep the two separated to keep them clean.

I included the digitization in the simulation because I was worried about the size of the output files by storing each arrival time for each energy deposit. However, after some discussions and seeing the updates on the IDEA calo, I'm already working on separating the SiPM simulation and using it afterwards. I am planning to include the sensitive detector hits and the digitizer module in this repository once I reach a stable configuration.

[lopezzot]

Ok seems fine.
Just one question on this:

I have not rebased my own branch on the main repository one yet, as I did some other changes for my own studies. I preferred to keep the two separated to keep them clean.

I don't fully understand what you mean with this. What I am asking is if your branch is alinged with this repository main branch (btw answer is it is not). That's because you forked from another fork. I suggest you rebase this branch (AndreaPareti:comparisonDataTB25) with this branch (DRCalo:main). If you don't do it we will never have a linear history on this repo and we might have conflicts in main branch. In short, your commits should be ahead of the last commit on this branch before merging.

[AndreaPareti]

Sorry, I though you were referring to my other changes in my own repository for the sipm digitization inside the simulation. I have rebased the comparisonDataTB25 branch in the DRCalo/main repository. Is it OK now?

[lopezzot]

Yes, better now. Maybe someone else wants to review?