-
Notifications
You must be signed in to change notification settings - Fork 15
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
Sopa read: Could not infer dataset_id
#146
Comments
Hello @GBeattie, thanks for reporting. Could you show me which file names are inside your Normally, it should contain a file that ends with Hope this helps! |
Thanks @quentinblampey for the speedy response! Yes I've followed those instructions, apart from missing the "Morphology_ChannelID_Dictionary.txt" file, which wasn't included in the AtoMx export, which will be my next issue to sort out! ls of my data directory below with the error
|
@GBeattie I think the issue comes from the fact that you used Can you try to use a relative path instead, as below: sopa read --technology "cosmx" Sam_reseg_30_10_2024_15_42_51_118 You should still have an error though, because you're missing the |
Thanks again, yes you're right! I was adjusting the path as I was previously getting an error that implied sopa was generating an incorrect path by repeating the first directory in the path (i.e "Sam_reseg_30_10_2024_15_42_51_118/" is put incorrectly as "Sam_reseg_30_10_2024_15_42_51_118/Sam_reseg_30_10_2024_15_42_51_118/"), which is now happening again with that command:
|
Hum, it seems that the So, I'll fix this, but meanwhile can you try using the API and specifying the from sopa.io import cosmx
sdata = cosmx("Sam_reseg_30_10_2024_15_42_51_118", dataset_id="L1_SU500") Sorry for these issues, the cosmx reader is still "new"/experimental, it should become more stable in the future! |
@quentinblampey, no problem at all, from my limited CosMx experience it is the most difficult spatial platform due to changing file formats and poor documentation, which probably underpins my issues running Sopa.. On a first note about "Morphology_ChannelID_Dictionary.txt", it looks to me as this may not be included in the outputs (at least in my case). A bit of digging and I found this page: https://nanostring-biostats.github.io/CosMx-Analysis-Scratch-Space/posts/napari-cosmx-basics/using-napari-cosmx.html that puts the file in the RunSummary directory, however in my case it's not there:
As for the API, I do get an error although an easy fix in theory (apart from the inevitable error due to missing "Morphology_ChannelID_Dictionary.txt").
And here are my column names for that file:
I can see in issue #63 and #65 that different AtoMx versions/output options have different column names so I can adjust as needed when I have some time this week, more worrying if AtoMx isn't generating "Morphology_ChannelID_Dictionary.txt" though, note: my AtoMx version is 1.3.2. |
Indeed the documentation is quite poor, and it seems the exports are different for everyone... Have you exported the data as shown in this comment? It seems he was also using version 1.3. I hope that you'll be able to get the right output by changing the way the data is exported! Else, I'll need to better understand the difference in terms of outputs depending on the AtomX versions, which may be difficult |
I just re-exported the FlatFiles only (previously I did both Flat and Raw), but no difference to the column names of that file. I'll keep an eye out to see any changes/other issues related to the missing "Morphology_ChannelID_Dictionary.txt" file as I'll be unable to proceed without it in any case. Thanks, and good luck wrangling with AtoMx versions, a very difficult task! |
Okay, please let me know if you have any updates on your side! |
Hi, trying to read a cosmx run using this CLI command:
sopa read --technology "cosmx" /Sam_reseg_30_10_2024_15_42_51_118
Here is the full error:
Running python 3.9.10 on UNIX.
Thanks in advance for any assistance!
All the best,
Gordon
The text was updated successfully, but these errors were encountered: