jump-dev / jump-dev/MathOptInterface.jl
Setting starting values for vector variable bridges
- Vorherrschende Sprache
- Julia
- Sterne
- 504
- Forks
- 101
- Ø Merge
- 6 Std. 26 Min.
- Gemergte PRs (30 T.)
- 22
Beschreibung
This is working for `FlipSignBridge` since it just multiply by `-1` but for a linear map that is not diagonal, we cannot set the starting values variable by variable.
https://github.com/jump-dev/MathOptInterface.jl/blob/5025b50de1d6cb29e6bbb0d26adfcf1b57b6a51c/src/Bridges/Variable/set_map.jl#L182-L192
We would need to cache the vector of starting values in the bridge and then do the linear map in `final_touch`.
Alternatively, this caching could be done by `BridgeOptimizer` to simplify the job of each bridge but that caching isn't needed for `FlipSignBridge` so it could be a waste.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start with src/Bridges/Variable/set_map.jl around lines 182-192 and read how FlipSignBridge handles starting values. Trace the bridge lifecycle through final_touch, then compare whether caching belongs in the bridge or BridgeOptimizer. Done means non-diagonal linear maps can set vector starting values consistently.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- julia
- Bereich
- backend
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 38/100