This is a test version of Biostars. For the public version, visit https://www.biostars.org.
Strange pattern of uneven read count distribution

Hi Biostars,

I have multiple murine whole genome sequencing samples which show a non-uniform readcount distribution along the genome, all following the same pattern, example attached. Has anyone be facing this pattern in readcount distribution before and may have an idea what could be causative? (i dont see patterns in standard QC parameters)

Thanks for any input on this! enter image description here

Update on GC bias:

GC content was proposed as a reason, so I plotted mean GC in reference genome along with the readcount distribution. There is no clear correlation, maybe a mild high GC - low coverage, but it’s very subtle. Thus, I guess GC bias is not the (major) cause of the fluctuating coverage. Does anyone have a different idea?

enter image description here

wgs fluctuating coverage

2 answers

Sequencing coverage by short reads depends on GC content (https://pubmed.ncbi.nlm.nih.gov/22323520/). Maybe, this coverage distribution reflects distribution of GC content along chromosomes?

Also, if you removed reads with low mapping quality, this may have reduced coverage in repetitive regions.

I had a quick look at overall GC content, which looked ok on a first look, but I'll dive deeper into GC, thanks for the hint!

Megabase/arm-level GC biases do exist. Whilst some tools perform post-segmentation CN smoothing to handle exact this sort of gradual change in CN without any explanatory SV, for the most part, CN biases on this scale remain largely uninvestigated.

GC normalisation is only for small-scale (~1kbp) differences in GC content. GC bias does not explain arm-level copy number biases. That fact you're seeing higher coverage toward all centromeres can't be explained by GC. The abrupt changes (e.g. chr12/chr13) can be explained by genomic rearrangements, but the gradual arm-level changes (e.g chr2) looks more like a sequence artifacts than real biology.

This agrees with my current picture of the problem. Thank you for your opinion!

Log in to answer this question.