Labs take two hours, and you’re expected to work in pairs.
As soon as the database is up to date, you’ll find information about groups, computer rooms and lab supervisors on the page Laborationsgrupper.
The labs are programming exercises that relate to the material covered in lectures, typically in the week before. Very few of you will be able to complete these exercises during a 2 hour lab session, so it is expected that you show up to the labs well-prepared, presumably with a good part of the code already written. If you attended the whole lab session in the beginning of a week, but weren't able to finish on time, you have until the deadline to hand it in. The details of how this is handled are not yet clear (at the beginning of March 2012), watch this space. Either there will be an extra lab, or you hand in at the beginning of next week’s lab.
|Name||Relates to what?||Lab session 2012||Deadline|
|1. Stable marriage||Introduction||10–15 Apr||TBA|
|2. Word ladders||Graphs||17–22 Apr||TBA|
|3. Spanning USA||Greedy algorithms||24–19 Apr||TBA|
|4. Closest pair||Divide and conquer||w 17: 23–29 Apr||TBA|
|5. Me: Gorilla or sea cucumber?||Dynamic programming||wtf?||TBA|
|6. Railroad planning||Network flow||wft?||TBA|
Frågor om innehållet: Peter Möller
Webbtekniska frågor: email@example.com
Senast uppdaterad: 2013-03-20