Actions » History » Version 5
Quentin Labourey, 2018-01-09 17:54
| 1 | 1 | Quentin Labourey | h1. Actions |
|---|---|---|---|
| 2 | 2 | Quentin Labourey | |
| 3 | h2. Concerning DFNs |
||
| 4 | |||
| 5 | *A.: Fault detection in PoM:* this comes down to data interpretation. Each time a pose is computed, an associated covariance is produced. The question is: how can the covariance (or any measure of error) be used to detect when a localization module is being faulty? |
||
| 6 | *Leads*: outlier covariance? Slippage detection? |
||
| 7 | |||
| 8 | --- |
||
| 9 | |||
| 10 | *A.: Fault detection in DEM building:* Each time a new Point cloud is available, a local DEM is built. In order for it to be fused with a larger DEM, we have to make sure that the localization of the robot is precise enough, else we are going to fuse two different geographic area and add noise to the DEM. |
||
| 11 | *Leads*: outlier height could be detected? Quadratic error measure between local DEM and internal/global DEM? |
||
| 12 | |||
| 13 | 4 | Quentin Labourey | --- |
| 14 | 1 | Quentin Labourey | |
| 15 | 4 | Quentin Labourey | *Data types definition and taxonomy:* Lots of datatypes are already available in the rock core datatypes, ASN.1 format. However some of our needed datatypes do not exist yet and have to be defined. |
| 16 | *Leads*: create a list of all datatypes yet to be defined and start producing corresponding ASN.1 files. |
||
| 17 | 3 | Quentin Labourey | |
| 18 | 4 | Quentin Labourey | --- |
| 19 | 2 | Quentin Labourey | |
| 20 | 5 | Quentin Labourey | *A. DPM data storing:* It is important to know what kind of data are stored inside the DPM and made accessible to other modules/other OGs. |
| 21 | *Leads*: create a list of all data products, intermediate data products, and raw data in each DFPCs and see which ones need to be internally stored. |
||
| 22 | |||
| 23 | h2. Concerning experimental evaluation |
||
| 24 | |||
| 25 | *A. Prepare a development plan and a validation plan for LAAS robots* |
||
| 26 | *Leads:* |