Can subjunc use splice sites from a reference annotation (i.e. GTF file)?
1
0
Entering edit mode
@ryan-c-thompson-5618
Last seen 8 months ago
Scripps Research, La Jolla, CA

Hello,

I am looking to test out subjunc for aligning my RNA-seq data. I have a reference genome and GTF file describing annotated transcripts, with splce sites implied by consecutive exons in the same transcript. If necessary, I could easily generate a tab-separated file just describing all the splice sites in the annotation. Many other spliced aligners can use this information to better align reads to known splice forms. Is there any way for subjunc to use this information? I don't see any option for this in either the command line subjunc program or the "align" function in the Rsubread package.

-Ryan Thompson

Annotation Rsubread • 1.1k views
ADD COMMENT
1
Entering edit mode
Wei Shi ★ 3.6k
@wei-shi-2183
Last seen 11 days ago
Australia/Melbourne/Olivia Newton-John …

Dear Ryan,

I agree that leveraging the knowledge of known splice sites is likely to increase the accuracy of read mapping.

When performing read alignments for RNA-seq data, subjunc firstly identifies high-confidence exon spanning reads and then uses them to compile a list of splice sites. It then uses the discovered splice sites to re-align all the reads to try to achieve the best mapping results. This is the fundamental difference between subjunc and other splice-aware aligners. Our evaluation results have already shown that subjunc was more accurate in identifying splice sites and in mapping exon-spanning reads (Tables 6 and 7 in PMID:23558742).

Allowing users to provide an annotation will complement the list of splice sites we discovered from the data and would possibly further improve the mapping results. It is on our to-do list to investigate this and possibly implement it.

Best wishes,
Wei

ADD COMMENT

Login before adding your answer.

Traffic: 473 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6