<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Read Length on Gigabase or gigabyte</title><link>https://wdecoster.github.io/gigabaseorgigabyte/tags/read-length/</link><description>Recent content in Read Length on Gigabase or gigabyte</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><copyright>© Wouter De Coster</copyright><lastBuildDate>Sat, 31 Oct 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://wdecoster.github.io/gigabaseorgigabyte/tags/read-length/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical length revisited: how long should ONT reads be for structural variant discovery?</title><link>https://wdecoster.github.io/gigabaseorgigabyte/posts/2026-10-31-critical-length-revisited/</link><pubDate>Sat, 31 Oct 2026 09:00:00 +0100</pubDate><author>Wouter De Coster</author><guid>https://wdecoster.github.io/gigabaseorgigabyte/posts/2026-10-31-critical-length-revisited/</guid><description>&amp;lt;no value&amp;gt;</description><content type="text/html" mode="escaped"><![CDATA[<p>In 2020 we published <a href="https://doi.org/10.1093/nargab/lqz027"><em>Critical length in long-read resequencing</em></a>, in which we simulated reads of a fixed length from human genome assemblies and concluded that reads of about 20 kb are sufficient for structural variant (SV) discovery. Six years later, both the data and the tools have changed, so I revisited the question.</p>
<p><strong>The short answer:</strong> the 2020 ballpark holds, but now as a library N50 rather than a fixed read length. For SV discovery from ONT R10 reads, a library with a read N50 of 20–30 kb gets you within a few F1 points of what much longer reads give. The variants that keep benefiting from longer reads are insertions of more than 1 kb and SVs in long, near-identical segmental duplications, where an ultra-long library still helps. Going from 15x to 30x gains about as much as going from a 20 kb to a 100 kb N50.</p>
<h2 id="what-is-different-from-2020">What is different from 2020<a href="#what-is-different-from-2020" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h2>
<table>
	<thead>
			<tr>
					<th></th>
					<th>2020</th>
					<th>Now</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Reads</td>
					<td>Simulated (SimLoRD, a PacBio error model in which short fragments are read in several passes and are therefore more accurate)</td>
					<td>Real ONT R10.4.1 reads, cut to length</td>
			</tr>
			<tr>
					<td>Read lengths</td>
					<td>One fixed length per dataset</td>
					<td>Fixed lengths, and the read length distribution of real libraries rescaled to a range of N50 values</td>
			</tr>
			<tr>
					<td>Genome and truth set</td>
					<td>HG00733 (and CHM13 draft, NA12878): SVs called from its own assembly</td>
					<td>HG002, with the GIAB v5.0q SV benchmark built from the near-complete HG002 Q100 assembly</td>
			</tr>
			<tr>
					<td>Software</td>
					<td>minimap2 2.14, Sniffles 1.0.10, SURVIVOR matching (same type, breakpoints within 500 bp)</td>
					<td>minimap2 2.31, Sniffles2 2.8.1, truvari 5.5.0</td>
			</tr>
			<tr>
					<td>Evaluation</td>
					<td>Genome-wide, unstratified</td>
					<td>Stratified by SV type, size and genomic context (tandem repeats, segmental duplications, low mappability)</td>
			</tr>
			<tr>
					<td>Coverage</td>
					<td>40x (and 20x)</td>
					<td>15x and 30x</td>
			</tr>
	</tbody>
