
Seconds of Warning
How can a few seconds of warning reach people before the shaking does, and how do we explain the waves and devices that make it possible?
The mystery: Earthquake early-warning systems can send an alert to phones a few seconds before strong shaking arrives, because the alert travels as a digital signal far faster than the slower seismic waves that do the damage.
Questions we will figure out together in this unit:
define the alert-explainer and alert-link problem with criteria and constraints, connect it to the community need it serves, and organize the class questions into need-to-knows.
Phase 1: Spark
Do Now. List every step you think happens between the ground starting to shake far away and a phone in your pocket buzzing with an alert. Number them.
Which is a constraint, not a criterion, for our classroom alert link?
Meet the client. A school district’s emergency-management office plans drills and writes safety guidance for families and staff. Families keep asking how earthquake alerts work, why they sometimes arrive after the shaking, and whether they can be trusted. The office has asked our class for two things: a clear, accurate technical explainer for families, and a working classroom demonstration of how an alert travels as a digital signal.
Driving question. How can a few seconds of warning reach people before the shaking does, and how do we explain the waves and devices that make it possible?
The alert chain. Seismic waves reach a seismometer → the ground motion becomes an electrical signal → it is digitized into bits → the bits travel over fiber-optic and radio links to processing centers → an alert is sent as radio waves to phones → the phone turns it into sound, light and vibration. Every arrow is a wave or a device that uses waves.
Our demonstration: a light-signal alert link. Teams will design a way to send a short coded alert across the room as flashes of visible light, the same idea as bits in a fiber, and test how reliably it arrives.
Our class criteria and constraints. Criteria: (1) the link sends a 16-bit alert code (location, strength, action) across at least 5 m of classroom; (2) the receiver decodes it with no uncorrected errors in 3 of 3 trials; (3) the total send time is at most 20 s; (4) the code includes at least one check (parity) bit. Constraints: (5) visible light only, from LED flashlights or a phone light (no lasers), and class materials only; (6) the receiver may be a person or a phone light-meter app, and nobody shines a light into anyone’s eyes.
Worked example 1: a 16-bit alert code. Mei’s team split 16 bits into fields: 4 bits for the region (16 possible regions), 3 bits for expected shaking (8 levels), 4 bits for the action to take, 4 bits for a message number, and 1 parity bit. With n bits you can write 2n different codes, so 4 bits give 24 = 16 regions. Designing the code is part of the engineering.
Worked example 2: who depends on it? Jamal listed the people who rely on the real system: students and staff in classrooms, hospital teams, train operators, and families at home. He wrote one sentence on what each could do in 5 seconds. Naming the need is the first part of a technical explainer.
Wonder Board and need-to-knows. Sort the class questions into What we know, What we need to know, and How we will find out (lab, data, simulation or published source). The need-to-knows become our investigation plan.
Teams and roles. Teams of four rotate weekly through Project Manager, Test Engineer, Data Analyst and Communications Lead (who keeps the explainer draft and the source list).
Work in your new team. Agree on each answer before you move on.
Write the project page of your Engineering Notebook.
Draw the alert chain from earthquake to phone. Label each step with the kind of wave or signal it uses, and circle the steps you do not yet understand.
Rank the six criteria and constraints for the alert link from most to least important to the client, and give a reason for your top two.
We have a client, a driving question and need-to-knows. Next phase, we investigate: first, waves we can see and measure on a spring.
Exit ticket: write the one need-to-know your team most needs answered before you can write the explainer, and say how you will find out.
How confident are you that you can describe the need an alert system meets and define our design problem with criteria and constraints?
Materials: the 4.01 question board, sticky notes, chart paper with three columns, role cards, an LED flashlight and a printed 16-bit code card to show the demonstration idea.
Setup: post the six alert-link criteria and constraints where every team can see them all unit; 4.07 to 4.09 test against these exact values.
Sensitivity: keep the tone calm and practical. The explainer’s audience includes families who may be anxious about earthquakes.
Listen for: “the alert predicts the earthquake”; “digital means no noise”; criteria with no number.
Support / stretch: give a blank alert-chain diagram with six boxes. Stretch: design the 16-bit code’s fields and show how many messages it can represent.