Description
Map percent onto a supplied affine span as value=baselineOrigin+(percent/100)*baselineSpan, requiring nonzero span.
A ratio compares quantities under a stated numerator and denominator. Fractions, percentage numerals, and percentage-point changes use different conventions, and changing a part can also change its whole. Unit consistency, zero denominators, rounding, and the order of adjustments determine the result.
Map percent onto a supplied affine span as value=baselineOrigin+(percent/100)*baselineSpan, requiring nonzero span.
When to use this tool
Use Percent Baseline Origin Offset when you need this specific ratio, allocation, transformation, interval, or adjustment-order calculation with an explicit base.
How to use the tool and how it works
- Enter percent, baselineOrigin, baselineSpan. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read value. Use the output convention below.
Map percent onto a supplied affine span as value=baselineOrigin+(percent/100)*baselineSpan, requiring nonzero span.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| percent | Percentage numeral, not a fraction; values outside zero through 100 allowed. | Required. Finite number. |
| baselineOrigin | Baseline Origin | Required. Finite number. |
| baselineSpan | Baseline Span | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| value | Value | Required. Finite number. |
{
"input": {
"percent": 25,
"baselineOrigin": 10,
"baselineSpan": 8
},
"output": {
"value": 12
}
}Limitations and assumptions
- Percent uses percentage numerals and is not bounded to zero through 100; negative spans are allowed. The tool does not infer anchors, clamp output, or validate a physical scale.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
- 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
Check numerator, denominator, units, and adjustment order before comparing results. Use a complete allocation or physical mixture model when a single arithmetic term leaves relevant constraints unspecified.
References
Similar or alternative tools
- Chained Retention Log Loss Term
Sum natural logarithms of retentionFractions for logRetention and exponentiate for retainedFraction.
- Concentration Addition Exact Volume Basis
Use an explicitly measured final volume rather than assuming additive component volumes.