Skip to content

Main content

Confusion Reject Column Partition

Explicit nonnegative square confusion table with unique supplied labels, actual rows and predicted columns; partition one explicit predicted reject column without removing actual rows or relabeling rejected observations as errors.

Loading tool…

Description

Partition one explicit predicted reject column without removing actual rows or relabeling rejected observations as errors.

A confusion table uses actual labels as rows and predicted labels as columns. Cells can contain occurrence counts or supplied nonnegative weights; the axis label order must stay with the matrix. Row, column and joint normalization have different denominators, and a zero denominator needs an explicit undefined result.

Partition one explicit predicted reject column without removing actual rows or relabeling rejected observations as errors.

When to use this tool

Use this tool to partition one explicit predicted reject column without removing actual rows or relabeling rejected observations as errors.

How to use the tool and how it works

  1. Enter matrix, labels, rejectLabel using the input definitions below.
  2. Run the operation. Resolve malformed-input errors before interpreting the result.
  3. Read result.actualLabels, result.predictedLabels, result.accepted, result.rejected. Interpret signs, units, ordering and null values using the rules below.

Find the exact rejectLabel column. Return all actual labels unchanged, remove that predicted column from accepted, and return its values separately as rejected; predictedLabels omits only the reject column.1

Input fieldMeaning and unitsAccepted input
matrixSquare nonnegative finite table: matrix[actualIndex][predictedIndex], both axes in labels order.Dense list of at most 128 rows of at most 128 finite numbers; the operation’s shape constraints also apply.
labelsDistinct label strings defining actual row and predicted column order; score tools require at least one label.Dense list of at most 128 strings, each at most 8,192 UTF-16 code units.
rejectLabelExact supplied label naming the predicted reject column.Text, at most 8,192 UTF-16 code units; the stated grammar and narrower limits also apply.
Output fieldInterpretation
resultObject containing the fields below.
result.actualLabelsAll original actual-axis labels, including the reject label if supplied.
result.predictedLabelsPredicted-axis labels excluding the explicit reject column.
result.acceptedTable with only the reject column removed; all actual rows remain.
result.rejectedRemoved predicted reject-column values in actual-label order.
json
{
  "input": {
    "matrix": [
      [
        2,
        1
      ],
      [
        0,
        1
      ]
    ],
    "labels": [
      "a",
      "b"
    ],
    "rejectLabel": "b"
  },
  "output": {
    "result": {
      "actualLabels": [
        "a",
        "b"
      ],
      "predictedLabels": [
        "a"
      ],
      "accepted": [
        [
          2
        ],
        [
          0
        ]
      ],
      "rejected": [
        1,
        1
      ]
    }
  }
}

Limitations and assumptions

  • Actual reject-label rows remain. The partition does not decide whether a rejection should be scored as an error.
  • Label strings are compared exactly. Confusion values may be nonnegative fractional weights; a count interpretation requires count data. Probability-like score rows use [0,1] entries with sum tolerance 10⁻⁸, without establishing calibration.
  • Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
  • Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.

Alternative or Complementary methods

Check label coverage and axis order before comparing tables. Use a separate evaluation design for uncertainty, calibration, operating thresholds and the consequences of real-world decisions.

References

  1. Tool behavior and example: Confusion Reject Column Partition — tool.io

Similar or alternative tools