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

In ci_bound_wn_i, if an equality constraint is imposed by == and appears before the user-defined variable(s), error will occur #69

Open
sfcheung opened this issue May 8, 2021 · 0 comments
Labels
bug Something isn't working low priority

Comments

@sfcheung
Copy link
Owner

sfcheung commented May 8, 2021

This problem occurs if the target variable is the user-defined variable.

This can be solved by placing the == equality constraint after the user-defined variable(s). However, the function should be able to handle this internally.

This issue is not of top priority because it can be solved by adding the == constraints to the end for now.

@sfcheung sfcheung added bug Something isn't working top priority labels May 8, 2021
@sfcheung sfcheung changed the title In ci_bound_wn_i, if an equality constraint is imposed by == and appears before the user-defined variable(s), error will occur In ci_bound_wn_i, if an equality constraint is imposed by == and appears before the user-defined variable(s), error will occur May 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working low priority
Projects
None yet
Development

No branches or pull requests

1 participant