Question: What Happened To -K In Tophat For Multiple-Mapping Reads?
1
gravatar for gaelgarcia05
6.5 years ago by
gaelgarcia05190
UK
gaelgarcia05190 wrote:

Selecting -g n in tophat does not discard reads mapping more than n, but instead only reports n alignments for those out all all their TOP scoring alignments.

I think there used to be an option -k that would allow one to discard reads that topped x alignments -- whatever happened to that? I only see -g in the tophat 2 manual, no reporting options like before...

ADD COMMENTlink modified 5.6 years ago by Dan D6.9k • written 6.5 years ago by gaelgarcia05190
1
gravatar for Dan D
5.6 years ago by
Dan D6.9k
Tennessee
Dan D6.9k wrote:

You're correct that it appears to be gone, as it's now an unrecognized option on the command line. If I had to hazard a guess, I would speculate that it's because it's tricky to know what to do with the discarded reads. They're certainly not "unmapped," but then do you make another BAM for the "abundant" reads? Either that or there was a change to the algorithm where concurrency considerations made it difficult to track the total number of alignments for a given read until later on in the process, where any efficiency gains would be wiped out.

Fortunately, you can easily remove these reads downstream of tophat using BAMTools filter. For example, if you wanted to remove any read which mapped 20 or more times, you could supply the following JSON to the tool:

{
   "tag" : "NH:<20"
}
ADD COMMENTlink modified 5.6 years ago • written 5.6 years ago by Dan D6.9k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1740 users visited in the last hour