Project

General

Profile

0116 » History » Version 4

Quentin Labourey, 2018-01-16 15:24

1 1 Quentin Labourey
h1. 01/16
2 2 Quentin Labourey
3
*Participants:* 
4
* From MAG: Vincent Bissonnette, Clément Le Bihan, Raphaël (?)
5
* From LAAS: Andrea, Ellon, Quentin
6
7 3 Quentin Labourey
*Goal of the meeting:* As we are going to test our algorithm chains in MORSE, we need to coordinate our effort on the simulator and collaborate where we can. As Clément already started working full-time on MORSE, we went there to see what was already available and how we can catch-up and improve.
8 2 Quentin Labourey
9 1 Quentin Labourey
h2. MORSE at MAG
10 3 Quentin Labourey
11 4 Quentin Labourey
MAG's goal at the moment is to produce a full working chain integrated into MORSE (and if possible, with our help, directly on our rovers), *by the end of February*. The first version of the processing chains they want to integrate is the following:
12 1 Quentin Labourey
13 4 Quentin Labourey
<pre>
14
Stereovision => Disparity computation => DEM building => Navigation Map => Path planning => Motion control
15
</pre>
16 1 Quentin Labourey
17 4 Quentin Labourey
All the algorithms come from CNES and need integration inside MORSE. The following sensor/actuator flows are already implemented:
18
* Lidar
19
* Stereobench
20
* Pan-tilt unit
21
* Robot control (did not ask which one, but from Simon's report it is a RMP440)
22 1 Quentin Labourey
23 4 Quentin Labourey
At the moment, the interface between MORSE and the algorithms is made via YARP, but they are working on an interface with ROS. The orchestration of scenarios is made through a simple state-machine written in Python. The scenario implemented so far is "Acquire a scan and move forward for a given distance". No localization is performed in MORSE.The pose of the robot is directly given through MORSE and does not come from a MAG algorithm. The machine has then two states:
24
* Move pan-tilt
25
* Go to point
26 1 Quentin Labourey
 
27 4 Quentin Labourey
28
29
*Concerning datatypes:* Right now, they are not using ASN.1 compliant datatypes. Vincent told us that the ESROCOS ASN.1 compiler exists but the did not interface anything with the C struct produced. He proposes that we use ROS datatypes for now and see for interfacing properly afterwards. We agreed on this.
30
31
h2. How LAAS can contribute
32
33
First thing is to provide MAG with accurate simulations of our rovers, in order to test their algorithms and ease integration directly on the rover. They require:
34
* Sensor streams:
35
** Velodyne
36
** Stereovision
37
** S