<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Peak calling on Pierre-François Roux</title>
    <link>https://www.pierre-francois-roux.com/tags/peak-calling/</link>
    <description>Recent content in Peak calling on Pierre-François Roux</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2021 Pierre-François Roux</copyright>
    <lastBuildDate>Fri, 19 Jun 2026 09:20:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.pierre-francois-roux.com/tags/peak-calling/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Use pseudoreplicates to make peak sets less fragile</title>
      <link>https://www.pierre-francois-roux.com/2026/06/19/use-pseudoreplicates-to-make-peak-sets-less-fragile/</link>
      <pubDate>Fri, 19 Jun 2026 09:20:00 +0000</pubDate>
      
      <guid>https://www.pierre-francois-roux.com/2026/06/19/use-pseudoreplicates-to-make-peak-sets-less-fragile/</guid>
      <description>Peak sets are surprisingly fragile. Change one replicate, one depth threshold or one peak-calling parameter, and thousands of regions may appear or disappear.
A useful way to reduce this fragility is to ask whether peaks are reproducible under resampling. This is the logic behind pseudoreplicates and IDR-style workflows.
The Core Idea For each biological replicate:
 Randomly split aligned reads into two pseudoreplicates. Call peaks on the original replicate. Call peaks on each pseudoreplicate.</description>
    </item>
    
  </channel>
</rss>