Conditional Value At Risk
Definition
Conditional Value-at-Risk (CVaR) of a random cost at confidence level is the
expected loss in the worst -tail of the cost distribution — the mean of conditioned
on exceeding its -quantile (the Value-at-Risk, VaR). It quantifies “how bad is bad”,
interpolating between the risk-neutral expectation () and the worst-case essential
supremum (). Unlike VaR (a quantile, hence a chance constraint), CVaR is a coherent risk
measure — monotone, translation-invariant, positively homogeneous and sub-additive/convex
(coherent_risk_measures) — which makes the constraint
both convex and a conservative tightening of the chance constraint
. CVaR is distribution-agnostic and independent of the free-flying /
free-floating regime; in all cited sources it is layered on top of the planning/control problem rather
than on the manipulator dynamics.
Key Equations
Symbols per notation.md.
The canonical Rockafellar–Uryasev optimization form (used directly by dixit2023risk),
with :
whose minimizer , the -quantile. Equivalently, as the tail-average
of VaR (majumdar2017how, eq. for ):
Convention flag. is the CVaR confidence level in notation.md (line: “CVaR confidence
level (risk layer)”), so the risk tail has mass and the page writes , matching
dixit2023risk — i.e. the subscript is the tail mass ( = worst case).
majumdar2017how keeps the same confidence-level meaning for but indexes the
subscript by the confidence level itself, writing for the average of the upper -tail
(so again = worst case); the tail-average formula below is quoted in that indexing.
ren2022chance uses for the tail probability (subscript = tail mass, like dixit).
Same metric, different subscript-indexing — read the subscript convention before reusing a formula.
Source Support
- majumdar2017how — derives CVaR from an axiomatic (“coherent / distortion”) theory of
risk for robotics; CVaR satisfies all six axioms (A1–A6) whereas VaR fails sub-additivity (A4). Primary for the
definition and the coherence argument. - dixit2023risk — gives the Rockafellar–Uryasev optimization form and its discrete/dual
(risk-envelope) representation; embeds CVaR as the obstacle-avoidance constraint in risk-averse MPC and contrasts it
with EVaR and total-variation-distance metrics. - ren2022chance — uses CVaR as a conservative approximation of a chance constraint
under a Gaussian-mixture uncertainty model: ,
with a closed-form second-order-cone reformulation; bounds the amount of violation, not just its probability. - akella2024risk — situates CVaR within the worst-case / risk-neutral / risk-aware
taxonomy of safety assessment; supporting context.
Related Topics
- coherent_risk_measures — CVaR is the canonical coherent (indeed distortion / spectral)
risk measure; every distortion metric is a weighted integral of CVaR over confidence levels. - chance_constraints — CVaR is the convex, sub-additive surrogate for a chance constraint;
implies and additionally caps the expected overshoot. - risk_aware_mpc — CVaR (or a general coherent measure) is the risk functional optimized/constrained
in the receding-horizon problems of dixit2023risk and ren2022chance. - motion_planning_under_uncertainty — CVaR is the risk metric these planners
impose on collision / constraint-violation cost to obtain safe, dynamically feasible trajectories. - control_barrier_functions — CVaR has been combined with CBFs (dixit2023risk cites
CVaR-CBF formulations) to enforce risk-bounded forward invariance of a safe set.
Open Questions
- All four sources apply CVaR to terrestrial/automotive systems (autonomous driving, bipeds, ground robots) with
linear or linearized discrete-time dynamics; none treats a free-flying space manipulator. Does the convexity that makes
tractable survive when is a collision/pointing cost coupled through the nonlinear
circumcentroidal dynamics (ffsm_dynamics)? - The natural risk variable for our inspection problem (versine pointing error, or singularity proximity )
is not a financial loss — what is the right cost , and at what confidence level , for a CVaR constraint on
proximity to a dynamic_singularity? - majumdar2017how flags that CVaR (single-level, single-stage) can violate time consistency in multi-stage planning;
does our receding-horizon inspection guidance need the nested/Markov-coherent form instead?