Fix Stage 12 comparison tolerance and UK geography metadata
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 52/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
- 领域
- backend, infrastructure, testing
调研方向
Start with the Stage 12 result-comparison and UK geography handlers, then trace resolution of the canonical PolicyEngine UK lookup files and the Stage 12 service credentials. Add unit tests for tolerance and missing-data failures, and deployment-infrastructure validation for access to both lookup objects. Done means valid metadata for both child simulations, explicit failures for missing data, exact artifact digests, and restricted lookup access.
由索引模型根据 Issue 内容生成。
描述
Problem
Stage 12 result comparison currently reports immaterial floating-point differences, while UK report artifacts can omit constituency and local-authority names and coordinates when the canonical lookup files are not resolved.
Scope
- Compare numeric result values using an absolute tolerance of 0.01 while retaining exact artifact digests.
- Resolve UK constituency and local-authority names and coordinates from the canonical PolicyEngine UK lookup files.
- Fail explicitly when required lookup data or output values are missing.
- Verify that the Stage 12 service credentials can read the two required lookup objects without granting access to unrelated private dataset objects.
- Add unit tests and deployment-infrastructure validation for these behaviors.
Acceptance criteria
- Numeric values whose absolute difference is no greater than 0.01 compare as equal.
- Both Stage 12 child simulations receive valid UK geography output metadata.
- Missing geography lookup data causes an explicit failure.
- Automated tests cover the comparison and geography handlers.
- Deployment validation checks access to both canonical lookup objects.
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 1 天 18 小时
- 30 天内合并 PR
- 59
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
Update policyengine to 6.7.3可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 半天 新手友好度 70/100
PolicyEngine/policyengine-sim-api#823 ·
维护者通常 1 天内回复
-
Integration tests fail due to missing UV virtual environment setup可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
维护者通常 1 天内回复
-
Update policyengine to 6.10.2可能已有人在做 @policyengine 于 2 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 25/100
PolicyEngine/policyengine-sim-api#908 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
PolicyEngine/policyengine-sim-api#907 ·
维护者通常 1 天内回复
-
Update policyengine to 6.10.1可能已有人在做 @policyengine 于 3 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 20/100
PolicyEngine/policyengine-sim-api#905 ·
维护者通常 1 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
The changelog workflow excludes otelbot but not dependabot, so every Dependabot pull request fails the changelog check可能已有人在做 @ocelotl 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 82/100
open-telemetry/opentelemetry-python#5825 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
cuga-project/cuga-agent#1020 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 70/100
microsoft/playwright#43640 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
stac-utils/stac-fastapi-elasticsearch-opensearch#965 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复