protein position to nucleotide position
2
0
Entering edit mode
9.4 years ago
MAK ▴ 10

I have translated a complete genome in the six frames then I got a start and stop position for a gene on this translated genome.

Now I need to compare these coordinates to nucleotide positions:

if I am in same positive strand what I thought of is:

if frame 1: nuc_start=prot_start*3

if frame 2: nuc_start=prot_start*3+1

if frame 3 nuc_start =prot_start*3+2

Question: Am I right? And what about the other strand frames?

genome protein translation DNA • 3.8k views
ADD COMMENT
4
Entering edit mode
9.4 years ago

Assuming you want 1-based coordinates, then you would instead want:

frame 1: nuc_start = 3*(prot_start-1)+1
frame 2: nuc_start = 3*(prot_start-1)+2
frame 3: nuc_start = 3*(prot_start-1)+3

This assumes that you simply ignore the first 2 bases when translating frame 3, rather than padding the translated sequence with something.

It works the same for the other strands, how you do the math will depend on whether you reversed the sequence or not. If you reversed things, then the resulting coordinates will be from the end of the chromosome/contig. Also, frame -1 will be dealt with the same as frame +3 and -3 the same as +1.

If this is unclear, draw out a short sequence, how this works should be apparent then.

Edit: And as Pierre pointed out, this all assumes that there's no splicing...

ADD COMMENT
0
Entering edit mode

Yes I translated the reverse complement for the other strand frames, I couldn't figure out how the frame -3 is dealt same as +1 and vice versa

ADD REPLY
1
Entering edit mode

The "also" was incorrect in that sentence. Just calculate the position as if you were on the + strand and the subtract that from one more then the chromosome/contig length.

ADD REPLY
0
Entering edit mode
ADD COMMENT
0
Entering edit mode

I assume there is no splicing

ADD REPLY

Login before adding your answer.

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