You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a) adding lower level variable bounds to model.ctr_lower after the single_blm is built. The existing code could do the rest of the work as model.lower_dual_to_sblm and model.lower_primal_dual_map.primal_con_dual_var already include the bounds.
b) Passing start values for all constrained variables after the single_blm is built.
Approach b) works fine (and I guess hints could be added the same way), for a) I am not sure if this might mess other things up that I didn't notice...
If a) does not cause chaos on other ends, I think it should be preferred?
I could take care of this in a PR.
The text was updated successfully, but these errors were encountered:
Currently, model.ctr_lower does not include variable bound references:
This leads to unexpected behavior when passing starting values to duals of variable bounds, they are not passed in this code sequence:
BilevelJuMP.jl/src/jump.jl
Lines 515 to 524 in 2d25399
Fixing this would be possible by:
a) adding lower level variable bounds to model.ctr_lower after the single_blm is built. The existing code could do the rest of the work as
model.lower_dual_to_sblm
andmodel.lower_primal_dual_map.primal_con_dual_var
already include the bounds.b) Passing start values for all constrained variables after the single_blm is built.
Approach b) works fine (and I guess hints could be added the same way), for a) I am not sure if this might mess other things up that I didn't notice...
If a) does not cause chaos on other ends, I think it should be preferred?
I could take care of this in a PR.
The text was updated successfully, but these errors were encountered: