-
Notifications
You must be signed in to change notification settings - Fork 50
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
umis and clonotype of trust-barcoderep-to-10X.pl results #282
Comments
When using UMI, the abundance information is transformed UMI count. I think the read count information is stored, so they are the same in the output. I think the clonotype_id in 10X's definition is not very clear. I think I saw some cases where the CDR3, V,J, C genes were the same but still had a different "Clonotype" ID. Therefore, I leave those as None. Is your downstream analysis workflow depend on this? |
Thanks a lot. |
I think you can use the CDR3 sequence to define the clonotype. |
I will have a try. And, thank you for all your quick replies. |
I used the trust-barcoderep-to-10X.pl to transform barcode_report, and got two questions:
The command I ran run the software is as follows:
run-trust4
-f hg38_bcrtcr.fa
--ref human_IMGT+C.fa
-t 15
-u R2_001.fastq.gz
--barcode R1_001.fastq.gz
--UMI R1_001.fastq.gz
--readFormat bc:0:16,um:17:28,r1:29:-1
--barcodeWhitelist P3CB.barcode.txt.gz
The text was updated successfully, but these errors were encountered: