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

Tophat with --no-coverage-search #8

Closed
stsergbg opened this issue Apr 9, 2020 · 4 comments
Closed

Tophat with --no-coverage-search #8

stsergbg opened this issue Apr 9, 2020 · 4 comments

Comments

@stsergbg
Copy link

stsergbg commented Apr 9, 2020

Hi!

When running VIcaller on one stage tophat suggests running itself in --no-coverage-search mode to make the process much faster. The run indeed completes much faster when this option is added to VIcaller.pl, so I wanted to ask if you tested this option before. Does this option (or can it, in principle), in your opinion, prevent VIcaller from finding/validating some viral integrations?

Sergei

@xunchen85
Copy link
Owner

Thanks for your question.

I haven't tried it yet! But in principle, it won't matter regarding finding or validating viral integrations. If it really speeds it up, I may also update to use --no-coverage-search mode in our tool.

Xun

@stsergbg
Copy link
Author

Yes, for a couple of samples I've tested there is a significant improvement in speed. I also wanted to ask if tophat is crucial or other aligners might be just as good for the first alignment, e.g. STAR? As I've understood from the code tophat is run on default parameters and the main workhorse in the tool is bwa.

By the way, when there is bam provided to the tool instead of fastq, as I got it, it is then converted to fastq only to be aligned afterwards with tophat again. Can this step be skipped altogether if I have a STAR-aligned bam file (to the same human reference) right from the start?

@xunchen85
Copy link
Owner

Tophat is only used for detect viral fusion transcript from RNA-seq data.

You are correct, if the aligner can generate the BAM file with CIGAR column, VIcaller should be able to take the output BAM file as the input.

If the input is BAM file, it will convert the discordant reads into FASTQ and then re-align those reads using BWA. Tophat is only used for aligning FASTQ against human reference if the input is FASTQ format. In another word, if you provided a STAR-aligned BAM file, VIcaller should not re-run Tophat against the human reference.

Let me know if you found issues with it.

Best,

@stsergbg
Copy link
Author

Thank you for the explanation! I've misunderstood the procedure with bam files as input, and now I tried running the tool on the already computed STAR bams - it works like a charm.

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