I have some questions about read orientation in Tophat that I cannot find the clear answers yet and I hope you can shed some light on these.
1 What are the orientation of reads for pair-end data for library fr-unstranded,fr-firststranded, or fr-secondstranded? I'm not sure whether these strand specific parameter related with pair orientation (ff, fr, rf in Bowtie). In Bowtie, this parameter (ff, fr, rf) need to be specified and Tophat use Bowtie for alignment. However, I cannot find the way to set this parameter in Tophat.
2 According to description about library type, "Reads from the left-most end of the fragment (in transcript coordinates) map to the transcript strand, and the right-most end maps to the opposite strand." does left-most end of fragment in transcript coordinates correspond to the read in first first file in paired-end data?
3 Some of public data that I collected do not have information about library type except only platform (standard illumine or strand specific Illumina), can I assume that they are fr-unstranded and fr-secondstrand respectively?
Thank you Ido for answers. By the way, does the fr in [fr-unstranded,fr-firststranded, fr-secondstranded] correspond to forward-reverse? I wonder whether paired end read orientation can be set for Tophat.
Thanks is expressed by upvoting. I never had to set read orientation for tophat. For me it worked with the default.
"I never had to set read orientation for tophat. For me it worked with the default". Is this true ? If you have fr-secondstrand type of data and you run top hat by using default (you do not specify any library type on the command), does it work right ?
I meant the paired end read orientation like ff vs fr. My data is always fr where the data of the reads are always sequenced from the fragment ends like -> <-. I think this was not in my answer when Chai_AF asked and I updated it afterwards.
Ido, what do you mean by "you come in from the right (3' end of the mRNA) " ? and viceversa?
Does anyone know yet if this info is actually used for mapping specificity or if it's just passed on to the XSA tag?