You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The IRIS-NP2 algorithm (which we're hoping to implement in Drake) examines many configurations to check for collisions, and then uses those samples in collision to run the hyperplane search from IRIS-NP. However, knowing the configuration that's in collision is not enough -- we also need to know which pair of geometries in the world are in collision. If we want to use SceneGraphCollisionChecker (to leverage its speed and parallelism), then it would be extremely helpful if that object could return not just whether or not a configuration is in collision, but also the corresponding SignedDistancePair that was used to determine that there's a collision. Note that this object is constructed as part of checking collisions -- we just need a way to return it to the caller.
The IRIS-NP2 algorithm (which we're hoping to implement in Drake) examines many configurations to check for collisions, and then uses those samples in collision to run the hyperplane search from IRIS-NP. However, knowing the configuration that's in collision is not enough -- we also need to know which pair of geometries in the world are in collision. If we want to use SceneGraphCollisionChecker (to leverage its speed and parallelism), then it would be extremely helpful if that object could return not just whether or not a configuration is in collision, but also the corresponding SignedDistancePair that was used to determine that there's a collision. Note that this object is constructed as part of checking collisions -- we just need a way to return it to the caller.
Related to #18830 and #21822. cc @rhjiang @wernerpe @AlexandreAmice @RussTedrake
The text was updated successfully, but these errors were encountered: