[Paper] Problem metadata: reference objectives and shared initial guess

Aperta
  • Qualcosa non va?
#286 1 commento 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

Enrich the problem metadata so that the benchmark and the paper can rely on it, and so that JuMP and OptimalControl share one source of truth.

Today

metadata(:problem) only holds grid_size and parameters. The JuMP and OptimalControl models each define their own initial guess.

Candidate fields

Field Content Used by
reference_objective best known value, with grid, scheme and source (COPS, BOCOP, Betts, fine computation) success criterion in CTBenchmarks; requested in #179
state / control / variable dimensions dimensions tables in the paper
final time :fixed or :free user guide
constraint types state bounds, control bounds, nonlinear path constraints, boundary conditions user guide
expected structure :smooth, :bang_bang, :singular, state constraint of order k… convergence study
tags :hard (proposed in control-toolbox/CTDirect.jl#580), :gpu_large, :analytic subset selection
initial guess one form usable by JuMP and OptimalControl (constants or functions of time) #151
reference solution (optional) x_star(t), u_star(t) when analytic convergence study

The type of every field is checked at load time (METADATA_TYPES); that check has to be extended.

Questions

  • How to obtain reference objectives: from the literature, or computed on a very fine grid with a high-order scheme and stored with the grid used?
  • Format of a shared initial guess when JuMP needs values at the nodes and OptimalControl takes functions.

Related

#179, #151, control-toolbox/CTDirect.jl#580. Interacts with the problem interface theme.

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.