_ [Contents]

Copyright © 2007 jsd

1  Fundamental Suggestions

Here are some hints on how to do basic math calculations.

These suggestions are intended to make your life easier. Some of them may seem like extra work, but really they cause you less work in the long run.

This is a preliminary document, i.e. a work in progress.

1.    Be tidy and systematic. Whenever you have data in tables, especially when place-value is important, be sure to keep things lined up in neat columns and neat rows. See section 4 for an example of how this works in practice.

2.    If your columns are wobbly, get a pad of graph paper and see if that helps. If you don’t have a supply of store-bought graph paper, you can make graph paper on your computer printer. There are freeware programs that do a very nice job of this.

If that’s too much bother, start with a plain piece of paper and sketch in faint guidelines when necessary.

3.    Paper is cheap. If you find that you are running out of room on this sheet of paper, get another sheet of paper, rather than squeezing the calculation into a smaller space. See section 4 for an example of using extra paper to achieve a better result.

4.    The whole calculation should be structured as a succession of true statements. The first statement is true, the next statement is true, and the statement after that, et cetera. Each statement is a consequence of the previous statements (in conjunction with known theorems, and the “givens” of the problem). Finally, we get to the bottom line, and we know it is true. An example of this can be seen in reference 1.

5.    Sometimes, especially for long and/or complex calculations, it helps to organize your calculation in two columns. An example of this can be seen in reference 1. In the left column, you write an equation. In the right column, make a note as to how you derived that equation. (Numbering all your equations makes this easier.) If there isn’t enough width to do this easily, turn the paper 90 degrees, so it becomes wider and less tall. (Writing paper isn’t suitable for this, so use graph paper ... or lacking that, plain white paper.)

6.    Avoid writing down an un-named number like 17, or an un-named expression like a+17 ... because you might forget the meaning thereof. Instead, whenever possible, write down an equation such as b=a+17. That way you can point to every item on the page and say that’s true, that’s true, that’s true... in accordance with the strategy described in item 4.

If the meaning of variables such as a and b is not obvious, write down a legend somewhere (like the legend of a map), explaining in a sentence or two the meaning of each variable. That is, a name is not the same as an explanation. Do not expect the structure of a name or symbol to tell you everything you need to know. Most of what you need to know belongs in the legend. The name or symbol should allow you to look up the explanation in the legend.

7.    It is important to be able to go back and check the correctness of the calculation you have done. See section 4 and/or reference 1 for examples of what this means in practice.

8.    As a corollary of item 7: Don’t perform surgery on your equations. That is, once you write down a correct equation, don’t start crossing out terms (or, worse, erasing terms) and replacing them with other expressions. Such a substitution may be “mathematically” correct, if the replacement is equal to the thing being replaced ... but it is a bad strategy, because it makes it hard for you to check your work. Instead, write a new equation. Leave the old equation as it is. Paper is cheap. An example of this can be seen in reference 1.

9.    Keep track of the units for each expression. For example, the statement “x=2.5 inches” means something rather different from “x=2.5 meters” ... and if you shorthand it as “x=2.5” you’re just asking for trouble.

Sometimes the penalty for getting this wrong is 328 million dollars, as in the case of the Mars Climate Orbiter (reference 2).

logo-98t-s
Figure 1: Mars Climate Orbiter mission logo

Most computer languages do not automatically keep track of the units, so you will have to do it by hand, in the comments. If the calculation is nicely structured, it may suffice to have a legend somewhere, spelling out the units for each of the variables. If variables are re-used and/or converted from one set of units to another, you need more than just a legend; you will need comments (possibly quite a lot of comments) to indicate what units are being used at each point in the code.

One policy that is sometimes helpful (but sometimes risky) is to convert everything to SI units as soon as it is read in, even in fields where SI units are not customary. Then you can do the calculation in SI units and convert back to conventional units (if necessary) immediately before writing out the results. (This is problematic when writing an “intermediate” file. Should it be SI or customary? How do you know the difference between an “intermediate” result and a final result?)

It is certainly possible for computer programs to keep track of the units automatically. A nice example is reference 3. It is a shame that such features are not more widely available

10.    The factor-label method is a convenient and powerful way of converting units when necessary. The correctness of this method is a direct consequence of the axioms of algebra, since it starts by multiplying by unity, which is allowed by the axioms.

11.    Haste makes waste, especially with multi-step processes. If you work methodically, you’ll get the right answer the first time, and that’s all there is to the story. If you try to do it twice as fast, you’ll get the wrong answer, and then you’ll have to do it over again ... and again ... and again.

2  Multiple Methods of Solution

