We know that finding the area under a function reverses the derivative, which is useful for solving problems. But some areas are harder to calculate than others.
For example, consider the following car. It begins its journy travelling at a rate of 60mph, and then slows down over time.
The velocity at any given time is represented by the following function:
To find the total distance the car travels in 3 hours, we need to find the shaded area under the function.
Finding this area seems... hard, to say the least. For all of the previous car examples, we had some area formula we could use. But now we don't!
Still, you might be able to estimate the area. In fact, give it a try! Take a look at the following graph and type in your best guess for the area under the curve.
Hint: Each grid square has an area of 5 miles. Can you count (roughly) how many grid squares are covered?
You didn't type in an estimate in the previous section! Maybe you didn't notice the box. Maybe you were just feeling lazy. Or maybe, just maybe, you knew that we would discover a better method, so spending your time on the first attempt wasn't actually that important. Well played.
Let's try estimating the area using vertical rectangles only. This estimate won't be perfect, and you might be able to think of ways to improve it. But it has two crucial benefits that we'll discuss soon.
On the graph above I've placed some vertical rectangles. Use the table below to calculate their areas.
Take a look at the area estimate produced by using the method above. Do you think that it is too high or too low? How does it compare to your original guess?
Alright, we have a structured way to make estimates. This strategy is called a Riemann sum. But why do it this way, rather than by some other method?
Riemann sums have two main benefits:
If you want to get a better estimate, being able to increase the number of rectangles is key. Try changing the number of rectangles using the slider below and watch what happens.
Hmmm... As the number of rectangles increases, the estimate improves. In fact, it seems to be converging to a "perfect" answer.
We new have an estimate that can become arbitrarily good simply by increasing N, the number of rectangles. That's really powerful! No matter how close you want to get to the "true" area, you can do it simply by increasing N.
But what if you don't want an estimate. Can we find the exact answer?
This is where your calculus spidey senses might start tingling.
When you have an estimate that's getting closer and closer and closer to some exact answer, what do you do? Take a limit, of course!
We want to take the following limit:
This is great in theory, but we need a way to represent our area estimate as math so that we can actually take the limit.
The area estimate is the sum of a bunch of rectangle areas, where each area is a height times a width. Each width is one Nth of the full width and each height is the value of the function on the left-hand side of the rectangle.
Let's go ahead and try to convert each part of this definition into math. I'll lay out the options, and you arrange the fridge magnets to make it all work:
Description | Math |
---|---|
The sum of a bunch of rectangle areas... | Empty space |
Where each area is a height times a width... | Empty space |
Each width is one Nth of the full width... | Empty space |
And each height is the value of the function... | Empty space |
On the left-hand side of the rectangle. | Empty space |
When you put all of these parts together, you get the following:
Amazing! Now we just look back to our original goal... We wanted to take the limit of this estimate as of the area estimate to get the actual area:
Now that we can take a limit, we can let . This means we can get an exact answer for the area under the function, which gives us the exact distance that the car travelled.
Drag the slider all the way to the end for the satisfaction of seeing infinity:
So it turns out that the exact answer is ≈83.178.