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

Segment and cache Stage 12 US simulations

未关闭
  • 哪里不对？
#711 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@anth-volk 已经在做这个了。

开始于 2026年9月30日。

  • #712 来自 @anth-volk —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
api, backend, devops, documentation, testing

调研方向

Start by locating the Stage 12 worker coordination path and the existing API v1 runner behavior that defines 20-part execution, then identify the dataset, baseline-cache, deployment-validation, and worker-manifest entry points. Verify the workflow with unit tests for segmentation, caching, coordination, validation, error preservation, and cancellation. Done means independent concurrent baseline and reform execution, 40 segment calls, validated cache artifacts, stable policy errors, consistent failure states, and deployment documentation.

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

描述

Problem

Stage 12 US reports currently execute each baseline and reform simulation as one calculation. They do not have the 20-part execution and precomputed baseline data used by the API v1 runner. The current coordination path also needs to preserve policy-validation details and stop observing the other simulation normally after either baseline or reform fails.

Scope

  • Implement deterministic 20-part US simulation execution within Stage 12 without importing or calling API v1 runner code.
  • Keep baseline and reform execution separate, producing 40 segment function calls for a complete report.
  • Precompute, version, store, validate, and load the Stage 12 dataset and baseline cache artifacts.
  • Include cache identity and validation results in the Stage 12 worker manifest.
  • Observe baseline and reform concurrently.
  • When either simulation fails, cancel the other simulation, preserve its failure details, and persist consistent report and simulation states.
  • Reject malformed policy effective periods with a stable error code and detailed message.
  • Document the deployment, cache, execution, and failure-handling behavior.
  • Add unit tests for segmentation, cache construction and loading, deployment validation, coordination, error preservation, and cancellation.

Acceptance criteria

  • A successful segmented US report produces two simulation calls and 40 segment calls.
  • Baseline and reform calculations run concurrently and remain separate through aggregation.
  • A failed simulation causes the report to fail and the other simulation to be cancelled or recorded as incomplete.
  • Validation errors retain their structured error code and useful summary at the simulation and report levels.
  • Worker deployment rejects missing, mismatched, or inaccessible cache artifacts.
  • The implementation remains independent of API v1 runner modules.
  • Unit tests and deployment documentation cover the complete workflow.
主要语言
Python
星标
1
派生
1
平均合并
1 天 8 小时
30 天内合并 PR
51

环境准备

从这里开始

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

PolicyEngine/policyengine-sim-api 的其他 Issue

查看 PolicyEngine/policyengine-sim-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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