Estimating Limits from Tables - Complete Interactive Lesson
Part 1: Why Use a Numerical Table?
📊 Estimating Limits from Tables
Part 1 of 4 — Why use a numerical table?
Topics in This Part
| Section |
|---|
| The Big Idea |
| 🔑 Choosing Good -Values |
| When Tables Help vs. When They Don't |
🔑 Why this matters: When you cannot just plug in (because of or an undefined point), a table lets you watch the outputs settle.
💡 The Big Idea
To estimate numerically, you pick -values close to — closer and closer — and read off in a table. If the outputs settle on a single number , then is the estimated limit.
💡 You are not plugging in . You are watching what does as approaches .
A clean example
Estimate .
Outputs settle on 7 from both sides. So (and indeed equals 7).
🔑 Choosing Good -Values
A useful table approaches from both sides with values that get visibly closer:
- Left side:
- Right side:
💡 Use at least 3 values per side, decreasing in distance by powers of 10. This makes the trend obvious.
Beware: bad table choices
| Bad table | Why |
|---|---|
| Only | You miss the left-hand behavior — could be a jump |
| Big spacing () | Outputs may not have "settled" yet |
| Skipping past | OK — never include in the table; the limit is about behavior near , not at |
✅ When Tables Help vs. When They Don't
| Situation | Use a table? |
|---|---|
| Direct substitution gives a clear number | No — just substitute |
| You get or (indeterminate form) | Yes — table gives an estimate |
| The function is given by data only | Yes — table is your only tool |
| Function oscillates wildly (like ) | ⚠️ Tables can mislead — see Part 4 |
⚠️ A table gives an estimate, not a proof. On the AP exam, "from the table" answers are valid, but if asked to justify, algebra (or theorems) outranks numerical evidence.
Concept Check 🎯
Pick the closest -values 🧮
You want to estimate . Type three values approaching 7 from the LEFT, smallest distance first (use comma separation; for you would type 1.999,1.99,1.9):
Part 2: Building a Two-Sided Table
📊 Building a Two-Sided Table
Part 2 of 4 — From rows of numbers to a limit estimate
Topics in This Part
| Section |
|---|
| 🔑 The Two-Sided Table Format |
| Worked Example: |
| Reading the Limit Off the Table |
🔑 Why this matters: Tables shine on forms. You see what the function "wants" to be, even when substitution fails.
🔑 The Two-Sided Table Format
For , build:
| Approach from the LEFT | Approach from the RIGHT | |
|---|---|---|
| , , | (skip ) | , , |
Compute at each , then ask:
- Are the left outputs settling on a value ?
- Are the right outputs settling on a value ?
- Is ? If yes, that common value is your estimate. If no → DNE.
📝 Worked Example:
Estimate . Direct substitution gives — indeterminate.
- Left side settles on .
- Right side settles on .
- , so .
💡 Sanity check: factor — for , which gives 2 at . The table agrees.
📖 Reading the Limit Off the Table
When outputs agree to the precision shown, round to a "clean" number — usually the value the digits are clearly converging toward.
| Sample outputs | Best estimate |
|---|---|
| (recognize the digits!) |
🔑 Recognize famous decimals: .
Concept Check 🎯
Match the table to the limit 🔽
Part 3: Recognizing DNE from a Table
🚫 Recognizing DNE from a Table
Part 3 of 4 — Spotting jump, blow-up, and oscillation in numerical data
Topics in This Part
| Section |
|---|
| Jump (the "step" pattern) |
| Blow-up (numbers explode) |
| Oscillation (numbers won't settle) |
🔑 Why this matters: Tables don't just give limits — they expose which way a limit fails.
1️⃣ Jump
Two clean values that disagree across .
For near 0:
Left → , right → . Jump. DNE.
2️⃣ Blow-up
Magnitudes balloon as approaches .
For near 0:
Both sides race to . We describe this as , but the limit does not exist as a finite number.
💡 Signature: outputs grow by factors of 10 or more as moves by factors of 10.
3️⃣ Oscillation
Outputs bounce around with no convergence.
For near 0:
No pattern, no settling — and choosing different -values gives wildly different outputs. Oscillation. DNE.
⚠️ This is the case where tables can trick you: pick the "wrong" -values and you might see a fake pattern. Always sanity-check with the algebraic form.
Diagnose the failure mode 🎯
Read the table 🧮
A table for shows: , , , .
1) Left-hand limit estimate: ?
2) Right-hand limit estimate: ?
3) Does exist? Type yes or no:
4) Failure mode (jump, blowup, oscillation, or none):
Part 4: Common Pitfalls
⚠️ Common Pitfalls with Numerical Tables
Part 4 of 4 — When tables mislead you
Topics in This Part
| Section |
|---|
| Calculator Precision Errors |
| The Oscillation Trap |
| Tables vs. Algebraic Proof |
🔑 Why this matters: A wrong-looking table can convince you of a wrong limit. Knowing the traps protects your AP score.
🧮 Pitfall 1: Calculator Precision
Calculators store finite digits. For near 0:
| (!) |
For tiny , the numerator rounds to exactly 0 in finite precision — catastrophic cancellation. The displayed limit appears to be 0, but the true limit is .
💡 Lesson: trust the trend across mid-range values, not the noisiest few. And compare with algebra/theorems when you can.
🌊 Pitfall 2: The Oscillation Trap
Consider at . If you sneakily pick for integer , then — every single time.
This table screams "limit = 0" — but the true limit DNE because also hits infinitely often. Different -sequences give different outputs.
⚠️ Lesson: for trigonometric arguments racing to infinity, always sanity-check with multiple "kinds" of -values.
📏 Pitfall 3: A Table Is an Estimate, Not a Proof
On the AP exam:
| Asked to... | What's allowed |
|---|---|
| Estimate the limit | A clean numerical table is fine |
| Find the limit | Use algebra (factoring, rationalizing, …) when possible |
| Justify an answer | Cite a theorem (continuity, squeeze, etc.) — tables alone usually don't earn justification points |
🔑 Bottom line: tables are a great first step and a great sanity check, but algebraic methods are the gold standard for finding exact values.
Pitfall Check 🎯
Exit Check ✅