1. 13 Jan, 2016 3 commits
  2. 15 Jun, 2015 1 commit
  3. 02 Jun, 2015 1 commit
  4. 30 Apr, 2015 2 commits
  5. 27 Apr, 2015 1 commit
  6. 12 Mar, 2015 2 commits
  7. 12 Dec, 2014 3 commits
  8. 10 Dec, 2014 1 commit
  9. 02 Dec, 2014 1 commit
  10. 28 Nov, 2014 1 commit
  11. 01 Apr, 2014 1 commit
  12. 24 Feb, 2014 1 commit
  13. 12 Dec, 2013 1 commit
  14. 26 Nov, 2013 2 commits
  15. 07 Nov, 2013 1 commit
  16. 06 Nov, 2013 4 commits
  17. 23 Sep, 2013 1 commit
  18. 10 Sep, 2013 1 commit
  19. 04 Sep, 2013 1 commit
  20. 26 Jul, 2013 2 commits
  21. 15 Jul, 2013 1 commit
  22. 11 Jul, 2013 1 commit
  23. 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
  24. 21 Jun, 2013 1 commit
  25. 19 Jun, 2013 1 commit
  26. 28 May, 2013 1 commit
  27. 22 May, 2013 2 commits
  28. 21 May, 2013 1 commit