View source for Project 2014-2015-CannonBall

=Preambule=

The project subject [[CannonBall_de_voitures_autonomes]]

This project is handled from years to years by Polytech and Ensimag Students : 

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

'''From january 14th 2015 march 2nd 2015''' : Malek Mammar and Opélie Pelloux-Prayer from Polytech'Grenoble. [http://air.imag.fr/index.php/Project-2014-2015-CannonBall Here]

This project is based on the work of Jules Legros and Benoit Perruche. 

It has also been handled by Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin.

It is now handled by four Polytech students : Alexandre LE JEAN / Malek MAMMAR / Ophélie PELLOUX-PRAYER / Hugo RODRIGUES

=Project presentation=


= Team =

* Supervisors : Amr Alyafi, Didier Donsez

* Members : Malek MAMMAR / Ophélie PELLOUX-PRAYER / Alexandre LE JEAN / Hugo RODRIGUES

* Departement : [http://www.polytech-grenoble.fr/ricm.html RICM 4], [[Polytech Grenoble]]

=GitHub=


=Specifications=

* prendre en main OpenCV sur Windows 8, Android et Ubuntu
* réaliser un banc d'essai de OpenCV pour la reconnaissance de marqueurs sur les différentes plateformes et pour différents modèles des caméras * externes et builtin. Utiliser les algorithmes existants.
* réaliser un algo de pilotage du véhicule (contrôle trajectoire, maîtrise de l'accélération, ...).
* réaliser un simulateur de pilotage de véhicule.
* évaluer les algorithmes sur les véhicules.
* mettre en place sur un serveur un infrastructure de collecte des paramètres de conduite du véhicule en s'appuyant sur les composants de * * * * Eclipse M2M (Mosquitto, Paho), Node-RED, Redis.io et MongoDB via un liaison Wifi/3G/4G. Visualisation rapide avec MQTT Panel.
proposer et implémenter un algorithme de consensus permettant à plusieurs véhicules de rouler en convoi en maintenant une distance (de sécurité) entre elles. Pour cela, les informations de vitesse et de localisation relevés par les véhicules et les radars de route seront diffusés de façon fiable et en temps réel entre les véhicules roulants sur le circuits ou un segment de route.

=Documents=
[http://air.imag.fr/index.php/Project_2014-2015-CannonBall/developer_guide Developer Guide]

[http://air.imag.fr/index.php/Project_2014-2015-CannonBall/SRS Software Requirements Specifications]

[http://air.imag.fr/index.php/Project_2014-2015-CannonBall/UML UML Diagram]

= Progress of the project =

The project started January 14th, 2015.

== Week 1 (January 13th - January 18th) == 
* Project discovery
* Discovery of OpenCV
* Material recovery

== Week 2 (January 19th - January 25th) ==

'''Work in software engineering''' [http://air.imag.fr/index.php/Project_2014-2015-CannonBall/SRS Software Requirements Specifications]

How to set up the project [http://air.imag.fr/index.php/Project_2014-2015-CannonBall/developer_guide Developer Guide]

=== Technology watch ===

* The idea of using a rasberry pi for images processing was put away because of a lack of cpu power.  Pour se donner un ordre d'idée le core i3 de la tablette Lenovo Thinkpad ....a ajouter des chiffre par rapport à la tablette

* The idea of using a raspberry pi to broadcast the video stream to a local server and processing it by a another machine is not conceivable because of the transmission latency of the stream. To give an order of magnitude if the latency is ~1 second, a car at 30 km/h would carry ~8.3 m before the second machine performs its processing.

* The idea of using a mini and compact tower (example: GB-XM1-3537) is interesting but the absence of in board batteries makes it dependente to a 220 Volts power source.

* The idea of using a phone is interesting because of the richness and accuracy of the sensors (accelerometer, gyroscope, ...). Especially if it has a Tegra type processor, offering greater processing performance. Notice that a simple ARM processor would not do it.
Moreover a phone is small and has onboard battery.
The main concern of our predecessor was that external cameras were not supported on android system. -> We will check on this, because what was true a year ago, might not be today.

=== Technologies chosen ===

* We keep MongoBD database because it offers high write performance and that it is scalable.

* We keep Node.js for creating a local server through which the tablet can display all the data. We use different modules : 
** socket.io for real time messaging between the client and the server
** mqtt for a subscribe/pusblish protocol
** mongoose for manipulating the MongoDB database from JavaScript

* We keep arUco library which we judge to be powerful enough for our requirements. Plus, it is based on opencv library.

=== What we have to accomplish ===

* Finish the prototype in order to be able to present it march 18th, 2015.
** Redirect the metrics and the webcam stream from the car to any computer accessing to the tablet network
** Enhance the algorithms of the car.
** Create a car convoy algorithm.

=== What we want to do ===

* Skip to a Linux environnent with a none proprietary IDE to replace Visual Studio 2013 
* We will stick to C++ language because it is more close of the opencv library which is actually coded in C++ language.

=== What is expected from us to consider ===

* Enhense the moves of the mini car. There are two ways to do so :
** Add a shield (MEMS) to the uno arduino
** Replace the arduino with a STM32 card which is already equipped with embedded sensors. MEMS (microelectromechanical  sensors including accelerometers, gyroscopes, digital compasses, inertial modules, pressure sensors, humidity sensors and microphones).
** An application with an Oculus device

=== The risks ===

* Our ability to take over our predecessors' code, and not going back from scratch
* Misunderstanding et communication problems amongst us and also with 3i team 
* Arriving to an unrealizable situation due to material choice
* Reaching a speed limit due to the tablet ability for image processing

== Week 3 (January 26th - February 01st) ==

''Notice that we have been joined by two colleague, A.Le Jean and H.Rodriguez.''

* New distribution of tasks :  two of us will work on the network part and the two others will work on the optimisation of the opencv use

== Week 4 (February 02nd - February 08th) == 

== Week 5(February 09th - February 15th) ==

== Week 6 (February 16th - February 22th) == 

== Week 7 (February 23rd - march 01st) ==