Image and Codomain

Context: FIT1058_MOC · the two “output sets” of a function · image codomain · the gap is closed by surjectivity

Quick Revision

  • 🎯 Objective: codomain = declared output set; image = values actually produced ➔ image codomain.
  • 📦 Core Components: codomain (promise) ➔ image (truth).
  • ⚡ Key Constraint: image = codomain iff surjective; the exact image is often intractable.

📝 Core

1. Two Output Sets

  • Codomain ➔ declared output space , guaranteed to contain every .
  • Image, the exact set of values.
  • Inclusion ➔ image codomain (possibly proper).

2. Promise vs Truth

  • Codomain promises ➔ all outputs lie in , but not that every element of is hit.
  • Why generous ➔ the exact image can be hard/impossible to pin down (sum-of-four-cubes is open).
  • Examples ➔ Fibonacci image ; image .

3. When They Coincide

  • Surjective ➔ image = codomain ➔ every codomain element is used.
  • Terminology ➔ avoid “range” (ambiguous); use codomain / image.

Key identities:

⚖️ Core Decision Matrix

SetMeaningDetermined by
codomaindeclared output spacethe specification
imageachieved valuesthe rule
relationimage codomainalways
equalityimage = codomainsurjective

When It Flips: the codomain is chosen for convenience; the image is forced by the rule. "Surjective" is exactly "the codomain promise is met with nothing unused". The preimages partition the domain (Equivalence Relation).

📊 Exam Execution Trace

Manual Execution Trace

, :

Step / StateImage so far
0 (Init)
11
200
324

⚠️ Common Mistakes

  • 💡 Codomain must contain all values ➔ a set smaller than the image is not a valid codomain; a generous codomain (e.g. ) is chosen because the exact image may be intractable.

🧠 Active Recall