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

Move PeakTransform* and IPeak to Geometry from API #12706

Closed
OwenArnold opened this issue May 29, 2015 · 1 comment
Closed

Move PeakTransform* and IPeak to Geometry from API #12706

OwenArnold opened this issue May 29, 2015 · 1 comment
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Vates
Milestone

Comments

@OwenArnold
Copy link
Contributor

This ticket is blocks : TRAC11872, TRAC11878

In order to determine if a peak should be deleted when a cursor passes over it exact (x,y and derived z) positions, we need to know if it intersects the peak. The easiest and best way to do this is to utilise the PeakShape of each Peak to return a PeakBoundingBox. Each subtype of Peak should be able to deliver a PeakBoundingBox as it quite a general concept. However, PeakBoundingBox is in Geometry and PeakShape is in the subpackage API. This ticket is concerned with moving the SC Peak transform and shape components into Mantid Geometry Crystal.


Keywords: vates

@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 11868

@OwenArnold OwenArnold added Framework Issues and pull requests related to components in the Framework Vates labels Jun 3, 2015
@OwenArnold OwenArnold self-assigned this Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 3.5 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Vates
Projects
None yet
Development

No branches or pull requests

1 participant