UNSW Sydney · FACULTY OF MATHEMATICS

MATH3411 Chap.2 Error Detection Through Linear Codes

- one subject, every graph, every model, every mark
7 Chapters4-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 2 of 7 · MATH3411

Error Detection Through Linear Codes

This chapter develops the geometry and algebra of error control. Hamming distance and weight quantify separation, sphere packing limits code size, and perfect codes attain the volume bound. Binary linear codes turn validity into matrix equations, so a parity-check matrix supplies both minimum-distance evidence and a syndrome decoder. Exam answers must distinguish guaranteed detection from guaranteed correction.

The same code is viewed in several compatible ways. A set-of-words picture shows distances, a packing argument counts disjoint correction regions, a generator matrix constructs legal words, and a parity-check matrix defines their constraints. Moving between those views is more valuable than memorising isolated statements. Minimum distance gives worst-case guarantees; it does not say every larger error is undecodable.

A nonzero syndrome labels a coset and becomes a location only when the column structure and promised error radius make that interpretation unique. Complete solutions state the relevant bound, carry out the binary calculation, map the result to the printed coordinate convention and verify that the repaired word has zero syndrome.

In this chapter

What this chapter covers

  • 01

    Hamming distance and weight

  • 02

    Detection and correction bounds

  • 03

    Sphere-packing condition

  • 04

    Perfect codes

  • 05

    Parity-check and generator matrices

  • 06

    Syndrome correction

  • 07

    Standard-form matrices

Worked example · free

Correct One Corrupted Coordinate

Q [3 marks]. A received word has syndrome equal to the fifth column of a parity-check matrix with distinct nonzero columns. Locate the error. The mark allocation shown is an independent study aid, not the university's published assessment scheme.
Each coloured circle represents every received word within t changes of one codeword; unique correction is possible only when those Hamming balls are disjoint.Each coloured circle represents every received word within t changes of one codeword; unique correction is possible only when those Hamming balls are disjoint.codeword acodeword bminimum distance dradius t balls must not overlap
Each coloured circle represents every received word within t changes of one codeword; unique correction is possible only when those Hamming balls are disjoint.
  • +1State the single-error assumption and syndrome identity.
  • +1Match the syndrome to column five.
  • +1Flip position five and verify zero syndrome.
The error lies in position five under the printed coordinate convention; the corrected word must have zero syndrome.
Sia tip — A syndrome names one position only when the error bound and column structure make that interpretation unique.
Glossary

Key terms

Hamming weight
The number of nonzero coordinates in a word.
Parity-check matrix
A matrix whose null space is the linear code.
Correction radius
The maximum distance from a codeword for guaranteed unique decoding.
FAQ

Error Detection Through Linear Codes FAQ

How many errors can distance d correct?

It corrects every pattern of up to the largest t satisfying 2t+1 at most d, while detection extends to d-1 errors. These are guaranteed worst-case limits rather than predictions about every larger pattern.

Why does distance equal minimum weight for a linear code?

The difference of two codewords is another codeword, so pairwise distances become weights of nonzero codewords. Translation by one codeword therefore reduces the minimum-distance search to comparison with zero.

What does a syndrome prove?

It identifies the coset of the received word. Under a bounded-error model, that coset can identify a unique low-weight error pattern. The error-radius assumption is what turns this label into a correction decision.

Study strategy

Exam move

Move among distance, counting and matrix views rather than revising them as unrelated formulas. Start with a small set of binary words and compute several pairwise Hamming distances. Identify the minimum, translate it into separate detection and correction guarantees, and write the two inequalities that justify those statements.

Change the distance by one and observe which guarantee changes; this is more reliable than memorising a rounded expression. For sphere-packing questions, calculate the volume of one Hamming ball before multiplying by the number of codewords. Label the ambient space size and decide whether the result gives an impossibility, an upper bound or equality for a perfect code.

Never treat the count as a construction unless an actual code is supplied. Matrix practice should alternate encoding and checking. Form a codeword as a message combination of generator rows, calculate its syndrome, and verify that generator and parity-check matrices are compatible through orthogonality and dimension. Then introduce one error, compute the new syndrome, match it to a column and flip the nominated coordinate.

Recalculate the syndrome after correction; the zero result is the required audit, not an optional flourish. Keep a coordinate key whenever columns have been reordered into systematic form. For proof questions, rehearse the short bridge from linearity to minimum weight: the difference of two codewords is a codeword, so translating one endpoint to zero turns distance into weight.

Also practise the parity-check column criterion as a lower-bound argument, followed by an explicit dependent set when equality is requested. Build an error log with distinct categories for confusing detection with correction, counting the wrong ball radius, claiming a lower bound as exact, losing binary cancellation and interpreting a syndrome outside the promised error radius.

For each category, write a one-sentence diagnostic question you can apply under time pressure. A productive mixed drill takes one distance statement, one volume bound, one generator calculation and one syndrome decoder in succession. Finish by explaining how all four answers describe separation between legal words.

That synthesis prepares you for less standard final-exam questions that provide information in one language and request a conclusion in another.

Working through Error Detection Through Linear Codes in MATH3411? Sia is AskSia’s AI Mathematics tutor — ask any MATH3411 Error Detection Through Linear Codes question and get a clear, step-by-step explanation grounded in how MATH3411 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 103 of your UNSW Sydney subjects - and 1,000+ Bibles across every Australian university.
Sia - your MATH3411 tutor, unlimited, worked the way the exam marks it
The full 4-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works
MATH3411 · Information, Codes and Ciphers - independent study guide on the AskSia Library. More UNSW Sydney subjects · Microeconomics across all universities