Summer – Writing an article for a conference
Summer was not the most productive period of the project. Due to the holidays of the different people involved, development was significantly slowed down.
After successfully training the networks described in the previous post, I tried to train the final version, with the arms completely free. Unfortunately, I was not able to get it working successfully.
After this failure, the training process had to be paused because we decided to write an article about our project and submit it to a conference. Since the free-arm motion is still under development, we decided to focus the article on the full-body network and leave the free-arm motion as part of the future improvements.
My contribution to the article was to write about the robot and simulators we were using, as well as the programs we were developing and the tests we performed on the network.
The tests were the main focus of my work. Although we had tested the network before, we did not have any concrete quantitative results, since this version was still under development.
For this reason, I developed a ROS2 node that sends a Twist command to the robot for 10 seconds and calculates the final position it should reach if the command is followed without any error. Once the robot finishes moving, the node calculates the error between the desired position and the actual obtained position.
I performed this test both in Gazebo and in MuJoCo, the original simulator used for the network. The results showed that the position error was larger in Gazebo than in MuJoCo.
I also repeated the test while changing the inference rate of the network, from 10 Hz to 70 Hz. This showed that the best inference rate in practice was around 60 Hz, while the network remained stable even at 20 Hz.
The errors we observed were acceptable. With a reactive controller on top of the network, the robot can move without any major problems, since small deviations from the desired trajectory can be corrected by sending another Twist command towards the desired position.
The main issue we noticed is that the robot tends to turn slightly to the right. This means that part of the observed error could come from the ROS2 code rather than the network itself. We still have to investigate the reason for this behavior.
Summary
- Failed to train the final network with completely free arms.
- Contributed to writing the conference article.
- Developed new tests to quantitatively evaluate the network.
- Compared the network’s performance in Gazebo and MuJoCo.
- Tested different inference rates, finding 60 Hz to be the best rate in practice.