Teacher and presenter guide · Guided linear time-of-flight investigation
You need: index.html open in any modern browser, on a
projector or on each student's phone. No network, no install, no accounts. Nothing is fetched at
runtime, so it works with the wi-fi off.
One per stage, in the learner's own words — these are the four Takeaway cards on screen, verbatim. If a student can say these four things and point at the evidence for each, the demo has done its job.
An AI-built classroom tool from Part four. Its goal is to separate what a detector measures from what you may conclude, its engine is live on the device, and its assumptions are one tap away in Details. It does not depend on any earlier demo, so it can be taught on its own; the habit it shares with the rest of Part four is naming the boundary between mechanism and claim.
What does a flight time actually tell you about an ion?
| Label | Meaning in this activity |
|---|---|
| dalton (Da) | A mass unit used for atoms and molecules. |
| elementary charge (e) | +1e or +2e is positive charge. The dimensionless charge number z is 1 or 2. |
| microsecond (µs) | One millionth of a second. The detector clock and the trace's horizontal axis show real flight time in µs. |
| metre (m) | Flight-tube length. Stages 1–3 hold it at 1.50 m; stage 4 compares 1.00 m with 2.00 m. |
| kilovolt (kV) | One thousand volts. Every stage holds the boost at 20 kV. |
The screen uses one scale for every core run: 1.00 physical µs takes 160 ms on screen, or 160,000× slow motion. The detector trace keeps the same 0–18 µs horizontal axis in all three core stages, so runs can be compared by eye.
Question: Both ions carry the same single positive charge. Which one reaches the detector first, and by how much?
Predict prompt: Which packet arrives first — 100 Da or 400 Da, both at +1? Run is locked until a student commits, and the list locks once the detector has answered. Take a show of hands before anyone taps.
Activity (3 minutes): 0:00 read the two ion cards and the two fixed conditions · 0:30 commit a prediction · 0:45 press Run detector · 1:00 watch both markers cross, and read the cue line under the flight window as each arrives · 2:00 read the finding and the summed trace.
Expected observation: Ion A at 7.64 µs, Ion B at 15.27 µs; separation 7.64 µs. Exactly a factor of two, which is the square root of the four-fold mass difference.
Check-yourself answer key: "Twice as long." The tempting wrong answer is "four times as long, because it is four times the mass" — that is the linear-in-mass error, and the observed 15.27 µs refutes it directly. The third option denies mass matters at all; the two traces refute it.
Teaching limit: Do not let "lighter is faster" become "flight time measures mass." Stage 2 breaks that immediately, and stage 1 is where students build the habit of saying what was held constant.
Question: Both ions weigh 200 Da. If one carries twice the charge, what does the same voltage do to it?
Predict prompt: Two ions of 200 Da, one at +1 and one at +2 — which arrives first? This one splits a room, and the split is worth surfacing before the run.
Activity (3 minutes): 0:00 note that both cards now read 200 Da and only the charge differs · 0:30 commit · 0:45 Run detector · 1:30 read the two arrivals against the prediction echo in the Predict card.
Expected observation: Ion A (+1) at 10.80 µs, Ion B (+2) at 7.64 µs. The ratio is 1.414 — the square root of two — because the +2 ion gained twice the kinetic energy.
Check-yourself answer key: "The same voltage gave it twice the kinetic energy." The two wrong options are the ones students actually reach for: that a +2 ion is somehow lighter (both cards say 200 Da), and that the tube keeps pulling on it during flight (the tube is field-free — the whole difference was made before the clock started).
Teaching limit: The demo shows that charge changes flight time in an ideal instrument. It does not show that charge states are easy to assign in a real spectrum.
Question: Ion A is 200 Da at +1 and Ion B is 400 Da at +2. What does the detector record?
Predict prompt: Equal m/z, different mass and charge — one peak or two? Ask for the reasoning before the vote; this is the stage where the reasoning matters more than the answer.
Activity (3 minutes): 0:00 compute 200 ÷ 1 and 400 ÷ 2 together on the board · 0:45 commit · 1:00 Run detector · 2:00 look at where the two coloured centre ticks land on the trace, and at the single peak the summed signal makes.
Expected observation: Both centres at 10.80 µs. The page checks the two times for exact equality, so the readout says "coincident arrival" rather than "close".
Check-yourself answer key: "Different ions could share the same mass-to-charge ratio." The wrong option — "exactly one kind of ion must be present" — is the conclusion a real spectrum invites and this stage has just refuted. Sit on this one; it is the demo's target claim.
Teaching limit: The claim is narrow and it is the important one: a single flight time constrains m/z and nothing else. It is not the claim that real identification is impossible — only that this measurement alone cannot do it.
Question: A 1.00 m tube cannot tell 200 Da from 205 Da. Does making the tube longer fix that?
Predict prompt: Doubling the tube doubles the gap between two arrivals — is that enough to separate the peaks? Most students say yes, and under one of the two assumptions they are right, which is what makes the stage work.
Activity (5 minutes): 0:00 introduce timing width in words before naming sigma · 1:00 Run paired comparison on the fixed-width assumption and read the table · 2:30 switch to Proportional width and run it again · 4:00 compare the two separation-to-width ratios.
| Assumed width rule | 1.00 m result | 2.00 m result | What changes |
|---|---|---|---|
| Fixed σ = 0.06 µs | Separation 0.089 µs FWHM 0.141 µs ratio 0.633 · overlapping | Separation 0.179 µs FWHM 0.141 µs ratio 1.266 · resolved | Separation doubles while the absolute width stays fixed. |
| σ = 1.5% of arrival time | Separation 0.089 µs mean FWHM 0.256 µs ratio 0.350 · overlapping | Separation 0.179 µs mean FWHM 0.512 µs ratio 0.350 · overlapping | Separation and width both double; the ratio does not move. |
Check-yourself answer key: "No — it depends on how the peak width behaves." The wrong options are "a longer path always separates peaks better" (the proportional run refutes it on screen) and "doubling the tube does not change the separation" (it does — 0.089 to 0.179 µs in both runs; separation was never the problem).
Teaching limit: Both width rules are assumptions this activity declares, not measurements, and the resolution criterion is a stated classroom rule. Clearing it is not a claim that any instrument could distinguish 200 from 205 Da, nor that it could identify either.
This ideal linear TOF does not model an ion source, extraction optics, reflectron focusing, detector efficiency, calibration, fragmentation, measurement uncertainty, or molecular identification. Full per-stage assumption lists are in the app's Details drawer, which is the surface students should be sent to when they ask "but is that real?".
The four stage tabs run across the top; stages 2 and 3 unlock as the previous stage produces evidence, and stage 4 is open from the start. Details in each stage intro opens that stage's formula, assumptions and sources. ? reopens the Guide. ⚙ Settings offers Open Presenter Notes (this document), Presentation mode and Reset.
Presentation mode scales the page up one notch, widens the instrument, and adds a Notes button
to the header for these cues. Reset returns the demo to its opening state without reloading the page
— stage 1, stages 2 and 3 locked again, no predictions, no evidence — and leaves
presentation mode as you set it. Run locks the prediction during flight; Replay uses the same physical-to-screen
scale, so two runs are directly comparable. A stage can be deep-linked with #stage-4.
These sources support the underlying physics; they do not endorse this activity. A Murray State project record supports plausible course fit; it is not named here, and the demo is not presented as any instructor's instrument or assignment.
index.html to run the investigation. src/demo-guide.html is the canonical source of this document; the shipped teacher-guide.html, the PDF beside it, and the in-app presenter notes are all generated from it at build time.