For Course 1DL451 and Part 1 of Course 1DL442 (in period 1), there are 3 mandatory modelling assignments (numbered 1 to 3 below, whose statements will appear in due time), worth 3 higher-education credits (ECTS credits) in total. For Part 2 of Course 1DL442 (in period 2), there are 3 mandatory programming assignments (numbered 4 to 6 below, whose statements will appear in due time), worth 5 higher-education credits (ECTS credits) in total. The main objective of the assignments, which are to be done in teams, is to exercise the theoretical knowledge gained in the lectures, on carefully selected problems of our choice. We are not just interested in sufficiently correct and efficient models or programs, but also in explanations and experimental evaluations, hence a report is also required for each assignment and its quality has an impact on the assignment score.
For each assignment, the assistants supervise 3 help sessions for troubleshooting in the preparation of your reports. Assignments 1 and 4 are scored pass/fail in order to get started gently on each part of the course, and each other assignment gets an assignment score in \(0..5\). An insufficiently good report in part 1 of the course can be defended orally to an assistant in a scheduled grading session. Solutions and collective feedback are given by an assistant in a solution session.
PhD students do either the assignments (possibly in a duo team), or just the project (solo; possibly in connection with their PhD research; but they are highly encouraged to do the assignments nevertheless), or both: contact the head teacher.
The objective of a help session is only for the assistants to help you prepare an acceptable solution for the assignment with the closest upcoming deadline. The assignment problems will normally be published at least a week prior to the first help session. Also, the necessary course material will normally have been presented in lectures at least a week prior to the first help session. You are thus able and even strongly encouraged to prepare your solution as far as possible until the help sessions and to attend them, in order to make best use of that reserved time span of personal attention by the assistants.
Note that no further tutoring on lecture topics, such as exercises whose solutions are given or to be handed in at the end of the session, will be performed by the assistants at the help sessions.
The initial score, in the integer interval 0..5 (or pass/fail for Assignments 1 and 4), of your assignment report will normally be determined by the late afternoon on the day before the grading and solution sessions for that assignment. Toward this, the assistants run your code on a grading test suite and examine your report. An initial score is the final score if in the set {0,3,4,5} (or pass for Assignments 1 and 4).
The objective of a grading session is to determine your final score for the submitted report for the assignment of the previous deadline. Each team with an initial score in the set {1,2} (or fail for Assignment 1) will normally be given an appointment with an assistant during the scheduled grading session, in a location of her/his choice, toward correcting minor mistakes during that meeting and possibly increasing your score by one unit. An initial score of 1 (or fail for Assignment 1) upon only major mistakes cannot be increased at a grading session.
Appointment times are strict: the initial score is final in case of a missed appointment. Exceptions must be negotiated in due time during work hours with the head teacher, upon reporting a convincing case of force majeure.
The objective of a solution session is only for an assistant to give collective feedback and discuss acceptable solutions to the assignment of the previous deadline. No code will be handed out. The first five solution sessions are merged with the initial help sessions to the next assignment.
Some comments on your submitted report can be found at Studium; more detailed individual feedback can be obtained orally from the assistants upon appointment.
Note that no further tutoring on lecture topics, such as exercises whose solutions are given or to be handed in at the end of the session, will be performed by the assistants at the solution sessions.
| Assignment | Help session a | Help session b | Help session c | Deadline | Grading session | Solution session |
|---|---|---|---|---|---|---|
| warmup-MiniZinc.pdf, exercises on comprehensions (no hand-in), and warmup-LaTeX.pdf | Thu 31 Aug | none | none | none | none | none |
| assignment1.pdf | Thu 31 Aug | Mon 04 Sep | Wed 06 Sep | Fri 08 Sep at 13:00 | Thu 14 Sep | Thu 14 Sep |
| assignment2.pdf | Thu 14 Sep | Mon 18 Sep | Wed 20 Sep | Fri 22 Sep at 13:00 | Thu 28 Sep | Thu 28 Sep |
| assignment3.pdf | Thu 28 Sep | Mon 02 Oct | Wed 04 Oct | Fri 06 Oct at 13:00 | Thu 12 Oct | Thu 12 Oct |
| warmup-MiniCP.pdf and exercises on lambda expressions (no hand-in) | Thu 02 Nov | none | none | none | none | none |
| assignment4.pdf | Fri 10 Nov | Mon 13 Nov | Wed 15 Nov | Fri 17 Nov at 13:00 | none | Fri 24 Nov |
| assignment5.pdf | Fri 24 Nov | Wed 29 Nov | Wed 06 Dec | Fri 08 Dec at 13:00 | none | Fri 15 Dec |
| assignment6.pdf | Fri 15 Dec | Wed 20 Dec | Mon 08 Jan | Fri 12 Jan at 13:00 | none | Fri 12 Jan |
All assignment reports, with imposed M4CO structure (LaTeX source), but no imposed CP structure, must be submitted electronically via Studium, whose clock may be different from yours. Submission deadlines are hard. Exceptions must be negotiated in due time during work hours with the head teacher, upon reporting a convincing case of force majeure. Grading will only start after a deadline, so you can submit multiple times until then.
For pedagogic and resource reasons, every assignment report and project deliverable must be prepared by a team of 2 students, both being first-time students or both being non-first-time students of this course. No permission will ever be granted for teams of three or more students.
Until 23:59 of Sun 3 Sep 2023, you can declare a team at Studium: both teammates must consent to forming a team. If you are not formally registered yet, or if your team is the union of two one-person teams in each of the two courses, then you can declare your team by email to the COCP helpdesk by that hard deadline. You are strongly encouraged to advertise your search for a teammate at a course event or by using the Teammate Search discussion at Studium. If you are however fine with a randomly assigned teammate, then declare this by email to the COCP helpdesk by that hard deadline: you might not get any teammate, because you are the odd one out or because the assigned one drops the course on short notice, so start working solo on Assignment 1 in order to guard against this possibility. All students who have done neither of those actions by that hard deadline will be considered to have dropped the course, but will not be unregistered by us: their submitted deliverables will normally not be graded.
Teams may change between assignments: permission will be granted, as long as you inform the COCP helpdesk in advance and the total number of teams does not increase.
Only one teammate of each team should submit each assignment report or project deliverable.
Exceptions for solo work must be negotiated in due time, during work hours, with the head teacher, upon reporting a convincing case of force majeure. The assignments are calibrated somewhat smaller for those students. Such an exception is only valid for the assignment(s) it was negotiated for.
The legislation on plagiarism and cheating (summary) of Uppsala University will be rigorously applied, without exceptions. This disallows using a public repository (such as GitHub, where you should use a free private student repository) for code management within your team: this is particularly important for part 2 of course 1DL442, where the same quizzes and assignments and are used worldwide in a massive open online course. We reserve the right to use plagiarism detection tools and point out that they are extremely powerful.
When submitting you implicitly certify that your report and all its uploaded attachments were produced solely by your team, except where explicitly stated otherwise and clearly referenced, that each teammate can individually explain any part starting from the moment of submitting your report, and that your report and attachments are not freely accessible on a public repository.
We reserve the right to give different assignment scores to the teammates of a team, depending on the performance at the grading session.
Please report any problems within a team to the head teacher, who will handle the case in confidence, in the best interest of both teammates, keeping the ethics dimension in mind.
One higher-education credit (ECTS credit) translates under Swedish university law into an expected 26.67 hours of work for the average student:
The modelling assignments (of Course 1DL451 and Part 1 of Course 1DL442, in period 1) are worth 3 credits: discounting about half of the 21 hours spent on the lectures (the other half being similarly discounted on the 2 project credits), the modelling assignments are calibrated to take about 21 hours of work on average by the average student, for each teammate, including the help, grading, and solution sessions.
The programming assignments (of Part 2 of Course 1DL442, in period 2) are worth 5 credits: discounting the 22.5 hours spent on the lectures and warm-up, the programming assignments are calibrated to take about 37 hours of work on average by the average student, for each teammate, including the help, grading, and solution sessions.
All this does not clash with other courses you are taking, as university studies are legally defined to take 400 hours of work per study period (normally 10 weeks), and the standard 15 credits targeted in a study period are calibrated to reach that total.
The modelling assignment grade for Course 1DL451 or for Part 1 of Course 1DL442 is determined by a published scale, depending on the modelling assignment scores.
The programming assignment grade for Part 2 of Course 1DL442 is determined by a published scale, depending on the programming assignment scores.
The overall grade for Course 1DL451 is determined by a published scale, depending on the modelling assignment scores and the project score.
The overall grade for Course 1DL442 is determined by a published scale, depending on the modelling assignment scores, the project score, and the programming assignment scores.
These rules are effective as of Mon 28 Aug 2023. The head teacher reserves the right to modify them at any moment, should special circumstances call for this.