fix: Correct BlockedSignal data contamination numbers

- Only 31 records from multi-timeframe alerts (not 11,429)
- 11,398 records are 1-minute data (kept as DATA_COLLECTION_ONLY)
- Total marked as OLD_V9_VERSION: 31 (15min/1H/4H/Daily only)
This commit is contained in:
mindesbunister
2025-12-05 10:40:02 +01:00
parent eefee98818
commit d7d8369cc7

View File

@@ -636,8 +636,8 @@ docs/COMMON_PITFALLS.md
**Purpose:** Track exact minute-by-minute price movements for blocked signals to determine EXACTLY when TP1/TP2 would have been hit
**CRITICAL: Data Contamination Discovery (Dec 5, 2025):**
- **Problem:** All TradingView alerts (5min, 15min, 1H, 4H, Daily) were attached to OLD v9 version with different settings
- **Impact:** 11,429 BlockedSignal records collected from wrong indicator parameters (confirmBars=0 instead of current v9)
- **Problem:** All TradingView alerts (15min, 1H, 4H, Daily) were attached to OLD v9 version with different settings
- **Impact:** 31 BlockedSignal records from wrong indicator version (multi-timeframe data collection)
- **Solution:** Marked contaminated data with `blockReason='DATA_COLLECTION_OLD_V9_VERSION'`
- **Exception:** 1-minute data (11,398 records) kept as `DATA_COLLECTION_ONLY` - not affected by alert version issue (pure market data sampling)
- **SQL Filter:** Exclude old data: `WHERE blockReason != 'DATA_COLLECTION_OLD_V9_VERSION'`