[Cron] cron-convergence

Abierto
#418 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
28/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, julia

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Julia
Estrellas
13
Forks
1
Merge medio
3 h 9 min
PR fusionados (30 d)
47

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de control-toolbox/OptimalControlProblems.jl

Todos los issues de control-toolbox/OptimalControlProblems.jl

Issues similares

Más issues de Julia

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.