Applied AI-Powered Bioinformatics Tools

Forensic STR Comparison Table

Last reviewed

Beginner

What you'll learn

~45 min
  • Ask an AI tool, in plan mode, for a program that reads a table of interpreted STR (short tandem repeat) calls (one row per sample per locus) and lays the questioned sample beside one reference at a time
  • Give it your laboratory's way of laying out a comparison table, and read its plan for what matters: every locus shown, each entry, code and source as written, single calls kept apart and sorted by whether the call is one of the other row's two, a locus that holds a code, an off-ladder entry or a third entry set apart unless a row there is empty, a count of each group, no conclusion words and no statistics
  • Check its tables against counts worked out for the practice file
  • Say what a count of loci with the same two calls shows, what it does not, and who decides what it means

The story, and what you will end up with

It is Thursday 12 November 2026, in the morning, at a university laboratory that types degraded samples. You are a DNA analyst. In a made-up case, MOCK-14, the laboratory has typed one questioned sample, Q-01, whose profile is incomplete, and three reference samples, R-01 to R-03.

The work that decides what is in the table is done. Q-01 was amplified twice and its calls were made from the two amplifications under the laboratory’s interpretation procedures; a colleague technically reviewed that interpretation, and all of it was finished before anyone looked at the references. The references were typed, and R-03, which gave no result at one locus, was amplified again and still gave none there. The reagent blanks, amplification blanks, positive controls and allelic ladders for the batch were reviewed, the profiles were checked against the profiles the laboratory keeps of its own staff, the sample identifiers were checked against the laboratory’s records, and the kit and software versions were recorded. The interpreted calls for all four samples are in one table.

In this practice laboratory a comparison table is then laid out by hand in a spreadsheet, one pair at a time, the way its procedure sets out, and a technical reviewer checks every table before any report is signed. A miscounted row, or a single call counted as if it were two, is the kind of slip the review is there to catch.

By the end of this lesson you will have a small program on your own computer, the comparison table, that lays Q-01 beside one reference you choose, locus by locus, and says for each locus only what the two rows hold. It counts the loci in each group and lists apart the loci where the rows do not show the same two calls. It never says match, inclusion or exclusion, never ranks one reference against another, and works out no statistic of any kind. You build it by asking your AI tool in plain English, and you check it against counts this lesson gives you.

🔍Words used in this lessonclick to expand
  • STR: short tandem repeat, the kind of DNA marker the laboratory types.
  • Locus (plural loci): one of the markers typed. Each row of the practice table is one sample at one locus.
  • Call: a value written for a sample at a locus, such as 11 or 9.3, after the analyst’s interpretation. A locus can hold two calls, one call, or none.
  • Plain call: a call in a row that carries no code.
  • Entry: anything written in an allele column, a call or something else, such as OL.
  • OL: off-ladder: this practice laboratory’s designation, written by the analyst at interpretation, for an entry that was not given a value against the allelic ladder. In this file it is an entry, not a call, and the table shows it as written.
  • Questioned sample: the sample whose source is the question in a case; here Q-01.
  • Reference: a sample taken for comparison; here R-01 to R-03.
  • No call: a locus where nothing is written for that sample.
  • Code: this practice laboratory’s own mark beside a sample’s calls at a locus, written by the analyst who interpreted the profile: NR (no result) or INC (inconclusive). What a code means and how it is used is set by the laboratory’s interpretation procedures, and the comparison table carries it as written.
  • Source: which amplification the calls came from: A1, A2, or A1+A2 for both.
  • Technical reviewer: the colleague who checks the work before a report is signed.

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:

Terminal window
mkdir -p ~/bio-workbench/14-str-comparison && cd ~/bio-workbench/14-str-comparison

Start 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/14/profiles.csv 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), the file is saved as data/profiles.csv, and a first snapshot, your checkpoint, is saved. Later you can ask whether the file has changed since then. If it does not mention one of them, ask: “Did you save a checkpoint with the file in it?” If the download does not work, download profiles.csv in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “profiles.csv is in my Downloads folder. Copy 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 file; later steps refer to it.

ℹWhat is in profiles.csvclick to expand

One table, which opens in a spreadsheet program: 80 rows, one for each of the four samples at each of 20 loci. Columns: Case (MOCK-14), Sample (Q-01, R-01, R-02, R-03), Locus, Allele_1, Allele_2, Allele_3, Code (NR, INC or blank) and Source (A1, A2 or A1+A2). One call is written in Allele_1 with the other two blank; a no call has all three blank.

