In this blog, I'll be posting about my experience as an intern at JdeRobot.
First, during this ninth week of internship, I have reviewed a problem detected in the Follow Line exercise by which, when running the application and changing the world, the kart goes off the circuit when the application is started in this new world with the reference solution, forcing the user to reload the application in order for the kart to run correctly. After the review, I have opened an issue of it.
On the other hand, I have helped my co-worker Carlos by reviewing a problem by which the ExerciseControl component of Robotics Academy was not being render correctly on the webpage, showing the ExerciseControl of Unibotics instead. The problem came from using the same ExerciseControl component of Unibotics in both cases in the exercise template.
I have also begun to investigate the Unibotics’ Play-Pause, Reset, Save and Evaluations buttons scripts because they have stopped working due to the widgets’ refactorization and the use of Robotics Academy as a submodule of Unibotics. I’ve found that most of these problems, especially in the case of the Play-Pause and Reset buttons, come from switching to use the new four-step RAM and using the Robotics Academy commsManager instead of Unibotics’ one. For these reasons, there are differences in RAM state names and commsManager commands that cause problems.
I tried to adapt the code of Unibotics’ Play-Pause button without success, achieving a partial solution, but with one problem: when doing Pause and then Play in the exercise, the Follow Line’s kart route is reset. This is due to the inclusion of a terminate_application command before the runCode command. However, removing this terminate_application causes transport errors in the RADI.
In response to this problem, Unibotics' Play-Pause code has been adapted using as a base the code of Robotics Academy’s Play-Pause button script, which was already adapted to the case of the new four-step RAM and the current commsManager, using the command resume for the control of the pause.
Also, the Reset button has been adapted correctly, correcting the states and commands to ones that the new RAM and commsManager recognize.
I’ve assigned myself the Unibotics’ registration error issue, but I haven’t been able to make much progress with it since last week. The error seems to be related to a url that is not detected, ‘activate’.
Finally, I have checked the other buttons (Save, Evaluations and Frequencies) as they were still giving problems. Save button's problems appear to be related to RAM states and Evaluations button's problems with a localBackend variable whose content is 'undefined'.