Add Vanadium consideration into EnginX algorithms

[Lottie Greenwood]

Currently EnginX CalibrateAll does not consider the vanadium number when calibrating. This is necessary to get useful calibration results.

In order to do this, there are two methods:

Method one

1) Add in option to load the ceria and vanadium numbers

2) Fit a spline to each pixel (V-Nb) and store them with vanadium in a filename

3) Divide each Ceria pixel by the spline

Method two

1) Add in option to load the ceria and vanadium numbers

2) Add together each V-Nb pixel to get 1 number (the sensitivity) and store it

3) Divide the ceria pixel with corrected sensitivity number

4) Convert unit to dspacing on V-Nb and add each bank together to get 2 spectr.

5) Fit spline to 2 spectrum and store

6) Convert unit ceria to dspacing and divide each pixel with the corresponding curve

7) Divide each ceria pixel by corrected sensitivity number

[Lottie Greenwood]

After testing, method 1 is found to be too noisy and not produce accurate results. So method 2 will be followed

[Lottie Greenwood]

From further discussion with EnginX Scientists, the scope of this ticket is expanded somewhat.

• CalibrateFull needs to include loading and preparing vanadium for fitting, along with a calibration

• Calibrate needs to do as above but save the two splines and sensitivities outputted from the vanadium calibration

• EnginXFocus should be renamed as EnginXDetFocus and a new EnginXFocus should be created that takes Difc and Zero from EnginXCalibrate rather than Detector Positions

[Nick Draper]

Moved to R3.5 at the R3.4 code freeze

[Federico M Pouzols]

(In #8368) Added new ENGIN-X tickets that have been opened in the last few months as 'blocked by'.

[Stuart Campbell]

This ticket has been transferred to github issue ​12426