geomGeant4: hadron-absorber and muon-shield field maps are mutually exclusive

[olantwin]

In python/geomGeant4.py (~line 193), the hadron-absorber field map is added in an elif of the muon-shield field-map branch:

if not shipGeo.muShield.WithConstField:
    ... defineFieldMap("muonShieldField", ...)
    fieldsList.append("muonShieldField")
elif not shipGeo.hadronAbsorber.WithConstField:
    ... defineFieldMap("HadronAbsorberMap", ...)
    fieldsList.append("HadronAbsorberMap")

So if the muon shield uses a field map (not a constant field), the hadron-absorber map is never added — even when both are configured as non-constant. Changing elif → if would make them independent, but this affects the composite global field, so a field/geometry expert should confirm whether the two maps are meant to coexist before changing the control flow. Flagged during a code review.

[olantwin]

@Gfrisella Could I please get a response here?

[Gfrisella]

Hi Oliver,
As already discussed in the last meeting, the hadron absorber's field map is included in the MS field map.
Therefore, I will exclude the file a priori.

[olantwin]

So no change is needed?

[Gfrisella]

I don't know who introduced the field map.
I can say from my point of view that you can even remove the option in python/geomGeant4.py.

[olantwin]

I don't know who introduced the field map.

Thomas did: 9445e00

I can say from my point of view that you can even remove the option in python/geomGeant4.py.

Could you please prepare a small PR to remove it along with the field map?

[Gfrisella]

ok