This makes these algorithms consistent with the rest of the code base.

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.

Elliot Oram authored Mar 14, 2018 and Gigg, Martyn Anthony committed Mar 15, 2018

PredictFractionalPeaks was using a new raytracer for every peak it created and therefore throwing away the caching information about the bounding boxs of detectors / panels causing a huge slow down. Resolved by exposing the findDetector(raytracer) overload to IPeaks and using single raytracer for all calls.
Work also include small refactor for const autos

Refs #22060

re #15289

re #15289

Refs #13156

They had previously been changed to Vectors as a fix, however they have now been changed to implement strings to set the values so that this issue can be fixed in a more general sense.
Refs #13156

When passing a string of values, the PropertyWithValue
constructor gets called and uses an empty vector
resulting in the value never being set when changed by the user.


Refs #13119

Refs #9642

and put back the usage example for PredictFractionalPeaks that was failing.
It failed because Python didn't understand the type of output
it was trying to give back.
Refs #9642