Forum Replies Created
MQL4 template has this default settings of retries:
int retry_attempts = 10000; // general retry attempts
int retry_attempts_bad_price = 3; // retry attempts if the error is bad price
double sleep_time = 2.0;
double sleep_maximum = 20.0;
if you want to edit these values, you need to change it in the MQL template or right in the MQL code
<p style=”text-align: left;”>https://strategyquant.com/doc/strategy-style/
honestly i dont trust MT5 MQL code as it is now in B124…
why would i need MT5 backtester, when i have SQX?
is anyone here using MT5 and know that strategies are trading the same way as in backtest?
- This reply was modified 4 days, 19 hours ago by hankeys.
what is constistency?
you will have loosing days, you will have loosing months and you could also have loosing years…
behind the profits lies very hard work, its not a question of a click of a BUTTON
i suggest that devteam will hide the “strategy config” and “pseudo code” bookmarks, because they are not true if we merge the portfolio
and it will be much better, that merged portfolios will be added to another databank, like “portfolios” – same behavior that QA has
because have strategies and portfolios in one databank is not user friendly
no, its not…its confusing, but the pseudo code as you can see is the code of the first strategy in portfolio
when a portfolio master will be added to SQX, are there any plans?
or you can go to USER – PROJECTS directory, where is everything saved also
i think you could be good with 32 GB RAM, i have 128 but this was need for the old SQ…the new SQX is not so much RAM consuming
making 1000 iterations on MC test change params is waste of time by my opinion
also MC test spread and slippage, there you could very well live with 20 iterations only, because the range of values is not huge…its nonsense to make 200 iterationg for slippage 1-5 for example
it could depend on what MC test you are doing – for example MC RANDOMIZE TRADES EXACT, there is endless combinations, and you can make this test repeatedly and you will come to a point, that no strategy will left you
its only probabilistic methods with some value of confidence
on the other side – MC test change parameters, where you set the probability and max change – so you are limiting the range where the MC tests will be done
my approach is different – i dont like BIG basic packs of strategies generated with the same settings…
i am using for now custom projects where i run all tasks together and work only with a “final” strategies
for MC tests i am using 200 iterations
very good question…
did you already made some not so time consuming tests – like higher/lower TF, another market, etc.
because running MC tests on 10000 strs is not reasonable
how did you get those strategies, did you try another settings, or this is only one setting at all?
did you have only test on all EURUSD data?