[Doc] User guide to the duals: every kind, constraint ↔ dual, direct ↔ indirect

オープン
  • 何か問題がありますか？
#1,035 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@ocots がすでに取り組んでいます。

2026年10月31日 から。

評価

この issue はまだ評価されていません。

説明

Part of control-toolbox/CTFlows.jl#512 (tracking of the constraint duals), workstream C.

Goal

A user-side guide to the duals of a solution. It should show users everything they can get, how each dual relates to its constraint, and how the direct and the indirect methods meet. #1015 (the page on the convention) and #1016 (the sign examples) are parts of it. This issue is the guide that puts them together and shows off the feature.

What the guide should show

  1. Every kind of dual, read by its label with dual(sol, ocp, :label): path (pure state, mixed), state box, control box, boundary, and variable box. For each kind: what it is (a function of time or a number), its sign, and how it appears in plot(sol).
  2. The link between a constraint and its dual.
    • An inequality has a nonnegative dual however it is written; an equality or a two-sided constraint has a signed dual (SGN2, SGN3).
    • The dual is 0 where the constraint is inactive and nonzero on a boundary arc.
    • The same constraint as a box or as a path constraint gives the same dual (SGN5).
    • The labels: why naming a constraint matters, and what happens without a name.
  3. The link between the direct and the indirect method.
    • The same problem solved by solve and rebuilt with Flow(ocp, law; constraint=:label, multiplier=μ): the same costate and the same duals, compared on one plot.
    • The dictionary between the μ of the maximum principle and dual.
    • What the indirect side computes by itself (control box, boundary duals by transversality) and what the user gives (μ of a state or mixed constraint).
    • Multi-phase solutions: the jumps of the duals at the switching times (#992).
  4. What a dual tells about the solution: sensitivity, a check of the extremal, and an unknown dual (PreconditionError) rather than a wrong 0.

Depends on

The features of control-toolbox/CTFlows.jl#512, workstreams A and B. Each section can be written as soon as its feature is released. Each example should also be a test (#1034).

Related: #1014, #1015, #1016, #1034, #992, #968.

🤖 Generated with Claude Code

主要言語
Julia
スター
135
フォーク
11
平均マージ
7時間 51分
マージ済み PR（30日）
22

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

control-toolbox/OptimalControl.jl のほかの issue

control-toolbox/OptimalControl.jl の issue をすべて見る

似ている issue

Julia の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。