-
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
BsplineTrajectory::AsLinearInControlPoints() #22533
Labels
component: planning and control
Optimization-based planning and control, and search- and sampling-based planning
priority: low
type: feature request
Comments
RussTedrake
added
component: planning and control
Optimization-based planning and control, and search- and sampling-based planning
priority: low
type: feature request
labels
Jan 26, 2025
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 26, 2025
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 27, 2025
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 27, 2025
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 27, 2025
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 27, 2025
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 28, 2025
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 28, 2025
For BsplineBasis and BsplineTrajectory. Towards RobotLocomotion#22533 which is towards RobotLocomotion#22500.
RussTedrake
added a commit
that referenced
this issue
Jan 28, 2025
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 29, 2025
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 29, 2025
Resolves RobotLocomotion#22533. This includes a breaking change. The vector<vector<Binding>> return types for KinematicTrajectoryOptimization AddAccelerationBounds and AddJerkBounds are now vector<Bindings>.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Jan 31, 2025
Resolves RobotLocomotion#22533. This includes a breaking change. The vector<vector<Binding>> return types for KinematicTrajectoryOptimization AddAccelerationBounds and AddJerkBounds are now vector<Bindings>.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Feb 1, 2025
Resolves RobotLocomotion#22533. This includes a breaking change. The vector<vector<Binding>> return types for KinematicTrajectoryOptimization AddAccelerationBounds and AddJerkBounds are now vector<Bindings>.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Feb 4, 2025
Resolves RobotLocomotion#22533. This includes a breaking change. The vector<vector<Binding>> return types for KinematicTrajectoryOptimization AddAccelerationBounds and AddJerkBounds are now vector<Bindings>.
RussTedrake
added a commit
to RussTedrake/drake
that referenced
this issue
Feb 4, 2025
Resolves RobotLocomotion#22533. This includes a breaking change. The vector<vector<Binding>> return types for KinematicTrajectoryOptimization AddAccelerationBounds and AddJerkBounds are now vector<Bindings>.
xuchenhan-tri
pushed a commit
that referenced
this issue
Feb 4, 2025
Resolves #22533. This includes a breaking change. The vector<vector<Binding>> return types for KinematicTrajectoryOptimization AddAccelerationBounds and AddJerkBounds are now vector<Bindings>.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component: planning and control
Optimization-based planning and control, and search- and sampling-based planning
priority: low
type: feature request
KinematicTrajectoryOptimization
(and other codes) make use ofBsplineTrajectory
, but have continued to use symbolic computations to reason about the linearity of the derivatives. Admittedly, that linearity is a tangled, convoluted mess. But we should eventually implement it correctly.We already have
BezierCurve::AsLinearInControlPoints()
, and we should have the same (or whatever it's natural equivalent is) forBsplineTrajectory
.The victory condition for this also includes removing all of symbolic variable bspline computations we have accumulated.
Related to #22500, which would add even more of this symbolic computation if we don't resolve this.
The text was updated successfully, but these errors were encountered: