For anyone currently using the "CyberCitySharedFunctionality" folder to upload the module's data to the server as well as receive it back by entering the correct flag, the folder itself has some libraries that are related to an eInk text/image display device that connected to each of the modules which previously used within the Cyber City project.
Unfortunately, as for our current project, we're not using the same display modules (or not even using them) anymore compared to last year's Robotic team. Consequently, some code optimisation will be needed so that it can reduce the project's data size, which will result in better performance in all aspects of the project itself.
(An example for clean-up section)
However, the main reason is to help those that is not yet using this folder for their modules not to get headaches about why such questionable errors appeared.
For anyone currently using the "CyberCitySharedFunctionality" folder to upload the module's data to the server as well as receive it back by entering the correct flag, the folder itself has some libraries that are related to an eInk text/image display device that connected to each of the modules which previously used within the Cyber City project.
Unfortunately, as for our current project, we're not using the same display modules (or not even using them) anymore compared to last year's Robotic team. Consequently, some code optimisation will be needed so that it can reduce the project's data size, which will result in better performance in all aspects of the project itself.
However, the main reason is to help those that is not yet using this folder for their modules not to get headaches about why such questionable errors appeared.