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

Offen
  • Stimmt etwas nicht?
#287 0 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@ocots arbeitet bereits daran.

Seit 31.10.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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
Vorherrschende Sprache
Julia
Sterne
13
Forks
1
Ø Merge
3 Std. 24 Min.
Gemergte PRs (30 T.)
34

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus control-toolbox/OptimalControlProblems.jl

Alle Issues in control-toolbox/OptimalControlProblems.jl

Ähnliche Issues

Weitere Issues zu Julia

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.