fix: multiframe image prefetch logic #3097
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the StudyPrefetcher is enabled, it prefetches the images of the current stack (and a prop is passed to react-cornerstone-viewport to stop it from prefetching).
Unfortunately, the code in StudyPrefetcher that computed which imageIds should be fetched was broken for multiframe images. As a result, nothing except the current image got loaded (triggering a load on every stack scroll, which is not great).
The first issue was that StudyPrefetcher used a non existent property
numFrames
, which made it think all images have a single frame (undefined > 1
is false).The second issue was that the getImageId standalone function delegates to InstanceMetadata#getImageId, but without passing along its arguments (the
frame
argument, in particular).The third issue was that InstanceMetadata#getImageId cached its return value, but that's not ok to do when the frame argument can vary.