Parallel Functional Programming – Programming Assignments | DAT280 / DIT261, LP4 2016 |
Home | Schedule | Labs | Lectures | Exam | About | Fire | Forum | TimeEdit | Links |
Parallel Functional Programming – Programming Assignments | DAT280 / DIT261, LP4 2016 |
Home | Schedule | Labs | Lectures | Exam | About | Fire | Forum | TimeEdit | Links |
It is advisable that both students in a group are at a similar level. Otherwise, there is a risk that the more experienced student will do most of the work, and the other student will not learn much.
If you need to find a lab partner, please use the discussion forum of the course.
If you want to use the latest GHC version on the student computers (not required), please follow these instructions.
▷ Lab A: Parallel Programming in Haskell
▷ Lab C: Parallel Functional Programming in Java 8
All lab assignments must be submitted using an electronic submission system called "Fire".
Remember to register both yourself and your lab partner in your lab group before you submit! By default, the submission system does not accept submissions made by single persons.
There are no pre-booked lab slots or supervision. To get help, you should go to the office of one of the TAs, Nick and Markus, at their scheduled office hours (or in extremis at some other time agreed in advance by email).
Each lab (except the first one) has three deadlines.
First deadline:
Final deadline (1 weeks after first deadline):
If you do miss a deadline, you may get a new chance at the end of the course. Otherwise, there is always a new opportunity to finish the labs next year or at the time of the reexam in August.
The feedback that you get on your lab submissions will make use of the following symbols:
--
Your function f does not work
Denotes something that has to be corrected and submitted again
==
Your function f is a bit too complicated
Denotes something that has to be corrected only if the lab has to be submitted anyway
**
I see you have solved the problem
Just a regular comment, nothing to correct
++
Your implementation of f is better than mine!
Something extra good, should of course not be corrected
Cheating on labs is unacceptable. Cheating means:
If you have problems, you should talk to us instead of copying from others. If needed, you may get more time and more help. If this is not enough, it is advisable to redo the course next year. This option makes much more sense than cheating.
Some cheating can be detected by the lab graders, when they discover similar solutions (e.g. same code, but different comments, layout, variable names, etc.). At the end of the course, we will also use automatic software that checks for similarity between all submitted solutions.
This is what happens if we detect cheating: