-
Notifications
You must be signed in to change notification settings - Fork 153
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
WIP: Refactor PV slicing tool #1663
base: main
Are you sure you want to change the base?
Conversation
6b4340d
to
b6b7b6e
Compare
Codecov Report
@@ Coverage Diff @@
## main #1663 +/- ##
==========================================
- Coverage 88.07% 87.64% -0.43%
==========================================
Files 247 247
Lines 23279 23272 -7
==========================================
- Hits 20502 20397 -105
- Misses 2777 2875 +98
Continue to review full report at Codecov.
|
6e2adab
to
26c08af
Compare
26c08af
to
fbe991f
Compare
fbe991f
to
054244a
Compare
…ion of compute_statistic
…edData.compute.fixed_resolution_buffer to ensure that multiple sliced datasets can be shown at the same time
…isabled by default
054244a
to
b5fc6e6
Compare
I'm currently stuck on an issue with Matplotlib getting stuck in an infinite loop in the following case:
When the path is updated, the second viewer then gets stuck in a drawing loop and never renders fully. Some things that seem to matter - if in the state class for the image viewer I return a random array instead of the fixed resolution buffer after the initial call, then there is no infinite loop. If I do the same in the PV SlicedData, it sometimes helps and sometimes not (randomly). This makes me think there is a race condition of some kind. |
Actually I think I found where the issue comes from - if I change the
then I get the following error which shouldn't be happening:
|
Still very early days... Remaining things to do in this PR:
Things that could be done in future:
Other thoughts