Ба́йесовская фильтра́ция спа́ма — метод для фильтрации спама, основанный на применении наивного байесовского классификатора, опирающегося на прямое использование теоремы Байеса. Теорема Байеса названа в честь её автора Томаса Байеса (1702—1761) — английского математика и священника, который первым предложил использование теоремы для...
it is known that the series of prices is close to be considered as a series of independent increments. Therefore, the set of n random variables d(1)=p(2)-p(1), d(2)=p(3)-p(2), ... d(n-1)=p(n)-p(n-1), p(n) will be close to independent. Now, any set of functions from our set will be independent if any argument is included only in the expression of one of them. To put it simply: the set for four bars from functions I1(d1,d2) and I2(d3,p4) will be independent, but I1(d1,d2,d3) and I2(d3,p4) will not be independent, because of d3. For example, two different MAs will always be dependent. But if you take two MAs such that the second one is shifted back in time by the period of the first one, then a system of the first MA and their difference will be independent.
This is very similar to finding the embedding space N and time delay Tau of chaotic processes, only there the "set" - a vector for one point of the modified multidimensional space - is made of N not consecutive samples of the original time series, but with a step Tau. Original source. The authors used this algorithm for neural network forecasting, but the essence is the same - independence of predictors - it is needed there at the input of the network just as in our statistical formula.
This is very similar to finding the embedding space N and time delay Tau of chaotic processes, only there the "set" - a vector for one point of the modified multidimensional space - is made of N not consecutive samples of the original time series, but with a step Tau. Original source. The authors used this algorithm for neural network forecasting, but the essence is the same - independence of predictors - it is needed there at the input of the network just as in our statistical formula.
The similarity is undoubtedly there, as the field of dynamic chaos research uses methods of the theory of random processes. I cannot judge to what extent and whether this is always justified. On the one hand it is constantly emphasised that stochastic and chaotic systems are fundamentally different (e.g. when the dimensionality of the embedding increases), and on the other hand, for example, all our computer random number generators are still dynamical systems, but they are somehow studied by means of theorver. Regarding the application of chaos to the market - Peters in his book calculated the attractor of some prices and it turned out to be of some huge dimension.
It's a typo made by the editor between the 3rd and 4th revision. In the 3rd revision the formulae are written in text by me - everything is correct there, but in the 4th revision the formulae are already in the form of a picture and with an error.
The implementation is throwing few errors while using RubbArray.mqh
Yes, MetaQuotes have changed MQL language since the publication date, breaking back compatibility (alas) with many existing source codes. ArrayCopy can not be used for arbitary pointers anymore.
You may use the attached header file as a relacement.
How to fix that something would work? ) Expert Advisor doesn't compile, MT5.
code generation error 1
and why write code with a lot of vornings?
'indstats.mq5' indstats.mq5 11'MarketMQL4.mqh' MarketMQL4.mqh 11'ind4to5.mqh' ind4to5.mqh 11
macro redefinition ind4to5.mqh 1709
macro redefinition ind4to5.mqh 1719
macro redefinition ind4to5.mqh 1749'mt4orders.mqh' mt4orders.mqh 11
macro redefinition mt4orders.mqh 4129
macro redefinition mt4orders.mqh 4139'IndicatN.mqh' IndicatN.mqh 11'fmtprnt2.mqh' fmtprnt2.mqh 11'RubbArray.mqh' RubbArray.mqh 11'Expert0fix.mqh' Expert0fix.mqh 11'HashMapTemplate.mqh' HashMapTemplate.mqh 11
possible loss of data due to type conversion MarketMQL4.mqh 498
possible loss of data due to type conversion MarketMQL4.mqh 618
possible loss of data due to type conversion MarketMQL4.mqh 638
possible loss of data due to type conversion MarketMQL4.mqh 658
possible loss of data due to type conversion MarketMQL4.mqh 778
possible loss of data due to type conversion MarketMQL4.mqh 798
possible loss of data due to type conversion MarketMQL4.mqh 898
possible loss of data due to type conversion MarketMQL4.mqh 918
possible loss of data due to type conversion MarketMQL4.mqh 1038
declaration of 'line' hides member declaration at line 14 fmtprnt2.mqh 2139
see previous declaration of 'line' fmtprnt2.mqh 1412
possible loss of data due to type conversion IndicatN.mqh 94545
possible loss of data due to type conversion IndicatN.mqh 94751
possible loss of data due to type conversion IndicatN.mqh 94773
possible loss of data due to type conversion IndicatN.mqh 94795
possible loss of data due to type conversion IndicatN.mqh 947117
possible loss of data due to type conversion IndicatN.mqh 947139
possible loss of data due to type conversion IndicatN.mqh 947161
possible loss of data due to type conversion IndicatN.mqh 95145
possible loss of data due to type conversion IndicatN.mqh 95347
possible loss of data due to type conversion IndicatN.mqh 95369
possible loss of data due to type conversion IndicatN.mqh 953113
possible loss of data due to type conversion IndicatN.mqh 95552
possible loss of data due to type conversion IndicatN.mqh 95752
possible loss of data due to type conversion IndicatN.mqh 96145
possible loss of data due to type conversion IndicatN.mqh 96167
possible loss of data due to type conversion IndicatN.mqh 96350
possible loss of data due to type conversion IndicatN.mqh 96551
possible loss of data due to type conversion IndicatN.mqh 96573
possible loss of data due to type conversion IndicatN.mqh 96747
possible loss of data due to type conversion IndicatN.mqh 97147
possible loss of data due to type conversion IndicatN.mqh 97169
possible loss of data due to type conversion IndicatN.mqh 97191
possible loss of data due to type conversion IndicatN.mqh 971113
possible loss of data due to type conversion IndicatN.mqh 971135
possible loss of data due to type conversion IndicatN.mqh 971157
possible loss of data due to type conversion IndicatN.mqh 97350
possible loss of data due to type conversion IndicatN.mqh 97372
possible loss of data due to type conversion IndicatN.mqh 97394
possible loss of data due to type conversion IndicatN.mqh 97550
possible loss of data due to type conversion IndicatN.mqh 97572
possible loss of data due to type conversion IndicatN.mqh 97745
possible loss of data due to type conversion IndicatN.mqh 97944
possible loss of data due to type conversion IndicatN.mqh 97966
possible loss of data due to type conversion IndicatN.mqh 98146
possible loss of data due to type conversion IndicatN.mqh 98168
possible loss of data due to type conversion IndicatN.mqh 98190
possible loss of data due to type conversion IndicatN.mqh 981112
possible loss of data due to type conversion IndicatN.mqh 98546
possible loss of data due to type conversion IndicatN.mqh 98568
possible loss of data due to type conversion IndicatN.mqh 98590
possible loss of data due to type conversion IndicatN.mqh 985112
possible loss of data due to type conversion IndicatN.mqh 98745
possible loss of data due to type conversion IndicatN.mqh 98767
possible loss of data due to type conversion IndicatN.mqh 98945
possible loss of data due to type conversion IndicatN.mqh 99448
possible loss of data due to type conversion IndicatN.mqh 99470
possible loss of data due to type conversion IndicatN.mqh 99652
possible loss of data due to type conversion IndicatN.mqh 99674
possible loss of data due to type conversion IndicatN.mqh 99696
possible loss of data due to type conversion IndicatN.mqh 99845
possible loss of data due to type conversion IndicatN.mqh 101142
possible loss of data due to type conversion IndicatN.mqh 141954
possible loss of data due to type conversion IndicatN.mqh 153815
declaration of 'e' hides global declaration in file 'indstats.mq5' at line 50 IndicatN.mqh 1582160
see previous declaration of 'e' indstats.mq5 508
possible loss of data due to type conversion IndicatN.mqh 163575
possible loss of data due to type conversion IndicatN.mqh 184949
possible loss of data due to type conversion Expert0fix.mqh 25418
possible loss of data due to type conversion IndicatN.mqh 7079
possible loss of data due to type conversion IndicatN.mqh 7079
possible loss of data due to type conversion IndicatN.mqh 7079
possible loss of data due to type conversion IndicatN.mqh 7079implicit conversion from'number' to 'string' fmtprnt2.mqh 6244implicit conversion from'number' to 'string' fmtprnt2.mqh 7717implicit conversion from'number' to 'string' fmtprnt2.mqh 9317
code generation error 111 error(s), 79 warning(s) 280
Warnings can be removed, I didn't create them on purpose, just a lot of inherited code, but now I've moved away from MQL - I can optimise them if you want, I have the source code.
I am posting corrected codes (without warnings). On old MT5 builds without support of serial functions a la MT4, without iBars and iBarShift - their implementations are enabled by MT5_BUILD_IS_LESS_THAN_1860 macro.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
only if all strategies are mutually independent and give a probability greater than 0.5
I took a closer look at the formula
P(Win|ABC) = P(Win|A)* P(Win|B)* P(Win|C) /[ P(Win|A)* P(Win|B)* P(Win|C) - (1 - P(Win|A))* (1 - P(Win|B))* (1 - P(Win|C))) ]
I took a closer look at the formula
This value is always greater than one (the numerator is greater than the denominator). What is the correct formula?Thanks for noticing the typo. There should be a "+" there, not a minus "-" https://ru.wikipedia.org/wiki/%D0%91%D0%B0%D0%B9%D0%B5%D1%81%D0%BE%D0%B2%D1%81%D0%BA%D0%B0%D1%8F_%D1%84%D0%B8%D0%BB%D1%8C%D1%82%D1%80%D0%B0%D1%86%D0%B8%D1%8F_%D1%81%D0%BF%D0%B0%D0%BC%D0%B0
Let's fix it.
it is known that the series of prices is close to be considered as a series of independent increments. Therefore, the set of n random variables d(1)=p(2)-p(1), d(2)=p(3)-p(2), ... d(n-1)=p(n)-p(n-1), p(n) will be close to independent. Now, any set of functions from our set will be independent if any argument is included only in the expression of one of them. To put it simply: the set for four bars from functions I1(d1,d2) and I2(d3,p4) will be independent, but I1(d1,d2,d3) and I2(d3,p4) will not be independent, because of d3.
For example, two different MAs will always be dependent. But if you take two MAs such that the second one is shifted back in time by the period of the first one, then a system of the first MA and their difference will be independent.
This is very similar to finding the embedding space N and time delay Tau of chaotic processes, only there the "set" - a vector for one point of the modified multidimensional space - is made of N not consecutive samples of the original time series, but with a step Tau. Original source. The authors used this algorithm for neural network forecasting, but the essence is the same - independence of predictors - it is needed there at the input of the network just as in our statistical formula.
This is very similar to finding the embedding space N and time delay Tau of chaotic processes, only there the "set" - a vector for one point of the modified multidimensional space - is made of N not consecutive samples of the original time series, but with a step Tau. Original source. The authors used this algorithm for neural network forecasting, but the essence is the same - independence of predictors - it is needed there at the input of the network just as in our statistical formula.
Thanks for noticing the typo. There should be a "+" there, not a minus "-" https://ru.wikipedia.org/wiki/%D0%91%D0%B0%D0%B9%D0%B5%D1%81%D0%BE%D0%B2%D1%81%D0%BA%D0%B0%D1%8F_%D1%84%D0%B8%D0%BB%D1%8C%D1%82%D1%80%D0%B0%D1%86%D0%B8%D1%8F_%D1%81%D0%BF%D0%B0%D0%BC%D0%B0
Let's fix it
It's a typo made by the editor between the 3rd and 4th revision. In the 3rd revision the formulae are written in text by me - everything is correct there, but in the 4th revision the formulae are already in the form of a picture and with an error.
The implementation is throwing few errors while using RubbArray.mqh
The implementation is throwing few errors while using RubbArray.mqh
Yes, MetaQuotes have changed MQL language since the publication date, breaking back compatibility (alas) with many existing source codes. ArrayCopy can not be used for arbitary pointers anymore.
You may use the attached header file as a relacement.
How to fix that something would work? ) Expert Advisor doesn't compile, MT5.
code generation error 1and why write code with a lot of vornings?
As for code generation error - as always - in SD.
Warnings can be removed, I didn't create them on purpose, just a lot of inherited code, but now I've moved away from MQL - I can optimise them if you want, I have the source code.