Skip to content

NLPBlock appears to be ignored #97

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.

Sign up for GitHub

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

Jump to bottom
Closed
mlubin opened this issue Oct 16, 2019 · 2 comments
Closed

NLPBlock appears to be ignored #97

mlubin opened this issue Oct 16, 2019 · 2 comments

Comments

@mlubin
Copy link

mlubin commented Oct 16, 2019

An error should be thrown if there's an NLPBlock in the input. See https://discourse.julialang.org/t/jump-not-getting-the-correct-solution-of-the-optimization-problem/29947.
@migarstka
Copy link
Member

migarstka commented Oct 16, 2019 •
edited
Loading

This is mainly caused by the fact that we use our own model copying functions (which up to this point ignore any unknown MOI.attributes) rather than using the MOI allocate-load - interface. I hope I have some time in the next few weeks to switch to that interface.

migarstka added a commit that referenced this issue Nov 18, 2019
@migarstka
<#97> Loop over all MOI-Attributes during copy_to
39d7bc1 
- Instead of writing specific functions for the attributes objective_function,
 VariablePrimalStart, ConstraintPrimalStart, ConstraintDualStart,
 loop over all ModelAttributes, VariableAttributes and ConstraintAttributes,
 call the corresponding `load(attribute)` function (if attribute is supported),
 or throw an error otherwise.

- Rename some of the MOI.set to MOI.load. This is necessary to trigger model-emptying
 in some cases.
- Modify unit tests accordingly.
- Add unit test for an unsupported attribute
- In response to the problem discussed in issue #97
@migarstka
Copy link
Member

Resolved by 39d7bc1

migarstka added a commit that referenced this issue Nov 18, 2019
@migarstka
<#97> Loop over all MOI-Attributes during copy_to
9f1b5ff 
- Instead of writing specific functions for the attributes objective_function,
 VariablePrimalStart, ConstraintPrimalStart, ConstraintDualStart,
 loop over all ModelAttributes, VariableAttributes and ConstraintAttributes,
 call the corresponding `load(attribute)` function (if attribute is supported),
 or throw an error otherwise.

- Rename some of the MOI.set to MOI.load. This is necessary to trigger model-emptying
 in some cases.
- Modify unit tests accordingly.
- Add unit test for an unsupported attribute
- In response to the problem discussed in issue #97
@blegat blegat mentioned this issue Nov 19, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mlubin @migarstka