Multiple Fields on Different Placements of the Same GDML File

[Laurie Nevay]

Scenario: 1x gdml file for some geometry. Used twice either as an ‘element’ or a placement, but with a different field attached to it. Currently, the 1 gdml file is loaded and cached so I don’t load it again. However, the multiple field definitions are registered to the same logical volumes and ultimately just the last constructed field definition wins.

Solution: I should check the (geometry file name, field definition) combination for caching the loaded geometry rather than just the geometry file.

I’ve created a new test that reproduces this and will commit it with the fix in coming days.

[Laurie Nevay]

Fix Issue #331. Change the caching of loaded geometry (any format) to be keyed with the (filename, field) instead of just filename. This can also be nullptr for no field.

→ <<cset 4c4706136116>>