[ARCHIVE!] Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Can't go anywhere without you - 4. - page 170

 
Good day! Dear Professionals, please advise how do you test your EAs? We used to use Birt's Patch script and got 99% results, but since the 1st date it stopped working because the terminal does not support old builds anymore... so i am not sure what to do if i trust the results of usual terminal tests? How do you get out of it? Or maybe someone can take a look at the script and adapt it to the latest build?
Files:
 
Lisi4ka330:
Good day! Dear Professionals, how do you test your EAs? We used to use Birt's Patch script and got 99% results, but since the 1st date it stopped working because the terminal does not support old builds anymore... so i am not sure what to do if i trust the results of usual terminal tests? How do you get out of it? Or maybe someone can take a look at the script and adapt it to the latest build?
Have you tried changing #define LAST_BUILD_KNOWN 406 to 432?
 
Roman.:

Is this the wrong forum?

So much for "Any newcomer's question to ...." to keep all sorts of users out.

 
FAQ:

This is something new, please show me.

On this chart, the Expert Advisor opened order 7447278. No arrow has been placed on this chart.


At the same time, another EA on another chart with the same currency opened a pending order. The open order arrow on the chart above appears here. Moreover, the pointer of the order being modified during trawling was not set. The arrow colour of the set order appears to be the same as that of the modified order. Of course, the Expert Advisors have different magicians.


 
pusheax:
Have you tried changing #define LAST_BUILD_KNOWN 406 to 432?
Yes, I did, but it didn't work((((
 
Lisi4ka330:
Yes, I tried, but it didn't work out((((
The easiest option is to put a separate 409 build on the computer, and test on it.
 

I have a question (it's the weekend anyway).
is this strategy realistic (maybe someone tried it)
have virtually open 3 orders with stop=take and are 50-100-200pp sootv.
IMPORTANT orders are opened at the same time.
Then we gradually accumulate statistics for order results
0-losses 1 wins
it will look like:
0 0 0 - 15%
1 0 1 -20%
I think the meaning is clear.
Here is the strategy: let's assume we virtually open a 50/50 order that worked out to 0 (losses), then after zero we look for variants 100-100 and 200-200 and look for the higher percentage of success, and open a real 100-100 order and so on.
Do you think this strategy has a place to live?

It's somewhat analogous to the grid. For example, let's take a variant for 2 orders 50/50, 100/100.
Suppose the statistics is as follows (all orders are of the buy type)
0 0 -10%
0 1- 20%
1 0 -40%
1 1- 30%
and a 50/50 order wins =1
then we look at all variants with 1 at the beginning it is
1 0-40% and 1 1-30% which logically means that a 100/100 buy order will most probably have a - sign, in this case we open a sell order instead of a buy one.

here's what we got in 10 years - stopes and takei:
SL1=250; TP1=250; SL2=500; TP2=500; SL3=1000; TP3=1000; SL4=1250; TP4=1250;
and the corresponding matrix:
0000-321
0001-34
0010-8
0011-119
0100-34
0101-2
0110-11
0111-117
1000-111
1001-18
1010-4
1011-36
1100-117
1101-15
1110-44
1111-340

it is clear that some options are very rare in comparison with others, so as orders close (it is clear that the first ones will be with lower stops and profits) we can already predict which orders will close + or - (and therefore we should not wait for a loss, but to prepare it beforehand)
for example 1 order closed in + those = 1
see
1000-111
1001-18
1010-4
1011-36
1100-117
1101-15
1110-44
1111-340
we see the most likely outcome 1111-340 we do not cover anything,
second order 0
1000-111
1001-18
1010-4
1011-36
the most probable variant is 1000-111 and it is reasonable to close 2 remaining orders with a loss, but smaller than it would be on the next order.

 
alsu:
The easiest option is to put a separate 409 build on your computer and test on it.
since June 1, versions younger than 416 are not supported
 
Lisi4ka330:
versions below 416 build are not supported from 1 June

Remove sections of code responsible for linking cov to any build...
 
Lisi4ka330:
as of June 1, versions younger than 416 build are not supported

They are the ones that are not supported by the server. Locally they work. I still use 225.

Roman.:

Remove code fragments that are responsible for linking cov to any build...
How come?