Skip to content

Main content

Pitfall Trap Rainout Effort Correction Tool

Remove explicit rainout trap-hours and report observed count rate; at zero effective effort the numeric placeholder is zero with rateDefined=false.

Loading tool…

Description

Calculate rainout-adjusted trap effort and a conditional catch rate.

Insect observations distinguish specimen anatomy, taxonomic sources, recorded visits, catch categories and sampling effort. Bulb-hours differ from elapsed trap-hours, and a landmark length/width ratio differs from an aerodynamic wing aspect ratio. Nondetection, missing observation and uncertain classification require their own record states.

Calculate rainout-adjusted trap effort and a conditional catch rate.

When to use this tool

Use Pitfall Trap Rainout Effort Correction when you already have scheduledTrapHours, rainoutTrapHours, observedCount and need to calculate rainout-adjusted trap effort and a conditional catch rate.

How to use the tool and how it works

  1. Enter scheduledTrapHours, rainoutTrapHours, observedCount. 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 effectiveTrapHours, countPerTrapHour, rateDefined. Inspect rateDefined before interpreting the associated values.

Require scheduled hours>=0, rainout within scheduled hours, and a nonnegative safe whole observedCount; effective=scheduled-rainout. Return count/effective if positive, otherwise zero with rateDefined=false.1

Input fieldMeaning and unitsAccepted input
scheduledTrapHoursScheduled Trap HoursRequired. Finite number; minimum 0.
rainoutTrapHoursRainout Trap HoursRequired. Finite number; minimum 0.
observedCountObserved CountRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
effectiveTrapHoursEffective Trap HoursRequired. Finite number.
countPerTrapHourCount Per Trap HourRequired. Finite number.
rateDefinedFalse for zero effective trap-hours, with rate=0 placeholder; no lost count is imputed.Required. Boolean.
json
{
  "input": {
    "scheduledTrapHours": 24,
    "rainoutTrapHours": 4,
    "observedCount": 10
  },
  "output": {
    "effectiveTrapHours": 20,
    "countPerTrapHour": 0.5,
    "rateDefined": true
  }
}

Limitations and assumptions

  • Zero effective effort is not a measured zero rate. No lost catch is imputed, detection probability estimated or trap-effort comparability established.
  • 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

Inspect original specimens, images, recordings and trap logs when verifying observations. Use the complete survey and calibration method for abundance or behavioral conclusions, preserving effort, detection and taxonomic definitions rather than treating one rate or label as that analysis.

References

  1. Calculation and input contract: entomology/pitfall-trap-rainout-effort-correction — tool.io

Similar or alternative tools