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

fix: 按最大干扰值去重CGI

Browse Source
This commit is contained in:
nixevol
2026-08-07 16:50:45 +08:00
parent 232b7c8b25
commit e6ceae74ca
4 changed files with 61 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aidocs/project_context.md
+5
View File
@@ -108,3 +108,8 @@
- Twenty-one containerized tests and offline-package execution pass. The deployed package SHA-256 is `11B0010E8FDFEC32058BC8B282E5A5608FC92C48572611A3F9F4632962C18D98`.
- 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-07: Duplicate CGI selection
- Retained high-interference rows are deduplicated by CGI before nearby counting and database insertion. When duplicates exist, the row with the numerically largest `interference_dbm` is kept; equal values keep the first encountered row. Converted source CSVs remain complete.
- The deduplication count is recorded as `duplicate_cgi_rows` in `manifest.json` and stdout. This prevents the existing `(metric_time, cgi)` database primary key from failing and prevents duplicate source rows from inflating `nearby_count`.