Week 13 Overview

During this thirteenth week, I continued testing the RADI engine for the Unibotics platform and resolved a significant issue within it.

First, the development team released a new version of RADI, version 4.5.10, which included some bug fixes and introduced a new exercise, ‘Obstacle Avoidance’. I proceeded to test this new exercise and found that it worked correctly without any errors.

Additionally, a problem similar to the previously detected ‘CV2’ module issue was found. In the ‘Amazon Warehouse’ exercise, the ‘ompl’ module, along with the ‘CV2’ module, was not being detected. This indicated that the issue was external to the modules themselves.

Finally, I discovered the root cause of the module detection problem. By examining the error messages, I noticed they were generated by ‘pylint’, a tool used to analyze Python code before execution within RADI. I realized that pylint was not detecting the modules, and upon manually updating it to a more recent version, it started recognizing the modules. I made the necessary changes for the tool to work with the functioning version and sent this to the development team. Once the development team verified the changes, they released a new version of RADI, version 4.5.11, incorporating these updates.