-
Notifications
You must be signed in to change notification settings - Fork 49
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
TRUST4 config for 10X Genomics #272
Comments
Which version of TRUST4 are you using? If it is v1.1.1, you can run TRUST4 on the BCR-seq portion without "--repseq" option. How many reads in the toassemble_bc.fq file have "missing_barcode" value? This can be useful to check whether the barcode portion is extracted appropriately. Thank you. |
I'm using TRUST4 v1.1.1-r505. |
And should I include UMI information when running trust4 or just ignore that? |
The UMI information affects little with the final results, you can include it. Do you see the same fraction of barcode as "missing_barcode" from the GEX side? If you have some of the cellranger VDJ results, you can also check whether the barcode resides on the first 16bp of R1. |
Hi mourisl, |
Those could be from error-corrected barcodes. |
Hello,
I have 2 10X Genomics datasets (BCR and GEX). What are the appropriate parameters setting for TRUST4?
I'm using
f"run-trust4 -1 {f1} -2 {f2} --barcode {f1} --UMI {f1} --readFormat bc:0:15,um:16:25,r1:26:-1 --barcodeWhitelist {whitelist_barcodes} --od {out_dir} -f {hg38_bcrtcr_path} --ref {human_IMGT_path} -t 24 --repseq" for BCR
and
f"run-trust4 -1 {f1} -2 {f2} --barcode {f1} --UMI {f1} --readFormat bc:0:15,um:16:25,r1:26:-1 --barcodeWhitelist {whitelist_barcodes} --od {out_dir} -f {hg38_bcrtcr_path} --ref {human_IMGT_path} -t 24" for GEX
whitelist_barcodes = cellranger-8.0.0/lib/python/cellranger/barcodes/3M-5pgex-jan-2023.txt
but the results are so little of # VDJs compared to Cellranger. I added the first few lines of {f1} and {f2} and index {f1} here too
Thank you
The text was updated successfully, but these errors were encountered: