Hi Ben,
I was playing around with the new bowtie version, and I noticed that specifying the --best flag resulted in an output that had a different number of mappings than when the flag is omitted. However, in the bowtie documentation, it says that --best does not change which alignments are considered valid. I tried this with multiple sets of reads, and each time the number of alignments differed. Is this a bug or am I misunderstanding the effects of --best? The other flags I was using (in both cases) were -S, -p, --solexa1.3-quals, --al, and --un.
Thanks!
I was playing around with the new bowtie version, and I noticed that specifying the --best flag resulted in an output that had a different number of mappings than when the flag is omitted. However, in the bowtie documentation, it says that --best does not change which alignments are considered valid. I tried this with multiple sets of reads, and each time the number of alignments differed. Is this a bug or am I misunderstanding the effects of --best? The other flags I was using (in both cases) were -S, -p, --solexa1.3-quals, --al, and --un.
Thanks!
. But it is definitely still possible to use Bowtie. My suggestion would be to use, for instance -n 1 -l X -e Y, where -l X is set so that the "seed" falls just short of the string of Ns, and -e Y is set according to the number of Ns + the number of mismatches you would like to allow beyond the Ns. (Your input is fasta, so every mismatch incurs a quality penalty of 30. So for 6 Ns + 1 mismatch, -e 210 is appropriate.) Here is an example where I align a read of the format you describe to the human genome:
Comment