-
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
Remove cache of Kabsch debugging #1761
Conversation
Was broken anyway for stills as image.index is always 0 Fixes #1734 Removed now redundant request dict as well
Yes, it would reopen #1213. What does change when moving through stills if not |
Is there an example dataset available somewhere I can look at to demonstrate #1734? |
Codecov Report
@@ Coverage Diff @@
## main #1761 +/- ##
=======================================
Coverage 67.22% 67.23%
=======================================
Files 616 616
Lines 69021 69012 -9
Branches 9618 9618
=======================================
Hits 46399 46399
+ Misses 20680 20671 -9
Partials 1942 1942 |
Still process imported experiments each have length 1 imageset -> index always 0, you iterate through imagesets. I will come up with a less destructive fix |
Reproduce: pick any sequence of still images, run through
stills processing need not have worked as the data will still have been imported |
By simply computing a hash of the settings including the imageset this still fixes the bug whilst leaving the other thing still fixed. Changing a request dict to a simple hash of a tuple of the settings stops a future reader from working through the code looking for where that request is sent to. Also named the hash the same as the object which is hashed, to make the connection clearer. Bug still fixed, no previous bugs restored. I believe these are good changes.
@phyy-nx @dagewa I have restored the fix to #1213 but restructured the code rather than aiming for a minimal change. Motivation:
FWIW simply including the |
This looks like a better solution. I did wonder if we could use |
@ndevenish are the build errors related to PR or some external influence? I cannot tell 🤔 |
cctbx/cctbx_project#627 to blame |
By simply computing a hash of the settings including the imageset this still fixes #1734 whilst leaving #1213 fixed. Changing a request dict to a simple hash of a tuple of the settings stops a future reader from working through the code looking for where that request is sent to. Also named the hash the same as the object which is hashed, to make the connection clearer.
Was broken anyway for stills as image.index is always 0 so did not update when moving to next frame.
Fixes #1734
Removed now redundant
request
dict as well