-
Notifications
You must be signed in to change notification settings - Fork 0
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
TIDDIT in single-cell DNA-seq #14
Comments
Hello! Nice to see that you found the translocation, I see that the coverage is rather deep "COVB=39.7400016784668;", and the breakpoint is well supported by 13 fragments "LFA=13;LFB=13;LTE=13"; there are no split reads, maybe the breakpoint is a bit repetitive, or are the reads shorter than 151 bp? By default, TIDDIT is tuned for high sensitivity; if you want higher precision, you may set the minimum number of pairs to a higher value (I usually use 6). Otherwise, I recomend you to use the default settings. I use IGV to interpret the translocation breakpoint; there I look if the breakpoint is clean (i.e if the discordant pairs map to only one unique region, or are spread across the genome), if there are any split reads, and if there are small CNV events at the breakpoints. Feel free to post a picture if you want any advice =P. output.sample.bam(3.5GB) and output.signals.tab are temporary files, I would delete those. output.signals.tab might be interesting, it contains the raw, unclustered signals (split reads and fragments). Good luck! |
Hi again!
As you can see, the bam is AGTAACGTAGTATTACTG and the colname in the vcf is AACAACCTAGTGATGTGC. Any thoughts? Thank you in advance!!! |
Hi! I would appreciate any help on this issue... Best regards! |
Hi @J35P312
I am trying to identify SV (translocations mainly) in patients with know translocations. I am setting up the pipeline with a patient with t(14:18) and I have a single-cell bam file (2000 cells) which I split by read-groups (cell ident), getting 2000 individual bam files.
I took one individual bam (corresponding to an individual cell seq) to test your tool and even though I got the expected results derived for the low coverage and probably other calculations of your algorithm, I have been able to detect the translocation!!
I was thinking in to use your tool to loop across all the 2000 bams, merge them, and extra info from it, at least, to know which cells carry each translocation (mainly the t(14:18) ).
Also, How can I interpret the translocation breakpoints and the ALT, because probably is not getting the mate break pair in the chr18.
What do you think about these results and the best way to tune your tool to squeeze my data in optimal conditions.
In addition, I got more output files than the described in your user guide; output.ploidy.tab, output.sample.bam(3.5GB), output.signals.tab, output.vcf, and output.wig
Thank you so much!!!
The text was updated successfully, but these errors were encountered: