Deterministic crop-day baseline
Every supported day resolves to an explicit schedule entry instead of a broad stage average or a hidden previous-day fallback.
- Crop-day key
- P1/P2 percentages and counts
- Runoff and dryback targets
Crop-steering software
Core Cannabis connects crop-day intent to explicit P1 recharge events, P2 maintenance events, P3 dryback, table-level response, and controller-ready runtime.
Every supported day resolves to an explicit schedule entry instead of a broad stage average or a hidden previous-day fallback.
The selected substrate profile defines the milliliters represented by one percent. Event volume follows the approved shot percentage.
Emitter count, emitter rating, or measured catch-test flow translates each approved volume into seconds without changing the crop target.
A submitted table response can adjust the matching table’s next schedule. Without a submitted response, the baseline remains unchanged.
Understand the three jobs irrigation performs across the crop day.
Read guideSee how each response signal is measured and kept station-specific.
Read guideConvert a catch test into accurate controller runtime.
Read guideIt is the deliberate use of irrigation timing, shot size, maintenance events, and dryback to support the operating intent for the crop stage.
Production schedules are reviewed and applied for the next cycle. Sensor and grower response can inform the next plan without silently rewriting a running irrigation day.
The station holds its current adaptive basis while normal crop-stage progression, including the finish taper, continues. Missing data does not erase a prior accepted correction.