Parallel Functional Programming – Programming Assignments | DAT280 / DIT261, LP4 2018 |
Home | Schedule | Labs | Lectures | Exam | About | Fire | Slack | TimeEdit | Links |
Parallel Functional Programming – Programming Assignments | DAT280 / DIT261, LP4 2018 |
Home | Schedule | Labs | Lectures | Exam | About | Fire | Slack | 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 slack of the course to advertise your availability.
▷ Lab A: Parallel Programming in Haskell
▷ Lab B: Tutorial Writing and Data Parallel Programming
▷ Lab C: Parallelizing a Sudoku Solver
▷ Lab J: Parallel Functional Programming in Java 8
▷ Lab S: Programming in Single Assignment C
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 a submissions made by a single person.
There are no pre-booked lab slots or supervision. To get help, you should go to the office of one of the TAs, Max 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 two deadlines.
First deadline:
Final deadline (typically 1 week 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.
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.
If we detect cheating, we will report all parties to the relevant disciplinary board. Our fervent hope is that you will all be sensible so that no problems with cheating arise.