In numerical analysis, the **Kahan summation algorithm**, also known as **compensated summation**,^{[1]} significantly reduces the numerical error in the total obtained by adding a sequence of finite-precision floating-point numbers, compared to the obvious approach. This is done by keeping a separate *running compensation* (a variable to accumulate small errors), in effect extending the precision of the sum by the precision of the compensation variable.

In particular, simply summing numbers in sequence has a worst-case error that grows proportional to , and a root mean square error that grows as for random inputs (the roundoff errors form a random walk).^{[2]} With compensated summation, using a compensation variable with sufficiently high precision the worst-case error bound is effectively independent of , so a large number of values can be summed with an error that only depends on the floating-point precision of the result.^{[2]}

The algorithm is attributed to William Kahan;^{[3]} Ivo Babuška seems to have come up with a similar algorithm independently (hence **Kahan–Babuška summation**).^{[4]} Similar, earlier techniques are, for example, Bresenham's line algorithm, keeping track of the accumulated error in integer operations (although first documented around the same time^{[5]}) and the delta-sigma modulation.^{[6]}

In pseudocode, the algorithm will be:

functionKahanSum(input)varsum = 0.0 // Prepare the accumulator.varc = 0.0 // A running compensation for lost low-order bits.fori = 1toinput.lengthdo// The arrayinputhas elements indexed input[1] to input[input.length].vary = input[i] - c //cis zero the first time around.vart = sum + y // Alas,sumis big,ysmall, so low-order digits ofyare lost. c = (t - sum) - y //(t - sum)cancels the high-order part ofy; subtractingyrecovers negative (low part ofy) sum = t // Algebraically,cshould always be zero. Beware overly-aggressive optimizing compilers!nexti // Next time around, the lost low part will be added toyin a fresh attempt.returnsum

This algorithm can also be rewritten to use the Fast2Sum algorithm:^{[7]}

functionKahanSum2(input)varsum = 0.0 // Prepare the accumulator.varc = 0.0 // A running compensation for lost low-order bits.fori = 1toinput.lengthdo// The arrayinputhas elements indexed input[1] to input[input.length].vary = input[i] + c //cis zero the first time around. (sum,c) = Fast2Sum(sum,y) //sum+cis an approximation to the exact sum.nexti // Next time around, the lost low part will be added toyin a fresh attempt.returnsum

This example will be given in decimal. Computers typically use binary arithmetic, but the principle being illustrated is the same. Suppose we are using six-digit decimal floating-point arithmetic, `sum`

has attained the value 10000.0, and the next two values of `input[i]`

are 3.14159 and 2.71828. The exact result is 10005.85987, which rounds to 10005.9. With a plain summation, each incoming value would be aligned with `sum`

, and many low-order digits would be lost (by truncation or rounding). The first result, after rounding, would be 10003.1. The second result would be 10005.81828 before rounding and 10005.8 after rounding. This is not correct.

However, with compensated summation, we get the correct rounded result of 10005.9.

Assume that `c`

has the initial value zero.

y = 3.14159 - 0.00000y = input[i] - ct = 10000.0 + 3.14159 = 10003.14159 But only six digits are retained. = 10003.1 Many digits have been lost! c = (10003.1 - 10000.0) - 3.14159 Thismustbe evaluated as written! = 3.10000 - 3.14159 The assimilated part ofyrecovered, vs. the original fully. = -0.0415900 Trailing zeros shown because this is six-digit arithmetic. sum = 10003.1 Thus, few digits frominput(i) met those ofsum.

The sum is so large that only the high-order digits of the input numbers are being accumulated. But on the next step, `c`

gives the error.

y = 2.71828 - (-0.0415900) The shortfall from the previous stage gets included. = 2.75987 It is of a size similar toy: most digits meet. t = 10003.1 + 2.75987 But few meet the digits ofsum. = 10005.85987 And the result is rounded = 10005.9 To six digits. c = (10005.9 - 10003.1) - 2.75987 This extracts whatever went in. = 2.80000 - 2.75987 In this case, too much. = 0.040130 But no matter, the excess would be subtracted off next time. sum = 10005.9 Exact result is 10005.85987, this is correctly rounded to 6 digits.

So the summation is performed with two accumulators: `sum`

holds the sum, and `c`

accumulates the parts not assimilated into `sum`

, to nudge the low-order part of `sum`

