Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Further work on error bars #5316

Closed
1 task done
mantid-builder opened this issue Jan 11, 2012 · 3 comments
Closed
1 task done

Further work on error bars #5316

mantid-builder opened this issue Jan 11, 2012 · 3 comments
Assignees

Comments

@mantid-builder
Copy link
Collaborator

This issue was originally TRAC 4469

Original Reporter: Russell Taylor

This ticket is blocked by :

Error bars can now be customised, but for Mantid curves this can only be done from Python, not from the plot dialog. It seems a pity (in more ways than just this) that apparently no regard was made to how QtiPlot does error bars when the ability was added to show Mantid error bars, because if it had been done in a similar way (having a separate curve for the error bars) customisation options would have appeared in the dialog 'for free'.

The following should be looked at:

  • Modifying Mantid error bar characteristics from the plot dialog.
  • Showing X errors.
  • The ability to add custom errors (e.g. % or from a table) to Mantid Curves (at the moment only the workspace errors can be attached to the curve unless it's first exported to a table).
  • Pulling in improvements made in today's QtiPlot to the way error bars are drawn (see the QwtErrorPlotCurve class, now called ErrorBarsCurve in QtiPlot).
@mantid-builder
Copy link
Collaborator Author

@NickDraper (2012-04-30T14:12:53):
Moved at end of release 2.1


@NickDraper (2012-08-10T12:43:37):
Moved at the end of release 2.2


@NickDraper (2012-10-28T11:38:49):
Moved to milestone 2.4


@NickDraper (2013-01-28T09:23:01):
Moved at the code freeze for release 2.4


Russell Taylor (2013-04-16T20:55:32):
Move the tickets I'm definitely not going to do this iteration so that I can better see the ones that I might.


@NickDraper (2013-07-26T13:54:58):
Moved to backlog at the code freeze for R2.6


@NickDraper (2014-02-14T11:04:56):
Bulk move to assigned at the introduction of the triage step


Russell Taylor (2014-06-16T19:08:52):
Orphaning tickets that I won't have time to look at.

@NickDraper NickDraper self-assigned this Feb 12, 2016
@NickDraper NickDraper added this to the Release 3.8 milestone Feb 12, 2016
@NickDraper
Copy link
Contributor

This is actually a valuable ticket that was echoed to some extent in the last SSC. Assigned to PM so it doesn't get lost.

@NickDraper NickDraper modified the milestones: Release 3.8, Release 3.9 Oct 3, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 14, 2016
@NickDraper
Copy link
Contributor

Will be superceeded in M4, closing

@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants