Evaluation Criteria
- (SI) Submitted Implementations: 50%
- (CE) Participation in Competitive Events: 20%
- (PP) Presentations and Class Participation: 30%
Each component has a grade from 0% to 100%.
(SI) Submitted Implementations
See detailed grades for this evaluation item
- We plan to have 10 evaluation problem sets. Each problemset is worth 12% of the total grade (with a maximum of 100% on this evaluation component).
- Each problem set will have a deadline associated with it. The typical deadline will be two weeks after the problems are made public.
- Each problem set has 6 problems. The first problem solved is worth 35%, the second one 30%, the third one 20% and the fourth one 15%. This means that:
- Solving one problem is worth 35%
- Solving two problems is worth 65%
- Solving three problems is worth 85%
- Solving at least four problems is worth 100%
- For each day after the delivery date you will have a 2% penalty on the respective problem. For example:
- 2 problems before the deadline and 1 problem four days after the deadline will give you 77% (65% for the first two problems and 12%=20%-4*2% for the third problem)
- 3 problems before the deadline and 1 problem 10 days after the deadline will give you 85% (85% for the first three problems and 0% for the last, since the penalty of 10*2% is more than than the 15% that the last problem would give you).
(CE) Competitive Events
There will be three competitive events where it is expected that the students appear and try to submit during the designated time:
- [25%] #01: (online, 1h40, live AtCoder Beginner Contest) [suggestion: 8th Jan / will count best contest on dec/jan ]
- [25%] #02: (on class, 3h, partial points per problem) [12th Jan]
- [50%] #03: (final contest, 4h, can have partial points/subtasks such as small and big testcases) [23rd feb]
Failure to participate in at least two of these events will result in a RFC evaluation (lack of an evaluation component).
You can participate in extra contests (ex: Codeforces Rounds) to compensate for any contest that did not go well for you (extra participations will be evaluated on a case by case basis).
(PP) Presentations and Class Participation
- [40%] (CP) Creating a Problem: each student should create a new problem on the style of a competitive programming event, together with all associated material (problem statement, solution and written editorial, inputs/outputs and generator) [deadline:
6th 19th Feb]
- [30%] (PP) Presenting a Problem: oral presentation of (at least) one of the student's accepted problems (selected by the professor) [see details] [deadline:
13th 22nd Feb]
- [30%] (GE) Global Effort: overall appreciation of the student overall effort on the course:
- Quality of submitted code (including comments) [deadline: 22nd Feb]
- Extra problems made (above the minimum for having 100% of the SI component)
- Extra contests where the students participated
- Participation on classes and slack
- Other relevant activities (ex: writing wiki-like articles about algorithms or data structures)
Pedro Ribeiro - DCC/FCUP |
Last update:
