Ticket #9269 (assigned)
SANS: Consider spotting when user has entered SANS run instead of TRANS run in error
Reported by: | Peter Parker | Owned by: | Peter Parker |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | SANS | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description (last modified by Peter Parker) (diff)
From Ann:
Using the SANS-ISIS gui, for LOQ, we can (in error) enter a SANS run number in the TRANS and direct beam boxes. Mantid then uses spectrum 3 to reduce the data but this is the bottom left hand pixel in the LOQ case. Would it be possible to catch this error for just LOQ please? It could be done just by looking at the number of spectra in the file to decide between SANS and TRANS.
Further comment from Steve:
When Ann says ‘bottom left hand pixel’ she means of the main (rear) detector. This MAY also affect SANS2D when it is using M3, rather than M4, for transmissions as then it, too, has separate SANS & TRANS runs.
Change History
Note: See
TracTickets for help on using
tickets.