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

Pyomo 6.4 can't use scip 8.0.1 #2545

Open
qiniuweihe opened this issue Sep 24, 2022 · 8 comments · Fixed by #2602
Open

Pyomo 6.4 can't use scip 8.0.1 #2545

qiniuweihe opened this issue Sep 24, 2022 · 8 comments · Fixed by #2602
Assignees
Labels

Comments

@qiniuweihe
Copy link

As title, when I use scip to solve my problem, it can't start to solve problem:
image

@qiniuweihe qiniuweihe added the bug label Sep 24, 2022
@mrmundt
Copy link
Contributor

mrmundt commented Sep 27, 2022

What version of pyomo are you using?

@qiniuweihe
Copy link
Author

image

@blnicho
Copy link
Member

blnicho commented Nov 3, 2022

@qiniuweihe is this still an issue for you? If so, please post the solver output by adding the option tee=True to your call to solve.

@whart222
Copy link
Member

I've confirmed that the Pyomo tests with SCIP all pass on the Pyomo 6.4.3 development branch. I don't know that there were any fixes to that branch, though. Hence, we'll need an example of the test failure to replicate this issue.

@qiniuweihe
Copy link
Author

It doesn't display the log:
image

@qiniuweihe
Copy link
Author

qiniuweihe commented Nov 13, 2022

Maybe it is the model problem? But cbc can solve it....
image

@mrmundt mrmundt reopened this Nov 21, 2022
@jsiirola
Copy link
Member

According to the SCIP source, -4 is

SCIP_NOFILE  =  -4,       /**< file not found error */

I am not at all sure why you are getting that error, unless SCIP also raises that for other conditions (like failing to read an NL file). Can you confirm that you are still seeing this error with the current Pyomo and SCIP releases? If so, please pose a minimal example that reproduces the problem. Without that, there is little we can do to resolve this and will need to close this issue.

@mrmundt
Copy link
Contributor

mrmundt commented Jan 4, 2024

@qiniuweihe - Are you still experiencing this error?

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

Successfully merging a pull request may close this issue.

5 participants