Bowtie2 alignment rate for 5hmC IP
1
0
Entering edit mode
8.3 years ago

Hi, I was trying to map the sequence generated after immunoprecipitation of 5hmC using bowtie. for input DNA (genomic DNA without IP) , I had relatively high alignment rate:

6835542 reads; of these:
  6835542 (100.00%) were unpaired; of these:
    294415 (4.31%) aligned 0 times
    5329518 (77.97%) aligned exactly 1 time
    1211609 (17.73%) aligned >1 times

while for the samples after IP, the mapping seems to be low:

6622988 reads; of these:
  6622988 (100.00%) were unpaired; of these:
    1734630 (26.19%) aligned 0 times
    2223155 (33.57%) aligned exactly 1 time
    2665203 (40.24%) aligned >1 times
73.81% overall alignment rate

another sample has almost more or less the same mapping rate. Is this result is acceptable or kind of alarming? Comments or suggestions appreciated.

ChIP-Seq next-gen alignment sequencing • 2.1k views
ADD COMMENT
1
Entering edit mode
8.3 years ago
igor 13k

It's a bit low. The 5hmC antibody is more likely to bind to repetitive regions, so you are getting more multi-mapping reads due to that. If you look at the unique and multi-mapping reads, the alignment rate is not so bad.

I recently looked at a few public MeDIP datasets and the unique alignment rates ranged from 40% to 75%, so it can be variable.

If you can still call peaks, it may still be a useable experiment.

ADD COMMENT
0
Entering edit mode

@igor. Hi, igor. Thank you for your kind comments and suggestions. Yes, I can still call peaks, see the attached image. 1st track: input; 2nd+3rd track: IPed samples I was wondering whether you have any idea about a related issue. Since there is about a quarter of the reads could not be aligned (align 0 times), suggesting that they are not of mouse origin,but contaminant (?). I wondered where they came from. I tried to map the sample after IP against human, E.coli, phage indexes (the most common species we are dealing with), but there were no significant proportion of reads mapped to those species. alignment result against human index:

6622988 reads; of these:
  6622988 (100.00%) were unpaired; of these:
    6347855 (95.85%) aligned 0 times
    31025 (0.47%) aligned exactly 1 time
    244108 (3.69%) aligned >1 times

alignment result against E. coli:

6622988 reads; of these:
  6622988 (100.00%) were unpaired; of these:
    6622910 (100.00%) aligned 0 times
    47 (0.00%) aligned exactly 1 time
    31 (0.00%) aligned >1 times
0.00% overall alignment rate

Alignment against phage:

  6622988 (100.00%) were unpaired; of these:
    6622789 (100.00%) aligned 0 times
    199 (0.00%) aligned exactly 1 time
    0 (0.00%) aligned >1 times
0.00% overall alignment rate

Do you have any idea about that? Tsk!

ADD REPLY
0
Entering edit mode

Hard to say what they are. My first guess would be adapter dimers. Try BLASTing a few of the sequences. If there is an obvious contaminant and it's a quarter of the reads, you should find it fairly quickly.

ADD REPLY
0
Entering edit mode

@igor. I collected the unmapped reads using bowtie2 option " --u",

--un ./Sample_unmapped.fq --al ./Sample_mapped.fq >

and blasted some of them:

AlignmentsDownloadGenBankGraphicsDistance tree of resultsShow/hide columns of the table presenting sequences producing significant alignments Sequences producing significant alignments: Select for downloading or viewing reports Description Max score Total score Query cover E value Ident Accession Select seq gb|AC157543.8| Mus musculus chromosome 1, clone RP23-271O17, complete sequence 283 283 76% 9e-73 97% AC157543.8 Select seq gb|AC115853.8| Mus musculus chromosome 5, clone RP24-273B9, complete sequence 110 110 31% 2e-20 96% AC115853.8

Select seq gb|AC184151.2| Mus musculus BAC clone RP24-91H6 from chromosome y, complete sequence 169 169 65% 2e-38 99% AC184151.2 ...

Basically, it seems that the all the "unmapped" reads produced significant alignments against mouse, even though with modest "Query coverage".

ADD REPLY

Login before adding your answer.

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