Final project 1 grader¶

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:

1. 200 points, which means an accepted submission (so-called minimal viable completion), require the following:
   • Successful completion of functional and integration tests (same hash)
   • Pedantic compilation successfully (same hash)
   • Valgrind has been run, but passing the grader is not required (same hash)
   • Perftests have been executed without timeouts or, for example, seg.fault errors (same hash)
   • Perfestimate has been excecuted (same hash)
   • Docs grader has been passed with any hash
2. 150 points - optimization points, 50 points per optimized function (get_affiliations_alphabetically, get_affiliations_distance_increasing, find_affiliation_with_coord). 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.
3. 250 points - performance test points. Students can get statistical info about the efficiency of their work through a separate results server (referred to as eduML). Score categories (ranges) are defined once a sufficient number of submissions have been collected, but at least one week before the deadline.