1. 30 Jun, 2016 1 commit
  2. 15 Apr, 2016 1 commit
  3. 14 Apr, 2016 1 commit
  4. 08 Apr, 2016 2 commits
  5. 16 Jan, 2016 1 commit
  6. 13 Jan, 2016 3 commits
  7. 15 Jun, 2015 1 commit
  8. 02 Jun, 2015 1 commit
  9. 30 Apr, 2015 2 commits
  10. 27 Apr, 2015 1 commit
  11. 12 Mar, 2015 2 commits
  12. 12 Dec, 2014 3 commits
  13. 10 Dec, 2014 1 commit
  14. 02 Dec, 2014 1 commit
  15. 28 Nov, 2014 1 commit
  16. 01 Apr, 2014 1 commit
  17. 24 Feb, 2014 1 commit
  18. 12 Dec, 2013 1 commit
  19. 26 Nov, 2013 2 commits
  20. 07 Nov, 2013 1 commit
  21. 06 Nov, 2013 4 commits
  22. 23 Sep, 2013 1 commit
  23. 10 Sep, 2013 1 commit
  24. 04 Sep, 2013 1 commit
  25. 26 Jul, 2013 2 commits
  26. 15 Jul, 2013 1 commit
  27. 11 Jul, 2013 1 commit
  28. 08 Jul, 2013 1 commit
    • olivier stasse's avatar
      Handle case where sensors information are not set appropriatly. · 2c6ef8ae
      olivier stasse authored
      Basically does nothing. Probably the system should send some message,
      but for geometrical test of the robot behavior this will generate too much
      unwanted error messages.
      A proper way would assume level of debug messages according to the context.
      Here we keep it simple.
      2c6ef8ae