AIM stands for Artificial Intelligence Modules (AIM website).
The AIM tools are meant for management of separate modules that each have AI functionality. They can be compared with the utilities that are provided with ROS, such as roscreate-pkg etc (of which we were not aware at the time), or with nodejs, such as npm (of which we were neither aware). The tools work together with the rur-builder, a (python) backend for omniidl.
The current AIM tools have been in operational mode for a long time with YARP. The newest useful addition has been Node.js, which allows us to deploy the modules using the npm (node package manager) system.
The goal of the AIM tools is to allow programmers to do rapid prototyping for multiple platforms and connecting them by multiple means without being bothered by the middleware specifics. We want you to be able to run a module on your smartphone, connect it to a server that you happen to have, and go from there to your raspberry PI and your television set. We do want to build an ecosystem where many AI modules are working together and do want to allow you to run our software on your own servers. Monetizing this ecosystem will be via the website dodedodo.com that will allow you to find other modules and function as a hub to download binaries from, it will not be the place though which all application traffic has to pass, but just a sophisticated name service.
The maturity of this software can be improved. However, it has been used already in quite some different scenarios. One of them is to connect to the servers of an Almende spinoff in sensor data cloud services (Sense Observation Systems), another use case has been the Surveyor robots, a third on the unmanned aerial vehicles of FireSwarm.
There are no known alternatives. Most modular approaches tie the user to a certain middleware (but do allow you to use different programming languages).
The AIM tools work together with the rur-builder. This needs to be installed first, follow the instructions.
Set the installation path, on Linux systems this is most often /opt, but it is up to you, let us say you want to use ~/Downloads:
set SETUP_PATH=~/Downloads # directory where you prefer to install fromTo install the aimtools, this is similar:
cd $SETUP_PATH
git clone https://github.com/dobots/aimtools.git
cd aimtools
make
sudo make installMultiple aim* binaries are now installed in /usr/bin, such as aimcreate-pkg. Type aim -h to get a list.
Now, define the environmental variable AIM_WORKSPACE, this will become a collection of repositories with AI modules, collected from multiple github repositories.
export AIM_WORKSPACE=$HOME/aim_workspace
echo $AIM_WORKSPACE >> ~/.bashrc # in case you use bash (check with e.g. `sh --version`).
And now you are ready to get actual AI modules:
aimget examples https://github.com/dobots/aim_modules
aimget robotics https://github.com/mrquincle/aim_modules
aimget navigation https://github.com/vliedel/aim_modulesThis will allow you to run all the modules defined in these repositories. Build one if you like to:
cd $AIM_WORKSPACE/examples
aimmake ReadModuleOptionally, you can now remove the files in $SETUP_PATH, however, if you quickly want to upgrade to newer versions, you might better of leaving them there. Anyway, to remove them:
cd $SETUP_PATH
rm -r aimtoolsHow to create your own module is not part of this readme, it is explained on the AIM website. However, to lift a little bit of the curtain, in the end you will need to write your functionality in C++ in a function called Tick() using ports to communicate with other modules:
void WriteToFileModuleExt::Tick() {
double input = *readInput();
ofstream myfile(cliParam->filename.c_str(), ios::app);
myfile << input << '\n';
myfile.close();
}The copyrights (2012) belong to:
- Author: Anne van Rossum
- Author: Scott Guo
- Almende B.V., http://www.almende.com and DoBots B.V., http://www.dobots.nl
- Rotterdam, The Netherlands