Implement curved RSU structure for the three layers of vertex barrel trackers

[ShujieL]

Briefly, what does this PR introduce?

created a new vertex barrel geometry file vertex_barrel_curved.xml with a new geo plugin to support smooth cylindrical surface and build-in inactive areas.
This work is a follow-up of #759 which creates flat sensors and barrel with staves.

What kind of change does this PR introduce?

• Bug fix (issue #__)
• [ x ] New feature (issue #__)
• Documentation update
• Other: __

Please check if this PR fulfills the following:

• Tests for the changes have been added
• Documentation has been added / updated
• [ x] Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

Does this PR change default behavior?

The # of hits on vertex barrels will reduce by a few percent due to the inactive areas.
Didn't see a significant change in tracking efficiency. Performance study on going.

[ShujieL]

VertexBarrelEnvelope_length and VertexTrackingRegion_length are not used anywhere. Can we remove them from dump-parameter-table?

Also, not sure why we keep VertexCheck in the xml file.

[ShujieL]

Also, validate-material-map failed due to "Propagation reached the step count limit of 1000 (did 1000 steps)". I remember seeing this error many times in the past but they didn't interrupt the program, a material map would still be generated. Any idea on how to deal with this? @wdconinc

[wdconinc]

Also, validate-material-map failed due to "Propagation reached the step count limit of 1000 (did 1000 steps)". I remember seeing this error many times in the past but they didn't interrupt the program, a material map would still be generated. Any idea on how to deal with this? @wdconinc

no time to look into it until next week (not even sure then)

[veprbl]

Also:

MultiSegmentation ERROR Invalid sub-segmentation identifier!
VertexBarrelHandler ERROR cellID: failed to access segmentation for VolumeID: 000000000103B21F [17019423]  [MultiSegmentation: Invalid sub-segmentation identifier!]
VertexBarrelHandler ERROR ....... G4-local:   (49.820797, 1.685985, 1.892819) G4-global:   (34.036452, 36.420795, -19.331181)
VertexBarrelHandler ERROR ....... TGeo-local: (4.982080, 0.168598, 0.189282) TGeo-global: (3.403645, 3.642079, -1.933118)
VertexBarrelHandler ERROR ....... Pre-step:  AV_1555!Module2_upper_58#58!RSU_upper_3#3  SD: VertexBarrel
VertexBarrelHandler ERROR ....... Post-step: AV_11865!VertexBarrelSubAssembly_3#3!VertexBarrel_layer2_1#1  SD: 
DDSim            ERROR Simulation failed!
Geant4Kernel     FATAL +++ Exception while simulating:MultiSegmentation: Invalid sub-segmentation identifier!

[wdconinc]

I don't understand why the module length is necessary as a map to vector. Will there be multiple modules with the same name? Do you need the length outside of this scope?

[ShujieL]

I use it to accommodate the upper and lower modules and pass to layer assembly. Is there a better way?

[ShujieL]

Also, validate-material-map failed due to "Propagation reached the step count limit of 1000 (did 1000 steps)". I remember seeing this error many times in the past but they didn't interrupt the program, a material map would still be generated. Any idea on how to deal with this? @wdconinc

no time to look into it until next week (not even sure then)

@wdconinc there is a new material mapping script to allow mapping without propagation but requires MaterialMapper from ACTS v34.
https://github.com/acts-project/acts/blob/main/Examples/Scripts/Python/material_mapping_core.py

Any plan for ACTS version upgrade?

[veprbl]

@ShujieL Is this ready? Once this is merged, will you be able to deploy an updated material map?