<p>Yes, your understanding is largely correct. This originates from the situation that for each detector on a nanopore array there are 4 pores. I'll explain mux scans and groups, but this is outdated information as now another system is used.</p>

<p>So a MinION FC has 2048 pores with 512 sensors. Not all of these pores will be equally suitable for sequencing. At the beginning of the run originally a mux scan was performed, to test for each sensor which the best pore would be (if any) out of the 4 available. The best pores will be used for sequencing first, the rest will be turned off. That is group 1. After 8 hours the expectation is that many of these pores have degraded/accumulated damage or are not functional for other reasons. Then it is time to swith to group 2. So you change to another set of pores, which in these cases often lead to a temporary increase in yield. The default script used 8 hours, although some used adaptive software to select new pores when the first group started going bad. Also note that during the run no new mux scan was performed: the software did not check if the selection it made in the beginning still made sense. Pores in group 1 got turned off after 8 hours and switched to group 2, without taking their current 'health' into account. Cumulative yield plots get a characteristic bumpy pattern from this. Each bump is less than the previous one, eventually flatting off.</p>

<p>Now that's history, as the software now uses dynamic muxing and will continuously check for the best pore per channel - and as such maximize yield by having as many healthy pores as possible available for sequencing. Cumulative yield plots are now smoother.</p>

CC BY-SA 4.0
2019-03-04T21:27:25.603Z
2019-03-04T21:27:25.603Z
Wouter De Coster
<p>I'm using <a href="https://github.com/roblanf/minion_qc" rel="nofollow noreferrer">MinIONQC</a> to do quality control on some ONT data. The software plots several read characteristics over time (hours passed during the sequencing process). These plots contain several vertical red lines. From the documentation:</p>

<blockquote>
  <p>Muxes, which occur every 8 hours, are shown as red dashed lines</p>
</blockquote>

<p><a href="https://i.sstatic.net/hh0IF.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/hh0IF.png" alt="Read quality by hour"></a></p>

<p>Reading <a href="https://dx.doi.org/10.12688/f1000research.7201.1" rel="nofollow noreferrer">this paper (doi:10.12688/f1000research.7201.1)</a> I was able to get a rough idea of what a "mux" or a "mux scan" is. If I understand correctly, it's a calibration step that scans each well containing 4 nanopores to determine which nanopores will be used for data collection in which order.</p>

<p>Do I understand the basic idea of the mux scan correctly? Does it occur at the same frequency on all ONT instruments? Does it always occur in 8hr intervals, even if the sequencing reaction is run for longer than the standard run time?</p>

<ngs><nanopore><quality-control>
Significance and timing of "mux scans"
# Significance and timing of "mux scans"

(Asked by: username_0 on 2019-03-04)

I'm using [MinIONQC](https://github.com/roblanf/minion_qc) to do quality control on some ONT data. The software plots several read characteristics over time (hours passed during the sequencing process). These plots contain several vertical red lines. From the documentation:

> Muxes, which occur every 8 hours, are shown as red dashed lines

[![Read quality by hour](https://i.sstatic.net/hh0IF.png)](https://i.sstatic.net/hh0IF.png)

Reading [this paper (doi:10.12688/f1000research.7201.1)](https://dx.doi.org/10.12688/f1000research.7201.1) I was able to get a rough idea of what a "mux" or a "mux scan" is. If I understand correctly, it's a calibration step that scans each well containing 4 nanopores to determine which nanopores will be used for data collection in which order.

Do I understand the basic idea of the mux scan correctly? Does it occur at the same frequency on all ONT instruments? Does it always occur in 8hr intervals, even if the sequencing reaction is run for longer than the standard run time?

**Tags:** ngs, nanopore, quality-control

---

## 1 answers

### Answer by username_1 on 2019-03-04. Score: 6

Yes, your understanding is largely correct. This originates from the situation that for each detector on a nanopore array there are 4 pores. I'll explain mux scans and groups, but this is outdated information as now another system is used.

So a MinION FC has 2048 pores with 512 sensors. Not all of these pores will be equally suitable for sequencing. At the beginning of the run originally a mux scan was performed, to test for each sensor which the best pore would be (if any) out of the 4 available. The best pores will be used for sequencing first, the rest will be turned off. That is group 1. After 8 hours the expectation is that many of these pores have degraded/accumulated damage or are not functional for other reasons. Then it is time to swith to group 2. So you change to another set of pores, which in these cases often lead to a temporary increase in yield. The default script used 8 hours, although some used adaptive software to select new pores when the first group started going bad. Also note that during the run no new mux scan was performed: the software did not check if the selection it made in the beginning still made sense. Pores in group 1 got turned off after 8 hours and switched to group 2, without taking their current 'health' into account. Cumulative yield plots get a characteristic bumpy pattern from this. Each bump is less than the previous one, eventually flatting off.

Now that's history, as the software now uses dynamic muxing and will continuously check for the best pore per channel - and as such maximize yield by having as many healthy pores as possible available for sequencing. Cumulative yield plots are now smoother.


---