Here’s a classic example: The task is to add 198 plus 215. The easiest way to solve this problem in your head is to rearrange it as (215 + (200 − 2)) which is 415 − 2 which is 413. The small point is that by rearranging it, a lot of carrying can be avoided.

One of the larger points is that it is important to have multiple methods of solution. This and about ten other important points are discussed in reference 4.

3  Drawing Inequalities

The classic "textbook" diagram of an inequality uses shading to distinguish one half-plane from the other. This is nice and attractive, and is particularly powerful when diagramming the relationship between two or more inequalities, as shown in figure 2.

inequalities-shaded
Figure 2: Inequalities Represented using Shading

However, when you are working with pencil and paper, shading a region is somewhere between horribly laborious and impossible.

It is much more practical to use hatching instead, as shown in figure 3.

inequalities
Figure 3: Inequalities Represented using Hatching

Obviously the hatched depiction is not as beautiful as the shaded depiction, but it is good enough. It is vastly preferable on cost/benefit grounds, for most purposes.

Some refinements:

4  Long Multiplication

4.1  Background

Short multiplication refers to any multiplication problem where you just memorize the answer. You must memorize the multiplication table for everything from 0×0 through 9×9. You get the next step (up to 10×10) practically for free, and it is often worthwhile to keep going up to 12×12.

Long multiplication refers to multiplying larger numbers. This works by breaking the numbers down into their individual digits, then multiplying on a digit-by-digit basis (using the short multiplication facts for zero through nine) and then combining all the results with due regard for place value.

4.2  The Algorithm

We now discuss a nice way to do long multiplication. The first steps are shown in figure 5. There are two parts to the figure, representing two successive stages of the work. Anything shown in black is something you actually write down, whereas anything shown in color is just commentary, put there to help us get through the explanation the first time.

long-mult-partway
Figure 5: Long Multiplication – Part Way Through

We start with the leftmost part of the figure. This is just the statement of the problem, namely 4567×321. The important point here is to line up the numbers as shown, so that the ones’ place of the top number lines up with the ones’ place of the bottom number, et cetera. Keeping things aligned in columns is crucial, since the colums represent place value. If you have trouble keeping things properly lined up, use grid-ruled paper. You can see such a grid in figure 5. If you don’t have grid-ruled paper, you can always sketch in some guide lines. As mentioned in item 1, tidiness pays off.

You may omit the multiplication sign (×) if it is obvious from context that this is a multiplication problem (as opposed to an addition problem).

Tangential remark: Some people attempt to call one of these numbers the multiplier and the other the multiplicand, but since multiplication is commutative the distinction is meaningless. People often use the terms in ways inconsistent with the supposed definition. I call both of them multiplicands, which is more-or-less Latin for “thing being multiplied”. In figure 6 we have two things being multiplied. Note that since multiplication is associative, you could easily have many things being multiplied, as in 12×32×65×99, in which case it again makes sense to call each of them multiplicands, and it is obviously hopeless to attempt to distinguish “the” multiplier from “the” multiplicand. As a related issue, there are also holy wars as to whether 4567×321 means 4567 “times” 321, or 4567 “multiplied by” 321. Again the distinction is meaningless. Don’t worry about it.

If one of the multiplicands is longer than the other, it will usually be more convenient to place the longer one on top. That’s not mandatory, but it makes the calculation slightly more compact.

We now proceed digit by digit, starting with the rightmost digit in the bottom multiplicand, which in this case is a 1. We multiply this digit into each digit of the upper multiplicand, working in order right-to-left, which makes sense because it is the direction of increasing place value (even though it is opposite to the direction of reading normal text).

We place these results in order in row c, with due regard for place value. The 1×7 result goes in the ones’ place, the 1×6 result goes in the tens’ place, and the 1×5 result goes in the hundreds’ place, and so forth. Actually, multiplication by 1 is so easy that you could just copy the whole number 4567 into row c without thinking about it very hard.

You may wish to leave a little bit of space above the numbers in row c, for reasons that will become apparent later.

That is all we need to do with the low-order digit of the bottom multiplicand. We now move on to the next digit, working right-to-left. In this case it is a 2.

Again we multiply this digit into each digit of the upper multiplicand. The result of the first such multiplication is 2×7=14, which we place in row d. This is most clearly seen in the middle column of the figure 6. Alignment is crucial here. The 14 must be aligned under the 2 as shown. That’s because it “inherits” the place value of the 2.

Next we multiply 2×6=12. You might be tempted to write this in row d, but there is no room for it there, so it must go on row e, as shown in the middle column of the figure. Again alignment is critical. The 12 is shifted one place to the left of the 14, because it inherits additional place value. It inherits some from the 2 and some from the 6. Since we are working systematically right-to-left, you don’t need to think about this too hard; just remember that each of these short-division products must be shifted one place to the left of the previous one.

