Skip to content

Main content

Feature Label Time Window Overlap Tool

Half-open temporal overlap audit, not a complete information-leakage detector.

Loading tool…

Description

Return positive-duration overlap between feature and label windows.

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.

Return positive-duration overlap between feature and label windows.

When to use this tool

Use Feature Label Time Window Overlap when checking an explicit feature-time or split-membership condition.

How to use the tool and how it works

  1. Enter featureStart, featureEnd, labelStart, labelEnd. 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 overlap, overlaps. Inspect overlaps before interpreting the associated values.

Return positive-duration overlap between feature and label windows. Require ordered endpoints; overlap is max(0,min(ends)-max(starts)), and overlaps uses strict positive intersection.1

Input fieldMeaning and unitsAccepted input
featureStartFeature StartRequired. Finite number.
featureEndFeature EndRequired. Finite number.
labelStartLabel StartRequired. Finite number.
labelEndLabel EndRequired. Finite number.
Output fieldInterpretationReturned shape
overlapOverlapRequired. Finite number.
overlapsOverlapsRequired. Boolean.
json
{
  "input": {
    "featureStart": 0,
    "featureEnd": 10,
    "labelStart": 8,
    "labelEnd": 20
  },
  "output": {
    "overlap": 2,
    "overlaps": true
  }
}

Limitations and assumptions

  • Touching endpoints are false; overlap alone does not establish every kind of target leakage.
  • 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-label-time-window-overlap — tool.io

Similar or alternative tools