Skip to content

Main content

Trap Lure Age Reset Token Tool

Age of a supplied lure inventory record, without a lure efficacy or replacement recommendation.

Loading tool…

Description

When replacementKnown is true, require replacedDay between installedDay and observedDay and use it as anchorDay; otherwise use installedDay.

Lure-age and servicing records need a common day origin and an explicit installation or replacement anchor. An age or due flag describes the supplied schedule, not measured lure effectiveness.

When replacementKnown is true, require replacedDay between installedDay and observedDay and use it as anchorDay; otherwise use installedDay.

When to use this tool

Use Trap Lure Age Reset Token when checking a recorded lure age or caller-supplied servicing interval.

How to use the tool and how it works

  1. Enter installedDay, replacedDay, observedDay, replacementKnown. 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 ageDays, anchorDay. Use the output convention below.

Require observedDay >= installedDay. When replacementKnown is true, require replacedDay between installedDay and observedDay and use it as anchorDay; otherwise use installedDay. ageDays = observedDay-anchorDay.1

Input fieldMeaning and unitsAccepted input
installedDayInstalled DayRequired. Safe integer.
replacedDayReplaced DayRequired. Safe integer.
observedDayObserved DayRequired. Safe integer.
replacementKnownReplacement KnownRequired. Boolean.
Output fieldInterpretationReturned shape
ageDaysAge DaysRequired. Safe integer.
anchorDayAnchor DayRequired. Safe integer.
json
{
  "input": {
    "installedDay": 10,
    "replacedDay": 20,
    "observedDay": 25,
    "replacementKnown": true
  },
  "output": {
    "ageDays": 5,
    "anchorDay": 20
  }
}

Limitations and assumptions

  • Use common numeric day coordinates. An unknown replacement leaves the installation anchor in force; no lure effectiveness or replacement interval is inferred.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • 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. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review deployment histories and product-specific monitoring protocols before selecting a replacement schedule.

References

  1. Calculation and input contract: entomology/trap-lure-age-reset-token — tool.io

Similar or alternative tools