Allow the same detector ID for multiple components in IDF

[Anders Markvardsen]

At the moment unique detector for each detector component.

This has worked well. But first Ron needs a new IDF for Polaris and now Matt upgrade for Pearl, and it would make the resulting IDFs cleaner if can assign the same ID to multiple components.

The effect of this will be merged detector geometries, i.e. as the IDF is read detector geometries will equal the sum of components with the same ID.... These merged detector shapes will still have unique IDs.

[Anders Markvardsen]

Suggestion for new XML along the lines of

<component type="bank" name="A" /> <component type="bank" name="B" />

<combined-component name="combined A-B">

<to-be-deleted name="A" ids="..."/> <to-be-deleted name="B" ids="..."/> <new-ids ... /> <new-parent name=""/>

</combined-component>

[Anders Markvardsen]

Although unlikely to be needed to be implemented now. If this was implemented XML could alternatively be:

<combine-detectors>

<from> <IDs> </from> <from> <IDs> </from> <from> <IDs> </from>

<new-component-name> <parent> i.e. what is the parent of these new shapes <new-ids>

</combine-detectors>

The code for implementing this

1) get Objects which will be combined 2) get rotation matrix and translation vector of objects relative to new parent 3) apply rotation matrix and vector to the surfaces contained in objects 4) somehow create a new object which is the union of the surfaces contained in the objects in 3) 5)...

[Anders Markvardsen]

After a number of discussions it was decided to leave this for another day since Matt (PEARL) and Ron (new POLARIS) can get by with the current setup

[Nick Draper]

This can be achieved using the current sp-det map

[Stuart Campbell]

This ticket has been transferred to github issue ​3904