feat: New warm MS option Stellatryon v.2 added

[Gfrisella]

Checklist

• Changelog updated (if applicable)
• Commit message follows conventional commits
• CI checks pass

[olantwin]

First set of comments. More to come.

Please make sure run_fixedTarget.py also runs and that the overlaps are fixed.

[olantwin]

For the SND support, @antonioiuliano2 @eduard322, could you have a look?

[olantwin]

A few more comments

[olantwin]

I'm also confused about warm_opt. run_simScript.py, run_fixedTarget, CI and Changelog all disagree.

[Gfrisella]

@eduard322 @antonioiuliano2

I believe that the SND is currently fixed at a set position along the Z-axis and therefore does not adapt to changes in the Muon Shield (MS) configuration.

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagL_1 ovlp=18
 = Overlap ov00001: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagR_1 ovlp=18
 = Overlap ov00002: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetL_1 ovlp=9.82
 = Overlap ov00003: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetR_1 ovlp=9.82

I already modified the code in ShipMuonShield.cxx in order to create an aperture in the middle of the last two magnets; however, the SND location appears to be hard-coded in the Python script. As a result, overlaps occur between Magnet 3 (the last magnet in this case is Magnet 5) and the MTC.

[eduard322]

hi @Gfrisella, the SND location is glued to the center of the chosen magnet, i’ll modify it.

[eduard322]

@eduard322 @antonioiuliano2

I believe that the SND is currently fixed at a set position along the Z-axis and therefore does not adapt to changes in the Muon Shield (MS) configuration.

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagL_1 ovlp=18
 = Overlap ov00001: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagR_1 ovlp=18
 = Overlap ov00002: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetL_1 ovlp=9.82
 = Overlap ov00003: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetR_1 ovlp=9.82

I already modified the code in ShipMuonShield.cxx in order to create an aperture in the middle of the last two magnets; however, the SND location appears to be hard-coded in the Python script. As a result, overlaps occur between Magnet 3 (the last magnet in this case is Magnet 5) and the MTC.

Here is the commit with changes of the MTC and SiW locations (python/shipDetConf.py is changed): eduard322@f7e62ce

Feel free to cherry-pick it.

[Gfrisella]

@eduard322 @antonioiuliano2
I believe that the SND is currently fixed at a set position along the Z-axis and therefore does not adapt to changes in the Muon Shield (MS) configuration.

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagL_1 ovlp=18
 = Overlap ov00001: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagR_1 ovlp=18
 = Overlap ov00002: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetL_1 ovlp=9.82
 = Overlap ov00003: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetR_1 ovlp=9.82

I already modified the code in ShipMuonShield.cxx in order to create an aperture in the middle of the last two magnets; however, the SND location appears to be hard-coded in the Python script. As a result, overlaps occur between Magnet 3 (the last magnet in this case is Magnet 5) and the MTC.

Here is the commit with changes of the MTC and SiW locations (python/shipDetConf.py is changed): eduard322@f7e62ce

Feel free to cherry-pick it.

Please add also the possibility to choose the magnet, in a new version of MS we are studying the possibility to use the two magnets before the last one for the SND

[eduard322]

@eduard322 @antonioiuliano2
I believe that the SND is currently fixed at a set position along the Z-axis and therefore does not adapt to changes in the Muon Shield (MS) configuration.

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagL_1 ovlp=18
 = Overlap ov00001: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagR_1 ovlp=18
 = Overlap ov00002: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetL_1 ovlp=9.82
 = Overlap ov00003: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetR_1 ovlp=9.82

I already modified the code in ShipMuonShield.cxx in order to create an aperture in the middle of the last two magnets; however, the SND location appears to be hard-coded in the Python script. As a result, overlaps occur between Magnet 3 (the last magnet in this case is Magnet 5) and the MTC.

Here is the commit with changes of the MTC and SiW locations (python/shipDetConf.py is changed): eduard322@f7e62ce
Feel free to cherry-pick it.

