Ticket #4496 (closed: fixed)
PeakIntegration: option not to limit by Run Number
Reported by: | Janik Zikovsky | Owned by: | Vickie Lynch |
---|---|---|---|
Priority: | minor | Milestone: | Release 2.1 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Janik Zikovsky |
Description
It might also be nice to have an option to NOT restrict by run number; maybe two runs were at the same goniometer setting but different temperature and you want to compare.
As a more general note, your code relies on the PeaksWorkspace to be sorted by run number, which is not guaranteed.
Change History
comment:2 Changed 9 years ago by Vickie Lynch
Refs #4496 new option and do not rely on sorted run numbers
Changeset: 0bfa1f093b417b4ddc8f961d71f398093920a5ce
comment:3 Changed 9 years ago by Vickie Lynch
Refs #4496 only integrate peaks on loaded banks
Changeset: 5a8a96d1e405f9ed0ce90da31a27c691c7b38f8b
comment:4 Changed 9 years ago by Vickie Lynch
Refs #4496 Use VisibleWhenProperty instead of custom dialog
Changeset: 794d748abcdb25a8acc8bfc413fa14ff97773846
comment:5 Changed 9 years ago by Vickie Lynch
- Status changed from accepted to verify
- Resolution set to fixed
PeakIntegration has an option MatchingRunNo and does not rely on the PeaksWorkspace being sorted by run number. Also custom dialog was replaced with VisibleWhenProperty for ShoeBox Limits.
comment:6 Changed 8 years ago by Janik Zikovsky
- Status changed from verify to verifying
- Tester set to Janik Zikovsky