There are three programming assignments, which you should do in pairs. If you have a good reason for doing the assignments by yourself, please contact the lecturer.
- You need to pass all three assignments in order to pass the course.
- Each of the assignments is divided into two parts with separate deadlines.
- The assignments have to be handed in using the Fire system.
Please read these early and carefully!
If you for some reason cannot make the deadline, contact us before the deadline, and tell us what your reason is, together with a realistic proposal of a new personal deadline for you. You may then get an extension of the deadline.
|Part I||January 29th (course week 2)|
|Part II||February 5th (course week 3)|
|Part I||February 12st (course week 4)|
|Part II||February 26th (course week 6)|
|Part I||March 5th (course week 7)|
|Part II||March 12rd (course week 8)|
Your last attempt has to be submitted before the final deadline. If you fail to do this, your submission will be rejected.
Assignments will be graded on a scale of 3 to 5 and will count towards your final grade on the course. Your last attempt has to be submitted before the final deadline. If you fail to do this, your submission will be rejected.
Not all the form of cooperation among students are considered cheating. Here follow the rules of cooperation between students in this course.
One is allowed to orally discuss exercises and programming assignments with one another.
For the programming assignments, one is allowed to work in groups of size two. Once you have cooperated on an assignment with a particular person, you must submit your answer to that assignment together with that person, and can not cooperate with anyone else.
Apart from with your own lab partner, you are not allowed to share any piece of code with another student, by any means. Examples of ways which you cannot use to share code are:
- e-mailing code,
- printing out your code and giving it on paper,
- stealing other people's print-outs,
- dictating code over the phone,
- copying files with or without permission,
- reading someone else's email,
- reusing code from the web, etc.
Violating any of these rules might not be considered cheating by itself, but violating any of these rules without informing the lecturer is definitely considered cheating.
It is possible that exceptions to these rules are granted, but only you should talk to the lecturer as soon as the problem arises.
The labs in this course require you to use a fairly recent version of GHC.
Unfortunately, the version provided by default on the Chalmers machines is
quite ancient. If you want to use the Chalmers machines for your lab work,
you will need to add the directory
/chalmers/sw/unsup64/phc/b/binh to your
One way to achieve this is to run the following in a terminal:
echo 'export PATH=/chalmers/sw/unsup64/phc/b/binh:$PATH' $HOME/.bashrc
After executing the above command, close your terminal window and open a new one. Then check that everything works as expected:
GHC should then print:
The Glorious Glasgow Haskell Compilation System, version 7.10.2
If the version printed is 7.10.2, then you're all set up and good to go. Note that you only need to perform this setup once on your Chalmers account, as these changes persist across reboots.