SimTrackerHit Detector ID's are screwed up

[omar-moreno]

Issue

After the update to the new detector ID's, the module ID is now 0 for all layers. This is causing a mismatch between the detector ID from a hit and those associated with a detector element.

Solution

The SD needs to be updated so it sets the correct module ID. Currently, the module numbers are being calculated from the copy numbers. Going forward, either a dedicated module parameter needs to be added to the GDML or the calculation needs to be fixed.

[tvami]

@bloodyyugo have you looked at module IDs recently? Is this still an issue?