jump-dev / jump-dev/MathOptInterface.jl
Dimension of SOS sets
- 主要语言
- Julia
- 星标
- 504
- 派生
- 101
- 平均合并
- 6 小时 26 分钟
- 30 天内合并 PR
- 22
描述
Should we forbid dimension=0 for SOS sets? What does this even mean?
You could argue that throwing an error on `MOI.SOS1(Float64[])` is a breaking change, but I don't really set a good reason why anyone would ever want to do it. There's also an argument for making `dimension > 1` for SOS1, and `dimension > 2` for SOS2...
```Julia
julia> using JuMP
julia> model = Model();
julia> @constraint(model, VariableRef[] in SOS1())
[] ∈ MathOptInterface.SOS1{Float64}(Float64[])
```
Discuss...
贡献指南
这个仓库没有索引到贡献指南
调研方向
Start with the MOI.SOS1(Float64[]) example and the SOS1/SOS2 dimension questions in the issue. Trace how these sets are represented and constructed, then clarify the intended validity rules and add coverage showing the resulting behavior.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- julia
- 领域
- api
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 活跃
- 描述清晰度
- 需要澄清
- 新手友好度
- 30/100