You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Metadata] Compute the features of a problem from its model #376
Agents: read the guide for agents in #310 first. Specification: this description, #306 and its comments.
Sub-issue of #306, part 2 of 5. Independent; the documentation switch waits for #311.
Scope
features(:p): dimensions, cost kind (Mayer, Lagrange, Bolza), fixed or free initial and final times, kinds and counts of constraints, computed from the ocp (OptimalControl modelings) or from the keys of the JuMP model for a problem available in JuMP only. Never written by hand. Replaces collect_problem_data of docs/browser.jl once #311 is merged; CTBenchmarks can read it.
Done when
features(:p) for every problem, tested against the model.
OptimalControlProblems.features(problem) and features(pb): dimensions, cost kind, fixed or free times, number of constraints of each kind, computed from the OptimalControl model with the CTModels functions; ExtensionError without OptimalControl.
New model equivalence check without a solve, in comparison: the scalarized and vector models have the same features (19 problems), shown failing on a broken model.
Activity
ocots commentedon Nov 6, 2026
Taken by an agent; draft PR to follow.
Merge pull request #392 from control-toolbox/feat/376-features
ocots commentedon Nov 6, 2026
Done in #392 (merged).
OptimalControlProblems.features(problem)andfeatures(pb): dimensions, cost kind, fixed or free times, number of constraints of each kind, computed from the OptimalControl model with the CTModels functions;ExtensionErrorwithout OptimalControl.comparison: the scalarized and vector models have the same features (19 problems), shown failing on a broken model.docs/browser.jlreads it; documentation build green.🤖 Generated with Claude Code