You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
dgault
changed the title
VSI:
VSI: Exception loading files from VS200 scanner with software version 3.4.1
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.The text was updated successfully, but these errors were encountered: