mapping PE or SE?
2
1
Entering edit mode
8.9 years ago
R ▴ 10

Hi,

I want to compare two data sets, one of them is SE and the other one is PE.

What's the difference if I map the PE data set and after mapping take mate1 and do further analysis or it is better to take one mate and map it as SE at the beginning ?

PS: I did both and I got equally the same amount of mapped reads.

I would really appreciate your suggestions.

Best regards,

ChIP-Seq • 2.2k views
ADD COMMENT
1
Entering edit mode
8.9 years ago

The batch effect will be minimized (likely not eliminated, since there may be other subtle confounders!) if you use only read #1 of the PE dataset. Whether that actually makes any real difference will depend on the details of your dataset.

ADD COMMENT
0
Entering edit mode

Thanks! I already mapped as PE. Do you think is better to map it again as SE or taking one mate from PE-mapped file is also fine?

ADD REPLY
0
Entering edit mode

Remap it as SE.

ADD REPLY
0
Entering edit mode
8.9 years ago
Fidel ★ 2.0k

Most of the differences that you would see between SE and PE mapping are related to repetitive regions (assuming that both data sets have the same read length). PE reads can map inside of repetitive regions given that the other pair is in a unique region. Also, because PE has more information it can map sometimes inside repetitive elements.

Thus, if you want to make a fair comparison between SE and PE you should map one of the PE read mates from the start as Devon suggested.

However, if you plan to compare coverage of reads, you can simply extend the SE reads to match the expected fragment length and extend the PE reads to the fragment length. Also you should use a random mapping strategy for repetitive regions. You may have some small bias around repetitive regions but unless you are looking for something specific to repetitive regions you wont have to worry.

ADD COMMENT

Login before adding your answer.

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