darashikoh/mql5
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Commit graph

  • d0c861b744 feat(ERMT PME v2.1): Add optional bar-counting entry system for backtesting ERMT_6.8 darashikoh 2026-02-01 11:52:53 +00:00
  • 5a3b8a13fd Based on the work we just completed on the contrarian M5 optimization, here's an appropriate commit message: darashikoh 2026-02-01 11:24:52 +00:00
  • 6aa699022d feat: ERMT PME v2.1 - Contrarian Entry Optimization with Graduated Protection Basma Qazi Chaudhry 2026-01-31 14:02:30 +00:00
  • 2b23261c88 darashikoh 2026-01-31 12:29:07 +00:00
  • f5de41d739 Fix v1.3 partial closures integration and streamline dashboard darashikoh 2025-12-04 12:00:09 +00:00
  • 51b8b942b1 feat: Implement ERMT PME v1.3 - Complete Three-Solution Optimization darashikoh 2025-12-03 15:22:48 +00:00
  • cea5a4e393 ERMT 1.2-> 1.3: Solution 1: Phase locks guarantee minimum profit for highest phase achieved. Adaptive trailing manages dynamic protection above that floor. Partial closures realize profits progressively. Together, they work in harmony instead of conflict. darashikoh 2025-12-03 13:57:36 +00:00
  • 0181be03c9 darashikoh 2025-11-19 11:20:38 +00:00
  • 300ca310db Refactor code structure for improved readability and maintainability; removed redundant code blocks and optimized functions. darashikoh 2025-11-18 10:37:19 +00:00
  • 945312b13e Add new optimization profiles for ERMT_7.1_ERMT-ML on EURUSD M5 darashikoh 2025-11-13 07:52:49 +00:00
  • efd4c0e156 Analysis: Let me chronologically analyze this conversation to capture all technical details, code patterns, and architectural decisions. darashikoh 2025-11-11 17:23:18 +00:00
  • d1349ddad8 Finished ERmt_7.1_ML debug and initialisation Created mql5 project knowledge darashikoh 2025-10-29 13:34:40 +00:00
  • 14165aac8c ERMT 7.1 (ERMT‑ML): add Entry‑Only mode, harden compilation on macOS/Wine, fix datatype order, and clean includes darashikoh 2025-10-28 23:35:47 +00:00
  • d12bddd4df High-level summary TechnicalAnalysis_PME_Fixed.mqh (call it "Fixed") is oriented toward robust ATR handling and keeps indicator handles as class members with create/release helpers. It contains fallback logic for ATR creation and a manual ATR calculation if indicator creation fails. TechnicalAnalysis_PME_Optimised.mqh (call it "Optimised") provides a richer set of analysis methods (advanced exit checks, divergence, ADX trend strength, MACD retrieval, volatility ratio) and more conservative/confirmed exit logic. It is more feature-rich for exit decision-making but uses simpler ATR handling (no manual fallback) and often creates temporary indicator handles in getters. File / header differences Fixed header: "Fixed Version with Proper ATR Handling". Optimised header: "Optimized Technical Analysis for PME (v1.1) — [FIXED: Premature Exit Signals]". Optimised defines a local enum ENUM_SIGNAL_TYPE (includes SIGNAL_EXIT); Fixed relies on similar enums but the file you provided doesn't show a local definition for ENUM_SIGNAL_TYPE — the Fixed class uses ENUM_SIGNAL_TYPE and ENUM_MARKET_CONDITION in its API (assumed defined in included headers). Class design and indicator handle management Fixed: Class members: m_atr_handle, m_ma_handle, m_rsi_handle, m_sar_handle, m_macd_handle, m_bb_handle. Has CreateIndicators() and ReleaseIndicators() helper methods to create and clean up member indicator handles. Initialize() calls CreateIndicators() and returns true (even if some indicators fail). It logs warnings and does not fail initialization on missing indicators. GetATR prefers the member m_atr_handle when symbol == _Symbol, otherwise creates a temporary handle; if indicators fail, it contains a manual ATR calculation fallback (averaging TR). Optimised: Class members: same set, initialized in Initialize, released in destructor. Initialize() creates the indicators directly (no separate CreateIndicators function). It returns success boolean only if essential indicators were created (checks m_atr_handle, m_ma_handle, m_rsi_handle). GetATR creates a temporary handle every time (iATR(symbol,...)), copies the buffer and releases the handle — no manual ATR fallback. Destructor explicitly releases any member indicator handles. Implication: Fixed is more defensive about indicator creation and provides fallback ATR computation for resilience on limited indicator support or resource errors. Optimised is simpler/leaner but will return 0 if ATR creation fails (no manual fallback). darashikoh 2025-10-28 13:59:12 +00:00
  • 4ec6b0ddc7 Summary - ATR Indicator Error 4302 Fixed Problem The EA was failing to initialize because the ATR indicator couldn't be created (error 4302), which occurs when: Not enough historical bars are loaded on the chart Chart data isn't ready when EA initializes Solution Applied 1. Enhanced error handling in TechnicalAnalysis module (TechnicalAnalysis_PME_Optimised.mqh:81-155): Added bar count check before creating indicators Individual error logging for each indicator with error codes Non-fatal initialization - returns success if core indicators load 2. Made Technical Analysis initialization non-fatal (ERMT_PME_1.2.mq5:432-440): EA continues even if indicators fail initially Logs warning instead of aborting Position management can work without technical indicators Expected Behavior Now When you attach the EA: If insufficient data: You'll see a WARNING message but EA will continue Indicators will be created on first successful data load EA remains functional for position management Detailed error darashikoh 2025-10-28 10:47:19 +00:00
  • 9f9dc62d16 Phase Management Integration - Complete Documentation Overview The ERMT_PME EA now has a fully integrated phase-based profit management system that adapts position management strategies based on profit levels. The system is modular and follows MQL5 best practices. Modular Architecture ERMT_PME_1.1.mq5 (Main EA) ├── DataTypes_PME.mqh (Base structures & enums) ├── Utilities_PME.mqh (Logging & utilities) ├── RiskManager_PME.mqh (Risk management) ├── TechnicalAnalysis_PME_Optimised.mqh (Market analysis) ├── PositionManager_PME_Complete.mqh (Position management) └── ProfitMaximizer_PME.mqh (Phase-based profit optimization) ← NEW Phase System Definition The system uses 6 distinct profit phases defined in ProfitMaximizer_PME.mqh:49-57: enum ENUM_PROFIT_PHASE { PHASE_INITIAL, // 0 - Early position development PHASE_PROTECTION, // 1 - Basic protection phase (40+ points) PHASE_ACCUMULATION, // 2 - Profit building phase (60+ points) PHASE_MAXIMIZATION, // 3 - Adv darashikoh 2025-10-27 23:36:10 +00:00
  • 41ef4f9808 Integrate Phase-Based Profit Maximization into ERMT_PME_1.0 >1.1 - Debug complete darashikoh 2025-10-27 23:16:57 +00:00
  • fe3ef20878 Integrate Phase-Based Profit Maximization into ERMT_PME_1.0 darashikoh 2025-10-27 20:24:20 +00:00
  • d1f4e8650f Profit maximisation update darashikoh 2025-10-27 18:54:25 +00:00
  • 07813ab51c ERMT_PME 1.0 and 2.0 to run simultaneously via updated Utlities_PME.mqh and creating instances PME1 and PME2. darashikoh 2025-10-09 12:09:59 +01:00
  • d26f4b72d3 ERMT_PME_2.0 Optimisation for M5 contrarian - Removed hardcoded disaster stop and made it configurable as contrarian signals were getting stopped out early darashikoh 2025-10-09 09:53:03 +01:00
  • f056e779bd darashikoh 2025-10-06 14:47:18 +01:00
  • 9e01e715b3 ERMT_PME 2.0 Optimised for Contrarian Profit Max - Debugged darashikoh 2025-10-06 14:46:38 +01:00
  • 5c73ff6fc6 ERMT_PME 2.0 - Optimised Profit Maximisation for Contrarian M5/M7/M9 darashikoh 2025-10-06 12:16:00 +01:00
  • cddf8b5a4c darashikoh 2025-10-03 10:03:10 +01:00
  • c2626acdfa darashikoh 2025-09-29 12:27:03 +01:00
  • 6e35c52728 darashikoh 2025-09-29 12:26:45 +01:00
  • 017ce2ff6e ERMT_PME - fully compiled darashikoh 2025-09-29 12:26:22 +01:00
  • 6bee286b93 main darashikoh 2025-09-23 11:34:40 +01:00
  • 0c08a0963b Delete experts (2).dat darashikoh 2025-09-23 10:29:07 +00:00
  • c9fe7020b8 Delete experts (1).dat darashikoh 2025-09-23 10:29:00 +00:00
  • 876c45ee28 Delete Profiles/Charts/Default/chart01.chr darashikoh 2025-09-23 09:26:46 +00:00
  • 35a84d589d Delete experts.dat darashikoh 2025-09-22 19:16:54 +00:00
  • 9492f99906 Delete experts (2).dat darashikoh 2025-09-22 19:16:48 +00:00
  • dfb8fbc376 Delete experts (1).dat darashikoh 2025-09-22 19:16:43 +00:00
  • 6a5877927f ERMT PME v1.0 - Quick Fix Guide Fixed Compilation Errors Error 1: Mismatched #ifdef/#endif pair in RiskManager_PME.mqh Problem: Missing closing #endif and required includes Solution: Created RiskManager_PME_Fixed.mqh with: darashikoh 2025-09-22 15:09:42 +01:00
  • 33f9bb20eb New ERMT: darashikoh 2025-09-22 13:24:18 +01:00
  • e3a22f4a97 darashikoh 2025-09-22 12:39:17 +01:00
  • 1ed8cf3d51 darashikoh 2025-09-22 12:39:05 +01:00
  • 848116acb9 Moved all previous ERMTs, with internal and limited external trade opening and management, to 'Previous' Folder darashikoh 2025-09-22 12:38:24 +01:00
  • ee2f97a700 darashikoh 2025-09-05 18:18:59 +01:00
  • f388e35a62 ERMT_6.8 - attempt to define dashboard darashikoh 2025-09-05 18:17:25 +01:00
  • 2866994557 Merge commit from 'origin' darashikoh 2025-09-05 10:15:01 +01:00
  • a3154f398c ✅ ExternalTradeManager.mqh - FINAL VERSION (just fixed) ERMT_7x darashikoh 2025-09-04 16:10:10 +00:00
  • 6f8c06a4d4 Dashboard colour as input darashikoh 2025-08-28 12:15:26 +01:00
  • 74a75d3681 revert 06e7431edc darashikoh 2025-09-02 09:20:47 +00:00
  • 443ce2d4f2 ERMT_6.9 Compilaton Errors part 1 - complete ERMT_6.9x darashikoh 2025-09-01 16:55:52 +01:00
  • bdca805d54 Two ERMTs, 6.8 original with 6.9 Dual Dash darashikoh 2025-08-29 19:26:00 +01:00
  • fd4ce1a083 EntrySystem v3.0 - Optimized & Future-Proofed I've completely rebuilt the EntrySystem with the following improvements: Architecture Enhancements: darashikoh 2025-08-29 12:50:38 +01:00
  • 6c32c0bae3 Both dashboards running simultaneously Original dashboard on left (X=20) New self-contained dashboard on right (X=350) Complete trading logic preserved darashikoh 2025-08-29 12:47:50 +01:00
  • 722baf8db9 Complete ERMT 6.9_DD with Dual Dashboard Support I've created the complete ERMT 6.9 system with both dashboards fully integrated for side-by-side testing: What's Included: darashikoh 2025-08-29 11:26:14 +01:00
  • 06e7431edc Dashboard colour as input darashikoh 2025-08-28 12:15:26 +01:00
  • 1b2b21dc59 ✅ ExternalTradeManager.mqh - FINAL VERSION (just fixed) The version I just provided fixes ALL the compilation errors: darashikoh 2025-08-27 21:53:01 +01:00
  • a2ae9dd5b6 Main Changes: darashikoh 2025-08-27 19:51:34 +01:00
  • a673c29a5a 1. TechnicalAnalysis.mqh - Complete Technical Analysis Module Key Features: darashikoh 2025-08-27 17:49:01 +01:00
  • 17bacd0374 1. Complete RiskManager.mqh A fully featured risk management module including: darashikoh 2025-08-27 16:59:00 +01:00
  • 63fab7676b The complete Utilities.mqh now includes all the missing implementations: darashikoh 2025-08-27 16:22:33 +01:00
  • 0404c71a35 3. Utilities.mqh - Remove Duplicates & Add Missing Members darashikoh 2025-08-27 15:53:29 +01:00
  • 493d01fe6d 2. ExternalTradeManager.mqh - Remove Duplicate Enum darashikoh 2025-08-27 15:49:38 +01:00
  • 2df3d42041 DataTypes.mqh - Complete Enums and Structures darashikoh 2025-08-27 15:48:27 +01:00
  • 0fb1bd1b0a Module Integration Summary for External Trade Management Overview To fully integrate the enhanced external trade management system, updates are required to 5 out of 7 existing modules. The updates maintain backward compatibility while adding new functionality for external trade handling. Module Update Requirements 🟢 No Updates Required (2 modules) darashikoh 2025-08-27 14:21:02 +01:00
  • 158a4f2d51 Key Improvements Made: 1. Proper Module Encapsulation * All risk management functions are now properly encapsulated within the CRiskManager class * Functions like ValidateAndAdjustRisk, CalculateTradeRisk, and NormalizeLotSize are now class methods 2. Consistent Method Calls * All risk management operations use the (*RiskMgr).MethodName() pattern * No more mixed standalone functions and class methods 3. Enhanced Risk Manager Features * Kelly Criterion implementation for optimal position sizing * Daily drawdown tracking and limits * Market condition-based risk adjustment * Performance metrics tracking for adaptive risk management 4. Fixed Compilation Issues * Resolved all function call errors * Added copy constructor to EntrySignal to fix deprecation warning * Proper parameter passing between modules Benefits of This Architecture: 1. Maintainability: All risk logic is in one place - the RiskManager module 2. Testability: Each module can be tested i darashikoh 2025-08-22 17:47:03 +01:00
  • 3f34c8cde5 new files added darashikoh 2025-08-22 17:46:10 +01:00
  • 4951f74957 Recompile and re-debug of ERMT_6.6; the last functional EA for external management darashikoh 2025-08-20 12:53:47 +01:00
  • 5dce04606c new files added darashikoh 2025-08-20 10:52:10 +01:00
  • 050880d47e Merge commit from 'origin' darashikoh 2025-08-19 18:36:58 +01:00
  • 8b1ff58567 Commit from local main repo as cannot checkout due to some unsaved version - which ones is unclear darashikoh 2025-08-19 18:36:26 +01:00
  • ad5ddad485 Merge pull request 'WIP-ERMT-Recovery of lost files - 18082025' (#1) from ERMT-ML into main darashikoh 2025-08-19 17:28:48 +00:00
  • a559f7ae04 Update Experts/Advisors/ERMT_7.1_ERMT-ML.mq5 darashikoh 2025-08-19 17:16:43 +00:00
  • 7caa89db31 Update Experts/Advisors/ERMT_7.1_main.mq5 darashikoh 2025-08-19 17:16:02 +00:00
  • ff69c0f3ad darashikoh 2025-08-15 23:05:57 +01:00
  • 19493874a2 darashikoh 2025-08-15 14:56:24 +01:00
  • 9c05f130ea new files added darashikoh 2025-08-15 14:53:55 +01:00
  • 4e7d1b3bb6 darashikoh 2025-08-15 13:14:24 +01:00
  • c7a617709f Resolution of git index lock due to VS Code repo editing darashikoh 2025-08-13 01:34:23 +01:00
  • d6eccab613 Resolution of git index lock from VS Code darashikoh 2025-08-13 01:33:37 +01:00
  • d346ae6a94 darashikoh 2025-08-08 20:32:34 +01:00
  • 39c0d6785c 1. Ultra-Low Latency Processing darashikoh 2025-08-08 11:05:06 +01:00
  • 926b6c195a darashikoh 2025-08-05 13:20:50 +01:00
  • 9f3303dbc2 Major Fixes Implemented: 1. Multi-Symbol Detection Fixed darashikoh 2025-08-04 22:50:57 +01:00
  • 2a617b1dab darashikoh 2025-08-01 11:25:48 +01:00
  • f14cb7649f Rename to v7.0 darashikoh 2025-08-01 11:25:16 +01:00
  • 9b1c52209b BRANCH ERMT v7 Enhanced Dashboard, MultiTrade Reporter, External Trade management M1-4 compile and debug darashikoh 2025-08-01 11:13:35 +01:00
  • 9afaf5efaf Summary I've provided you with a comprehensive solution for managing your commercial EA trades using the Risk Management Overlay EA, despite MT5's one-EA-per-chart limitation: 1. Complete Management Guide darashikoh 2025-08-01 10:56:06 +01:00
  • 56a1014695 Established enhanced dashboard and advanced reporting for external trades darashikoh 2025-07-31 19:52:26 +01:00
  • 82c958b8a4 ERMT_v6.6 darashikoh 2025-07-30 20:50:27 +01:00
  • 56209c4d63 Summary of Fixes The "Stop distance must be greater than 0" error is caused by a chain of issues in the ATR calculation. Here's what you need to do: 1. Replace the GetValidATR function in EntrySystem.mqh The original code had a recursive call bug. Replace the entire EntrySystem.mqh file with the fixed version I provided above. 2. Update the GetATR method in TechnicalAnalysis.mqh Replace the GetATR method with the fixed version that includes fallback calculations. 3. Update the AnalyzeMarket method in TechnicalAnalysis.mqh Replace the AnalyzeMarket method with the enhanced version that ensures volatility is always valid. 4. Update the main EA file (ERMT_6.0.mq5) Replace the CheckEntrySignals() and UpdateMarketConditions() functions with the enhanced versions that include debugging and validation. Key Changes Made: darashikoh 2025-07-30 19:33:01 +01:00
  • 44f028731b Summary The "Stop distance must be greater than 0" error was caused by: darashikoh 2025-07-30 18:55:56 +01:00
  • bd30cf417a The Problem: In MT5's Strategy Tester environment, file operations are restricted for security reasons. The backtest runs in a sandboxed environment where file creation/writing may be blocked or redirected to a different location. darashikoh 2025-07-30 14:26:35 +01:00
  • 3295dab1db Summary of Changes to Fix Zero Stop Distance Error The error "Invalid stop distance: 0.0" was occurring because the entry signals were being generated with invalid (zero) stop distances. This happened when the market volatility (ATR) value was 0 or not properly calculated. Key Changes Made (Version 6.5.1): darashikoh 2025-07-30 13:32:29 +01:00
  • 32998d8c9a What Was Wrong: darashikoh 2025-07-28 18:23:20 +01:00
  • a74c45d240 Summary of Fixes I've identified and fixed the lot size calculation issue. The problem was in the formula used to calculate lot size from risk amount. Here's what was wrong and how it's fixed: The Problem The original calculation was producing lot sizes that were off by a factor of 100,000 (e.g., 1,315,295 lots instead of ~13 lots). This was due to an incorrect formula that wasn't properly using the tick value and tick size. The Solution The corrected formula now: darashikoh 2025-07-23 23:46:39 +01:00
  • 3ae0f49654 The issue is in the lot size calculation in RiskManager.mqh. The calculation is producing an extremely large value (860,373 lots!) when it should be much smaller. darashikoh 2025-07-22 18:24:37 +01:00
  • 53c5b161e5 fix: resolve pointer syntax errors and missing return statements darashikoh 2025-07-22 18:11:53 +01:00
  • ffae6bf4ff Fix: Resolve backtesting trade execution issues Problem: EA was not opening trades during backtesting due to overly restrictive spread validation and position sizing calculation failures. Changes Made: 1. EntrySystem.mqh - Improved Signal Validation darashikoh 2025-07-22 17:33:44 +01:00
  • cd2696ae28 fix: resolve invalid pointer access error in EA initialization darashikoh 2025-07-22 17:07:29 +01:00
  • b801040daf Risk Management Overlay EA v6.0 - Code Review and Fix Guide Critical Issues Found 1. Main EA File (ERMT_6.0.mq5) Missing Definitions: darashikoh 2025-07-22 16:37:29 +01:00
  • 32705c5d61 1 - Backtest for 1.5 years EURUSD M5 - no trades initia; Critical error on exitlised 2- Compile and debug - Critical error on exit - OnDeinit 3- Fix for Entry System - Add to OnTick(): 4 - ENUM_TECHNICAL_LEVEL enum in DataTypes.mqh -> other Enums and structures DataTypes.mqh v3 The Complete DataTypes Module provides the robust foundation needed for your institutional-grade risk management system, offering better trade tracking, risk analysis, and technical integration capabilities essential for professional algorithmic trading. darashikoh 2025-07-20 22:38:24 +01:00
  • 644016f8e2 Moved ERMT_6.0, post first compile and debug to Advisors folder darashikoh 2025-07-20 19:23:58 +01:00
  • fb5ce9481d Added v2.0 in the header to reflect function change from Compile 1 Debug darashikoh 2025-07-20 17:37:34 +01:00