0228 » History » Version 6
Quentin Labourey, 2018-03-06 14:00
1 | 1 | Quentin Labourey | h1. 02/28 : PoM Discussion |
---|---|---|---|
2 | 2 | Quentin Labourey | |
3 | *Participants:* |
||
4 | Simon, Andrea, Ellon, Pierre, Quentin |
||
5 | 3 | Quentin Labourey | |
6 | *Goal of the meeting*: Discuss the new PoM architecture, taking into account the different frames to handle and the way we're going to handle changes in positions in the past |
||
7 | |||
8 | h2. Sum-up |
||
9 | |||
10 | First, we have to keep a transform tree up to date. The tree used here is represented below: |
||
11 | |||
12 | !frames.png! |
||
13 | 4 | Quentin Labourey | |
14 | 5 | Quentin Labourey | The frames are the nodes of the graph, and the DFPCs that change them are visible in red. Some DFPCs give a transformation between the same frame at two successive times (WO for wheel Odometry, and VO for visual Odometry) while some DFPCs give the transform between two frames at a given time. |
15 | 6 | Quentin Labourey | |
16 | The way we proposed to do it is to index the poses on the highest frequency localization DFPC (Wheel Odometry on principle), and timestamp each observation made by any sensor in order to keep track of the poses we need to memorize. Below is a small example in time commented: |
||
17 | |||
18 | !timeline1.png! |