A sensor produces a measurement. A useful system also needs a decision rule and a response when the reading is uncertain.
Your challenge
Build or simulate a water-level indicator for a model tank. Define the threshold and repeat tests below, near and above it.
LEARN & APPLY / 1
Know what you measure
A water-level sensor estimates level or distance. It does not establish drinking safety or water quality. Label units and explain the relationship between a reading and your model.
Try it yourself
Draw input, processing and output with the measurement units.
LEARN & APPLY / 2
Calibrate and repeat
Compare readings with known positions. Repeat trials at low, near-threshold and high levels. Record inconsistent alerts as evidence rather than deleting them.
Try it yourself
Run five trials at each of three levels, or use an equivalent simulation.
LEARN & APPLY / 3
Make failure visible
Test a missing reading and a restart. Use only facilitator-approved low-voltage equipment; keep liquids away from electronics. A simulation is a complete route through this mission.
Try it yourself
Show a failure mode, one improvement and its retest.
WHAT YOU WILL BE ABLE TO DO
Distinguish measurement variation from a decision threshold.
Record false alerts, missed alerts and missing readings.
WORKED EXAMPLE
See the thinking.
A simulated tank alert turns on at 80 cm. Record the true model level, reading, expected alert and actual alert. A true level of 82 cm with no alert is a missed alert; a true level of 72 cm with an alert is a false alert.
RETRIEVE. EXPLAIN. CHECK.
Why might an alert flicker when a reading is close to 80 cm?
Write your own answer before opening the explanation. Then improve one sentence using what you learned.
Compare your reasoning
Small variations can repeatedly cross the boundary. A possible improvement is to turn on at 80 cm and off at 75 cm, then test whether this behaviour fits the purpose. Never hide missing readings as normal results.
Stretch yourself
Test two thresholds, a missing reading and restart in a simulator. No hardware purchase is needed.
Project ideas for coding and data. Choose simulator-compatible activities; some projects require equipment.
Build it. Try it. Change one thing.What would you test when the easy example works?Illustrated learning characters · fictional sceneTEN-MINUTE FIRST TRY
Try before you read the solution.
The Builder's alert turns on at 80 and off at 75; between them it keeps its state. Starting OFF, trace 74,80,78,76,75,79,81.
Scratch space: not saved. Copy useful reasoning into your private workbook.
Choose a fictional club service, a water-data investigation, or an accessible information tool as your capstone. Keep the same problem brief through your budget, prototype, tests, revision and final defence. The crew exercises teach a method; apply that method to your chosen project and explain any adaptation. Simulation is a complete route.
THE CREW AT WORK / GUIDED PRACTICAL
Stop an alarm from flickering
60–90 minutes · Paper or browser · No purchase required
Builder
“My tank alert switches on and off near 80 cm.”
Researcher
“Keep a state. Turn on at 80, but do not turn off until the reading falls to 75.”
Illustrated learning characters. Scenarios and numbers are fictional; your human mentor reviews your evidence.
01 / PREDICT
What happens at 78 cm if the alarm was already on? What if it was off?
Write a prediction before you reveal the worked reasoning.
Your starter material
Simulated water-height readings in cm: 74,79,80,78,76,75,74. Initial state off. Turn on at height ≥80; turn off at height ≤75. Treat missing readings as unknown. These classroom values are not an engineering safety specification.
PRACTICAL STEP 1
Trace a simple threshold
First label each reading on if ≥80 and off otherwise. Observe that it turns off immediately at 78. Explain why repeated values near 80 could cause flicker.
PRACTICAL STEP 2
Add memory
Use the sensor lab or a paper state table: retain the previous state between 75 and 80. Compare the two sequences. State is a stored value that can change future behaviour.
PRACTICAL STEP 3
Test faults and restart
Insert ‘?’ for missing data and explain why unknown must be visible. Restart the model at 78 and state your initial-state assumption. If using hardware later, seek supervised validation; a simulator is not a safety device.
INTERACTIVE / NO ACCOUNT OR AI KEY NEEDED
Sensor state simulator
Predict a result first. Change an input, compare the output and explain why it changed. These fictional models are learning aids.
Initial state: off. Unknown is displayed for missing data; internal memory keeps the last valid state. This is a classroom model, not a safety controller.
Step | cm | Simple threshold | With memory
1 | 74 | off | off
2 | 79 | off | off
3 | 80 | on | on
4 | 78 | off | on
5 | 76 | off | on
6 | 75 | off | off
7 | 74 | off | off
Tool inputs reset when you leave. Download results or record them in your private mission workbook.
Compare with the crew’s reasoning
With memory, the sequence is off, off, on, on, on, off, off. At 78 the result depends on previous state. Missing data shows unknown; in this classroom model the last valid internal state is retained for the next reading. A real control system requires a separate safe-failure design.
Finding the answer is not evidence of mastery. Explain it, test a changed input and record your own work.
Your evidence checklist
My state table matches all seven readings.
I test a missing value and a restart, not just normal data.
I explain sensor input, stored state and output separately.
Independent challenge
Change thresholds to 70 and 85. Predict a new sequence before running it and explain the trade-off.
Open the workbook template
Time | Reading (cm) | Previous state | Rule used | Output
Simple threshold sequence:
Two-threshold sequence:
Missing-data behaviour:
Restart assumption:
Choose a twist. Use paper, a sketch or a conversation.
Optional practice. Copy useful observations into your workbook; choosing a twist does not record completion.
Compare ideas with someone you know. Sharing is optional.
Need a hint or a clearer next step?
Work through Stop an alarm from flickering with a focused prompt. Your notes stay private unless you choose to paste an excerpt here.
Use fictional examples. Leave out names, contact details, passwords and private records.
Get an answer here with my own OpenAI API key
Requires an active learning profile. Your provider may charge you; API billing is separate from ChatGPT. EaseBrain has no paid-key fallback.
Key clears after each attempt. EaseBrain saves only a daily request count, not your key, prompt or answer. OpenAI’s data policies apply. Up to 500 output tokens and 20 attempts a day; no automatic retries. These limits do not guarantee a spending ceiling.