PAR-clip T to C mutations becoming T to G in minus strand?
1
0
Entering edit mode
9.5 years ago
t.candelli ▴ 70

I am looking at some PAR-clip data. trimming and mapping went perfectly, however, when I look at the data on IGV, in the plus strand I have a vast majority of T to C mutations (as expected), but in the minus strand I see a lot of T to G mutations, like a vast predominance.

is there any way to explain this? how is it possible that only the minus mapping reads are affected? there must be a technical issue somewhere!

IGV PAR-clip Mapping Transversion • 2.3k views
ADD COMMENT
0
Entering edit mode
9.5 years ago

Weird things do happen all the time. Since all alignments are (should be) represented on the forward strand the mutation should be shown relative to that strand as well, here it just happens to look like complement but it is most likely caused by more subtle errors.

there are papers on this subject, search for strand bias in snp calling

The effect of strand bias in Illumina short-read sequencing data BMC Genomics 2012, 13:666

(whoops I may have jumped ahead of myself, I don't know what PAR-Clip is, I assume it still applies ;-) )

ADD COMMENT
0
Entering edit mode

yeah I thought a long while about this and realized that in SAM files the sequence is always given on the forward strand, irrespective of whether it maps to the reverse. this flipping makes it so the T->C in the reverse become A->G in the forward.

i am relatively convinced by this but I would like confirmation. I really thought IGV would be smart and report the correct mismatch depending on which strand the read maps to, but it seems it's not the case, unless I misunderstood something.

ADD REPLY
0
Entering edit mode

IGV is a visualizer and it shows alignments as they are produced.

Showing a different mismatch depending on the strand would be actually counterproductive as the DNA is complementary so there is nothing to be gained from showing one event as being two different ones - it would only add to the information overload.

ADD REPLY

Login before adding your answer.

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