![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Question: What is the probability of a combination appearing in the market that matches the required 64 digits? Answer: (1/2^64)*BarsCount. That is, with a probability close to 100% such a combination will not be found. So, obviously, only number int or long cannot fully describe the pattern, so we need an additional parameter specifying the length of the pattern.
This is if we look at all 64 bits. But it is obviously unnecessary.
When I performed such investigations, I found out that it is not reasonable to take the length of a candlestick pattern longer than 5. Moreover, if we distinguish between bars not only by the "bull-bear" ones but by their sizes as well, even this length is too long.
If we have a pattern with large length - it is much more reasonable to specify "characteristic features" and simply limit the length by minimal and maximal values.
Not exactly formed yet, but the general idea is: two parameters - length and int parameter from 0 to 3. Inside the Expert Advisor is already interpreting this number (Pseudobit representation):
It remains to decide how to code these parameters. A straightforward solution: a structure in which each int parameter (the first column of the table) corresponds to a Pseudobit representation (the third column). If you limit the mask to only five characters (xxxxxx), the structure is not very big.
And the most important thing - the optimizer allows you to rearrange the structure!
You can also make three separate parameters for the three candles in the properties window. Two birds are killed at once - it is both clear and optimised.
The same can be done for 10 candlesticks.
You can also make three separate parameters for the three candles in the properties window. Two birds are killed at once - it is both clear and optimised.
The same may be done for 10 candlesticks.
I support
Not exactly formed yet, but the general idea is: two parameters - length and int parameter from 0 to 3. Inside the Expert Advisor is already interpreting this number (Pseudobit representation):
It remains to decide how to code these parameters. A straightforward solution: a structure in which each int parameter (the first column of the table) corresponds to a Pseudobit representation (the third column). If the mask is limited to only five characters (xxxxxx), the structure is not very big.
And the most important thing - the optimizer allows you to rearrange the structure!
This is the enumeration for mask from x to xxxx:
Morse code version "1.005"
Here is the solution: the mask is defined as an enumeration
in OnInit(), the mask is translated into a string variable"sExtMorseCode" (the variable"sExtMorseCode" is declared globally) in the ConvertNumberToString function:
Two problems have been solved:
1). the user sees the pattern as "0101" in the input parameters:
2). The input parameter is perfectly optimized in the tester.
Morse code version "1.005"
Two problems have been solved:
1). the user sees the pattern as "0101" in the input parameters:
2). The input parameter is perfectly optimized in the tester.
The user can specify a candlestick combination without mathematical calculations according to the initial idea?
The user can specify a candlestick combination without mathematical calculations, as originally conceived?
Yes, he can do it without any mathematical calculations. And now you don't need to enter the combination manually - just select the appropriate candlestick combination from the"pattern mask" drop-down list.