![]() |
TopHat BowTie -n mode
Someone must have already asked this question before but I couldn't find any straight answer so posting it again (sorry for the redundancy).
If I want to run TopHat on longer reads (say >75 bps from Illumina) I'll definitely need to allow more mismatches in the alignment. I can adjust it using "--initial-read-mismatches" and "--segment-mismatches" option. Is there any upper limit on the number of mismatches that TopHat can accept? If I want TopHat to run BowTie in -n mode, how do I change seed mismatches (-n), seed length (-l) and -e values? |
--initial-read-mismatches and --segment-mismatches are the two values passed to "bowtie -n" or "bowtie -v" at different Bowtie searches in the TopHat pipeline. I'm not sure you can control the -l or -e Bowtie values from the TopHat command line and so you'll probably have to edit the tophat python code to do it.
Chris |
All times are GMT -8. The time now is 10:45 AM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2022, vBulletin Solutions, Inc.