CECS Home | ANU Home | Search ANU
The Australian National University
ANU College of Engineering and Computer Science
School of Computer Science
Printer Friendly Version of this Document

UniSAFE

COMP2300/6300: Tutorial and Laboratory Exercises (2009)

The laboratory documents and associated files will be put up on this web site when they are ready - generally the Friday before the week of the corresponding sesion. Until that time, the links to them below will not work. Answers (if any) for the current session will be put up by early in the following week.

The sessions with a tutorial component will require you have a hardcopy of the Tutorial Exercises that you bring with you to your session. Some of these will also have associated Preparation Exercises, which you will answer on a sperate piece of paper before your session, and bring the answers with you to the session. A collated handout for these Exercises will be distributed in week 1. If you miss or lose this, print another copy using the links below.

Aside from the Preparation Exercises, it is very important that you come to your tute/lab session prepared. That means, at the least, having revised relevant lectures and had a look at the whole exercise to see if there is anything you would like explained. Your two hour session is valuable time, as its the only formal opportunity to get help and advice from your tutor.

You will notice that some parts of the lab exercises are assessable, and some parts are not. This does not necessarily mean that the non-assessable parts are less important. It only means that some parts can more easily computer-assessed than others.

For the assessable part, you are encouraged to use the previewAutoMark command to see if your program will pass the automated marking. If your program fails a test, it will print a line-by-line comparison between your program's output (on the left) with the expected output (on the right), using the sdiff -l command: see this sdiff primer for more information on how to interpret this. The actual marking is done later off-line on the program that you submitted via the submit command. Note: the test cases used on the submitted files may be slightly different to those used by previewAutoMark!

Note also:

  • if you can't make your normal class in a particular week, you may attend another session (provided there is space). Ask the tutor to record your attendance.
  • if you cannot make your normal class on a regular basis, you should contact the course co-ordinator and ask for a change.
  • the tute/lab attendance marks is based on effort. Being well prepared (i.e. having done any required Preparation Exercises and not needing to waste time poring over lecture notes during the session) is an important aspect of this.

Week: Beginning Title Handout Selected Answers (Sometimes!)
2: Mon 02 Mar Tutorial 1: Number Systems 2 pages Answers  
3: Mon 09 Mar Tute/Lab 2: Basic C Programming --
  • Program 1 [source]
  • isdigit() and friends [source]
  •  
    4: Mon 16 Mar Tute/Lab 3: I/O, Pointers, Structures
    2 pages
    Some Answers and Comments  
    5: Mon 23 Mar Tute/Lab 4: Introduction to PeANUt 2 pages Selected answers  
    6: Mon 30 Mar Tute/Lab 5: PeANUt Experiments 1 page Selected answers  
    7: Mon 06 Apr Tute/Lab 6: PeANUt Assembler 2 pages Selected answers  
    8: Mon 27 April Tute/Lab 7: Bit Operations and Address Parameters in PeANUt --  
    10: Mon 11 May Tute/Lab 8: Virtual Memory in PeANUt 1 page Selected answers  
    11: Mon 18 May Tute/Lab 9: Caches, SPARC Assembly plus Linking and Loading 2 pages Some answers  
    12: Mon 26 May Home Work 1: Computer Communication
    --  

    Last modified: 26/05/2009, 16:40

    Copyright | Disclaimer | Privacy | Contact ANU