Labs
We offer four labs in the course.
The first lab is to refresh your Haskell skills. You don't have to hand in this lab, and you won't get a grade, but working on it does give a bonus point.
Work on the labs together with a lab-partner: discussing potential solutions and problems together helps learning and understanding. Mail Johan Jeuring if you cannot find a lab partner.
Each group will get a dedicated TA for the assessment of the labs.
The other three labs are assessed with Pass/Resit exam. To pass a lab you have to do the following: - Before you had in your final solution: discuss the feedback from the auto grader at least once with your TA in a lab session - Discuss the final solution you hand in with your TA
For each of the labs we will offer two feedback opportunities. If you submit your lab on or before the feedback opportunity date, we will run the auto grader on it, and provide feedback. The dates by which you need to hand in your preliminary and final solutions are in the below table. Note that the auto grader returns a score to give an indication of the quality of your work, but the final grade for a lab is Pass/Resit exam. The feedback opportunity dates are chosen so that you can discuss your preliminary solution the next day with the teaching assistants in the lab session. You don't have to submit your preliminary solutions for all feedback opportunities - one is enough - but then you miss an opportunity to get feedback. You do have to submit a final solution.
| Lab | Description | Start | Feedback opportunity I | Feedback opportunity II | Submit |
|---|---|---|---|---|---|
| P0 | Haskell refresh | 17 Nov | |||
| P1 | iCal | 24 Nov | 30 Nov | 2 Dec | 7 Dec |
| P2 | Arrow | 8 Dec | 14 Dec | 16 Dec | 4 Jan |
| P3 | CSharp | 5 Jan | 18 Jan | 25 Jan | 1 Feb |
The assessment of your lab is done in a discussion with the TA to which you are connected. You make a separate appointment of 15 minutes with your TA, to discuss the lab you submitted. In this discussion you will have to show that you have thought about the problem and its solution, and that you have authored the solution to the problem yourself. Your solution does not have to be perfect, and it is not necessarily a problem if your solution is incomplete or contains some errors. We run the auto grader on your submission, and discuss the results of the auto grader. Each member of the team has to be able to explain the submitted code.