</table>
<p>The two changes that matter most are the reads and the length distribution. Simulated reads only came from assembled sequence, and their accuracy changed with their length, as it did for PacBio data at the time but does not for ONT, so read length and accuracy could not be separated. Real nanopore reads keep their real error profile at every length. A single fixed length per dataset is also not what a sequencing run produces.</p>
<h2 id="approach">Approach<a href="#approach" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h2>
<p>All code is available at <a href="https://github.com/wdecoster/critical-length-revisited">github.com/wdecoster/critical-length-revisited</a>.</p>
<p>I used the public ONT HG002 ultra-long R10.4.1 data (sup basecalling, two flow cells, 53x coverage, read N50 of 106 kb, and 16x in reads of at least 150 kb).</p>
<ul>
<li><strong>Fixed length:</strong> every read of at least L is cut into pieces of exactly L, placed at random within the read, for L from 1 to 150 kb.</li>
<li><strong>Library N50:</strong> pieces are drawn from the read length distribution of a standard ONT HG002 library (the public <code>giab_2025.01</code> data, ligation kit), rescaled to an N50 of 5 to 100 kb. This is closer to what you actually get from a sequencing run than a single length.</li>
</ul>
<p>The pieces were aligned with minimap2, subsampled to 15x and 30x, and SVs were called with Sniffles2 and compared to the GIAB HG002 v5.0q benchmark on five chromosomes, split by SV type, size and genomic context.</p>
<details>
<summary>The details</summary>
<ul>
<li>Long pieces only fit in long reads, so the drawing is calibrated until the pieces&rsquo; N50 is within 1% of the target.</li>
<li>Alignment with minimap2 (<code>lr:hq</code>) to GRCh38 (no-alt analysis set), subsampled to exactly 15x and 30x in the evaluation regions.</li>
<li>Chromosomes chr1, chr7, chr15, chr16 and chr20 (about 20% of the genome, 6,176 benchmark SVs, 555 of them in segmental duplications). The segmental duplication partners of these chromosomes elsewhere in the genome are included, so that reads from paralogous copies can still mismap into them.</li>
<li>Genomic context from the GIAB v3.6 stratifications: tandem repeats, segmental duplications, low mappability and the rest.</li>
<li>Scoring uses GIAB&rsquo;s benchmarking setup for truvari: matching on position, size and sequence, followed by <code>truvari refine</code>, which realigns the calls and the benchmark locally where they disagree (mostly in tandem repeats, where the same SV can be represented in different ways). Without sequence comparison and refine, the F1 values are 0.02–0.03 lower, with the same shapes.</li>
</ul>
</details>
<h2 id="results">Results<a href="#results" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h2>
<h3 id="library-n50">Library N50<a href="#library-n50" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h3>
<p><img src="/gigabaseorgigabyte/images/2026-10_critical_n50.png" alt="F1 of SV discovery against the read N50 of the library, at 15x and 30x"></p>
<table>
	<thead>
			<tr>
					<th>Library N50</th>
					<th>All SVs, 15x</th>
					<th>All SVs, 30x</th>
					<th>Segmental duplications, 15x</th>
					<th>Segmental duplications, 30x</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>5 kb</td>
					<td>0.781</td>
					<td>0.816</td>
					<td>0.559</td>
					<td>0.595</td>
			</tr>
			<tr>
					<td>8 kb</td>
					<td>0.814</td>
					<td>0.842</td>
					<td>0.587</td>
					<td>0.615</td>
			</tr>
			<tr>
					<td>10 kb</td>
					<td>0.825</td>
					<td>0.849</td>
					<td>0.608</td>
					<td>0.639</td>
			</tr>
			<tr>
					<td>15 kb</td>
					<td>0.843</td>
					<td>0.869</td>
					<td>0.605</td>
					<td>0.642</td>
			</tr>
			<tr>
					<td>20 kb</td>
					<td>0.855</td>
					<td>0.876</td>
					<td>0.640</td>
					<td>0.673</td>
			</tr>
			<tr>
					<td>30 kb</td>
					<td>0.868</td>
					<td>0.885</td>
					<td>0.652</td>
					<td>0.668</td>
			</tr>
			<tr>
					<td>50 kb</td>
					<td>0.871</td>
					<td>0.891</td>
					<td>0.674</td>
					<td>0.715</td>
			</tr>
			<tr>
					<td>100 kb</td>
					<td>0.881</td>
					<td>–</td>
					<td>0.718</td>
					<td>–</td>
			</tr>
	</tbody>
