-
Notifications
You must be signed in to change notification settings - Fork 24
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
Add tests for MIQP #144
Comments
Should I add tests written in C code (or some other format)? |
Can you try reading QP instances from MPS? I see that Coin-OR supports the quadratic objective with |
Just double-check: we do not want to modify |
I was not following this issue (coin-or/Smi#4), but it looks like the functions are already there for quadratic objective. Quadratic constraints are different, although Gurobi suggests some new cards such as Otherwise, we can start with unit test. |
Yes, the function is there. I tested the readQuadraticMps() function in
I think it is not hard to implement it by modifying the code in |
OK. I reopened #58. This might be a less priority to the other tasks you have. Can you test QP functionalities in unit test? |
Sure. I am working on that. |
Added unit test for MIQP Functions: Check the following cases:
B. With stochastic quadratic objectives:
|
@cheesecakeball The test did not pass. Please check that. |
This is because Gurobi is not available in CI (similar to issue #145). By the way, how did you solve issue #145? Through this commit (636e796)? |
If any specific solvers are used, we need to use macro (e.g., I resolved #145 by this line: https://github.com/Argonne-National-Laboratory/DSP/blob/master/.travis.yml#L65 But, this does not work for gurobi because the license is activate on a dedicated machine. |
Thanks for the answer. My unit test lines all depend on Gurobi, because the checking criterion is based on the solution of the sample problem. |
The unit test should be independent of the solver. I will modify it in |
We need to add tests and unit tests for QP implementations.
The text was updated successfully, but these errors were encountered: