Skip to main content

Unit information: Coding Theory (M) in 2012/13

Please note: you are viewing unit and programme information for a past academic year. Please see the current academic year for up to date information.

Unit name Coding Theory (M)
Unit code EENGM2010
Credit points 10
Level of study M/7
Teaching block(s) Academic Year (weeks 1 - 52)
Unit director Professor. Piechocki
Open unit status Not open
Pre-requisites

None

Co-requisites

None

School/department School of Electrical, Electronic and Mechanical Engineering
Faculty Faculty of Engineering

Description including Unit Aims

Coding theory tackles the theory and design of error correction codes. Error correction codes are a common component within many communications and data storage systems, to ensure that information is accurately reproduced in the presence of transmission errors. The codes rely on the addition of additional redundant parity data in order to facilitate the detection and correction of transmission errors. The subject stems from pioneering work by Claude Shannon in 1948 who showed that it is theoretically possible to accurately transmit data at any rate below the channel capacity. Since then much effort has been invested in the development of good codes and efficient decoding methods for reliable communication. Many of the commonly used techniques rely on the use of the structure associated with finite algebra. This module will cover a variety of commonly used coding techniques including linear block codes, cyclic codes and convolutional codes. The performance of codes will be examined, both for random and burst error environments. The module will also cover some more complicated practically useful techniques, including Reed Solomon codes and concatenated codes.

Elements:

Introduction to Coding Theory - Shannon’s noisy coding theorem, channel types, code rate , coding gain;

Block codes - encoding and decoding, Hamming distance;

Finite algebra; - finite fields, vector spaces;

Linear block codes - generator and parity check matrices, systematic codes, standard array, performance bounds, Hamming codes, modified codes, calculation of error rates;

Cyclic codes - generator polynomials, syndrome calculation, modified codes, low rate codes, CRCs, Reed Solomon codes;

Convolutional codes - encoding, state & trellis diagrams, Viterbi decoding, performance, puncturing for code adaptation;

Practical exercise – implementing and simulating linear block codes in Matlab, comparing theoretical performance for block codes.

Intended Learning Outcomes

The project contains a research or investigative element which allows you to demonstrate individual talent and intellectual ability. It attempts to mirror a research and/or development project of the type you might encounter upon graduation and as such contains elements of project planning and budgetary control. The project report also provides an opportunity for you to demonstrate report structuring and writing skills.

Teaching Information

Teaching takes place over two Semesters, the first lasting for weeks 1-12 and the second for weeks 13-24. Exams normally commence in week 25 and last for approximately three weeks. The remainder of the programme is then dedicated to full-time work on the research project.

Taught phase

The taught units and their associated assessments (including examinations) occur in the first 35 weeks and the research project runs full-time during the latter 15 weeks of the programme. The taught material is presented over 2 Semesters, each 12 weeks in duration; excluding the Christmas and Easter vacations of 8 weeks in total. Further, the examinations are held May/June each year over a 3 week period. During the second Semester you will commence the background reading phase of your research project. The taught material is arranged in units extending over a 12-week period (a Semester), typically with 2 lectures per week, each of 50 minutes duration.

The Laboratory

Laboratory activities are scheduled for two afternoons a week during the first two terms, although you may not have labs scheduled in all sessions. Predominantly, these will take place in the MSc Laboratory. Precise details of activities and a laboratory timetable will be provided separately by the Programme Tutor and will also be available online at: https://www.bris.ac.uk/eeng/intranet/pg/msc

Assessment Information

Taught Phase

The assessment of this material is via a combination of continuous assessment (usually laboratory assignments) and formal examination.

Laboratory work

At various times throughout the year you will be asked to write about an aspect of your laboratory. Unless otherwise instructed, you will be asked to submit this either as a Technical Note (TN) or as a Full Report (FR). In either case the report should be written on an individual basis even if the lab was performed in groups.

A TN is briefer than an FR: you should refer to The Guidelines on Writing Technical Reports (Section 2.4) for more information on their structure and content.

As an approximate guide, we suggest that a TN should be 1000 words plus diagrams etc., whereas a FR should be 3000 words plus diagrams etc. Our time calculations are based on you spending (at most) 12 hours writing a TN and (at most) 24 hours writing a FR.

Where appropriate, your laboratory notebook will also be inspected from time to time by a member of staff or a demonstrator. Coursework or laboratory assessments will normally contribute 10-20% of the total unit assessment (see unit breakdown information on the MSc website for specific unit details): http://www.bris.ac.uk/eeng/intranet/units/programmes.html

Project phase assessment

  • Interim report
  • Poster presentation
  • Final project thesis

Interim report assessment

The interim report will be independently assessed by both your supervisor and an assessor (these will be notified in advance). The assessment will be based on the following criteria:

  • Report
  • Presentation and standard of written English (including figure captions and titles, correct use of references, etc.).
  • Clear idea of objectives and relevance of project.
  • Review of related work.
  • Initial top level design and resource requirements.
  • Workplan, risks and critical paths.

Presentation and interview

  • 5-10 minute presentation to two members of academic staff, outlining aims and objectives, initial findings, and proposed research plan
  • Quality of answers

Poster presentation

This will be performed by two members of staff who will undertake the assessment separately. They will first read through your poster and then ask you a number of questions relating to the work described. You will be given the opportunity to present any demonstrations you have prepared.

Reading and References

There are 12 branch libraries covering different disciplines and members of the University may use any of them. However, the Queen’s Building Library has the most relevant collections for the Electrical & Electronic Engineering students.

There are many information resources available to Electrical & Electronic Engineers. Library Services provides access to the most important ones via our resource gateway, MetaLib: http://metalib.bris.ac.uk

  • Lin, S & Costello, D.J. Error Control coding: Fundamentals and Applications, Prentince Hall, 1983, ISBN 0 13 283796 X (QA 268 Lin)
  • Sweeney, P. Error Control Coding: From Theory to Practice, J Wiley, 2002, ISBN 0 47 084356 X

http://ieeexplore.ieee.org/Xplore/dynhome.jsp

Feedback