Skip Navigation | ANU Home | Search ANU | Search FEIT | Feedback
The Australian National University
Faculty of Engineering and Information Technology (FEIT)
Department of Computer Science
Printer Friendly Version of this Document
COMP2300 Introduction to Computer Systems

COMP2300: Tutorial and Laboratory Exercises (2008)

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 your to your session. Some of these will also have a Preparation Exercises, which you will answer on prepare before your session, and bring it with you to the session. Handouts for these will be distributed in the Thurs or Fri lecture of the previous week.

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. 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 Lab Selected Answers (Sometimes!)
2: Mon 3 Mar Tutorial 1: Number Systems
(handout Fri wk 1)
Answers  
3: Tue 11 Mar Tute/Lab 2: Basic C Programming
(no handout!)
  • Program 1 [source]
  • isdigit() and friends [source]
  •  
    4: Mon 17 Mar Tute/Lab 3: I/O, Pointers, Structures
    (handout Thu wk 3)
    Some Answers and Comments  
    5: Mon 24 Mar Tute/Lab 4: Introduction to PeANUt
    (handout Thu wk 4)
    Selected answers  
    6: Mon 31 Mar Tute/Lab 5: PeANUt Experiments
    (handout, Thu wk 5)
    Selected answers
    7: Mon 7 Apr Tute/Lab 6: PeANUt Assembler
    (handout Thu wk 7)
    Selected answers  
    8: Mon 23 April Tute/Lab 7: Bit Operations and Address Parameters in PeANUt
    (no handout!)
     
    10: Mon 12 May Tute/Lab 8: Virtual Memory in PeANUt
    (handout Wed wk 9, p1 only)
    Selected answers  
    11: Mon 19 May Tute/Lab 9: Caches, SPARC Assembly plus Linking and Loading
    (handout Fri wk 10)
    Some answers  
    12: Mon 21 May Home Work 1: Computer Communication
     

    Last modified: 22/08/2008, 07:14

    Copyright | Disclaimer | Privacy | Contact ANU