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

docs: 记录分制式邻近统计部署结果

Browse Source
This commit is contained in:
nixevol
2026-08-11 17:24:15 +08:00
parent 3835a0b928
commit 467b9a1dfd
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidocs/project_context.md
+5 -1
View File
@@ -113,7 +113,11 @@
- 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`. - 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. - 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. - 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 locally and in the runtime image.
- Deployed package SHA-256 is `638EEC791FACA55937FCF335402F40776B0749375216D27FBB9F8F1864007EBE`. A first run (`9ccdc7cba5bc48fd8c57a698de3dde84`) returned `status=skipped` and migrated the schema; all eight new columns were confirmed through the Database API.
- Because the `16:00` sources were late, the user chose to truncate `interference_hourly_summary` and reprocess the `15:00` group instead of waiting. Run `23d870b5d1434a548520c7fc2413e2ba` inserted 1,062 rows (869 threshold-filtered, 0 duplicate CGI, 1,059 coordinates matched).
- Production verification: every row satisfies `nearby_26g + nearby_700m + nearby_tdd + nearby_fdd = nearby_count` (totals 847/216/1,194/3,229 = 5,486); cross-type pair sums are symmetric; `network_type` contains only `2.6G=145`, `700M=68`, `TDD=206`, `FDD=643`. The history CSV was rewritten in GBK with the nineteen-column header and 1,062 rows.
- The reprocessed batch has empty previous-period fields by design because the `14:00` data no longer existed; from the next group onward the previous fields, including the new splits, populate normally.
## 2026-08-11: Network type relabeled to 2.6G/700M/TDD/FDD ## 2026-08-11: Network type relabeled to 2.6G/700M/TDD/FDD