CbmRoot

Done, see attachment

Thank you Evgeny!

Florian, could you please commit the following 3 files:

1. to macro/sts/geometry
   http://cbm.uni-muenster.de/cbmroot/more/sts_v19h_105mm/create_stsgeo_v19h.C
   http://cbm.uni-muenster.de/cbmroot/more/sts_v19h_105mm/create_stsgeo_v19i.C
2. to geometry/sts/passive
   http://cbm.uni-muenster.de/cbmroot/more/sts_v19h_105mm/sts_passive_v19i.gdml

You can also generate a STS v19i geometry and commit it to the trunk. Thanks!

When trying to create the geometry I get the following warnings. Could you please let me know if this is expected or if these warninge have to be taken seriously.

===> Creating STS....
Info in <TGDMLParse::TGDMLParse>: Re-use existing material: STSBoxCarbonFibre
Info in <TGDMLParse::TGDMLParse>: Re-use existing material: STSBoxCarbonFoam
Info in <TGDMLParse::TGDMLParse>: Re-use existing material: air
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!
Medium: aluminium, Not Yet Defined!

sts_v19i: size 94.8472 x 96.0000 x 81.5520, assembly
Daughters: 
      Unit00R_1, size 18.028 x 48.000 x  3.526, position (    0.000,    0.000,  -36.750 )
      Unit00L_2, size 18.028 x 48.000 x  3.526, position (    0.000,    0.000,  -36.750 )
      Unit01R_3, size 29.846 x 48.000 x  9.500, position (    0.000,    0.000,  -36.750 )
      Unit01L_4, size 29.846 x 48.000 x  9.500, position (    0.000,    0.000,  -36.750 )
      Unit02R_5, size 29.846 x 64.000 x  9.500, position (    0.000,    0.000,  -26.250 )
      Unit02L_6, size 29.846 x 64.000 x  9.500, position (    0.000,    0.000,  -26.250 )
      Unit03R_7, size 41.664 x 64.000 x  9.500, position (    0.000,    0.000,  -15.750 )
      Unit03L_8, size 29.846 x 64.000 x  9.500, position (    0.000,    0.000,  -15.750 )
      Unit04R_9, size 29.846 x 80.000 x  9.500, position (    0.000,    0.000,   -5.250 )
     Unit04L_10, size 41.664 x 80.000 x  9.500, position (    0.000,    0.000,   -5.250 )
     Unit05R_11, size 41.664 x 80.000 x  9.500, position (    0.000,    0.000,    5.250 )
     Unit05L_12, size 29.846 x 80.000 x  9.500, position (    0.000,    0.000,    5.250 )
     Unit06R_13, size 41.664 x 92.000 x  9.500, position (    0.000,    0.000,   15.750 )
     Unit06L_14, size 41.664 x 92.000 x  9.500, position (    0.000,    0.000,   15.750 )
     Unit07R_15, size 41.664 x 96.000 x  9.500, position (    0.000,    0.000,   26.250 )
     Unit07L_16, size 41.664 x 96.000 x  9.500, position (    0.000,    0.000,   26.250 )
     Unit08R_17, size 41.664 x 96.000 x  3.526, position (    0.000,    0.000,   36.750 )
     Unit08L_18, size 41.664 x 96.000 x  3.526, position (    0.000,    0.000,   36.750 )
sts_passive_v19i_18, size 234.000 x 142.500 x 103.800, position (    0.000,    0.000,    2.680 )

top: size 234.0000 x 142.5000 x 103.8000, assembly
Daughters: 
     sts_v19i_1, size 234.000 x 142.500 x 103.800, position (    0.000,    0.000,   62.750 )

Info in <TGeoManager::CheckGeometry>: Fixing runtime shapes...
Info in <TGeoManager::CheckGeometry>: ...Nothing to fix
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit0A_half_Top_Part1" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit0A_half_Top_Part2" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit0A_half_Top_Part3" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit0A_half_POB" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit0A_half_Center" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit2A_half_POB" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit2A_half_Center" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3A_half_POB" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3A_half_Top_Part1" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3A_half_Top_Part2" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3A_half_Top_Part3" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3A_half_Center" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3B_half_POB" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3B_half_Top_Part1" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3B_half_Top_Part2" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3B_half_Top_Part3" has no medium: assigned dummy medium and material
Warning in <TGeoManager::CheckGeometry>: Volume "passive_unit3B_half_Center" has no medium: assigned dummy medium and material

Sone screenshots of STS v19a vs STS v19i and PIPE v16b_1e from setup_sis100_hadron.C:

There are overlaps to resolve with STS v19i.

I see in https://git.cbm.gsi.de/CbmSoft/cbmroot_geometry/blob/master/media.geo all required materials. I do not know where the error comes from.
Concerning overlaps I do not have input from mechanics to resolve it.

I was able to solve the materials issue. See attachment.
Overlap issue is still open.

These are the elements I removed in STS v19h and STS v19i from the inner part:

Hi Evgeny,

in your box for the STS v19i, from the gdml file,
I do not see the cutouts on the front and the backpanel,
see screenshots below - a comparison between STS v19a and v19i.

Could you please fix those cutouts?

STS box frontpanel

STS box backpanel

I finally got it:
new STS v19i with 105 mm station pitch and
new PIPE v16i with kink at the position of station 3.

Dear David, good job solving the overlap problem. As I understand, the target chamber and beam pipe were moved upstream. Does this break the integration with RICH and MUCH?
I've carefully redone the GDML. Now all cutouts should be in place. Please check.

Hi Evgeny,

the STS box looks much better now.

However, if I look upstream through the hole in the backside, the front panel is not completely open (see last 2 screenshots below).
Could you please increase the length of the cutout volume a few mm upstream, to clear that opening?

Dear David, I can not confirm that the walls are closed.
Using the very last GDML I attached - I can see through the entire detector.

Front

Dear David, I did not receive your feedback so far. Maybe due to my mistake not changing the assignee to you.

I have checked the target and MVD positions with STS v19a as reference:

z= 0, 8, 12, 16 and 20 cm

The MVD position does not change when displacing the pipevac1 volume, see below.
Here we do need a MVD with stations at z= 4, 8, 12 and 16 cm.

Finally, the STS v19i with a shifted MVD v17b TR in full glory and at the correct (!) positions:

There are two overlaps

Unexpected Overlap: = Overlap ov00000: cave/pipe_v16d_1e_0/pipe1_0 overlapping cave/sts_v19i_0/sts_passive_v19i_18/passive_Box_Wall_Front_Wrong_1 ovlp=0.247

Unexpected Overlap: = Overlap ov00001: cave/pipe_v16d_1e_0/pipevac1_0 overlapping cave/sts_v19i_0/sts_passive_v19i_18/passive_Box_Wall_Front_Wrong_1 ovlp=0.247

Hi Evgeny,

this seems to be an overlap between the MVD part of the beampipe and the STS box front wall.
I do not know how to edit the STS box gdml file, so I reassign this overlap issue to you.

Hello David,
I've tried to move the pipe upstream by 0.25 cm and overlaps are gone. Please check the global Z positioning of the pipe.
The STS as a whole was moved exactly by 2 cm upstream to compensate for 4 cm extension, so there is no chance of a deltaZ of 0.247 appearing.

Hello Volker,

the overlap is still present as of today when using STS v19i:

gGeoManager->CheckOverlaps(0.001);

[..]

root [3] gGeoManager->PrintOverlaps();
=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/magnet_container_0 overlapping cave/rich_v17a_1e_0/rich_container_290 ovlp=11.5
 = Overlap ov00001: cave/pipe_v16d_1e_0/pipe1_0 overlapping cave/sts_v19i_0/sts_passive_v19i_18/passive_Box_Wall_Front_Wrong_1 ovlp=0.247
 = Overlap ov00002: cave/pipe_v16d_1e_0/pipevac1_0 overlapping cave/sts_v19i_0/sts_passive_v19i_18/passive_Box_Wall_Front_Wrong_1 ovlp=0.247

It is not present with STS v19h:

gGeoManager->CheckOverlaps(0.001);

[..]

root [3] gGeoManager->PrintOverlaps();
=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/magnet_container_0 overlapping cave/rich_v17a_1e_0/rich_container_290 ovlp=11.5
root [4] 

STS v19i is a v19h with the adiidional STS box by Evgeny. So the overlap is between the pipe and Evgeny's STS box.
I do not know how to edit that box, so this problem should be resolved by Evgeny.

The STS as a whole was moved exactly by 2 cm upstream to compensate for 4 cm extension, so there is no chance of a deltaZ of 0.247 appearing.

It is not clear to me what is meant with this statement.

That bug prevents this long STS geometry to become the new default.

Beampipe overlap issue solved in #1737

I have backported the solution for the beampipe overlap issue for STS Box to v19i.

Hi,

I have discovered another overlap, which is not reported by the check:
It is an overlap between the downstream wall of the box intruding into the pipe v16d_1e.

As agreed per email of 29 June, not required for APR20. I thus shift to OCT20.

Mehul is working on it ...