Labanotation vs Benesh Notation Literacy Lookup

Audit actual caller-defined notation literacy task evidence per system with pass/fail/unknown distinction; no automatic translation, cultural hierarchy or certification from checklist.

Description

Notation literacy checklists can distinguish passed, failed and unknown tasks for each system.

Notation literacy checklists can distinguish passed, failed and unknown tasks for each system. Evidence must accompany results.^[1]

Enter nonempty unique system/task IDs and aligned binary result/evidence matrices with one row per system and one column per task. Return counts and systems with every task verified passed.

When to use Labanotation vs Benesh Notation Literacy Lookup

Use Labanotation vs Benesh Notation Literacy Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No notation translation, cultural hierarchy or certification is inferred.

Prepare the annotated dance, timing, rehearsal or inventory records requested. Supply caller rules, evidence flags and local reference values; distinguish beats, bars, counts and seconds.

How to use Labanotation vs Benesh Notation Literacy Lookup and understand its results

Prepare the annotated dance, timing, rehearsal or inventory records requested. Supply caller rules, evidence flags and local reference values; distinguish beats, bars, counts and seconds.
Enter callerNotationSystemIds, callerRequiredNotationTaskIds, observedTaskPassFlags, taskEvidenceFlags using the field table and calculation rules, then run the tool.
Read knownPassedTaskCountsBySystem, knownFailedTaskCountsBySystem, unknownTaskCountsBySystem, systemsWithAllCallerTasksVerified. 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
callerNotationSystemIds	Caller notation system ids	list of string	Required
callerRequiredNotationTaskIds	Caller required notation task ids	list of string	Required
observedTaskPassFlags	Observed task pass flags	list of list of number	Required
taskEvidenceFlags	Task evidence flags	list of list of number	Required

Enter nonempty unique system/task IDs and aligned binary result/evidence matrices with one row per system and one column per task. Return counts and systems with every task verified passed.

knownPass=pass1 and evidence1; knownFail=pass0 and evidence1

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

Output field	Meaning	Value type
knownPassedTaskCountsBySystem	Known passed task counts by system	list of number
knownFailedTaskCountsBySystem	Known failed task counts by system	list of number
unknownTaskCountsBySystem	Unknown task counts by system	list of number
systemsWithAllCallerTasksVerified	Systems with all caller tasks verified	list of string

json

{
  "input": {
    "callerNotationSystemIds": [
      "Labanotation",
      "Benesh"
    ],
    "callerRequiredNotationTaskIds": [
      "read",
      "write"
    ],
    "observedTaskPassFlags": [
      [
        1,
        0
      ],
      [
        1,
        1
      ]
    ],
    "taskEvidenceFlags": [
      [
        1,
        1
      ],
      [
        1,
        0
      ]
    ]
  },
  "output": {
    "knownPassedTaskCountsBySystem": [
      1,
      1
    ],
    "knownFailedTaskCountsBySystem": [
      1,
      0
    ],
    "unknownTaskCountsBySystem": [
      0,
      1
    ],
    "systemsWithAllCallerTasksVerified": []
  }
}

Limitations and assumptions

No notation translation, cultural hierarchy or certification is inferred.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Matrices are limited to 128 rows and 128 entries per row. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Laban Effort Factors Flow Weight Time Space Lookup: Laban effort-factor inventories require declared poles and evidence. Flow, weight, time and space remain separate columns. For a complementary task, use Mirror Dependency Facing Away Transfer Drill Lookup: Matched phrase error counts expose transfer differences between mirror and facing-away conditions. Signed differences allow improvement.

References

Labanotation vs Benesh Notation Literacy Lookup — tool.io

Similar or alternative tools

Laban Effort Factors Flow Weight Time Space Lookup
Laban effort-factor inventories require declared poles and evidence. Flow, weight, time and space remain separate columns.
Mirror Dependency Facing Away Transfer Drill Lookup
Matched phrase error counts expose transfer differences between mirror and facing-away conditions. Signed differences allow improvement.