Metrix/InterferenceETL
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: 邻近高干扰小区数按制式拆分统计

Browse Source
This commit is contained in:
nixevol
2026-08-11 16:59:48 +08:00
parent eca4c5cbb1
commit 3835a0b928
4 changed files with 126 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidocs/project_context.md
+6
View File
@@ -109,6 +109,12 @@
- The current `2026-08-07 14:00:00` database result was exported directly through the history-only path and replaced in Storage as a verified GBK CSV: 1,082 rows, 150,251 bytes, no UTF-8 BOM, and the expected eleven columns. The temporary UTF-8 backup was deleted after validation.
- The newer `2026-08-07 15:00:00` source group currently contains duplicate CGI rows, for example `460-00-122737-22`. Its database transaction rolled back on the existing `(metric_time, cgi)` primary key, so the retained `14:00` database and history result were not replaced. Duplicate-row selection requires a separate business rule.
## 2026-08-11: Per-network-type nearby counts
- Summary CSV, database table, and history CSV add `nearby_26g`, `nearby_700m`, `nearby_tdd`, and `nearby_fdd`: the same 1 km high-interference neighbors split by the neighbor's `network_type`. Each defaults to `0` and the four values always sum to `nearby_count`.
- Previous-period fields `prev_nearby_26g`, `prev_nearby_700m`, `prev_nearby_tdd`, and `prev_nearby_fdd` follow the `prev_nearby_count` rules: matched by CGI from the previously retained database time, empty/`NULL` when unmatched or on the first run. On the first run after this upgrade the previous rows only have `NULL` in the new columns, so the previous split fields stay empty for that one period and self-heal afterwards.
- Existing tables migrate automatically: current count columns are `INT NOT NULL DEFAULT 0`, previous count columns are `INT NULL`. The history export SELECT is now generated from `SUMMARY_HEADER`, so result columns stay in one place. Twenty-two tests pass.
## 2026-08-11: Network type relabeled to 2.6G/700M/TDD/FDD
- `network_type` keeps its column name but now labels radio type per source prefix: `5G干扰监控` is `2.6G` (the user treats 2.6G as the unambiguous 5G label because 700M is also 5G), `700M干扰监控` is `700M`, `SDR_TDD干扰监控` and `反开RD干扰监控` are `TDD`, and the three FDD-schema sources (`SDR_FDD干扰监控`, `5G下FDD干扰监控`, `700M下FDD干扰监控`) are `FDD`. The old `2.6G/700M/4G` grouping is gone.