Implement module-theta readout (with per-layer merging)

[giovannimarchiori]

This code implements the RedoSegmentation method for the module-theta readout implemented in HEP-FCC/FCCDetectors#56
Allows for instance to have two module-theta readouts with different grouping of cells (useful e.g. for debugging)

Tagging @gartrog , @BrieucF

[kjvbrt]

Hi @giovannimarchiori,
can the switch between different segmentation types be extracted into separate tool? Something like RedoSegmentationTool with interface defined in k4FWCore/k4Interface.

[giovannimarchiori]

Hi @kjvbrt
I am not sure to understand your suggestion here.
BTW, of the 3 PRs (FCCDetectors, k4RecCalorimeter, k4SimGeant4) this is the least important one - it's useful IMO because it allows having multiple instances of the module-theta merged readout in a single job with different merging configurations so that makes debugging of the new segmentation much easier (I couldn't have done it without this feature), but apart from that, in real life one can run with a single segmentation with the baseline merging configuration. So I wouldn't spend much of my time to refactor this code for having merged - if you think it should leave only in my fork for my own debugging purposes, so be it.

[kjvbrt]

Can you share your steering file, just to have an idea how you use the algorithm?

[giovannimarchiori]

Hi @kjvbrt ,
here is the steering file for fccrun
https://github.com/giovannimarchiori/LAr_scripts/blob/gmarchio-main-ModuleThetaReadout/FCCSW_ecal/run_thetamodulemerged.py

[kjvbrt]

Hi @giovannimarchiori, thanks for the steering file.
OK, I see how it is used, let's merge it like this.

I wanted to avoid creating notion for segmentation type or in general some hierarchy among segmentations.