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

VSI: Exception loading files from VS200 scanner with software version 3.4.1 #3859

Closed
dgault opened this issue Aug 10, 2022 · 1 comment · Fixed by #3925
Closed

VSI: Exception loading files from VS200 scanner with software version 3.4.1 #3859

dgault opened this issue Aug 10, 2022 · 1 comment · Fixed by #3925

Comments

@dgault
Copy link
Member

dgault commented Aug 10, 2022

Issue has been reported by multiple users on forum thread https://forum.image.sc/t/vsi-format-update-unable-to-open-new-files/70366/5

This appears to be recently occurring after performing a software update for VS200 scanner to software version 3.4.1

I can reproduce the issue with the sample dataset provided and standalone Bio-Formats 6.10.0. I have not got to root of the issue but it looks to be due to Bio-Formats finding more available files than it was expecting to. My initial though is that it may be related to the blob_21_f_Frame#0 files found in the stack10000 folder, moving those out of the fileset seems to allow for the image to be opened.

I have not confirmed what these additional files relate to, though there is a blob_21_f.meta file included. This looks likely to a be an update to the proprietary VSI spec as a result of the software update.

@dgault dgault changed the title VSI: VSI: Exception loading files from VS200 scanner with software version 3.4.1 Aug 10, 2022
@imagesc-bot
Copy link

This issue has been mentioned on Image.sc Forum. There might be relevant details there:

https://forum.image.sc/t/vsi-format-update-unable-to-open-new-files/70366/7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants