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

A possible explanation for issues with Clustree not finding enough clustering data #104

Open
beazors opened this issue Jan 31, 2025 · 0 comments

Comments

@beazors
Copy link

beazors commented Jan 31, 2025

Hello,

Thanks for developing this package, I have used it for several years. Recently I went to test my old Clustree code to help a colleague with their data, and found that I had the same issue as others mentioned in issues #51 and #86.

I had previously written code to run FindClusters at different resolutions (it was written as a loop), and the resulting factor of cluster identities at each resolution used to be saved by default into the object's meta.data (e.g., "integrated_snn_res0.1").

In testing out my old code, I realized that this no longer happens. It looks like Seurat was modified in later updates such that, after clustering, the IDs and SNN are no longer stored, see here and here.

I am now trying to figure out how to write the clustering IDs to the metadata and having an unrelated problem with that (just getting the writing of the name in meta.data to work within my loop), but I wanted to point out that I think this is why people have had this issue. Clustering data at different resolutions is no longer automatically saved in meta.data.

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

1 participant