Please add also the possibility to choose the magnet, in a new version of MS we are studying the possibility to use the two magnets before the last one for the SND

hey, can you send me the picture of the muon shield and with snd locations you consider. I’m quite confuse, should SiW and MTC be inside one magnet or as it was (SiW in the magnet before the last and MTC in the last magnet)?

[Gfrisella]

@eduard322 @antonioiuliano2
I believe that the SND is currently fixed at a set position along the Z-axis and therefore does not adapt to changes in the Muon Shield (MS) configuration.

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagL_1 ovlp=18
 = Overlap ov00001: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagR_1 ovlp=18
 = Overlap ov00002: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetL_1 ovlp=9.82
 = Overlap ov00003: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetR_1 ovlp=9.82

I already modified the code in ShipMuonShield.cxx in order to create an aperture in the middle of the last two magnets; however, the SND location appears to be hard-coded in the Python script. As a result, overlaps occur between Magnet 3 (the last magnet in this case is Magnet 5) and the MTC.

Here is the commit with changes of the MTC and SiW locations (python/shipDetConf.py is changed): eduard322@f7e62ce
Feel free to cherry-pick it.

Please add also the possibility to choose the magnet, in a new version of MS we are studying the possibility to use the two magnets before the last one for the SND

hey, can you send me the picture of the muon shield and with snd locations you consider. I’m quite confuse, should SiW and MTC be inside one magnet or as it was (SiW in the magnet before the last and MTC in the last magnet)?

This is the configuration at the moment:

[olantwin]

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/target_vacuum_box_1 overlapping cave/MuonShieldArea_1/MagnAbsorb_MiddleMagL_1 ovlp=3.39
 = Overlap ov00001: cave/target_vacuum_box_1 overlapping cave/MuonShieldArea_1/MagnAbsorb_MiddleMagR_1 ovlp=3.39
 = Overlap ov00002: cave/target_vacuum_box_1 overlapping cave/MuonShieldArea_1/MagnAbsorb_MagRetL_1 ovlp=3.39
 = Overlap ov00003: cave/target_vacuum_box_1 overlapping cave/MuonShieldArea_1/MagnAbsorb_MagRetR_1 ovlp=3.39
 = Overlap ov00004: cave/target_vacuum_box_1 overlapping cave/MuonShieldArea_1/MagnAbsorb_MagBotLeft_1 ovlp=3.39

[eduard322]

@eduard322 @antonioiuliano2
I believe that the SND is currently fixed at a set position along the Z-axis and therefore does not adapt to changes in the Muon Shield (MS) configuration.

=== Overlaps for FAIRGeom ===
 = Overlap ov00000: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagL_1 ovlp=18
 = Overlap ov00001: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MiddleMagR_1 ovlp=18
 = Overlap ov00002: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetL_1 ovlp=9.82
 = Overlap ov00003: cave/SiliconTarget_1 overlapping cave/MuonShieldArea_1/Magn3_MagRetR_1 ovlp=9.82

I already modified the code in ShipMuonShield.cxx in order to create an aperture in the middle of the last two magnets; however, the SND location appears to be hard-coded in the Python script. As a result, overlaps occur between Magnet 3 (the last magnet in this case is Magnet 5) and the MTC.

Here is the commit with changes of the MTC and SiW locations (python/shipDetConf.py is changed): eduard322@f7e62ce
Feel free to cherry-pick it.

Please add also the possibility to choose the magnet, in a new version of MS we are studying the possibility to use the two magnets before the last one for the SND

hey, can you send me the picture of the muon shield and with snd locations you consider. I’m quite confuse, should SiW and MTC be inside one magnet or as it was (SiW in the magnet before the last and MTC in the last magnet)?

This is the configuration at the moment:

eduard322@f66061e

I've added the SND_location key for macro/run_simScript.py with the default value of -1 (last magnet). The flexibility fully depends on the mechanism of creating the wholes in the magnet though...