4.10.23 · D3Advanced Topics (Elite Level)

Worked examples — Uniform continuity — difference from pointwise

2,915 words13 min readBack to topic

This page is a workout. The parent note built the ideas; here we drill every kind of case the topic can throw at you until none is unfamiliar. If a word or symbol looks new, we re-earn it on the spot.

Two symbols we use constantly, spelled out in words:

  • (epsilon) — the output tolerance: how close the two heights are allowed to differ. "Up–down" distance.
  • (delta) — the input closeness we are allowed to demand. "Sideways" distance.
  • — the sideways gap; — the up–down gap. The vertical bars mean "distance, always positive".

The scenario matrix

Every uniform-continuity question falls into one of these cells. The examples below hit each one, and the label after each example name tells you which cell.

Cell What makes it that cell Example
A. Bounded compact domain closed & bounded — Heine–Cantor guarantees UC Ex 1
B. Unbounded domain, amplifier grows $ x+y
C. Bounded but NOT closed, blow-up at open end , near → fails Ex 3
D. Non-Lipschitz yet still UC slope but tamed by a root bound Ex 4
E. Lipschitz constant hunt (uses MVT) bounded derivative → explicit Ex 5
F. Oscillation degenerate case on — bounded output, still fails Ex 6
G. Limiting / boundary-repair extend to an endpoint to restore UC Ex 7
H. Real-world word problem temperature-sensor closeness rule Ex 8
I. Exam twist: sum/product of UC is UC on ? Ex 9

We will also touch the degenerate zero cases (constant function, single-point domain) inside Ex 1.


Ex 1 — Cell A: compact domain, and the degenerate zeros

Forecast: guess — on a finite closed stretch, does one survive? Write your bet before reading.

  1. WHAT: write the output gap using the amplifier factorisation. Why this step? Factoring exposes the multiplier that turns an input gap into an output gap — the whole behaviour lives in that factor.

  2. WHAT: bound the amplifier on this domain. Since , Why this step? Because the domain is bounded, the dangerous factor is capped by a fixed number — no dependence on where we are. That is the seed of uniformity.

  3. WHAT: choose . Take . Then Why this step? contains only and the number — no . That "no " is literally the definition of uniform continuity.

  4. Degenerate zeros.

    • Constant : output gap is always , so any works — vacuously uniformly continuous.
    • One-point domain : the only pair is , gap — again vacuously UC. Why this step? Extreme inputs must never surprise us; here they are the easiest cases, not exceptions.

Verify: pick . Take the worst nearby pair : , and . ✓


Ex 2 — Cell B: unbounded domain, amplifier explodes

Forecast: which grows faster as we march right — the input gap we're allowed, or the output gap it produces?

  1. WHAT: fix the target . Suppose a rescuer hands us some . Why this step? To negate "there exists a ", we defeat an arbitrary .

  2. WHAT: engineer the pair Their gap is — legally close. See

    Figure — Uniform continuity — difference from pointwise
    (figure: the parabola with a yellow pair at for a larger and a red pair at for a smaller — both a fixed sideways gap apart; the red vertical output gap is visibly far taller — showing that as shrinks the engineered point marches right into steeper territory). Why this step? We place the pair far out where the slope is huge, keeping them sideways-close.

  3. WHAT: compute the output gap. Why this step? The output gap exceeds no matter how small was — the negation is complete.

Verify: : ✓, and ✓.


Ex 3 — Cell C: bounded but not closed, blow-up at an open end

Forecast: "bounded" felt safe in Ex 1 — why might it fail here?

  1. WHAT: note is not closed: the point is missing, and as . Why this step? Heine–Cantor Theorem needs closed AND bounded (Compactness). Missing breaks closedness, so no guarantee — we test directly.

  2. WHAT: fix ; take any ; pick points hugging : Gap . See

    Figure — Uniform continuity — difference from pointwise
    (figure: the curve rocketing upward as it approaches the yellow dotted wall at ; a red pair of points near the wall shows a tiny sideways step producing a huge vertical leap). Why this step? The steepness lives near , so we crowd the pair against that wall.

  3. WHAT: measure the output gap. For this is . Why this step? Output gap as — beats any tolerance, so no single works.

Verify: : ✓, ✓.


Ex 4 — Cell D: non-Lipschitz yet uniformly continuous

Forecast: the slope near — same warning sign as . Why does survive where died?

  1. WHAT: Lipschitz would need a fixed with . Near the derivative , so no finite exists. Why this step? We first admit the easy test fails — Lipschitz is sufficient, not necessary.

  2. WHAT: prove the square-root inequality from scratch. Assume WLOG , so . Compare against : because (we only added the non-negative to the second factor while the first factor ). Taking square roots of gives Why this step? This is the engine of the whole example, so we derive it rather than quote it: replacing the smaller factor by the larger can only increase the product, and that larger product is exactly .

  3. WHAT: read off the growth. The output gap grows only like — a gentler growth. Unlike , the function stays bounded and finite everywhere, including at ; its graph flattens (not steepens) as grows. Compare the mild slope in

    Figure — Uniform continuity — difference from pointwise
    (figure: the green curve rising steeply from the origin then flattening; a red dot near marks where the slope is largest, yet the output stays finite).

  4. WHAT: choose . Then Why this step? depends on alone — uniformity achieved without Lipschitz.

Verify: . Worst near- pair : (boundary), , which is . ✓


Ex 5 — Cell E: hunt the Lipschitz constant via the Mean Value Theorem

Forecast: wiggles forever — does "forever" break uniformity like did?

  1. WHAT: compute the derivative and bound it. , and for all . Why this step? A bounded slope is the cleanest route to Lipschitz. Here — a single number for the whole line.

  2. WHAT: invoke the Mean Value Theorem. For any there is a between them with Why this step? MVT converts "bounded derivative" into "bounded output-to-input ratio", i.e. Lipschitz with .

  3. WHAT: choose (since ). Why this step? No in — uniform, even though the graph never stops oscillating. The wiggle is bounded in height and steepness, unlike 's ever-growing steepness.

Verify: . Take : ✓.


Ex 6 — Cell F: bounded oscillation that STILL fails

Forecast: the output never leaves — so how can output gaps blow past ?

  1. WHAT: fix ; take any . Choose two peaks/valleys of the wiggle near , indexed by a positive integer : Then and . Why this step? Near the graph oscillates infinitely fast, so a crest and a trough sit arbitrarily close together — see

    Figure — Uniform continuity — difference from pointwise
    (figure: the blue curve wiggling faster and faster toward ; a yellow dot marks a crest and a red dot a nearby trough, so two close inputs give an output jump of ).

  2. WHAT: check domain membership. For every integer the denominators satisfy , so both . Every is legal; no smallness assumption is needed. Why this step? We must confirm the engineered points actually live in the domain before using them, and here even already lands safely inside .

  3. WHAT: estimate the sideways gap so we can beat any . Subtracting the two fractions over a common denominator, So given any , pick large enough that this quantity is ; both points still lie in by step 2. Why this step? The explicit formula proves the crests bunch up at — we don't just assert it.

  4. WHAT: yet the output gap is Why this step? Bounded output does not save you — what matters is that close inputs can still give a fixed jump of . Frequency, not amplitude, kills uniformity.

Verify (n=1): , ; , output gap ✓.


Ex 7 — Cell G: limiting/boundary repair restores UC

Forecast: can plugging a single missing point turn a "maybe" into a guaranteed UC — and can we still write a concrete closeness rule?

  1. WHAT: compute the limit at the open end. Why this step? The only thing stopping compactness was the missing endpoint . If the function has a finite limit there, we can fill the hole continuously.

  2. WHAT: set . Now is continuous on the closed bounded interval . Why this step? is compact; unlike Ex 3's open , nothing runs off to infinity.

  3. WHAT (qualitative): apply Heine–Cantor Theorem: continuous on a compact set uniformly continuous. Why this step? We converted a boundary defect into a compact domain, and the theorem does the rest.

  4. WHAT (quantitative ): we build by hand, and we prove the slope bound rather than assert it. Write for (and by symmetry, since is even). Use the two standard inequalities valid for : Then the numerator obeys and (using , ) it also obeys . Hence So on all of . By the Mean Value Theorem this gives Lipschitz constant , so Why this step? Heine–Cantor guarantees a ; the Taylor-type bounds and turn "one checks" into a genuine everywhere-valid inequality , handing us an explicit .

Verify: the limit numerically: ✓; and the bound: the actual maximum of on is at , , consistent with our proven bound ✓, so is a safe (loose) Lipschitz constant.


Ex 8 — Cell H: real-world word problem

Forecast: does one closeness rule cover the whole run, or must it change over time?

  1. WHAT: find the steepest rate of change (bound the derivative). Why this step? Bounded slope on the compact interval gives Lipschitz via Mean Value Theorem — the physical version of "one rule everywhere".

  2. WHAT: Lipschitz bound: . Why this step? Turns "how fast can temperature move" into "how far apart two readings can be".

  3. WHAT: solve : minutes ( seconds). Why this step? depends only on the tolerance and the slope bound — not on which minute we sample. Uniformity = one compliance rule for the whole shift.

Verify: worst case near (steepest): , ; gap ✓. Units: ✓.


Ex 9 — Cell I: exam twist on products

Forecast: it is tempting to think "product of two well-behaved functions must be well-behaved." Bet yes or no before reading — the exam trap is that the answer is no.

  1. WHAT: test the derivative for a growing slope. At : , so . Why this step? An unbounded slope is the classic warning flag (recall ). The factor amplifies the oscillation's steepness without limit — so we suspect failure and go hunting for bad pairs.

  2. WHAT: engineer sideways-close, output-far pairs. Near (where , so ) take a nearby point with a fixed small : The sideways gap is ; choose so it is legally close. Then Why this step? With fixed the sideways gap never changes, but grows without bound as — this is the exact negation pattern from Ex 2.

  3. WHAT: conclude. For any candidate pick (so and ), then pick large enough that . Two points closer than with output gap above exist ⇒ is not uniformly continuous on . There is no rescuing . Why this step? Moral: uniform continuity is not closed under multiplication on unbounded domains — a genuine exam trap. (On any bounded it is fine, by Heine–Cantor.)

Verify: take , so , : , and . Doubling roughly doubles this gap ⇒ unbounded ✓.


Recall Scenario checklist to run on any function

Compact domain? → UC free (Heine–Cantor). Bounded derivative? → Lipschitz, . Slope or domain unbounded / open at a blow-up? → hunt bad pairs (crowd them where it's steep). Bounded output but infinite oscillation? → still can fail (Ex 6). Missing endpoint with a finite limit? → fill it and gain compactness (Ex 7).

Connections

  • Continuity (pointwise) — the weaker property every example starts from.
  • Heine–Cantor Theorem — powers Ex 1 and Ex 7.
  • Compactness / Lebesgue number lemma — why closed+bounded rescues.
  • Lipschitz continuity — Ex 5, Ex 8 (and Ex 4 shows it's not necessary).
  • Mean Value Theorem — bounded slope → Lipschitz, used in Ex 5, Ex 7 & Ex 8.
  • Cauchy sequences — UC preserves Cauchyness, the deeper reason fails on .