Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Usability of Strand-specific RNA-seq Data #18

Closed
DarioS opened this issue Jun 1, 2018 · 3 comments
Closed

Usability of Strand-specific RNA-seq Data #18

DarioS opened this issue Jun 1, 2018 · 3 comments

Comments

@DarioS
Copy link

DarioS commented Jun 1, 2018

According to the journal article, the method works for strand-specific reads. However, none of the options specified by the user to the software are for specifying the strand-specific type of sequencing done. For example, StringTie has options --fr and --rf. Can Strawberry correctly assemble transcripts if they have overlapping genomic coordinates but are on opposite strands?

@ruolin
Copy link
Owner

ruolin commented Jun 1, 2018

Hi @DarioS, thanks for reporting. I will fix this during the weekend. Currently, I don't have a proper test case. Do you have a strand-specific bam file that you can share with me? Yes. Strawberry can assemble transcripts on opposite strands. If you can give me the url or send me to rliu0606@gmail.com

@DarioS
Copy link
Author

DarioS commented Jun 2, 2018

You might like to use a publicly available BAM file from ENCODE Project, for instance. You could check genes which are on opposite strands and have largely overlapping 3' UTRs to make sure they are not being assembled into one transcript.

@ruolin
Copy link
Owner

ruolin commented Jun 5, 2018

Hi @DarioS thank you for the bam file. I have implemented the Strand-specific options and test against the bam file that you provided. Strawberry is able to assemble overlapping transcripts. Please see https://github.com/ruolin/strawberry/releases/tag/0.9.2

@DarioS DarioS closed this as completed Jun 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants