Jump to content

Methods of computing square roots

From Wikipedia, the free encyclopedia
(Redirected from Reciprocal square root)

Methods of computing square roots are algorithms for approximating the non-negative square root of a positive real number . Since all square roots of natural numbers, other than of perfect squares, are irrational,[1] square roots can usually only be computed to some finite precision: these methods typically construct a series of increasingly accurate approximations.

Most square root computation methods are iterative: after choosing a suitable initial estimate of , an iterative refinement is performed until some termination criterion is met. One refinement scheme is Heron's method, a special case of Newton's method. If division is much more costly than multiplication, it may be preferable to compute the inverse square root instead.

Other methods are available to compute the square root digit by digit, or using Taylor series. Rational approximations of square roots may be calculated using continued fraction expansions.

The method employed depends on the needed accuracy, and the available tools and computational power. The methods may be roughly classified as those suitable for mental calculation, those usually requiring at least paper and pencil, and those which are implemented as programs to be executed on a digital electronic computer or other computing device. Algorithms may take into account convergence (how many iterations are required to achieve a specified precision), computational complexity of individual operations (i.e. division) or iterations, and error propagation (the accuracy of the final result).

A few methods like paper-and-pencil synthetic division and series expansion, do not require a starting value. In some applications, an integer square root is required, which is the square root rounded or truncated to the nearest integer (a modified procedure may be employed in this case).

History

[edit]

Procedures for finding square roots (particularly the square root of 2) have been known since at least the period of ancient Babylon in the 17th century BCE. Babylonian mathematicians calculated the square root of 2 to three sexagesimal "digits" after the 1, but it is not known exactly how. They knew how to approximate a hypotenuse using (giving for example for the diagonal of a gate whose height is rods and whose width is rods) and they may have used a similar approach for finding the approximation of [2]

Heron's method from first century Egypt was the first ascertainable algorithm for computing square root.[3]

Modern analytic methods began to be developed after introduction of the Arabic numeral system to western Europe in the early Renaissance.[citation needed]

Today, nearly all computing devices have a fast and accurate square root function, either as a programming language construct, a compiler intrinsic or library function, or as a hardware operator, based on one of the described procedures.

Initial estimate

[edit]

Many iterative square root algorithms require an initial seed value. The seed must be a non-zero positive number; it should be between 1 and , the number whose square root is desired, because the square root must be in that range. If the seed is far away from the root, the algorithm will require more iterations. If one initializes with (or ), then approximately iterations will be wasted just getting the order of magnitude of the root. It is therefore useful to have a rough estimate, which may have limited accuracy but is easy to calculate. In general, the better the initial estimate, the faster the convergence. For Newton's method (also called Babylonian or Heron's method), a seed somewhat larger than the root will converge slightly faster than a seed somewhat smaller than the root.

In general, an estimate is pursuant to an arbitrary interval known to contain the root (such as ). The estimate is a specific value of a functional approximation to over the interval. Obtaining a better estimate involves either obtaining tighter bounds on the interval, or finding a better functional approximation to . The latter usually means using a higher order polynomial in the approximation, though not all approximations are polynomial. Common methods of estimating include scalar, linear, hyperbolic and logarithmic. A decimal base is usually used for mental or paper-and-pencil estimating. A binary base is more suitable for computer estimates. In estimating, the exponent and mantissa are usually treated separately, as the number would be expressed in scientific notation.

Decimal estimates

[edit]

Typically the number is expressed in scientific notation as where and n is an integer, and the range of possible square roots is where .

Scalar estimates

[edit]

Scalar methods divide the range into intervals, and the estimate in each interval is represented by a single scalar number. If the range is considered as a single interval, the arithmetic mean (5.5) or geometric mean () times are plausible estimates. The absolute and relative error for these will differ. In general, a single scalar will be very inaccurate. Better estimates divide the range into two or more intervals, but scalar estimates have inherently low accuracy.

For two intervals, divided geometrically, the square root can be estimated as[Note 1]

This estimate has maximum absolute error of at a = 100, and maximum relative error of 100% at a = 1.

For example, for factored as , the estimate is . , an absolute error of 246 and relative error of almost 70%.

Linear estimates

[edit]

A better estimate, and the standard method used, is a linear approximation to the function over a small arc. If, as above, powers of the base are factored out of the number and the interval reduced to , a secant line spanning the arc, or a tangent line somewhere along the arc may be used as the approximation, but a least-squares regression line intersecting the arc will be more accurate.

A least-squares regression line minimizes the average difference between the estimate and the value of the function. Its equation is . Reordering, . Rounding the coefficients for ease of computation,

That is the best estimate on average that can be achieved with a single piece linear approximation of the function y=x2 in the interval . It has a maximum absolute error of 1.2 at a=100, and maximum relative error of 30% at S=1 and 10.[Note 2]

To divide by 10, subtract one from the exponent of , or figuratively move the decimal point one digit to the left. For this formulation, any additive constant 1 plus a small increment will make a satisfactory estimate so remembering the exact number isn't a burden. The approximation (rounded or not) using a single line spanning the range is less than one significant digit of precision; the relative error is greater than 1/22, so less than 2 bits of information are provided. The accuracy is severely limited because the range is two orders of magnitude, quite large for this kind of estimation.

A much better estimate can be obtained by a piece-wise linear approximation: multiple line segments, each approximating some subarc of the original. The more line segments used, the better the approximation. The most common way is to use tangent lines; the critical choices are how to divide the arc and where to place the tangent points. An efficacious way to divide the arc from y = 1 to y = 100 is geometrically: for two intervals, the bounds of the intervals are the square root of the bounds of the original interval, 1×100, i.e. [1,2100] and [2100,100]. For three intervals, the bounds are the cube roots of 100: [1,3100], [3100,(3100)2], and [(3100)2,100], etc. For two intervals, 2100 = 10, a very convenient number. Tangent lines are easy to derive, and are located at x = 1*10 and x = 10*10. Their equations are: and . Inverting, the square roots are: and . Thus for :

The maximum absolute errors occur at the high points of the intervals, at a=10 and 100, and are 0.54 and 1.7 respectively. The maximum relative errors are at the endpoints of the intervals, at a=1, 10 and 100, and are 17% in both cases. 17% or 0.17 is larger than 1/10, so the method yields less than a decimal digit of accuracy.

Hyperbolic estimates

[edit]

In some cases, hyperbolic estimates may be efficacious, because a hyperbola is also a convex curve and may lie along an arc of y = x2 better than a line. Hyperbolic estimates are more computationally complex, because they necessarily require a floating division. A near-optimal hyperbolic approximation to x2 on the interval is y = 190/(10−x) − 20. Transposing, the square root is x = 10 − 190/(y+20). Thus for :

The division need be accurate to only one decimal digit, because the estimate overall is only that accurate, and can be done mentally. This hyperbolic estimate is better on average than scalar or linear estimates. It has maximum absolute error of 1.58 at a = 100 and maximum relative error at a = 10, where the estimate of 3.67 is 16.0% higher than the root of 3.16. If instead one performed Newton-Raphson iterations beginning with an estimate of 10, it would take two iterations to get to 3.66, matching the hyperbolic estimate. For a more typical case like 75, the hyperbolic estimate of 8.00 is only 7.6% low, and 5 Newton-Raphson iterations starting at 75 would be required to obtain a more accurate result.

Arithmetic estimates

[edit]

A method analogous to piece-wise linear approximation but using only arithmetic instead of algebraic equations, uses the multiplication tables in reverse: the square root of a number between 1 and 100 is between 1 and 10, so if we know 25 is a perfect square (5 × 5), and 36 is a perfect square (6 × 6), then the square root of a number greater than or equal to 25 but less than 36, begins with a 5. Similarly for numbers between other squares. This method will yield a correct first digit, but it is not accurate to one digit: the first digit of the square root of 35 for example, is 5, but the square root of 35 is almost 6.

A better way is to the divide the range into intervals halfway between the squares. So any number between 25 and halfway to 36, which is 30.5, estimate 5; any number greater than 30.5 up to 36, estimate 6.[Note 3] The procedure only requires a little arithmetic to find a boundary number in the middle of two products from the multiplication table. Here is a reference table of those boundaries:

a nearest square est.
1
1 (= 12) 1
2.5
4 (= 22) 2
6.5
9 (= 32) 3
12.5
16 (= 42) 4
20.5
25 (= 52) 5
30.5
36 (= 62) 6
42.5
49 (= 72) 7
56.5
64 (= 82) 8
72.5
81 (= 92) 9
90.5
100 (= 102) 10
100

The final operation is to multiply the estimate k by the power of ten divided by 2, so for ,

The method implicitly yields one significant digit of accuracy, since it rounds to the best first digit.

The method can be extended 3 significant digits in most cases, by interpolating between the nearest squares bounding the operand. If , then is approximately k plus a fraction, the difference between a and k2 divided by the difference between the two squares: where

The final operation, as above, is to multiply the result by the power of ten divided by 2;

k is a decimal digit and R is a fraction that must be converted to decimal. It usually has only a single digit in the numerator, and one or two digits in the denominator, so the conversion to decimal can be done mentally.

Example: find the square root of 75. 75 = 75 × 10· 0, so a is 75 and n is 0. From the multiplication tables, the square root of the mantissa must be 8 point something because a is between 8×8 = 64 and 9×9 = 81, so k is 8; something is the decimal representation of R. The fraction R is 75 − k2 = 11, the numerator, and 81 − k2 = 17, the denominator. 11/17 is a little less than 12/18 = 2/3 = .67, so guess .66 (it's okay to guess here, the error is very small). The final estimate is 8 + .66 = 8.66. 75 to three significant digits is 8.66, so the estimate is good to 3 significant digits. Not all such estimates using this method will be so accurate, but they will be close.

Binary estimates

[edit]

When working in the binary numeral system (as computers do internally), by expressing as where , the square root can be estimated as

which is the least-squares regression line to 3 significant digit coefficients. has maximum absolute error of 0.0408 at =2, and maximum relative error of 3.0% at =1. A computationally convenient rounded estimate (because the coefficients are powers of 2) is:

[Note 4]

which has maximum absolute error of 0.086 at 2 and maximum relative error of 6.1% at a = 0.5 and a = 2.0.

For , the binary approximation gives . , so the estimate has an absolute error of 19 and relative error of 5.3%. The relative error is a little less than 1/24, so the estimate is good to 4+ bits.

An estimate for good to 8 bits can be obtained by table lookup on the high 8 bits of , remembering that the high bit is implicit in most floating point representations, and the bottom bit of the 8 should be rounded. The table is 256 bytes of precomputed 8-bit square root values. For example, for the index 111011012 representing 1.851562510, the entry is 101011102 representing 1.35937510, the square root of 1.851562510 to 8 bit precision (2+ decimal digits).

Heron's method

[edit]

The first explicit algorithm for approximating is known as Heron's method, after the first-century Greek mathematician Hero of Alexandria who described the method in his AD 60 work Metrica.[3] This method is also called the Babylonian method (not to be confused with the Babylonian method for approximating hypotenuses), although there is no evidence that the method was known to Babylonians.

Given a positive real number , let x0 > 0 be any positive initial estimate. Heron's method consists in iteratively computing until the desired accuracy is achieved. The sequence defined by this equation converges to

This is equivalent to using Newton's method to solve . This algorithm is quadratically convergent: the number of correct digits of roughly doubles with each iteration.

Derivation

[edit]

The basic idea is that if is an overestimate to the square root of a non-negative real number then will be an underestimate, and vice versa, so the average of these two numbers may reasonably be expected to provide a better approximation (though the formal proof of that assertion depends on the inequality of arithmetic and geometric means that shows this average is always an overestimate of the square root, as noted in the article on square roots, thus assuring convergence).

More precisely, if is our initial guess of and is the error in our estimate such that then we can expand the binomial as: and solve for the error term

if we suppose that

Therefore, we can compensate for the error and update our old estimate as Since the computed error was not exact, this is not the actual answer, but becomes our new guess to use in the next round of correction. The process of updating is iterated until desired accuracy is obtained.

This algorithm works equally well in the p-adic numbers, but cannot be used to identify real square roots with p-adic square roots; one can, for example, construct a sequence of rational numbers by this method that converges to +3 in the reals, but to −3 in the 2-adics.

Example

[edit]

To calculate for to seven significant figures, use the rough estimation method above to get

Therefore to seven decimal places. (The true value is 354.0451948551....) Notice that early iterations only needed to be computed to 1, 2 or 4 places to produce an accurate final answer.

Convergence

[edit]
Semilog graphs comparing the speed of convergence of Heron's method to find the square root of 100 for different initial guesses. Negative guesses converge to the negative root, positive guesses to the positive root. Note that values closer to the root converge faster, and all approximations are overestimates. In the SVG file, hover over a graph to display its points.

Suppose that Then for any natural number Let the relative error in be defined by and thus

Then it can be shown that

And thus that and consequently that convergence is assured, and quadratic.

Worst case for convergence

[edit]

If using the rough estimate above with the Babylonian method, then the least accurate cases in ascending order are as follows:

Thus in any case,

Rounding errors will slow the convergence. It is recommended to keep at least one extra digit beyond the desired accuracy of the being calculated, to avoid significant round-off error.

Bakhshali method

[edit]

This method for finding an approximation to a square root was described in an ancient Indian manuscript, called the Bakhshali manuscript. It is algebraically equivalent to two iterations of Heron's method and thus quartically convergent, meaning that the number of correct digits of the approximation roughly quadruples with each iteration.[4] The original presentation, using modern notation, is as follows: To calculate , let be the initial approximation to . Then, successively iterate as:

The values and are exactly the same as those computed by Heron's method. To see this, the second Heron's method step would compute and we can use the definitions of and to rearrange the numerator into:

This can be used to construct a rational approximation to the square root by beginning with an integer. If is an integer chosen so is close to , and is the difference whose absolute value is minimized, then the first iteration can be written as:

The Bakhshali method can be generalized to the computation of an arbitrary root, including fractional roots.[5]

One might think the second half of the Bakhshali method could be used as a simpler form of Heron's iteration and used repeatedly, e.g. however, this is numerically unstable. Without any reference to the original input value , the accuracy is limited by that of the original computation of , and that rapidly becomes inadequate.

Example

[edit]

Using the same example as in the Heron's method example, the first iteration gives

Likewise the second iteration gives Unlike in Heron's method, must be computed to 8 digits because the formula for does not correct any error in .

Digit-by-digit calculation

[edit]

This is a method to find each digit of the square root in a sequence. This method is based on the binomial theorem and basically an inverse algorithm solving . It is slower than the Babylonian method, but it has several advantages:

  • It can be easier for manual calculations.
  • Every digit of the root found is known to be correct, i.e., it does not have to be changed later.
  • If the square root has an expansion that terminates, the algorithm terminates after the last digit is found. Thus, it can be used to check whether a given integer is a square number.
  • The algorithm works for any base, and naturally, the way it proceeds depends on the base chosen.

Disadvantages are:

  • It becomes unmanageable for higher roots.
  • It does not tolerate inaccurate guesses or sub-calculations; such errors lead to every following digit of the result being wrong, unlike with Newton's method, which self-corrects any approximation errors.
  • While digit-by-digit calculation is efficient enough on paper, it is much too expensive for software implementations. Each iteration involves larger numbers, requiring more memory, but only advances the answer by one correct digit. Thus algorithm takes more time for each additional digit.

Napier's bones include an aid for the execution of this algorithm. The shifting nth root algorithm is a generalization of this method.

Basic principle

[edit]

First, consider the case of finding the square root of a number S, that is the square of a base-10 two-digit number XY, where X is the tens digit and Y is the units digit. Specifically: S will consist of 3 or 4 decimal digits.

Now to start the digit-by-digit algorithm, we split the digits of S in two groups of two digits, starting from the right. This means that the first group will be of 1 or 2 digits. Then we determine the value of X as the largest digit such that X2 is less than or equal to the first group. We then compute the difference between the first group and X2 and start the second iteration by concatenating the second group to it. This is equivalent to subtracting from S, and we're left with . We divide S' by 10, then divide it by 2X and keep the integer part to try and guess Y. We concatenate 2X with the tentative Y and multiply it by Y. If our guess is correct, this is equivalent to computing: and so the remainder, that is the difference between S' and the result, is zero; if the result is higher than S' , we lower our guess by 1 and try again until the remainder is 0. Since this is a simple case where the answer is a perfect square root XY, the algorithm stops here.

The same idea can be extended to any arbitrary square root computation next. Suppose we are able to find the square root of S by expressing it as a sum of n positive numbers such that

By repeatedly applying the basic identity the right-hand-side term can be expanded as

This expression allows us to find the square root by sequentially guessing the values of s. Suppose that the numbers have already been guessed, then the m-th term of the right-hand-side of above summation is given by where is the approximate square root found so far. Now each new guess should satisfy the recursion where is the sum of all the terms after , i.e. the remainder, such that for all with initialization When the exact square root has been found; if not, then the sum of the s gives a suitable approximation of the square root, with being the approximation error.

For example, in the decimal number system we have where are place holders and the coefficients . At any m-th stage of the square root calculation, the approximate root found so far, and the summation term are given by

Here since the place value of is an even power of 10, we only need to work with the pair of most significant digits of the remainder , whose first term is , at any m-th stage. The section below codifies this procedure.

It is obvious that a similar method can be used to compute the square root in number systems other than the decimal number system. For instance, finding the digit-by-digit square root in the binary number system is quite efficient since the value of is searched from a smaller set of binary digits {0,1}. This makes the computation faster since at each stage the value of is either for or for . The fact that we have only two possible options for also makes the process of deciding the value of at m-th stage of calculation easier. This is because we only need to check if for If this condition is satisfied, then we take ; if not then Also, the fact that multiplication by 2 is done by left bit-shifts helps in the computation.

Decimal (base 10)

[edit]

Write the original number in decimal form. The numbers are written similar to the long division algorithm, and, as in long division, the root will be written on the line above. Now separate the digits into pairs, starting from the decimal point and going both left and right. The decimal point of the root will be above the decimal point of the square. One digit of the root will appear above each pair of digits of the square.

Beginning with the left-most pair of digits, do the following procedure for each pair:

  1. Starting on the left, bring down the most significant (leftmost) pair of digits not yet used (if all the digits have been used, write "00") and write them to the right of the remainder from the previous step (on the first step, there will be no remainder). In other words, multiply the remainder by 100 and add the two digits. This will be the current value c.
  2. Find p, y and x, as follows:
    • Let p be the part of the root found so far, ignoring any decimal point. (For the first step, p = 0.)
    • Determine the greatest digit x such that . We will use a new variable y = x(20p + x).
      • Note: 20p + x is simply twice p, with the digit x appended to the right.
      • Note: x can be found by guessing what c/(20·p) is and doing a trial calculation of y, then adjusting x upward or downward as necessary.
    • Place the digit as the next digit of the root, i.e., above the two digits of the square you just brought down. Thus the next p will be the old p times 10 plus x.
  3. Subtract y from c to form a new remainder.
  4. If the remainder is zero and there are no more digits to bring down, then the algorithm has terminated. Otherwise go back to step 1 for another iteration.

Examples

[edit]

Find the square root of 152.2756.

          1  2. 3  4 
       /
     \/  01 52.27 56

         01                   1*1 <= 1 < 2*2                 x=1
         01                     y = x*x = 1*1 = 1
         00 52                22*2 <= 52 < 23*3              x=2
         00 44                  y = (20+x)*x = 22*2 = 44
            08 27             243*3 <= 827 < 244*4           x=3
            07 29               y = (240+x)*x = 243*3 = 729
               98 56          2464*4 <= 9856 < 2465*5        x=4
               98 56            y = (2460+x)*x = 2464*4 = 9856
               00 00          Algorithm terminates: Answer=12.34

Binary numeral system (base 2)

[edit]

This section uses the formalism from the digit-by-digit calculation section above, with the slight variation that we let , with each or .
We iterate all , from down to , and build up an approximate solution , the sum of all for which we have determined the value.
To determine if equals or , we let . If (i.e. the square of our approximate solution including does not exceed the target square) then , otherwise and .
To avoid squaring in each step, we store the difference and incrementally update it by setting with .
Initially, we set for the largest with .

As an extra optimization, we store and , the two terms of in case that is nonzero, in separate variables , :

and can be efficiently updated in each step:

Note that: which is the final result returned in the function below.

An implementation of this algorithm in C:[6]

int32_t isqrt(int32_t n) {
    assert(("sqrt input should be non-negative", n > 0));

    // X_(n+1)
    int32_t x = n;

    // c_n
    int32_t c = 0;

    // d_n which starts at the highest power of four <= n
    int32_t d = 1 << 30; // The second-to-top bit is set.
                         // Same as ((unsigned) INT32_MAX + 1) / 2.
    while (d > n) {
        d >>= 2;
    }

    // for dₙ … d₀
    while (d != 0) {
        if (x >= c + d) {      // if X_(m+1) ≥ Y_m then a_m = 2^m
            x -= c + d;        // X_m = X_(m+1) - Y_m
            c = (c >> 1) + d;  // c_(m-1) = c_m/2 + d_m (a_m is 2^m)
        }
        else {
            c >>= 1;           // c_(m-1) = c_m/2      (aₘ is 0)
        }
        d >>= 2;               // d_(m-1) = d_m/4
    }
    return c;                  // c_(-1)
}

Faster algorithms, in binary and decimal or any other base, can be realized by using lookup tables—in effect trading more storage space for reduced run time.[7]

Exponential identity

[edit]

Pocket calculators typically implement good routines to compute the exponential function and the natural logarithm, and then compute the square root of S using the identity found using the properties of logarithms () and exponentials ():[citation needed] The denominator in the fraction corresponds to the nth root. In the case above the denominator is 2, hence the equation specifies that the square root is to be found. The same identity is used when computing square roots with logarithm tables or slide rules.

A two-variable iterative method

[edit]

This method is applicable for finding the square root of and converges best for . This, however, is no real limitation for a computer-based calculation, as in base 2 floating-point and fixed-point representations, it is trivial to multiply by an integer power of 4, and therefore by the corresponding power of 2, by changing the exponent or by shifting, respectively. Therefore, can be moved to the range . Moreover, the following method does not employ general divisions, but only additions, subtractions, multiplications, and divisions by powers of two, which are again trivial to implement. A disadvantage of the method is that numerical errors accumulate, in contrast to single variable iterative methods such as the Babylonian one.

The initialization step of this method is while the iterative steps read Then, (while ).

The convergence of , and therefore also of , is quadratic.

The proof of the method is rather easy. First, rewrite the iterative definition of as Then it is straightforward to prove by induction that and therefore the convergence of to the desired result is ensured by the convergence of to 0, which in turn follows from .

This method was developed around 1950 by M. V. Wilkes, D. J. Wheeler and S. Gill[8] for use on EDSAC, one of the first electronic computers.[9] The method was later generalized, allowing the computation of non-square roots.[10]

Iterative methods for reciprocal square roots

[edit]

The following are iterative methods for finding the reciprocal square root of S which is . Once it has been found, find by simple multiplication: . These iterations involve only multiplication, and not division. They are therefore faster than the Babylonian method. However, they are not stable. If the initial value is not close to the reciprocal square root, the iterations will diverge away from it rather than converge to it. It can therefore be advantageous to perform an iteration of the Babylonian method on a rough estimate before starting to apply these methods.

  • Applying Newton's method to the equation produces a method that converges quadratically using three multiplications per step:
  • Another iteration is obtained by Halley's method, which is the Householder's method of order two. This converges cubically, but involves five multiplications per iteration:[citation needed] and
  • If doing fixed-point arithmetic, the multiplication by 3 and division by 8 can implemented using shifts and adds. If using floating-point, Halley's method can be reduced to four multiplications per iteration by precomputing and adjusting all the other constants to compensate: and

Goldschmidt's algorithm

[edit]

Goldschmidt's algorithm is an extension of Goldschmidt division, named after Robert Elliot Goldschmidt,[11][12] which can be used to calculate square roots. Some computers use Goldschmidt's algorithm to simultaneously calculate and . Goldschmidt's algorithm finds faster than Newton-Raphson iteration on a computer with a fused multiply–add instruction and either a pipelined floating-point unit or two independent floating-point units.[13]

The first way of writing Goldschmidt's algorithm begins

(typically using a table lookup)

and iterates until is sufficiently close to 1, or a fixed number of iterations. The iterations converge to and Note that it is possible to omit either and from the computation, and if both are desired then may be used at the end rather than computing it through in each iteration.

A second form, using fused multiply-add operations, begins

(typically using a table lookup)

and iterates until is sufficiently close to 0, or a fixed number of iterations. This converges to and

Taylor series

[edit]

If N is an approximation to , a better approximation can be found by using the Taylor series of the square root function:

As an iterative method, the order of convergence is equal to the number of terms used. With two terms, it is identical to the Babylonian method. With three terms, each iteration takes almost as many operations as the Bakhshali approximation, but converges more slowly.[citation needed] Therefore, this is not a particularly efficient way of calculation. To maximize the rate of convergence, choose N so that is as small as possible.

Continued fraction expansion

[edit]

The continued fraction representation of a real number can be used instead of its decimal or binary expansion and this representation has the property that the square root of any rational number (which is not already a perfect square) has a periodic, repeating expansion, similar to how rational numbers have repeating expansions in the decimal notation system.

Quadratic irrationals (numbers of the form , where a, b and c are integers), and in particular, square roots of integers, have periodic continued fractions. Sometimes what is desired is finding not the numerical value of a square root, but rather its continued fraction expansion, and hence its rational approximation. Let S be the positive number for which we are required to find the square root. Then assuming a to be a number that serves as an initial guess and r to be the remainder term, we can write Since we have , we can express the square root of S as

By applying this expression for to the denominator term of the fraction, we have

Compact notation

The numerator/denominator expansion for continued fractions (see left) is cumbersome to write as well as to embed in text formatting systems. So mathematicians have devised several alternative notations, like[14]

When throughout, an even more compact notation is:[15] For repeating continued fractions (which all square roots of non-perfect squares do), the repetend is represented only once, with an overline to signify a non-terminating repetition of the overlined part:[16]

For 2, the value of is 1, so its representation is:

Proceeding this way, we get a generalized continued fraction for the square root as

The first step to evaluating such a fraction[17] to obtain a root is to do numerical substitutions for the root of the number desired, and number of denominators selected. For example, in canonical form, is 1 and for 2, is 1, so the numerical continued fraction for 3 denominators is:

Step 2 is to reduce the continued fraction from the bottom up, one denominator at a time, to yield a rational fraction whose numerator and denominator are integers. The reduction proceeds thus (taking the first three denominators):

Finally (step 3), divide the numerator by the denominator of the rational fraction to obtain the approximate value of the root: rounded to three digits of precision.

The actual value of 2 is 1.41 to three significant digits. The relative error is 0.17%, so the rational fraction is good to almost three digits of precision. Taking more denominators gives successively better approximations: four denominators yields the fraction , good to almost 4 digits of precision, etc.

The following are examples of square roots, their simple continued fractions, and their first terms — called convergents — up to and including denominator 99:

S ~decimal continued fraction convergents
2 1.41421
3 1.73205
5 2.23607
6 2.44949
10 3.16228
1.77245
1.64872
1.27202

In general, the larger the denominator of a rational fraction, the better the approximation. It can also be shown that truncating a continued fraction yields a rational fraction that is the best approximation to the root of any fraction with denominator less than or equal to the denominator of that fraction — e.g., no fraction with a denominator less than or equal to 70 is as good an approximation to 2 as 99/70.

Approximations that depend on the floating point representation

[edit]

A number is represented in a floating point format as which is also called scientific notation. Its square root is and similar formulae would apply for cube roots and logarithms. On the face of it, this is no improvement in simplicity, but suppose that only an approximation is required: then just is good to an order of magnitude. Next, recognise that some powers, p, will be odd, thus for 3141.59 = 3.14159×103 rather than deal with fractional powers of the base, multiply the mantissa by the base and subtract one from the power to make it even. The adjusted representation will become the equivalent of 31.4159×102 so that the square root will be 31.4159×101.

If the integer part of the adjusted mantissa is taken, there can only be the values 1 to 99, and that could be used as an index into a table of 99 pre-computed square roots to complete the estimate. A computer using base sixteen would require a larger table, but one using base two would require only three entries: the possible bits of the integer part of the adjusted mantissa are 01 (the power being even so there was no shift, remembering that a normalised floating point number always has a non-zero high-order digit) or if the power was odd, 10 or 11, these being the first two bits of the original mantissa. Thus, 6.25 = 110.01 in binary, normalised to 1.1001 × 22 an even power so the paired bits of the mantissa are 01, while .625 = 0.101 in binary normalises to 1.01 × 2−1 an odd power so the adjustment is to 10.1 × 2−2 and the paired bits are 10. Notice that the low order bit of the power is echoed in the high order bit of the pairwise mantissa. An even power has its low-order bit zero and the adjusted mantissa will start with 0, whereas for an odd power that bit is one and the adjusted mantissa will start with 1. Thus, when the power is halved, it is as if its low order bit is shifted out to become the first bit of the pairwise mantissa.

A table with only three entries could be enlarged by incorporating additional bits of the mantissa. However, with computers, rather than calculate an interpolation into a table, it is often better to find some simpler calculation giving equivalent results. Everything now depends on the exact details of the format of the representation, plus what operations are available to access and manipulate the parts of the number. For example, Fortran offers an EXPONENT(x) function to obtain the power. Effort expended in devising a good initial approximation is to be recouped by thereby avoiding the additional iterations of the refinement process that would have been needed for a poor approximation. Since these are few (one iteration requires a divide, an add, and a halving) the constraint is severe.

Many computers follow the IEEE (or sufficiently similar) representation, and a very rapid approximation to the square root can be obtained for starting Newton's method. The technique that follows is based on the fact that the floating point format (in base two) approximates the base-2 logarithm. That is

So for a 32-bit single precision floating point number in IEEE format (where notably, the power has a bias of 127 added for the represented form) you can get the approximate logarithm by interpreting its binary representation as a 32-bit integer, scaling it by , and removing a bias of 127, i.e.

For example, 1.0 is represented by a hexadecimal number 0x3F800000, which would represent if taken as an integer. Using the formula above you get , as expected from . In a similar fashion you get 0.5 from 1.5 (0x3FC00000).

To get the square root, divide the logarithm by 2 and convert the value back. The following program demonstrates the idea. The exponent's lowest bit is intentionally allowed to propagate into the mantissa. One way to justify the steps in this program is to assume is the exponent bias and is the number of explicitly stored bits in the mantissa and then show that

/* Assumes that float is in the IEEE 754 single precision floating point format */
#include <stdint.h>
float sqrt_approx(float z)
{
	union { float f; uint32_t i; } val = {z};	/* Convert type, preserving bit pattern */
	/*
	 * To justify the following code, prove that
	 *
	 * ((((val.i / 2^m) - b) / 2) + b) * 2^m = ((val.i - 2^m) / 2) + ((b + 1) / 2) * 2^m)
	 *
	 * where
	 *
	 * b = exponent bias
	 * m = number of mantissa bits
	 */
	val.i -= 1 << 23;	/* Subtract 2^m. */
	val.i >>= 1;		/* Divide by 2. */
	val.i += 1 << 29;	/* Add ((b + 1) / 2) * 2^m. */

	return val.f;		/* Interpret again as float */
}

The three mathematical operations forming the core of the above function can be expressed in a single line. An additional adjustment can be added to reduce the maximum relative error. So, the three operations, not including the cast, can be rewritten as

	val.i = (1 << 29) + (val.i >> 1) - (1 << 22) + a;

where a is a bias for adjusting the approximation errors. For example, with a = 0 the results are accurate for even powers of 2 (e.g. 1.0), but for other numbers the results will be slightly too big (e.g. 1.5 for 2.0 instead of 1.414... with 6% error). With a = −0x4B0D2, the maximum relative error is minimized to ±3.5%.

If the approximation is to be used for an initial guess for Newton's method to the equation , then the reciprocal form shown in the following section is preferred.

Reciprocal of the square root

[edit]

A variant of the above routine is included below, which can be used to compute the reciprocal of the square root, i.e., instead, was written by Greg Walsh. The integer-shift approximation produced a relative error of less than 4%, and the error dropped further to 0.15% with one iteration of Newton's method on the following line.[18] In computer graphics it is a very efficient way to normalize a vector.

float invSqrt(float x) {
    float xhalf = 0.5f * x;
    union {
        float x;
        int i;
    } u;
    u.x = x;
    u.i = 0x5f375a86 - (u.i >> 1);
    /* The next line can be repeated any number of times to increase accuracy */
    u.x = u.x * (1.5f - xhalf * u.x * u.x);
    return u.x;
}

Some VLSI hardware implements inverse square root using a second degree polynomial estimation followed by a Goldschmidt iteration.[19]

Negative or complex square

[edit]

If S < 0, then its principal square root is

If S = a+bi where a and b are real and b ≠ 0, then its principal square root is

This can be verified by squaring the root.[20][21] Here

is the modulus of S. The principal square root of a complex number is defined to be the root with the non-negative real part.

See also

[edit]

Notes

[edit]
  1. ^ The factors two and six are used because they approximate the geometric means of the lowest and highest possible values with the given number of digits: and .
  2. ^ The unrounded estimate has maximum absolute error of 2.65 at 100 and maximum relative error of 26.5% at y=1, 10 and 100
  3. ^ If the number is exactly half way between two squares, like 30.5, guess the higher number which is 6 in this case
  4. ^ This is incidentally the equation of the tangent line to y = x2 at y = 1.

References

[edit]
  1. ^ Jackson 2011.
  2. ^ Fowler & Robson 1998.
  3. ^ a b Heath 1921.
  4. ^ Bailey & Borwein 2012.
  5. ^ Simply Curious 2018.
  6. ^ Guy & UKC 1985.
  7. ^ Steinarson, Corbit & Hendry 2003.
  8. ^ Wilkes, Wheeler & Gill 1951.
  9. ^ Campbell-Kelly 2009.
  10. ^ Gower 1958.
  11. ^ Goldschmidt, Robert E. (1964). Applications of Division by Convergence (PDF) (Thesis). M.Sc. dissertation. M.I.T. OCLC 34136725. Archived (PDF) from the original on 2015-12-10. Retrieved 2015-09-15.
  12. ^ "Authors". IBM Journal of Research and Development. 11: 125–127. 1967. doi:10.1147/rd.111.0125. Archived from the original on 18 July 2018.
  13. ^ Markstein 2004.
  14. ^ see: Generalized continued fraction#Notation
  15. ^ see: Continued fraction#Notations
  16. ^ see: Periodic continued fraction
  17. ^ Sardina 2007, 2.3j on p.10.
  18. ^ Lomont 2003.
  19. ^ Piñeiro & Díaz Bruguera 2002.
  20. ^ Abramowitz & Stegun 1964, Section 3.7.26.
  21. ^ Cooke 2008.

Bibliography

[edit]
[edit]