Signal and noise: precision cultivation

What this is, and why a grow room is really a listening problem

Every sensor reading in your grow room is two things added together: the real story (the signal) and meaningless jitter (the noise). Your whole job is seeing the first through the second.

The hard part of growing has moved from collecting data to reading it. Sensors are cheap and dashboards are pretty, yet most decisions still run on gut feel. Collecting data used to be the work. Now the work is separating the meaningful pattern from the meaningless wobble. This paper teaches you to hear what your plants are telling you above the static, and, just as important, when to do nothing.

A single flower room can generate hundreds of thousands of datapoints a week^[8], so a method for safely ignoring most of them is not optional. More data is not more insight. A firehose of low-quality data is harder to act on than a trickle of good data.

Key terms, defined once

The vocabulary comes from radio engineering, manufacturing and statistics, so the words can sound intimidating. They are not. Signal-to-noise ratio (SNR) is how loud the thing you care about is compared to everything else competing for your attention^[9]. A high-SNR room is calm and decisive. A low-SNR room is anxious and reactive.

Where the noise comes from

You cannot reduce what you cannot name. Grow-room noise enters through six channels. Three are physical and inherent: the sensor itself (electronic jitter, drift, no calibration), placement (a probe near a vent or light, or a sample of one), and biology (one plant differs from the next). The other three are procedural, and therefore the cheapest to fix: the environment (doors, HVAC cycling), the operator (inconsistent manual sampling) and the data pipeline (logging gaps, mixed-up units, clock skew).

Sensor-specific calibration is not a nicety. In low-cost permittivity soil-moisture sensors, applying a sensor-by-sensor calibration cut error by roughly 70% versus the factory default^[6]. Most ‘the room is fighting me’ stories are really ‘I am fighting the noise’ stories.

Averaging and how often to measure

The most powerful, most ignored noise filter in horticulture is replication. Ask one plant how the room is doing and you get a rumour. Average twelve plants across the bench and the individual quirks cancel, leaving only the shared room signal. The maths is friendly: the error of an average shrinks with the square root of how many readings you combine^[5]. Four probes roughly halve the noise, nine cut it to a third.

How often you measure matters just as much. Sample too slowly and a fast pattern folds into a slow one that was never there. Engineers call this aliasing: the wagon-wheel-spinning-backwards effect from old films. The rule of thumb, from the Nyquist–Shannon sampling theorem, is to sample at least twice as fast as the fastest pattern you need to see^[4]. To catch a 30-minute irrigation response, log every 10–15 minutes.

Control limits: knowing when a wiggle deserves a response

The most valuable idea in the paper comes from manufacturing's quality revolution: statistical process control (SPC). Walter Shewhart, working at Bell Laboratories, split all variation into two kinds^[1]. Common-cause variation is the natural jitter of a stable process: it lives inside the control limits and should be left alone. Special-cause variation is a real, assignable event that breaks outside the limits and earns investigation.

Control limits are computed from the process's own history, conventionally the mean plus or minus three standard deviations^[1], not from a guess. Here is the hard part: W. Edwards Deming proved that tampering (reacting to common-cause jitter) amplifies a process's variation rather than reducing it^[2]. SPC gives you permission to do the hardest thing in cultivation: watch a number move and correctly do nothing.

These pattern rules catch real shifts that a single out-of-limits point would miss, and they do it without raising false alarms on ordinary noise^[3]. The lesson is blunt: the over-reactive grower, nudging a stable process all day, is usually the room's single biggest noise source.

The operator's playbook, step by step

None of the highest-return moves needs new capital. Most need only discipline, tackled top-down. Here is the order to do it in.

1. 1
   Stop watching live numbers

   A live ticker invites tampering. Look at decision charts on a schedule, not the raw feed all day.
2. 2
   Set a sampling cadence per channel

   Use the table above. Fast channels fast, slow channels slow, no faster than you'll act on.
3. 3
   Add a rolling average to every decision chart

   Smooth the line you decide from, but keep a raw view one click away so a real emergency isn't hidden.
4. 4
   Aggregate across 6–12 probes

   Never single-source a decision. Report the average and let one weird probe be outvoted.
5. 5
   Write SOPs for manual readings

   Same time, same method, same spot, every time. That kills operator noise for free.
6. 6
   Calibrate on a logged schedule

   This quarter: a fixed calibration cadence against a reference is your only defence against drift.
7. 7
   Compute control limits for your top 3 KPIs

   Mean ±3σ from your own history. Now you know what 'abnormal' actually means.
8. 8
   Audit placement and widen twitchy dead-bands

   Move probes off edges, vents and lights into the canopy core, and loosen dead-bands that chatter.

Three workhorse filters cover almost all grow data: the moving average (simple), the EWMA (exponentially-weighted, leaning on recent readings so it lags less for the same smoothing^[7]), and the median filter (which deletes single-point spikes). Start with a window spanning roughly 30–60 minutes and adjust.

Common pitfalls

The two opposite failures are over-smoothing and tampering. Filtering is sugar: a little clarifies, too much rots. Crank the window too wide and you erase a real fast event, a pump failure or an EC spike from a clogged dripper, at exactly the moment you needed to see it. The opposite mistake is reacting to every twitch, which destabilises the very room you were trying to steady^[2].

A specific systems failure is hunting. A feedback loop fed noisy data, or tuned too tight, over-corrects one way. The noisy measurement says it overshot, so it slams back the other way, and the room oscillates instead of settling. The fingerprint is a regular saw-tooth in temperature, RH or VWC that isn't driven by day/night. If your HVAC or fertigation seems to ‘fight itself’, suspect a noisy sensor or a too-tight dead-band before you suspect broken equipment.

Realistic expectations

Facilities climb a predictable ladder, and knowing which rung you're on tells you what to do next.

Most commercial rooms sit at Logged, which is paradoxically more stressful than flying blind, because now there's a wall of noise to panic about. The goal is not the summit overnight. It's one rung up. The jump from Logged to Filtered, just smoothing plus sampling rules, is the highest-return move in this whole paper, and it costs almost nothing but habit.

Track few high-signal KPIs, not forty gauges. The metric most tied to commercial success is often uniformity, measured as the batch coefficient of variation, not peak yield. Reducing the spatial and temporal fluctuation of your environment (a lower coefficient of variation) has been shown to improve crop growth and quality^[8]. A batch where every plant yields 95g sells better than one averaging 110g with a 40g spread.

Next: see how a clean, filtered signal actually drives irrigation in smart watering by VWC & EC, and how that closes the loop without hunting in closed-loop control.