Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Manage state information more cleanly

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
backend

调研方向

Start by tracing state and exclusion logic across Problem, ModelSubspace, ModelSpace, and CandidateSpace, including the state changes from #128. Then inspect graph_iteration_layers and Problem.state to determine how iteration methods should be represented. Done means state is managed separately from CandidateSpace and plotting makes FAMoS method switches clear.

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

描述

Currently, the method state information is mostly stored in the candidate space object. All state information could be moved into a separate state object, such that the candidate space is no longer stateful. e.g. there are a few objects (Problem, ModelSubspace, ModelSpace, CandidateSpace) that each contain some logic to manage exclusions -- this could all be moved to the state object.

State information (some of which is only used by the FAMoS method currently):

  • each iteration:
    • the identified models
    • the calibrated models
    • the method
  • exclusions (accumulative over iterations)

Partially resolved by #128 , where all calibrated models from all iterations are now stored in Problem.state.

Use this in plotting code too, e.g.:

  • add method information from each iteration to graph_iteration_layers, to make FAMoS method switches clear
主要语言
Python
星标
14
派生
1
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

PEtab-dev/petab_select 的其他 Issue

查看 PEtab-dev/petab_select 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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