--
You received this message because you are subscribed to the Google Groups "trinityrnaseq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trinityrnaseq-u...@googlegroups.com.
To post to this group, send email to trinityrn...@googlegroups.com.
Visit this group at http://groups.google.com/group/trinityrnaseq-users.
For more options, visit https://groups.google.com/d/optout.
Ultimate stresses sportsmanship and fair play. Competitive play is encouraged, but NEVER AT THE EXPENSE OF RESPECT BETWEEN PLAYERS, adherence to the rules and the BASIC JOY OF PLAY.
Hi Tiago,Thanks for the reply. My library is a normal non-stranded library, so I suppose mapping Trinity transcripts back to the genome will not tell me anything about the quality of the Trinity transcriptome. I came across a paper in which the authors does this to access their transcriptome assembly and I was just not sure if this is something i should try.Detonate: both RSEM-EVAL and REF-EVAL should be tested?
Hi Karen,
The first thing I see is that the filenames are .txt but you say they are .fq. Could this be causing the issue? Also you can add --SS_lib_type parameter to make it clear its strand-specific. Maybe this would fix it?
Thanks, Mark
Hi Karen,
Sorry I misread about stranded/unstranded. Maybe try renaming the files to .fq to see is anything changes. Is samtools in your PATH? Maybe Brian would suggest upgrading to ver. 2.0.6 too? These are just some ideas :)
Thanks, Mark
Hi Karen,
Were your sequence files .txt files when you received them? If not then is it possible they have been saved as .txt files more recently and hence the line breaks could have been changed? (Just another idea!)
--Mark