Comments (7)
Thanks for opening an issue. I'll have a look.
from cosmo.jl.
I hope this fixes it 623a704 I will tag v0.8.5 shortly. Let me know if the issue persists.
from cosmo.jl.
Many thanks, this works but another error pops up:
ERROR: TypeError: in <:, expected Type, got a value of type COSMO.CliqueGraphMerge
Stacktrace:
[1] COSMO.SparsityPattern(L::SparseArrays.SparseMatrixCSC{Float64, Int64}, N::Int64, ordering::Vector{Int64}, merge_strategy::COSMO.OptionsFactory{COSMO.CliqueGraphMerge}, row_range::UnitRange{Int64}, cone_ind::Int64, nz_ind_map::SparseArrays.SparseVector{Int64, Int64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\types.jl:200
[2] _analyse_sparsity_pattern(ci::COSMO.ChordalInfo{Float64}, csp::Vector{Int64}, sets::Vector{COSMO.AbstractConvexSet}, C::COSMO.PsdConeTriangle{Float64}, k::Int64, psd_row_range::UnitRange{Int64}, sp_ind::Int64, merge_strategy::COSMO.OptionsFactory{COSMO.CliqueGraphMerge})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:64
[3] analyse_sparsity_pattern!(ci::COSMO.ChordalInfo{Float64}, csp::Vector{Int64}, sets::Vector{COSMO.AbstractConvexSet}, C::COSMO.PsdConeTriangle{Float64}, k::Int64, psd_row_range::UnitRange{Int64}, sp_ind::Int64, merge_strategy::COSMO.OptionsFactory{COSMO.CliqueGraphMerge})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:55
[4] find_sparsity_patterns!(ws::COSMO.Workspace{Float64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:47
[5] chordal_decomposition!(ws::COSMO.Workspace{Float64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:18
[6] macro expansion
@ .\timing.jl:299 [inlined]
[7] optimize!(ws::COSMO.Workspace{Float64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\solver.jl:90
[8] optimize!
@ C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\MOI_wrapper.jl:151 [inlined]
[9] optimize!
@ C:\Users\Miguel\.julia\packages\MathOptInterface\QxT5e\src\MathOptInterface.jl:81 [inlined]
[10] optimize!(m::MathOptInterface.Utilities.CachingOptimizer{COSMO.Optimizer{Float64}, MathOptInterface.Utilities.UniversalFallback{MathOptInterface.Utilities.Model{Float64}}})
@ MathOptInterface.Utilities C:\Users\Miguel\.julia\packages\MathOptInterface\QxT5e\src\Utilities\cachingoptimizer.jl:285
PS: I am trying to debug this myself by overriding COSMO fundtions. Let me know if you need any variables in my session.
from cosmo.jl.
You can also try using a different merge strategy, e.g. pass in the setting merge_strategy = COSMO.ParentChildMerge
or merge_strategy = COSMO.NoMerge
. see: https://oxfordcontrol.github.io/COSMO.jl/dev/decomposition/
from cosmo.jl.
Thanks @migarstka. Btw, I can confirm that in the OP, my instance indeed has only one clique. Also your fix 623a704 still returns the correct result for a smaller instance. However, on the larger instance, using
COSMOOPTIMIZER = optimizer_with_attributes(
COSMO.Optimizer,
"max_iter" => 100_000,
"verbose" => true,
"verbose_timing" => true,
"eps_abs" => 1e-8,
"merge_strategy" => COSMO.NoMerge,
)
still returns error
ERROR: TypeError: in <:, expected Type, got a value of type COSMO.NoMerge
Stacktrace:
[1] COSMO.SparsityPattern(L::SparseArrays.SparseMatrixCSC{Float64, Int64}, N::Int64, ordering::Vector{Int64}, merge_strategy::Type{COSMO.NoMerge}, row_range::UnitRange{Int64}, cone_ind::Int64, nz_ind_map::SparseArrays.SparseVector{Int64, Int64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\types.jl:200
[2] _analyse_sparsity_pattern(ci::COSMO.ChordalInfo{Float64}, csp::Vector{Int64}, sets::Vector{COSMO.AbstractConvexSet}, C::COSMO.PsdConeTriangle{Float64}, k::Int64, psd_row_range::UnitRange{Int64}, sp_ind::Int64, merge_strategy::Type{COSMO.NoMerge})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:64
[3] analyse_sparsity_pattern!(ci::COSMO.ChordalInfo{Float64}, csp::Vector{Int64}, sets::Vector{COSMO.AbstractConvexSet}, C::COSMO.PsdConeTriangle{Float64}, k::Int64, psd_row_range::UnitRange{Int64}, sp_ind::Int64, merge_strategy::Type{COSMO.NoMerge})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:55
[4] find_sparsity_patterns!(ws::COSMO.Workspace{Float64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:47
[5] chordal_decomposition!(ws::COSMO.Workspace{Float64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\chordal_decomposition.jl:18
[6] macro expansion
@ .\timing.jl:299 [inlined]
[7] optimize!(ws::COSMO.Workspace{Float64})
@ COSMO C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\solver.jl:90
[8] optimize!
@ C:\Users\Miguel\.julia\packages\COSMO\6NlGI\src\MOI_wrapper.jl:151 [inlined]
[9] optimize!
@ C:\Users\Miguel\.julia\packages\MathOptInterface\QxT5e\src\MathOptInterface.jl:81 [inlined]
[10] optimize!(m::MathOptInterface.Utilities.CachingOptimizer{COSMO.Optimizer{Float64}, MathOptInterface.Utilities.UniversalFallback{MathOptInterface.Utilities.Model{Float64}}})
@ MathOptInterface.Utilities C:\Users\Miguel\.julia\packages\MathOptInterface\QxT5e\src\Utilities\cachingoptimizer.jl:285
I'll try switching off the chordal decomposition completely and see what happens. Two questions:
- should I open a separate issue for the type error?
- the branch with_multi_threading is also up to date with v0.8.5 right?
from cosmo.jl.
should I open a separate issue for the type error?
It would be great if you could provide me with some code that I can use to reproduce the error.
the branch with_multi_threading is also up to date with v0.8.5 right?
I try to keep it in sync with the latest version
from cosmo.jl.
from cosmo.jl.
Related Issues (20)
- Custom convex set vs convex cones? HOT 1
- SVM example in documentation throws many warnings in output HOT 3
- Possible bug in KKT equilibration
- Model question HOT 1
- Usage of `SecondOrderCone`: Supply value of t HOT 1
- MKLPardisoKKTSolver not correctly exported in namespace HOT 2
- can't install COSMO & Clarabel.jl together HOT 3
- MKLPardisoKKTSolver have inconsistent behavior vs default KKTSolver HOT 2
- Error 'Unsupported constraints' appears when using MOI to load and solve CBF files HOT 1
- Passing attributes error in JuMP/MOI wrapper HOT 2
- a minor bug HOT 1
- Support for compute_conflict!(model) HOT 1
- COSMO & conflicting hard constraints? HOT 5
- Test failure on 1.9 due to upstream bug HOT 1
- Error in indirect KKT solver: `tol` keyword in IterativeSolvers.jl deprecated HOT 6
- Error in sparsity pattern analysis HOT 7
- Outdated note in the docs about JuMP not supporting arbitrary precision HOT 2
- Arbitrary precision when COSMO is used with JuMP
- Arbitary precision for PSD Cone
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cosmo.jl.