Skip to content

Main content

Vertical Farm Harvest Cycle Day Utilization Tool

Calculate vertical farm harvest cycle day utilization from explicit caller-supplied inputs.

Loading tool…

Description

Sum growingDays, cleaningDays, and idleDays for positive cycleDays.

An indoor-growing record or design budget combines quantities such as tray area, operating time, water volume, electrical energy, and light output. Ratios depend on a stated production boundary and period. Supplied conversion factors and idealized geometry need to remain separate from measured equipment and crop performance.

Sum growingDays, cleaningDays, and idleDays for positive cycleDays.

When to use this tool

Use Vertical Farm Harvest Cycle Day Utilization when you need one stated production, lighting, water, or geometry term from a consistently defined growing-system budget.

How to use the tool and how it works

  1. Enter growingDays, cleaningDays, idleDays, horizonDays. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read cycleDays, completeCycles, productiveShare. Use the output convention below.

Sum growingDays, cleaningDays, and idleDays for positive cycleDays. Return completeCycles=floor(horizonDays/cycleDays) and productiveShare=growingDays/cycleDays, requiring all durations nonnegative.1

Input fieldMeaning and unitsAccepted input
growingDaysGrowing DaysRequired. Finite number; minimum 0.
cleaningDaysCleaning DaysRequired. Finite number; minimum 0.
idleDaysIdle DaysRequired. Finite number; minimum 0.
horizonDaysHorizon DaysRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
cycleDaysCycle DaysRequired. Finite number.
completeCyclesComplete CyclesRequired. Safe integer.
productiveShareProductive ShareRequired. Finite number.
json
{
  "input": {
    "growingDays": 20,
    "cleaningDays": 3,
    "idleDays": 2,
    "horizonDays": 100
  },
  "output": {
    "cycleDays": 25,
    "completeCycles": 4,
    "productiveShare": 0.8
  }
}

Limitations and assumptions

  • Only complete cycles count toward completeCycles. This is a supplied schedule model without partial-harvest credit, yield estimation, crop requirements, or cleaning validation.
  • The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.

Alternative or Complementary methods

Compare the supplied budget with measured system records and keep the same production boundary. Equipment selection, installation, and crop requirements need an appropriate engineering or agronomic assessment.

References

  1. Calculation and input contract: vertical-farming/vertical-farm-harvest-cycle-day-utilization — tool.io

Similar or alternative tools