Treatment Threshold Level Checker

Independent measured mite indicator vs independently applicable site/season/protocol monitoring bands; flags only, no chemical treatment choice, rate or efficacy claim. Unknown indices distinguish zero placeholders from known zero margins. Caller independently verifies strain, site, protocol and evidence; not colony-health, treatment, transport-safety or regulatory certification.

Description

Mite monitoring requires a measurement protocol and independently chosen review limits.

Mite monitoring requires a measurement protocol and independently chosen review limits.^[1]

A band comparison does not select a treatment or determine colony health. Use Treatment Threshold Level Checker to compare known observations with supplied bands.

When to use Treatment Threshold Level Checker

Use Treatment Threshold Level Checker to compare known observations with supplied bands. Choose independently established criterion bands in consistent units and mark unassessed observations with known flag 0.

How to use Treatment Threshold Level Checker and understand its results

Choose independently established criterion bands in consistent units and mark unassessed observations with known flag 0.
Enter Observed observed protocol mite indicator, Caller observed protocol mite indicator lower, Caller observed protocol mite indicator upper, Known observed protocol mite indicator flags using the field table and validation rules below, then run the tool.
Read Signed known margins, Known review indices, Unknown indices; interpret the units, signs, ordering and unknown-value placeholders described below.
Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.

Input field	Meaning	Value type	Requirement
observedObservedProtocolMiteIndicator	Observed observed protocol mite indicator	array of number	Required; constraints below
callerObservedProtocolMiteIndicatorLower	Caller observed protocol mite indicator lower	array of number	Required; constraints below
callerObservedProtocolMiteIndicatorUpper	Caller observed protocol mite indicator upper	array of number	Required; constraints below
knownObservedProtocolMiteIndicatorFlags	Known observed protocol mite indicator flags	array of number	Required; constraints below

Provide aligned nonempty arrays of observations, lower limits, upper limits and known flags. All numbers must be finite, each lower limit must not exceed its upper limit, and flags must be 0 or 1. Known criteria receive min(observation−lower, upper−observation); a negative margin requests review, while equality is inside the band. Unknown criteria receive a zero placeholder and are listed separately. Review and unknown indices are zero based and retain input order. Limits and their applicable units come from the caller, rather than an installed assessment scale.

known margin = min(observation−lower, upper−observation); unknown margin = 0 placeholder

Use the field order, units and branch conditions described above.

Output field	Meaning	Value type
signedKnownMargins	Distance to the closer inclusive band limit; negative means outside; unknown entries use zero placeholders.	array of number
knownReviewIndices	Zero-based known-criterion indices strictly outside inclusive bands.	array
unknownIndices	Zero-based indices marked unknown; their zero margins are placeholders.	array of number

json

{
  "input": {
    "observedObservedProtocolMiteIndicator": [
      2,
      5
    ],
    "callerObservedProtocolMiteIndicatorLower": [
      1,
      1
    ],
    "callerObservedProtocolMiteIndicatorUpper": [
      3,
      4
    ],
    "knownObservedProtocolMiteIndicatorFlags": [
      1,
      0
    ]
  },
  "output": {
    "signedKnownMargins": [
      1,
      0
    ],
    "knownReviewIndices": [],
    "unknownIndices": [
      1
    ]
  }
}

Limitations and assumptions

A band comparison does not select a treatment or determine colony health. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use Tracheal Mite Dissection Threshold Lookup for a related task: Tracheal-mite dissection thresholds depend on protocol and interpretation.

Use Small Hive Beetle Trap Threshold Checker for a related task: Trap counts need matched observation durations to express beetles per trap-day.

References

Treatment Threshold Level Checker — tool.io

Similar or alternative tools

Tracheal Mite Dissection Threshold Lookup
Tracheal-mite dissection thresholds depend on protocol and interpretation.
Small Hive Beetle Trap Threshold Checker
Trap counts need matched observation durations to express beetles per trap-day.