Skip to content

Main content

Share Transfer Difference Tool

Transfer an explicit amount between two pools while retaining total mass and signed share change.

Loading tool…

Description

Transfer an explicit amount between two pools while retaining total mass and signed share change.

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.

Transfer an explicit amount between two pools while retaining total mass and signed share change.

When to use this tool

Use Share Transfer Difference 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

  1. Enter firstAmount, secondAmount, transfer. 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 firstAfter, secondAfter, firstShareChange. Use the output convention below.

Return firstAfter=firstAmount-transfer, secondAfter=secondAmount+transfer, and firstShareChange=-transfer/(firstAmount+secondAmount). Require positive combined nonnegative amounts and transfer keeping both nonnegative.1

Input fieldMeaning and unitsAccepted input
firstAmountFirst AmountRequired. Finite number; minimum 0.
secondAmountSecond AmountRequired. Finite number; minimum 0.
transferTransferRequired. Finite number.
Output fieldInterpretationReturned shape
firstAfterFirst AfterRequired. Finite number.
secondAfterSecond AfterRequired. Finite number.
firstShareChangeFirst Share ChangeRequired. Finite number.
json
{
  "input": {
    "firstAmount": 30,
    "secondAmount": 70,
    "transfer": 10
  },
  "output": {
    "firstAfter": 20,
    "secondAfter": 80,
    "firstShareChange": -0.1
  }
}

Limitations and assumptions

  • Negative transfer reverses direction. The combined base stays fixed; this is arithmetic allocation, not a transaction, legal entitlement, or indivisible-item rounding procedure.
  • 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

  1. Calculation and input contract: proportions/share-transfer-difference — tool.io

Similar or alternative tools