Course Overview
In this class there are no exams. Instead, there will be a number of sets of compulsory assignments, and in order to pass the class you have to (1) pass all the sets of compulsory assignments and (2) participate in two programming contests.
- There will be approximately 13 sets of compulsory assignments, with some exceptions the following will hold:
- There will be a new set of compulsory assignments published every week, related to the topic of the lectures of that week.
- A set of assignments will consist of 4 tasks, to pass the set you need to complete at least 2 of the tasks.
- The deadline to complete the assignment will be on the Sunday 3 or 4 weeks after the assignment set is covered in the lectures.
- If you miss even one deadline you fail the class.
You also need to register your Kattis user to this course specifically, by clicking I am a student taking this course and I want to register for it on Kattis Links to an external site. on the uib.kattis pages. The secret key to be admitted is «isweariwillnotcheat».
For each problem you solve, follow the following submission procedure:
1. Submit an accepted solution to the relevant problem group at uib.kattis
2. Copy your code to the clipboard (preferably from the submission page at uib.kattis so that we get syntax highlighting)
3. Find the corresponding problem in the Assignments, and paste your code there as your submission before the due date.
We will do two individual meetings with each of you to discuss your solutions. Each meeting takes approximately 30 minutes. The first batch of meetings will most likely be in April. The second one will be in late May, early June. More information will follow in an announcement closer to the actual dates.
- There will be two programming contests, attending these is compulsory to pass the course. The competitions will start during the time of the lecture / group session of INF237. Alternatively, participation in Google Hash Code or IDI Open will also count towards this requirement.
If you participate in more than two programming contests, you earn a "wild card" for each extra contest you participate in. You can thus earn up to two wild cards during the semester. A wild card gives you the opportunity to do one task less for one of the problem sets. You may not use more than one wild cards on the same problem set.