Skip to content

feat(models): ModelingToolkit convergence cron, trajectories, and documentation (#439) - #444

Merged
ocots merged 13 commits into
mainfrom
feat/439-mtk-cron-docs
Nov 11, 2026
Merged

ocots merged 13 commits into
mainfrom
feat/439-mtk-cron-docs

Conversation

@ocots

@ocots ocots commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

Warning

This description is obsolete. It was written before the critical review and the fixes that followed (merge of main, tests aligned with #446, model equivalence test, shared tests, CI scope fix). The current state, the list of changes and the verification are in this comment. The original description is kept below as a trace; several of its points no longer hold (for instance the documentation snippet, docs/Project.toml, the reference_objective(..., scheme=:trapeze) comparison of the cron, and the verification numbers).


Original description (obsolete)

Closes #439.
Part 3 of 3 of #308. Supports #314.

Applied conventions: ct-conventions v0.11.0, ct-agents v0.4.0.

Summary of Changes

  1. Trajectory Reconstruction (#314):

    • Implemented SolveModelingToolkit.dynamic_trajectory and SolveModelingToolkit.trajectory in test/common/solve_modelingtoolkit.jl to reconstruct state and control trajectories from Corleone solutions.
    • Costates are set to an empty dict (Dict{String, Vector{Float64}}()) because Corleone is a direct shooting solver without explicit costate dynamics.
    • Controls are piecewise-constant on intervals and extended to $N$ grid points to match the time grid in plots.
    • Added unit tests in test/suite/ModelingToolkit/test_methods.jl.
  2. Convergence Cron & CI Schedule:

    • Created test/cron/ModelingToolkit/test_convergence.jl looping over Main.TestStatus.for_each_problem with ModelingToolkitBackend().
    • Compares Corleone solve objectives against analytic_reference(problem).objective and reference_objective(problem; grid_size=N, scheme=:trapeze).
    • Enabled weekly schedule (0 4 * * 6) in .github/workflows/CronModelingToolkit.yml and updated cadence in tools/cron/report.py.
  3. Documentation Adapter & References:

    • Updated docs/modelings.jl with note explaining that Corleone enforces state path constraints on constraint grid points with piecewise-constant controls, along with a complete solve snippet.
    • Added ModelingToolkit to docs/Project.toml, docs/make.jl, and docs/api_reference.jl.
    • Fixed pre-existing Documenter cross-references to OptimalControlProblems.Problems.Problem.
  4. Developer Guides:

    • Documented ModelingToolkitModels in ext/README.md.
    • Documented the ModelingToolkit test suite and cron in test/README.md.

Verification

  • Pkg.test(test_args=["ModelingToolkit", "*methods*"]): 34 passed.
  • Pkg.test(test_args=["ModelingToolkit", "cron"]): report and trajectories generated successfully.
  • Pkg.test(test_args=["core"]): 1306 passed, 0 failed.
  • python3 -m unittest discover -s tools/ci/test -p 'test_*.py': 47 passed.
  • julia --project=docs docs/make.jl: documentation built cleanly with Vitepress.

🤖 Generated with Claude Code

ocots added 4 commits November 9, 2026 21:54
Add dynamic_trajectory and trajectory functions in SolveModelingToolkit
to reconstruct state and control trajectories from Corleone solutions for
the documentation results pipeline (#314). Add unit tests in test_methods.jl.
…439)

Add test/cron/ModelingToolkit/test_convergence.jl to record convergence
and trajectories for ModelingToolkit problems against analytic and
discretized references. Enable the Saturday cron schedule in
CronModelingToolkit.yml and update cron report scope description.
Add ModelingToolkit to docs Project.toml, make.jl, api_reference.jl, and
update the ModelingToolkit adapter in modelings.jl with Corleone direct
shooting explanation and snippet. Fix Documenter cross-references to
OptimalControlProblems.Problems.Problem.
)

Document ModelingToolkitModels extension in ext/README.md and the
ModelingToolkit fast test suite and convergence cron in test/README.md.
@ocots ocots added run ci github-runner Trigger the CI workflow on GitHub-hosted runners test ModelingToolkit backend Package-specific scope or cron label run documentation Trigger the Documentation workflow on this PR labels Nov 10, 2026
@ocots

ocots commented Nov 10, 2026

Copy link
Copy Markdown
Member Author

Critical review (agent self-review)

Applied: ct-conventions v0.11.0, ct-agents v0.4.0. CI (core + ModelingToolkit) and the Documentation build pass, but several points should be fixed before this leaves draft.

Blocking

  1. Local path leaked in the committed docs Manifest. docs/src/assets/Manifest.toml now contains
    path = "/Users/ocots/Research/logiciels/dev/control-toolbox/OptimalControlProblems-439" for OptimalControlProblems. The file is copied by docs/make.jl from the local docs environment and is tracked (!docs/src/assets/Manifest.toml in .gitignore); on main it has no OptimalControlProblems entry. It is also published as a download for reproducibility, so it must not point to a developer machine. Likewise, OptimalControlProblems was added to [deps] of docs/Project.toml (and its asset copy) as a side effect of Pkg.develop during the local build: the CI already develops the package, so this entry is churn. → Revert both asset files and the OptimalControlProblems line; keep only ModelingToolkit (+ compat) in docs/Project.toml.

  2. The documentation snippet is wrong and does not match what the cron runs. In docs/modelings.jl:

    • the time span is hardcoded to (0.0, 1.0): correct for bryson_denham only, wrong for any future problem with another horizon;
    • the comment says the path constraints are discretized on the constraint grid, but the snippet passes sys directly to CorleoneDynamicOptProblem — the discretization (_discretize_path_constraints) lives in the test helpers only, so a user copying the snippet solves a different problem (the state constraint of bryson_denham is not handled the same way);
    • inits = [u => initial_guess(pb).control ...] is never executed anywhere (the pipeline uses 0.0) and it is unclear that initial_guess(pb) of a ModelingToolkit Problem has a .control usable as a scalar value.

    The snippet is rendered but not run, so nothing catches this. → Either make the snippet minimal and honest (retrieve the System, point to Corleone), or expose the preparation (tspan + path-constraint discretization) as code that the snippet and SolveModelingToolkit.prepare share, and run it in the docs build.

Should fix

  1. Duplicated problem construction. dynamic_trajectory rebuilds the whole CorleoneDynamicOptProblem (tspan, grid, path-constraint discretization, switches, Tsit5) — a copy of prepare. Any change in one silently breaks the reconstruction in the other (the parameter layout used by Corleone.pack must be identical). → Have prepare return opt_prob (or solve return (res, opt_prob)), and build the trajectory from it.

  2. shooting is not propagated. test_convergence.jl calls S.trajectory(sol, pb; grid_size=N) without shooting=get(config, :shooting, :single). Harmless today (only :single), wrong as soon as multiple shooting is added.

  3. Gaps printed in the cron.

    • TestStatus.result! already computes the gap to reference_objective(problem; grid_size, scheme), but here scheme = :shooting_single, so the report never shows a gap; the gaps exist only in the log. The issue asks for them to be printed, fine, but they should also reach the report (or at least be documented as log-only).
    • gap_analytic divides by abs(analytic.objective) without a zero guard; reuse TestStatus.gap (absolute when the reference is zero).
    • When the solve fails, sol.objective can be Inf/NaN and the lines are misleading: print only when converged.
  4. Timing is not comparable with the other crons. JuMP solves once to warm up and times the second solve; here the first (compiling) solve is timed, so the time column of the ModelingToolkit report includes compilation.

  5. violation = 0.0 (from [Tests] Corleone solve helper and ModelingToolkit test suite (smoke, reference solution) (#308) #438, but now published by the cron for the documentation): with path constraints enforced only at grid points, a hardcoded zero is misleading in the published results. → Compute it, or record NaN/missing and say so.

  6. Stale workflow README. .github/workflows/README.md still lists CronModelingToolkit.yml as "manual only until the scope exists"; it should say Saturday. Also check the note (“Ubuntu, CPU”): the reusable workflow's CPU job description mentions Ubuntu and Windows.

Minor

  1. test/README.md says "The tests themselves are discovered from the files: this page lists none of them", yet the new section lists test_problem, test_smoke, test_methods. → Drop the list.
  2. Test.@test true mirrors the JuMP cron; fine, but a comment saying why (count a passing problem) would help.
  3. The docs build went from ~13–14 min to ~24 min with ModelingToolkit in the docs environment. Worth mentioning in the PR description, and worth checking whether it is needed at all: if the snippet is not executed, ModelingToolkit is only needed for the API reference of ModelingToolkitModels.
  4. The Documenter cross-reference fixes (OptimalControlProblems.Problems.Problem) are unrelated to MTK; they are fine but the PR description should explain why they were needed here (dead links appeared only once ModelingToolkit was loaded?), or they should go to a separate commit/PR.

Summary

The core of the issue (trajectory extraction, cron, schedule) works and is tested, but items 1–2 must be fixed before review, and 3 is a maintainability risk. Proposed next step: address them in separate commits on this branch.

Brings in #446 (JuMP and comparison tests rationalized), #447 (label
dispatch) and #448 (statuses permission for the crons). No conflict.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep

@ocots ocots left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Critical review after merging main (#446, #447, #448)

Applied: ct-conventions v0.11.0, ct-agents v0.4.0. main was merged into this branch (df5f3b3, no conflict). Not run locally (no Julia in this environment): the CI must run again on the merge, and the "Verification" numbers of the description predate #446.

The self-review of 10 Nov is still entirely open: no commit since. Its blocking items stand and I confirm them by reading the code: the docs Manifest commits path = "/Users/ocots/…" and OptimalControlProblems was added to docs/Project.toml (against SITE18: the package comes from LOAD_PATH, see docs/make.jl); the snippet hardcodes (0.0, 1.0) and does not discretize the path constraints it says it discretizes; dynamic_trajectory duplicates prepare; timing includes compilation; violation = 0.0; .github/workflows/README.md still says "manual only". I do not repeat them below.

New: what this PR does not do that #446 now expects

#446 set the philosophy of the tests (test/README.md, "Three kinds of tests"). The ModelingToolkit environment does not follow it:

  1. No model equivalence for ModelingToolkit — "the most important part, since comparing models is fair only if they are the same problem". suite/comparison/test_modelings checks JuMP against both OptimalControl modelings at the continuous level; nothing checks that the ModelingToolkit System is the same problem as the OptimalControl model. The cron will publish ModelingToolkit results next to the others (and the docs say checked_against=:OptimalControl) with no evidence that the problem is the same. → Add a test_modelings in the ModelingToolkit environment (opt-in, so the comparison environment stays free of ModelingToolkit), reusing common/continuous.jl: evaluate the equations, the integrand, the boundary and path constraints of the System at the points of Continuous.trajectories and compare with Continuous's OptimalControl functions. This needs OptimalControl in test/suite/ModelingToolkit/Project.toml.
  2. Duplication instead of shared tests. #446 wrote the Problem API, smoke and convergence tests once (common/optimalcontrol_tests.jl), parameterized by backend. suite/ModelingToolkit/test_problem.jl is a near copy (including changed), test_smoke.jl and the new cron copy the loops. → Generalize the shared module to a modeling-agnostic one (model type check, solve module, outcome and trajectory as arguments), or at least share changed and the loops; the cron should become the same thin wrapper as cron/OptimalControl/test_convergence.jl.
  3. Convergence is tested on every PR. suite/ModelingToolkit/test_reference_solution.jl (from #442) asserts succeeded(res) and a 5 % gap: against #360 ("convergence is reported, not tested"), and 5 % is too loose to detect a wrong model. Its natural place is the cron (reported), while an equivalence check (point 1) catches model errors on every PR.
  4. Initial guess ignored (inline): the solves start from 0.0, never from initial_guess(pb), so the cron does not measure what the report is meant to measure (#377, #378).
  5. Generic code tested on a named problem (inline): fine with one problem; once there are more, select with Representative.select over problems(ModelingToolkitBackend()) and for_each_problem(...; only=...) (#446).

Other

  1. The cron's grid (grid_size_data = 500 for bryson_denham) is a collocation grid reused as the shooting control grid and the path-constraint grid; the PR gives no duration for a cron run. Please state it, or choose a grid for shooting explicitly.
  2. Gaps are only println-ed (inline); the trapezoidal reference is not a meaningful comparison for a shooting solve; only the analytic gap is.
  3. The trajectory tests are structural only (inline): nothing checks the reconstructed values.
  4. tools/cron/report.py: ModelingToolkit is absent from DEFAULT_SCOPES, so the summary issues get no placeholder section for it before its first run; minor, but the cadence edit alone does not integrate the scope.
  5. docs/modelings.jl: checked_against=:OptimalControl is false today; packages misses OptimizationMOI and OrdinaryDiffEqTsit5 (inline).

Verdict

Not ready to leave draft. Order I would suggest: (a) the self-review's blocking items (Manifest/Project, snippet); (b) one prepare used by solve, trajectory and initial guess; (c) the continuous equivalence test MTK vs OptimalControl; (d) align the suite and cron with the shared tests of #446; (e) re-run CI with test ModelingToolkit backend and report the cron duration.


Generated by Claude Code

Comment thread test/common/solve_modelingtoolkit.jl Outdated

# Controls and initial values
ctrl_syms = filter(MTK.isinput, MTK.unknowns(sys))
inits = [u => 0.0 for u in ctrl_syms]

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The initial guess of the problem is never used: here and in prepare (l. 138) every control starts at 0.0, whatever initial_guess(pb) says. test_problem checks that the init of the metadata (#377) is recorded and that init= is honoured, but no solve reads it, so the convergence cron does not measure "does the initial guess lead to the best known solution", which is what the report is for (#378). JuMP and OptimalControl start from the init. → Use OCP.initial_guess(pb).control (a number, a vector or a function of t: evaluate it at the switching times), in one place.

Also, this function rebuilds the whole problem a second time (already in the self-review): if grid_size differs from the one of the solve, reconstruct(res.u) silently gives a wrong trajectory or throws, and the cron pays a second symbolic build at N = 500. Return the CorleoneDynamicOptProblem from prepare and reuse it.


Generated by Claude Code

Main.TestStatus.for_each_problem(test, backend) do problem
pb = getfield(OptimalControlProblems, problem)(backend)
N = OptimalControlProblems.grid_size_data(problem)
time = @elapsed sol = S.solve(

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since #446 the convergence tests of a modeling are written once (common/optimalcontrol_tests.jl) and the cron files are thin wrappers. This file re-implements the loop with three divergences from it:

  • the first (compiling) solve is timed, OptimalControl and JuMP time the second one;
  • N = grid_size_data(problem) is the collocation grid of the problem (500 for bryson_denham), reused here as 499 control switches and 500 discretized path constraints in single shooting with ForwardDiff: is that what we want to report, and how long does it take? Nothing in the PR says;
  • the gaps are println-ed: they never reach the report (scheme = :shooting_single has no reference, so result! records no gap), and comparing a shooting solve with the trapezoidal reference at N = 500 mixes two discretizations — only the gap to the analytic solution is meaningful. Put it in the report (e.g. a reference for the scheme, or a column), not in the log.

Generated by Claude Code

Comment thread docs/modelings.jl Outdated
res = solve(prob, Ipopt.Optimizer())
res.objective""",
model_start=r"^\s*ModelingToolkit\.@named sys = ModelingToolkit\.System\(",
checked_against=:OptimalControl,

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

checked_against=:OptimalControl is false (from #440, but this PR publishes the modeling in the docs): by the header of this file it means "the modeling whose NLP this one is checked equal to on every pull request", and nothing compares the ModelingToolkit model with the OptimalControl one — suite/comparison/test_modelings (#446) is JuMP vs OptimalControl/scalarized only. Either add that check (see the review summary) or set nothing until it exists.

Also: packages omits OptimizationMOI and OrdinaryDiffEqTsit5, which the snippet loads.


Generated by Claude Code

Test.@test isfinite(out.objective)

# 8. trajectory reconstruction
dyn_traj = Main.SolveModelingToolkit.dynamic_trajectory(res, pb; grid_size=10)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These checks are all structural (keys, lengths). Nothing checks that the reconstructed trajectory is the solution: e.g. that x₁(0), x₂(0) are the initial conditions, the final ones match the boundary constraints, and the control is the one of res.u. With a 2-iteration solve the values are meaningless anyway; a check on the converged solve of test_reference_solution (or against analytic_reference(problem).state at a loose tolerance) would actually test the reconstruction.

The control extension vals[min(i, length(vals))] assumes Corleone returns n - 1 control values; if it returns n, the code is still right, if it returns them on another grid it is silently wrong. Worth one assertion.

Also, the problem and its component names are hardcoded (bryson_denham, "x₁"): #446 never names a problem, it computes the selection from the catalogue (common/representative.jl). Fine with one problem today, but take the names from state_components(sys).


Generated by Claude Code

…stops at the model (#439)

The asset Manifest committed a local path and docs/Project.toml listed the package, which the
docs load from LOAD_PATH (SITE18). The snippet solved with a hardcoded time span and without
the discretization of the path constraints the tests use: it now stops at the model, and
checked_against is nothing since no check runs on every pull request.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep
…modelings (#439)

common/modeling_tests.jl holds the tests of common/optimalcontrol_tests.jl (#441),
parameterized by the backend and an adapter, the solves of the modeling, so that
ModelingToolkit uses them too. result! takes the reference of the gap, by default the
reference objective of the discretization.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep
…nd measure the violation (#439)

prepare returns the Optimization problem and the Corleone one; solve returns both with the
result, and the trajectory is read from the problem solved instead of a copy of prepare. The
controls start from the initial guess of the problem (#377), not 0. The violation is the
largest violation of the constraints and bounds of the NLP, no longer 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep
…ests, thin cron (#439)

test_modelings reads the System as the data of a JuMP problem and compares it with the
OptimalControl model by Continuous.compare (#441). test_problem, test_smoke and the cron are
wrappers of the shared tests; the cron times the compiled solve and records the gap to the
analytic objective. test_reference_solution, which tested convergence on every run (#360), is
removed. OptimalControl joins the ModelingToolkit environment for the comparison.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep
…he tests (#439)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep
…thing runs

When a shared file runs every environment, the test arguments were empty, which runs
every environment except the opt-in ones: the label `test ModelingToolkit backend` was
lost, and the ModelingToolkit environment never ran on this pull request. The environments
are now named, with the opt-in ones of the labels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSmPZipCYwgepwKpMP9sep

ocots commented Nov 11, 2026

Copy link
Copy Markdown
Member Author

Update after the review (head cc56b5a)

Applied: ct-conventions v0.11.0, ct-agents v0.4.0. main (#446, #447, #448) is merged into this branch, no conflict. This replaces the "Verification" section of the description, which predates #446 and these changes.

What changed since the self-review and the critical review

Documentation

  • The asset Manifest.toml/Project.toml are back to main (no local path); OptimalControlProblems is out of docs/Project.toml (SITE18).
  • The ModelingToolkit snippet stops at the model (the shooting choices are not part of it) instead of a solve with a hardcoded time span and no path-constraint discretization. checked_against is nothing: no check runs on every pull request.

Solve helpers (test/common/solve_modelingtoolkit.jl)

  • prepare builds the Corleone problem once; solve returns the result with both problems, and the trajectory is read from the problem that was solved (no copy of prepare any more).
  • The controls start from the initial guess of the problem ([Metadata] Shared initial guess in the metadata, read by every modeling #377), not 0.0.
  • violation is computed (constraints and bounds of the NLP at the solution), no longer 0.0.
  • The reconstruction of the controls checks the lengths it assumes.

Tests aligned with #446

  • common/modeling_tests.jl: the Problem API, smoke and convergence tests written once, parameterized by the backend and an adapter. OptimalControl and ModelingToolkit use them; the ModelingToolkit test files and the cron are thin wrappers. The cron times the compiled (second) solve.
  • suite/ModelingToolkit/test_modelings: the model equivalence that was missing. The System is read as the data of a JuMP problem (common/continuous_modelingtoolkit.jl) and compared with the OptimalControl and scalarized models by Continuous.compare, without discretizing. OptimalControl joins the ModelingToolkit environment for this, so comparison stays free of ModelingToolkit.
  • test_reference_solution is removed: it tested convergence on every run ([Tests] Report convergence instead of testing it; keep hard checks for breakage and model equivalence #360).
  • TestStatus.result! takes the reference of the gap; for ModelingToolkit it is the objective of the analytic solution (a shooting solve has no reference objective of its own discretization).

CI and reports

  • tools/ci/scope.py: an opt-in environment asked for by a label was lost when a shared file ran everything (empty test arguments), so the ModelingToolkit environment never ran on this pull request. The environments are now named in that case; one unit test added.
  • ModelingToolkit added to the placeholder scopes of the cron summary issues; the workflow README and the note of the cron are corrected (Saturday, Ubuntu + Windows).
  • test/README.md, CHANGELOG.md updated.

Verification

CI on cc56b5a (Julia 1.13, Ubuntu), all green:

  • core: 1308 passed, 1 broken (pre-existing);
  • JuMP, OptimalControl, OptimalControlScalarized, comparison: passed (the shared tests did not break them);
  • ModelingToolkit: 78/78 (test_methods 35, test_modelings 20, test_problem 22, test_smoke 1);
  • documentation build and spell check: passed;
  • python3 -m unittest discover -s tools/ci/test (48) and tools/cron/test (33): passed.

Still open

  • The convergence cron has not run: its duration on the default grid (500 for bryson_denham: 499 control switches, 500 discretized path constraints) and the time/gap columns it records are unknown. To check before the first Saturday run: dispatch CronModelingToolkit.yml with problems=bryson_denham.
  • The comparison is one problem today (bryson_denham is the only ModelingToolkit problem).
  • Not decided yet: whether OptimalControl in the ModelingToolkit environment is acceptable (the extension is no longer tested alone there); a control guess that is a function of time is taken at t0.

Generated by Claude Code

ocots and others added 2 commits November 11, 2026 16:48
…ed (#439)

A System does not say its time span when the cost has no integral (a Mayer cost): tspan
reads it from the parameters of the problem, as the continuous comparison does. A test checks
that the controls of the problem solved start from the initial guess of the problem (#377).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…odeling (#439)

A better sample than bryson_denham alone: a Lagrange cost, state bounds with boundary
conditions, a Mayer cost with state and control bounds. They pass the continuous comparison
with OptimalControl and the smoke solve; the comparison fails, on the right check, when a
parameter of the ModelingToolkit model is changed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@ocots
ocots marked this pull request as ready for review November 11, 2026 16:41
@ocots
ocots merged commit 68b58e2 into main Nov 11, 2026
20 checks passed
@ocots
ocots deleted the feat/439-mtk-cron-docs branch November 11, 2026 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

run ci github-runner Trigger the CI workflow on GitHub-hosted runners run documentation Trigger the Documentation workflow on this PR test ModelingToolkit backend Package-specific scope or cron label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Cron/Doc] ModelingToolkit convergence cron, trajectories, and documentation (#308)

2 participants