That may be useful in using one of those three rules in a subroutine (that totally incorporates the full rule for random function sent evaluated values) necessary for okay approximations where the error in approximating is good enough. ... So what I learned today were: Simpson's Rule is the best! So are Texas Instruments TI-84 + CE calculators to have! 😂
Yes! Storing the function to use the alpha button is the way to go. Something else good to know is that you can store any of these answers or values you might need later in your calculator by using the stor-> button, then entering one of the green letters to bind the value to that letter, almost like a variable or constant. Now, that letter represents the value. This is especially useful when having to find the area between two curves when the intersections are decimal approximations, and you would otherwise have to type the whole decimal.
The trick with storing intersections is that when the graph window is pointing to an (x,y) value, you can quit to the Home Screen and use “ x [sto->] A”, for example to store the x coordinate from the graph into the free variable A. Then you can integrate from 0 to A or something like that. Do the quit grapher -> store X on the Home Screen sequence immediately after getting the Intersection point displayed (without hitting trace or any buttons on the arrow pad to move the graph cursor around) for max precision.
That may be useful in using one of those three rules in a subroutine (that totally incorporates the full rule for random function sent evaluated values) necessary for okay approximations where the error in approximating is good enough. ... So what I learned today were: Simpson's Rule is the best! So are Texas Instruments TI-84 + CE calculators to have! 😂
Yes! Storing the function to use the alpha button is the way to go. Something else good to know is that you can store any of these answers or values you might need later in your calculator by using the stor-> button, then entering one of the green letters to bind the value to that letter, almost like a variable or constant. Now, that letter represents the value. This is especially useful when having to find the area between two curves when the intersections are decimal approximations, and you would otherwise have to type the whole decimal.
The trick with storing intersections is that when the graph window is pointing to an (x,y) value, you can quit to the Home Screen and use “ x [sto->] A”, for example to store the x coordinate from the graph into the free variable A. Then you can integrate from 0 to A or something like that. Do the quit grapher -> store X on the Home Screen sequence immediately after getting the Intersection point displayed (without hitting trace or any buttons on the arrow pad to move the graph cursor around) for max precision.
Thanks so much for showing that calculator trick! This will help me so much on calculus homework. Unfortunately, I’m not allowed my ti-84 on tests😢
4 2 4. The famous Brazilian line up.
any tips for a casio991ex clswiz calculator though?
My question is : lim(x~1) the function sqrt(x)/sqrt(x) -1
Ooo… now do Gaussian quadrature
Welcome to like 2008-era calculator tricks, lol. Are your college calculus tests all no-calculator?
We actually let students use graphing calculators. Btw, I agree with you that this is so like 20 years ago 😆
👍👍👍👍👍
t-shirts are for loosers, I'm wearing ϕ-shirt :D