Leaf Chopping Size By Instar Lookup

Measured leaf chop size by independently established instar/leaf type against caller bands, not feeding/nutrition suitability. Unknown indices distinguish zero placeholders from known zero margins. Caller independently verifies strain, stage, protocol and evidence; not disease-free, biological adequacy or process-safety certification.

Description

Leaf chop-size records need an independently established instar and leaf context.

Leaf chop-size records need an independently established instar and leaf context.^[1]

This checker compares measured lengths with supplied bands rather than determining nutritional suitability.

When to use Leaf Chopping Size By Instar Lookup

Use this tool when you need to identify observed values outside a supplied band and keep unknown evidence visible. Prepare independently matched strain, cohort, instar or stage, protocol, and measurement records.

How to use Leaf Chopping Size By Instar Lookup and understand its results

Prepare independently matched strain, cohort, instar or stage, protocol, and measurement records.
Enter observedObservedLeafChopLength, callerObservedLeafChopLengthLower, callerObservedLeafChopLengthUpper, knownObservedLeafChopLengthFlags, following the field table and rules below, then run the tool.
Read signedKnownMargins, knownReviewIndices, unknownIndices. Use the output meanings below to interpret units, signs, flags, and any nested result fields.
Correct reported input issues and run again. For a successful result, check the stated evidence coverage and assumptions before using it in your review.

Input field	Meaning	Value type	Requirement
observedObservedLeafChopLength	Observed observed leaf chop length	list of number	Required
callerObservedLeafChopLengthLower	Caller observed leaf chop length lower	list of number	Required
callerObservedLeafChopLengthUpper	Caller observed leaf chop length upper	list of number	Required
knownObservedLeafChopLengthFlags	Known observed leaf chop length flags	list of number	Required

Use aligned nonempty observation, lower-bound, upper-bound, and known-flag lists. Flags are binary zero or one and every lower bound must be at most its upper bound, including unknown entries. For known observations, return the smaller signed distance to the two bounds. A positive margin is inside the band, zero is on a boundary, and a negative margin is outside. Return zero-based review indices only for known values strictly outside the band. Unknown entries receive zero margin placeholders and separate unknown indices; these zeros do not confirm compliance.

margin_i=known_i?min(observed_i−lower_i,upper_i−observed_i):0

Symbols follow the input and output meanings and the calculation rules above.

Output field	Meaning	Value type
signedKnownMargins	Signed known margins	list of number
knownReviewIndices	Known review indices	list of number
unknownIndices	Unknown indices	list of number

json

{
  "input": {
    "observedObservedLeafChopLength": [
      2,
      5
    ],
    "callerObservedLeafChopLengthLower": [
      1,
      1
    ],
    "callerObservedLeafChopLengthUpper": [
      3,
      4
    ],
    "knownObservedLeafChopLengthFlags": [
      1,
      0
    ]
  },
  "output": {
    "signedKnownMargins": [
      1,
      0
    ],
    "knownReviewIndices": [],
    "unknownIndices": [
      1
    ]
  }
}

Limitations and assumptions

The bands and applicability are supplied by the user. Unknown evidence is not a passing test, and the tool does not validate the source or the suitability of a criterion.

Missing required fields, unknown fields, wrong types, and violated calculation rules are input issues. Numeric values must be finite; nonfinite results are rejected. Evidence arrays must be dense, with no missing cells. Numeric observation lists allow at most 10,000 entries, subject to any smaller bounds stated above.

Alternative or Complementary methods

For a related review, use Feeding Frequency By Instar Lookup: Feeding frequency depends on instar, strain, and leaf conditions in the applicable protocol. This lookup returns a verified schedule notice rather than setting a universal frequency. For a complementary step, use Feed Intake Instar Share Percent Table: An observed feed-intake share allocates a five-instar dry-leaf inventory across stages. Net-consumed dry mass must already account for leftovers before percentages are calculated.

References

Leaf Chopping Size By Instar Lookup — tool.io

Similar or alternative tools

Feeding Frequency By Instar Lookup
Feeding frequency depends on instar, strain, and leaf conditions in the applicable protocol. This lookup returns a verified schedule notice rather than setting a universal frequency.
Feed Intake Instar Share Percent Table
An observed feed-intake share allocates a five-instar dry-leaf inventory across stages. Net-consumed dry mass must already account for leftovers before percentages are calculated.