# Round-off error

A roundoff error, also called rounding error, is the difference between the result produced by a given algorithm using exact arithmetic and the result produced by the same algorithm using finite-precision, rounded arithmetic. Rounding errors are due to inexactness in the representation of real numbers and the arithmetic operations done with them. This is a form of quantization error. When using approximation equations or algorithms, especially when using finitely many digits to represent real numbers, one of the goals of numerical analysis is to estimate computation errors. Computation errors, also called numerical errors, include both truncation errors and roundoff errors.
When a sequence of calculations with an input involving roundoff error are made, errors may accumulate, sometimes dominating the calculation. In ill-conditioned problems, significant error may accumulate.
In short, there are two major facets of roundoff errors involved in numerical calculations:
1. Digital computers have magnitude and precision limits on their ability to represent numbers.
2. Certain numerical manipulations are highly sensitive to roundoff errors. This can result from both mathematical considerations as well as from the way in which computers perform arithmetic operations.

## Representation error

The error introduced by attempting to represent a number using a finite string of digits is a form of roundoff error called representation error. Here are some examples of representation error in decimal representations:
 Notation Representation Approximation Error 1/7 0. 0.142 857 0.000 000 ln 2 0.693 147 180 559 945 309 41... 0.693 147 0.000 000 180 559 945 309 41... log10 2 0.301 029 995 663 981 195 21... 0.3010 0.000 029 995 663 981 195 21... cube root| 1.259 921 049 894 873 164 76... 1.25992 0.000 001 049 894 873 164 76... square root| 1.414 213 562 373 095 048 80... 1.41421 0.000 003 562 373 095 048 80... e 2.718 281 828 459 045 235 36... 2.718 281 828 459 045 0.000 000 000 000 000 235 36... π 3.141 592 653 589 793 238 46... 3.141 592 653 589 793 0.000 000 000 000 000 238 46...

Increasing the number of digits allowed in a representation reduces the magnitude of possible roundoff errors, but any representation limited to finitely many digits will still cause some degree of roundoff error for uncountably many real numbers. Additional digits used for intermediary steps of a calculation are known as guard digits.
Rounding multiple times can cause error to accumulate. For example, if 9.945309 is rounded to two decimal places, then rounded again to one decimal place, the total error is 0.054691. Rounding 9.945309 to one decimal place in a single step introduces less error. This commonly occurs when performing arithmetic operations.

## Floating-point number system

Compared with the fixed-point number system, the floating-point number system is more efficient in representing real numbers so it is widely used in modern computers. While the real numbers are infinite and continuous, a floating-point number system is finite and discrete. Thus, representation error, which leads to roundoff error, occurs under the floating-point number system.

### Notation of floating-point number system

A floating-point number system is characterized by integers:
• Any has the following form:

### Normalized floating-number system

• A floating-point number system is normalized if the leading digit is always nonzero unless the number is zero. Since the mantissa is, the mantissa of a nonzero number in a normalized system satisfies. Thus, the normalized form of a nonzero IEEE floating-point number is where. In binary, the leading digit is always so it is not written out and is called the implicit bit. This gives an extra bit of precision so that the roundoff error caused by representation error is reduced.
• Since floating-point number system is finite and discrete, it cannot represent all real numbers which means infinite real numbers can only be approximated by some finite numbers through rounding rules. The floating-point approximation of a given real number by can be denoted.
• * The total number of normalized floating-point numbers is

### IEEE standard

In the IEEE standard the base is binary, i.e., and normalization is used. The IEEE standard stores the sign, exponent, and mantissa in separate fields of a floating point word, each of which has a fixed width. The two most commonly used levels of precision for floating-point numbers are single precision and double precision.
 Precision Sign Exponent Mantissa Single 1 8 23 Double 1 11 52

## Machine epsilon

can be used to measure the level of roundoff error in the floating-point number system. Here are two different definitions.
• The machine epsilon, denoted, is the maximum possible absolute relative error in representing a nonzero real number in a floating-point number system.
• The machine epsilon, denoted, is the smallest number such that. Thus, whenever.

## Roundoff error under different rounding rules

There are two common rounding rules, round-by-chop and round-to-nearest. The IEEE standard uses round-to-nearest.
• Round-by-chop: The base- expansion of is truncated after the digit.
• * This rounding rule is biased because it always moves the result toward zero.
• Round-to-nearest: is set to the nearest floating-point number to. When there is a tie, the floating-point number whose last stored digit is even is used.
• * For IEEE standard where the base is, this means when there is a tie it is rounded so that the last digit is equal to.
• * This rounding rule is more accurate but more computationally expensive.
• * Rounding so that the last stored digit is even when there is a tie ensures that it is not rounded up or down systematically. This is to try to avoid the possibility of an unwanted slow drift in long calculations due simply to a biased rounding.
• The following example illustrates the level of roundoff error under the two rounding rules. The rounding rule, round-to-nearest, leads to less roundoff error in general.
 x Round-by-chop Roundoff Error Round-to-nearest Roundoff Error 1.649 1.6 0.049 1.6 0.049 1.650 1.6 0.050 1.6 0.050 1.651 1.6 0.051 1.7 -0.049 1.699 1.6 0.099 1.7 -0.001 1.749 1.7 0.049 1.7 0.049 1.750 1.7 0.050 1.8 -0.050

### Calculating roundoff error in IEEE standard

Suppose the usage of round-to-nearest and IEEE double precision.
• Example: the decimal number can be rearranged into
Since the bit to the right of the binary point is a and is followed by other nonzero bits, the round-to-nearest rule requires rounding up, that is, add bit to the bit. Thus, the normalized floating-point representation in IEEE standard of is
• Now the roundoff error can be calculated when representing with.
This representation is derived by discarding the infinite tail
from the right tail and then added in the rounding step.

### Measuring roundoff error by using machine epsilon

The machine epsilon can be used to measure the level of roundoff error when using the two rounding rules above. Below are the formulas and corresponding proof. The first definition of machine epsilon is used here.

#### Theorem

1. Round-by-chop:
2. Round-to-nearest:

#### Proof

Let where, and let be the floating-point representation of.
Since round-by-chop is being used, it is
• In order to determine the maximum of this quantity, the is a need to find the maximum of the numerator and the minimum of the denominator. Since , the minimum value of the denominator is. The numerator is bounded above by. Thus,. Therefore, for round-by-chop.
The proof for round-to-nearest is similar.
• Note that the first definition of machine epsilon is not quite equivalent to the second definition when using the round-to-nearest rule but it is equivalent for round-by-chop.

## Roundoff error caused by floating-point arithmetic

Even if some numbers can be represented exactly by floating-point numbers and such numbers are called machine numbers, performing floating-point arithmetic may lead to roundoff error in the final result.

Machine addition consists of lining up the decimal points of the two numbers to be added, adding them, and then storing the result again as a floating-point number. The addition itself can be done in higher precision but the result must be rounded back to the specified precision, which may lead to roundoff error.
For example, adding to in IEEE double precision as follows,
• This is saved as since round-to-nearest is used in IEEE standard. Therefore, is equal to in IEEE double precision and the roundoff error is.
From this example, it can be seen that roundoff error can be introduced when doing the addition of a large number and a small number because the shifting of decimal points in the mantissas to make the exponents match may cause the loss of some digits.

### Multiplication

In general, the product of -digit mantissas contains up to digits, so the result might not fit in the mantissa. Thus roundoff error will be involved in the result.
• For example, consider a normalized floating-point number system with the base and the mantissa digits are at most. Then and. Note that but since there at most mantissa digits. The roundoff error would be.

### Division

In general, the quotient of -digit mantissas may contain more than -digits. Thus roundoff error will be involved in the result.
• For example, if the normalized floating-point number system above is still being used, then but. So, the tail is cut off.

### Subtractive cancellation

The subtracting of two nearly equal numbers is called subtractive cancellation.
• When the leading digits are cancelled, the result may be too small to be represented exactly and it will just be represented as.
• * For example, let and the second definition of machine epsilon is used here. What is the solution to ?
It is known that and are nearly equal numbers, and. However, in the floating-point number system,. It can be seen that is too small so it is represented as.
• Even if the result is representable, the result is still regarded as "garbage". There is not much faith in this value because the most uncertainty in any floating-point number is the digits on the far right.
• * For example,. The result is clearly representable, but there is not much faith in it.

## Accumulation of roundoff error

Errors can be magnified or accumulated when a sequence of calculations is applied on an initial input with roundoff error due to inexact representation.

### Unstable algorithms

An algorithm or numerical process is called stable if small changes in the input only produce small changes in the output and it is called unstable if large changes in the output
are produced.
A sequence of calculations normally occur when running some algorithm. The amount of error in the result depends on the stability of the algorithm. Roundoff error will be magnified by unstable algorithms.
For example, for with given. It is easy to show that. Suppose is our initial value and has a small representation error, which means the initial input to this algorithm is instead of. Then the algorithm does the following sequence of calculations.
The roundoff error is amplified in succeeding calculations so this algorithm is unstable.

### Ill-conditioned problems

Even if a stable algorithm is used, the solution to a problem is still inaccurate due to the accumulation of roundoff error when the problem itself is ill-conditioned.
The condition number of a problem is the ratio of the relative change in the solution to the relative change in the input. A problem is well-conditioned if small relative changes in input result in small relative changes in the solution. Otherwise. the problem is called ill-conditioned. In other words, a problem is called ill-conditioned if its condition number is "much larger" than.
The condition number is introduced as a measure of the roundoff errors that can result when solving ill-conditioned problems.
For example, higher-order polynomials tend to be very ill-conditioned, that is, they tend to be highly sensitive to roundoff error.
In 1901, Carl Runge published a study on the dangers of higher-order polynomial interpolation. He looked at the following simple-looking function:
which is now called Runge's function. He took equidistantly spaced data points from this function over the interval. He then used interpolating polynomials of increasing order and found that as he took more points, the polynomials and the original curve differed considerably as illustrated in Figure “Comparison1” and Figure “Comparison 2”. Further, the situation deteriorated greatly as the order was increased. As shown in Figure “Comparison 2”, the fit has gotten even worse, particularly at the ends of the interval.
Click on the figures in order to see the full descriptions.

### Real world example: Patriot missile failure due to magnification of roundoff error

On 25 February 1991, during the Gulf War, an American Patriot missile battery in Dharan, Saudi Arabia, failed to intercept an incoming Iraqi Scud missile. The Scud struck an American Army barracks and killed 28 soldiers. A report of the Government Accountability Office entitled "Patriot Missile Defense: Software Problem Led to System Failure at Dhahran, Saudi Arabia" reported on the cause of the failure: an inaccurate calculation of the time since boot due to computer arithmetic errors. Specifically, the time in tenths of a second, as measured by the system's internal clock, was multiplied by 10 to produce the time in seconds. This calculation was performed using a 24-bit fixed point register. In particular, the value 1/10, which has a non-terminating binary expansion, was chopped at 24 bits after the radix point. The small chopping error, when multiplied by the large number giving the time in tenths of a second, led to a significant error. Indeed, the Patriot battery had been up around 100 hours, and an easy calculation shows that the resulting time error due to the magnified chopping error was about 0.34 seconds.. A Scud travels at about meters per second, and so travels more than half a kilometer in this time. This was far enough that the incoming Scud was outside the "range gate" that the Patriot tracked. Ironically, the fact that the bad time calculation had been improved in some parts of the code, but not all, contributed to the problem, since it meant that the inaccuracies did not cancel.