Skip to content
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

[trajoptlib] Make constraints use current and next index #830

Conversation

calcmogul
Copy link
Member

Fixes #811.

@calcmogul calcmogul force-pushed the trajoptlib-make-constraints-use-current-and-next-index branch 2 times, most recently from ef2f7ed to 7289928 Compare October 3, 2024 23:08
@calcmogul calcmogul force-pushed the trajoptlib-make-constraints-use-current-and-next-index branch from 7289928 to c45ac87 Compare October 4, 2024 01:44
@spacey-sooty
Copy link
Collaborator

This introduces a regression in differential generation. The straight line path passes on main.
choreo-diagnostics-kj9Stldq.zip

@calcmogul
Copy link
Member Author

calcmogul commented Oct 4, 2024

I get "locally infeasible" for that project's straight line path on both main and this PR. Here's the solver output on main:

iter   time (ms)      error          cost       infeasibility
=============================================================
  40       0.263   1.575792e+01   7.871685e+01   1.022015e-01
The problem is infeasible due to violated inequality constraints.
Violated constraints (cᵢ(x) ≥ 0) in order of declaration:
  8/297: -1.616065222258007e-06 ≥ 0
  13/297: -2.663494520752877e-06 ≥ 0
  23/297: -2.241180900109177e-08 ≥ 0
  38/297: -6.995848632047105e-06 ≥ 0
  48/297: -1.5678674351732313e-06 ≥ 0

@spacey-sooty
Copy link
Collaborator

I get "locally infeasible" for that project's straight line path on both main and this PR. Here's the solver output on main:

iter   time (ms)      error          cost       infeasibility
=============================================================
  40       0.263   1.575792e+01   7.871685e+01   1.022015e-01
The problem is infeasible due to violated inequality constraints.
Violated constraints (cᵢ(x) ≥ 0) in order of declaration:
  8/297: -1.616065222258007e-06 ≥ 0
  13/297: -2.663494520752877e-06 ≥ 0
  23/297: -2.241180900109177e-08 ≥ 0
  38/297: -6.995848632047105e-06 ≥ 0
  48/297: -1.5678674351732313e-06 ≥ 0

Ah yep nvm it was passing on beta 2 we've introduced a regression somewhere betweeen there and here. Interesting because I thought I tested differential stuff for #821 and a similar path was passing

Copy link
Collaborator

@spacey-sooty spacey-sooty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and seems fine

@calcmogul
Copy link
Member Author

Beta 2 also works for me, and the commit right after beta 2 has feasibility restoration converge to a locally infeasible point.

commit 3c0603a8037815a4924e1dc0f7f6697266a8a4ae
Author: bruingineer <[email protected]>
Date:   Wed Oct 2 20:40:06 2024 -0700

    [trajoptlib] Make GetIndex() usage consistent and fix GetIndex() (#820)

@shueja shueja enabled auto-merge (squash) October 4, 2024 04:12
@shueja shueja merged commit 5050542 into SleipnirGroup:main Oct 4, 2024
32 checks passed
@calcmogul calcmogul deleted the trajoptlib-make-constraints-use-current-and-next-index branch October 4, 2024 04:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make TrajoptLib kinematics use current and next variables instead of previous and current
3 participants