Summation Notation

Context: FIT1058_MOC · the sign for adding a sequence’s terms · partial sums form a new sequence · evaluated by Arithmetic Series / Geometric Series

Quick Revision

  • 🎯 Objective: = add a sequence’s terms ➔ partial sums form a new sequence.
  • 📦 Core Components: index ➔ range ➔ summand ➔ bound local variable.
  • ⚡ Key Constraint: math fixes no order (associative/commutative); code’s finite arithmetic is order-sensitive.

📝 Core

1. The Notation

  • Definition; partial sums are a new sequence.
  • Anatomy = index; initial; final; range; summand.
  • Evaluate ➔ substitute each index value, add.

2. Notation vs Algorithm

  • Math ➔ specifies the result, fixes no order (addition associative + commutative).
  • Program ➔ also fixes order, names/initialises the total; finite arithmetic isn’t perfectly associative ⟹ rounding depends on order.

3. The Index Is Bound

  • Arbitrary name (renamed consistently).
  • Local ➔ scope = the summation, like a bound variable under a quantifier.
  • Reuse warning ➔ outer differs from summation’s .

Key identities:

⚖️ Core Decision Matrix

AspectNotationProgram
specifiesthe resultresult + order
ordernone (assoc/comm)fixed
arithmeticexactfinite precision
roundingn/aorder-dependent

When It Flips: studying the partial-sum sequence is often the goal; its closed form comes from arithmetic / geometric series formulas. Mathematically the sum is unique; in floating-point, order changes accumulated error.

📊 Exam Execution Trace

Manual Execution Trace

:

Step / State
0 (Init)0
1111
2234
3359
44,57,916,25

⚠️ Common Mistakes

  • 💡 Reindex everywhere ➔ change both limits and the summand together, and avoid a name already used outside; the index is a bound, local variable.

🧠 Active Recall