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

How to properly select metrics&cutoffparameter #586

Open
MaybeTommorow opened this issue Jan 23, 2025 · 1 comment
Open

How to properly select metrics&cutoffparameter #586

MaybeTommorow opened this issue Jan 23, 2025 · 1 comment

Comments

@MaybeTommorow
Copy link

Hi,

Thanks for developing scirpy, it's a powerful tool for analyzing TCR data.
I have a question regarding the selection of the metrics parameter when using scirpy.pp.ir_dist, scirpy.tl.ir_query, scirpy.tl.ir_query_annotate.

Assuming we are analyzing T cells and pooling TCR clones based on the amino acids (i.e., sequence = 'aa').
I noticed in your tutorial that tcrdist is used to compute CDR3 neighborhood graph, with a cutoff of 15 allowing 3 Rs mutating into N. However, while matching cells with VDJdb, identity is used.
Can I interpret this as a recommendation to use identity when matching data with public data, and tcrdist is preferable for computing similarity among a large pool of cells from the same specific condition?

Additionally, the default cutoff is 10 when using alignment, but in your tutorial, 15 is set when using tcrdist. Is this also a recommended value?

Thank you for your guidance.

@grst
Copy link
Collaborator

grst commented Jan 28, 2025

Hi,

unfortunately, there is no straightforward answer. I am not aware of any benchmark that shows that at a given cutoff, receptors still have a X% chance of binding to the same epitope. So in the end it's just a gradient from "very stringent" (identity) to less stringent (alignment/tcrdist with increasing cutoffs).

This applies to both the definition of clonotype clusters and database search.

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

2 participants