the next time around. Thus the summation proceeds with "guard digits" in `c`

, which is better than not having any, but is not as good as performing the calculations with double the precision of the input. However, simply increasing the precision of the calculations is not practical in general; if `input`

is already in double precision, few systems supply quadruple precision, and if they did, `input`

could then be in quadruple precision.

This section may be confusing or unclear to readers. In particular, this section uses ε, while there exist two conflicting definitions. I suggest to use u instead, whose definition is rather standard. Please help clarify the section. There might be a discussion about this on the talk page. (December 2021) (Learn how and when to remove this template message)

A careful analysis of the errors in compensated summation is needed to appreciate its accuracy characteristics. While it is more accurate than naive summation, it can still give large relative errors for ill-conditioned sums.

Suppose that one is summing values , for . The exact sum is

- (computed with infinite precision).

With compensated summation, one instead obtains , where the error is bounded by^{[2]}

where is the machine precision of the arithmetic being employed (e.g. for IEEE standard double-precision floating point). Usually, the quantity of interest is the relative error , which is therefore bounded above by

In the expression for the relative error bound, the fraction is the condition number of the summation problem. Essentially, the condition number represents the *intrinsic* sensitivity of the summation problem to errors, regardless of how it is computed.^{[8]} The relative error bound of *every* (backwards stable) summation method by a fixed algorithm in fixed precision (i.e. not those that use arbitrary-precision arithmetic, nor algorithms whose memory and time requirements change based on the data), is proportional to this condition number.^{[2]} An *ill-conditioned* summation problem is one in which this ratio is large, and in this case even compensated summation can have a large relative error. For example, if the summands are uncorrelated random numbers with zero mean, the sum is a random walk, and the condition number will grow proportional to . On the other hand, for random inputs with nonzero mean the condition number asymptotes to a finite constant as . If the inputs are all non-negative, then the condition number is 1.

Given a condition number, the relative error of compensated summation is effectively independent of . In principle, there is the that grows linearly with , but in practice this term is effectively zero: since the final result is rounded to a precision , the term rounds to zero, unless is roughly or larger.^{[2]} In double precision, this corresponds to an of roughly , much larger than most sums. So, for a fixed condition number, the errors of compensated summation are effectively , independent of .

In comparison, the relative error bound for naive summation (simply adding the numbers in sequence, rounding at each step) grows as multiplied by the condition number.^{[2]} This worst-case error is rarely observed in practice, however, because it only occurs if the rounding errors are all in the same direction. In practice, it is much more likely that the rounding errors have a random sign, with zero mean, so that they form a random walk; in this case, naive summation has a root mean square relative error that grows as multiplied by the condition number.^{[9]} This is still much worse than compensated summation, however. However, if the sum can be performed in twice the precision, then is replaced by , and naive summation has a worst-case error comparable to the term in compensated summation at the original precision.

By the same token, the that appears in above is a worst-case bound that occurs only if all the rounding errors have the same sign (and are of maximal possible magnitude).^{[2]} In practice, it is more likely that the errors have random sign, in which case terms in are replaced by a random walk, in which case, even for random inputs with zero mean, the error grows only as (ignoring the term), the same rate the sum grows, canceling the factors when the relative error is computed. So, even for asymptotically ill-conditioned sums, the relative error for compensated summation can often be much smaller than a worst-case analysis might suggest.

Neumaier^{[10]} introduced an improved version of Kahan algorithm, which he calls an "improved Kahan–Babuška algorithm", which also covers the case when the next term to be added is larger in absolute value than the running sum, effectively swapping the role of what is large and what is small. In pseudocode, the algorithm is:

functionKahanBabushkaNeumaierSum(input)varsum = 0.0varc = 0.0 // A running compensation for lost low-order bits.fori = 1toinput.lengthdovart = sum + input[i]if|sum| >= |input[i]|thenc += (sum - t) + input[i] // Ifsumis bigger, low-order digits ofinput[i]are lost.elsec += (input[i] - t) + sum // Else low-order digits ofsumare lost.endifsum = tnextireturnsum + c // Correction only applied once in the very end.

This enhancement is similar to the replacement of Fast2Sum by 2Sum in Kahan's algorithm rewritten with Fast2Sum.

For many sequences of numbers, both algorithms agree, but a simple example due to Peters^{[11]} shows how they can differ. For summing in double precision, Kahan's algorithm yields 0.0, whereas Neumaier's algorithm yields the correct value 2.0.

