Right now the RRT has much less documentation than I'd like (the RRT is one of the most useful parts of our codebase, since it's modularized). We need to try to make thorough docs for the rrt.

Once we have most of the way done to this, I'll add documentation generation so we can have a RRT docs site we can link to on our README, just like robocup-software and robocup-firmware.

This is a goo

There are many different places around where we setup specific timeouts, errors values and that type of thing. See here for example. It would be really nice to condense all these configs down into a single location under a Passing config or a Shooting config.

It would be nice to build up the kicker co

Is your feature request related to a problem? Please describe.

Can't delete annotation types.

Describe the solution you'd like

Allow deletion of annotation types in the web-ui.

Workaround

$ sudo 

Using Qt Style Comment to Doxygenize grSim.

Describe the feature
This adds documentation as comments to functions, classes, namespaces, files, etc. throughout the code using doxygen macros.

Remove unit tests from documentation (as discussed today).

Relevant items from (#121):

Remove names after @file in Doxygen
Reason: Apparently we do not actually need any name after this tag, so we should just remove it using a script

Lors d'un but, il faut que les robots dansent.

Currently we do not have solid documentation for the majority of our build system. @petersonev has agreed to put some work into making it more understandable for all of us.

The way the defender algorithm works currently is a bit magical. Some documentation on what happens and why would be nice

Add an audio spectrum visualizer on the victim board tab.

This will help the operator and the judge see that there's an actual audio activity.

See:

• https://github.com/strengthmate/web-audio-fft-visualization-with-react-hooks
• https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API/Visualizations_with_Web_Audio_API
• https://github.com/nasso/urmusic
• https://github.com/a-vis/sp

When new users encounter the GUI, they may be overwhelmed and not know what to. To counter this, I propose the integration of Intro.js. After they have read the documentation on core concepts, the Intro.js framework could tour them around the software so they have a general idea of what's going on.

This walkthrough should be accessible through the 'help' menu & when Robo

The CTRE lib is a little bit old, it would be interesting to check what is new in the most recent version. If it's deem interesting we could update it.

During RoboCup 2017, two teams failed to run in the Gazebo challenge because their kill.sh scripts were called immediately. 35880e7c39b33284723c9acf214c96966bede609 might fix this, but this should be verified.

Also, we should check if we can print the reason for a player being killed.