Open ilevantis opened 9 years ago
Are these weird RNASeq reads correctly or incorrectly mapped?
I don't have the actual RNASeq data to hand so I can't say for sure. I'm guessing that it might be due to 2 regions of very similar sequence being close together.
For example, a read that came from gene1 exon2-3, ends up mapped as spanning from gene1 exon2 to gene2 exon3 because gene1 exon3 and gene2 exon3 are very similar.
Have a look at the region Si_gnH.scaffold00008:424866..433120 for an example.
Would be incredibly helpful (especially with RNASeq / RNASeq Coverage) to hide all features in any(all) tracks that lie outside a specified window.