</table>
<p><em>F1 (Sniffles2, GIAB truvari setup with refine) by library N50 and coverage. The ultra-long data do not have enough coverage for 30x at a 100 kb N50.</em></p>
<p>The F1 rises steeply up to an N50 of about 20 kb and gains only about 0.03 from 20 to 100 kb. Doubling the coverage to 30x shifts the whole curve up by 0.02–0.035. Almost all of the gain is in recall: precision stays at 0.93–0.95 at every N50 and coverage. Variants in tandem repeats, two thirds of the SVs, follow the overall curve. Variants in segmental duplications are a different story: their F1 is much lower and still increasing at 100 kb.</p>
<details>
<summary>The details</summary>
<ul>
<li>The segmental duplication values are noisier (555 SVs) and not strictly increasing from one N50 to the next, but the trend from 0.61 at 10 kb to 0.72 at 100 kb (15x) is consistent at both coverages.</li>
<li>The shape of the read length distribution matters little: the standard library&rsquo;s distribution and the ultra-long library&rsquo;s distribution, rescaled to the same N50, give F1 values within 0.02 of each other (the standard shape slightly ahead). The N50 is therefore a reasonable single number to plan with.</li>
</ul>
</details>
<h3 id="fixed-read-length">Fixed read length<a href="#fixed-read-length" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h3>
<p><img src="/gigabaseorgigabyte/images/2026-10_critical_fixed_length.png" alt="F1 of SV discovery against a fixed read length at 15x"></p>
<p>With all reads cut to the same length, the F1 plateaus at about 0.88 from 50 kb onward, and reads of 20–30 kb are within 0.01–0.02 of that. The difference between SV types is informative:</p>
<ul>
<li><strong>Deletions:</strong> reads of 2–3 kb already find most of them.</li>
<li><strong>Insertions</strong> need reads of about 20 kb, because the read has to contain the inserted sequence and anchor on both sides.</li>
<li><strong>Insertions of more than 1 kb</strong> and <strong>segmental duplications</strong> keep improving up to 100 kb and beyond. Deletions of the same size do not need long reads.</li>
</ul>
<details>
<summary>The details</summary>
<ul>
<li>Deletions: F1 0.84 at 3 kb, 0.87 at 10 kb, 0.88 at most.</li>
<li>Insertions: 0.83 at 10 kb, 0.86 at 20 kb, 0.89 at most.</li>
<li>Insertions of 1–6 kb: F1 0.72 with 10 kb reads, 0.83 at 20 kb and 0.91 at 100 kb; of 6–10 kb: 0.49, 0.75 and 0.88. Deletions of 1–6 kb are at 0.83 already with 2 kb reads (0.88 at 10 kb, 0.93 at 100 kb), and those of 6–10 kb at 0.95 with any length.</li>
<li>SVs of more than 10 kb are rare in the benchmark (39 in these chromosomes) and are often missed even with 150 kb reads.</li>
<li>Segmental duplications: F1 0.66 at 20 kb, 0.74 at 150 kb.</li>
<li>Replicate cuts at 5, 20 and 100 kb gave F1 values within 0.005 of each other.</li>
<li>Cutting the standard HG002 library to 10, 20 and 30 kb gave the same results as cutting the ultra-long library, so the ultra-long library does not behave differently once the length is fixed.</li>
</ul>
</details>
<h3 id="then-and-now">Then and now<a href="#then-and-now" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h3>
<p><img src="/gigabaseorgigabyte/images/2026-10_critical_then_and_now.png" alt="F1 against read length for the 2020 pipeline on HG00733 and HG002, and real R10 reads now"></p>
<p>To place this next to the 2020 result, I reran the 2020 pipeline unchanged on the HG00733 assembly used in the paper, and on HG002 Q100.</p>
<p>Two things stand out. First, the simulated curves are flat from 5 kb (the first simulated length after 1 kb), while real reads keep improving up to 20–30 kb. Part of that difference comes from the simulation: SimLoRD models PacBio sequencing, in which a short fragment is read in several passes and is therefore more accurate than a long one, while ONT reads have the same accuracy at every length. Second, the small decline at the longest simulated lengths that we reported in 2020 also appears with the gap-free HG002 Q100 assembly, so it is not caused by assembly gaps. Real reads show no decline up to 150 kb, the longest length with enough coverage, so I would not plan around it.</p>
<details>
<summary>The details</summary>
<ul>
<li>The 2020 pipeline: SimLoRD simulation, minimap2 2.14, Sniffles 1, SURVIVOR matching. It scores against its own assembly-based truth with looser matching, and the simulated curves are at 40x (HG00733) and 20x (HG002), against 15x for the real reads, so the absolute values are not directly comparable to the truvari-based curve.</li>
<li>In the simulation, reads were only drawn from assembled sequence, which excluded the regions where length matters most, and the effect of length was partly offset by accuracy.</li>
<li>The decline on HG002 Q100 is in recall: 0.49 at 100 kb, 0.45 at 500 kb, with precision going up (not plotted; the F1 drops from 0.60 to 0.58 between 300 and 500 kb).</li>
</ul>
</details>
<h2 id="recommendation">Recommendation<a href="#recommendation" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h2>
<ul>
<li><strong>Aim for an N50 of 20–30 kb</strong> for SV discovery from ONT R10 reads. Beyond that the overall gains are small (about 0.03 F1 from 20 to 100 kb at 15x).</li>
<li>Once you are there: <strong>Invest in coverage before read length</strong>, as 30x instead of 15x gains as much as going from a 20 kb to a 100 kb N50.</li>
<li><strong>Go ultra-long for insertions of more than 1 kb and segmental duplications,</strong> which keep improving with read length, or if you plan to assemble.</li>
<li><strong>Deletions</strong> are already well called with short reads, so read length matters mostly for insertions and larger variants.</li>
</ul>
<h2 id="limitations">Limitations<a href="#limitations" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h2>
<ul>
<li>One genome (HG002), five chromosomes, the GIAB benchmark regions only, and one SV caller, so the absolute F1 values are optimistic.</li>
<li>Only read-based SV calling; assembly-based calling, phasing and the completeness of the inserted sequence are left for a follow-up.</li>
</ul>
<details>
<summary>The details</summary>
<ul>
<li>The GIAB benchmark regions exclude the regions where alignment of the assembly to the reference breaks, which are among the hardest for read-based calling.</li>
<li>Cut pieces lack the artifacts of real read ends (low-quality starts, adapter remnants), which slightly favours the shorter lengths.</li>
</ul>
</details>
<h2 id="try-it-yourself">Try it yourself<a href="#try-it-yourself" class="anchor" aria-hidden="true"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2"
      stroke-linecap="round" stroke-linejoin="round">
      <path d="M15 7h3a5 5 0 0 1 5 5 5 5 0 0 1-5 5h-3m-6 0H6a5 5 0 0 1-5-5 5 5 0 0 1 5-5h3"></path>
      <line x1="8" y1="12" x2="16" y2="12"></line>
   </svg></a></h2>
<p>The cutting tool is standalone and part of the repository, if you want to repeat this for your own data or question:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="c1"># all reads cut to 20 kb</span>
</span></span><span class="line"><span class="cl">python workflow/scripts/cut_reads.py reads.fastq.gz --length <span class="m">20000</span> --seed <span class="m">1</span> --output pieces.fastq.gz
</span></span><span class="line"><span class="cl"><span class="c1"># pieces following a library&#39;s read length distribution, rescaled to an N50 of 20 kb</span>
</span></span><span class="line"><span class="cl">python workflow/scripts/cut_reads.py reads.fastq.gz --distribution lengths.tsv --n50 <span class="m">20000</span> --seed <span class="m">1</span> --output pieces.fastq.gz
</span></span></code></pre></div><p>Feedback and suggestions are, as always, welcome.</p>
]]></content></item></channel></rss>