Finished implementing and connecting and testing the ControllerStatusBanner class into the flying agent GUI as a first step towards simultaneously making this cleaner and fixing the annoying GUI crash bug (other source of the bug could be the graphing in the CS1 controller tab)

Added ControllerStatusBanner class to the flying agent GUI as a first step towards simultaneously making this cleaner and fixing the annoying GUI crash bug (other source of the bug could be the graphing in the CS1 controller tab)

Small changes to active controller highlighting in the controller tabs part of the Flying Agent GUI in an attempt to remove the bug that causes the GUI to crash.

Made the maximum step duration 20 seconds for the CS1 controller. And changed the default values displayed in the fields

Added vertical banner to all GUI tabs indicating whether that controller is active not. Tested in simulation (there is a small chance this causes the GUI to occassionaly crash becuase of simultaneous setting of the properties of the banners). Tested in Simulation. Also fixed small mistake in the coordinator launch file

Connected the CS1 integrator buttons to the GUI and tested to be working in simulation. Needs testing on the real system

Purged the code of all occurances of the terminology teacher. This was replaced by either master or by System Config GUI

Added Mocap Emulator and complete the Quadcopter Simulator class. Tested and working on a single laptop. Next step to test on a network of laptops

Added the remote controller tab widget to the GUI as a copy of the template controller. Next step is to connect it up

Added remote controller to GUI menu, enable and yaml buttons, and a tab. Compiles but needs testing. The tab itself still needs to be added

Fixed System Conig GUI so that objects with naming convention CFXX are plotted as question marks for an XX id that is greater than 9 (previously nothing was plotted)

The test motors controller is now integrated to the flying agent client. The Default controller has the z integrator turned on, and the setpoint smoothing was slightly changed

Default controller compiles and is tested. Once remaining discrepancy is that the default controller switches into integrator mode too early

Finished implementing the Default controller (except for the integrator). Needs compiling and testing. (Also changed the ClientConfig.yaml to be FlyingAgentClientConfig.yaml)

Mostly finished with converting the Flying Agent Client to the Default controller. Needs comoiltion testing. Next step is to make the Default controller able to perform take-off and land manoeuvres

Started process of converting the Flying agent client from the safe controller to the default controller, and streamlining things at the same time. Currently compiles and flys, but needs cleaning up and proper implementing of the take-off and land functions.

Small changes to the picker controller for paramter loading, and to Flying agent GUI for units of the yaw error