Description
Check label overlap with a validation window extended after its end.
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.
Check label overlap with a validation window extended after its end.
When to use this tool
Use Cross Validation Purge Window Overlap when checking an explicit feature-time or split-membership condition.
How to use the tool and how it works
- Enter labelStart, labelEnd, validationStart, validationEnd, embargo. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlap. Inspect overlap before interpreting the associated values.
Check label overlap with a validation window extended after its end. Require ordered windows and nonnegative embargo; compare min(labelEnd,validationEnd+embargo) > max(labelStart,validationStart).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| labelStart | Label Start | Required. Finite number. |
| labelEnd | Label End | Required. Finite number. |
| validationStart | Validation Start | Required. Finite number. |
| validationEnd | Validation End | Required. Finite number. |
| embargo | Nonnegative duration extending validationEnd only; does not symmetrically extend both boundaries. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlap | Overlap | Required. Boolean. |
{
"input": {
"labelStart": 1,
"labelEnd": 5,
"validationStart": 4,
"validationEnd": 8,
"embargo": 0
},
"output": {
"overlap": true
}
}Limitations and assumptions
- The embargo extends only the validation end here; no full cross-validation purge procedure is executed.
- 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
Similar or alternative tools
- Feature Label Time Window Overlap
Return positive-duration overlap between feature and label windows.
- Feature Window Availability Slack
Return feature publication time and safety-lag slack.