Mrthfx

CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?

Why proton concentration is divided by 10⁻⁷?

Replacement ford fiesta radiator has extra hose

How to count words in a line

What type of postprocessing gives the effect of people standing out

How can I handle a player who pre-plans arguments about my rulings on RAW?

Why does the author believe that the central mass that gas cloud HCN-0.009-0.044 orbits is smaller than our solar system?

What is better: yes / no radio, or simple checkbox?

If a druid in Wild Shape swallows a creature whole, then turns back to her normal form, what happens?

What prevents the construction of a CPU with all necessary memory represented in registers?

How can I find an Adventure or Adventure Path I need that meets certain criteria?

I can't die. Who am I?

Sometimes a banana is just a banana

Is my plan for fixing my water heater leak bad?

How to count occurrences of Friday 13th

Hacker Rank: Array left rotation

Is there a low-level alternative to Animate Objects?

What am I? I am in theaters and computer programs

Where is this triangular-shaped space station from?

What do the pedals on grand pianos do?

Whom do I have to contact for a ticket refund in case of denied boarding (in the EU)?

As a new poet, where can I find help from a professional to judge my work?

How to speed up a process

What to do when being responsible for data protection in your lab, yet advice is ignored?

Significance and timing of “mux scans”

Finding the location and unit length of repetitive sequences within a long readHow can we distinguish between true zero and dropout-zero counts in single-cell RNA-seq?Split FASTQ and matching BAM into matching chunksCOSMIC Genotypes and PhenotypesHow hard is it to clean and QC gene expression microarray data?What are the pros and cons of the different basecallers in Oxford Nanopore Technology Sequencing?I have two files: mys.nuc and ms.prep and need to use bioseq to extract the ORF sequences and save as “mys.nuc2”Difference between 1D and 1D^2 dataDifference between copy number neutral reads and active readswtdbg2: practical implications of k-mer fsize and psize choice

1

$begingroup$

I'm using MinIONQC 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

Reading this paper (doi: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?

sequencing nanopore quality-control

share|improve this question

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

$endgroup$

add a comment | 

1

$begingroup$

I'm using MinIONQC 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

Reading this paper (doi: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?

sequencing nanopore quality-control

share|improve this question

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

$endgroup$

add a comment | 

$begingroup$

I'm using MinIONQC 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

Reading this paper (doi: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?

sequencing nanopore quality-control

share|improve this question

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

$endgroup$

share|improve this question

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

share|improve this question

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

asked 2 hours ago

Daniel StandageDaniel Standage

2,368329

1 Answer
1

active

oldest

votes

3

$begingroup$

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.

share|improve this answer

answered 1 hour ago

Wouter De CosterWouter De Coster

63216

$endgroup$

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "676"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbioinformatics.stackexchange.com%2fquestions%2f7169%2fsignificance-and-timing-of-mux-scans%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

$begingroup$

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.

share|improve this answer

answered 1 hour ago

Wouter De CosterWouter De Coster

63216

$endgroup$

add a comment | 

3

$begingroup$

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.

share|improve this answer

answered 1 hour ago

Wouter De CosterWouter De Coster

63216

$endgroup$

add a comment | 

$begingroup$

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.

share|improve this answer

answered 1 hour ago

Wouter De CosterWouter De Coster

63216

$endgroup$

share|improve this answer

answered 1 hour ago

Wouter De CosterWouter De Coster

63216

answered 1 hour ago

Wouter De CosterWouter De Coster

63216

answered 1 hour ago

Wouter De CosterWouter De Coster

63216