0123 » History » Version 3
Quentin Labourey, 2018-01-24 11:47
1 | 2 | Quentin Labourey | h1. 01/23 - Discussion on PoM |
---|---|---|---|
2 | 3 | Quentin Labourey | |
3 | *Participants:* |
||
4 | Quentin, Simon |
||
5 | |||
6 | *Goal of the meeting:* Discuss the general state of the processing we want to showcase in sprint 1 and more precisely the problems we might encounter on PoM. |
||
7 | |||
8 | h2. General chain discussion |
||
9 | |||
10 | Ellon and I have been working on providing the right types of data to the DEM module. At the moment the chain from MORSE to the DEM module looks like this: |
||
11 | |||
12 | !existing_chain.png! |
||
13 | |||
14 | With: |
||
15 | * *Fake velodyne*: take as input the pointclouds produced by velodyne, aggregates them into one point cloud, and associate the pose of the robot to it. |
||
16 | * *Point cloud pose stamped* is a data structure defined in IDL for genom3 module from which we can build the DEM |
||
17 | |||
18 | ATM: *No POM*. What we would like is the following : |
||
19 | |||
20 | !wanted_chain.png! |
||
21 | |||
22 | This includes: |
||
23 | * *Changing fake velodyne* : makes it quite a bit harder as this means Ellon needs to "rewrite TF" and keep changes in pose in memory in order to aggregate properly when the robot moves |
||
24 | * *Accepting some |