jump-dev / jump-dev/MathOptInterface.jl
Setting starting values for vector variable bridges
- Lingua principale
- Julia
- Stelle
- 504
- Fork
- 101
- Merge medio
- 6h 26m
- PR unite (30g)
- 22
Descrizione
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.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- julia
- Ambito
- backend
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 38/100