We have now more than half-way finished. We have reached the stage shown in figure 5.

Figure 6 shows all the steps.

long-mult
Figure 6: Long Multiplication

The next step is the 2×5=10 multiplication. There is room for this on row d, which is a good place to put it. Next we do the 2×4=8 multiplication. There is room for this on row e, which is a good place to put it. Note the pattern of placing successive short-division results on alternating rows. This is guaranteed to work, because the product of two one-digit numbers can never have more than two digits.

At this point (or perhaps earlier), if you are not using grid-ruled paper, you should lightly sketch in some vertical guide lines, as shown by the dashed lines in figure 7. The tableau has become large enough that there is some risk of messing up the alignment, i.e. putting things into the wrong columns, if you don’t put in guide lines.

That’s all for the “2” digit in the bottom multiplicand. We now progress to the “3” digit. The work proceeds in the same fashion. All the short-multiplication results are put in rows f and g.

In the tableau, you can see where everything comes from. The color-coded background indicates which digit of the upper multiplicand was involved, and the row indicates which digit of the bottom multiplicand was involved.

At this point you can draw a line under row g as shown in the figure. All that remains is a big addition problem, adding up rows c through g inclusive. You can use the space above row c to keep track of carries if you wish, but this is not mandatory. (There are never very many carries, so keeping track of them is easy, no matter how you do it. Some people just count them on their fingers.)

The result of the addition is the result of the overall multiplication problem, as shown on row h.

Let’s do another example, as shown in figure 7, which illustrates one more wrinkle.

long-mult-2
Figure 7: Another Long Multiplication

This example calls attention to the situation where some of the short-multiplication products have one digit, while others have two. You can see this on row c of the figure, where we have 3×3=9 and 3×8=24. In most cases it is safer to pretend they all have two digits, which is what we have done in the figure, writing 9 as 09. Similarly on line d we write 6 as 06. This makes the work fall into a nice reliable pattern. It helps you keep things lined up, and makes the work easier to check.

In some cases, such as 345×1 or 432×2, all the short-multiplication products have one digit, so you can write them all on a single line, if you wish. This saves a little bit of paper. On the other hand, remember the advice in item 3: paper is cheap. You may find it helpful to write the short-multiplication products as two digits even if you don’t have to.

Mathematically speaking, writing one-digit products as two digits is unconventional, but it is entirely correct. It has the advantage of making the algorithm more systematic, and therefore easier to check.

In any case, the result of the addition is the result of the overall multiplication problem, as shown on row g of figure 7. That’s all there is to it.

4.3  Remarks

This algorithm uses two rows of intermediate results for each digit in the bottom multiplicand (except when the digit is zero or one). This has two advantages: First of all, you don’t need to do any adding or carrying as you go along; you just write down the short-multiplication results “as is”. Secondly, it makes it easy to check your work. Each of the short-multiplication results is sitting there in an obvious place, almost begging to be checked.

This differs from the old-fashioned “textbook” approach, which uses only one row per digit, as shown below. The old-fashioned approach supposedly uses less paper – but the advantage is slight at best, and if you allow room keeping track of “carries” throughout the tableau, the advantage becomes even more dubious.

What’s worse is that the old-fashioned approach is significantly more laborious. It may look more compact, but it involves more work. You have to do the same number of short multiplications, and a greater number of additions. It requires you to do additions (including carries) as you go along.

Last but not least, it makes it much harder to check your work.

  4567
 × 321
  4567
 9134 
13701  
1466007

The old-fashioned approach.
Not recommended.

Remember, paper is cheap (item 3) and it is important to be able to check your work (item 7).

5  Long Division

The usual “textbook” instructions for how to do long division are both unnecessarily laborious and unnecessarily hard to understand. There’s another way to organize the calculation that is much less mysterious and much less laborious (especially when long multi-digit numbers are involved).

Note that as discussed above, keeping things lined up in columns is critical. It may help to use grid-ruled paper, or at least to sketch in some guidelines.

5.1  The Algorithm : Using a Crib

Figure 8 shows an example. The assignment is to divide 7527 by 13.

long-div
Figure 8: Long Division

After writing down the statement of the problem, and before doing any actual dividing, it helps to make a crib, as shown in the lower left of the figure. This is just a multiplication table, showing all multiples of 13 (or, more generally, all multiples of the assigned divisor). It is super-easy to construct such a table, since no multiplication is required. Successive addition will do the job. We need all the multiples from ×1 to ×9, but you might as well calculate the ×10 row, by adding 117+13, as a check on all the additions that have gone before.

The first step is to consider the leading digit of the dividend (which in this case is a 7). Since this is less than the divisor (13), there is no hope of progress here, so we proceed to the next step.

Now consider the first two digits together, namely the 7 and the 5. Look at the crib to find the largest entry less than or equal to 75. It is 65, as in 5×13=65. Write copy this entry to the division problem, on row b, directly under the 75. Since this came from row 5 of the crib, write a 5 on the answer line, aligned with the 75 and the 65, as shown. Check the work, to see that 5 (on the answer line) times 13 (the divisor, on line a), equals 65 (on line b).

Now do the subtraction, namely 75−65=10, and write the result on line c as shown.

We now shift attention from the first column to the middle column of figure 8. Bring down the 2 from the dividend, as shown by the red arrow in the middle column of the figure. So now the number we are working on is 102, on line c.

The steps from now on are a repeat of earlier steps.

Look at the crib to find the largest entry less than or equal to 102. It is 91, as in 7×13=91. Write copy this entry to the division problem, on row d, directly under the 102. Since this came from row 7 of the crib, write a 7 on the answer line, aligned with the 102 and the 91, as shown. Check the work, to see that 7 (on the answer line) times 13 (the divisor, on line a), equals 91 (on line d). Do the subtraction.

As a check on the work, when doing this subtraction, the result should never be less than zero, and should never be greater than or equal to the divisor. Otherwise you’ve used the wrong line from the crib, or made an arithmetic error.

We now shift attention to the rightmost column of figure 8. Bring down the 7, look in the crib to find the largest entry less than or equal to 117, which is in fact 117, as in 9×13=117. Since this came from line 9 of the crib, write a 9 on the answer line, properly aligned.

The final subtraction yields the remainder on line g. The remainder is zero in this example, because 13 divides 7527 evenly.

5.2  Remarks

The crib plays several important roles.

Perhaps the crib’s most important advantage, especially when people are first learning long division, is that the crib removes the mystery and the guesswork from the long division process. This is in contrast to the “trial” method, where you have to guess a quotient digit, and you might guess wrong. Using the crib means we never need to do a short division or trial division; all we need to do is skim the table to find the desired row.

We have replaced trial division by multiplication and table-lookup. Actually we didn’t even need to do any multiplication, so it would be better to say we have replaced trial division by addition.

Another advantage is efficiency, especially when the dividend has many digits. That’s because you only need to construct the crib once (for any given divisor), but then you get to use it again and again, once for each digit if the dividend. For long dividends, this saves a tremendous amount of work. (This is not a good selling point when kids are just learning long division, because they are afraid of big multi-digit dividends.) Setting up the crib is so fast that you’ve got almost nothing to lose, even for small dividends.

Another advantage is that it is easy to check the correctness of the crib. It’s just sitting there begging to be checked.

When bringing down a digit, you may optionally bring down all the digits. For instance, in the middle column of figure 8, if you bring down all the digits you get 1027 on row c. One advantage is that 1027 is a meaningful number, formed by the expression 7527−13×5×102. This shows how the steps of the algorithm (and the intermediate results) actually have mathematical meaning; we are not not blindly following some mystical mumbo-jumbo incantation. I recommend that if you are trying to understand the algorithm, you should bring down all the digits a few times, at least until you see how everything works.

A small disadvantage is that bringing down all the digits requires more copying. The countervailing small advantage is that it may help keep the digits lined up in their proper columns. Whether the advantages outweigh the cost is open to question, and probably boils down to a question of personal preference.

Another remark: Division is the “inverse function” of multiplication. In a profound sense, for any function that can be tabulated, you can construct the inverse function – if it exists – by switching columns in the table. That is, we interchange abscissa and ordinate: (x,y)↔(y,x). That’s why we are able to perform division using what looks like a multiplication table; we just use the table backwards.

6  References

1.
John Denker, “Balancing Reaction Equations using Gaussian Elimination” ./gauss-elim.htm

2.
NASA Mars Climate Orbiter Fact Sheet: http://mars.jpl.nasa.gov/msp98/orbiter/fact.html
Mission patch:http://mars.jpl.nasa.gov/msp98/gif/m98patch.gif
Small logo: http://mars.jpl.nasa.gov/msp98/gif/logo-98t-s.gif

3.
Google Calculator. Example: furlongs per fortnight, converted to SI units. http://www.google.com/search?q=1+furlong+per+fortnight+in+m/s

4.
John Denker, “Teaching (and Learning) Thinking Skills” ./thinking.htm
[Contents]

Copyright © 2007 jsd

_