Дополнительные рекомендации по использованию утилиты:
1. Количество свечей, взятых как эталонный участок, оптимально не более 30, а если вы хотите получить прогноз на более длительную перспективу, то лучше переключиться на старший таймфрейм.
2. Чем меньшее количество свечей в эталонном участке, тем более узким можно настраивать канал сверки (минимальное значение для входной переменной Channel равно 0.5), и тем более точным будет получаться прогноз.
3. Если процесс поиска синхронного экземпляра продолжается слишком долго (порядка 30 мин и более), то необходимо немного расширить канал сверки, то есть увеличить значение входной переменной Channel на 0.1.
4. Если на графике явно восходящая тенденция, то желательно, чтобы начальная свеча эталонного участка была восходящая и совпадала с каким-либо ближайшим нижним экстремумом (по цене открытия).
5. Если на графике явно низходящая тенденция, то желательно, чтобы начальная свеча эталонного участка была низходящая и совпадала с каким-либо ближайшим верхним экстремумом (по цене открытия).
6. Прогноз, полученный из явно флетового эталонного участка, как правило непригоден для использования.
7. Прогноз, отображающий флетовое состояние, также непригоден для использования.
Additional recommendations for using the utility:
1. The number of candles, taken as a reference area, is optimal not more than 30, and if you want to get a forecast for a longer term, it is better to switch to a higher timeframe.
2. The smaller the number of candles in the reference area, the narrower the reconciliation channel can be set (the minimum value for the input variable Channel is 0.5), and the more accurate the forecast will be.
3. If the process of searching for a synchronous instance lasts too long (about 30 minutes or more), it is necessary to slightly expand the reconciliation channel, that is, to increase the value of the input variable Channel by 0.1.
4. If on the chart is clearly an upward trend, it is desirable that the initial candle of the reference area is upward and coincides with any nearest lower extremum (at the opening price).
5. If on the chart is clearly a downward trend, it is desirable that the initial candle of the reference area is downward and coincides with any nearest upper extremum (at the opening price).
6. The forecast, obtained from explicitly to the flat reference area, is usually unusable.
7. The forecast, showing the flat state, is also unusable.
asaens15: Been awhile since you made a comment/recommendation, would appreciate any new discoveries on the product.
Hello.
So far, the recommendations remain the same.
But, according to my observations, the best result is obtained on the D1 timeframe, with the value of the input variable Candles equal to 22.
In addition, you can make a clarifying forecast, that is, first get a forecast with a certain value of Candles, and then get a forecast with a value of Candles half the previous one, and then see how these two forecasts correlate with each other, or vice versa, these two forecasts contradict each other.
Would the program run faster if it didn't have to update the screen constantly but instead update when analysis completed? Maybe an option in the input section could have True/False to update or wait until analysis completed.
asaens15: Would the program run faster if it didn't have to update the screen constantly but instead update when analysis completed? Maybe an option in the input section could have True/False to update or wait until analysis completed.
Hello.
Using the input variable Visible=Result, you can disable drawing, and then the indicator will work a little faster (but in fact this mode does not speed up the process too much) and display only the final result. In this mode, the indicator does not draw anything except the main button, which blinks, indicating that the process is happening and is not frozen.
If this algorithm was performed using special hardware that is adapted to perform just such an algorithm, the calculations would be performed much faster. However, such hardware does not exist in nature, and the execution of the algorithm in the usual software way takes a lot of time, even taking into account the fact that we have to resort to such a method as normalization (proportional reduction of the values of the volume columns).
I bought this indicator and downloaded to my mt4 platform and it says installed to my mt4 but nothing shows as there is no indicator - what is happening?
jmhuang: I bought this indicator and downloaded to my mt4 platform and it says installed to my mt4 but nothing shows as there is no indicator - what is happening?
Hello.
Thank you for your purchase.
This product is not an indicator.
It is the utility, in other words, it is the indicator based on the expert advisor.
If the utility was paid for, it should appear in the terminal window Navigator -> Expert Advisors -> Market.
There are several options when the product was paid for, but it cannot be set to the chart (or can be set but not work):
1. The product not appeared in the terminal at all. In this case, you should try two methods to upload the product - via the product page, or directly via the terminal. If both methods do not work, then only the Service Desk can help you.
2. The product appeared in the terminal, but it can't be installed to the chart by double-clicking or dragging. Then, after double-clicking (or dragging), you need to check that the product is present (or missing) on the chart. Right-click on the chart and in the drop-down menu select the item "Expert Advisors". Then a new window will open, and in this window there will be a list of expert advisors located on the chart. If this menu item is not active,or if the product is not in this list, then it means that the product is not installed on the chart, and in this case only the Service Desk can help you.
3. The product appeared in the terminal and it is normally set to the chart, but it doesn't draw anything at all. In this case, you should inform the developer, i.e. me.
And now you must choose from the options that I wrote above, and let me know which option is happening to you.
thank you i managed to get it working and tried it on the D1 timeframe and set the input variable candle to 22 and pressed on the toggle button "pause" to activate and waited for it to stop. Very interesting forecast indicator. look forward to trying it out on my live account on 0.01 trade. Of course, i have other methods to confirm price direction. Should be a good complement. Hope this forecast indicator will be better than other common forecast indicators like Vanga, iVar, Sultonov etc. Thumbs up to the author for coming out with this indicator. Just wondering what is the minimum lowest timeframe it can get to and what input variable for say H4 and H1 timeframes?
jmhuang: thank you i managed to get it working and tried it on the D1 timeframe and set the input variable candle to 22 and pressed on the toggle button "pause" to activate and waited for it to stop. Very interesting forecast indicator. look forward to trying it out on my live account on 0.01 trade. Of course, i have other methods to confirm price direction. Should be a good complement. Hope this forecast indicator will be better than other common forecast indicators like Vanga, iVar, Sultonov etc. Thumbs up to the author for coming out with this indicator. Just wondering what is the minimum lowest timeframe it can get to and what input variable for say H4 and H1 timeframes?
I recommend a timeframe no lower than H1.
But the most optimal, given the time it takes to search for the forecast (waiting time for the result), it is better for D1.
In addition, you can make a dual forecast, that is, first get a forecast with a certain value of input variable Candles (for example 22), and then get a forecast with a value of input variable Candles half the previous one (that is 11), and then see how these two forecasts correlate with each other, or vice versa, these two forecasts contradict each other.
From version to version, I have gradually optimized the source code, and the speed is now the limit.
Due to the specifics of this speed, the indicator can be used on a timeframe no lower than M15 (or even no lower than M30).
Thanks for the reply i will try and use the specific timeframes as suggested also what is the difference between this predictor and the neural predictor?
Thanks for the reply i will try and use the specific timeframes as suggested also what is the difference between this predictor and the neural predictor?
Hello.
It's hard to explain in a few words.
In short, the "Neural Predictor" is, in a sense, a self-learning program.
At the same time, it is not a neural network in the full sense of the term "neural network", but yet it is able to learn.
Been awhile since you made a comment/recommendation, would appreciate any new discoveries on the product.
Hello.
So far, the recommendations remain the same.
But, according to my observations, the best result is obtained on the D1 timeframe, with the value of the input variable Candles equal to 22.
In addition, you can make a clarifying forecast, that is, first get a forecast with a certain value of Candles, and then get a forecast with a value of Candles half the previous one, and then see how these two forecasts correlate with each other, or vice versa, these two forecasts contradict each other.
All other settings can be used by default.
Would the program run faster if it didn't have to update the screen constantly but instead update when analysis completed? Maybe an option in the input section could have True/False to update or wait until analysis completed.
Hello.
Using the input variable Visible=Result, you can disable drawing, and then the indicator will work a little faster (but in fact this mode does not speed up the process too much) and display only the final result. In this mode, the indicator does not draw anything except the main button, which blinks, indicating that the process is happening and is not frozen.
If this algorithm was performed using special hardware that is adapted to perform just such an algorithm, the calculations would be performed much faster. However, such hardware does not exist in nature, and the execution of the algorithm in the usual software way takes a lot of time, even taking into account the fact that we have to resort to such a method as normalization (proportional reduction of the values of the volume columns).
I bought this indicator and downloaded to my mt4 platform and it says installed to my mt4 but nothing shows as there is no indicator - what is happening?
Hello.
Thank you for your purchase.
This product is not an indicator.
It is the utility, in other words, it is the indicator based on the expert advisor.
If the utility was paid for, it should appear in the terminal window Navigator -> Expert Advisors -> Market.
There are several options when the product was paid for, but it cannot be set to the chart (or can be set but not work):
1. The product not appeared in the terminal at all. In this case, you should try two methods to upload the product - via the product page, or directly via the terminal. If both methods do not work, then only the Service Desk can help you.
2. The product appeared in the terminal, but it can't be installed to the chart by double-clicking or dragging. Then, after double-clicking (or dragging), you need to check that the product is present (or missing) on the chart. Right-click on the chart and in the drop-down menu select the item "Expert Advisors". Then a new window will open, and in this window there will be a list of expert advisors located on the chart. If this menu item is not active, or if the product is not in this list, then it means that the product is not installed on the chart, and in this case only the Service Desk can help you.
3. The product appeared in the terminal and it is normally set to the chart, but it doesn't draw anything at all. In this case, you should inform the developer, i.e. me.
And now you must choose from the options that I wrote above, and let me know which option is happening to you.
thank you i managed to get it working and tried it on the D1 timeframe and set the input variable candle to 22 and pressed on the toggle button "pause" to activate and waited for it to stop. Very interesting forecast indicator. look forward to trying it out on my live account on 0.01 trade. Of course, i have other methods to confirm price direction. Should be a good complement. Hope this forecast indicator will be better than other common forecast indicators like Vanga, iVar, Sultonov etc. Thumbs up to the author for coming out with this indicator. Just wondering what is the minimum lowest timeframe it can get to and what input variable for say H4 and H1 timeframes?
I recommend a timeframe no lower than H1.
But the most optimal, given the time it takes to search for the forecast (waiting time for the result), it is better for D1.
In addition, you can make a dual forecast, that is, first get a forecast with a certain value of input variable Candles (for example 22), and then get a forecast with a value of input variable Candles half the previous one (that is 11), and then see how these two forecasts correlate with each other, or vice versa, these two forecasts contradict each other.
on lower timeframes it predicts up to 3 candles is there a way i can change this to more candles?
Hello.
Just need to adjust the input variable "Forecast" more.
The description of this input variable is in the section "Input variables".
Hello.
Just need to adjust the input variable "Forecast" more.
The description of this input variable is in the section "Input variables".
ok i will try this also is there a way it can speed up the process as it takes a couple of minutes to predict the market or is this normal
ok i will try this also is there a way it can speed up the process as it takes a couple of minutes to predict the market or is this normal
Hello.
It is impossible to increase the speed.
From version to version, I have gradually optimized the source code, and the speed is now the limit.
Due to the specifics of this speed, the indicator can be used on a timeframe no lower than M15 (or even no lower than M30).
Hello.
It is impossible to increase the speed.
From version to version, I have gradually optimized the source code, and the speed is now the limit.
Due to the specifics of this speed, the indicator can be used on a timeframe no lower than M15 (or even no lower than M30).
Thanks for the reply i will try and use the specific timeframes as suggested also what is the difference between this predictor and the neural predictor?
Thanks for the reply i will try and use the specific timeframes as suggested also what is the difference between this predictor and the neural predictor?
Hello.
It's hard to explain in a few words.
In short, the "Neural Predictor" is, in a sense, a self-learning program.
At the same time, it is not a neural network in the full sense of the term "neural network", but yet it is able to learn.
And it works many times faster.
This is norma projection?
This is norma projection?
Hello.
Before I can give an answer, show me the indicator settings window.