EnginXFitPeaks expected Peak analysis problem

[lottiegreenwood]

This issue was originally TRAC 10907

This ticket is blocks : TRAC8368

When entering a list of expectedPeaks into FitPeaks, if one expected peak is not there, the algorithm will stop and not produce any results. If just one peak is out of range of the data then this should be stated but otherwise ignored. If all expectedPeaks are not there then the algorithm should fail gracefully.

This affects EnginXCalibrate and CalibrateFull which both utilise FitPeaks.

[lottiegreenwood]

@NickDraper (2015-04-27T08:10:34):
Moved to R3.5 at the R3.4 code freeze

---

Federico M Pouzols (2015-05-06T15:52:18):
(In http://trac.mantidproject.org/mantid/ticket/8368) Added new ENGIN-X tickets that have been opened in the last few months as 'blocked by'.

---

Federico M Pouzols (2015-06-02T21:11:32):
Note that in addition to

• sometimes FindPeaks will not find the expected peaks
  The following can happen:
• FindPeaks finds them, but it produces 0 width and/or height
  This is currently skipped with an if... continue when processing the workspace spectra.

[FedeMPouzols]

It looks like this is the behavior that we want: if errors such as 'some peaks were not found by FindPeaks' happen, the calibration algorithms should continue as far as possible. The output files generated will have a suffix like '_with_errrors` appended, to give a hint.

When used from the GUI, a pop-up should warn the user, before the "peaks diagnostics" visualization, but it should still be possible to go on and then accept the diagnostics step and save the files.