You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Original Reporter: @jzikovsky
Possibility one:
Possibility two:
The text was updated successfully, but these errors were encountered: