-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Effort limits for KinematicTrajectoryOptimization #22500
Comments
This would be awesome and would definitely cover 90% of my usage needs! Thank you for considering it! If possible, it would be nice to add custom bounding box constraints (or costs) to the effort beyond what is written in the MultibodyPlant. For instance, I'm imagining using the default effort limits at all of the control points to constrain the overall trajectory, but then adding tighter constraints (or a cost) at a few key normalized times to ensure that the trajectory hits a "balanced banking angle" where centrifugal and gravitational forces are balanced. |
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
While this is technically possible now, it certainly isn't easy.
In order to be parallel with
AddPositionBounds
,AddVelocityBounds
, etc, and to leverage the fact that we can create oneshared_pointer
constraint for all of the times, my proposal would be to add the following method toKinematicTrajectoryOptimization
:cc @cohnt, @hongkai-dai ... in case you have any suggestions.
The text was updated successfully, but these errors were encountered: