François Felix Ingrand » OSMOSIS

h1. LAAS Code (GenoM3) for the OSMOSIS show case.

This project contains all the GenoM3 components needed for the "OSMOSIS case study":https://osmosis.gitlab.io/ . It can be used with ROS or PocoLibs middleware, with the "simulation in gazebo":https://osmosis.gitlab.io/experiment/simulation.html or on the real robot.

h2. Robot setup

Below is a drawing of the Robot Setup. All the components with are available as sub-projects.

The components are:

* "IMUDriver-genom3":https://redmine.laas.fr/projects/imudriver/gollum/README : complete and compiles, properly tested on the real IMU.

* "LaserDriver-genom3":https://redmine.laas.fr/projects/laserdriver/gollum/README : tested with an Hokuyo UTM-30LX at LAAS and on the real robot.

* "PotentialField-genom3":https://redmine.laas.fr/projects/potentialfield/gollum/README : complete and compiles, tested with the simulator and the real robot.

* "SafetyPilot-genom3":https://redmine.laas.fr/projects/safetypilot/gollum/README :  complete and compiles,  tested with the simulator and the real robot.

* "Teleop-genom3":https://redmine.laas.fr/projects/teleop/gollum/README : complete and compiles, tested on the real robot.

* "RobotDriver-genom3":https://redmine.laas.fr/projects/robotdriver/gollum/README : we do not have the source to fully implement this component. For now it is a proxy to get the /odom and /joy topics from the real robot controler (and copy them in the proper port), and provides the /summit_xl_control/cmd_vel topic to the real controller from the Safety Pilot Cmd port. This module only makes sense when using PocoLibs as it will "translate" topics from ROS to GenoM3 ports and vice versa. Otherwise, you may as well directly map to the ros topics. 

* "GPSDriver-genom3":https://redmine.laas.fr/projects/gpsdriver/gollum/README :  complete and compiles, tested with the simulator and on the real robot.

* "Localization-genom3":https://redmine.laas.fr/projects/localization-g3/gollum/README : this component is basically "pom-genom3":https://git.openrobots.org/projects/pom-genom3?jump=welcome . In simulation, it will grab the /odom Odometry  topics from gazebo, translate it ina  pose-estimator format used by pom-genom3 and then pom will produce the pose which can be used directly. On the real robot, we use pom which grab GPS position, Odometry speed and IMU speed/accel and merge them.

* "Navigation-genom3":https://redmine.laas.fr/projects/navigation/gollum/README : complete and compiles,  tested with the simulator.

* "NRWLSensor-genom3":https://redmine.laas.fr/projects/rwlsensor/gollum/README : complete and compiles,  tested with the simulator.

The figure below show all the components as well as their ports (produced by the component they are attached to, and read by the component(s) with an arrow pointing to the port). For example the @pose@ port is produced by _Localization/POM_ and read by _Navigation_, _RWLSensor_ and _PotentialField_.

---

!{width:600px}OSMOSIS.png!

---

Most components are using some IDL types defined in the "osmosis-idl":https://redmine.laas.fr/projects/osmosis-idl project. There are also types comming from the "openrobots-idl":https://git.openrobots.org/projects/openrobots-idl?jump=welcome project.

h2. Simulation setup

There is also a simulation setup which can be used (instructions on how to install it can be found "here":https://osmosis.gitlab.io/experiment/simulation.html ). It has less functional modules (as some of them are handled by the Gazebo simulator). All the ports shared with the simulator (IMU, LaserScan, Odometry, Cmd) are ROS topics and are properly defined in IDL as to correspond to their ROS counterpart. Still, Pom does a poor job when merging Odometry, GPS and IMU in simulation (probably because the Odometry is terrain truth, so using a kahlman does not make sense). So we just grab /odom for position.

--- 

!{width:600px}simu.png!

---

h2. Scripts to run the whole demo