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

オープン
#286 コメント 1 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@ocots がすでに取り組んでいます。

2026年10月31日 から。

評価

この issue はまだ評価されていません。

説明

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
主要言語
Julia
スター
13
フォーク
1
平均マージ
3時間 24分
マージ済み PR(30日)
34

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

control-toolbox/OptimalControlProblems.jl のほかの issue

control-toolbox/OptimalControlProblems.jl の issue をすべて見る

似ている issue

Julia の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。