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

SE events in output table do not match to the GTF annotation #401

Closed
CyberGypsy6324 opened this issue May 8, 2024 · 5 comments
Closed

Comments

@CyberGypsy6324
Copy link

CyberGypsy6324 commented May 8, 2024

Hi rMATS team,

I have a question about the output table of skipped exon. From my understanding, "Upstream-Skipped-Downstream" is the known event in the GTF annotation file and "Upstream-Downstream" is the novel event detected by rMATS from RNA-Seq data.

Untitled

However, I find an event in the output table of skipped exon which looks weird:

GeneID	geneSymbol	chr	strand	exonStart_0base	exonEnd	upstreamES	upstreamEE	downstreamES	downstreamEE
ENSG00000102181.21	CD99L2	chrX	-	150828305	150829604	150816278	150816455	150831230	150831293

The positon of exons is shown in the IGV:

Screen Shot 2024-05-08 at 2 56 07 PM

In this detected event, the connecting of "Upstream-Skipped-Downstream" cannot be found in the GTF annotation. This makes me confused. I wonder my understanding above is not correct. Can you help me about this question? Thank you.

@EricKutschera
Copy link
Contributor

rMATS can detect events where some of the exons or junctions are not annotated. The inclusion isoform (up-skip-down) and/or the skipping isoform (up-down) could have novel exons or junctions. These posts have some details:
#277 (comment)
#17 (comment)

@CyberGypsy6324
Copy link
Author

Hi Eric,

Thank you for sharing some previous answers. I'm still not quite clear about my question after reading them. I didn't enable --novelSS when running rMATS. The exon skipping event I mentioned above is from the output file SE.MATS.JCEC.txt. I expected all inclusion isoforms (up-skip-down) should exist in the GTF annotation file. However, the 3 exons involved in that event only have the isoforms 1) up-down 2) skip-down while the isoform up-skip-down doesn't exist according to the annotation.

Screen Shot 2024-05-10 at 11 26 42 AM

@EricKutschera
Copy link
Contributor

It looks like all 3 exons are annotated in the GTF. rMATS can detect events with novel combinations of annotated splice sites even without --novelSS

https://github.com/Xinglab/rmats-turbo/tree/v4.3.0?tab=readme-ov-file#output

fromGTF.novelJunction.[AS_Event].txt: AS events derived from novel combinations of splice sites annotated in the GTF file. Does not include events with an unannotated splice site

@CyberGypsy6324
Copy link
Author

CyberGypsy6324 commented May 13, 2024

Hi Eric

Thank you for your explanation. Now I see why there are novel connections.

And I'm interested in the changes in protein sequence caused by the alternative splicing. For exon skipping, my original plan to extract novel protein sequences is:

  1. Using the upstream, skipped, and downstream exons to identify the affected transcripts.
  2. Edit the transcript sequences according to the skipping events.
  3. Extract the novel protein sequences from edited transcript sequences.
Screen Shot 2024-05-13 at 12 28 21 PM

Do you think this workflow is correct? Also like the case I mentioned above, when upstream, skipped, and downstream exons cannot even identify one transcript (which means the connection up-skip-down doesn't exist in the GTF annotation file), how should I know what effect SE has on the protein sequence?

@EricKutschera
Copy link
Contributor

Splicing events reported by rMATS are based on reads covering individual junctions and exons. You can compare the rMATS events to annotated transcripts, but the events may not match nicely to transcripts. You could try limiting your analysis to cases where there is an annotated transcript that has all 3 exons in order

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