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

SANS: Consider spotting when user has entered SANS run instead of TRANS run in error #10112

Closed
PeterParker opened this issue Apr 7, 2014 · 2 comments
Labels
ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS Reported By User Issues that were found or highlighted by a user/scientist SANS Issues and pull requests related to SANS Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@PeterParker
Copy link
Contributor

sans_bugfix
This issue was originally TRAC 9269

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.

@PeterParker PeterParker added the SANS Issues and pull requests related to SANS label Jun 3, 2015
@PeterParker PeterParker self-assigned this Jun 3, 2015
@AntonPiccardoSelg
Copy link
Contributor

That might be hard to do, especially since we allow the detector regions for TRANS now.

@gemmaguest gemmaguest added the ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS label Aug 29, 2019
@gemmaguest gemmaguest added the Reported By User Issues that were found or highlighted by a user/scientist label Jul 29, 2020
@DavidFair
Copy link
Contributor

I'm going to close this as stale as we haven't heard much about it
If users are still running into it often enough to warrant work feel free to re-open it and we can look at it

@DavidFair DavidFair added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ISIS Team: LSS Issue and pull requests managed by the LSS subteam at ISIS Reported By User Issues that were found or highlighted by a user/scientist SANS Issues and pull requests related to SANS Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
Status: Stale
Development

No branches or pull requests

5 participants