This post somehow got lost a year ago. I am reposting it here.
Years ago I wrote an assembly language routine that drew circles with a pen plotter. This entailed approximating the arc of a circle with a series of small horizontal and vertical steps. I was proud of the method because its critical loop used only additions and multiplications by 2 (bit shift left in assembly language) and was very fast.
So I thought this summer that if I can draw a circle fast, I ought to be able to calculate fast. I wrote a routine in the Python programming language, optimized it as best I could and here are my results. (My method also allowed me to calculate – also very slowly)
This is just terribly slow. As I read the table, it takes 10 times the time to get one more digit of . I stopped when the program ran 524 seconds and still hadn’t calculated 9 digits of . I will describe the method I used and the reason it was so slow in the rest of the article.
Our object is to trace the arc of a circle as closely as possible using only up and down, and right and left movements of one step. Start with a point on a circle with radius , for example , so that . Without loss of generality assume we are in the first quadrant and we are drawing the circle in a counterclockwise direction. Since we can only take one step vertically or horizontally at a time, we either increase by or decrease by . If we increase by , the square of the distance of the new point from the origin is . The change in the distance squared () is . Call this . If we decrease by , the change in is . Call this . We choose to keep nonnegative and as small as possible. So we calculate and , add each to separately, and see which result is nonnegative and smallest.
The cool thing is that each time, our new is just the old plus or depending on which change in variable we chose. Here is why. Say we start at on the circle and choose to increase by . Now . Call the new , so that we are now at . As an example now say we wish to increase by so that our new is .
The is just the old , so we just add to the old to get the updated and continue. By the way this method can be used to “draw” any conic section with axes parallel to the coordinate axes.
To calculate , every time is increased, add the current to a area accumulator. Stop the process when . From the outlined area in the diagram subtract the area of the triangle OAB and what’s left is the approximate area of an eighth of a circle. Calculate . This is basically a crude integration.
Here are two python program fragments that show the algorithm. The first is the original version which was written for clarity to stay close to the mathematics and the second was optimized for speed – not that it helped much.
It is fairly easy to see where the error comes from. By staying just outside of the circle – at most one vertical or horizontal step, the area is overestimated by at most . The calculated area is at most . Dividing by gives . Increasing ten times moves the decimal point over one.
My discovery of “drawing” conic sections by looking only one step ahead was satisfying and at least years ago useful. I was sobered by the sad slow algorithm that I devised to calculate . A method with linear efficiency is really slow. I now have more than a theoretical understanding of this fact.