--- title: "Refactoring and Converting Existing Algorithms - Examples - MCP and AI - MetaEditor Help" description: "MQL4-to-MQL5 conversion: Indicator-handle migration: Matrix and vector conversion: Trace-locked architectural rewrite... - Refactoring and Converting Existing Algorithms - Examples - MCP and AI" image: "https://www.metatrader5.com/i/logo_metatrader5.png" url: "https://www.metatrader5.com/en/metaeditor/help/practical_examples/refactoring_converting_algorithms" --- [MetaEditor Help](https://www.metatrader5.com/en/metaeditor/help) → [MCP and AI](https://www.metatrader5.com/en/metaeditor/help/mcp_and_ai) → [Examples](https://www.metatrader5.com/en/metaeditor/help/mcp_and_ai/practical_examples) → Refactoring and Converting Existing Algorithms # Refactoring and Converting Existing Algorithms Using AI > Adapt file names, symbols, periods, risk limits, and requirements to your project or preferences. Preserve an unchanged baseline and test the algorithm in a demo environment before live use. > > You are solely responsible for AI-generated content, AI-assisted actions, trading decisions, trading results, and any resulting losses. MQL4-to-MQL5 conversion: Provide the MQL5 version of this MQL4 EA. Replicate the same exact logic and explain any case where you had to apply the closest equivalent. Fix all errors so that the MQL5 version works perfectly in MetaTrader 5. Indicator-handle migration: Replace repeated creation of one indicator type with a handle initialized once, read-only after BarsCalculated and CopyBuffer succeed, and released in OnDeinit. Compare its latest 200 signal timestamps with the baseline. Matrix and vector conversion: Create an experimental native matrix or vector version of this calculation. Check 1,000 fixed inputs for indexing, warm-up, missing-value, and numeric equivalence, then benchmark both versions three times and keep the clearer one unless the gain is material. Trace-locked architectural rewrite: Capture the first 100 consecutive decision events, or all available if fewer, from a historical test of this monolithic EA over the latest 500 H1 bars, including inputs, signal state, requests, transactions, and position changes. Use the trace as a behavioral contract while extracting only the signal and risk modules. Compare once, accept the refactor only if the trace and trade list remain identical, and otherwise report the first mismatch without iterating. Synchronous-to-event-driven execution: Convert this order path to OrderSendAsync with idempotent request IDs and explicit states for submission, acceptance, partial-fill, full-fill, rejection, and recovery. Verify five sequences. Normal fill, partial-fill, rejection, reordered transactions, and restart after acceptance. Never duplicate exposure. Python model to native ONNX inference: Convert this Python pipeline to ONNX backed MQL5 inference. Preserve feature order, scaling, missing-values, tensor names, shapes, types, and thresholds, then compare 10 fixed Python vectors with MQL5 outputs within a declared tolerance before exposing a trading signal. DLL removal and native replacement: Replace one DLL exported calculation with native MQL5 matrix, vector, file, or network facilities. Capture 20 normal, five boundary, and five invalid reference cases. Preserve numeric and error behavior, and report any part that lacks a safe native equivalent before migrating another function. Single-symbol to portfolio engine: Convert this single-chart EA into a portfolio engine for EURUSD, GBPUSD, and USDJPY without changing per-symbol rules. Isolate state, schedule updates fairly, normalize monetary risk, cap aggregate currency exposure, reconcile restarts, and prove that EURUSD only mode reproduces the original one-month trade list. Dual netting-and-hedging conversion: Make this hedging only EA support netting accounts while preserving virtual leg attribution. Verify five cases, entry, scale in, partial close, reversal, and manual position change, and define how per leg stops combine into one net position. Behavior-preserving refactor: Run a one-month EURUSD H1 baseline for LegacyEA.mq5, then refactor duplicated signal, sizing, and order code one-component at a time. Stop at the first difference in trade time, price, volume, or final balance. Adding a feature safely: Add the requested session filter behind a disabled-by-default input. On a two week EURUSD H1 test, require disabled mode to reproduce the baseline exactly. In enabled mode, log each filtered signal and reason. Paste requirements. Automatic documentation: Document the main program and up to eight directly referenced files without changing executable statements. Add only contract and invariant comments, then create a concise README covering architecture, inputs, setup, test reproduction, limitations, and account assumptions. ## In this section - [Creating Automated Strategies and Trading Tools](https://www.metatrader5.com/en/metaeditor/help/practical_examples/creating_automated_strategies) - [Deploying Expert Advisors, Indicators, and Scripts](https://www.metatrader5.com/en/metaeditor/help/practical_examples/deploying_programs) - [Researching and Analyzing Trading Algorithms](https://www.metatrader5.com/en/metaeditor/help/practical_examples/researching_algorithms) - Refactoring and Converting Existing Algorithms - [Building Multi Timeframe Automated Strategies](https://www.metatrader5.com/en/metaeditor/help/practical_examples/multi_timeframe_strategies) - [Generating Boilerplate Code and Frameworks](https://www.metatrader5.com/en/metaeditor/help/practical_examples/generating_boilerplate) - [Debugging and Auditing Trading Algorithms](https://www.metatrader5.com/en/metaeditor/help/practical_examples/debugging_auditing_algorithms) - [Optimizing Algorithms for Performance and Speed](https://www.metatrader5.com/en/metaeditor/help/practical_examples/optimizing_performance) - [Using Self-Improvement Loops for Algorithms](https://www.metatrader5.com/en/metaeditor/help/practical_examples/self_improvement_loops) ```json {"@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ {"@type": "ListItem", "position": 1, "item": {"@id": "https://www.metatrader5.com/en/metaeditor/help", "name": "MetaEditor Help"}}, {"@type": "ListItem", "position": 2, "item": {"@id": "https://www.metatrader5.com/en/metaeditor/help/mcp_and_ai", "name": "MCP and AI"}}, {"@type": "ListItem", "position": 3, "item": {"@id": "https://www.metatrader5.com/en/metaeditor/help/mcp_and_ai/practical_examples", "name": "Examples"}}, {"@type": "ListItem", "position": 4, "item": {"@id": "https://www.metatrader5.com/en/metaeditor/help/practical_examples/refactoring_converting_algorithms", "name": "Refactoring and Converting Existing Algorithms"}} ]} { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "MetaTrader 5: Refactoring and Converting Existing Algorithms", "acceptedAnswer": { "@type": "Answer", "text": "MQL4-to-MQL5 conversion: Indicator-handle migration: Matrix and vector conversion: Trace-locked architectural rewrite: Synchronous-to-event-driven..." } }] } ```