Skip to content
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

Error on Step 15: No feature overlap between existing object and new layer data #646

Open
r-osorio opened this issue Mar 8, 2024 · 7 comments

Comments

@r-osorio
Copy link

r-osorio commented Mar 8, 2024

Hello,

Thank you for your wonderful product!

I am analyzing multiple datasets in parallel using a similar inferCNV code workflow. My datasets are integrated seurat objects which I have converted to inferCNV objects without issue. Four of my six datasets get through my workflow perfectly and without issue. Two of them however are throwing the same error on step 15 of my inferCNV analysis:

`STEP 15: computing tumor subclusters via leiden

INFO [2024-03-08 09:45:32] define_signif_tumor_subclusters(p_val=0.1
INFO [2024-03-08 09:45:35] define_signif_tumor_subclusters(), tumor: myTumor
INFO [2024-03-08 09:45:35] Setting auto leiden resolution for myTumor to 0.000278088
Error: No feature overlap between existing object and new layer data
Execution halted`

I am confused because all six datasets underwent the same preprocessing and clustering workflow before my cnv analysis (some even have the same cells - they are different combinations of integrated datasets). The only differences I can think of between datasets is the two that are throwing this error are by far the two largest datasets of the bunch.

Thanks for any help you can provide, I am stumped on how to troubleshoot this error since my other workflows ran successfully on the same code.

@kiritsugu233
Copy link

hey, I have the same problem. did you solve it?

@r-osorio
Copy link
Author

no fix yet - tried rebuilding the cnv object from the raw data/from scratch and the same error occurs. Really not sure where to go from here...

@mortadelo93
Copy link

Same error here...

@mortadelo93
Copy link

Hey, I could fix it by simply changing cluster names.
I had clusters as numbers so gave them a character name. That fixed it...

@kiritsugu233
Copy link

I will try it. thank you mortadelo93 !!

@r-osorio
Copy link
Author

All my samples already had cluster names as character strings. Will try renaming them to something else and running, @kiritsugu233 let me know if you have success. Thanks @mortadelo93

@sd68515
Copy link

sd68515 commented Aug 27, 2024

I encountered the same problem. Finally, the numerical column names of the clusters in the read data were renamed to the corresponding cell type names.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants