Ever had problems with dimensionality in your robots' data? Ever wished
you didn't have to manage it all manually?
Wow, that sounds like an informercial. Anyway, the experimental RADAR
extensions for Python developed as part of my research provide
facilities for dealing with dimensioned data directly within the program
code quickly and easily. You can specify the units of data directly in
your code, quickly see what units data is using, and no longer have to
manually convert from one unit to another. The system will also catch
errors in dimensioned data (for example, if you try to tell your robot
to move forward at 3 degrees per second, or add a speed and an angle
together), saving you the headache of debugging errors in dimensionality.
Through the playerc_wrap thin wrapper around the Python bindings for
player, this system supports Player. It will ensure that any dimensioned
data going into and coming out of the Player API is dimensionally
consistent. In the wake of (actually in preparation for as well) the
Player 2 release, I have updated playerc_wrap and the examples to work
with Player 2. You can get these and the modified Python interpreter at
the following page:
I recommend you read the Getting Started guide to help you get up and
running, and check out the examples.
Any feedback on the system (or improvements to it) are most welcome.
Robotics research group, University of Auckland