Repository navigation
feat(tools): the skeleton of a new problem (T3 of #449) - #468
Merged
Merged
Conversation
…ne (T3 of #449) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
16 of 53 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #449 (T3). Based on #467 (the linter): to merge after it, then the base becomes
main. Conventions: ct-conventions v0.14.0, ct-agents v0.5.0.Summary
The first step of a tool to fill a new problem bit by bit: a skeleton that passes the linter but for its
TODOs, which mark what is left to write.julia --project tools/new/problem.jl new <problem> <modelings...>: the metadata, the description and one model per modeling given (no default: a problem need not exist in every modeling), each:draft, an example problem (ẋ = u, x ≤ x_u, ∫u²) to write over.julia --project tools/new/problem.jl add <problem> <modelings...>: a model file per new modeling of an existing problem, and a:draftstatus for each in its metadata (the other fields do not depend on the modeling; statuses set by hand are kept).tools/new/templates/: one template per modeling ofMODELING_SPECS, the metadata and the description. A test checks there is exactly one per modeling: a new modeling of the package needs its template.TODO)", and the metadata read by evaluating the file (as the package does), so that a problem not yet known to the loaded package, or under another root, can be linted.ext/README.md(step 0, skeleton) andAGENTS.md("Add a problem") point to it.Test plan
test_new: the skeleton in every modeling and in some, thenadd, linted in a temporary directory (only theTODOcheck fails, then no failure once filled); refusals (unknown or repeated modeling, existing problem or modeling, invalid name).TODOs filled:Pkg.testJuMP, OptimalControl, OptimalControlScalarized, ModelingToolkit passed (1310); not committed.core: 1287 passed.🤖 Generated with Claude Code