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

Runtime Error when using Gurobi and Bound tightening #571

Closed
marcel-v opened this issue Jun 14, 2022 · 5 comments · Fixed by #572 or #575
Closed

Runtime Error when using Gurobi and Bound tightening #571

marcel-v opened this issue Jun 14, 2022 · 5 comments · Fixed by #572 or #575

Comments

@marcel-v
Copy link

Hi,

I observe an runtime error when running Marabou with this query when using --lp-solver gurobi and any bound tightening strategy, i.e., not using --tightening-strategy none.

I can trace the error to a bad access in Tableau::updateVariableToComplyWithUpperBoundUpdate( unsigned int, double ),
specifically, _variableToIndex[variable] (Tableau.cpp:1770),
see the stack.
At access time, _variableToIndex still points to NULL.

Commit is 492c1b8.

Thanks in advance for any feedback!

Best,
Marcel

@wu-haoze
Copy link
Collaborator

Hi @marcel-v , thanks for your interest in the tool and tracking down the error. This does seem to be a issue stemming from this latest commit.
We will fix the bug asap.
For now, could you please revert back to the previous commit 2641ce7? This one should work.

@wu-haoze
Copy link
Collaborator

Hi @marcel-v , please try the latest master. should be fixed.

@marcel-v
Copy link
Author

Hi @marcel-v , please try the latest master. should be fixed.

Great, works!

@marcel-v
Copy link
Author

There appears to be another invalid access to the tableau internals when using Gurobi with this query, resulting in
this stack.

I am at latest commit eb93d44.

@wu-haoze wu-haoze reopened this Jun 17, 2022
@wu-haoze wu-haoze linked a pull request Jun 17, 2022 that will close this issue
@wu-haoze
Copy link
Collaborator

Hi @marcel-v , I apologize for the inconvenience. A new Pr should fix these issues, and all the regression tests now pass with Gurobi on.

wu-haoze added a commit that referenced this issue Jun 17, 2022
* put back guard

* fix bug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants