Skip to content

Main content

Functional Test Support Share Tool

Calculate functional test support share from explicit caller-supplied inputs.

Loading tool…

Description

Sum attempted weights and weights satisfying all three flags; return their ratio with defined=true when attemptedWeight>0, otherwise share=0 and defined=false.

Movement research distinguishes elapsed time, active time, cycle phase, measured force, and assessment-score conventions. Normalizing or remapping these quantities can help compare records when their units and definitions agree. A local arithmetic term does not by itself validate a functional assessment or an exercise program.

Sum attempted weights and weights satisfying all three flags; return their ratio with defined=true when attemptedWeight>0, otherwise share=0 and defined=false.

When to use this tool

Use Functional Test Support Share when you need this motion, timing, force, annotation, or score-mapping component for supplied research records.

How to use the tool and how it works

  1. Enter taskWeights, attempted, validProtocol, completeRecord. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read attemptedWeight, supportedWeight, share, defined. Inspect defined before interpreting the associated values.

Require aligned nonnegative taskWeights with attempted, validProtocol, and completeRecord arrays. Sum attempted weights and weights satisfying all three flags; return their ratio with defined=true when attemptedWeight>0, otherwise share=0 and defined=false.1

Input fieldMeaning and unitsAccepted input
taskWeightsTask WeightsRequired. Array of finite number; minimum 0; maximum items 256.
attemptedAttemptedRequired. Array of boolean; maximum items 256.
validProtocolValid ProtocolRequired. Array of boolean; maximum items 256.
completeRecordComplete RecordRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
attemptedWeightAttempted WeightRequired. Finite number.
supportedWeightSupported WeightRequired. Finite number.
shareDimensionless share under the stated base; not a percentage numeral.Required. Finite number.
definedWhether the associated ratio is defined; inspect before using a zero placeholder.Required. Boolean.
json
{
  "input": {
    "taskWeights": [
      2,
      3,
      5
    ],
    "attempted": [
      true,
      true,
      false
    ],
    "validProtocol": [
      true,
      true,
      true
    ],
    "completeRecord": [
      true,
      false,
      true
    ]
  },
  "output": {
    "attemptedWeight": 5,
    "supportedWeight": 2,
    "share": 0.4,
    "defined": true
  }
}

Limitations and assumptions

  • Flags and weights are caller-supplied. This measures supported attempted weight, not success, ability, unattempted coverage, or the validity of a clinical test battery.
  • 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. Signed zero is exported as zero.

Alternative or Complementary methods

Use the intended assessment or motion-analysis protocol with verified timing, units, and event annotations. A complete interpretation needs the relevant measurement properties and task context beyond this local calculation.

References

  1. Calculation and input contract: physiotherapy/functional-test-support-share — tool.io

Similar or alternative tools