Planner no longer has god-view. It assumes threats enter from detection boundary (unified info network earliest detection point), not route start. Core: DetectionCalculator (EO attenuated by Visibility, radar/IR unaffected; earliest detection via segment-circle intersection). EquipmentDeployment: drop DetectionRadius, add RadarRange/EORange/IRange/DetectionAccuracy. FireUnit detection fields activated in BuildFireUnits. IDefensePlanner.Plan adds 4th param detectionSources. Engine: BuildDetectionSources merges standalone detectors + fire-unit self-detection into unified list, passed to planner. Fix: Solve robustness when GenerateFireEventsAt returns empty (detection boundary too late to intercept). Tests 193 to 208 (+15). 0 warnings.
35 lines
1.7 KiB
Markdown
35 lines
1.7 KiB
Markdown
# 探测驱动的规划(8.1.1)
|
||
|
||
- **日期**:2026-06-15
|
||
- **提出人**:tian
|
||
- **关联需求**:V1.0 功能需求(探测设备)、技术要求终版
|
||
- **优先级**:高
|
||
|
||
## 变更描述
|
||
|
||
planner 不再有上帝视角。仿真开始时,planner 假设威胁从"探测边界"(统一信息网络的最早发现点)进入,而非航路真实起点。探测精度差 → 抛撒散布范围扩大。
|
||
|
||
### 设计原则
|
||
planner 是参谋,只能基于侦查信息制定方案。假设我方有统一信息网络,可同步威胁信息。独立探测设备与火力单元自带探测并存。
|
||
|
||
### 变更内容
|
||
1. **新增 DetectionCalculator**:探测能力评估的唯一实现。光电受 Visibility 衰减,雷达/红外不受影响;统一信息网络找最早探测点
|
||
2. **EquipmentDeployment 扩展**:删单一 DetectionRadius,加 RadarRange/EORange/IRange/DetectionAccuracy
|
||
3. **FireUnit 探测字段激活**:BuildFireUnits 赋值(原为死代码)
|
||
4. **planner 接口扩展**:Plan 加第 4 参数 detectionSources;到达时间基于探测边界
|
||
5. **SimulationEngine 构建探测源**:独立探测 + 火力单元自带探测统一传入 planner
|
||
|
||
## 影响范围
|
||
|
||
- [x] 接口变更:IDefensePlanner.Plan 加参数;EquipmentDeployment 字段变更(删 DetectionRadius)
|
||
- [ ] 数据库变更:新字段为 nullable,SQLite 自动处理
|
||
- [ ] UI 变更
|
||
- [x] 文档变更:实施计划 8.1.1、CHANGELOG、VERSION
|
||
|
||
## 验收
|
||
|
||
- 全量测试 193 → **208**(+15),64s 通过
|
||
- DetectionCalculator 13 项单测(天气衰减/最早探测点/散布半径)
|
||
- 探测驱动规划 2 项测试(planner 基于探测边界、集成场景不破坏)
|
||
- 范围外:实时探测→火控链路(未来增强)
|