Actions » History » Revision 2
Revision 1 (Quentin Labourey, 2018-01-09 17:16) → Revision 2/5 (Quentin Labourey, 2018-01-09 17:40)
h1. Actions
h2. Concerning DFNs
*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?
*Leads*: outlier covariance? Slippage detection?
---
*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.
*Leads*: outlier height could be detected? Quadratic error measure between local DEM and internal/global DEM?
--
Make budget for the M3 operation (PM3_24)
- Cf interrobot communications ? -> not existing directly, everything goes through ground station (multi robot scheme and setup still need to be defined)
- balance of partners involvment in the DFPC, state where LAAS will effectively contribute -> still TBD
- DataTypes definition and taxonomy -> still more work to do on this (DEM)
- DPM: raw data, intermediary products, data products- cf ORB Slam
- Prepare a development plan and a validation plan for LAAS robots -> in boxes
- sujets de stage ? -> TBD (different DFIs of the same DFNs, e.g. test different visual extractors)
- Choisir la liste des capteurs, se faire 2 super robots (caméra panoramique ?) ->