SampleWhat its rows hold
Q-01Two calls at 11 loci; one call at D7S820 (10, coded INC), D13S317 (11, no code) and D22S1045 (15, no code, from A2 only); no call, coded NR, at CSF1PO, FGA, D18S51, D1S1656, D2S1338 and D12S391
R-01Two calls at 19 loci; one call at D22S1045 (15)
R-02Two calls at 19 loci; three entries at TPOX (8, 10, 11)
R-03Two calls at 17 loci; one call at D7S820 (10); OL and 14 at D8S1179; no call, coded NR, at D2S441 (from A1+A2)

The loci are in the file in this order: CSF1PO, FGA, TH01, TPOX, vWA, D3S1358, D5S818, D7S820, D8S1179, D13S317, D16S539, D18S51, D21S11, D1S1656, D2S441, D2S1338, D10S1248, D12S391, D19S433, D22S1045.

Everything in this file is made up for this course except the locus names (see How real tables differ): the case, the samples, every call, code and source. They describe no one. Each lesson in this track has its own practice files.

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 file, 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 file to use, and what you want from it:

I prepare STR comparison tables at a DNA lab. Build a program that lays the questioned sample in data/profiles.csv beside one reference at a time, locus by locus, saying what the two rows show. Ask me what you need first.

Your AI tool usually reads the file and comes back with questions. It may already point out some of what it sees: the loci with no call in Q-01, the single calls, or the OL entry. Leave its questions for now: send the six messages below first, then answer them. Your AI tool may wait for your answers or go straight on to propose a plan; either way, do not approve a plan until the six messages are sent.

Give it your laboratory’s way of laying out the table

The groups below are this practice laboratory’s way of sorting a comparison table, not a rule of the field; they say only what the two rows hold, never what that means. Your laboratory’s own procedure says how its comparison tables are laid out; use that.

For each locus, name one of these: same two calls; one call in each, same value; one call, one of the other row's two; one call, not one of the other row's two. I'll send the other groups next.

Wait for its reply, then send the rest of the groups:

The other groups: different calls; no call in the questioned sample, in the reference, or in both; anything else, shown as written.

Wait for its reply, then send this practice laboratory’s rule for a locus where a row carries a code or an entry that is not a call. The first five groups are the four in your first groups message and different calls. The rule says only where the table puts such a locus, not what any code means; your laboratory’s procedures decide where yours go.

A locus with no entries in a row stays under no call. Otherwise only plain calls with no code in both rows go in the first five groups; any code, OL or third entry goes only under anything else.

Wait for its reply, then send the words to keep out:

Show every entry, code and source as written. Never use words like match, consistent, inclusion, exclusion, identical, likely, agrees, shared or concordant. Never rank references or put several references' counts together. No statistics of any kind.

Even after this, an AI tool may put several references’ counts together in a reply, at any turn. Whenever that happens, send at once the sentence under Look at what it built that has such a summary removed, and use nothing from that reply.

Wait for its reply, then send what your laboratory’s procedure asks of every comparison table before anyone reads it:

Head each table with the case, both sample IDs, the file's name, today's date, and blank lines for who prepared it and the technical reviewer. Count each group and the loci with plain calls in both rows.

Wait for its reply, then send what the table must cover:

Show every locus in the file's order. List apart the loci where the rows don't show the same two calls, to sort by. Make it a program I can run again on another file, never changing the file it reads.

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 asksYou might say
What words for each locus: your laboratory’s terms, or neutral ones?Only the groups I gave you.
How should NR be shown?NR goes under no call, with the code shown as written.
INC: show the call, or leave it out?Show the call and INC as written, under anything else.
One call with no code: show it as 11, as 11, 11, or flag it?Show a single call as written; never add a code or a second call.
What about OL, or three entries at one locus?Both go under anything else, shown as written.
Are A1 and A2 two amplifications? Show the source?Yes, two amplifications. Show the source.
How does the file say which sample is questioned?Q-01 is the questioned sample; R-01 to R-03 are references.
On screen, a spreadsheet file, or a page?A table on screen and a file my spreadsheet opens.
The file’s order, or a kit’s order?The file’s order.
One table for one reference, or all at once?One table for one reference I name.
No call on one side and OL on the other: which group?The no-call group for that side.
Two calls in a different order: the same?Yes, the order of two calls does not matter.
Two calls against two that share one value: different calls?Yes, two calls against two that are not the same two are different calls.
Does 12, 12 count as two calls?This file writes a single call once, so 12, 12 does not occur here.
The same group whichever row holds the single call?Yes, the same group whichever row holds it.
Is a locus with a third entry left out of the plain-calls count?Yes, a third entry goes under anything else, so that locus is not counted.
Sort the separate list by group or by locus name?By group, then the file’s order.
A cell that starts with = or +, which a spreadsheet may run as a formula: stop and name it?Yes, stop and name the cell.

If it asks several questions at once, answer the ones about how loci are sorted and what each table must show from your laboratory’s own procedures, a sentence each, and accept its suggestions only about how the table looks. If you cannot tell which kind a question is, treat it as one for your procedures. 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:

  1. Every locus in the file is shown for the pair, in the file’s order, with both rows’ entries, codes and sources as written: 9.3 stays 9.3, and a code is never added where the file has none.
  2. Each locus goes in exactly one group, from the entries as written, and the group counts add up to the number of loci. One call against one call of the same value is its own group, not “same two calls”, and one call against two goes in one of two groups, by whether that call is one of the other row’s two. Any other pair of plain calls goes under different calls. A locus where either row carries a code, OL or a third entry goes under anything else, shown as written; a row with no entries keeps its locus under no call. A group names only what the rows hold; the entries shown beside it say which values they are.
  3. The count of loci with plain calls in both rows is shown beside the other counts, leaving out every locus under anything else. It counts entries, whatever their source.
  4. The loci where the rows do not show the same two calls are listed apart, as an aid for working through the table, not a list of the only loci to look at. In this practice laboratory every locus is still looked at.
  5. The heading carries the case, both sample IDs, the file’s name, the date and the two blank lines, and nothing in the table is a conclusion word, a ranking or a statistic. One pair at a time.
  6. It is a program you can run again on another file, and your file is read and left as it is.

A first plan often leaves one of these out, even when you have asked for it. Say so in a sentence, in your own words, for example:

The plan puts one call against one call of the same value under same two calls. Keep it as its own group, one call in each, same value.

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 a few scratch files of its own, ask it what they are for, and to remove them if you do not want them there.

Look at what it built

Ask it to run what it built for each reference in turn:

Run it for Q-01 with R-01, then R-02, then R-03, and show me the three tables.

It may show the tables in the terminal and save them as files your spreadsheet program opens, or build a page where you choose the reference. If it builds a page, ask: “Open the table in my browser.” If it gives you a file location or an address without opening it, copy that into your browser’s address bar and press Enter. If it starts the page at a local address, one ending in a number, and says the address is already in use, say: “Something else is using that address. Don’t stop it. Use a different address for my page.” If your AI tool does not take a message after opening the page, wait a minute. If it still does not, close the terminal window, open a new one, type this lesson’s folder line again, start your tool, and say: “Start the page again so it keeps running while we talk.” The page and your saved work are files in the folder, so nothing is lost. When you have finished with the page, ask: “Stop the table page if it is still running.”

Your AI tool may also put the three references’ counts side by side in one summary of its own. Have it taken off, on screen and in any file: “Remove the summary that puts the three references’ counts side by side, and don’t make one again.” Do not use counts it sets side by side in a reply either. Then read each pair’s own table.

Your tables will be worded and laid out in their own way. Check them for these:

  • Each table shows all 20 loci in the file’s order, under a heading with the case MOCK-14, Q-01 and the reference, profiles.csv, the date, and blank lines for who prepared it and the technical reviewer.
  • Q-01 with R-01: 11 same two calls; 1 one call in each, same value (D22S1045: 15 in each, no code); 1 one call, one of the other row’s two (D13S317: Q-01’s 11, R-01’s 11 and 12); 6 no call in the questioned sample; 1 anything else (D7S820, Q-01’s 10 coded INC); the other groups 0. 13 loci with plain calls in both rows. 9 loci listed apart.
  • Q-01 with R-02: 4 same two calls (D5S818, D8S1179, D10S1248, D19S433); 1 one call, one of the other row’s two (D13S317); 1 one call, not one of the other row’s two (D22S1045: Q-01’s 15, R-02’s 14 and 16); 6 different calls (TH01, vWA, D3S1358, D16S539, D21S11, D2S441); 6 no call in the questioned sample; 2 anything else (TPOX, where R-02 shows 8, 10 and 11, and D7S820); the other groups 0. 12 loci with plain calls in both rows. 16 listed apart.
  • Q-01 with R-03: 6 same two calls; 2 one call, one of the other row’s two (D13S317, D22S1045); 3 different calls (TPOX, D3S1358, D10S1248); 6 no call in the questioned sample; 1 no call in the reference (D2S441, coded NR); 2 anything else (D7S820, and D8S1179 with OL and 14); the other groups 0. 11 loci with plain calls in both rows. 14 listed apart.
  • In every table the groups add up to 20.
  • TH01 shows 9.3 as written, Q-01’s D13S317 shows 11 with no code beside it, and Q-01’s D7S820 shows 10 with INC beside it.
  • No line says match, consistent, inclusion, exclusion, identical or likely, or a word like them, such as agrees, shared, concordant or excluded; there is no percentage, probability, ratio or frequency; and no line sets one reference against another.
  • When you ask “Has my profiles file changed since the checkpoint?”, it compares the file with the checkpoint and says no.

If something on the list is not true, tell your AI tool in a sentence what you see and what you expected, for example: “D22S1045 for Q-01 and R-01 is under same two calls. Each row has one call there, so it goes under one call in each, same value.”

Notice what the table does not say

Find Q-01 with R-01 in your tables. A newcomer who sees it in a hurry may put it on a slide as “R-01 matches Q-01”. Ask your AI tool:

A colleague's slide says R-01 matches Q-01. What do these files show about that pair, and what don't they? Don't change anything.

Before you read on: what would you put on the slide instead?

The files show 20 loci. At 11 of them both rows have the same two calls. At one, D22S1045, each row has one call, 15, with no code, and Q-01’s came from one amplification only. At one, D13S317, Q-01’s one call, 11, is one of R-01’s two. At D7S820, Q-01’s one call, 10, is coded INC, so this practice laboratory’s table puts that locus under anything else and counts it in no other group. At six, Q-01 has no call at all. That makes 13 loci with plain calls in both rows, counted whatever their source, and “13 of 20” is exactly the figure a slide turns into a 13-locus conclusion: only 11 of the 13 have two calls on each side.

What the files do not show is the part that decides it. What a single call means, why a locus has no call, and whether any call is right are not in this table: they are questions for the data behind each call, judged under your laboratory’s interpretation procedures, and in this practice laboratory the technical reviewer checks every locus against that data, the 11 with the same two calls included. The table works out no statistic. In this practice laboratory, nothing goes on a slide or into a report until the analyst and the technical reviewer have done that work.

If your AI tool answers with a word such as consistent or match, or with a number such as a probability, tell it in a sentence, for example: “Take out ‘consistent’. Say only what the two rows show at each locus.”

The comparison table shows what the two rows hold at each locus; what the same calls, different calls or a single call mean, and what is reported, are for the DNA analyst and the technical reviewer to decide under the laboratory’s own interpretation procedures.

One real run

Here is part of what one AI tool said after the question above, with Claude Code on 12 November 2026. Yours will word it differently; check your tables against the checks above, not against this.

| one call in each, same value (1) | D22S1045: Q-01 15 (source A2 only), R-01 15 |
| one call, one of the other row's two (1) | D13S317: Q-01 11, R-01 11, 12 |
| anything else (1) | D7S820: Q-01 10 coded INC (source A1 only), R-01 10, 11 |
That leaves 13 loci with plain calls in both rows.
- **Interpretation.** The slide's wording is an interpretive conclusion, which
is the analyst's call under the lab's guidelines. Nothing in the files
states it.

The case, samples and calls it talks about are made up for this course.

The same answer also said that the files hold no population frequencies or statistics of any kind. What goes on a slide is still for the analyst and the technical reviewer to decide, after the work above.

How real tables differ

  • The locus names are real. All twenty are in the list headed “CODIS Core STRs” on STRBase, NIST’s Short Tandem Repeat DNA Database (strbase.nist.gov, read 12 November 2026). Check which loci your laboratory’s tables hold, and in what order.
  • Check what else yours holds. This practice file leaves out on purpose a sex marker and any locus beyond these twenty. Check what your laboratory’s comparison tables record, such as other loci, the kit and its version, run and injection identifiers and the analyst’s initials.
  • Check how yours writes a single call. Check whether it writes one call once, as here, or twice, such as 8, 8, and how many allele columns it has. If yours writes a single call twice, tell the program before you trust its groups, or it may count a single call as two.
  • The codes are this practice laboratory’s. NR and INC stand in for your laboratory’s own codes and designations. Whatever yours are, the table carries them as written and never adds one.
  • What one set of guidelines asks. Guidelines for forensic DNA laboratories from the Scientific Working Group on DNA Analysis Methods say: “The laboratory must establish guidelines to ensure that, to the extent possible, DNA typing results from evidentiary samples are interpreted before comparison with any known samples, other than those of assumed contributors.” They also say: “Comparisons (e.g., inclusions/exclusions) should not simply be based on the presence or absence of alleles for a particular contributor at a given locus, but instead be based on the possible genotype(s) that are being evaluated for each contributor at each locus while considering the overall quality of the profile (e.g., degradation, preferential amplification, inhibition, drop-out) and any assumptions being made with the interpretation.” (SWGDAM Interpretation Guidelines for Autosomal STR Typing by Forensic DNA Testing Laboratories, approved 12 January 2017, revised 13 July 2021, sections 3.1.1 and 3.1.3.1, read 12 November 2026.) The comparison table’s groups only sort what is written at each locus; the comparison that second passage describes is not something the table does.

Keep going

Small changes do not need plan mode. Say each in a sentence, then run it again:

  1. “Make a printable copy of each table, with the heading on every page.” Whether a printed copy is signed, and how, is for your laboratory’s procedures to say.
  2. “Does the program name any locus, sample or case from these practice files? If it does, make it work those out from the file instead.” A program built in a conversation may keep your examples written into it, and on another case’s file it would get them wrong.
  3. “Put a version number for the program on every table’s heading, and tell me when it changes.” How a tool’s versions are recorded is for your laboratory’s quality procedures to say.
  4. “Save a checkpoint.” Your AI tool saves a snapshot you can return to.

A program like this is used on casework only if your laboratory’s quality procedures allow it, after whatever validation and approval they require. If they do, the finished program 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. Records of a real case never go to your AI tool: not a profile, from casework or from a reference sample, not a row, not a sample identifier, not a screenshot of an error. Whether they may go anywhere else is set by your laboratory’s policy and its quality procedures; if they keep casework data on laboratory systems only, the program goes there only by the route those procedures set, and your AI tool does not. Your laboratory’s table of interpreted calls may not be shaped like the practice file; check its columns and its codes against the practice file’s. Do these steps in order; the first five happen now, while your AI tool is open and this folder still holds only the practice file:

  1. 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. Casework data is governed by your laboratory’s own procedures; your technical leader, and anyone else those procedures name, must agree. Go on only if they allow this use.

  2. Decide on a folder of its own for your real tables, outside this course folder, for example ~/str-tables. 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 str-tables in my home folder.”

  3. Ask your AI tool for a blank file and a made-up one to try: “In ~/str-tables, put only a blank profiles file my spreadsheet opens and a made-up one with one questioned sample and one reference. Keep the program and its checkpoints here. Run it on the made-up one and show me.” Look for it running the program on the made-up file and showing a table with its heading, groups and counts. Then open your own laboratory’s table of calls in a spreadsheet and tell your AI tool the names of its columns and how it writes a single call, a no call and its codes, with two rows you make up in the same shape, made-up samples and values, never a real row. For example: “My table’s columns are Sample Name, Marker, Allele 1 to Allele 4, Flag and Amp. Here are two made-up rows like that. Change the program to read such files, and change the made-up file in str-tables the same way.” Then paste the two rows you made up. Give column names only where your laboratory 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 calls from a case never go to it.

  4. Give the program your laboratory’s own codes, the groups its procedure lays a comparison table out in and its rule for where a coded, off-ladder or three-entry locus goes, including when the other row has no call, in place of this practice laboratory’s. For example: “Replace the practice codes, groups and rule for coded loci with ours, which I’ll send next. Then make up one pair in ~/str-tables with a locus for each group, and show me the table.” Your AI tool reads what you send it, so if your laboratory treats its procedures as confidential, ask whoever owns them before any of their wording goes to it. Wait for its reply, then send yours, in short messages as you sent the practice groups. Check that each made-up locus lands in the group it was made for, with its codes as written.

  5. Ask your AI tool for the exact line, for example: “Give me the exact one line to run this myself on a profiles file inside a folder called str-tables in my home folder, for R-01, with full paths, saving everything it writes there, never in this folder.” 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 -B /home/dana/bio-workbench/14-str-comparison/compare_str.py /home/dana/str-tables/profiles.csv R-01 --csv /home/dana/str-tables/Q-01_R-01_table.csv

    Read it left to right. python3 runs a Python program, and -B stops Python leaving its own cache files beside the program. Next comes the comparison program, in this lesson’s folder; then the table of calls, in str-tables. R-01 names the reference to lay beside the questioned sample, and --csv and the path after it name the table file it saves, in str-tables. /home/dana is the home folder of someone whose user name is dana; your own user name goes where dana is, and on a Mac the folders begin /Users/ instead of /home/. The line depends on the computer: the one above came from a Linux computer, so use the line your own AI tool gives you. The line runs the program where it is, so leave this lesson’s folder in place. Ask your AI tool, too, which column names your table of calls must keep, how its codes must be written, and how the line names the questioned sample and each reference’s output file, and note its answer beside the line. A run for the same pair may write over that pair’s last table files, so ask your AI tool whether it does, and rename those first if you want to keep them. If you are unsure about any part, ask your AI tool now, while it is still open.

    Then, before you leave your AI tool, try the line on the made-up file, because a real case’s profiles must never end up in the course folder: “Run that line on the made-up file in ~/str-tables, with its reference. Did the table land there, and did running it change anything in this folder?” Look for it saying the new table is in str-tables and nothing in this lesson’s folder changed. If the table landed in this lesson’s folder, tell your AI tool so and ask it for the line again.

  6. Leave your AI tool the way you did at the start of this lesson.

  7. Before any casework file goes into str-tables, the program goes through whatever validation and approval your laboratory’s quality procedures require, on the data they choose for it. Laying one pair out by hand the way your laboratory does now and comparing it with the program’s, locus by locus, is a first check, not a validation; if the two differ, find out why first. Go on only once the program is approved.

  8. First remove the made-up files and every table made from them; the blank file can stay. Or have your AI tool do it before you leave it in step 6, while only made-up data is there. As setup says, a tool started with approval prompts off can open other files your account can open. So save your laboratory’s table of calls into str-tables, named as your line names it and with the columns you noted, only if your laboratory’s procedures allow casework data on the computer and user account your AI tool runs under; if they do not, the program and the file go where those procedures say, by the route they set. Either way, start your AI tool only in your course folder from now on and never ask it about the str-tables folder; that is a habit, not a safeguard. Paste the line from your note at the $ or % prompt, now that your AI tool is closed, and put your own reference’s identifier in place of the made-up one wherever the line has it, the output file’s name included, so that one reference’s table is never written over another’s. Press Enter, and do the same once for each reference. The tables appear beside your real file, not in the course folder. Every table still goes to technical review, as your laboratory’s procedures set it. 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 with mkdir.

Try another case

Before the quiz, write two or three sentences for yourself. A newcomer shows you a slide that reads “R-07: 13 of 13 loci agree”. The comparison table behind it shows 10 loci with the same two calls, 3 with one call in each of the same value, and 7 with no call in the questioned sample. What do you ask them to change on the slide, and what do you tell them?

A good answer asks for the slide to say what the table says, with the 20 loci, the 13 with plain calls in both rows, and the three single calls written as single calls, and to drop “agree”. It tells them that what those rows mean is decided under the laboratory’s interpretation procedures, by the analyst and the technical reviewer, from the data behind each call.

Key takeaways

  • A short ask, then your laboratory’s layout. Say what you do and which file; give the groups and the words to avoid in your procedure’s own terms.
  • Read the plan for how loci are sorted: every locus shown, single calls kept apart, a locus with a code, OL or a third entry under anything else unless a row there is empty, codes carried as written, the count of loci with plain calls in both rows.
  • Check a new table against counts you know before you trust it on a case you do not.
  • A count of loci with the same calls is not a conclusion: it is a count of what is written in the table.
  • Practice data stays practice data: real profiles go to the finished program, with your AI tool closed, after the data check.
KNOWLEDGE CHECK

A comparison table for one pair shows: 12 same two calls, 2 one call in each, same value, 6 no call in the questioned sample, and nothing else. What can you write on a slide about this pair?

KNOWLEDGE CHECK

At one locus a reference's row shows three entries, 8, 10 and 11, and the questioned sample shows 8 and 11. What should the table do?

What’s next

The next lesson is about setting what turned up in an environmental DNA run’s controls beside what turned up in its field samples.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons