Show-Control Trigger Coverage

Audit show-control trigger mappings.

Description

A show-control trigger maps an event to a planned system response.

A show-control trigger maps an event to a planned system response. Checking trigger labels identifies missing mappings without testing their timing or hardware behavior.^[1]

Audit show-control trigger mappings.

When to use Show-Control Trigger Coverage

Use this tool to audit show-control trigger mappings.

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.

How to use Show-Control Trigger Coverage and understand its results

Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
Enter requiredTriggers, mappedTriggers using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
requiredTriggers	Required show-control triggers	list of string	Required
mappedTriggers	Mapped triggers	list of string	Required

Enter requiredTriggers and mappedTriggers label lists. Trim labels, reject blank entries and match case-insensitively with en-US lowercase. Deduplicate each list, requiring at least one distinct required item; an empty observed list is allowed. Return matched, missing, unexpected labels and coverage. Duplicate normalized labels keep their last trimmed spelling at the first key position.

coverage%=100 matchedDistinctRequirements/distinctRequirements

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "requiredTriggers": [
      "alpha",
      "beta",
      "gamma",
      "delta"
    ],
    "mappedTriggers": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 50,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma",
      "delta"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

It does not execute triggers, inspect mapping destinations or test control-system interlocks. Spelling differences beyond case and outer whitespace remain distinct.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Keyboard-Patch Coverage: Audit keyboard patch coverage. For a complementary task, use Running-Sheet Coverage: Audit running-sheet action coverage.

References

Show-Control Trigger Coverage — tool.io

Similar or alternative tools

Keyboard-Patch Coverage
Audit keyboard patch coverage.
Running-Sheet Coverage
Audit running-sheet action coverage.