Difference Between "Mate Pair" And "Pair-End"
3
8
Entering edit mode
10.7 years ago
weiqiangduan ▴ 130

Just as the title , I can't tell the difference between those two conception. :) waiting for your help.

paired-end ngs library • 40k views
ADD COMMENT
7
Entering edit mode

Did you try google? The first hit for "mate-pair vs paired-end" explains it: http://seqanswers.com/forums/showthread.php?t=15626

ADD REPLY
5
Entering edit mode
10.7 years ago

In terms of the resulting sequenced data, they are pretty much the same thing. Although you might be able to argue that the quality of pairing might differ.

They differ in library preparation. In pair-end sequencing, the machine is sequencing the ends of a fragment. So if you have a 500bp fragment, you machine will sequence 1-75 and 425-500 of the fragment. In mate-pair libraries, you are creating a library of fragment ends and then performing normal sequencing on these end fragments,

ADD COMMENT
5
Entering edit mode
10.7 years ago

Refer to Figures 6B and 6C on page 5 of this PDF: Illumina Genomic Sequencing Datasheet

ADD COMMENT
0
Entering edit mode

THANKS A LOT MALACHI

ADD REPLY
0
Entering edit mode

thanks, it helps a lot

ADD REPLY
4
Entering edit mode
10.7 years ago

"Paired end" is pretty straight forward, you make fragments, you sequence both ends, and you have some knowledge of the distribution of fragment sizes in your library, so that helps you properly map.

One might want to make a library of 2 kb long fragments, so that you could get paired end data where each end is expected to be about that far from the other end, but there are practical reasons why you can't. Mate pair preps are designed to get around this. It's a more involved process that involves doing a lot of stuff so that in the end, you have 500 bp fragments, but the sequence at each end originated from regions of the reference that are much farther apart.

ADD COMMENT

Login before adding your answer.

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