Applied AI-Powered Bioinformatics Tools

Mass Spectrometry Data Viewer

Last reviewed

Advanced

What you'll learn

~50 min
  • Ask an AI tool, in plan mode, for a page that draws one spectrum exported as a table of mass-to-charge (m/z) and intensity, with the peak list your instrument's software produced for it marked on the trace, zoom, and a table of the called peaks, made from the two files as they are
  • Read its plan for what matters: the trace drawn from every exported point, each peak marked where the list puts it, every column of the list shown as written, no peak found or measured by the page, and the page made again from other files in one step
  • Check the page against values worked out for the practice files, including the difference in m/z between two peaks you pick and the count of called peaks in the range on screen
  • See, by zooming into your own page, a feature the eye finds and the peak list lacks, and noise that looks like a row of peaks, and know who decides what either is

The story, and what you will end up with

It is Thursday 19 November 2026 at a university mass spectrometry core facility that runs samples for other labs. You are a staff scientist there: you run the instrument, and you sit with users to go through their spectra. Last week the facility ran one sample for a graduate student in a client lab. The facility’s mass spectrometrist processed it and sent the student and the lab’s PI the data files and a short report with a picture of the spectrum.

This morning the student emailed. They had zoomed into the picture in the report: “There’s a small peak just to the right of the tallest one, and your peak list leaves it out. That must be my product, so the reaction worked.” Tomorrow at ten the student and the PI meet you and the mass spectrometrist to look at the data together.

Some of the work for that meeting is already done. The mass spectrometrist has the processing record: which software and version produced the peak list, with which settings, and the day’s calibration record with its mass error. They have checked that the report’s picture was drawn from this scan, and whether it is a single scan or an average of several. They have asked the student for the expected formula, the ion polarity and the adducts and charges the student expects, and they will bring the neighbouring scans and the blank run to the meeting. The mass spectrometrist works out where the student’s expected ions would fall and compares that with the data before the meeting; your page does not. You know how the picture in the report was made. And you have agreed with the mass spectrometrist that they speak for what the data show, and that nothing gets called an identification in the room.

For the meeting the mass spectrometrist exported two small files from the scan the report shows: the spectrum, the part of the scan from m/z 640 to 680, as a table of m/z and intensity, and the rows of the peak list the instrument’s software produced for that scan that fall in the same range. The instrument’s own data file stays the record of the scan; the two exports are copies made from it, and the mass spectrometrist has noted how they were exported.

