Calling robotplanning.planToCartesianObjective with valid parameters and plan options fails because the second argument of MotionPlan's constructor should not be q0, but type for the type of solver to use. This specific line is the culprit.
planToConfig implements it correctly by not passing q0 as an argument to the constructor. See this line.
The fix: remove q0 from the constructor call, as it is not used. The endpoints are set latter in the function implementation.
This affects the devel branch too. I'll try and make a pull request.
Calling
robotplanning.planToCartesianObjective
with valid parameters and plan options fails because the second argument of MotionPlan's constructor should not beq0
, buttype
for the type of solver to use. This specific line is the culprit.planToConfig
implements it correctly by not passingq0
as an argument to the constructor. See this line.The fix: remove
q0
from the constructor call, as it is not used. The endpoints are set latter in the function implementation.This affects the devel branch too. I'll try and make a pull request.