[ALICE3] Fix some overlaps between services and supports

Author: marcovanleeuwen

Detectors/Upgrades/ALICE3/TRKFT3/FT3/simulation/src/FT3Layer.cxx

@@ -469,7 +469,8 @@ void FT3Layer::createLayer(TGeoVolume* motherVolume)
     double z_local_offset = z_layer_thickness / 2.0;
     // ensure staves fully encapsulated in the layer volume,
     // but don't cross out of max nominal radii of 38.5cm & 71.5cm respectively (3.5cm tolerance)
-    TGeoTube* layer = new TGeoTube(mInnerRadius - 0.2, mOuterRadius + 3.49, z_layer_thickness / 2);
+    // MvL: try 70.5 // 2.5 cm tolerance instead
+    TGeoTube* layer = new TGeoTube(mInnerRadius - 0.2, mOuterRadius + 2.49, z_layer_thickness / 2);
     layerVol = new TGeoVolume(mLayerName.c_str(), layer, medAir);
 
     if (ft3Params.drawReferenceCircles) {

Detectors/Upgrades/ALICE3/TRKFT3/TRK/simulation/src/TRKServices.cxx

@@ -629,7 +629,7 @@ void TRKServices::createMLServicesPeacock(TGeoVolume* motherVolume)
   motherVolume->AddNode(middleBarrelCarbonSupportVolume, 1, nullptr);
 
   // Get geometry information from TRK which is already present
-  float rMinMiddleServices = 38.5f;                       // cm, start radius of the ML services = maximum radius allowed for sensors (35 cm), plus some margin for disk paving with modules
+  float rMinMiddleServices = 38.0f;                       // cm, start radius of the ML services = maximum radius allowed for sensors (35 cm), plus some margin for disk paving with modules
   const float zMiddleServicesBarrel = 64.5f;              // cm, z position of the first barrel ML service disk
   const float zMiddleServicesBarrelFwdConnection = 143.f; // cm, z position of barrel to forward connection services
   const float zLengthCylinderMiddleServicesBarrel = zMiddleServicesBarrelFwdConnection - zMiddleServicesBarrel;