Higher-order modifications of better accuracy are also possible. For example, a variant suggested by Klein,^{[12]} which he called a second-order "iterative Kahan–Babuška algorithm". In pseudocode, the algorithm is:

functionKahanBabushkaKleinSum(input)varsum = 0.0varcs = 0.0varccs = 0.0varc = 0.0varcc = 0.0fori = 1toinput.lengthdovart = sum + input[i]if|sum| >= |input[i]|thenc = (sum - t) + input[i]elsec = (input[i] - t) + sumendifsum = t t = cs + cif|cs| >= |c|thencc = (cs - t) + celsecc = (c - t) + csendifcs = t ccs = ccs + ccend loopreturnsum + cs + ccs

Although Kahan's algorithm achieves error growth for summing *n* numbers, only slightly worse growth can be achieved by pairwise summation: one recursively divides the set of numbers into two halves, sums each half, and then adds the two sums.^{[2]} This has the advantage of requiring the same number of arithmetic operations as the naive summation (unlike Kahan's algorithm, which requires four times the arithmetic and has a latency of four times a simple summation) and can be calculated in parallel. The base case of the recursion could in principle be the sum of only one (or zero) numbers, but to amortize the overhead of recursion, one would normally use a larger base case. The equivalent of pairwise summation is used in many fast Fourier transform (FFT) algorithms and is responsible for the logarithmic growth of roundoff errors in those FFTs.^{[13]} In practice, with roundoff errors of random signs, the root mean square errors of pairwise summation actually grow as .^{[9]}

Another alternative is to use arbitrary-precision arithmetic, which in principle need no rounding at all with a cost of much greater computational effort. A way of performing exactly rounded sums using arbitrary precision is to extend adaptively using multiple floating-point components. This will minimize computational cost in common cases where high precision is not needed.^{[14]}^{[11]} Another method that uses only integer arithmetic, but a large accumulator, was described by Kirchner and Kulisch;^{[15]} a hardware implementation was described by Müller, Rüb and Rülling.^{[16]}

In principle, a sufficiently aggressive optimizing compiler could destroy the effectiveness of Kahan summation: for example, if the compiler simplified expressions according to the associativity rules of real arithmetic, it might "simplify" the second step in the sequence

`t = sum + y;`

`c = (t - sum) - y;`

to

`c = ((sum + y) - sum) - y;`

and then to

`c = 0;`

thus eliminating the error compensation.^{[17]} In practice, many compilers do not use associativity rules (which are only approximate in floating-point arithmetic) in simplifications, unless explicitly directed to do so by compiler options enabling "unsafe" optimizations,^{[18]}^{[19]}^{[20]}^{[21]} although the Intel C++ Compiler is one example that allows associativity-based transformations by default.^{[22]} The original K&R C version of the C programming language allowed the compiler to re-order floating-point expressions according to real-arithmetic associativity rules, but the subsequent ANSI C standard prohibited re-ordering in order to make C better suited for numerical applications (and more similar to Fortran, which also prohibits re-ordering),^{[23]} although in practice compiler options can re-enable re-ordering, as mentioned above.

A portable way to inhibit such optimizations locally is to break one of the lines in the original formulation into two statements, and make two of the intermediate products volatile:

functionKahanSum(input)varsum = 0.0varc = 0.0fori = 1toinput.lengthdovary = input[i] - cvolatile vart = sum + yvolatile varz = t - sum c = z - y sum = tnextireturnsum

In general, built-in "sum" functions in computer languages typically provide no guarantees that a particular summation algorithm will be employed, much less Kahan summation.^{[citation needed]} The BLAS standard for linear algebra subroutines explicitly avoids mandating any particular computational order of operations for performance reasons,^{[24]} and BLAS implementations typically do not use Kahan summation.

The standard library of the Python computer language specifies an fsum function for exactly rounded summation, using the Shewchuk algorithm^{[11]} to track multiple partial sums.

In the Julia language, the default implementation of the `sum`

function does pairwise summation for high accuracy with good performance,^{[25]} but an external library provides an implementation of Neumaier's variant named `sum_kbn`

for the cases when higher accuracy is needed.^{[26]}

In the C# language, HPCsharp nuget package implements the Neumaier variant and pairwise summation: both as scalar, data-parallel using SIMD processor instructions, and parallel multi-core.^{[27]}