[Cron] cron-convergence

未关闭
#418 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
28/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, julia

调研方向

Open the linked GitHub Actions run and compare its moonlander result with the previous report on the results branch. Read the workflow guidance in .github/workflows/README.md and the threshold logic in tools/cron/report.py; determine whether the lost convergence is expected or a regression. The issue is done when the sections say No findings.

由索引模型根据 Issue 内容生成。

描述

cron-convergence

Convergence that got worse

Written by the weekly cron workflows, one section per scope, replaced by each run of that scope. Convergence is reported, not tested (#360): each entry below is a solve that converged in the previous run of the scope and no longer does, or whose objective moved by more than the threshold of tools/cron/report.py.

Who: a maintainer looks; nothing fails and nothing changes automatically.

What to do: open the run, compare with the previous report on the results branch, and decide whether the change is expected (new initial guess, new solver version) or a regression to investigate. Details: README. This issue updates itself; close it when the sections say No findings.

cron-convergence

Run: https://github.com/control-toolbox/OptimalControlProblems.jl/actions/runs/42387115100

platform problem modeling test outcome
cron-JuMP-robustness-1.13-ubuntu-latest moonlander JuMP solver=ipopt mu_strategy=monotone mu_init=0.001 lost
主要语言
Julia
星标
13
派生
1
平均合并
3 小时 9 分钟
30 天内合并 PR
47

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

control-toolbox/OptimalControlProblems.jl 的其他 Issue

查看 control-toolbox/OptimalControlProblems.jl 的全部 Issue

相似的 Issue

更多 Julia Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。