Skip to content

Main content

Joint Motion Unit Factor Tool

Calculate joint motion unit factor from explicit caller-supplied inputs.

Loading tool…

Description

Calculate joint motion unit factor from explicit caller-supplied inputs.

A bench or research calculation starts from supplied measurements, reference values, and unit conventions. A transformed value, timing difference, or support fraction describes that model; its clinical meaning depends on measurement validity and a separate professional assessment.

Calculate joint motion unit factor from explicit caller-supplied inputs.

When to use this tool

Use it for joint motion unit factor when the required inputs and conventions are already available.

How to use the tool and how it works

  1. Enter angle, radiansPerSourceUnit, radiansPerTargetUnit. Use the stated units and boundary conventions.
  2. Run the calculation. Correct any input error before interpreting a result.
  3. Read convertedAngle. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

Convert an angle by multiplying by radiansPerSourceUnit and dividing by radiansPerTargetUnit, requiring both supplied conversion factors positive.1

Input fieldMeaning and unitsAccepted input
angleAngleRequired. Finite number.
radiansPerSourceUnitRadians Per Source UnitRequired. Finite number; strictly above 0.
radiansPerTargetUnitRadians Per Target UnitRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
convertedAngleConverted AngleRequired. Finite number.
json
{
  "input": {
    "angle": 90,
    "radiansPerSourceUnit": 0.017453292519943295,
    "radiansPerTargetUnit": 1
  },
  "output": {
    "convertedAngle": 1.5707963267948966
  }
}

Limitations and assumptions

  • The conversion factors are not looked up or verified and must describe the intended angular units. Conversion alone does not establish normal motion, measurement quality, or clinical significance.
  • The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
  • Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.

Alternative or Complementary methods

For joint motion unit factor, check the source records and the supplied rule before comparing the result with another method. Use an appropriately validated measurement or analysis method for clinical interpretation.

References

  1. Calculation and input contract: rheumatology/joint-motion-unit-factor — tool.io

Similar or alternative tools