Document setting timelimit strategy

Author: vmcj

doc/manual/config-basic.rst

@@ -129,6 +129,7 @@ Before a contest, you will want to have tested your reference
 solutions on the system to see whether those are judged as expected
 and maybe use their runtimes to set timelimits for the problems.
 
+
 The simplest way to do this is to include the jury solutions in a
 problem zip file and upload this. You can also upload a zip file
 containing just solutions to an existing problem. The zip
@@ -140,4 +141,11 @@ it need not have started yet). You can verify whether the submissions
 gave the expected answer in the Judging Verifier, available from
 the jury index page.
 
+After this check change the evaluation to full in the configuration
+page and rejudge with a reasonable overshoot to distinguish between the
+slowest *Accepted* solution and the fastest *Time Limit Exceeded*.
+As a rule of thumb set the timelimit to twice the slowest *Accepted*
+solution. The Statistics/Analytics page of each problem has a graphic
+overview for those submissions.
+
 .. _ICPC-compatible teams.tsv files: https://ccs-specs.icpc.io/2021-11/ccs_system_requirements#teamstsv

webapp/src/Controller/Jury/JuryMiscController.php

@@ -247,18 +247,8 @@ public function judgingVerifierAction(Request $request): Response
     {
         /** @var Submission[] $submissions */
         $submissions = [];
-        if ($contest = $this->dj->getCurrentContest()) {
-            $submissions = $this->em->createQueryBuilder()
-                ->from(Submission::class, 's')
-                ->join('s.judgings', 'j', Join::WITH, 'j.valid = 1')
-                ->select('s', 'j')
-                ->andWhere('s.contest = :contest')
-                ->andWhere('j.result IS NOT NULL')
-                ->setParameter('contest', $contest)
-                ->getQuery()
-                ->getResult();
-        }
-
+        /** @var ContestProblems[] $problems */
+        $problems = [];
         $numChecked   = 0;
         $numUnchecked = 0;
 
@@ -272,6 +262,20 @@ public function judgingVerifierAction(Request $request): Response
 
         $verifyMultiple = (bool)$request->get('verify_multiple', false);
 
+        $contest = $this->dj->getCurrentContest();
+        if ($contest) {
+            $problems = $contest->getProblems();
+            $submissions = $this->em->createQueryBuilder()
+                ->from(Submission::class, 's')
+                ->join('s.judgings', 'j', Join::WITH, 'j.valid = 1')
+                ->select('s', 'j')
+                ->andWhere('s.contest = :contest')
+                ->andWhere('j.result IS NOT NULL')
+                ->setParameter('contest', $contest)
+                ->getQuery()
+                ->getResult();
+        }
+
         foreach ($submissions as $submission) {
             // As we only load the needed judging, this will automatically be the first one
             /** @var Judging $judging */
@@ -329,6 +333,7 @@ public function judgingVerifierAction(Request $request): Response
             'verified' => $verified,
             'nomatch' => $nomatch,
             'earlier' => $earlier,
+            'problems' => $problems,
             'verifyMultiple' => $verifyMultiple,
         ]);
     }

webapp/templates/jury/check_judgings.html.twig

@@ -99,4 +99,15 @@
     {{ checkJudgings.verifyResults('earlier', 'Verified earlier', earlier, true) }}
     {{ checkJudgings.verifyResults('nomatch', 'Without magic string', nomatch, true) }}
 
+    {% if problems != [] %}
+        <h2>Problem runtime analytics</h2>
+        You probably want to <a href="{{  path('jury_config') }}">fully</a> judge all submissions with enough overshoot
+        to see the maximum runtime for <code>Accepted</code> solutions and tune those against expected
+        <code>Time Limit Exceeded</code> solutions.<br>
+        {% for p in problems %}
+            {% set link = path('analysis_problem', {'probid': p.probid, 'view': 'hidden'}) %}
+            <a href="{{ link }}">{{ p | problemBadge }}</a>
+        {% endfor %}
+    {% endif %}
+
 {% endblock %}