The deadlines for all exercises can be found in the course schedule. All deadlines are at 23:59 of the mentioned date. As a general rule no deadline can be postponed. Don't wait until exactly 23:59 to submit but try to do this at least 5 mins earlier to avoid problems with clocks.
If you find yourself in a situation where you have not finished the exercise, submit what you have done so far but make sure that the version you submit really works, be it incomplete. In order to always be able to submit a working version, always make a copy of a working intermediate version.
Tools and starting material can be found under Tools & Software
What to make
Each exercise has its own specification of what should be done. However, for each submitted exercise
- the relevant (i.e. modified, added) sources must include comments about the changes made and why those changes have been made. In other words, explain your design (decisions).
- test files must be made. These testfiles are the test cases you used to test your modifications. Indicate what the expected result of a testfile should be (for example, in a README file), in particular which tests yield errors or other deviating behavior.
The following table gives an indication of what we consider adequate (v=voldoende), good (g=goed) or excellent (u=uitstekend) in terms of judgement of an exercise.
| Exercise/opgave || for 'v' || for 'g' || for 'u' |
| 1 || basic features || also extra features || a discussion of design alternatives for the extra features (which makes sense, possibly combined with alternative implementations) |
| 2 || up to including step 1 || up to including step 2 || all |
| 3 || up to including step 3 || up to including step 4 || a neat (minimal, consistent, etc) solution which also works with other input (than the ones from the lecture notes). For example: let id = \x -> x in (\x -> x) id ni with output. |
The computation of the effect on your exam mark can be found on the CourseSchedule
Submit via http://www.cs.uu.nl/docs/submit/
. Choose the following names for the 'Opgave:' (exercise):
Submit in 1 zip file:
- The software you have constructed.
- The test input files you used, in particular for every aspect of the exercise.
- A README file which tells us those things we (as staff) cannot easily guess, such as expected result of tests, what the content is of your additions and modifications.
- Please make the README file plain text, and do not put .rar or other zip files inside the zip file.
A 1Mb size limit is imposed on submitted files. Please try to keep the directory names as in the zip file you downloaded, i.e. SL1 for assignment
1 and so on.
Results of lab exercises
Results will be posted on-line no more than two weeks after the deadline.