Skip to content
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

Cleanly handle volumes missing slices #11

Open
csparker247 opened this issue Apr 2, 2023 · 1 comment
Open

Cleanly handle volumes missing slices #11

csparker247 opened this issue Apr 2, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@csparker247
Copy link
Member

Since the volume is lazy loaded at runtime, missing slices can cause a number of unexpected crashes across our various programs. Need to review the current behavior on image load and its effect on the apps. Might also want to add a verification util or something.

@csparker247
Copy link
Member Author

#18 will keep VC from crashing, but this doesn't really handle any of the other edge cases. Historically we've considered a missing slice a hard error since it could be a missing file, data corruption, etc.

Since the current paradigm seems to be leaning towards partial volume downloads, the behavior here needs to be rethought. In particular, we want to know when slices are missing and decide how to handle them based on context. A segmentation algorithm should probably stop when it's missing a slice, for instance, but a GUI might not care.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant