Skip to content

Main content

Split Group Empty Fold Budget Tool

Calculate split group empty fold budget from explicit caller-supplied inputs.

Loading tool…

Description

Identify empty and below-minimum group-count folds.

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.

Identify empty and below-minimum group-count folds.

When to use this tool

Use Split Group Empty Fold Budget when checking an explicit feature-time or split-membership condition.

How to use the tool and how it works

  1. Enter groupCounts, minimumGroups. 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 emptyIndices, insufficientIndices. Use the output convention below.

Identify empty and below-minimum group-count folds. Require nonnegative whole minimumGroups and nonnegative groupCounts; return zero-valued indexes and indexes whose count < minimum.1

Input fieldMeaning and unitsAccepted input
groupCountsGroup CountsRequired. Array of safe integer; maximum items 256.
minimumGroupsMinimum GroupsRequired. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
emptyIndicesEmpty IndicesRequired. Array of safe integer; maximum items 256.
insufficientIndicesInsufficient IndicesRequired. Array of safe integer; maximum items 256.
json
{
  "input": {
    "groupCounts": [
      3,
      0,
      1
    ],
    "minimumGroups": 2
  },
  "output": {
    "emptyIndices": [
      1
    ],
    "insufficientIndices": [
      1,
      2
    ]
  }
}

Limitations and assumptions

  • The counts are supplied, not reconstructed; minimumGroups zero makes empty folds sufficient under that threshold.
  • 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/split-group-empty-fold-budget — tool.io

Similar or alternative tools