
use peer critique and test data to improve my cooling sleeve, evaluate the accuracy and limits of my data, and revise the test so its results are more trustworthy.
Phase 4: Build
Do Now. Look at your version 1 data. Write one result you trust and one you do not, and say why.
Two repeats of the same sleeve gave 2.4 °C and 0.6 °C of extra cooling (sample data). What does this most suggest?
Gallery critique. Teams set out their sleeves, matrices and data. Visitors leave sticky notes in three colors: I like… (a strength backed by data), I wonder… (a question about the test or the science), and What if… (a specific change). Critique the design, not the designer.
Class criteria (set in 1.07). A cooling sleeve on a 500 mL “model arm” bottle of water that starts at about 37 °C must (1) cool it at least 2 °C more than a bare control bottle in 10 minutes in front of a fan, (2) use no more than 50 mL of water per test, (3) cost no more than 8 sample budget points, and (4) stay on a moving arm for a full work hour without slipping.
Worked example 1: evaluating data (sample data). A team ran version 1 twice: extra cooling 2.4 °C and 0.6 °C. They checked their notes: in trial 2 the sleeve had dried out by minute 6 and the fan had been bumped to a lower speed. Their data were not precise (repeats disagreed) and possibly not accurate (the thermometer was touching the bottle wall, not the water). Fixes: mark the fan position, re-wet at a fixed time, and hang the thermometer in the middle of the water.
Worked example 2: version 2 (sample data). The team added a light outer mesh and re-wet the sponge at minute 5 with 10 mL more water (still within 50 mL). Three repeats gave 2.6, 2.9 and 2.7 °C of extra cooling: mean 2.7 °C, range 0.3 °C. Version 2 met criterion 1, and the small range shows the revised test is more precise. They also tested a partner team’s bottle to see whether the result held on a second setup, which makes the finding more generalizable.
From sleeve to system. A sleeve is an object. The co-op also needs a process: a work-rest and drinking routine. A full plan is a system: sleeves, shade, water and salt replacement, rest breaks and a buddy check for warning signs such as confusion, dizziness or stopping sweating, which call for emergency help.
| Version | Trial 1 (°C extra) | Trial 2 | Trial 3 | Mean | Range | Criteria met (1-4) |
|---|---|---|---|---|---|---|
| 1 | ||||||
| 2 |
Use your critique notes and both versions’ data.
Evaluate your investigation.
Evaluate your test: how accurate and precise were your data, what is one limitation, and does your evidence show the sleeve helps a body stay near its set point? Then revise your test plan to make the results more generalizable, and explain why.
Federal workplace-safety agencies in the United States run a heat-illness prevention campaign built around three words: water, rest, shade. Guidance from the National Institute for Occupational Safety and Health (NIOSH) adds a fourth idea: acclimatization. Over one to two weeks of gradually increasing work in the heat, the body adapts: people start sweating sooner and sweat more, and their heart rate rises less for the same work. NIOSH advises that new workers build up their time in the heat gradually over their first days on the job, because people who are new to the heat face the highest risk. In other words, the body’s own feedback system gets better with practice, and a good safety plan gives it time to do so.
Think about it: Which parts of your cooling plan support the body’s loop, and which give it time to adapt? What would you add for a worker’s first week?
Sleeve version 2 and your data feed straight into the Heat Stress Explanation in the next lesson.
Exit ticket: which change from version 1 to version 2 made the biggest difference, and what evidence shows it?
How confident are you that you can evaluate the accuracy and precision of my data and revise a test to make it more trustworthy.
Materials: version 1 sleeves and setups, sticky notes in three colors, extra sponge and mesh, thermometers, fans, goggles.
Timing: about 15 minutes of gallery critique, 25 minutes to build and test version 2, 10 minutes to log and evaluate.
Listen for: “precise” and “accurate” used as synonyms; revisions with no data behind them.
Support / stretch: give a revision-log template. Stretch: graph both versions with error bars from the range and decide whether the improvement is larger than the spread.