Question: CLIP-Seq read density
gravatar for Anil Kesarwani
2.8 years ago by
United States
Anil Kesarwani80 wrote:

Dear Bioinfo Geeks,

I have obtained CLIP-Seq read coverage, which is mostly sequestered in 3’ UTR with relatively much lesser density in the CDS and 5’ UTR (Example). This scenario is true for almost all genes I looked. I am struggling to find a way to represent this pattern for all genes in one figure, which can explain that compared to 3’ UTR, the read density in other regions is lower. Given every gene has different count and lengths of 5' and 3'UTR and CDS, its difficult to adjust all to the same scale. I found some papers, where they used binned density, but I am not able to understand the basic steps to do so. Could some body please help.

rna-seq • 899 views
ADD COMMENTlink modified 2.8 years ago by genomax63k • written 2.8 years ago by Anil Kesarwani80
gravatar for Martombo
2.8 years ago by
Seville, ES
Martombo2.4k wrote:

check RSeQC out, especially and The former can count the density of reads in the different genetic regions, while the latter can produce a stacked coverage picture. For that you'll need to create a custom bed file, around the stop codon of the genes.

ADD COMMENTlink written 2.8 years ago by Martombo2.4k

Thanks for your suggestion. In the RSeqQC, I dont find any option for normalizing the read count for the specific region by gene expression (FPKM already calculated). I have conducted CLIP-Seq and the RNA-Seq (for normalization) for the sample in 3 replicates.

Using an approach similar to RSeqQC, I binned each gene feature (5' UTR, CDS, 3'UTR) in to 100 windows (quantiles). But the extraction of read count from BAM file using samtools is not fast enough, as for each case its 100 (bin) X 3 (repl) times. Could you please suggest me if the read count calculation for each bin can be made faster, may be considering the file format other than BAM.

ADD REPLYlink modified 2.8 years ago • written 2.8 years ago by Anil Kesarwani80
Please log in to add an answer.


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