Open marrts opened 1 month ago
I think it would probably make the most sense to separate out the adding the mesh process from the motion plan call. This would give us more flexibility in motion planning to either require a mesh or not. It would also potentially enable adding multiple meshes if the scenario ever came up.
Sounds like a reasonable approach to me
I think it would probably make the most sense to separate out the adding the mesh process from the motion plan call. This would give us more flexibility in motion planning to either require a mesh or not. It would also potentially enable adding multiple meshes if the scenario ever came up.
How would you separate out adding the mesh process?
How would you separate out adding the mesh process?
snp_msgs
package.
If you pass a mesh to the motion planner and there is no mesh at that filepath it will print an error, but just continue with the motion plan. This could lead to unexpected behavior and motion plans that are not collision free.