SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
under the hood of Unified genotyper jfb Bioinformatics 0 02-11-2012 11:37 PM
multireads in BAM file? dglemay RNA Sequencing 3 10-27-2011 10:47 PM
Confidence that Alternative Splicing is NOT happening Germwise Bioinformatics 9 09-07-2011 07:14 AM
RNA-Seq: BM-Map: Bayesian Mapping of Multireads for Next-Generation Sequencing Data. Newsbot! Literature Watch 0 04-27-2011 02:00 AM
TopHat multireads? gthomas RNA Sequencing 0 06-04-2010 09:30 AM

Reply
 
Thread Tools
Old 11-10-2009, 04:11 PM   #1
choy
Member
 
Location: Michigan

Join Date: Jul 2009
Posts: 14
Default TopHat and Multireads - what is happening under the hood?

Hi all -

I have had success so far with TopHat, and it is a great tool!

My RNA-seq workflow is to run TopHat and then Cufflinks. Recently, I noticed that some of the transcripts that are produced are "false positives" due to multi-mapped reads. In otherwords, the vast majority of coverage (RPKM) in those transcripts due to reads that map to multiple locations.

I could eliminate all of these false positives by setting TopHat's (-g/--max-multihits) option to '1', but I would rather not do this because it would sacrifice sensitivity in exchange for guaranteed uniqueness.

Ideally, I want to be able to know some statistics about how many of the reads in each transcript came from multi-mapping vs. uniquely mapping reads. Is there any information in the 'accepted_hits.sam' file about this? What about in any of the other temporary files that TopHat generates.

How does everyone else handle multi-mapping reads and TopHat?

Also, in the SAM output file, I noticed that the mate pair reference is always set to '=' even if the two mates map to different references.

Finally, would it be possible to add the 'insert size' parameter to the accepted_hits.sam file?

Best regards, and thanks again!
choy is offline   Reply With Quote
Old 11-12-2009, 03:55 AM   #2
MerFer
Member
 
Location: Germany

Join Date: Sep 2009
Posts: 21
Default

Quote:
Originally Posted by choy View Post
Hi all -
Also, in the SAM output file, I noticed that the mate pair reference is always set to '=' even if the two mates map to different references.

Finally, would it be possible to add the 'insert size' parameter to the accepted_hits.sam file?

Best regards, and thanks again!
In tophat manual there is already an option for the expected inner distance between mate pairs. I think, it would help you.

-r/--mate-inner-dist <int> This is the expected (mean) inner distance between mate pairs. For, example, for paired end runs with fragments selected at 300bp, where each end is 50bp, you should set -r to be 200. There is no default, and this parameter is required for paired end runs.

Best
Meryem
MerFer is offline   Reply With Quote
Old 11-12-2009, 01:01 PM   #3
choy
Member
 
Location: Michigan

Join Date: Jul 2009
Posts: 14
Default

Quote:
Originally Posted by MerFer View Post
In tophat manual there is already an option for the expected inner distance between mate pairs. I think, it would help you.

-r/--mate-inner-dist <int> This is the expected (mean) inner distance between mate pairs. For, example, for paired end runs with fragments selected at 300bp, where each end is 50bp, you should set -r to be 200. There is no default, and this parameter is required for paired end runs.

Best
Meryem
Thanks Meryem. I am actually setting this parameter already. However, even though we pass the expected inner distance to TopHat, each individual mate pair will have its own insert size when mapped.

I suppose that since TopHat maps to the human genome, it is not possible to approximate the actually insert size until transcript assembly is complete.

Best regards,
choy is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 02:08 AM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO