Final project 1 grader¶

Final grading goes step by step

The final evaluation utilizes ready submissions, which is why the grader checks before submission that all required sub-graders can be found with the given git commit hash. If they are not found, the work cannot be submitted.

Steps for the final evaluation, also see the image below:

200 points >= pass criteria, requires the following:

Grader	Same hash
Successful completion of functional and integration tests	✅
Pedantic compilation successfully	✅
Perftests have been executed without timeouts or seg.fault errors	✅
Perfestimate excecuted (same hash)	✅
Valgrind has been run; passing not required	✅
Docs grader passed	Any hash

150 points - optimization points, points for each optimized function (70p for get_places_alphabetically, 80p for get_places_distance_increasing). Optimization requires that the function operates more efficiently when run frequently compared to a single run. In the chart shown, the number of iterations is 20.
250 points - performance test points. Students can get statistical info about the efficiency of their work in comparison with others through a separate results server (referred to as eduML, check the left sidemenu). Score categories (ranges) are defined followingly:
- 250p: <= 1.350.000 (command count)
- 200p: <= 3.300.000
- 150p: <= 5.500.000
- 100p: <= 7.000.000
- 50p: <= 10.000.000

Attention

This grader accepts only 5 submissions. Make sure to test your code with the previous graders before submitting it here.

A+ esittää tässä kohdassa tehtävän palautuslomakkeen.