Ticket #7410 (assigned)
EllipsoidPeakRepresentation
Reported by: | Owen Arnold | Owned by: | Owen Arnold |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | GUI | Keywords: | |
Cc: | Blocked By: | #7411 | |
Blocking: | #6820 | Tester: |
Description (last modified by Nick Draper) (diff)
New algorithm for Crystal called EllipsoidPeakRepresentation which outputs a table workspace (much like PeaksInRegion and PeaksOnSurface) linking a peak index, with some additional information to describe the peak as an ellipsoid in a particular coordinate system.
This algorithm can then be used under-the-hood by the slice viewer to transform the representation of integrated peaks, such that it aligns correctly with the MDWorkspace being shown.
Rough procedure would be as follows.
- Input a PeaksWorkspace and fetch the coordinate system used for the integration ( via getSpecialCoordinates )
- Input an MDWorkspace and fetch it's special coordinate system ( via getSpecialCoordinates ). Call this the target coordinate system.
- Fetch the integration radius (same for all peaks) and origin (different from all peaks) from the peaks workspace.
- According the the special coordinate system of the peaks workspace and the target coordinate system calculate the transformation matrix required to move the peaks workspace into the target coordinate system.
- Now for each peak, use the radius, and the position to calculate information that could be used to describe a 3D ellipsoid. {Not sure how best to do this yet}. Write this information out into the output workspace.
Change History
comment:2 Changed 7 years ago by Nick Draper
- Owner set to Owen Arnold
- Status changed from new to assigned
- Component changed from Framework to VATES
- Description modified (diff)
comment:5 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at the code freeze for R2.6
comment:6 Changed 7 years ago by Owen Arnold
- Milestone changed from Backlog to Release 3.0
Duration = 2 days
comment:7 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.0 to Backlog
Moved out to backlog as not enough time in R3.0
Note: See
TracTickets for help on using
tickets.