docs: scope junction exclusion routing follow-up
This commit is contained in:
1 parent
cfb3593a0b
commit
b9c38b0b7b
5 files changed
+63
No files matched your search
@@ -0,0 +1 @@
|
||||
{"_example": "Fill with {\"file\": \"<path>\", \"reason\": \"<why>\"}. Put spec/research files only — no code paths. Run `python3 .trellis/scripts/get_context.py --mode packages` to list available specs. Delete this line once real entries are added."}
|
||||
@@ -0,0 +1 @@
|
||||
{"_example": "Fill with {\"file\": \"<path>\", \"reason\": \"<why>\"}. Put spec/research files only — no code paths. Run `python3 .trellis/scripts/get_context.py --mode packages` to list available specs. Delete this line once real entries are added."}
|
||||
@@ -0,0 +1,21 @@
|
||||
# 复杂排除区绕行与多通行区求解范围研究
|
||||
|
||||
## Goal
|
||||
|
||||
承接已归档父任务的区域求解遗留;先确定来源通行关系和安全可行域,不将多边形裁切等同于路径规划。
|
||||
|
||||
## Requirements
|
||||
|
||||
- 审计来源通行关系、排除区与必要入口连接,区分面裁切、连通区域和车辆绕障路径。
|
||||
- 比较支持边界、失败诊断与可行方案,明确是否需要车辆尺寸及转弯半径等输入。
|
||||
- 优先完成 junction-layer-seams;本任务当前仅规划,不恢复已归档父任务。
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] 为接缝被阻断、核心内部障碍和多个隔离通行区提供可重复反例。
|
||||
- [ ] 给出当前求解器的支持/拒绝矩阵和下一实现单元的可观察验收条件。
|
||||
- [ ] 明确需要用户决定的通行语义与安全约束,实施前完成设计和实施计划。
|
||||
|
||||
## Notes
|
||||
|
||||
src/compile/junction-region-solver.js 当前是多边形 difference,不提供绕障路径规划。不能仅凭区域相连推断合法机动车转向。此前“可以直接完成”的估计过于宽泛,本专项先研究边界,不承诺任意障碍布局或车辆扫掠规划。
|
||||
@@ -0,0 +1,14 @@
|
||||
# 区域求解边界初审
|
||||
|
||||
2026-09-17,只读审计;本专项仍为 planning,不在接缝专项内更换区域算法。
|
||||
|
||||
| 场景 | 当前路径 | 限制 |
|
||||
| --- | --- | --- |
|
||||
| 入口与排除区域相交 | junction-boundary-graph.js:99 检测相交并标记 overlaps-known-region,设施生成省略入口 | 没有重新布置入口绕障 |
|
||||
| 核心内部已知安全孔洞 | buildCoreClosure 按 isHole、包含关系、入口避让发布 holes | 只能保证该结构核心面保留孔洞 |
|
||||
| 障碍穿过核心边界或切断必需接口 | buildCoreClosure 返回 known-exclusion-region | 不重求连通区域 |
|
||||
| 多个断开的铺装区域 | solveComplexPavementRegion 返回 disconnected | 不生成跨区连接,不等同于多通行区规划 |
|
||||
|
||||
需要优先澄清的实现风险:complex-junction-surfaces.js 的 appendPavementRegion 只取各面 coordinates[0];junction-pavement-region.js 又以 polygon[0] 填掉所有合并结果孔洞。因而不能由 buildCoreClosure 的孔洞单测推断最终权威铺装保留已知排除区域。后续应先添加最终发布面的排除区反例,区分构建缝隙与已知孔洞,再考虑绕障。当前未声称运行了该最终反例,也未改产品行为。
|
||||
|
||||
建议的实施顺序:最终铺装保留排除区 → 对象级连接/拒绝契约 → 有限障碍布局的区域求解 → 需要来源与车辆约束的路径规划。不能只对凹多边形做裁切后宣称已提供合法车辆绕行。
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"id": "junction-exclusion-routing",
|
||||
"name": "junction-exclusion-routing",
|
||||
"title": "复杂排除区绕行与多通行区求解范围研究",
|
||||
"description": "承接已归档父任务的区域求解遗留;先确定来源通行关系和安全可行域,不将多边形裁切等同于路径规划。",
|
||||
"status": "planning",
|
||||
"dev_type": null,
|
||||
"scope": null,
|
||||
"package": null,
|
||||
"priority": "P2",
|
||||
"creator": "dingkang",
|
||||
"assignee": "dingkang",
|
||||
"createdAt": "2026-09-17",
|
||||
"completedAt": null,
|
||||
"branch": null,
|
||||
"base_branch": "main",
|
||||
"worktree_path": null,
|
||||
"commit": null,
|
||||
"pr_url": null,
|
||||
"subtasks": [],
|
||||
"children": [],
|
||||
"parent": null,
|
||||
"relatedFiles": [],
|
||||
"notes": "",
|
||||
"meta": {}
|
||||
}
|
||||
Reference in new issue
Block a user