Free calculator · runs in your browser
Logger sampling interval simulator
See what a logger actually records from the same 24 hours at 1, 5, 15, 30 or 60 minute intervals — and watch a real excursion disappear.
At 30-minute sampling this study looks clean. The highest reading is 7.22 °C, comfortably inside 2–8 °C, and nothing in the data suggests anything happened. In reality the room was above 8 °C for 17 minutes and reached 9.64 °C — the door opening at 10:24 fell neatly between two readings. An excursion you never sampled is an excursion you cannot investigate, report or learn from.
Every interval, side by side
| Interval | Readings | Highest recorded | Excursion | Reported duration |
|---|---|---|---|---|
| 1 min | 1,440 | 9.64 °C | seen | 17 min |
| 5 min | 288 | 9.64 °C | seen | 15 min |
| 10 min | 144 | 9.64 °C | seen | 10 min |
| 15 min | 96 | 8.56 °C | seen | 15 min |
| 30 min | 48 | 7.22 °C | missed | — |
| 60 min | 24 | 7.07 °C | missed | — |
Same 24 hours, same room, same event. The only thing that changes is how often the logger looked.
Demo data generated in your browser — a realistic cold-room profile, not a recording of a real facility.
Runs entirely in your browser · nothing you enter is sent to a server
How the calculation works
- 01A reference 24-hour cold-room trace is generated at 1-minute resolution, including compressor cycling, two defrost cycles and a goods-in door opening.
- 02The logger is simulated by taking every nth minute from that trace, starting at 00:00 — exactly what a logger set to an n-minute interval does.
- 03An excursion is any reading outside the limits; the duration a reviewer would report is the number of such readings multiplied by the interval.
- 04The true excursion is measured on the 1-minute trace, so recorded and actual can be compared directly.
Limitations
- The trace is a realistic demonstration, not a recording of a real facility, and not a thermal model of any particular room.
- Sampling starts on the hour. A logger started at a different offset would catch a different slice — which is itself the point: what a slow logger sees is partly luck.
- It shows detection, not compliance. Whether an excursion matters is decided by the product's stability data.
Frequently asked questions
- What sampling interval should I use for temperature mapping?
- One to five minutes is the usual recommendation, because it resolves door openings, defrost cycles and compressor cycling. This simulator shows why: at 30 minutes, a 17-minute excursion that peaked at 9.6 °C leaves no trace in the data at all.
- Can a logger miss a temperature excursion completely?
- Yes. If the excursion begins and ends between two readings, nothing in the dataset records it. The study then looks clean, and the excursion cannot be investigated, reported or learned from.
- Why does a slower logger show a lower maximum?
- It only ever sees the moments it sampled. A peak that happens between readings is not averaged in or smoothed — it is simply absent, so the recorded maximum understates the real worst case.
- Does a shorter interval mean too much data?
- Rarely a real constraint. A modern logger stores weeks at one-minute resolution, and 1,440 readings a day is trivial to analyse. The storage saving from a slow interval is worth far less than the evidence it costs you.
Need the reasoning, not just the number?
Ask ValiTrac AI and see the standards evidence and the engine calculation behind the answer.
Ask ValiTrac AIRead the theory
Choosing sampling interval and study duration
Short enough to see events, long enough to include the cycles that matter — and consistent across all sensors.
Data-quality checks before analysing mapping data
Statistics computed on bad data are precise and wrong. Check the data first.
Temperature mapping report: a worked example
A complete mapping report for a 2–8 °C cold room, with the actual numbers: per-sensor statistics, hot and cold spots, an excursion, data-quality findings and the acceptance decision. Demo data throughout.
What a continuous temperature monitoring system must do
Capture at an appropriate interval, alarm reliably, store data securely with an audit trail, and keep working through power and network failures.