Stopping criteria for solvers

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python

调研方向

The issue describes solver stopping criteria and points to PR #176, where an initial objective-change criterion for ProximalPoint and ProximalGradient is proposed. Read that pull request and the solver implementations to identify how criteria are applied across solvers and how individual objective terms can be evaluated. Done means all solvers support stopping criteria, including criteria that operate on one objective term.

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

描述

enhancement good first issue help wanted

Motivation

PyProximal solvers are currently only stopped when the maximum number of iterations is reached.

It is desirable to introduce stopping criteria to prematurely stop a solver based on some condition. A first attempt at introducing a stopping criterion to ProximalPoint and ProximalGradient based on the change in objective function between two consecutive iterations can be found in https://github.com/PyLops/pyproximal/pull/176

Definition of done

The same criterion should be implemented to all solvers

  • More of such criteria should be implemented (e.g., operating only on one term of an objective function instead of the overall objective function)
主要语言
Python
星标
85
派生
22
平均合并
2 小时 11 分钟
30 天内合并 PR
7

环境准备

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

从这里开始

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

PyLops/pyproximal 的其他 Issue

查看 PyLops/pyproximal 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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