-
Notifications
You must be signed in to change notification settings - Fork 34
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
TCR dist #11
Comments
In GitLab by @szabogtamas on Jan 24, 2020, 20:23 I think we could leave the decision up to the user. One option would be to ignore secondary chains. The other option would be to have four distances between each pair of cells:
The last point I don't really get. They must have a rationale behind capping the score but for me it would be more logical to use alignment scores as they are... I will try to look into the paper again. |
In GitLab by @grst on Jan 30, 2020, 11:03 changed the description |
In GitLab by @szabogtamas on Feb 12, 2020, 13:37 Add clonotype overlap as a distance metric. |
In GitLab by @szabogtamas on Feb 12, 2020, 13:47 [removed] |
In GitLab by @grst on Feb 14, 2020, 16:13 changed the description |
In GitLab by @grst on Feb 14, 2020, 16:19 mentioned in merge request !10 |
In GitLab by @grst on Feb 28, 2020, 09:10 marked the task Add clonotype overlap as a distance metric (simple 0-1) as completed |
In GitLab by @grst on Feb 28, 2020, 12:51 closed via merge request !10 |
Feat/tcrdist Closes #11 See merge request icbi-lab/pipelines/singlecell_tcr!10 Former-commit-id: 200dd159156d880ada06d8a25e190cbcc29219d3
In GitLab by @grst on Jan 24, 2020, 13:50
Getting the alignments was quite straightforward, thanks to parasail.
We said that we focus on CDR3, at least initially.
@szabogtamas, some points to discuss
4
. Does that make sense?Edit:
Prototype works. ToDo for now.
primary_only
orall chains
The text was updated successfully, but these errors were encountered: