Ticket #3281 (closed: fixed)
Wrong data in single crystal peak selection tool
Reported by: | Andrei Savici | Owned by: | Andrei Savici |
---|---|---|---|
Priority: | blocker | Milestone: | Iteration 29 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Vickie Lynch |
Description
I loaded a file, selected peaks. The TOF reported in the peaks workspace is smaller than the TOF that I selected by a factor of about 2*Pi. Same if I use a workspace having d-spacing units
Change History
comment:1 Changed 9 years ago by Andrei Savici
- Owner changed from Roman Tolchenov to Andrei Savici
- Status changed from new to assigned
comment:2 Changed 9 years ago by Andrei Savici
- Status changed from assigned to verify
- Resolution set to fixed
comment:3 Changed 9 years ago by Andrei Savici
To test, when selecting a peak, note the TOF/dspacing/whatever and check if the same value is written in the peaks workspace
comment:4 follow-up: ↓ 5 Changed 9 years ago by Vickie Lynch
- Status changed from verify to verifying
- Tester set to Vickie Lynch
Note: See
TracTickets for help on using
tickets.
Found the problem: the Peak object constructor uses Q/(2*Pi) components