Essa é uma revisão anterior do documento!
Tabela de conteúdos
Routine
The routine represents the execution of the user's code in a specific arena. The routine panel, located in the upper left corner of sBotics, allows you to start, stop, and restart the simulation. Routine information, such as score, time, and multipliers, are displayed in the upper center of the screen, as illustrated in the image below.
To start the routine, click the “play” symbol. To stop it, click the square in the same location. If you wish to restart the scenario, use the restart icon (↺
).
Console
The console is the main tool for data output in sBotics, along with the Buzzer and LED components. It allows you to print sensor values, display text, and describe the robot's step-by-step execution.
It is possible to clear the console manually through the broom icon and access the detailed log by clicking the document icon, both located on the right side of the panel.
Log
The log file, accessible through the “Document” icon in the console panel, is an external record to sBotics. It allows you to generate graphs, .csv
files, and other complex implementations from the data generated during the simulation.
Scorer/Tracker
sBotics uses tiles to score the routine. Each tile has a score value, which is added (or multiplied) to the total as the robot navigates the arena.
The path, formed by tiles, can be divided into smaller segments, called “trajetos” (routes), using “Checkpoints.” A typical sBotics arena can contain one or more trajetos. Deviating from the correct trajeto can result in a “Progress Failure.”
Trajeto / Checkpoints
As mentioned earlier, the trajeto is subdivided into checkpoints. In the routine panel, the checkpoint tiles are identified by orange arrows, which indicate the direction in which the robot will be repositioned when starting a new attempt from that checkpoint. If the trajeto passes through the same tile in different positions, multiple arrows will be displayed.
In this way, the arena below, when considering the checkpoints, is segmented into small trajetos.
Progress Failure
If the robot deviates from the expected trajeto, a progress failure counter will be displayed in the lower corner of the interface, indicating the type of failure and the remaining time before penalization. In the example below, the counter indicates a failure due to robot inactivity.
When it reaches zero, a new attempt is started, forcing the robot to restart.
For progress failures related to the trajeto, deviating more than two tiles results in a “grave” (severe) failure, while deviating only one tile results in a “leve” (minor) failure. The time granted for correction varies according to the arena configuration, being 50 seconds for minor failures and 10 seconds for severe failures in OBR.
Observe nas imagens acima que desviar um ladrilho é indicado por laranja, enquanto desviar dois ou mais é indicado por vermelho.
Attempts Panel
The routine panel allows you to start new attempts and advance to other trajetos, if available. It also displays the routine status in relation to attempts and trajetos.
![]() | ![]() | ![]() |
---|---|---|
Path | No. of Tries | Total Attempts |
Current trajeto number | Attempt number in the current trajeto | Total number of attempts across all trajetos |
Observação: O painel de tentativas e as funcionalidades de nova tentativa e avanço só estão disponíveis em arenas do tipo “linha/trajeto”.
New Attempt / Advance
It is possible to restart the current trajeto or advance to the next, restarting the robot's position and code.
Note: In some arenas, the “Advance” button will only be available after a minimum number of attempts (3 in OBR).
To keep values between attempts, use static variables: “estatico numero
” / “estatico texto
” / “estatico booleano
” in rEduc or 'static double' / 'static string' / 'static bool' in C#.
Execution Report
The execution report, displayed at the bottom of the attempts panel, records routine events in two formats: simplified and detailed.
Both reports allow recreating the robot's path and identifying scoring and failure points. The detailed report is used by the competition system to verify execution integrity.
Example of a report excerpt:
[0:00] Pontuação adicionada; ↳ 5 Pts. (×1,00); ↳ 1 @ 1. [0:00] Entrou no ladrilho pela primeira vez: 0; [0:05] Superou ladrilho: 0; [0:05] Entrou no ladrilho pela primeira vez: 1; [0:11] Pontuação adicionada; ↳ 15 Pts. (×1,00); ↳ 1 @ 1.