Discussion of article "Experiments with neural networks (Part 3): Practical application" - page 4
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
Hi Roman,
I just finished reading your last article thoroughly. I am not surprised by the 443 DNN Angle results; they mirror mine. I suspect that the problem arises in the close out decision processing although I have not examined it in depth. I will be examining your new EAs in detail shortly.
In the meantime, here is my completed CSV Reformatter with the associated Winfile for you. You may be able to use its concepts to automate part of your EA by allowing you to read in the weight values directly without performing the file insert process. It is designed to read the saved CSV version of an Optimization Report while removing passes that have a low frequency of trades or produce losing result. The reformatted CSV file will be read directly into my EA to either set the DNN weights or to select the most effective values in a optimization test.
It is important to remember that the Excel file of the Optimization run must reformat the Equity and Profit columns to NUMBERS without a comma 1000's separator prior to running the reformatter Path and file names that contain spaces MUST be enclosed with a triple double quotes, """, not just a single quotes to pass the spaces correctly to Windows. Also directory separators \ must be entered as \\ to eliminate the escape processing in the compiler.
Hope this helps,
Cheers
Hi Roman,
I just finished reading your last article thoroughly. I am not surprised by the 443 DNN Angle results; they mirror mine. I suspect that the problem arises in the close out decision processing although I have not examined it in depth. I will be examining your new EAs in detail shortly.
In the meantime, here is my completed CSV Reformatter with the associated Winfile for you. You may be able to use its concepts to automate part of your EA by allowing you to read in the weight values directly without performing the file insert process. It is designed to read the saved CSV version of an Optimization Report while removing passes that have a low frequency of trades or produce losing result. The reformatted CSV file will be read directly into my EA to either set the DNN weights or to select the most effective values in a optimization test.
It is important to remember that the Excel file of the Optimization run must reformat the Equity and Profit columns to NUMBERS without a comma 1000's separator prior to running the reformatter Path and file names that contain spaces MUST be enclosed with a triple double quotes, """, not just a single quotes to pass the spaces correctly to Windows. Also directory separators \ must be entered as \\ to eliminate the escape processing in the compiler.
Hope this helps,
Cheers
Thank you. I will definitely look.
Roman,
I am just beginning to evaluate your current work in detail. Here is a chart of comparisons that I have run.
It demonstrates clearly that 8 Preceptron EAs are vastly superior to a 4443 NDD Original model. In running these tests I noticed a small oversight in MQ5 BackTest tab. It shows results in thousands with a space between the third and fourth digits which was their attempt to eliminate commas. However, the space misled me to think it was the number of trades.
I am interested in modifying the Preceptrons to include fewer or more than 8 nodes. Can you explain the schema used to generate 5, 6, 7, 9 etc node Preceptrons? Alternatively, can you cite any references that explain its structure? In looking at your 2 Preceptron EAs, it seems that making a set of Preceptron Classes and parameterize the input might be beneficial. As then you could instantiate multiple versions of identical nodes to be used for different purposes. I think I will be trying this approach although I'm sure it will be slower than your code.
Stay Safe,
CapeCoddah
Roman,
I am just beginning to evaluate your current work in detail. Here is a chart of comparisons that I have run.
It demonstrates clearly that 8 Preceptron EAs are vastly superior to a 4443 NDD Original model. In running these tests I noticed a small oversight in MQ5 BackTest tab. It shows results in thousands with a space between the third and fourth digits which was their attempt to eliminate commas. However, the space misled me to think it was the number of trades.
I am interested in modifying the Preceptrons to include fewer or more than 8 nodes. Can you explain the schema used to generate 5, 6, 7, 9 etc node Preceptrons? Alternatively, can you cite any references that explain its structure? In looking at your 2 Preceptron EAs, it seems that making a set of Preceptron Classes and parameterize the input might be beneficial. As then you could instantiate multiple versions of identical nodes to be used for different purposes. I think I will be trying this approach although I'm sure it will be slower than your code.
Stay Safe,
CapeCoddah
Hi. Send me a private message. I am now recruiting a development team. If you are ready to work hard join. Participation is paid.
Hi. Send me a private message. I am now recruiting a development team. If you are ready to work hard join. Participation is paid.
Not really interested, retired 20 years ago and programing is now a part time hobby. Thanks for the offer & I don't know how tos send a private message.
Not really interested, retired 20 years ago and programing is now a part time hobby. Thanks for the offer & I don't know how tos send a private message.
Please, if you change your mind, you are welcome.
Hi Roman,
I am focusing on your 4 Perceptron TP/SL models. In doing Visualize runs in the tester, I am noticing some significant order processing problems that are causing large draw downs, most notably around 2022 07/05 where there is a $1,350 draw down see Bad Trades attachment
This appears to be caused by order 3534 which lacks both a TP & SL and is highlighted in Light green. In some cases the the highlight is in the Rose color indicating that the Price identified is outside the trading range. The comments identify it as "tp104740" instead of "Perceptron EN_xx and the volume is ).62/0.62. This seems to indicate that there was incomplete processing of the order setup.
This problem repeats itself each time the Perceptron row for loop resets, for(int i=0; i<=(ArraySize(EURUSD)/6)-2; i++){ . I tested a version by decreasing the upper limit by one and the errors persist.
BTW you should change the ArraySize to ArrayRange(EURUSD,0) ad drop the calculations.
The problem also manifests itself each time the signal switches from buy to sell or vice versa.
The problem could be be caused by an initialization problem caused either at the start of the loop or at the end or is this a Netting problem and the buy/sell functions should be moved outside of the for loop?
In reviewing all of the trades with a zero SL, I noticed that nearly all have a date time which is seconds off of 00. Thinking that your IsNewBar was off, I substituted my NewBar and obtained identical results. Consequentially it seems that anytime there is no trade activity in the first second of a new bar, the error may occur. This does not bode well for using this concept for other currency pairs that do not trade as frequently as EURUSD.
Thus, I have a lot of potential problems but no good concept on how to proceed as I am in the beginning of converting from MT4 to MT5 and do not thoroughly understand the order processing details of MT5. Can you identify and correct the problem??
Thanks CapeCoddah
BTW Your concept of using 10 of the first 100 Perceptron rows from the optimization run is brilliant. I certainly increases the efficiency of the EA.
Hi Roman,
I am focusing on your 4 Perceptron TP/SL models. In doing Visualize runs in the tester, I am noticing some significant order processing problems that are causing large draw downs, most notably around 2022 07/05 where there is a $1,350 draw down see Bad Trades attachment
This appears to be caused by order 3534 which lacks both a TP & SL and is highlighted in Light green. In some cases the the highlight is in the Rose color indicating that the Price identified is outside the trading range. The comments identify it as "tp104740" instead of "Perceptron EN_xx and the volume is ).62/0.62. This seems to indicate that there was incomplete processing of the order setup.
This problem repeats itself each time the Perceptron row for loop resets, for(int i=0; i<=(ArraySize(EURUSD)/6)-2; i++){ . I tested a version by decreasing the upper limit by one and the errors persist.
BTW you should change the ArraySize to ArrayRange(EURUSD,0) ad drop the calculations.
The problem also manifests itself each time the signal switches from buy to sell or vice versa.
The problem could be be caused by an initialization problem caused either at the start of the loop or at the end or is this a Netting problem and the buy/sell functions should be moved outside of the for loop?
In reviewing all of the trades with a zero SL, I noticed that nearly all have a date time which is seconds off of 00. Thinking that your IsNewBar was off, I substituted my NewBar and obtained identical results. Consequentially it seems that anytime there is no trade activity in the first second of a new bar, the error may occur. This does not bode well for using this concept for other currency pairs that do not trade as frequently as EURUSD.
Thus, I have a lot of potential problems but no good concept on how to proceed as I am in the beginning of converting from MT4 to MT5 and do not thoroughly understand the order processing details of MT5. Can you identify and correct the problem??
Thanks CapeCoddah
BTW Your concept of using 10 of the first 100 Perceptron rows from the optimization run is brilliant. I certainly increases the efficiency of the EA.
Thanks for the feedback. Send me an EA with an error in private messages. I'll try to figure it out.
Roman,
Use the 1 Perceptron Angle SL TP Trade.EX5 that you released with this article.
Strategy Tester: Visualize from 2021 12/09 to 2022 12/09 producing a back test profit of approximately $2747.02 (it has varied from 2747 to 2758) Select History tab in the Strategy Tester and select Orders, then sort ascending on S/L. Look at order 991 to se the rose high light. Notice the time stamp times and also the comments.
I ran two tests, one without buy orders and the other without sells. Both exhibited the problem.
Enjoy
CapeCoddah
Roman,
Use the 1 Perceptron Angle SL TP Trade.EX5 that you released with this article.
Strategy Tester: Visualize from 2021 12/09 to 2022 12/09 producing a back test profit of approximately $2747.02 (it has varied from 2747 to 2758) Select History tab in the Strategy Tester and select Orders, then sort ascending on S/L. Look at order 991 to se the rose high light. Notice the time stamp times and also the comments.
I ran two tests, one without buy orders and the other without sells. Both exhibited the problem.
Enjoy
CapeCoddah
Hi. I didn't find any problems. See screenshot. What is your broker?