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

Calculate budget windows on the v2 economy path

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the v2 economy path and the existing /simulate/economy/budget-window gateway flow, then inspect the simulation entry point and the v2 economy result storage. The issue calls for a new simulation.budget_window_runs table, report routes declared for the generated client, and staging qualification against gateway totals. Done means window runs are stored by year, totals are summed from stored budget figures, and concurrent windows fit the available Modal capacity.

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

描述

The Public API's /v2/reports will offer budget windows: one reform compared with its baseline in each year of a window of up to 75 years, with the totals. Today only the old gateway calculates them (/simulate/economy/budget-window), as one Modal batch call whose state lives in Modal.

The Simulation Entrypoint should calculate them itself on the v2 economy path, so that their results are stored as rows like other v2 economy results:

  • a budget-window report (an economy report with a window size) and its runs, one row per calculation in a new simulation.budget_window_runs table, grouping one report run per year;
  • the years started a few at a time, so that one window does not take every Modal container, with the next years started when earlier years' calls report their ends and by the safety check;
  • totals summed from each year's stored budget figures when the report is read;
  • routes for submitting, reading and running budget-window reports again, declared for the generated client;
  • enough Modal capacity on the v2 economy functions for several windows at once;
  • a way to qualify the totals on staging against the old gateway's budget windows.
主要语言
Python
星标
1
派生
1
平均合并
1 天 19 小时
30 天内合并 PR
81

环境准备

从这里开始

  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 摘要。