Ticket #6820 (assigned)
Smarter Integrated Peak Area Plotting
| Reported by: | Owen Arnold | Owned by: | Owen Arnold |
|---|---|---|---|
| Priority: | critical | Milestone: | Backlog |
| Component: | Framework | Keywords: | |
| Cc: | Blocked By: | #6521, #7410, #7411 | |
| Blocking: | Tester: |
Description
In #6521 I implemented a warning around the fact that Peaks integrated using IntegratedPeaksMD, could be shown in the PeaksViewer/SliceViewer ontop of a workspace, that has a different coordinate system from the one the PeaksWorkspace was integrated in. i.e. You view peaks integrated using IntegratePeaksMD (from a workspace in LabQ), then you take the HKL workspace (ultimately made from the same LabQ workspace) and visualize that in the SliceViewer, with the integrated workspace ontop. The problem being that the radius is being shown in LabQ, whereas the underlying features of the MDWorkspace are in HKL coordinates.
To fix this, it should be possible to take the UB off the MDWorkspace (assuming it is a HKL one, which we can now determine using the getSpecialCoordinates routine). Then invert the UB and perform a multiplication with the Coordinates of the Radius endpoints. Then set the radius end points to be these newly calculated coodinates (should generate an elipse of some kind).
This is a feature Pascal wants, which is why the priority has been set high.
Change History
comment:9 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at R2.6 code freeze
comment:10 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
Bulk move to assigned at the introduction of the triage step
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 7666
