Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

MosekChordalSDP

MosekChordalSDP uses symbolic elimination to replace one large positive-semidefinite cone with overlapping clique cones, while exposing the same solve and QCQP recovery lifecycle as the monolithic formulation. After solve(), qcqpValues() and variableEVRs() are optional, independent functional queries for recovered vectors and rank-one diagnostics.

QCQP vectors carry no homogenizing coordinate. Each PSD block is instead the lifted matrix [1x⊤xX]\begin{bmatrix}1 & x^\top\\ x & X\end{bmatrix} of the keys it holds, with one constant entry; linear cost and constraint terms act on the lifted vector xix_i (row-0 slice).

Open In Colab

Chordal decomposition

The aggregate sparsity graph of the lifted QCQP is completed according to either ChordalOrderingType.Metis or ChordalOrderingType.Colamd. Symbolic elimination produces a Bayes tree; each clique defines a smaller PSD cone, and separator consistency constraints make the clique matrices agree on overlaps.

METIS is generally the scalable default. COLAMD is useful for deterministic comparisons and small problems. bayesTree() exposes the symbolic decomposition chosen by the solver.

status: ProblemStatus::PrimalAndDualFeasible
objective: 1.2082779221600504e-11
solve time (s): 0.025856971740722656
Bayes-tree cliques: 1
ordered dimensions: {8646911284551352320: 12, 8646911284551352321: 12, 8646911284551352322: 12}
eigenvalue ratios: [21606102095761.6, 4526942104661.99, 2169262047143.9036]
maximum Pose3 error: 3.5850844871612547e-07

Use the monolithic solver as a simple reference and the chordal solver when sparsity makes the clique cones materially smaller than the full lifted matrix. Both recover the same D=1 QCQP representation and therefore use the same typed extraction functions.