Ticket #3658 (assigned)
Mask tab lets you define coordinates that don't fall on a pixel boundary
Reported by: | Mathieu Doucet | Owned by: | Roman Tolchenov |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | MantidPlot | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
It's a little confusing to some users that you can define a rectangular mask with dimensions that doesn't correspond to detector boundaries. It's not clear what the system does to decide which detector is masked and which is not.
Change History
comment:1 Changed 9 years ago by Nick Draper
- Owner set to Roman Tolchenov
- Status changed from new to assigned
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 30 to Iteration 31
Bulk move of tickets to iteration 31 at the iteration 30 code freeze
comment:3 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:4 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:5 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:6 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:7 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:10 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:11 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:12 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 4505
This I think can be solved by documentation in the wiki pages, just explain how the detectors within the region are selected.