Ticket #3487 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Output from a fit does not contain errors

Reported by: Martyn Gigg Owned by: Roman Tolchenov
Priority: critical Milestone: Iteration 30
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Martyn Gigg

Description

Rob Dalgiesh reported that the output from running a Gaussian fit was a workspace that contained zeroes for all of the errors. This may only occur for the Gaussian function but the others should be checked as well.

Contact Rob if you need an example to recreate the bug.

Change History

comment:1 Changed 9 years ago by Nick Draper

  • Priority changed from major to critical

comment:2 Changed 9 years ago by Roman Tolchenov

  • Status changed from new to accepted

comment:3 Changed 9 years ago by Roman Tolchenov

In [14006]:

Added error bars to the Fit output workspace. re #3487

comment:4 Changed 9 years ago by Roman Tolchenov

In [14007]:

Cleared warnings. re #3487

comment:5 Changed 9 years ago by Roman Tolchenov

In [14008]:

There seems to be a problem with precompiled headers on the 32-bit windows build. re #3487

comment:6 Changed 9 years ago by Roman Tolchenov

  • Status changed from accepted to verify
  • Resolution set to fixed

comment:7 Changed 9 years ago by Martyn Gigg

  • Status changed from verify to verifying
  • Tester set to Martyn Gigg

comment:8 Changed 9 years ago by Martyn Gigg

  • Status changed from verifying to closed

Confirmed with a focussed GEM data set that the errors are also passed through to the final fit result workspace.

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4334

Note: See TracTickets for help on using tickets.