My last post was about how the TI-83/84 calculates integrals (how fnInt works), and how it messes up for when you have large intervals.

I just came from my Multivariable Calculus class, where each student had done some thinking about it. One investigated the Gauss-Kronrod quadrature. A couple others played around with fnInt and came up with some bounds for when fnInt was good and when fnInt was bad for our function .

What we did today was to start investigating fnInt in a different way. (Yeah, my goal was to start triple integrals today… but this was way more exciting in the moment…)

We looked at and used fnInt to calculate it.

It turns out that fnInt goes crazy and fails to be a good estimator at a particular large interval.

So we continued looking at , , , etc. We looked at where fnInt broke down.

This is what we found out:

The left column is the exponent in . The right column is the last integer you can integrate (using fnInt) to so that doesn’t give a terrible estimation of the area. (Recall we’re integrating from **1** onwards, not from 0.)

My kids are going to go home and see what they can make of this data. We hope we can use it to come up with a prediction for where fnInt will go awry for estimating the area for something like ? And maybe it’ll also work for non-integral values, like ? We’ll see.

…Hopefully we’ll start on triple integrals soon, though…

### Like this:

Like Loading...

*Related*

This is really interesting. I’m curious as to what you find out.

See my comment on tolerance in your previous post. Increasing the tolerance for each numerical integration should increase the maximum domain that still yields a reasonable result. For x^(-21), fnInt worked up to [1,530], yielding an answer of 1/2 before the calculator decided it wasn’t worth its time for 531 and called it 9.86E-11.

[…] is a way to see how we are succeeding, or failing, at that.” Recommended posts: “fnInt reprise” and “TI-83/84 […]