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

Constraint Conflict Resolution or .gms file #11

Open
avinashresearch1 opened this issue Oct 20, 2021 · 1 comment
Open

Constraint Conflict Resolution or .gms file #11

avinashresearch1 opened this issue Oct 20, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@avinashresearch1
Copy link

It currently appears as if conflict resolution of constraints (e.g., using compute_conflict! is not supported even though the connected GAMS solver (like BARON) supports it. Is it possible to set up such an option or alternatively print out a .gms file such that we can do it manually?

@renkekuhlmann renkekuhlmann added the enhancement New feature or request label Oct 21, 2021
@renkekuhlmann
Copy link
Member

That's a good idea. We will look into this. However, I can't promise any short term solution for supporting compute_conflict!. Note that the GAMS Optimizer will always write the file moi.gms in the working directory, which is the GAMS equivalent of your JuMP model. You can use this file to perform the conflict analysis. Unfortunately, the variable and equation names have generic names (numbering ordered by addition time), so it may be difficult for you to map the variables / equations back again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants