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

IntegratePeaksMD: determine when the peak radius or background shell is falling off the detector edge #5844

Closed
mantid-builder opened this issue Mar 19, 2012 · 2 comments
Assignees
Milestone

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: @jzikovsky

Possibility one:

  • Like the inelastic people, create events for every bin so we know our coverage.
    • This is the OneEventPerBin option of ConvertToDiffractionMDWorkspace
    • Perhaps set the edge pixels to NANs to be a clear flag that you are going over the edge?

Possibility two:

  • It might be fastest to back-calculate the detector pixel and some points along the EDGES of the integration radii. Check if these are off the detector or on a masked pixel (requires the original MatrixWorkspace!). Flag radiuses that are too large?
    • Look at Peak::findDetector() method for the ray-tracing code that finds a detector.
    • The PredictPeaks::doHKL() builds up the Q vector to search for.
@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 4998

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants