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

Option "qp_iteration_limit" is unknown #1967

Closed
odow opened this issue Oct 11, 2024 · 4 comments
Closed

Option "qp_iteration_limit" is unknown #1967

odow opened this issue Oct 11, 2024 · 4 comments
Assignees
Labels
question Further information is requested

Comments

@odow
Copy link
Collaborator

odow commented Oct 11, 2024

Is there something special about qp_iteration_limit and qp_nullspace_limit?

julia> using HiGHS

julia> h = Highs_create()
Ptr{Nothing} @0x00007f8d4a76da00

julia> typeP = Ref{Cint}(0)
Base.RefValue{Int32}(0)

julia> Highs_getOptionType(h, "qp_iteration_limit", typeP)
ERROR:   getOptionIndex: Option "qp_iteration_limit" is unknown
-1

julia> Highs_getOptionType(h, "qp_nullspace_limit", typeP)
ERROR:   getOptionIndex: Option "qp_nullspace_limit" is unknown
-1

Raised by @sstroemer in jump-dev/HiGHS.jl#231

@jajhall
Copy link
Member

jajhall commented Oct 11, 2024

Strange, I'll look into this today, as there's probably a simple explanation and fix

@jajhall jajhall self-assigned this Oct 11, 2024
@jajhall
Copy link
Member

jajhall commented Oct 12, 2024

Calls to getOptionType are made for all options in TestOptions.cpp so I can't see that there is a bug in HiGHS. My only thought is the version number. I introduced qp_iteration_limit and qp_nullspace_limit on 1 May 2024, so they will have been in releases from v1.7.1 (11 June 2024).

What version of HiGHS are you using, @sstroemer?

@jajhall jajhall added the question Further information is requested label Oct 12, 2024
@sstroemer
Copy link

Thanks - that solved it! (can't close this since it's not mine)

If someone stumbles upon this: Doing update HiGHS_jll in package mode should be enough to fix this.


Just adding some context:

I'm using HiGHS.jl, version v1.9.3 - however when calling HiGHS it showed version 1.7.0 (git hash: 50670fd4c). I've recreated the environment on another computer, which now gives me (with the same HiGHS.jl version) 1.7.2, where it works as you said. Why?

I did update HiGHS.jl some time ago, but it's compat entry currently lists HiGHS_jll = "=1.5.1, =1.5.3, =1.6.0, =1.7.0, =1.7.1, =1.7.2", which left me at the old version of HiGHS_jll.jl. Interestingly enough, it seems like @odow was able to reproduce the bug in jump-dev/HiGHS.jl#231, which I assume can only happen for a similar env with an old HiGHS_jll.jl - maybe that pitfall might be worth a note somewhere on the JuMP or MOI side of things (assuming there is the actual need to keep the old versions in the compat)?

@odow
Copy link
Collaborator Author

odow commented Oct 12, 2024

Oops. I didn't check the version. I just assumed it was the most recent. Sorry for the noise.

@odow odow closed this as completed Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants