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%.
Current Evaluation State
Final grades are now available! [protected access]
(SI) Submitted Implementations
See detailed grades for this evaluation item
- There are 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 40%, the second one 30%, the third one 20% and the fourth one 10%. This means that:
- Solving one problem is worth 40%
- Solving two problems is worth 70%
- Solving three problems is worth 90%
- 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 82% (70% for the first two problems and 12%=20%-4*2% for the third problem)
- 3 problems before the deadline and 1 problem 6 days after the deadline will give you 90% (90% for the first three problems and 0% for the last, since the penalty of 6*2% is more than than the 10% 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:
More information will be given when the events have a fixed date. There is no mininum grade, but 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 or Topcoder SRMs) 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).
- [30%] (PP) Presenting a Problem: mandatory oral presentation of one of the student's accepted problems (selected by the professor) [we will have a session with presentations from all students on Jan 22]
- [30%] (GE) Global Effort: overall appreciation of the student overall effort on the course:
- Quality of submitted code (including comments)
- Extra problems made (above the minimum for having 100% of the SI component)
- Extra contests where the students participated
- Participation on classes and piazza
- Other relevant activities (ex: writing wiki-lie articles about algorithms or data structures)
Pedro Ribeiro - DCC/FCUP |
Last update:
