Harvest Forecast Calibration
GrowScope forecasts a weight range and harvest date from a plant's canopy width and light readings, then blends in the user's own completed-cycle history — matched by strain, then plant type — once any exists.
How to do this in GrowScope
- The base forecast uses canopy width and the latest light (DLI) reading — no history required.
- Once completed cycles exist in the archive, GrowScope matches by strain first, falling back to plant type (autoflower/photoperiod).
- Matching cycles' actual grams-per-square-meter and cycle duration blend into the forecast, weighted by how many matching cycles exist, up to a cap.
- A checkmark on the forecast indicates it's calibrated against history rather than the base formula alone.
Harvest forecast calibration
- Category
- Plant tracking & health
- Purpose
- Predict a plant's harvest weight range and date, improving in accuracy as the user's own completed-cycle history grows.
- Input
- Canopy width and light (DLI) reading (base forecast); the account's own completed cycles (calibration)
- Location
- Plant list cards, shown under each plant's cycle progress bar
- User action
- None to trigger — computed automatically whenever canopy width and a light reading exist
- Output
- A weight range (grams) and expected harvest date, with a checkmark when calibrated against the user's own history; blend weight capped at 70% of the forecast even with many matching cycles.
- Used by
- None
Notes
- Matching prefers the same strain (case-insensitive) among the user's completed cycles; if none match, it falls back to the same plant type (autoflower vs. photoperiod).
- Even a single matching completed cycle is used, but its blend weight is capped (roughly 25% per matching cycle, up to a 70% cap) so one unusual cycle can't dominate the forecast.
- With zero completed-cycle history, the forecast still returns — it uses the base canopy/light formula and is marked uncalibrated, never blocked entirely for lack of history.
- Calibration only ever uses the account's own completed cycles — never other growers' data, which is a separate feature (Grower Benchmarks).
Frequently asked questions
How many past cycles do I need before calibration kicks in?
Just one matching cycle is enough to start calibrating, though its influence is capped so a single unusual result can't dominate the forecast.
What if I've never grown this strain before?
The forecast falls back to matching by plant type (autoflower or photoperiod) among your other completed cycles instead of strain.
Is the forecast guaranteed accurate?
No — it's explicitly presented as an estimate, both before and after calibration, and can't account for anything not yet reflected in your logged data.