[Paper] New problems: analytic solutions, large state dimension, roadmap

Aperta
  • Qualcosa non va?
#287 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ocots ci sta già lavorando.

Dal 31/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

paper

Goal

Add the problems the paper needs, beyond the current collection.

Needed by the paper (priority order)

  1. Problems with an analytic solution, for the convergence study. They already exist in the branch order / add-vanderpol-problem of control-toolbox/benchmark-paper (code/PaperProblems.jl): smooth double integrator, minimum-time double integrator (bang-bang), minimum-fuel with one switch, Van der Pol with bounded control. A smooth problem whose solution is not polynomial is missing: the current one has a cubic solution that Gauss–Legendre integrates exactly (errors at 1e-15), so orders 4 and 6 cannot be measured.
  2. Problems with a large state dimension, for the GPU study, with the dimension as a parameter: semi-discretized PDE (heat equation with boundary control), chain of masses and springs, multi-agent systems. Every current problem has a state of dimension 2 to 6.
  3. Problems from the roadmap #257: Swimmer (see CTDirect test/problems/swimmer.jl, swimmer2.jl), MRI, Kepler, then examples from ICLOCS, COPS, PSOPT, MINTOC, Dymos, BOCOP and Betts.
  4. Excluded problems (bioreactor, cart_pendulum, moonlander): understand why they are excluded in make_list_of_problems(), then reinstate or remove them. See also control-toolbox/CTDirect.jl#626 for the moonlander.
  5. Space shuttle with the heating state constraint (control-toolbox/CTBenchmarks.jl#22): the behavior was reported as unexpected; compare with space_shuttle.

For every new problem: OptimalControl model, JuMP model (three schemes), complete metadata, description, test.

Related

#257, #179, control-toolbox/CTBenchmarks.jl#22.

How to work on this theme

This is a theme issue: it describes the work to do and what is known so far, it is not meant to be closed by a single PR.

  1. Whoever takes it first defines the work precisely and splits it into sub-issues (they can live in any repository of the organization).
  2. Work proceeds through the sub-issues; tick the checklist below as they are closed.
  3. Close the theme when everything is done or explicitly dropped.

Context: tracking issue control-toolbox/CTBenchmarks.jl#200; planning notes: objectives and directions and updating OptimalControlProblems and CTBenchmarks (in control-toolbox/benchmark-paper).

Sub-issues
  • to be created when the theme is taken
Lingua principale
Julia
Stelle
13
Fork
1
Merge medio
3h 20m
PR unite (30g)
27

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/OptimalControlProblems.jl

Tutte le issue di control-toolbox/OptimalControlProblems.jl

Issue simili

Altre issue su Julia

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.