Inconsistent coordinates when accessing geometry

[mferril]

I am writing to report a bug I discovered while working on run_simScript.py.

In short, the halfpoint position of the decay volume accessed through ship_geo.decayVolume.z in run_simScript.py, which correctly returns the value 0 cm (as the origin of the reference frame)

decayVolume: {'z': 0.0, 'length': 5000.0}

does not correspond to what you get via geometry navigation in getGeoInformation.py, returning 22 cm instead of the origin of the coordinate system:

   Detector element             z(midpoint)     halflength       volume-start volume-end   dx                x-start       x-end       dy                y-start     
  6 DecayVolume_1               : z=   22.7500cm  dZ= 2500.7500cm  [-2478.0000    2523.5000] dx=  224.0000cm [ -224.0000     224.0000] dy=  324.0000cm [ -324.0000     324.0000]                    dummy

FYI: @antonioiuliano2

[olantwin]

We should probably read decayVolume.length and z from the yaml. In this case, I think getGeoinformation is correct, but it would be good to confirm.

[olantwin]

Thanks for reporting the issue!