Description
Test exact membership in configuredKeys and mark unused only when configured but absent from usedKeys.
Trial records can encode conditions, response keys, inclusion masks and blind-code mappings. Literal membership and balanced counts describe the supplied records; they do not establish valid randomization, effective blinding or clinical conclusions.
Test exact membership in configuredKeys and mark unused only when configured but absent from usedKeys.
When to use this tool
Use Response Key Unused Choice Flag when you need a specified experimental-record or allocation-index check.
How to use the tool and how it works
- Enter key, configuredKeys, usedKeys. Keep parallel arrays aligned. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read configured, unused. Inspect configured, unused before interpreting the associated values.
Test exact membership in configuredKeys and mark unused only when configured but absent from usedKeys.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| key | Key | Required. Text; maximum UTF-16 length 8192. |
| configuredKeys | Configured Keys | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| usedKeys | Used Keys | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| configured | Configured | Required. Boolean. |
| unused | Unused | Required. Boolean. |
{
"input": {
"key": "j",
"configuredKeys": [
"f",
"j"
],
"usedKeys": [
"f"
]
},
"output": {
"configured": true,
"unused": true
}
} Limitations and assumptions
- An unconfigured key has unused false. Lists are supplied records, not observed keyboard behavior, valid responses or an inferred participant preference.
- 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.
Alternative or Complementary methods
Review the complete experimental design, controlled mappings and source records. Validate actual randomization, permissions, missingness and analysis assumptions rather than inferring them from one token or count.
References
Similar or alternative tools
- Response Key Laterality Code
Label a supplied key left, right or unmapped by exact membership.
- Response Change Initial Final Key Pair Tool
Compare explicit initial and final response keys while preserving their ordered pair without judging correctness.