-
Notifications
You must be signed in to change notification settings - Fork 82
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
Reading in MERSCOPE sample data with squidpy.read.vizgen() doesn't work for every dataset? #686
Comments
hi @Laura-Waechter , could you try to install form main? let me know if it works, |
Thanks for your fast reply @giovp . I now tried to install it the way you suggested, but the matrix is still empty... |
can you try with #679 ? |
I replaced the code of the function with this: |
This issue should be resolved now. |
it is in main, thank you again @dfhannum . Am trying to cut release asap but encountering few hiccups, but should manage to do it this week. |
Hi guys, I'm encountering the same issue. The
from this line of code in Using the version in conda, I managed to run the function, but then the fov, volume, and center obs data is NaN. And I'm using the Human Breast Cancer data that is publicly available on vizgen website. |
Hi all, I'm still encountering this issue using squidpy.read.vizgen(), the obs from the AnnData object are only filled with NaN after changing line 164 of the squidpy.read.vizgen() function from |
hi both, I think the version in conda is not up to date yet, so please use the pip installable version |
Dear all,
I tried to follow this workflow (https://squidpy.readthedocs.io/en/stable/external_tutorials/tutorial_vizgen_mouse_liver.html) for the Human Liver cancer dataset (https://info.vizgen.com/ffpe-showcase) instead. But when using squidpy.read.vizgen(), the obsm and var from the AnnData object are only filled with NaN, despite the documents containing the same information as the mouse liver dataset. Did anyone have this problem before and knows how to solve it?
Thanks very much in advance!
The text was updated successfully, but these errors were encountered: