This reverts commit bd6530b5.

I'm reverting the change to precision in Parameter.h for now because this is causing test failures which are out of scope for this PR.

Re #21749

Moved code from FindPeaksMD into new method on Goniometer. Then added option onto peaks workspace.

No need for exclusion ranges, so code is cleaner. There is however now recursion, so performance will need to be tracked.

# 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.

Merge done to enable documentation be be fixed, because of removal of
alias directive and addition of related algorithms directive.

Signed-off-by: Karl Palmen <karl.palmen@stfc.ac.uk>

# 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.

These fixes were not applied by clang-tidy because they are either
inside a macro, not included by any source files or conditionally
compiled on a condition which is false on my OS.

They were found using grep -rnI '^[^/#*]*typedef' Framework/

Elliot Oram authored 7 years ago and Gigg, Martyn Anthony committed 7 years ago

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