Description
Compare axis and unit labels with expected labels exactly and serialize axis, unit and numeric value as a JSON-array key.
Music research records can contain supplied counts, axes and source labels. Literal consistency helps organize observations but does not perform linguistic analysis, authenticate instruments or establish musical and cultural interpretation.
Compare axis and unit labels with expected labels exactly and serialize axis, unit and numeric value as a JSON-array key.
When to use this tool
Use Instrument Measure Axis Label when you need a supplied music-record count or label check.
How to use the tool and how it works
- Enter value, axis, unit, expectedAxis, expectedUnit. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read compatible, recordKey. Inspect compatible before interpreting the associated values.
Compare axis and unit labels with expected labels exactly and serialize axis, unit and numeric value as a JSON-array key.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| value | Value under the stated unit, type, and placeholder convention. | Required. Finite number. |
| axis | Axis | Required. Text; maximum UTF-16 length 8192. |
| unit | Unit | Required. Text; maximum UTF-16 length 8192. |
| expectedAxis | Expected Axis | Required. Text; maximum UTF-16 length 8192. |
| expectedUnit | Expected Unit | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| compatible | Compatible | Required. Boolean. |
| recordKey | Record Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"value": 10,
"axis": "length",
"unit": "cm",
"expectedAxis": "length",
"expectedUnit": "cm"
},
"output": {
"compatible": true,
"recordKey": "[\"length\",\"cm\",10]"
}
}Limitations and assumptions
- Literal labels are not unit conversions or dimensional validation. The key does not establish an instrument's identity, source authenticity or cultural classification.
- 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
Review original source documentation and the relevant performer, linguistic or musical context. Keep transcription and classification decisions distinct from record arithmetic.
References
Similar or alternative tools
- Questioned Line Width Unit Base
Multiply for baseWidth and compare unit with referenceUnit literally.
- Public Register Volume Token
Serialize repository, series and volumeToken as a JSON-array source key, and flag volume presence by trimmed nonempty text.