ALICE 3 geometry building is broken

[plariono]

When running o2-sim-serial-run5 -n 1 -g pythia8hi -m A3IP TRK FT3 TF3

The geometry building breaks at FT3 and I get a seg fault.

@sadekr could you have a look what is wrong there please?

[11:38:19][INFO] Running simulation with no beam pipe.
[11:38:19][INFO] Creating FT3 Backward layers:
[11:38:19][INFO] Inserting FT3Sensor_0_0 inside FT3Chip0
[11:38:19][INFO] Inserting FT3Chip0 inside FT3Layer0_0
[11:38:19][INFO] Inserting FT3Layer0_0 inside FT3V
[11:38:19][INFO] Inserting FT3Sensor_0_1 inside FT3Chip1
[11:38:19][INFO] Inserting FT3Chip1 inside FT3Layer0_1
[11:38:19][INFO] Inserting FT3Layer0_1 inside FT3V
[11:38:19][INFO] Inserting FT3Sensor_0_2 inside FT3Chip2
[11:38:19][INFO] Inserting FT3Chip2 inside FT3Layer0_2
[11:38:19][INFO] Inserting FT3Layer0_2 inside FT3V
Warning in <TGeoMaterial::ctor>: Material Kapton (cooling pipe) defined with fractional Z=6.880000
Warning in <TGeoMaterial::ctor>: Material FT3_Kapton defined with fractional Z=6.880000
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
ERROR: Cannot create geometry builder with NULL geometry
...
[11:38:59][ERROR] Error in cd-ing to /cave_1/barrel_1/TRKV_2/TRKLayer0_1/TRKStave0_0/TRKModule0_0/TRKChip0_0/TRKSensor0_1/

 *** Break *** segmentation violation



===========================================================
There was a crash.
This is the entire stack trace of all threads:
===========================================================

[atriolo]

Hello @plariono, the geometry building breaks at the error [ERROR] Error in cd-ing to /cave_1/barrel_1/TRKV_2/TRKLayer0_1/TRKStave0_0/TRKModule0_0/TRKChip0_0/TRKSensor0_1/ due to a path research that does not exist in the geometry.
This happens when the "TRKBase.layoutML=kTurboStaves;TRKBase.layoutOL=kStaggered;" configKeyValues are omitted, since the default geometry for the simulation is the full cylindrical one (without staves, modules and chips), and it's not possible to retrieve those elements from the geometry file.

I would propose to add an exception for the path getter in the case of a cylindrical layer, to search for a different path structure, and at the same time set the default geometry for ML(OT) as turbo(staggered), since this should be the base for the studies. Then, if one wants to simulate the cylindrical geometry on purpose, one should add --configKeyValues "TRKBase.layoutML=kCylinder;TRKBase.layoutOL=kCylinder;" when running the simulation.
I can handle this.

For the ERROR: Cannot create geometry builder with NULL geometry, this seems to be linked to the FT3 module, but at the same time, this does not seem to break the simulation (meaning the simulation process reaches the end). However, it should be checked in detail whether this has a bad impact the geometry for FT3 or not.

[plariono]

Hi @atriolo, thank you for the explanation. For me it's fine to make the default turbo staggered and to keep the cylindrical option with the config key. If you could fix this, would be great!

[plariono]

Still, this fixes only the bottom part of the issue.

The issue with the FT3 results in absence of the disks in the geometry: