Incorporate Calibration information into the SCD workflow

[Ruth Mikkelson]

The LoadIsawPeaks algorithm must incorporate the calibrated instrument information that's written at the top of the peaks file. The detector position information from the peaks file must be used to update the positions of the detector pixels so the corrected positions are also used by other algorithms.

[Ruth Mikkelson]

Refs #5487 LoadIsawPeaks now incorporates Calibration info

Values in test programs were slighly off. Also, changes were needed when the instrument was parameterized from the start.

Changeset: 23894feec97044c7960fe22fe19c4b6284f9be2a

[Ruth Mikkelson]

Refs #5487 LoadIsawPeaks now incorporates Calibration info

Values in test programs were slighly off. Also, changes were needed when the instrument was parameterized from the start.

Changeset: 23894feec97044c7960fe22fe19c4b6284f9be2a

[Nick Draper]

Moved at the end of release 2.2

[Dennis Mikkelson]

This ticket was tested as follows. TOPAZ 5637 was loaded and converted to a diffraction MD workspace. Find peaks MD was used to find 500 peaks. FindUBUsingFFT then reported that 490 of 500 peaks would be indexed to within 0.1. To test the use of calibration information, an ISAW DetCal file with more accurate detector positions was loaded into the TOPAZ 5637 event file. After converting this calibrated workspace to a diffraction MD workspace, peaks were again found and indexed. In the peaks workspace using calibrated data, 496 of 500 peaks were indexed to within 0.1, so the calibration gave more accurate peak positions. Finally, the calibrated peaks workspace was saved using SaveIsawPeaks and loaded to a different workspace using LoadIsawPeaks. When FindUBUsingFFT was used on the reloaded peaks workspace, 496 of 500 peaks were again indexed to within 0.1, indicating that the calibration information from the top of the peaks file was used by LoadIsawPeaks, rather than the default detector positions.

[Stuart Campbell]

This ticket has been transferred to github issue ​6333