Sequencing Run QC Triage
Last reviewed
BeginnerWhat you'll learn
~45 min- Ask an AI tool, in plan mode, for a program that reads a run's demultiplexing summary (the table of read pairs and quality figures per sample, written after the reads are sorted by index) and the read pairs each lab requested
- Give it your facility's rules, and read its plan for what matters: a sample on two lanes added up, samples matched by lab and name, a reason beside every flag, a flagged lane's unmatched index pairs listed, and no word that sounds like a release
- Check its list against values worked out for the practice files
- Say why a flag tells you a sample needs a look but not what went wrong or what happens next
The story, and what you will end up with
It is Wednesday 11 November 2026, 8 in the morning, at a genomics core. A paired-end run (explained in the box below) of two lanes finished overnight. You are the staff scientist who releases its data to the labs. The core made and pooled every library on this run, and the labs’ submission forms asked them to state how many read pairs each sample needs.
Before this morning you did what comes first. When the pool was planned, you checked that no two samples in a lane had index pairs close enough to be confused, with the second index read either way round. You looked at the run in the instrument’s own viewer: the run finished, and both lanes and their index reads were in range by your facility’s run checks, which may include the share of clusters passing filter and a control library’s error rate. When the sample sheet (the table that says which index pair belongs to which sample) was made, you confirmed which way round this instrument reads the second index, and you know how many mismatched letters your demultiplexing allows. You compared the sample sheet with the submission forms. Then the demultiplexing step sorted the reads to samples by their indexes and wrote its summary.
Now, before anything goes to a lab, you want two things. First, any lane with too many read pairs that matched no sample, shown with the index pairs most often left unmatched in it, because that is what you read before going through the samples one by one. Then every sample sorted into two piles, the ones that look fine by your facility’s rules and the ones someone needs to look at, with the reason for each. Today that means reading three tables side by side.
By the end of this lesson you will have a small program on your own computer, the triage list, that reads a run’s summary files and makes that list on screen and as a file your spreadsheet program opens. It calculates no quality figure of its own, such as Q30 (explained in the box below): it reads the numbers the instrument’s software and the demultiplexing step wrote, adds read pairs across lanes, works out each sample’s share of its request and each lane’s share of undetermined read pairs, and compares them with your rules. Beside a lane that needs a look, it lists the index pairs most often left unmatched there, with their read pairs, and leaves what they mean to you. It never sends anything. You build it by asking your AI tool in plain English, and you check it against numbers this lesson gives you.
🔍Words used in this lessonclick to expand
- Read pair: on a paired-end run, each fragment is read from both ends, giving two reads. The files here count each pair once.
- Index: a short stretch of letters added to every fragment of one library, so libraries pooled in one lane can be told apart. These samples carry two, Index and Index2 (often called i7 and i5).
- Demultiplexing: sorting a lane’s reads to samples by their index pairs, using the sample sheet, the table that says which index pair belongs to which sample.
- Undetermined: read pairs whose index pair matched no sample on the sample sheet.
- Q30: the instrument maker’s measure of base-call quality. In its words, “Sequencing quality scores measure the probability that a base is called incorrectly”, and Q30 means a probability of “1 in 1000” (Illumina, Sequencing Quality Scores, read 11 November 2026). The files give, for each sample in each lane, the share of bases at Q30 or above, as the software reported it.
- Perfect index reads: the share of a sample’s read pairs whose indexes matched the sample sheet exactly, with no letter different.
Before you start
First, if your AI tool is still open, leave it: type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead), and wait until you see the $ or % prompt. The next line goes there, in the terminal, not in the AI tool. It makes a folder for this lesson beside your practice folder and goes into it:
mkdir -p ~/bio-workbench/18-run-triage && cd ~/bio-workbench/18-run-triageStart your AI tool with the start line you kept from the setup lesson, the one with approval prompts off. Then ask it to set the folder up:
Set this folder up so we can undo any change you make, download https://learn.intellimetrics.net/starters/biotech/18/run-summary.zip and unpack it into a data folder, and save a checkpoint.Look for it saying three things: the folder is set up with Git (the program that saves snapshots, from setup), three files are in the data folder (demux-summary.csv, requested.csv and top-unknown-index-pairs.csv), and a first snapshot, your checkpoint, is saved. Later you can ask whether the files have changed since then. If it does not mention one of them, ask: “Did you save a checkpoint with the files in it?” It may also keep the zip file in the data folder, which is fine; if it says it kept one somewhere outside this folder, ask it to delete that copy. If the download does not work, download run-summary.zip in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “run-summary.zip is in my Downloads folder. Unpack that one file into a data folder here, and save a checkpoint.” In Windows PowerShell or a desktop app, “my Downloads folder” works as is; only say “my Windows Downloads folder” if you use Ubuntu (WSL) on Windows, which keeps its own Downloads folder apart from Windows.
The box below says what is in the practice files; later steps refer to them.
ℹWhat is in run-summary.zipclick to expand
Three files, each of which opens in a spreadsheet program, from one paired-end run of two lanes:
demux-summary.csv: one row per sample per lane, plus an Undetermined row for each lane. Columns: Lane, Sample_ID, Lab, Index, Index2, Read_Pairs, Perfect_Index_Pct, Q30_Pct.requested.csv: the read pairs each lab asked for on its submission form. Columns: Sample_ID, Lab, Pairs_Requested.top-unknown-index-pairs.csv: for each lane, the four index pairs that matched no sample most often, with their read pairs. The program reads this list; it does not find the pairs itself.
Read pairs in these files are those that passed the instrument’s filter, as the demultiplexing step counted them.
| Sample | Lab | Requested | Lane 1 read pairs | Lane 2 read pairs | Q30 |
|---|---|---|---|---|---|
| S-01 | LAB-17 | 20,000,000 | 22,410,336 | 92.4 | |
| S-02 | LAB-17 | 20,000,000 | 17,918,204 | 91.8 | |
| S-03 | LAB-17 | 20,000,000 | 18,086,551 | 92.1 | |
| S-04 | LAB-23 | 30,000,000 | 31,552,870 | 71.3 | |
| S-05 | LAB-23 | 60,000,000 | 29,804,117 | 31,207,456 | 92.0 and 91.4 |
| S-06 | LAB-23 | 30,000,000 | 12,603,388 | 91.6 | |
| S-07 | LAB-31 | 25,000,000 | 26,880,245 | 90.9 | |
| S-08 | LAB-31 | 25,000,000 | 25,113,902 | 91.2 | |
| S-09 | LAB-31 | 25,000,000 | 24,402,118 | 90.7 | |
| S-10 | LAB-31 | 25,000,000 | 1,204 | 84.0 | |
| S-11 | LAB-31 | 25,000,000 |
S-01 to S-06 were in lane 1 and S-05 to S-10 in lane 2; S-05 was run on both lanes. Undetermined read pairs: 2,633,868 in lane 1 and 25,323,450 in lane 2. S-11 is in the requested file only: it is on a submission form but was not on this run, which you saw when you compared the sample sheet with the forms. The list should still show it, so a sample a lab is waiting for is not forgotten when the run’s data goes out. Every sample’s perfect index reads are 98.2% to 98.8%, except S-10’s, 61.4%.
Everything in these files is made up for this course: every sample, lab, index and number; no instrument or real run produced them. Each lesson in this track has its own practice files, with their own people and dates.
Switch to plan mode
Your AI tool is already open. Switch to plan mode now: Shift+Tab until it says plan, or /plan (the keys for each tool). In plan mode it usually reads your files, asks its questions and shows you a plan before it builds anything; the order can vary.
The conversation
Each message below is an example. Say it your own way.
Say what you want
Say what you do, which files to use, and what you want from them:
I release data at our genomics core. Build a program that reads each run's files, like those in data, and sorts samples into fine and needs a look, by rules I'll give you. Ask me what you need first.Your AI tool usually reads the files and comes back with questions, starting with your rules. It may already point out some of what it sees: S-05 on two lanes, S-11 with no reads, lane 2’s undetermined reads, or something about S-10.
Give it your rules
These are this practice facility’s own rules, numbers included. Your facility’s are in its own written procedures; use those.
Our rules: a sample needs a look under 90% of requested read pairs, added across lanes, or in any lane under 80% Q30 or under 95% perfect index reads.Wait for its reply, then send the lane rule in a second message:
A lane needs a look over 5% undetermined; beside it, list its most common unmatched index pairs with their read pairs, without saying what they mean. Give reasons. Never say passed, failed or released.The list says fine or needs a look because it is a first sort, not a decision about any sample.
Answer its questions
Answer each in a sentence. These are questions the tools often ask, with one way to answer each. Yours may ask them in a different order or show a list of choices:
| If it asks | You might say |
|---|---|
| Does exactly meeting a limit count as fine? | Yes. Exactly at a limit is fine. |
| For a sample on two lanes, check Q30 per lane or as an average? | Check each lane on its own; any lane under 80% needs a look. |
| Should a lane with too many undetermined reads flag every sample in it? | No. Give the lane its own warning; don’t flag every sample in it. |
| Count undetermined out of every read pair in the lane? | Yes, out of every read pair in the lane, undetermined included. |
| How many unmatched pairs should it show for a lane? | All the pairs the file lists for that lane. |
| A requested sample with no reads, or reads nobody requested? | Both need a look. |
| A missing or blank value? | It needs a look. |
| Is getting more read pairs than requested a problem? | No. Over the request is fine. |
| Should it look for likely causes, such as an index entered backwards? | No. Flag it, and I’ll work out the cause myself. |
| On screen, a spreadsheet file, or a report for the labs? | A list on screen and a file I can open in a spreadsheet. |
| Will each run be its own folder with these three files? | Yes, each run is its own folder with these three files. |
If it asks several questions at once, answer the ones about your rules and how samples are counted from your facility’s own procedures, a sentence each, and accept its suggestions only about how the list looks. If you cannot tell which kind a question is, treat it as a rule. If it asks something not listed here, answer it the same way, in a sentence.
Read the plan
Next it usually shows you a plan: what it will build and how it will check it. Read it for six things:
- A sample on two lanes is added up before its read pairs are compared with what was requested.
- Samples are matched by lab and name together, and a sample requested but not in the run, or in the run but not requested, needs a look.
- Every sample or lane that needs a look gives its reason, with the rule and its numbers, and the rules are the ones you gave.
- A lane is checked for undetermined read pairs on its own: beside a lane that needs a look come its most common unmatched index pairs with their read pairs, with nothing said about what they mean, and a lane’s warning does not change what the list says about the samples in it.
- The list says fine or needs a look, never passed, failed or released.
- It is a program you can run again on the next run’s folder, and your files are read and left as they are.
A first plan often leaves one of these out, most often item 2. Say so in a sentence, in your own words, for example:
Match each sample by its lab and its name together, not by name alone, and flag any sample whose lab differs between the files.When the plan has all six, approve it: if your AI tool offers a choice to go ahead, pick it; otherwise say “Yes, go ahead and build it.” In Codex, press Shift+Tab first to leave plan mode. In Copilot, saying it brings up a choice to go ahead; pick that. Let it build. It may run what it built and tell you how to run it yourself; either way, the next step asks it to. When it has finished, ask it: “Did you install anything, and where?” Nothing, or something inside this lesson’s folder, is fine for these lessons. If it names anywhere else on your computer, such as the zip file it downloaded, ask it what that is for, and to remove it if you do not want it there.
Look at what it built
Ask it to run what it built:
Run it on the files in data and show me the list.Your list will be worded and laid out in its own way, and some figures may be only in the spreadsheet file, not on screen. Check it for these:
- Five samples need a look. S-02: 17,918,204 of 20,000,000 read pairs, 89.6%. S-04: Q30 71.3% in lane 1. S-06: 12,603,388 of 30,000,000, 42.0%. S-10: 1,204 of 25,000,000, 0.0% at one decimal place, and perfect index reads of 61.4% in lane 2. S-11: requested, with no reads in this run.
- Six samples are fine: S-01, S-03 (90.4%), S-05, S-07, S-08 and S-09.
- S-05 is fine with 61,011,573 of 60,000,000 read pairs, 101.7%, its two lanes added together. If it needs a look at about half its request, the lanes have not been added; tell your AI tool so.
- Lane 2 needs a look: 25,323,450 of its 132,928,375 read pairs are undetermined, 19.1%. Lane 1 is fine at 2,633,868 of 135,009,334, 2.0%. These count undetermined pairs out of every read pair in the lane, undetermined included. If yours counts them out of only the read pairs that matched a sample, lane 2 shows 23.5%; tell your AI tool to count every read pair in the lane.
- Beside lane 2 are its most common unmatched index pairs with their read pairs, the first
CTTTCCCAATwithGAACAACGGG, 23,918,540 read pairs, and nothing that says what they mean. Some lists show lane 1’s pairs too; that does no harm. - No line says passed, failed or released.
- When you ask “Have my run files changed since the checkpoint?”, it compares them with the checkpoint and says no.
The percentages here are rounded to one decimal place; yours may show more, such as 89.5910%. The list should compare the numbers before rounding, so a sample shown as 90.0% may still be just under 90% and need a look.
If something on the list is not true, tell your AI tool in a sentence what you see and what you expected, for example: “S-05 shows 52.0% in lane 2. Add its two lanes together before comparing with the 60,000,000 requested.”
Notice what a flag does not say
Start with the lane: lane 2 needs a look, 19.1% of its read pairs undetermined, with its most common unmatched index pairs beside it. Then S-10: needs a look, 1,204 of 25,000,000 read pairs and perfect index reads of 61.4%. Read alone, S-10 looks like a library that failed, and a lane to run again.
Before you ask your AI tool about them, put the first pair beside lane 2 on your list next to S-10’s index pair. S-10’s pair is in demux-summary.csv in this lesson’s data folder; you can ask your AI tool to show you S-10’s row. What do you see? Then ask your AI tool:
Lane 2 and S-10 both need a look. Is there anything in these files that could explain them? Don't change anything.Lane 2’s most common unmatched index pair, 23,918,540 read pairs, is CTTTCCCAAT with GAACAACGGG. S-10’s index pair on the sample sheet is CTTTCCCAAT with CCCGTTGTTC. The first index is the same. The second is S-10’s second index read backwards with each letter swapped for its pair (A for T, C for G), the reverse complement. That one pair is 94.5% of lane 2’s undetermined read pairs; without it, lane 2’s undetermined share would be 1.1%, and S-10’s read pairs would come to 95.7% of its request. So the two flags are probably one event, and S-10’s reads may be in the run under an index pair the sample sheet did not list. It says nothing against S-05, S-07, S-08 or S-09, the other samples in lane 2.
It is a lead, not a finding. The files show a match, not how the index was entered or why. Before anything changes, you check the core’s library record for S-10 and the sample sheet, and find the step where its second index came to be written that way. Confirming which way round the instrument reads the second index settles the sheet’s convention; it does not catch one entry written the other way. The other LAB-31 samples matched their indexes, so the files show nothing wrong with their entries; whether any other entry was made the same way is for the sample sheet to tell you. Before lane 2 is demultiplexed again with the corrected pair, you check that pair against every other sample in lane 2, at the number of mismatches your demultiplexing allows. Nothing is promised to LAB-31 until new counts are confirmed. The 1,204 read pairs now under S-10 are most likely strays from other samples in the lane: only 61.4% of them matched its indexes exactly, against 98.2% to 98.8% for every other sample. So their Q30 of 84.0 is not read as S-10’s until lane 2 has been demultiplexed again with the corrected index. The list flags the 61.4% by your rule; what it means is yours to read.
S-04 needs a look for another reason: enough read pairs, but a Q30 of 71.3% in a lane where the other samples are at 91 to 93%. One sample’s low figure in a lane that is otherwise high may be a question about that library rather than the run. On a real run, check what your procedures ask you to look at before saying so, such as which read is the low one, where your software gives Q30 for each read, or that library’s other signs, such as adapter content; these files give one figure.
The list says which samples need a look, not what went wrong or what happens next: releasing, demultiplexing again, rerunning or talking to the lab is the staff scientist’s decision under the facility’s procedures.
A sample on the fine side has met your rules’ numbers, and that is all. It is not released until you have done everything else your facility requires.
One real run
Here is part of what one AI tool said after the question above, with Claude Code on 11 November 2026. Yours will word it differently; check your list against the checks above, not against this.
- **Low perfect index.** S-10's 61.4% perfect-index figure fits the idea that the 1,204 reads it got only matched with errors, but it doesn't prove anything by itself.One part of that answer is wrong. The summary shows 61.4% of those read pairs matching S-10’s indexes exactly, so they did not “only match with errors”: a tool’s explanation of your data is checked against the file like anything else.
The samples, lane and index pairs it talks about are made up for this course.
The same answer ended by saying that demultiplexing lane 2 again with the corrected second index “should move those reads to S-10”. That is something to confirm once the new counts exist, not something to tell the lab now.
How real runs differ
- The maker’s quality figure is for a run, not a sample. The instrument maker publishes a quality specification for each instrument, kit and read length. For example, for one instrument family at 2 × 150 bp it gives ”≥ 90% of bases higher than Q30”, and adds: “Quality scores are based on an Illumina PhiX control library; performance may vary based on library type and quality, insert size, loading concentration, and other experimental factors.” (Illumina, NextSeq 1000 and NextSeq 2000 specifications, XLEAP-SBS chemistry, read 11 November 2026). This practice facility’s 80% for each sample is its own rule, not the maker’s. The maker also says Q30 “corresponds to a predicted base-call accuracy of 99.9%” (Sequencing Quality Scores): a prediction from its software, read beside everything else you know about the library.
- Which way round the second index goes depends on the instrument. The maker’s guidance says: “When performing dual indexing, all Illumina sequencers read the first index (i7) in the forward orientation; however, the second index (i5) is read in different orientations depending on the instrument and chemistry” (Illumina, Guidelines for reverse complementing i5 sequences for demultiplexing, read 11 November 2026). The article lists what each instrument and piece of software expects; your sample sheet procedure is where your facility settles it.
- Undetermined is not all mistakes. A control library added to a lane and not listed on the sample sheet lands in the undetermined reads. Check whether your core adds one. Here the core pooled the libraries, so you know whether a control went into each lane and can read its share in the run’s own metrics; read a lane’s undetermined share with that in mind. These practice files do not include it.
- Who made and pooled the libraries matters. Here the core made and pooled them. When a lab pools its own libraries, a sample’s shortfall may come from its pooling, and your facility’s policy says what the core guarantees, what is run again, and who pays. Whether a sample well over its request, such as S-01 at 112.1%, matters for billing is policy too; the list calls it fine.
- Other checks may come before release. Check whether your procedures also call for checks of adapter content, duplication or contamination before data goes out, and whether data from human samples has rules about who may receive it and how.
- Real summaries may hold more. Check what yours holds, for example: more lanes and samples; samples topped up from an earlier run, whose read pairs need adding in; Q30 given for each read (read 1, read 2, the index reads) instead of one figure per sample; counts and quality in separate files; single-index samples in a dual-index lane; several versions of a sample sheet; requests written in other units, such as total reads instead of read pairs. Make sure the request and the counts are in the same unit, converting or asking the lab where they differ, or the 90% rule means nothing.
- Sample names can identify people or animals. Check whether your facility’s sample names carry a patient or animal identifier; if they do, treat them as you would the data.
Keep going
Small changes do not need plan mode. Say each in a sentence, then run it again:
- “Draft a short note to LAB-31 about S-10 that says only what the files show, with a blank for what we will do.” Check every number in it, and fill in the blank only after you have decided; nothing goes to the lab until then.
- “Does the program name any sample or lane from these practice files? If it does, make it work those out from the files instead.” A program built in a conversation may keep your examples written into it, and on the next run’s files it would get them wrong.
- “Save a checkpoint.” Your AI tool saves a snapshot you can return to.
When you want a list for a real run, use the finished program. It runs on your real files by itself, with your AI tool closed, so your AI tool never sees them. Nothing confidential or unpublished, and nothing about people or about animals under a protocol, goes to your AI tool or into this course folder. Your demultiplexing software’s summary will not be shaped like the practice files, and your requests may live in a form or a sheet. Do these steps in order; the first five happen now, while your AI tool is open and this folder still holds only the practice files:
-
Go through the data check, the questions in setup about what the data is, who decides how it is used, and which AI tool would see it. A lab’s data is that lab’s to decide on, and human-sample data may need your facility director or compliance office as well. Go on only if they allow this use.
-
Decide on a folder of its own for your real files, outside this course folder, for example
~/run-triage. Nothing has to be in it yet. If the folder is not there, ask your AI tool to make it: “Make an empty folder called run-triage in my home folder.” -
Ask your AI tool for a blank requested file and a made-up run to try: “Make me a blank requested file my spreadsheet program can open, in the run-triage folder in my home folder, and a made-up run folder here with one sample, and show the program working on it.” Look for it running the program on the made-up run and showing that sample as fine or needing a look. The blank requested file has a Lab column; fill it from the submission forms. Your demultiplexing summary may have no lab column: if not, tell your AI tool where each sample’s lab is recorded, such as a project column on your sample sheet. If your software gives Q30 for each read, say which reads your rule applies to. Then look at your own demultiplexing summary in a spreadsheet and tell your AI tool the names of its columns (if your software writes counts and quality in separate files, say so and give each file’s columns), with two rows you make up in the same shape, made-up sample names and numbers, never a real row. For example: “My demultiplexing summary has the columns Lane, Sample, i7, i5, Pairs PF, Perfect % and Q30 %. Here are two made-up rows in the same shape. Change the program to read files like that.” Then paste the two rows you made up. Give column names only where your core is content for them to go to your AI tool; if it treats them as confidential, ask whoever is responsible first, or make up equivalents. Real sample names never go to it.
-
Give the program your facility’s own rules in place of the four practice rules, from its written procedures, numbers included. For example: “Replace the four practice rules with ours, which I’ll send next. Then make up one sample or lane for each rule that only that rule flags, and show me the list.” Send your rules, then check that each made-up sample or lane is flagged by the rule it was made for, with that rule’s reason.
-
Ask your AI tool for the exact line, for example: “Give me the exact one line to run this myself on a run folder inside a folder called run-triage in my home folder, with full paths, saving the list there too.” Use your own folder’s name. If it offers to copy your real files into this folder instead, say no. Copy the line it gives you into a note. It will look something like this one, though yours may differ:
Terminal window python3 /home/dana/bio-workbench/18-run-triage/triage.py /home/dana/run-triage/RUN_NAME -o /home/dana/run-triage/triage-RUN_NAME.csv | tee /home/dana/run-triage/triage-RUN_NAME.txtRead it left to right.
python3runs a Python program. Next comes the triage program, in this lesson’s folder; then the run’s folder inside run-triage;-oand the name after it say where the spreadsheet file goes.| teeand the last name keep a copy of the on-screen list in a text file there too.RUN_NAMEstands for your run folder’s name, in three places; each run, you change it to that run’s./home/danais the home folder of someone whose user name is dana; your own user name goes wheredanais, and on a Mac the folders begin/Users/instead of/home/. The line runs the program where it is, so leave this lesson’s folder in place. If you are unsure about any part, ask your AI tool now, while it is still open. -
Leave your AI tool the way you did at the start of this lesson.
-
Put a real run’s files in a folder of their own inside run-triage, named as your line names it, with your requested file filled in from the submission forms. Paste the line from your note at the
$or%prompt and press Enter. The list appears beside your real files, not in the course folder. To come back to the lesson folder later, type this lesson’s folder line again, the line near the top of this page that begins withmkdir. -
Before you act on the list, compare a few of its figures with your demultiplexing software’s own report for the same run. If they differ, find out why first.
Try another case
Before the quiz, write two or three sentences for yourself. Next week the list says lane 1 needs a look, with 6% of its read pairs undetermined, and every sample in lane 1 has what it requested. A colleague says the lane is fine and asks you to clear the warning. What do you check, and what do you decide?
A good answer looks at the most common unmatched index pairs before deciding anything: whether they match a sample’s indexes written another way, a control added to the lane, or nothing on the sample sheet. It treats the warning as a reason to look, not as a verdict on the samples, and it leaves the rule as the facility wrote it; whether the lane needs anything done is the staff scientist’s call, written down under the facility’s procedures.
Key takeaways
- A short ask, then your rules. Say what you do and which files; give your facility’s rules in its own words.
- Read the plan for how samples are counted and matched: lanes added, lab and name together, a reason beside every flag.
- Check a new list against numbers you know before you trust it on a run you do not.
- A flag says where to look. Why a sample is short, and what happens to it, is yours to find out and decide.
- Practice data stays practice data: real runs go to the finished program, with your AI tool closed, after the data check.
A lab asked for 40,000,000 read pairs for one sample. The sample was run on two lanes and got 21,000,000 in one and 19,500,000 in the other. By this practice facility's rule of 90% of the requested read pairs, added across lanes, what does the list say?
The list says one sample needs a look: 900 of 30,000,000 read pairs. The same lane has 22% of its read pairs undetermined, and its most common unmatched index pair is that sample's first index with its second index reversed and complemented. What should happen next?
What’s next
The next lesson is about checking the editing outcomes a genome-editing core’s analysis software has already recorded against the core’s rules, and listing which samples need a look.