Description
Round total*minimumFraction/quantum upward to integer quanta and return actualShare=quanta*quantum/total.
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.
Round total*minimumFraction/quantum upward to integer quanta and return actualShare=quanta*quantum/total.
When to use this tool
Use Minimum Share Quantum Count 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 total, minimumFraction, quantum. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read quanta, actualShare. Use the output convention below.
Round total*minimumFraction/quantum upward to integer quanta and return actualShare=quanta*quantum/total. Require positive total and quantum and fraction within zero through one.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| total | Total | Required. Finite number; strictly above 0. |
| minimumFraction | Minimum Fraction | Required. Finite number; minimum 0; maximum 1. |
| quantum | Quantum | Required. Finite number; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| quanta | Quanta | Required. Safe integer. |
| actualShare | Rounded-up quantity divided by total; can exceed one. | Required. Finite number. |
{
"input": {
"total": 100,
"minimumFraction": 0.23,
"quantum": 5
},
"output": {
"quanta": 5,
"actualShare": 0.25
}
}Limitations and assumptions
- ActualShare can exceed one when the quantum is too large for the total. This meets the supplied lower-share target arithmetically without guaranteeing a feasible indivisible allocation or distributing a remainder.
- 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.