Description
Return firstShare=amount/firstBase, secondShare=amount/secondBase, and ratio=firstBase/secondBase.
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.
Return firstShare=amount/firstBase, secondShare=amount/secondBase, and ratio=firstBase/secondBase.
When to use this tool
Use Reference Share Normalization Two Bases 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 amount, firstBase, secondBase. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read firstShare, secondShare, ratio. Use the output convention below.
Return firstShare=amount/firstBase, secondShare=amount/secondBase, and ratio=firstBase/secondBase. Require positive bases while allowing signed amount.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| amount | Amount | Required. Finite number. |
| firstBase | First Base | Required. Finite number; strictly above 0. |
| secondBase | Second Base | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| firstShare | First Share | Required. Finite number. |
| secondShare | Second Share | Required. Finite number. |
| ratio | firstBase/secondBase, converting firstShare into secondShare. | Required. Finite number. |
{
"input": {
"amount": 20,
"firstBase": 100,
"secondBase": 80
},
"output": {
"firstShare": 0.2,
"secondShare": 0.25,
"ratio": 1.25
}
}Limitations and assumptions
- Ratio converts firstShare into secondShare, rather than the other way around, and remains defined when amount is zero. Bases must use compatible units; shares are not constrained to zero through one.
- 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
- Two Stage Yield Backcalculate Input
Backcalculate afterFirst=output/secondYield and input=afterFirst/firstYield.
- Chained Retention Log Loss Term
Sum natural logarithms of retentionFractions for logRetention and exponentiate for retainedFraction.