-
Notifications
You must be signed in to change notification settings - Fork 46
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
dials.export_bitmaps
with resolution rings
#2360
Conversation
Don't need unit_cell and space_group in this function
I see there are some artefacts at the image edges for the single panel case |
This might be more of an esthetic choice than anything, but what would you say about putting all phil parameters in one scope, i.e.:
|
Yeah, I'm inclined to agree that's better 👍 |
Ah, I know why I did that. It's because |
Ah, consistency is definitely also a great reason. I personally don't have particular interest in any version; I was just curious. |
These happen when a path has gone outside a panel and then back in. To keep the calculation simple just reject any segment with a dx or dy distance of > 30 pixels
Codecov Report
@@ Coverage Diff @@
## main #2360 +/- ##
==========================================
- Coverage 82.90% 78.51% -4.39%
==========================================
Files 593 602 +9
Lines 68592 73173 +4581
Branches 9221 9935 +714
==========================================
+ Hits 56863 57454 +591
- Misses 9613 13599 +3986
- Partials 2116 2120 +4 |
This adds optional resolution rings to
dials.export_bitmaps
. Additional PHIL controls are:Example with a P6M image:
This also works for multi-panel and non-coplanar detectors. For I23: