Publish v2 catalog regions from the Public API's own region reference files
维护者通常 3 天内回复
评估
调研方向
Start by locating the v2 region publication code and the certified data release inputs that provide row filters and weight matrices; the issue does not name specific files or tests. Check how the current PolicyEngine.py region registry feeds /v2/regions, then trace how region reference files should select households. Done means publication uses repository-owned references, rejects unavailable selectors, and omits US places that cannot run.
由索引模型根据 Issue 内容生成。
描述
What
The Public API should publish the regions of each v2 catalog version from region reference files it keeps in its own repository, one per country, instead of copying PolicyEngine.py's region registry.
Each file should list every region's code, label, type, parent and US state, the value that selects its households, and the v1 identifier it replaces (for example country/ni and constituency/Aldershot). Publication should then give each region its dataset and filter from the certified data release that PolicyEngine.py ships:
- US states and congressional districts, and UK nations: a row filter (a column and a value).
- UK constituencies and local authorities: the release's weight matrix and the region's row code in it.
It should refuse to publish a region the data cannot select, and leave out regions that cannot run yet (US places).
Why
- Today
/v2/regionslists only the regions PolicyEngine.py's registry exposes: 5 UK regions, and 333 US places that would calculate national figures if run as listed. - UK constituencies and local authorities are missing, and are known in v1 by name rather than by ONS code.
- The registry's region lists and filters change with each PolicyEngine.py release, and nothing checks them against the data.
With reference files owned by the Public API, the catalog lists all 1,015 UK regions by ONS code, uses "United States" and "United Kingdom" as the national labels, and fails loudly when a filter column or matrix row is missing.
- 主要语言
- Python
- 星标
- 18
- 派生
- 33
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 36
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-api 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 88/100
PolicyEngine/policyengine-api#3911 ·
维护者通常 3 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
PolicyEngine/policyengine-api#3910 ·
维护者通常 3 天内回复
-
Stop serving economy results cached with ×100 decile relative changes可能已有人在做 @anth-volk 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 45/100
PolicyEngine/policyengine-api#4025 ·
维护者通常 3 天内回复
-
Store the metadata v3 reads in the v2 catalog, from PolicyEngine.py's public records可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 4/5 3-5 天 新手友好度 48/100
PolicyEngine/policyengine-api#4022 ·
维护者通常 3 天内回复
-
Request UK constituency and local-authority impacts separately from the national economy result可能已有人在做 @anth-volk 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
PolicyEngine/policyengine-api#4021 ·
维护者通常 3 天内回复
查看 PolicyEngine/policyengine-api 的全部 Issue
相似的 Issue
-
Python Volcengine provider returns failures instead of raising them可能已有人在做 @Ricardo-M-L 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 79/100
agent-infra/sandbox#248 ·
-
Textractor leaves empty temporary files when remote retrieval fails可能已有人在做 @HuaTNA 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
test(bm_generation): pin the learning parameters and CPU sync shortcut可能已有人在做 @iloveeyjafjalla 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
qboson/kaiwu-pytorch-plugin#1341 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
elder-plinius/V3R1T4S#625 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复