Documentation: sign conventions (min/max, p⁰, constraints, duals) and how they appear in a solution

Aperta
  • Qualcosa non va?
#1,015 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ocots ci sta già lavorando.

Dal 21/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

documentation

Summary

Add a page to the documentation that explains the sign conventions of the ecosystem and how they show up in a solution, once they are settled in the discussion control-toolbox/OptimalControl.jl#1014. This issue is the place for that page; it should not be written before the choices are made.

Related: control-toolbox/OptimalControl.jl#968 (documentation items waiting on other packages), control-toolbox/CTDirect.jl#639, control-toolbox/CTFlows.jl#472.

What the page should explain

  • min vs max: the value of p⁰, the Hamiltonian (with and without constraints), and whether p and the duals change sign when min J becomes max −J.
  • Inequality constraints: g ≥ 0 or c ≤ 0, the sign of the multiplier on each side, two-sided constraints, equalities.
  • What dual(sol, ocp, :label) returns for each kind of constraint (path, box, boundary, variable box): sign, scaling (continuous-time density or raw NLP value), and its meaning at the first and last nodes.
  • The same constraint solved directly (solve) and by an indirect method (Flow(ocp, law; constraint=:label, multiplier=μ)): how to read the duals on both sides, and the dictionary between μ and dual.
  • Transversality and boundary constraints: the sign of β and of the dual of a boundary constraint.
  • Which of these do not depend on the NLP solver (Ipopt, MadNLP).

Elements already available

  • Probes of 2026-10-21 (closed-form problems; table in the discussion).
  • The KKT derivation per scheme and the measurements in control-toolbox/CTDirect.jl#639.
  • The existing section Formulation → Notation and conventions, to complete or to point to.
  • A runnable probe such as solution_duals.jl (see #968), extended with an indirect solve, so the page is checked by the documentation build.

Depends on

  • Decision on the conventions: control-toolbox/OptimalControl.jl#1014
  • CTDirect alignment: control-toolbox/CTDirect.jl#639
  • Duals of Flow(ocp, law): control-toolbox/CTFlows.jl#472
Lingua principale
Julia
Stelle
135
Fork
11
Merge medio
7h 51m
PR unite (30g)
22

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di control-toolbox/OptimalControl.jl

Tutte le issue di control-toolbox/OptimalControl.jl

Issue simili

Altre issue su Julia

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.