Question: rsubread: featureCounts, extending ChIP-seq reads, counting the fragments
0
gravatar for tonja.r
3.9 years ago by
tonja.r460
UK
tonja.r460 wrote:

I have single-end reads from ChIP-seq experiment from some histone marks. With the cross-correlation plots (from correlatedReads from scaw package I identifies the fragments length: app. 180 bp, read length is 50bp). I want to count features falling in a specific genomic location using featureCounts from rsubreads.

featureCounts has such options: readExtension5, readExtension3,minReadOverlap.

More reasonable would be to count the fragments (extended reads) and not the reads themselves. Because it might happen that my genomic regions (which is a bit less than 180 bp) is occupied by lets say H3K4me1, meaning that the reads will be out of the defined region and this region will be reported as empty. On the contrary, if I extend my reads and count the fragments, I will definitely catch the fragments and my region will not be reported as empty. Is it correct?

So, I need to extend my reads. I think, I need to extend them downstream from 3' ( I am not quite sure why would somebody want to extend the reads upstream from 5' because) by app. 130 bp. Is it correct? Does featureCount take into consideration the strand of the read when extending downstream from 3'?

Let me know if I have some flaws in my thinking.

chip-seq R • 1.8k views
ADD COMMENTlink modified 3.9 years ago by Ying W3.9k • written 3.9 years ago by tonja.r460
0
gravatar for Ying W
3.9 years ago by
Ying W3.9k
South San Francisco, CA
Ying W3.9k wrote:

> I want to count features falling in a specific genomic location using featureCounts from rsubreads.

The point of read extension is to infer fragment size which is important when counting (esp for sharp peaks).

> Does featureCount take into consideration the strand of the read when extending downstream from 3'?

Yes

 

ADD COMMENTlink written 3.9 years ago by Ying W3.9k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1208 users visited in the last hour