Millionaire Expert (save as EA)

to speed it up

f

now i feel there is no problems.

looping cancelation in progress (to increase speed by x factor that equal number of group element)
for example if you use 28 pairs, speed will be faster by 28x
instead of looping we will use sequential system, "in sequence" , each update one pair only.

therefore if you set expert timer at 1 sec, and all entry conditions are satisfied for all 28 pairs, you need 28 seconds for the first order of each pair.

then ITERATE button is recommended in this case.
we hit 10 birds using only one stone

do not forget, no hurry, the market will not fly or disappear, and 28 seconds is nothing compared to horizon trading time!! it is a matter of better thought



g

and that will lead to reduce dashboard update with each new orders also by another 28x factor

look, each 5 seconds, new order for the NEXT pair (sequential process)
slow orders(market will not fly), but expert is very speedy.

g

also in the main calling function there is no loop!
how this can be accomplished?
look at the picture!
looping without loop function "for" (advantage of MAHAL)

H

iP is zeroed , when it reachs to the last pair N
iP=-1,
then iP++ will make iP = 0,
The first pair #0 will be visited first

in next update iP++, point to pair#1, since iP =1

and so on

this post is actually for me and for programmers, not for traders, under the umbrella of our slogan "Market will not fly"

do you know why iP must be a global variable
iP: index of Pair

no for loop in main function
no for loop in branch function

the best thing that you can imagine, especially if you trade 100 pair!! will be similar to trading one pair, from speed viewpoint.

g

from now and on,
the csv input files will be renamed as the name of expert itself
for MAHAL, it will be mahal.csv
for this expert it will be grid.csv
all preceded by underscore _ then aa then underscore _, to make them on the top

_aa_mahal.csv
_aa_smart_grid.csv

This expert from this moment will be renamed _Axx_SMART_GRID.ex4

good by for old names
L

Guess what is the better solution for this latency?
any smart solution!
we want expert to correct itself if there is any latency, in next update!
==

the solution is to use GMT or LOCAL(your PC) TIMERS

Terminal timer during vacations stop update till next week open

for programmers:
magic solution
next you will find orders are paced by 10 seconds (assuming you use TradingTimer=10, and ExpertTimer=1),
and if there is anything wrong, it will be corrected for next orders

g

and some minor modifications to make things better -- less calling function.

f

الفستان زي ما تؤوول اتخلع لوحده ليلة الدخلة

smart solutions are smart
look orders paced by 10 seconds, no latency.
but if exists for any reason it will be corrected in next sequence
all orders end by 8

f

now is a check for why single order consume the complete 1 second?
what is the source that consume great part of this 1 second?
look at the picture:
visit in: 33:29
visit out: 34:31
duration: 1.02 second

g

Therefore, please be smart enough to set trading timer higher than the actual order duration,
give adequate breathe for expert. to achieve agility.
in picture any order functions (open + SL + TP consumes 1.02 seconds) --- then set TradingTimer at 2 seconds at least. yu will be happy--use red dipson buttons to show IN-OUT details in expert/journal.
1.02 for my PC, please discover your PC best timing design

g

this is my PC
your PC may be better or more worse

f