Skip to content

Task 0 — Submission


One result file, on the eYRC portal. Nothing on this documentation site is a submission — the P Controller page is where you go to find your Kp value, not to submit it.

#WhatWhereMarks
1Installation + Kp result — NV#<team_id>.jsonPortal100

See Grading below for exactly what each of those 100 marks depends on.


Terminal window
pip3 install -U eyantra-autoeval

If the command is not found afterwards, pip installed it into ~/.local/bin, which is not on your PATH:

Terminal window
echo 'export PATH=$PATH:~/.local/bin' >> ~/.bashrc
source ~/.bashrc

Part of this task’s score comes from a number you choose yourself: the proportional gain Kp of a P controller.

Open the P Controller page and use the interactive slider there to see how different Kp values drive the simulated robot. Tune it until you find the best value (Note: It will never follow the line perfectly, but you have to look for best one), and note it down. You’ll be asked for this exact number in the next step.

Run the evaluation. Nothing else needs to be running for this one:

Terminal window
eyantra-autoeval evaluate --year 2026 --theme NV --task 0

Partway through, it will pause and ask you to enter your Kp value — type the number you tuned to on the P Controller page and press Enter. Once it finishes, it writes a file such as result-2026-NV-0-20250904.json into whichever directory you ran it from. A successful run looks like this:

Auto-eval script output

Rename it to NV#<team_id>.json — so team 1455 uploads NV#1455.json — then upload it on the eYRC Portal — Task 0.


This task is graded out of 100 marks, from the single result file in Step 3. Both rows below come from that one file — there’s nothing else to submit.

ComponentMarksWhat you doWhenValue usedWhere it’s submitted
Installation80Install Miniconda + CoppeliaSim, then run the evaluatorStep 3Detected automatically — SUCCESS = full marks, FAILED = zero, no partial creditNV#<team_id>.json on the portal
Kp value20Tune Kp on the P Controller pageStep 2, before running the evaluatorWhatever you type at the tool’s prompt in Step 3Same NV#<team_id>.json