Skip to content

Main content

Tray Count Level Boundary Token Tool

Count supplied rack levels under explicit endpoint inclusion before expanding to tray units.

Loading tool…

Description

Count supplied rack levels under explicit endpoint inclusion before expanding to tray units.

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.

Count supplied rack levels under explicit endpoint inclusion before expanding to tray units.

When to use this tool

Use Tray Count Level Boundary Token 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 firstLevel, lastLevel, traysPerLevel, includeFirst, includeLast. 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 countedLevels, trays. Use the output convention below.

Count the integer levels from firstLevel through lastLevel under includeFirst and includeLast, clamping the result to zero, then multiply by traysPerLevel. Require nonnegative ordered level indices and nonnegative integer traysPerLevel.1

Input fieldMeaning and unitsAccepted input
firstLevelFirst LevelRequired. Safe integer; minimum 0.
lastLevelLast LevelRequired. Safe integer.
traysPerLevelNonnegative integer tray count for each counted level.Required. Safe integer; minimum 0.
includeFirstInclude FirstRequired. Boolean.
includeLastInclude LastRequired. Boolean.
Output fieldInterpretationReturned shape
countedLevelsCounted LevelsRequired. Safe integer.
traysTraysRequired. Safe integer.
json
{
  "input": {
    "firstLevel": 1,
    "lastLevel": 5,
    "traysPerLevel": 8,
    "includeFirst": true,
    "includeLast": false
  },
  "output": {
    "countedLevels": 4,
    "trays": 32
  }
}

Limitations and assumptions

  • For a singleton range excluding its sole level counts zero without double exclusion. This is an explicit numbering convention, not a rack layout, capacity certification, or automated inventory.
  • 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/tray-count-level-boundary-token — tool.io

Similar or alternative tools