Fitting result changes depending on log level

[MichaelWedel]

This issue was originally TRAC 10515

While I was doing some experimental work on POLDI 2D-fitting, I discovered that the result depends on the log level. For log-level information or debug, the fit converges differently and gives a different result.

Since this was experimental work, I will just push the small changes I made to reproduce this problem.

[MichaelWedel]

@MichaelWedel (2014-11-07T14:52:09):
Refs http://trac.mantidproject.org/mantid/ticket/10515. Adding latest parameters for comparison.

Current software works with those parameters, so for comparison they are required.

4d92843

---

@MichaelWedel (2014-11-07T14:52:09):
Refs http://trac.mantidproject.org/mantid/ticket/10515. Small changes to PoldiCalculateSpectrum2D

06dafd9

---

@MichaelWedel (2014-11-07T15:04:10):
Refs http://trac.mantidproject.org/mantid/ticket/10515. Adding test data

3f4e305

---

@MichaelWedel (2014-11-07T15:05:41):
Script (UsageData-directory must be configured as data directory):

fileRange = range(73,76)

workspaces = []
for i in fileRange:
    wsName = "243%s" % (i)
    workspaces.append(wsName)
    LoadSINQFile("poldi2014n0243%s.hdf" % (i), "POLDI", OutputWorkspace=wsName)
    LoadInstrument(wsName, InstrumentName="POLDI")

SiWs = GroupWorkspaces(InputWorkspaces=','.join(workspaces))
Merged=PoldiMerge(SiWs)

PoldiAutoCorrelation(InputWorkspace='Merged', OutputWorkspace='corr')
PoldiPeakSearch(InputWorkspace='corr', MaximumPeakNumber=30, OutputWorkspace='corrPeaks')
PoldiFitPeaks1D(InputWorkspace='corr', FwhmMultiples=4, PoldiPeakTable='corrPeaks')
DeleteTableRows(TableWorkspace='RefinedPeakTable', Rows='10-15')
PoldiCalculateSpectrum2D(InputWorkspace='Merged', PoldiPeakWorkspace='RefinedPeakTable', PeakProfileFunction='Gaussian', OutputWorkspace='d')

[FedeMPouzols]

@MichaelWedel : for when you're back, I think that this issue was solved as #12948. And by the way we 'fixed' one of your Poldi tests for that change (see PR #12961) so please close this issue if you think that the problem is gone now.

[MichaelWedel]

As suggested by @FedeMPouzols, the issue has been solved in another context, so I'm closing this issue.