Closed arntanguy closed 10 months ago
Sorry I mistakenly thought r1ActiveJoints
was the currently supported option.
I chose the following:
r1Joints/r2Joints
in favor of the clearer r1ActiveJoints/r2ActiveJoints
. There is a warning if r1Joints
is used and contains an empty vector (breaking change as it has the opposite meaning as the current option)r1InactiveJoints/r2InactiveJoints
r1JointsInactive == true
we should save the inactive joints as the r1InactiveJoints
vector and not save the boolean value ;)I think this should cover all cases this time ;)
This PR adds the ability to select unactive joints in a collision constraint. Without this we do not have the ability to disable all joints of a robot in a collision constraint, and more often than not it's more natural to specify which joints we want to disable.
This:
r1Joints/r2Joints
tor1ActiveJoints/r2ActiveJoints
and deprecates use of the formerr1UnactiveJoints/r2UnactiveJoints
activeJoints
andunactiveJoints
are present,activeJoints
takes precedence:r1ActiveJoints: []
andr2ActiveJoints: []
-> all joints activer1ActiveJoints: [J1, J2]
andr2ActiveJoints: anything
-> J1 and J2 activer1ActiveJoitns: []
andr2ActiveJoints: [J1, J2]
-> J1 and J2 unactiveSlightly annoying, with this way of describing it we do not have a direct way of disabling all joints short of listing them all in YAML.