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

Ouverte
  • Quelque chose ne va pas ?
#287 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@ocots y travaille déjà.

Depuis le 31/10/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

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
Langage dominant
Julia
Étoiles
13
Forks
1
Merge moyen
3 h 9 min
PR mergées (30 j)
47

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de control-toolbox/OptimalControlProblems.jl

Toutes les issues de control-toolbox/OptimalControlProblems.jl

Issues similaires

Plus d'issues Julia

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.