-
Notifications
You must be signed in to change notification settings - Fork 18
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
Dectris file writer writes inverted beam; won't fix #542
Comments
Aha! Simples just invert the direction for that instrument serial number
nope |
OK, an afternoon of hacking later I think I have a reasonable logical check to see if your detector is upstream of the beam:
|
Hang on, maybe I am not so happy with that solution after all 🤔 |
This one I am happy with -> now need to work out how to edit the detector model to compensate -
|
What is the best way to get around this issue? Currently, I just invert the last value in the "origin" array manually, and then it seems to work. |
OK, I could have sworn that a fix went out for this along the lines described above. Digging through the history to verify. What version of DIALS are you using? |
If you could confirm that this is indeed fixed I will close this issue (since it has been fixed, but seems impolite to close an issue when a user has just reported the problem) |
Problem comes from SLS where they are using a newer version of the file writer which writes very nearly nexus which looks like NXmx but has inverted beam direction according to how we read.
This reads as NXmx but
yes the effective distance is -150mm
The text was updated successfully, but these errors were encountered: