Applied AI-Powered Bioinformatics Tools

Skeletal Element Inventory Visualizer

Last reviewed

Beginner

What you'll learn

~40 min
  • Ask an AI tool, in plan mode, for a program that reads the typed inventory from a field school's mock recovery (one row per recorded item) and the project's own lists, and tallies the entries by element and side
  • Give it the project's recording rule, and read its plan for what matters: every entry tallied as recorded, nothing corrected, every broken rule, every repeated element and side and every unused field number listed, and no count of individuals
  • Check its list against values worked out for the practice files
  • Say what a tally of entries can and cannot show, and who settles the questions it raises

The story, and what you will end up with

It is Thursday 12 November 2026 in a university’s forensic anthropology laboratory. You lead the laboratory inventory after field recoveries. Last week, on 3, 4 and 5 November, the department’s field school held its mock recovery at the university’s outdoor teaching site. The field school’s director had buried replica skeletal material in a gridded area of sixteen one-metre units, A1 to D4. Two pairs of students did the work: for each item, one pair exposed and lifted it, bagged it, gave it a field number from the field-number register and recorded it on a paper field form. The director keeps the burial record sealed until the students have done their laboratory inventory, so that inventory tests their recording; neither you nor the students know what was buried.

What comes first is done. At the close of each day the bags were counted against the field log, and the bags were sealed and signed into the laboratory: 31 bags over the three days, by the field log. The register shows field numbers F-001 to F-031 issued, none voided, and the paper forms were counted against it: 31 forms. The paper forms are the record. They were scanned, and then one student typed them into one file; the file as the student handed it over is kept unchanged, with the student’s name. Tomorrow you and a colleague check that typed file against the forms and the bags, entry by entry, and on Monday the students begin the laboratory inventory.

Before tomorrow’s check you want to know: how many entries each element and side has, which elements on the project’s list have no entry, which field numbers issued from the register have no entry, and which entries to look at first, because they break the project’s recording rule or repeat an element and side already recorded. Today that means reading the typed list by eye.

By the end of this lesson you will have a small program on your own computer that reads the typed inventory and makes that list, on screen and as a file your spreadsheet program opens. It tallies entries and lists what needs a look. It cannot catch an entry that follows the rule but is wrong, such as an L typed for an R, or B2 for B3: that is what tomorrow’s check against the forms and bags is for. 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
  • Element: a named bone, such as femur or clavicle, as the project’s list names it.
  • Side: L (left) or R (right) for an element the project’s list marks as taking a side. In this project, “indeterminate” is a side the recorders wrote down on purpose, when they could not tell; a blank means nothing was written.
  • Portion: how much of the element the item is, in this project’s own words: whole, proximal, distal, shaft or fragment, as its recording sheet uses them. It is the recorders’ reading in the field, until someone looks at the item in the laboratory.
  • Field number: the number given to each item from the field-number register (the list of numbers issued), written on its bag and its form.
  • Grid unit: the one-metre square, A1 to D4, the item came from.
  • Entry: one row of the typed inventory, one recorded item. A tally here is a count of entries.
  • Recording rule: what every entry must carry, and what each column may hold, under this practice project’s own procedure (in the conversation below). Your laboratory’s procedure is the one that governs.

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/21-field-inventory && cd ~/bio-workbench/21-field-inventory

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/21/field-inventory.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), four files are in the data folder (inventory.csv, elements.csv, allowed.csv and register.csv, CSV files: plain tables a spreadsheet program opens), 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 field-inventory.zip in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “field-inventory.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 field-inventory.zipclick to expand

Four files, each of which opens in a spreadsheet program:

  • inventory.csv: the typed field inventory, 31 entries, one per recorded item. Columns: field_no, date_recorded, grid_unit, element, side (L, R, indeterminate, or blank for an element that takes none), portion, pieces (how many pieces are in the bag) and recorded_by (the pair of students).
  • register.csv: the field numbers issued from the field-number register, F-001 to F-031, one per row.
  • allowed.csv: the project’s own list of what four columns of the inventory may hold, one value per row:
ColumnAllowed values
date_recorded2026-11-03, 2026-11-04, 2026-11-05 (the days of the exercise)
grid_unitA1 to D4, the sixteen units of the grid
portionwhole, proximal, distal, shaft, fragment
recorded_byJM/RT, KO/LP
  • elements.csv: the project’s own list of element names, sixteen of them, each marked yes or no for whether it takes a side.
ElementTakes a side
cranium, mandible, sternum, sacrumno
clavicle, scapula, humerus, radius, ulna, os coxae, femur, patella, tibia, fibula, talus, calcaneusyes

The list is short for practice: it has no teeth, vertebrae, ribs, or hand and foot bones other than the talus and calcaneus.

Everything in these files is made up for this course: the field school, the teaching site, the students, every field number and every entry, which stand for replica material, not human remains. 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 lead our lab's inventory after the field school's mock recovery. From the files in data, build a small program that tallies the entries by element and side and lists what needs a look. Ask me what you need first.

Your AI tool usually reads the files and comes back with questions. It may already point out some of what it sees. Leave its questions for now: send the four rule 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 four messages are sent.

Give it your rules

These are this practice project’s own rules. Your laboratory’s are in its own written procedures; use those.

Recording rule: every entry needs a field number used once, a date, a grid unit, an element from elements.csv, a side (L, R or indeterminate) if it takes one, the portion, pieces and recorders. List any entry that breaks it.

That message counts a blank side as a break and “indeterminate” as allowed, because in this project “indeterminate” was written on purpose and a blank was not.

Wait for its reply, then send the rest of the rule, which points at the project’s lists:

Values must also be allowed: dates, grid units, portions and recorders as listed in allowed.csv, pieces a whole number, and no side for an element that takes none. Also list every field number in register.csv that has no entry.

A value can be written and still not be one the project allows, such as a day outside the exercise. A field number issued from the register with no entry may be a bag that was never typed or a number typed wrong elsewhere; the register, the forms and the bags show which.

Wait for its reply, then send the rule about repeats:

List every element and side recorded more than once, with each entry's field number, grid unit and portion. In the spreadsheet file, leave a blank column for what the form and the bag show.

The blank column is for tomorrow’s check: you write in it what the form and the bag show for each entry.

Wait for its reply, then send the last rule message:

Call each tally a count of entries. Don't give a number of individuals, don't say two entries are or aren't the same bone, and never call the inventory complete.

This last message is part of this practice project’s procedure, as yours may be: the list counts entries, and anything about individuals or bones is decided elsewhere.

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
Count entries, add up the pieces, or both?Count entries only. Don’t add up the pieces; show each entry’s pieces beside it.
Is “indeterminate” an accepted side?Yes, our rule allows it. A blank side breaks the rule.
Is the recovery meant to be one individual?We don’t know, and it isn’t for this list to say. Just list the repeats.
Are the list files the rules, or only a guide?They are our rules. Flag what breaks them and keep the original values.
Correct anything, or add a column of suggested fixes?Flag only. No suggested fixes.
“Humerous”: flag it, or count it as a humerus?Flag it as written. Don’t count it as a humerus.
Should 0 pieces count as valid?No. Zero pieces breaks the rule.
Put the blank column on the rule-breaks file too?Yes, put it there too.
A program in the terminal, with files a spreadsheet opens?A list on screen and files my spreadsheet program opens.
One spreadsheet workbook, or separate files?Plain CSV files, one for each table, so it needs nothing added.
Who reads the list?Me and a colleague, for tomorrow’s check.

If it asks several questions at once, answer the ones about your rules and how entries are counted from your laboratory’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.

Wait for its reply, then say what the list must show, in a message of its own:

Tally every entry as recorded and correct nothing. Show every element and side on our list, saying no entry recorded where there is none. Make it a program I can run again, and leave my files as they are.

Your AI tool may offer, before it has the last rule message, to say whether a repeat could be a second individual or whether two pieces could belong to one bone. That message rules it out; if it still offers, say: “No. List the repeats only, and say nothing about individuals or bones.”

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 entry is read and tallied as recorded. Nothing is corrected, merged or dropped: “humerous” stays as written and is not counted as a humerus.
  2. Every element and side on the project’s list is shown with its count of entries, those with none shown as having no entry recorded. An entry whose side is blank or indeterminate, or whose element is not on the list, is not counted as left or right; it has a row of its own, so the tally’s counts add up to every entry.
  3. Every entry that breaks the recording rule is listed with its reason, including a value not on the project’s lists: dates, grid units, portions and recorders are checked against allowed.csv, pieces as a whole number, and no side for an element that takes none. Every field number in the register with no entry is listed.
  4. Every element and side recorded more than once is listed with each entry’s field number, grid unit and portion, and the spreadsheet file has a blank column for what the form and the bag show.
  5. Each tally is called a count of entries. Nothing gives a number of individuals, says two entries are or are not the same bone, or calls the inventory complete.
  6. It is a program you can run again on the next inventory, and your files are read and left as they are.

A first plan often leaves one of these out. Say so in a sentence, in your own words. If it plans a spreadsheet workbook that needs something added to your computer, say, for example:

Use plain CSV files, one for each table, so it needs nothing added.

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 details may be only in the spreadsheet file, not on screen. Check it for these:

  • There are 31 entries, field numbers F-001 to F-030, with F-020 on two of them.
  • The left femur has 3 entries, the right humerus 2 and the cranium 2; every other element and side with an entry has 1.
  • The sternum, the right talus, the left calcaneus and the left fibula show as having no entry recorded, not as missing or absent.
  • The tally’s counts add up to 31: F-019, F-022 and F-027 each have a row of their own, apart from left and right.
  • F-019, a fibula recorded as side indeterminate, is not counted as left or right, and is not listed as breaking the rule.
  • The repeats are listed with each entry’s field number, grid unit and portion: left femur F-008 (proximal, B2), F-009 (distal, B3) and F-030 (whole, D4); right humerus F-014 and F-028 (both whole, both C2); cranium F-001 (whole, A1) and F-023 (fragment, 4 pieces, C4).
  • F-022, a clavicle, needs a look: it takes a side and has none. It is not counted as left or right.
  • F-026, a right tibia, needs a look: it has no grid unit.
  • F-027 needs a look: “humerous” is not on the project’s list. It is not counted as a humerus, so the left humerus still has 1 entry, F-005.
  • F-029, a left scapula, needs a look: its portion is blank.
  • F-020 needs a look: it is the field number of two entries, a right radius from B1 on 4 November and a left patella from D2 on 5 November.
  • F-012, a sacrum, needs a look: its date, 2026-11-14, is not a day of the exercise. It is still counted as the sacrum’s entry.
  • F-016, a right femur, needs a look: its portion, “midshaft”, is not on the project’s list. It is still counted as the right femur’s entry.
  • F-031 is listed as a field number issued in the register with no entry.
  • That is 15 entries needing a look in all (the 8 that break the rule and the 7 repeat entries), and one field number, F-031, with no entry. F-020 is the field number of two of the 8, so the lines above name seven field numbers for them.
  • No line gives a number of individuals, says two entries are or are not the same bone, or calls the inventory complete. If the list shows the largest tally, it says it is a count of entries.
  • When you ask “Have my data files changed since the checkpoint?”, it compares them 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: “The left humerus shows 2. Humerous isn’t on our list; list it as written and don’t count it as a humerus.”

Count the entries yourself. Your AI tool may give a total in passing, before it has built anything, and that total may not match the file. If a line or reply fails the check about individuals above, say: “Take that off. A tally is a count of entries, and the list says nothing about individuals or bones.” Your AI tool may also say that once “humerous” is corrected to humerus, the left humerus becomes a repeat. The file does not say what F-027 is; whoever has its form and its bag does.

Notice what a tally counts

Look at the three left femur entries on your list: F-008, a proximal portion from B2; F-009, a distal portion from B3; and F-030, whole, from D4. It is tempting to read the portions and work out from them how many left femora are in the bags. Before you do, try this:

Make a copy of the inventory in this folder. In the copy only, change F-009's portion from distal to proximal. Then show me the left femur tally from the copy beside the original.

Before you read on: the copy now has two proximal portions of a left femur where the original had a proximal and a distal one. What do you expect the tally to do?

It stays at 3. A tally counts entries, so it leaves out the columns that bear on whether two entries could be one bone, the portion and the grid unit, and the portion is itself the recorders’ reading in the field until someone looks at the items in the laboratory. Whether F-008 and F-009 could be one bone is a question for the bench, with the items in hand, not for the list. An element recorded only once says no more: one entry for the right femur does not show that one individual is represented. When you have looked, remove the copy: “Delete that copy; I’m done with it.”

Each repeat on the list is a question for someone with something the list does not have:

  • F-014 and F-028, two whole right humeri, both from C2, recorded on 4 and 5 November by different pairs. The forms and the bags show whether there are two items or one item entered twice. If there are two, anything further is a question for the bench.
  • F-001 and F-023, the cranium entries, whole from A1 and a fragment entry of 4 pieces from C4: for the bench.
  • The three left femur entries: for the bench to decide.

The other entries on the list go back to the paper. Take F-026 first, to its form and its bag label: the typed copy has no grid unit for it, and the form or the bag label may. Then F-020’s two entries to the forms, the bag labels and the field-number register; F-027, “humerous”, to whoever has its form and its bag, who says what was meant; F-022’s missing side, F-029’s missing portion, F-012’s date and F-016’s portion to the forms; F-031, issued with no entry, to the register, the bag labels and the forms. None of them is corrected in the typed file until the form or the bag says what it should be. The typed file’s 31 entries and the field log’s 31 bags agree in number; that does not show that each entry matches its bag, which is what tomorrow’s check is for. The list already shows why: F-020 is on two entries and F-031 on none.

In a typed inventory, an element and side recorded more than once is a question about the record, not a finding about the remains: how many items there are is checked against the forms and the bags, and whether items are one bone or several, and how many individuals are represented, are for whoever your laboratory’s procedures name to determine, never for a list.

In this exercise those questions go to the students’ laboratory inventory, checked against the director’s sealed burial record afterwards. In a real recovery, who decides is set by your laboratory’s procedures; check which record holds that decision.

One real run

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

The tally is the same, 3 entries, because it counts entries by element and side, and portion isn't part of that.

The entries it talks about are made up for this course.

How real inventories differ

The practice files are short and tidy, and they stand for replica material. A real recovery’s inventory may carry more. Check what yours holds.

  • A bag may hold many pieces, and bag numbers may be kept apart from field numbers. Check how your laboratory links the bag, the field number and the form.
  • Real entries may include fragments not identified to any element, entries marked as possible or with a question mark beside the side, and items recorded as indeterminate or not human. Check how your procedure records each, so the program lists them rather than drops them.
  • An inventory typed into a sheet that accepts only values from the project’s lists cannot hold a misspelling such as “humerous”. Check how yours is typed and who checks the typing.
  • Your forms may carry depth or coordinates, the layer or level, features, photo numbers, notes on condition, and a second person’s check, none of which is in these files.
  • Your laboratory’s element list may number teeth, vertebrae, ribs, and hand and foot bones as well as side them, and its portion words may be far finer than whole, proximal, distal, shaft and fragment. Its own list and portion words go into the program in place of these.
  • Items may be re-bagged or moved between bags in the laboratory. Check how your record shows that before an entry is matched to a bag.
  • In this practice project the typed file is a copy of the forms. Check which record your own laboratory’s procedures treat as the record, and who signs the reconciliation. The program’s list is a place to start that check, not a sign-off.

Keep going

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

  1. “Sort the needs-a-look list by grid unit, then by field number.” Tomorrow’s check goes unit by unit through the bags.
  2. “Does the program name any field number or element 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 inventory it would get them wrong.
  3. “Save a checkpoint.” Your AI tool saves a snapshot you can return to.

When you want to check a real inventory, use the finished program. It runs on your 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 recovery never go to your AI tool: not the typed inventory, not a form, not a single row. Whether they may go anywhere else is set by your laboratory’s policy, its custody procedures and any agreement that covers the recovery. Your laboratory’s typed inventory may not be shaped like the practice one; check its columns 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 files:

  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. Go on only if the people who decide allow this use.

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

  3. Ask your AI tool for a blank inventory and copies of the three list files (elements, allowed values, register) in that folder, and to show the program working:

    Make a blank inventory with the same columns and one made-up entry, and copies of the three list files, in ~/inventory-checks, that my spreadsheet opens. Keep the program and its checkpoints here. Run the program on them and show me.

    Look at what it shows: one made-up entry, tallied. If your laboratory’s inventory has other column names, tell your AI tool those names, with two rows you make up in the same shape, never real rows, and ask it to read files like that.

  4. Give the program your laboratory’s own recording rule in place of this practice project’s. Put your own where this example has its made-up ones:

    Use our recording rule instead of the practice one: every entry also needs a bag number and a photo number, and side may be L, R, ?L, ?R or indeterminate. Update the files in ~/inventory-checks to match.

    Wait for its reply, then:

    Make up one entry that breaks each of my rules and show me the list.

    Check that each made-up entry is listed with the reason for the rule it breaks. Your laboratory’s element list and its allowed values for each column are procedure, not records: open the two copies in the inventory-checks folder in your spreadsheet program, put yours in their place, and save them. A real recovery’s register of issued field numbers is one of its records, so it goes in only at step 7, with the inventory; for now, put three made-up field numbers in the register copy, written the way your project writes them, and save it. Then send “Make up one entry that breaks each of my rules and show me the list.” again. Check that each made-up entry is still listed with the reason for the rule it breaks, and that each made-up field number no entry uses is listed as issued with no entry.

  5. Ask your AI tool for the exact line:

    Write me the exact line to run this myself on an inventory in a folder called inventory-checks 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
    cd /home/dana/inventory-checks && python3 /home/dana/bio-workbench/21-field-inventory/inventory_report.py /home/dana/inventory-checks

    Read it left to right. cd and the folder after it go into the folder that holds your inventory and lists, and && means “then”. python3 runs a Python program. Next comes the program your AI tool wrote, in this lesson’s folder; last comes the folder whose files it reads. This example line uses that folder for what the program writes; the check on the made-up files just below is what shows where the files land on your own computer, perhaps in a folder of their own inside it. /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 the files must keep, and what the program does if the list’s files from an earlier run are already in that folder (it may stop rather than replace them), and note that too. 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 files, because a real inventory must never end up in the course folder: “Run that line on the made-up files in ~/inventory-checks. Did the list land there, and did running it change anything in this folder?” Look for it saying the list’s files are in inventory-checks and nothing in this lesson’s folder changed. If the list 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. First remove the made-up entries and the list’s files made from them, or have your AI tool do it before you leave it in step 6, while only made-up data is there. Put your inventory and your register’s list of issued field numbers in that folder in place of the blank inventory and the copied register, named as your AI tool said. 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 with mkdir.

  8. Before you use the list on a new inventory, run it on a past inventory you have already reconciled yourself, and compare every entry it lists with what you found. If they differ, find out why first. Keep a written record of that comparison, and check whether your laboratory’s procedures require more before a program like this is used on its records.

Try another case

Before the quiz, write two or three sentences for yourself. On Friday afternoon a student looks at your list and says: “Left femur, three. So there are three people in the bags.” What would you say?

A good answer says the 3 counts entries in the typed file, not femora and not individuals: two of those entries are a proximal and a distal portion, and whether they are one bone is for the bench; the portions are the students’ reading until the items are examined. It sends the question to the laboratory inventory, where the bones are examined under the laboratory’s procedures, and it does not offer a different number instead.

Key takeaways

  • A short ask, then your rules. Say what you do and which files; give your project’s recording rule in its own words.
  • Read the plan for what is tallied and listed: every entry as recorded, nothing corrected, every broken rule and every repeat listed, no count of individuals.
  • Check a new list against values you know before you trust it on an inventory you do not.
  • A tally counts entries. A repeat is checked against the forms and the bags; whether items are one bone, and how many individuals there are, is for whoever your procedures name, never for a list.
  • Practice data stays practice data: real inventories go to the finished program, with your AI tool closed, after the data check.
KNOWLEDGE CHECK

In a typed inventory, the right humerus has two entries: both whole, both from grid unit C2, recorded on different days by different pairs of students. What does the tally of 2 tell you?

What’s next

The next lesson is about checking a week of a core facility’s instrument bookings for clashes, bookings over maintenance and users not on the trained list.

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