Skip to content

Main content

Trap Servicing Valid Share Tool

Calculate trap servicing valid share from explicit caller-supplied inputs.

Loading tool…

Description

Summarize usable trap exposure after servicing time, relative to total deployment duration.

Insect sampling effort can be expressed as trap-nights, active hours, flower-minutes, distance or area-times-beats. Normalizing catch by effort makes its denominator explicit, but does not automatically estimate abundance or equalize detection.

Summarize usable trap exposure after servicing time, relative to total deployment duration.

When to use this tool

Use Trap Servicing Valid Share when normalizing a supplied catch, visit count or sampling exposure.

How to use the tool and how it works

  1. Enter deployedDurations, servicingDurations, usable. Keep parallel arrays aligned. 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 deployedTotal, serviceTotal, validExposure, validShare, defined. Inspect defined before interpreting the associated values.

Require equally long deployedDurations, servicingDurations and usable arrays, with 0 <= servicingDuration <= deployedDuration. Sum deployedTotal and serviceTotal over all records. validExposure sums deployed-servicing only for usable entries; validShare divides it by deployedTotal, or is zero with defined = false when deployedTotal is zero.1

Input fieldMeaning and unitsAccepted input
deployedDurationsDeployed DurationsRequired. Array of finite number; maximum items 256.
servicingDurationsServicing DurationsRequired. Array of finite number; maximum items 256.
usableUsableRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
deployedTotalDeployed TotalRequired. Finite number.
serviceTotalService TotalRequired. Finite number.
validExposureValid ExposureRequired. Finite number.
validShareValid ShareRequired. Finite number.
definedWhether the stated denominator has positive support; read this before interpreting a zero placeholder.Required. Boolean.
json
{
  "input": {
    "deployedDurations": [
      10,
      10
    ],
    "servicingDurations": [
      2,
      1
    ],
    "usable": [
      true,
      false
    ]
  },
  "output": {
    "deployedTotal": 20,
    "serviceTotal": 3,
    "validExposure": 8,
    "validShare": 0.4,
    "defined": true
  }
}

Limitations and assumptions

  • Servicing is not deducted from the share's denominator. Usability flags are supplied; overlaps, trap failures and sampling bias are not independently verified.
  • 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

Use a suitable sampling and detection model for abundance inference, and review actual deployments and conditions before aggregating effort.

References

  1. Calculation and input contract: entomology/trap-servicing-valid-share — tool.io

Similar or alternative tools