Description
Return feature publication time and safety-lag slack.
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 feature publication time and safety-lag slack.
When to use this tool
Use Feature Window Availability Slack when checking an explicit feature-time or split-membership condition.
How to use the tool and how it works
- Enter featureWindowEnd, publicationDelay, predictionAt, suppliedSafetyLag. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read availableAt, slack, usableUnderInputs. Inspect usableUnderInputs before interpreting the associated values.
Return feature publication time and safety-lag slack. Require nonnegative publicationDelay/suppliedSafetyLag; availableAt = featureWindowEnd+delay, slack = predictionAt-availableAt-safetyLag, usableUnderInputs includes zero.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| featureWindowEnd | Feature Window End | Required. Finite number. |
| publicationDelay | Publication Delay | Required. Finite number; minimum 0. |
| predictionAt | Prediction At | Required. Finite number. |
| suppliedSafetyLag | Nonnegative extra lag required after featureWindowEnd+publicationDelay. | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| availableAt | Available At | Required. Finite number. |
| slack | Slack | Required. Finite number. |
| usableUnderInputs | Usable Under Inputs | Required. Boolean. |
{
"input": {
"featureWindowEnd": 10,
"publicationDelay": 2,
"predictionAt": 15,
"suppliedSafetyLag": 1
},
"output": {
"availableAt": 12,
"slack": 2,
"usableUnderInputs": true
}
}Limitations and assumptions
- Supplied timestamps and lags do not prove actual data availability or absence of other 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
Similar or alternative tools
- Feature Label Time Window Overlap
Return positive-duration overlap between feature and label windows.
- Feature Availability Lag Gap
Compare feature publication lag with a supplied allowance.