Skip to content

Main content

Feature Availability Lag Gap Tool

Calculate feature availability lag gap from explicit caller-supplied inputs.

Loading tool…

Description

Compare feature publication lag with a supplied allowance.

Model validation depends on when information became available and how records or entities enter splits. A timestamp inequality or group overlap count can identify one local issue without proving absence of every form of leakage.

Compare feature publication lag with a supplied allowance.

When to use this tool

Use Feature Availability Lag Gap when checking an explicit feature-time or split-membership condition.

How to use the tool and how it works

  1. Enter eventAt, availableAt, allowedLag. 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 lag, gap. Use the output convention below.

Compare feature publication lag with a supplied allowance. Require allowedLag >= 0; lag = availableAt-eventAt, gap = allowedLag-lag.1

Input fieldMeaning and unitsAccepted input
eventAtEvent AtRequired. Finite number.
availableAtAvailable AtRequired. Finite number.
allowedLagAllowed LagRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
lagLagRequired. Finite number.
gapGapRequired. Finite number.
json
{
  "input": {
    "eventAt": 10,
    "availableAt": 15,
    "allowedLag": 8
  },
  "output": {
    "lag": 5,
    "gap": 3
  }
}

Limitations and assumptions

  • Negative lags are retained; no provenance, actual release time or causal feature eligibility is 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 complete data-provenance and validation-design review, including label horizons, entity dependence and preprocessing fit scope.

References

  1. Calculation and input contract: data-science/feature-availability-lag-gap — tool.io

Similar or alternative tools