Debug EA - Results on visual and non-visual backtests are not the same MT5

MQL5 Indicadores Asesores Expertos

Trabajo finalizado

Plazo de ejecución 1 día
Comentario del Cliente
Amazing developer! Very knowledgeable, debugged everything with ease! Highly recommended
Comentario del Ejecutor
Great customer, knew what he needed exactly and was spot on finding the last bugs!

Tarea técnica

Dear Developers,

I'm looking for someone experienced on both MQL5 and MT5 backtests, knows the ins and outs of backtesting an EA, how multi time frame backtesting works, how indicators interfere, the importance of data and etc.

I had an EA developed and everything seemed to work fine but I eventually realised that the visual backtest is giving different results from non visual (which is what i was using for most of my initial testing) - I have been trying but cannot reach the original developer of the project so I am looking for someone to help me with this debugging. It seems like the visual mode misses a lot of trades it should take and are not missed by non visual (i know, very weird) - problem is i do not know how the EA would behave live, if it would work like visual or non visual, hence the need to fix it.

The indicators that are connected to the EA all work fine on visual backtest, and the MT5 visual backtest for indicators match exactly as if i am plotting it on the chart. Now, there are functions within the EA that could be causing this issue somehow, like ADR calculation (which is used a lot on this EA for entries, add trades and exits) - ADR (average daily range) calculation knowledge is also needed. I don't want to waste time with inexperienced coders that i will have to explain what is ADR, how it is calculated etc..

My suggestion is to add a piece of code to the EA that will write to a csv file the value data for each of the indicators being used on each candle, as well as ADR, and some distances it has to calculate.... So we can compare the file generated by visual and non visual backtest and figure out where the issue is happening...

In addition to identifying where the issue is happening we need to go ahead and fix it after identifying.... Currently the EA has a dashboard that shows some information, I want to add adr spacing since last trade (that will help us identify potential issues)

Other than that, a couple of functions that were initially thought about ended up not being used / working as expected and i would like to remove them so we don't have unnecessary stuff there.

I will make a video showing the logic of the EA, the issue with backtesting and give you set file to replicate my problem exactly. I will also guide you to what info we want to have on the CSV files as well as to what we can remove from the EA.

Please let me know if you have any questions.
 


Han respondido

1
Desarrollador 1
Evaluación
(258)
Proyectos
265
29%
Arbitraje
0
Caducado
3
1%
Libre
Ha publicado: 2 ejemplos
2
Desarrollador 2
Evaluación
(57)
Proyectos
72
22%
Arbitraje
13
46% / 15%
Caducado
5
7%
Libre
3
Desarrollador 3
Evaluación
(27)
Proyectos
43
7%
Arbitraje
18
6% / 78%
Caducado
26
60%
Libre
4
Desarrollador 4
Evaluación
(41)
Proyectos
46
28%
Arbitraje
9
0% / 100%
Caducado
7
15%
Libre
5
Desarrollador 5
Evaluación
(27)
Proyectos
36
72%
Arbitraje
1
0% / 0%
Caducado
2
6%
Libre
Ha publicado: 2 artículos, 12 ejemplos
Solicitudes similares
Project Overview I am looking for an experienced MQL4/MQL5 developer to create an Expert Advisor (EA) for MetaTrader 4 and MetaTrader 5 based on a Moving Average High/Low channel and Bollinger Bands strategy. The EA must support both BUY and SELL operations and use opposite signal exits. Indicators Required 1. Moving Average High Period: 5 Applied to: High Price Method: Simple Moving Average (SMA) User configurable
Joseph 30+ USD
I want robot to make money for me because the straight trading it doesn't make better money and the account shows me a R0 I don't know why but I want to make money
Test instructions: - Run EA on US30 (Dow Jones) - Timeframe: H1 - Test period: last 3–6 months - Use default risk settings (1% per setup) - Check Friday breakout logic only Expected behavior: - EA should mark Friday High/Low - Wait for candle close breakout - Wait for retracement into range - Enter only when H1 candle closes inside range - Execute 2 trades per setup (TP1 = 1R, TP2 = 2R) - Respect 1.5% daily loss
I need help configuring my Sierra charts to run real time data, at the moment it’s running delayed data even though I have the proper subscriptions in place. I am at a last resort effort now where I want to get this problem solved efficiently. And build indicators. I need to find someone with flawless years of experience with Sierra who can accurately guide me and help me trouble shoot
ART 1: NUMBER OF TRADES ALLOWED IN ONE DIRECTION: Maximum number of trades in one direction = ------------------------------ ------------------------------ ------------------------------ -------------- par PART 2 PARTIAL CLOSURE OF STOPLOSS: Total STOPLOSS =------ Pips 1a: Percentage of Stoploss =--% 1b Percentage of Lot size =--% 2a: Percentage oe of Lot size =--% f Stoploss =--% 2b
MT5 Expert Advisor (EA) Acquisition Request – Proven XAUUSD Martingale / Grid EA I am looking to purchase a fully developed, actively traded, and proven MT5 Expert Advisor for XAUUSD (Gold) that uses Martingale, Grid, Averaging, Recovery, or Hybrid Recovery techniques. Mandatory Verification Requirement To be considered, please provide: - MT5 Investor Password (Read-Only Access) for verification - Account Number /
I'm looking to connect with an experienced MT5 developer who has previously built or worked on advanced trade copier systems beyond standard master-slave copying. Requirements: • Strong MT5 and MQL5 experience • Experience developing trade copiers • Familiarity with manual trade replication concepts • Knowledge of MT5 terminal architecture and execution workflows • Experience integrating MT5 with external
Hello, I have two Expert Advisors (EAs) that I'm migrating to my MQL5 VPS. I need a program that I can run on a separate chart or other interface to: - Allow EA #2 (with the magic number) to trade only during the Asian session. Therefore, EA #2 needs to be blocked during all other sessions. - Allow EA #1 to trade without restriction. Thank you
Labouchere System has many series and can transfer the Units to any other Series when needed (this function is very important). Building a dedicated SeriesManager class to handle all eight arrays would be very useful to make the unit transfers "atomic," so the logic is bulletproof and we never have to worry about data errors during the series transitions. The coders who really knows this cancellation sytem can apply
Project Overview I need an MQL5 developer to review and confirm their understanding of this project before providing a quote. Objective: Backtest an Opening Range Breakout (ORB) strategy on NAS100USD and generate detailed trade documentation. Requirements: Instrument NAS100USD only. Backtesting Run the ORB strategy on historical data. Target a minimum of 200 trades if the available data allows. Advise how much

Información sobre el proyecto

Presupuesto
50 - 120 USD