By the end of this lesson you will have a page on your own computer that draws that spectrum as a trace, marks the peaks the software called on it, zooms, and shows the called peaks in a table with everything the software reported for each. It finds no peaks and measures nothing: it draws the exported points, marks where the peak list puts each peak, and does two pieces of plain arithmetic, the difference in m/z between two peaks you pick and a count of called peaks in the range on screen. It runs with no internet connection and sends nothing anywhere, and it is made from the two files as they are, so you can make it again from another scan’s files yourself. 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
  • m/z: mass-to-charge, the position along a spectrum’s horizontal axis. A tutorial review in the Journal of Mass Spectrometry, Understanding Mass Spectrometry: From Ion Generation to Spectral Interpretation (read 12 November 2026), says: “m/z denotes the dimensionless quantity obtained by dividing the ion mass (expressed in unified atomic mass units, u) by the absolute value of its charge number z”.
  • Exported spectrum: here, a table with one row for each point the instrument’s software wrote out, an m/z and an intensity. Drawn as a line, it is the trace.
  • Peak list: the table of peaks the instrument’s software called in that spectrum under its settings, one row for each, with the m/z and other figures it reported.
  • Called peak: a peak that is in the peak list. A bump in the trace that is not in the list is not called, whatever it looks like.
  • Profile and centroid: a profile spectrum keeps the shape of each peak as many points; a centroid spectrum keeps one m/z and one intensity for each peak. The same review says: “mass spectra can be represented either as profile data (full peak shapes, as exemplified in Figure 6) or as centroided data, in which each peak is reduced to a single m/z–intensity pair.” The practice spectrum is profile; the peak list is the software’s reduction of it to one row per peak.

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/04-spectrum-viewer && cd ~/bio-workbench/04-spectrum-viewer

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/04/mass-spec-files.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), two files are in the data folder (spectrum.csv and peak-list.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 mass-spec-files.zip in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “mass-spec-files.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 mass-spec-files.zipclick to expand

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

  • spectrum.csv: the columns mz and intensity, 4,001 rows, one every 0.01 from m/z 640.00 to 680.00. The data is simplified on purpose: its points are evenly spaced, its peaks are all one width, and the intensity is in no stated unit. Check how your own exports differ.
  • peak-list.csv: 13 rows, P01 to P13, with the columns peak, mz (four decimal places), intensity, relative_intensity (a percentage of P08’s intensity, the tallest peak in these rows; the file does not say whether P08 is the tallest in the whole scan), resolution, signal_to_noise and charge. Every value is the made-up software’s own figure; the file does not say whether its intensity is a peak’s height or its area. P12 and P13 have no charge: the cell is empty.
PeakP01P02P03P04P05P06P07P08P09P10P11P12P13
m/z645.3210645.8227646.3244648.4472652.8840653.8874654.8907661.8476662.3493662.8510663.3526667.2533671.4021
Charge22211112222(empty)(empty)

Everything in these files is made up for this course: the spectrum, the peak list and every number in them; no instrument, sample or real software produced them, and no compound is behind 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 to see:

I run the instrument at our mass spec core and go through spectra with users. Build an offline browser page drawing the data folder's spectrum, its peak list marked, zoomable, with a peak table. Ask me what you need first.

Your AI tool usually reads the files and comes back with questions. It may already say that the spectrum is profile data, that two peaks have no charge, or that some peaks look like groups.

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
One page with these files built in, or a button to open your own?Show the files in the data folder at start, with a button to open other files like them.
Is the spectrum profile or centroid data?The spectrum file is profile; the peak list is the software’s, one row per peak.
Will other files have the same columns? Tab-separated, or centroid only?Same columns, comma-separated, one scan at a time.
How should peaks show? Group or colour the ones that look like clusters?Mark each called peak with its ID at the m/z the list gives. No grouping or colouring.
Should markers sit at the listed intensity or on the drawn trace?On the drawn trace, at the m/z the list gives. The table shows the list’s intensity.
How should zoom work? Click a table row to go to that peak?Drag to zoom, double-click to reset, click a table row to zoom to that peak.
Intensity as written, as a percentage of the tallest peak, or both?Intensity as written in the file.
Which columns in the table? Add a calculated one, such as a mass worked out from m/z and charge?All columns as written, sortable, blanks left blank. Add nothing calculated.
Show a missing charge as a dash, or work it out?Leave a missing charge blank, as the file does. Work nothing out.
Export, a facility name, other extras?No export, no branding, nothing else for now.
Where will it be used, and in which browser?On my computer when I sit with users, in a current browser, with no internet.

If it asks several questions at once, answer the ones about how peaks are marked and what the table shows, a sentence each, and accept its suggestions only about how the page looks. If you cannot tell which kind a question is, answer it yourself. If it offers to group peaks, work out masses or charges, or find, smooth or measure anything in the spectrum, say no: the page shows what the software reported and nothing more. If it asks something not listed here, answer it the same way, in a sentence. If it did not ask about each of these (how the trace is drawn, where peaks are marked, what the table shows, and whether the page finds, smooths or measures anything), send this after your answers:

Draw every point in the spectrum file as written. Mark each listed peak at its m/z and show every column as written, blanks blank. Find, smooth or measure nothing.

If your AI tool already shows a plan or a choice to approve one, do not approve it until you have sent the next two messages.

Wait for its reply, then ask for the two pieces of arithmetic the page does in a message of its own:

Also let me pick two peaks and see the difference between their listed m/z values, and show how many called peaks are in the range on screen.

Wait for its reply, then say how the page is to be made in a message of its own, because you will use it on other scans:

Don't type anything from the files into the page. Build it from the two files as they are, show their names, and let me remake it from two other files with the same columns in one step, without you.

Wait for its reply, then read the plan.

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. The trace is drawn from every point in the spectrum file, as written: nothing smoothed, corrected or left out.
  2. Each called peak is marked at the m/z the peak list gives, and the table shows every column of the list as written, with an empty cell left empty.
  3. The page finds no peaks and measures nothing: no peak finding, no widths, no signal-to-noise, no charges or masses worked out. Everything about a peak comes from the list.
  4. You can pick two peaks and see the difference in their m/z, from the list’s values, and the page shows how many called peaks are in the range on screen.
  5. It works with no internet connection, and your files are read and left as they are.
  6. The page is made from the two files as they are: nothing from them typed into the page by your AI tool, both file names shown on it, and making it again from two other files with the same columns is one step you can take yourself, with your AI tool closed.

A first plan often leaves one of these out. Say so in a sentence, in your own words, for example:

Update the count of called peaks in view whenever I zoom or reset.

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 test what it built and tell you how to open it. 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 open the page:

Open the page in my browser.

Your AI tool may open the page for you. A page opened straight from a file cannot read other files by itself, so the program your AI tool writes may copy the two files into the page each time it makes the page; that is what lets you make it again from other files in one step. If it gives you a file location or an address without opening it, copy that into your browser’s address bar and press Enter, or ask your AI tool to open it for you. On Windows, the folder is inside Ubuntu, so ask your AI tool: “How do I open this page in my Windows browser?” 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. If the page says it cannot load the files, tell your AI tool what the page says. When you have finished with the page, ask: “Stop the spectrum page if it is still running.” Your page will be laid out in its own way, and may zoom by dragging, by scrolling or with buttons.

Check it for these:

  • The page shows the names of the two files it was made from, spectrum.csv and peak-list.csv.
  • The trace runs from m/z 640 to 680, and its tallest point is at m/z 661.85.
  • There are 13 called peaks, P01 to P13, each marked at the m/z the list gives. P08 sits at 661.8476, a little to the left of the trace’s tallest point, which is one of the exported points; the list’s m/z falls between two of them.
  • The table shows all seven columns of the list as written. P08’s intensity is 1,028,500, the list’s figure, not the 993,871 of the trace’s tallest point. P12 and P13 show no charge: an empty cell, not 0.
  • Picking P08 and P09 shows a difference of 0.5017; picking P05 and P06 shows 1.0034. Your page may show the difference with a minus sign, −0.5017, depending on the order you picked the peaks in; either is fine as long as the size is 0.5017.
  • With the whole spectrum on screen the page counts 13 called peaks in view. Zoomed to m/z 661.5 to 662.5, it counts 2, P08 and P09. If you cannot set that exact range, any view that keeps P08 and P09 and leaves out P07 and P10 counts 2.
  • When you ask “Does the page load anything from the internet, or send anything? Show me where. And have my files changed since the checkpoint?”, it says the page loads nothing from the internet and sends nothing, shows you where it looked, and compares your files with the checkpoint and says they have not changed.

If something on the list is not true, tell your AI tool in a sentence what you see and what you expected, for example: “P12 shows a charge of 0. The list leaves that cell empty; show it empty.”

Notice what the picture cannot say

Zoom the page to m/z 661.5 to 662.5, around the tallest peak. You should see three bumps: P08, marked; a much smaller one just to its right, not marked; and P09, marked. The page counts two called peaks in that range; if you cannot set that exact range, any view that keeps P08 and P09 and leaves out P07 and P10 counts 2. That small bump is the one the student wrote about. Now ask your AI tool:

Don't change anything. In the spectrum file between 661.95 and 662.10, what is the highest point, and does the peak list have any peak there?

Before you read on: the page marks only what the list holds. What do you expect the answer to be?

The highest point there is at m/z 662.02, intensity 32,812, about a thirtieth of the tallest point in the file (993,871 at 661.85). The peak list has nothing between 661.95 and 662.10. So something is in the exported data there, and the software did not call it. These files cannot tell you why. Your AI tool may offer a reason of its own, for example by comparing the bump with the peaks the list does have; that is not for your AI tool to settle. It is the mass spectrometrist’s question, answered from the processing settings, the neighbouring scans and the blank run, not from the picture.

Now zoom the page to m/z 675 to 679, a stretch with no called peaks; the page counts 0. Look at the intensity axis. If its top came down when you zoomed, the trace fills the picture with bumps that look like a row of peaks. If its top stayed the same, ask your AI tool to fit the intensity axis to the range on screen, and look again. The highest point in that stretch is 1,596, under a five-hundredth of the tallest point in the file. Zoomed far enough, a stretch with no called peaks can look like a row of peaks; the intensity axis shows how small it is, but only if you read it.

A peak marked from a peak list is the software’s call under its settings, not an identification: what a feature in a spectrum is, and what the facility reports about it, are for its staff to judge under its procedures, and the scientific claim is the user’s to make, from more than a picture.

So at the meeting the page is for looking together, not for deciding. Plain words help in the room: “There is a feature near m/z 662.0 in this scan that is not in the peak list. What it is has not been assessed.” What these two files do not show, called or not, is a structure, which of several isomers is present, how much product there is, or whether the reaction worked. The mass spectrometrist answers the student and the PI from the full record, and the facility’s written report, not the page, records what was and was not concluded.

When you picked P08 and P09, the page showed a difference of 0.5017, and the list gives both a charge of 2. The page did not work out the charge; it only subtracted the two listed m/z values. The charge is the software’s assignment, and the difference’s four decimal places come from the list, not from the instrument’s accuracy.

A tutorial review in the Journal of Mass Spectrometry, Understanding Mass Spectrometry: From Ion Generation to Spectral Interpretation (read 11 November 2026), says of the isotope peaks of a simple organic compound: “As a result, adjacent peaks are typically separated by approximately 1.003 Da, corresponding to the mass difference between 13C and 12C. Because the x‐axis in a mass spectrum corresponds to m/z rather than neutral mass, this spacing scales with charge state; for an ion with charge z, the observed spacing is: d≈1.003/z”.

On the practice list the arithmetic is plain: P09 minus P08 is 0.5017, P06 minus P05 is 1.0034, and half of 1.0034 is 0.5017. The small bump’s highest point, 662.02, is 0.1724 above P08’s m/z, though that compares one exported point with a figure from the list. What a spacing means for a bump the list does not hold, that one or a row of even bumps elsewhere, is for the mass spectrometrist to say.

One real run

Here is what one AI tool said after the question above, with Codex on 12 November 2026. Yours will word it differently; check your page against the list above, not against this.

Between 661.95 and 662.10 m/z, inclusive, the highest spectrum point is
662.02 m/z, with intensity 32,812.
The peak list has no called peak in that interval.
No files were changed.

The spectrum and peak list it talks about are made up for this course.

How real data differs

  • Check how tidy your export is. Look for header lines with the scan number, retention time, polarity and settings; points unevenly spaced, with stretches of zero intensity left out; numbers with decimal commas or in scientific notation; intensity in the instrument’s own units. Tell your AI tool what yours looks like, with made-up numbers, before you use the page on it.
  • Profile or centroid. Ask whoever exported the file whether it keeps each peak’s shape as many points or one point per peak, and compare the page with the instrument’s own picture before you rely on it.
  • A peak list says what the software reported, under its settings. Check that software’s documentation and your facility’s processing record for which figures the list gives and how each is worked out, such as whether its intensity is a height or an area and how it states resolution. The page shows the figures; it does not explain them.
  • Check how your list writes no charge: an empty cell, as here, or a 0. Make sure the page does not show a 0 that means “not assigned” as if it were a charge.
  • Check what your scans cover. See what range your scans span, and whether a file is the whole scan or an excerpt; if it is an excerpt, say so on the page, and check what the list’s relative intensity is relative to. Your real scans may have no stretch as empty as m/z 675 to 679 here.
  • Check how much your page draws. If your export is much larger than the practice file, ask your AI tool whether the page draws every point, and have the page say so.

Keep going

Small changes do not need plan mode. Say each in a sentence, then look at the page again:

  1. “Print the file names and the m/z range shown on the picture, so a saved image says what it is.”
  2. “Save a checkpoint.” Your AI tool saves a snapshot you can return to.

When you want to look at a real scan, use the finished page: make it again from that scan’s two exports. Making it and looking at it happen on your computer by themselves, with your AI tool closed, so your AI tool never sees the files. A user’s data is that user’s lab’s. Nothing confidential or unpublished, and nothing about people or about animals under a protocol, goes to your AI tool or into this course folder; nor does data covered by an agreement or from human samples. Check whether your instrument’s exports have the same columns and layout as the practice files. Do these steps in order; the first four 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. Your facility’s procedures say whose agreement you need before a lab’s unpublished results, data under an agreement or data from human samples are used this way. Go on only if they allow this use.

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

  3. Export one spectrum as a table and its peak list from your instrument’s software, and open each in your spreadsheet program yourself, on the instrument’s computer or wherever your facility’s procedures let you; your AI tool does not see these files. Tell your AI tool the column names and anything above the column names (such as lines giving the scan number), with two rows you make up in the same shape, made-up numbers, never a real row. For example: “My spectrum export has two header lines, then the columns Mass and Intens. Here are two made-up rows in the same shape. Make the page read files like that.” Then paste the two rows you made up. Wait for its reply, then do the same for your peak list, saying which column holds a peak’s m/z and which its label, for example: “My peak list export has the columns ID, Centroid, Abundance and Z. Centroid holds each peak’s m/z and ID its label. Here are two made-up rows in the same shape. Make the page read files like that.” Then paste those two made-up rows. Your AI tool may ask for the first lines of a real export. Make up lines in the same layout instead, header lines included, and say whether those lines change from one export to the next. Share only the layout, with made-up numbers; if your facility treats column names or header lines as confidential, ask whoever is responsible first, or make up equivalents. Whoever exports spectra at your facility can make up the rows for you. Look for it saying it has changed what makes the page so it reads files like that, and that files like the practice ones still work. Then ask: “Put a made-up spectrum file and peak list in that layout in ~/spectra, make the page from them, and show it to me.” Use your own folder’s name.

  4. Ask your AI tool for the exact line, for example: “Write me the exact line to make the page myself from a spectrum file and a peak list in ~/spectra, with full paths, saving the page 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/04-spectrum-viewer/build_viewer.py "/home/dana/spectra/SPECTRUM.csv" "/home/dana/spectra/PEAKLIST.csv" -o "/home/dana/spectra/viewer.html"

    Read it left to right: python3 runs a Python program, first the one your AI tool wrote in this lesson’s folder, which makes the page; then the spectrum export and the peak list, both in spectra, spectrum first, where SPECTRUM.csv and PEAKLIST.csv stand for your two files’ names; last, -o and the name after it say where the page is written, here beside your files, so the page in this lesson’s folder is left as it is. 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 quotation marks keep each name in one piece if it has a space in 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 runs the program where it is, so leave this lesson’s folder in place. On Windows, this lesson’s folder is inside Ubuntu, so ask your AI tool now: “How do I open this page in my Windows browser, and how do I get files from my Windows folders into spectra?” 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 scan’s numbers must never end up in the course folder: “Run that line on the made-up files in ~/spectra. Did the page land there, and did running it change anything in this folder?” Look for it saying the new page is in spectra and nothing in this lesson’s folder changed. If the page landed in this lesson’s folder, tell your AI tool so and ask it for the line again.

  5. Ask your AI tool to stop anything it started for the page, then leave it the way you did at the start of this lesson.

  6. Copy a real scan’s two exports into spectra, in place of the made-up files, moving them off the instrument’s computer the way your facility’s procedures say (on Windows, the way your AI tool told you in step 4). At the $ or % prompt, paste the line from your note, put in the two files’ names, and press Enter. The page appears beside your real files, not in the course folder. Open it in your browser: copy the page’s full path from your line into the browser’s address bar and press Enter. If it will not open, start your AI tool in an empty folder and ask it how to open a page file on this computer, giving it no data. Check that the page shows the two file names you expect. The page may hold a copy of the two files’ numbers, so treat it as the user’s data, like the exports themselves. 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.

  7. Before you show the page to a user, compare it with the same scan in your instrument’s software: the m/z range, the tallest peak, and a few called peaks with their figures. If they differ, find out why first. Check, too, who your facility’s procedures say must approve a page you made before it is shown to users under the facility’s name.

Try another case

Before the quiz, write two or three sentences for yourself. Next month a user sends you a picture from your page, zoomed to a narrow stretch with no called peaks, where the trace rises in five even bumps. They write: “Five peaks the software missed. Can you add them to my peak list?” What do you check, and what do you tell them?

A good answer reads the intensity axis first, notes the bumps’ spacing on the m/z axis, and compares them with the tallest peak in the scan and with the noise elsewhere, without deciding from the picture that they are or are not peaks. It does not add anything to the list by hand: the peak list is what the software called under its settings, and whether processing again with other settings is warranted is for the mass spectrometrist under the facility’s procedures. And it tells the user plainly what the picture can and cannot show.

Key takeaways

  • Ask briefly, and let your AI tool ask back. Say what you do, which files and what you want to see; its questions fill in how peaks are marked and shown.
  • Read the plan for what the page must not do: find, smooth or measure anything. Every figure about a peak comes from the list.
  • Check a new page against numbers you know before you show it to a user.
  • What the eye finds and the list lacks is a question, not an answer. It goes to whoever knows the processing settings and the data.
  • Practice data stays practice data: real scans go to the finished page, with your AI tool closed, after the data check.
KNOWLEDGE CHECK

Your page shows a small unmarked bump beside the tallest peak. The peak list has nothing there. The user says it is their product. What is the best next step?

What’s next

The next lesson is about reading a differential expression results table and the per-sample counts behind it.

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