Catastrophic cancellation

From testwiki
Revision as of 12:53, 13 February 2025 by 145.137.135.1 (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:Short description In numerical analysis, catastrophic cancellation[1][2] is the phenomenon that subtracting good approximations to two nearby numbers may yield a very bad approximation to the difference of the original numbers.

For example, if there are two studs, one L1=253.51cm long and the other L2=252.49cm long, and they are measured with a ruler that is good only to the centimeter, then the approximations could come out to be L~1=254cm and L~2=252cm. These may be good approximations, in relative error, to the true lengths: the approximations are in error by less than 0.2% of the true lengths, |L1L~1|/|L1|<0.2%.

However, if the approximate lengths are subtracted, the difference will be L~1L~2=254cm252cm=2cm, even though the true difference between the lengths is L1L2=253.51cm252.49cm=1.02cm. The difference of the approximations, 2cm, is in error by almost 100% of the magnitude of the difference of the true values, 1.02cm.

Catastrophic cancellation is not affected by how large the inputs are—it applies just as much to large and small inputs. It depends only on how large the difference is, and on the error of the inputs. Exactly the same error would arise by subtracting 52cm from 54cm as approximations to 52.49cm and 53.51cm, or by subtracting 2.00052km from 2.00054km as approximations to 2.0005249km and 2.0005351km.

Catastrophic cancellation may happen even if the difference is computed exactly, as in the example above—it is not a property of any particular kind of arithmetic like floating-point arithmetic; rather, it is inherent to subtraction, when the inputs are approximations themselves. Indeed, in floating-point arithmetic, when the inputs are close enough, the floating-point difference is computed exactly, by the Sterbenz lemma—there is no rounding error introduced by the floating-point subtraction operation.

Formal analysis

Formally, catastrophic cancellation happens because subtraction is ill-conditioned at nearby inputs: even if approximations x~=x(1+δx) and y~=y(1+δy) have small relative errors |δx|=|xx~|/|x| and |δy|=|yy~|/|y| from true values x and y, respectively, the relative error of the difference x~y~ of the approximations from the difference xy of the true values is inversely proportional to the difference of the true values:

x~y~=x(1+δx)y(1+δy)=xy+xδxyδy=xy+(xy)xδxyδyxy=(xy)(1+xδxyδyxy).

Thus, the relative error of the exact difference x~y~ of the approximations from the difference xy of the true values is

|xδxyδyxy|.

which can be arbitrarily large if the true values x and y are close.

In numerical algorithms

Subtracting nearby numbers in floating-point arithmetic does not always cause catastrophic cancellation, or even any error—by the Sterbenz lemma, if the numbers are close enough the floating-point difference is exact. But cancellation may amplify errors in the inputs that arose from rounding in other floating-point arithmetic.

Example: Difference of squares

Given numbers x and y, the naive attempt to compute the mathematical function x2y2 by the floating-point arithmetic fl(fl(x2)fl(y2)) is subject to catastrophic cancellation when x and y are close in magnitude, because the subtraction can expose the rounding errors in the squaring. The alternative factoring (x+y)(xy), evaluated by the floating-point arithmetic fl(fl(x+y)fl(xy)), avoids catastrophic cancellation because it avoids introducing rounding error leading into the subtraction.[2]

For example, if x=1+2291.0000000018626451 and y=1+2301.0000000009313226, then the true value of the difference x2y2 is 229(1+230+231)1.8626451518330422×109. In IEEE 754 binary64 arithmetic, evaluating the alternative factoring (x+y)(xy) gives the correct result exactly (with no rounding), but evaluating the naive expression x2y2 gives the floating-point number 229=1.86264514923095703125_×109, of which less than half the digits are correct and the other (underlined) digits reflect the missing terms 259+260, lost due to rounding when calculating the intermediate squared values.

Example: Complex arcsine

When computing the complex arcsine function, one may be tempted to use the logarithmic formula directly:

arcsin(z)=ilog(1z2iz).

However, suppose z=iy for y0. Then 1z2y and iz=y; call the difference between them ε—a very small difference, nearly zero. If 1z2 is evaluated in floating-point arithmetic giving

fl(fl(1fl(z2)))=1z2(1+δ)

with any error δ0, where fl() denotes floating-point rounding, then computing the difference

1z2(1+δ)iz

of two nearby numbers, both very close to y, may amplify the error δ in one input by a factor of 1/ε—a very large factor because ε was nearly zero. For instance, if z=1234567i, the true value of arcsin(z) is approximately 14.71937803983977i, but using the naive logarithmic formula in IEEE 754 binary64 arithmetic may give 14.719644263563968_i, with only five out of sixteen digits correct and the remainder (underlined) all incorrect.

In the case of z=iy for y<0, using the identity arcsin(z)=arcsin(z) avoids cancellation because 1(z)2=1z2y but i(z)=iz=y, so the subtraction is effectively addition with the same sign which does not cancel.

Example: Radix conversion

Numerical constants in software programs are often written in decimal, such as in the C fragment double x = 1.000000000000001; to declare and initialize an IEEE 754 binary64 variable named x. However, 1.000000000000001 is not a binary64 floating-point number; the nearest one, which x will be initialized to in this fragment, is 1.0000000000000011102230246251565404236316680908203125=1+5252. Although the radix conversion from decimal floating-point to binary floating-point only incurs a small relative error, catastrophic cancellation may amplify it into a much larger one:

double x = 1.000000000000001;  // rounded to 1 + 5*2^{-52}
double y = 1.000000000000002;  // rounded to 1 + 9*2^{-52}
double z = y - x;              // difference is exactly 4*2^{-52}

The difference 1.0000000000000021.000000000000001 is 0.000000000000001=1.0×1015. The relative errors of x from 1.000000000000001 and of y from 1.000000000000002 are both below 1015=0.0000000000001%, and the floating-point subtraction y - x is computed exactly by the Sterbenz lemma.

But even though the inputs are good approximations, and even though the subtraction is computed exactly, the difference of the approximations y~x~=(1+9252)(1+5252)=42528.88×1016 has a relative error of over 11% from the difference 1.0×1015 of the original values as written in decimal: catastrophic cancellation amplified a tiny error in radix conversion into a large error in the output.

Benign cancellation

Cancellation is sometimes useful and desirable in numerical algorithms. For example, the 2Sum and Fast2Sum algorithms both rely on such cancellation after a rounding error in order to exactly compute what the error was in a floating-point addition operation as a floating-point number itself.

The function log(1+x), if evaluated naively at points 0<x1, will lose most of the digits of x in rounding fl(1+x). However, the function log(1+x) itself is well-conditioned at inputs near 0. Rewriting it as log(1+x)=xlog(1+x)(1+x)1 exploits cancellation in x^:=fl(1+x)1 to avoid the error from log(1+x) evaluated directly.[2] This works because the cancellation in the numerator log(fl(1+x))=x^+O(x^2) and the cancellation in the denominator x^=fl(1+x)1 counteract each other; the function μ(ξ)=log(1+ξ)/ξ is well-enough conditioned near zero that μ(x^) gives a good approximation to μ(x), and thus xμ(x^) gives a good approximation to xμ(x)=log(1+x).

References

Template:Reflist