cyberbotics / competition-record-action Goto Github PK

Currently the action uses environment variables as inputs. GitHub provides inputs for actions which have extra functionalities like making inputs required, adding a helpful description or settings a default value.

We could also split the first parameter INPUT_INDIVIDUAL_EVALUATION into its three separate inputs (id:repository:private) as it would make the code more understandable and easier to maintain in the future. This would require to also modify the competition workflow files to use said inputs.

The re-build of the Webots and participant dockers could be skipped in a round.

If the new competitor wins a game, the last competitor gets a wrong value for its performance in participants.json.
Unfortunately, this prevents new competitors from entering the competition until the participant.json is manually fixed.

On the leaderboard and participants.json file, we should include a link to the log of the GitHub action corresponding to the last game of each competitor. That would facilitate the understanding that the log is available and corresponds to a specific game.

The current implementation uses TCP/IP to communicate between the controller container and the Webots container.
However, Webots also supports using IPC to communicate across containers through a shared volume containing shared memory segments and pipes. Such a solution is faster than using TCP, especially for camera and lidar images. Therefore, we should use this approach instead of TCP/IP.