-
Notifications
You must be signed in to change notification settings - Fork 65
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
Is it possible to compare immunarch objects with repOverlap? #40
Comments
Hi @diyaazak sorry for the very late response! Can you please explain what do you mean by "immunarch objects"? |
Ping @diyaazak about comparing single-cell repertoires in immunarch |
I'm really sorry I haven't been checking this post for some time..
What I would like to do for examlpe, is use functions like repOverlap to compare VDJ_Cluster_1 to VDJ_Cluster_2, or compare the gene usage between Clusters. Is there a way to do that? Thanks a lot! |
Hi @diyaazak Thank you for getting back to us, our team appreciates that! Currently you need to create a metadata table by hand and put your data in a common
You can wrap it in a simple function to work with any number of clusters. Full single-cell support (seamless stratification to patients and clusters by barcodes, paired chain analysis, etc.) is our next major milestone, so your feedback on your data analysis routines and goals is much appreciated! |
Thanks a lot for the quick feedback!
This is how my data and metadata list looks like:
A tibble: 616 x 20Clones Proportion CDR3.nt CDR3.aa V.name D.name J.name V.end D.start D.end J.start VJ.ins VD.ins DJ.ins Sequence chain … with 606 more rows, and 4 more variables: Barcode , RawClonotypeID , RawConsensusID , ContigID$data[[2]] A tibble: 522 x 20Clones Proportion CDR3.nt CDR3.aa V.name D.name J.name V.end D.start D.end J.start VJ.ins VD.ins DJ.ins Sequence chain … with 512 more rows, and 4 more variables: Barcode , RawClonotypeID , RawConsensusID , ContigID$meta Also, geneUsage doesn't seem to work:
I wonder what I might be doing wrong. |
Hi @diyaazak I see, thank you. I have questions regarding the barcode preparations. Regarding the analysis. Can you please name your clusters:
And try again? |
Hi @diyaazak We made a major improvements to the package, and now you can easily split datasets by clusters and barcodes. Here is more info: https://immunarch.com/articles/web_only/v21_singlecell.html Please let me know if it's what you seek, if it's work or if you have any other questions. Your input is much appreciated! |
Hi @vadimnazarov
Is this the way you would perform it or is there a more straightforward way? I tried running select_clusters as follows but it doesn't seem to work:
Thanks! |
Hi @diyaazak thank you! Can you print Can you also send me the error message after |
Now that I look at it, it could be because the barcodes in the filtered_contig_annotations.csv file have a -1 at the end while the barcodes from a Seurat object lack that. I only started learning R recently so I was just doing this manually in an excel sheet before using I don't get an error when I run
Thanks! |
Hi @diyaazak It definitely can be a case since barcode matching is straightforward and not "smart" to check for "-1" etc. You can easily add "-1" to your barcodes by (note that I don't change the Seurat object here):
Thank you for pointing us to that issue, we will fix it by removing "-1" in the next release for the convenience |
Hi @diyaazak Did it work? |
Hi @vadimnazarov |
Hello, There was no activity on this issue for a while, so we plan to close it in 1 month. You are welcome to comment and reopen the issue if there are still unresolved questions. |
Hello,
Thanks a lot for the great tool.
As the title says, Is it possible to compare immunarch objects with repOverlap?
I created several immunarch objects from a 10x dataset using the "filter_barcode" function based on clusters I got from UMAP clustering of the cells by Seurat.
I can now look at the repertoire diversity per cluster, but I want to check the overlap between clusters too. Is there a way to do this?
Thanks a lot.
The text was updated successfully, but these errors were encountered: