move3d » move4d

fixed in move4d on branch fix1184

The LocalPath::isValid method now uses the move4d collision system instead of the p3d one (API::CollisionInterface)

This probably introduce regressions, need to issue a bug tracker on merging this pr.

When trying RRT on ball/human scenario, the path generated for the ball is not in collision with human. Once the path is generated, calling check on it returns True (ok), however when moving the human inside the generated path, check still returns True while it should return False.

That's due to the fact that the pathes stores their last check status,
there is no python interface to reset it yet

On 30/05/2018 10:42, Guilhem Buisan wrote:

Issue #1184 has been updated by Guilhem Buisan.

When trying RRT on ball/human scenario, the path generated for the ball is not in collision with human. Once the path is generated, calling check on it returns True (ok), however when moving the human inside the generated path, check still returns True while it should return False.

----------------------------------------
Bug #1184: LocalPath::isValid break
https://redmine.laas.fr/issues/1184#change-1506

• Author: Jules Waldhart
• Status: New
• Priority: High
• Assignee:
• Category:
• Target version:
  ----------------------------------------
  Somehow the API::LocalPath::isValid method is broken and seems to always return true. This is probably due to bad settings of global variables...

--
Jules Waldhart
Doctorant / Ph.D student
CNRS, LAAS-CNRS, Université de Toulouse
Équipe RIS
Bureau H111
Tel: [+33 5 61 33] 68 76