Proper handling of VOI specifications when fetching across neuroglancer fragment volumes
When fetching from a multi-fragment neuroglancer provider with a voi, the current implementation returned a full-size but almost empty volume. This PR tries to fix the problem, and had to address a couple of downstream issues with neuroglancer fetching.
It needs testing and independent review...
The design of neuroglancer volumes, scales, providers etc. appears overcomplicated and makes it difficult to solve this elegantly, but solving the higher level design will be part of siibra-python v2.
Codecov Report
Attention: Patch coverage is 19.51220% with 66 lines in your changes missing coverage. Please review.
Project coverage is 47.48%. Comparing base (
6ada413) to head (4bb16b4). Report is 14 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #656 +/- ##
==========================================
- Coverage 47.49% 47.48% -0.02%
==========================================
Files 71 71
Lines 7430 7432 +2
==========================================
Hits 3529 3529
- Misses 3901 3903 +2
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.