The same car can have a very different score on two successive evaluations :

1. round 1 score is 63 : {"car":{"chassis":{"vecteurs":[1.0524477,0,0.48183152,0.56480825,0,0.3274586,-0.3776758,0.5775818,-0.55395633,0,-0.8949374,-0.12054062,0,-0.8672349,0.46732175,-0.28825176],"densite":79.377144},"wheel1":{"radius":0.44368792,"density":64.14404,"vertex":2},"wheel2":{"radius":0.40008456,"density":95.26903,"vertex":5}},"score":63}

2. round 2 score is 42 : {"car":{"chassis":{"vecteurs":[1.0524477,0,0.48183152,0.56480825,0,0.3274586,-0.3776758,0.5775818,-0.55395633,0,-0.8949374,-0.12054062,0,-0.8672349,0.46732175,-0.28825176],"densite":79.377144},"wheel1":{"radius":0.44368792,"density":64.14404,"vertex":2},"wheel2":{"radius":0.40008456,"density":95.26903,"vertex":5}},"score":42}

I know the terrain used for evaluation can impact the score but is that amount of difference expected ?

Faire fonctionner sous Python 3

The JavaScript starter should have the same data types as other starters (car and car view) to ease crossover step.

Suite au refactoring de l'objet Car (renommage de la propriété chassi en chassis), le mur des champions n'affiche plus les voitures soumises par les candidats (erreur JS dans la console).

L'asynchronisme est gênant lors de l'appel REST.

3 pistes:

• http://caolan.github.io/async/docs.html#waterfall
• http://www.supinfo.com/articles/single/724-gerez-mieux-votre-code-asynchrone-avec-asyncjs
• https://github.com/ForbesLindesay/sync-request

Suite au refactoring de l'objet Car (renommage de la propriété chassi en chassis), le mur des champions n'affiche plus les voitures soumises par les candidats (erreur JS dans la console).