Complex and non-uniform (pixel) detectors geometries in detector configuration
Is there any way how to deal with non-uniform pixel arrays? If not, what could be the preferred way to implement this? E.g. for long and ganged pixels necessary for multi-chip modules. In EUTelescope we had the the geometries functionality based on ROOT TGeo which allowed to describe specific sensor types. Application is in ATLAS ITk pixel (as we intend to move to Corry at some point) quad chip and triple modules.
A related issue: we are using in the moment still EUDAQ1 for data taking (but for EUDAQ2 this would apply as well) and we are getting the individual chips on a module written as individual blocks in an event. At some point a plane has to be created. In former DAQ systems we did it in the converter plug-in but this makes it quite complex. Would there be a possibility in Corry to pre-process the data; basically combining planes with an additional module?