You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Marathon Match Setup and Management.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Before starting:
27
27
6. Save the scorer config separately with `Save Scorer Config`.
28
28
7. Launch the challenge after the scorer config is saved and operationally ready.
29
29
8. Monitor submissions from the Work app Submissions tab, including score links, artifacts, and ECS runner logs.
30
-
9. If the tester changes during the challenge, publish a new version, update the scorer config, and rerun the latest submissions.
30
+
9. If the tester changes during the challenge, publish a new version and update the scorer config; active configs automatically rerun the latest submissions for the open scoring phase.
31
31
32
32
## Challenge Creation
33
33
@@ -284,8 +284,8 @@ Use this flow when the tester source changes after the challenge is active.
284
284
2. In the scorer section, select the current scorer and click `New Version`.
285
285
3. Create the new version with the updated Java source.
286
286
4. Wait until compilation reaches `SUCCESS`.
287
-
5. Save the scorer config so the challenge points at the new tester ID.
288
-
6.Trigger a rerun of latest submissions for the open Submission/Provisional phase using the Work app rerun control or `POST /v6/marathon-match/challenge/:challengeId/rerun`.
287
+
5. Save the scorer config so the challenge points at the new tester ID. If the config is active, this automatically reruns the latest submission from each submitter for the open scoring phase.
288
+
6.Use the Work app rerun control or `POST /v6/marathon-match/challenge/:challengeId/rerun` only when you need to manually repeat the same latest-submission rescore.
289
289
7. If Review/System scores also need to be regenerated, call `POST /v6/marathon-match/challenge/:challengeId/rerun/system`.
290
290
8. Monitor the rerun ECS tasks, runner logs, artifacts, and review scores.
- Requires the selected tester to be compiled successfully.
299
-
- Requires a phase config that matches the currently open challenge phase.
299
+
- Requires at least one phase config that matches the currently open challenge phase.
300
300
- Fetches `isLatest=true` submissions from Submission API.
301
-
- Queues one ECS task for the latest submission per member.
302
-
- Uses the current open phase's scorer seeds and test count. During Submission this is normally the `PROVISIONAL`config.
301
+
- Queues one ECS task for the latest submission per member per matching phase config.
302
+
- Uses each matching phase config's scorer seeds and test count. During Submission this normally includes both `EXAMPLE` and `PROVISIONAL`when both are mapped to the Submission phase.
303
303
304
-
The response includes the queued submission IDs and ECS task IDs or per-submission errors.
304
+
The response includes the queued submission IDs, phase config type, and ECS task IDs or per-submission errors.
305
305
306
306
System rerun behavior:
307
307
@@ -399,7 +399,7 @@ During the challenge:
399
399
- Watch Submission tab scores and timestamps.
400
400
- Spot-check artifacts for early submissions.
401
401
- Open runner logs for failures, timeouts, compile errors, and missing output.
402
-
- If tester source changes, publish a new version and rerun latest submissions.
402
+
- If tester source changes, publish a new version and update the scorer config. Active configs automatically rerun latest submissions; use the manual rerun control if you need to repeat that rescore.
Copy file name to clipboardExpand all lines: docs/marathon-match-setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -158,9 +158,9 @@ To switch an active challenge to a newer tester:
158
158
1. Publish the new tester version with `PUT /v6/marathon-match/testers/:id`
159
159
2. Wait for `GET /v6/marathon-match/testers/:newTesterId` to return `compilationStatus = SUCCESS`
160
160
3. Update the challenge config with `PUT /v6/marathon-match/challenge/:challengeId` and the new `testerId`
161
-
4.Trigger a rescore of current competitors with `POST /v6/marathon-match/challenge/:challengeId/rerun`
161
+
4.The update automatically reruns the latest submission from each submitter when the config is active. You can also trigger the same rescore manually with `POST /v6/marathon-match/challenge/:challengeId/rerun`.
162
162
163
-
The standard rerun endpoint selects `isLatest` submissions for the challenge in received order and launches ECS scorer tasks for them in parallel using the scorer config for the currently open challenge phase. This does not happen automatically when `testerId` changes, so the rerun call is the operational step that recalculates Submission/Provisional scores.
163
+
The standard rerun endpoint selects `isLatest` submissions for the challenge in received order and launches ECS scorer tasks for every scorer config that matches the currently open challenge phase. During Submission, this normally reruns both `EXAMPLE` and `PROVISIONAL` scoring when both configs are mapped to the Submission phase, so the latest displayed scores are recalculated with the current tester.
This endpoint selects the latest submission for each member in received order and launches ECS scorer tasks in parallel using the scorer config that matches the currently open challenge phase. During Submission this is normally the challenge's `PROVISIONAL`phase config. Use it after changing the tester or when current latest submissions need to be rescored without waiting for new submission events.
123
+
This endpoint selects the latest submission for each member in received order and launches ECS scorer tasks in parallel for every scorer config that matches the currently open challenge phase. During Submission this normally includes both `EXAMPLE` and `PROVISIONAL`when they are mapped to the Submission phase. It is also triggered automatically after an active challenge's `testerId` changes, and can be called manually when current latest submissions need to be rescored without waiting for new submission events.
0 commit comments