-
Notifications
You must be signed in to change notification settings - Fork 87
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 support for starting values in bridges #684
Comments
Another missing one is square to triangular PSD matrices: #1730 |
This comment was marked as outdated.
This comment was marked as outdated.
function get_unsupported_bridges()
dict = Dict{String,Vector{String}}()
for attr in ("VariablePrimalStart", "ConstraintPrimalStart", "ConstraintDualStart")
ret = String[]
for t in ("Constraint", "Objective", "Variable")
dir = "src/Bridges/$t/bridges"
for file in readdir(dir)
filename = joinpath(dir, file)
contents = read(filename, String)
if occursin("SetMapBridge", contents)
continue
end
if !occursin("::MOI.$attr", contents)
push!(ret, filename)
end
end
end
dict[attr] = ret
end
return dict
end
dict = get_unsupported_bridges() Then with a bit of manual culling, I thing we can get things down to:
|
With the latest PRs (and excluding
|
But actually, the LogDet bridge does support starting values. And the geo-mean and norm bridge are niche enough that there isn't a big drive. They're also slightly complicated to work out the duals for? So maybe this issue can be closed. There's still the unresolved #2117. And since there's a better error message telling people to open an issue if they hit a case that isn't implemented, we can re-open if there is demand. |
@blegat are you ready to close this? |
There are still a few missing |
Sure. But are they useful? We have an error message telling people to open an issue, and no one has 😄 |
I think we're good, these are not the only attributes not implemented by bridges |
Updated list
The text was updated successfully, but these errors were encountered: