-
Notifications
You must be signed in to change notification settings - Fork 71
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
Nanostring reader error #585
Comments
hi @jnmark , can you try to install from current main? the problem should be fixed |
fixed in main |
Hello @giovp , I have a similar issue (on squidpy 1.2.4.dev2+g1397d11): KeyError Traceback (most recent call last) File ~/.conda/envs/stpy/lib/python3.8/site-packages/squidpy/read/_read.py:255, in nanostring(path, counts_file, meta_file, fov_file) KeyError: '32' Thanks! |
hi @carlosf79 , I just tried by re-downloading the data and using latest squidpy from main and don't have any issue, it reads properly with these 2 expected warnings
could it be that you have 2 versions of squidpy installed in your conda env>? |
Hi @giovp , thanks for checking this. I have tried with two freshly made condaenvs, one with I have the same error in both cases. If I have installed things correctly, then it should be something else with my system - will look into it. Do you have any suggestions on what could potentially be? |
can you share the code snippet you used? |
@giovp I am also getting this Key Error pointing at this line in the sq.read.nanostring function, Squidpy v1.2.2 I'm wondering whether this actually has something to do with the files provided by Nanostring, do you have any sense of which input file I should look in to see if there is something improperly annotated as '26'? Worth noting that the function worked just fine in the same Conda environment on two other slides of data from the same Nanostring CosMx run |
Wait, yeah, this is probably an issue with the files provided by Nanostring. I just checked in /5 Raw Data/RunXXXX/CellComposite, CellLabels, etc. contain the wrong FOVs (from another slide of data that had 26 FOV instead of 23). I'd bet that's the problem Edit: Last update on this, I think that TAP has some bugs in the R code they use to generate these directories. The first 23 FOVs are correct but FOVs 24-26 are the same images as present for my other sample. So it must append extra images in certain cases! I manually deleted the extra FOV image files and I was able to import the dataset without trouble |
I think at should add a check that warns if the FOV file is present (but not in the annotations) and vice-versa. |
it'd be useful to know which dataset you have tried @cdpolt @carlosf79 , thanks! |
@giovp it is a dataset we generated from Nanostring Tech Access Program (if you think it would be helpful we can try figure out a way I can share some of the files with you to reproduce) but I am nearly positive the issue I am seeing with reader key error is due to their delivery of the data being misformatted, nothing to do with squidpy itself! just want others dropping by this thread to be able to try to fix their issue by removing the extra files from the folder as I did. |
I had the same error as above when downloading the dataset from this tutorial: https://squidpy.readthedocs.io/en/stable/external_tutorials/tutorial_nanostring.html
I fixed it by removing the lines with fov greater than 30 in the file "Lung5_Rep2_fov_positions_file.csv". |
Hello, I get the following error while trying to replicate the Nanostring tutorial. I tried installing both the 'dev' version from Github as well as Squidpy 1.2.2.
The text was updated successfully, but these errors were encountered: