EEE1008 2012-13

EEE1008: Notes, documents and links

C Programming

Module leader: Dr Albert Koelmans

Lecture Timetable

Day	Time	Room
Tuesday	11:00-12:00	STB F16
Tuesday	12:00-13:00	STB F16

Practical Timetable:

(Supervised practicals start on Wednesday 3 October)

Day	Time	Room	Demonstrators Coordinator
Wednesday	09:00-11:00	Merz Cluster, EECE Computer Lab 1st Floor	James Docherty

Starting the Bash Shell

Please read the following document: Helpful Hints. You can also access the Bash Shell on the Windows 7 desktop by moving the mouse pointer to the lower left of the screen. Then click on All Programs, Accessories, Cygwin, Cygwin Bash Shell. You might want to put a shortcut to this on your desktop.

"Standard" C libraries of functions under Cygwin

These libraries can be found by typing (in your Cygwin bash shell)
cd /usr/include
Alternatively, it should be reached (using the Windows Explorer) on your K: drive, in "central/Cygwin/Program Files/Cygwin/usr/include"
You will find the file stdio.h here (discussed during the lectures); just have a look at its contents with the command
more stdio.h
(keep pressing the space bar to get to the end)

C programs

All the programs used in the lecture notes

How to print the contents of the Cygwin Bash window

Dr. K. Wright's document on printing Cygwin

Installing/copying Cygwin

The Cygwin software used in the practicals can be freely downloaded on to your own computer. Go to the cygwin download page and download the file setup.exe. Please read the entire page before proceeding. Note that wwwcache.ncl.ac.uk with port number 8080 is the correct information about the University proxy machine (if you are downloading from within the University). When it asks what packages to install, type gcc in the search box, and then click everywhere where it says Default until it changes to Install. Keep the setup.exe program - you need to run it again if you want to install additional packages later.

List of Upcoming Assignments

Assignment 1 (deadline - 25 October; marked 15% of total)
Familiarisation exercises. Pts 1-5 and Familiarisation exercises. Pts 6-9
Deliverables and Assessment Procedure
Assignment 2 in two parts (deadline for Part 1 - show the program to demonstrator by 8 November; marked 10% of total, deadline for submitting the program and documentation on Blackboard Friday 9 November; marked 35% of total)
Assignment 2: Simple Circuit simulator. Please also have a look at the marksheet (pdf file) to see what is required.
Assignment 3 (deadline - 29 November - submit to Blackboard; marked 20% of total)
Assignment 3: Simple plot. Please also have a look at the marksheet (pdf file) to see what is required.
Assignment 4 (deadline - Friday 14th December - submit to Blackboard; marked 20% of total)
Assignment 4: Ladder network . Please also have a look at the marksheet (pdf file) to see what is required.

Practical Schedule

Week 1 Familiarisation: Familiarisation exercises. Pts 1-5 and Familiarisation exercises. Pts 6-9
Week 2 Exercises to go with chapter 2. These can be found here but will not be marked. They get you used to the program development cycle. Do them in any order you like.
Week 3 Continue with exercises, and also prepare for your first submission
Week 4 Submission deadline for assignment 1. Exercises for this week can be found here
Week 5 Work on assignment 2. Continue with exercises if necessary.
Week 6 Submission deadline for assignment 2.
Week 7 Work on assignment 3.
Week 8 Work on assignment 3.
Week 9 Submission deadline for assignment 3
Week 10 Work on the final assignment
Week 11 Submission deadline for assignment 4
Week 12 This is the first week of January. The course will be finished - there will be no lectures and practicals.

Submission Documentation Requirements and Deadline Policy

NOTE ABOUT PLAGIARISM

Plagiarism is an attempt to pass someone else's work as your own. This is a serious offence and may result in disciplinary measures being taken against anyone who is found to be plagiarising.

In particular, copying someone else's program code, algorithm design solutions, documentation etc. is seen as examples of plagiarism and will be treated as such with all appropriate consequences, from having a zero mark given for the relevant piece of submitted work to a case raised to the university disciplinary committee. More details on plagiarism can be found here.

albert.koelmans at ncl.ac.uk
October 2012