Ticket #3169 (closed: wontfix)

Opened 9 years ago

Last modified 5 years ago

Add ability to inspect event lists in MantidPlot

Reported by: Russell Taylor Owned by: Peter Peterson
Priority: major Milestone: Release 2.6
Component: MantidPlot Keywords:
Cc: lynchve@… Blocked By:
Blocking: Tester: Mathieu Doucet

Description

Matt Frost was asking how he could look at the actual events in his workspace. The answer: not easily (possible via python I suppose but that doesn't qualify as easy enough).

We should add some way of looking at the events in a MantidPlot table. One suggestion would be to allow the construction and display of a table containing the events for a particular pixel via a right-click option on the matrix display. The list could be long, of course, but my expectation is that MantidPlot would cope.

Change History

comment:1 Changed 9 years ago by Russell Taylor

  • Cc lynchve@… added

comment:2 Changed 9 years ago by Janik Zikovsky

  • Milestone changed from Iteration 29 to Iteration 30

Moved my tickets that won't get finished by iteration 29

comment:3 Changed 9 years ago by Janik Zikovsky

Russell, who is most familiar with the QtiPlot interface? do you think this is something Roman could do more easily than myself?

comment:4 Changed 9 years ago by Russell Taylor

Roman would certainly have the most experience with this if he's able to allocate the time to it. Otherwise, I can help you to some extent. We should be sure to use Qt's model-view-presenter mechanism to avoid copying the data and only pull it through when it's in view. We also have to hook it up such that any table is deleted when the workspace is.

comment:5 Changed 9 years ago by Janik Zikovsky

  • Milestone changed from Iteration 30 to Iteration 31

comment:6 Changed 9 years ago by Nick Draper

  • Milestone changed from Iteration 32 to Iteration 33

Moved to iteration 33 at iteration 32 code freeze

comment:7 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.1 to Release 2.2

Moved at end of release 2.1

comment:8 Changed 8 years ago by Janik Zikovsky

  • Owner changed from Janik Zikovsky to Peter Peterson
  • Status changed from new to assigned

Hi Pete,

Here's an old ticket that would be kind of nice to have!

comment:9 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.2 to Release 2.3

Moved at the end of release 2.2

comment:10 Changed 8 years ago by Nick Draper

  • Milestone changed from Release 2.3 to Release 2.4

Moved to milestone 2.4

comment:11 Changed 8 years ago by Peter Peterson

  • Milestone changed from Release 2.4 to Release 2.5

comment:12 Changed 7 years ago by Nick Draper

  • Milestone changed from Release 2.5 to Release 2.6

Moved to r2.6 at the end of r2.5

comment:13 Changed 7 years ago by Peter Peterson

  • Status changed from assigned to accepted

comment:14 Changed 7 years ago by Peter Peterson

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

#7208 is adding more bits to the python side of things. While it doesn't take care of the "I'd like a table of events," it does allow the user more access to the events for inspection.

comment:15 Changed 7 years ago by Mathieu Doucet

  • Status changed from verify to verifying
  • Tester set to Mathieu Doucet

comment:16 Changed 7 years ago by Mathieu Doucet

  • Status changed from verifying to closed

I don't think it really made sense anyway...

comment:17 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4016

Note: See TracTickets for help on using tickets.