Lea Kapelevich
Lea Kapelevich
+1, I've wanted to do this many times
How would testing "glued packages" look? Could there be something similar for a `test/Project.toml` and files like `test/glue/A.jl` etc.?
I was getting the same error (slightly different error trace now) with a single equality constraint, e.g.: ``` model = SOSModel(with_optimizer(Mosek.Optimizer)) @variable(model, gamma) @constraint(model, y - gamma >= 0, domain...
Dropping a test in case it helps save a little bit of time: ```cpp TEST_CASE("MIP-get-saved-solutions-presolve", "[highs_test_mip_solver]") { const std::string solution_file = "MipImproving.sol"; Highs highs; highs.setOptionValue("output_flag", dev_run); highs.setOptionValue("mip_improving_solution_save", true); highs.setOptionValue("mip_improving_solution_report_sparse", true);...
I'm not sure. I have't seen any references online. I also emailed to ask but haven't heard back :-).
The manual for Pardiso 7.2 is now online https://pardiso-project.org/manual/manual.pdf though I haven't looked through it
I would like to use matrix logarithms and running into this as well
Hi @galabovaa. That works, no issues. I still think it's strange that the shared library and executable get a .pdb with the same name. FWIW, I just found this flag...
I think adding `PDB_NAME` would resolve this fully. An analogous issue/fix in another repo: https://github.com/eclipse/mosquitto/issues/2714
That's great. Is there a reason not to add the flag for FAST_BUILD ON, so that it can stay when FAST_BUILD OFF disappears?