-
Notifications
You must be signed in to change notification settings - Fork 128
Crosshair bugfix release next #39598
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does indeed work as advertised. I tried with normal line plots.
Thanks for fixing those bugs we found with the plot crosshair, I don't envy you adding anything to the plotting interface, it's a minefield. |
…39611) We found a bug with the new crosshair plotting feature where its lines would show up in the plot settings (see comment #39598 (comment)) This pr gives the crosshair lines the label `'_nolegend_'` which means they are ignored by the plot settings. Co-authored-by: thomashampson <thomas.hampson@stfc.ac.uk>
Description of work
This PR handles errors that arises from crosshair functions interacting with mantid. PR 39491
The issue is when changing normalisation and error bars, the figure object is treated as mantid object such as mantidaxes with key word arg such as "workspaces". The crosshair, at the moment, is implemented purely as matplotlib object and would cause error and crash the plot. A quick fix is to catch these errors.
In the long term, we will integrate the crosshair as a mantid specific object for handling mantid data.
Summary of work
Fixes #39592 .
Further detail of work
To test:
Run the instructions in the smoking tests, specifically focusing on changing normalisation and error bars while crosshair is open.
This script can be used to quickly open the plot pannel for testing:
Reviewer
Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.
Code Review
Functional Tests
Does everything look good? Mark the review as Approve. A member of
@mantidproject/gatekeepers
will take care of it.Gatekeeper
If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.