How to Write Multiple Sums with Complicated Indices
At a glance
- 1. Identify the indices
List each summation variable and the conditions that determine which tuples are allowed.
- 2. Define the index set
Collect the conditions into one set of admissible index tuples.
- 3. Write one sum
Sum the summand over that set, or use a constrained-sum notation.
- 4. Keep order when needed
For infinite sums, retain the iterated form unless changing the order is justified.
When several summation limits depend on one another, the nested notation can become difficult to scan. A useful alternative is to describe all allowed index tuples as a set, then sum over that set. This separates the question “which indices are included?” from “what is being added?”
There is no single best notation for every situation. Use a set-based sum when the constraints are the main source of clutter; keep the iterated sum when the order or structure of the summation is useful.
Replace complicated limits with an index set
Suppose a sum uses integer indices , , and , with bounds that depend on earlier indices. Collect the restrictions into a set of allowed triples. Then write
The notation says to include one term for every triple in . If the set is not already clear, define it explicitly, for example:
This is equivalent to writing all three sums with their limits. It is often easier to check the conditions in the set than to follow a long chain of nested bounds.
A fully worked example
Consider the finite sum
The allowed indices satisfy and . Define
The same sum can now be written as
For a concrete check, take and let . The allowed pairs are , , and . Their respective ranges are through , through , and through . Thus
The set-based notation gives exactly the same 12 terms. It does not change the sum; it only packages the index restrictions differently.
Other useful forms
For a one-off expression, you can put the conditions directly beneath the summation symbol:
This is compact, but it can become cramped if the conditions are long. If the same collection of indices appears repeatedly, naming it—such as —usually improves readability.
If the indices range independently over a Cartesian product, ordinary nested limits are often clearest. For example, when and independently, write , or equivalently sum over . The set form is more useful when the allowed pairs are restricted, such as .
When to keep the nested sum
Nested sums show dependencies directly. In the example, the upper limit for is determined by , so the iterated notation makes that relationship visible. It can also be the better choice when you plan to evaluate the sum one index at a time or use an argument that depends on the summation order.
For finite sums, changing the order of summation does not change the result, provided you include the same terms. For infinite sums, changing or suppressing the order can change the meaning or value when the series is not absolutely convergent. In that setting, keep the order explicit unless a theorem or a stated convention justifies rearranging the terms.
Common mistakes
- Leaving the domain implicit. State that indices are integers or natural numbers when it is not clear from context. A condition such as alone does not specify the allowed values.
- Changing strict inequalities accidentally. The constraints and include different index tuples. Check endpoints when translating limits into a set.
- Forgetting empty ranges. A nested sum may have no terms for some outer-index values. The standard convention for a finite empty sum is ; the set-based version handles this naturally because it contributes no elements.
- Treating an infinite sum as order-free. A compact sum over tuples should not obscure a meaningful iterated order for a non-absolutely convergent series.
- Using an unexplained shorthand. If you write , define what an index contains and what belongs to the first time it appears.
Spotted an error? Send a correction. Read how we write and check articles in our editorial policy.