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

[BUG] Constraint residuals wrong/ dont make sense #3094

Open
timothy-nunn opened this issue Mar 7, 2024 · 0 comments
Open

[BUG] Constraint residuals wrong/ dont make sense #3094

timothy-nunn opened this issue Mar 7, 2024 · 0 comments

Comments

@timothy-nunn
Copy link
Contributor

Describe the bug

Two constraint equations both seem to be satisfied, as indicated by a negative CC (negated to make it positive before being passed to the solver), but the residual of the first is negative and residual of the second is positive (positive residual should mean constraint satisfied?).

I have an output file that shows 12 of the inequality constraints have negative residuals but the CC’s are showing only one of the constraints are violated. We should probably review our constraint equations to ensure the CC’s and residuals make sense and that everything being passed to the solver and output is valid.

Metric Bound Residue (err) CC
bmaxtf (4.62711) bmxlim (14) -9.3722 -2.026
sig_tf_case (84138147) sig_tf_case_max (750000000) 665861853 -7.91

Steps to reproduce

Run the IN.DAT and observe the values in the table above. (The file won't converge but will write out an OUT.DAT)
LT-INSPIRED-QSP-ISSUE.IN.DAT.txt
LT-INSPIRED-QSP-ISSUE.OUT.DAT.txt

Expected behaviour

Positive residual = satisfied? Therefore both should be positive, (or both should be negative)

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

No branches or pull requests

1 participant