-
Notifications
You must be signed in to change notification settings - Fork 25
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
Issues with reading 10X VISIUM Cytassist data SpaceRanger Output #76
Comments
Hi Jimmy, thanks for reporting. Can you try using the latest main version? @giovp worked on a related problem on #51 and therefore it could be fixed now. Otherwise, @giovp could you please have a look? Maybe we could test the various SpaceRanger versions with scripts in the spatialdata-sandbox that I run nightly, wdyt? |
Hi @LucaMarconato ,
|
Same issue here... the IO function should ideally support both h5 files with and without |
I had the same issue now with the naming of the files, it would be very useful to have the option to load without the prefix. |
The PR #91 should fix the problem. I haven't made a full test like @giovp did in #51 of the various SpaceRanger versions, but I am testing against three datasets (see details in the PR), including one that doesn't contain the Please @grst @benedekp @ilia-kats @thjimmylee, if you have the change let me know if this fixes your problem. If not I am happy to be more systematic and include more datasets in the nightly job. |
Hi,
This is a cool spatial tool, but I run into issue might be specific to the new Visium Cytassist SpaceRanger output
For instance, if I directly read the spaceranger output using
spatialdata_io.visium
, I would get the error below:By reading the error message, I got that the tool was expecting to have a library_id for the matrix.h5 file, which is not essentially included in the spaceranger output, but I renamed it with some random string and it worked, but then I encounter another error message as shown below:
Below is the file tree of the spaceranger output:
I am currently using the latest version of Space Ranger 2.0.1 (January 18, 2023).
The text was updated successfully, but these errors were encountered: