Evaluation Criteria
- (SI) Submitted Implementations: 40%
- (CE) Participation in Competitive Events: 35%
- (PDC): Presentations, Discussion of Solutions and Problem Creation: 25%
Each component has a grade from 0% to 100%.
(SI) Submitted Implementations [40% of your grade]
- We plan to have 11 evaluation problem sets. Each problemset is worth 10% 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 [35% of your grade]
There will be three competitive events where it is expected that the students appear and try to submit during the designated time. The predicted dates for these events are:
- [30%] #01: 1st Contest - 21 Oct
- [30%] #02: 2nd Contest -16 Dec
- [40%] #03: 3rd Contest - Jan?
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 or AtCoder Rounds) to compensate for any contest that did not go well for you (extra participations will be evaluated on a case by case basis).
(PDC) Presentations, Discussion of Solutions and Problem Creation [25% of your grade]
- [50%] (PC) Problem Creation: 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: 26 Jan]
- [25%] (CQ) Code Quality: quality of submitted code (including comments) [deadline: 26 Jan]
- [25%] (CP) Class Participation this will take into account global effort and class participation, taking into account areas such as:
- Extra problems made (above the minimum for having 100% of the SI component)
- Extra contests where the students participated
- Participation on classes and discord
- Any other relevant activities (e.g. writing articles about algorithms and data structures)
Pedro Ribeiro - DCC/FCUP | Last update:
