Nonsense mutation and translation
1
0
Entering edit mode
2.6 years ago
vpsev3 ▴ 20

Does a nonsense mutation at the end of an exon prevent future exons of the gene from being translated into protein?

mutation • 930 views
ADD COMMENT
0
Entering edit mode
2.6 years ago
Mensur Dlakic ★ 27k

Any nonsense mutation stops the translation. However, you don't necessarily know the correct translation frame from a single exon, so it may not mean anything.

ADD COMMENT
0
Entering edit mode

So if there is no other start codon in other exons, the translation stops and the other exons will not be translated into protein?

ADD REPLY
1
Entering edit mode

You are asking me to make a definitive statement without providing much information. The answer is that I don't know. That is because I don't know whether your exon is first, last, or in the middle. Also because it is almost impossible for any exon of decent size not to have a start codon. Or maybe you don't have the first exon. There are all kinds of answers to your question and you will most likely have to figure it out on your own after some investigation.

ADD REPLY
0
Entering edit mode

I see, the exon is in the middle

Is there a tool to check by entering the gene sequence?

ADD REPLY
0
Entering edit mode

You can always try to concatenate all the exons in order, and predict the ORF from that combined sequence. Chances are very high that a nonsense codon at the end of a middle exon (or really anywhere in the middle exon) is nothing to worry about.

I think you need to reconsider how you ask the questions. If you provided all the information in the beginning, it could have been answered with a single post. Instead, you are asking single-sentence questions, and we are going back and forth. And if some of my comments have provided clarity on your question, it is customary to upvote and/or accept the answer(s).

ADD REPLY

Login before adding your answer.

Traffic: 1905 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