4.0
- fixing data-type circular import - removing HOLD signal from saving to database to reduce data size
This commit is contained in:
@@ -102,6 +102,11 @@
|
||||
- **Reasoning**: Real-time strategy execution requires different architecture than batch processing - event-driven triggers, background signal processing, throttled chart updates, and integration with existing dashboard refresh cycles.
|
||||
- **Impact**: Enables live strategy signal generation that integrates seamlessly with the existing chart system. Provides concurrent strategy execution, real-time signal storage, error handling with automatic strategy disabling, and performance monitoring for production use.
|
||||
|
||||
### 11. Exclusion of "HOLD" Signals from All Signal Storage
|
||||
- **Decision**: Modified signal storage mechanisms across both real-time and batch processing to exclude "HOLD" signals, only persisting explicit "BUY" or "SELL" signals in the database.
|
||||
- **Reasoning**: To significantly reduce data volume and improve storage/query performance across all execution types, as the absence of a BUY/SELL signal implicitly means "HOLD" and can be inferred during analysis or visualization.
|
||||
- **Impact**: Leads to more efficient database usage and faster data retrieval for all stored signals. Requires careful handling in visualization and backtesting components to correctly interpret gaps as "HOLD" periods.
|
||||
|
||||
## Tasks
|
||||
|
||||
- [x] 1.0 Core Strategy Foundation Setup
|
||||
|
||||
Reference in New Issue
Block a user