WIP: 6+ weeks of uncommitted EA development and preset tuning
Confluence EA (v1.16 → v1.20): - Per-EA realized P&L tracking via history deals - Weekly drawdown protection - Warmup bars, pivot cache, state persistence - Point-scaled pivot thresholds, ranging ATR factor - Market filling mode helper per symbol Grid EA (v3.1 → v4.1): - Adaptive filters, adaptive entry, spread filter - Session filter, breakeven, correlation caps, range drift - Profit protection (stop-after-profit, cycle reports) - Edge cleanup v5.0 — close wrong-side positions outside grid - Master one-shot shutdown, grid state persistence Presets: - Fix GetOut=Y shutdown bug on 4 grid presets - Relax ADXMax 18→40, widen RSI 20/80 across grid presets - Standardize daily drawdown 3%→5%, add weekly 10% - Increase grid lots 0.01→0.03 - Normalize confluence ATR thresholds per pair - Add XAGUSD, EURCHF, EURGBP, AUDNZD presets Docs & DevOps: - April 23 audit files (preset mismatch, code review, checklist) - n8n workflow and validation infrastructure updates - AI agent analyses in notes/ Known issues carried forward: - Shared drawdown budget contamination (both EAs) - Confluence ranging-market threshold inversion - Older grid presets missing v4.1 safety controls
This commit is contained in:
@@ -0,0 +1,81 @@
|
||||
# 2026-04-23 OrdersEA Smart Grid - Live Preset Comparison
|
||||
|
||||
Compared repo grid preset files against the live MT5 preset files under:
|
||||
|
||||
`~/mt5-docker/config/.wine/drive_c/Program Files/MetaTrader 5/MQL5/Presets/`
|
||||
|
||||
## Scope
|
||||
|
||||
Compared these pairs:
|
||||
- `grid-eurusd.set`
|
||||
- `grid-usdjpy.set`
|
||||
- `grid-gbpusd.set`
|
||||
- `grid-gbpjpy.set`
|
||||
- `grid-xauusd.set`
|
||||
- `grid-audusd.set`
|
||||
- `grid-usdcad.set`
|
||||
- `grid-usdchf.set`
|
||||
- `grid-nzdusd.set`
|
||||
- `grid-eurjpy.set`
|
||||
- `grid-eurgbp.set`
|
||||
- `grid-eurchf.set`
|
||||
- `grid-audnzd.set`
|
||||
|
||||
Checked the settings that materially affect runtime behavior:
|
||||
- `MagicNum`
|
||||
- `GetOut`
|
||||
- `OpenNewTrades`
|
||||
- `InpUseSessionFilter`
|
||||
- `InpSessionStartHour`
|
||||
- `InpSessionEndHour`
|
||||
- `InpUseBreakeven`
|
||||
- `InpMaxSpreadPoints`
|
||||
- `InpMaxLongSymbols`
|
||||
- `InpMaxShortSymbols`
|
||||
- `InpAdaptiveEntry`
|
||||
- `InpRelaxFilterAfterDays`
|
||||
- `InpRangeDriftEnable`
|
||||
- `InpUseStopLoss`
|
||||
- `StopLoss`
|
||||
- `InpMaxDailyDrawdown`
|
||||
- `InpMaxWeeklyDrawdown`
|
||||
- `BaseEquity`
|
||||
|
||||
## Result
|
||||
|
||||
The live MT5 preset files match the repo presets for all reviewed pairs and tracked fields.
|
||||
|
||||
There is no repo-vs-live drift in the preset files themselves.
|
||||
|
||||
## Important Implication
|
||||
|
||||
This confirms that the preset-file issues already identified are also present in the live preset files:
|
||||
|
||||
- `GetOut=Y` is present in live `grid-usdjpy.set`
|
||||
- `GetOut=Y` is present in live `grid-gbpusd.set`
|
||||
- `GetOut=Y` is present in live `grid-gbpjpy.set`
|
||||
- `GetOut=Y` is present in live `grid-xauusd.set`
|
||||
|
||||
The older live presets also still omit many newer v4.1 controls, including:
|
||||
- explicit session filter settings
|
||||
- explicit spread caps
|
||||
- explicit breakeven settings
|
||||
- explicit correlation caps
|
||||
- explicit adaptive relaxation settings
|
||||
|
||||
The newer live presets (`grid-eurgbp.set`, `grid-eurchf.set`, `grid-audnzd.set`) do include those newer controls.
|
||||
|
||||
## Limitation
|
||||
|
||||
This comparison only proves that the preset files on disk match the repo.
|
||||
|
||||
It does **not** prove:
|
||||
- that each MT5 chart has reloaded the latest preset
|
||||
- that each chart is attached to the intended preset
|
||||
- that the running chart state matches the preset file currently on disk
|
||||
|
||||
## Next Verification Options
|
||||
|
||||
1. Inspect MT5 logs to infer the settings each live chart actually initialized with.
|
||||
2. Compare chart-by-chart loaded values inside MT5 terminal properties.
|
||||
3. Normalize the obvious preset issues first, then reload charts and verify again.
|
||||
Reference in New Issue
Block a user