Experts: Milestone - page 20
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
Does anyone having "waiting for calendar..." bug today on 22.3 version???
18.2 & 20.5 seems normal and okay..
it just me or happened to anyone else???
Does anyone having "waiting for calendar..." bug today on 22.3 version???
18.2 & 20.5 seems normal and okay..
it just me or happened to anyone else???
YES, i know about it, its just a display issue dont worry it still works and i will have it fixed.
Very merry xmas
for( int i = 0; i <= OrdersTotal() - 1; i++ ) {
It's not a good idea!
for( int i = OrdersTotal() - 1; i >= 0; i-- ) better than for( int i = 0; i <= OrdersTotal() - 1; i++ ) {
what are you talking about? there are many loops and this is a very important part to the system, if you think its a bug describe exactly where so i can fix it. There are many loops, some of them do not need a reverse iteration.
After a few days backtest, I have come to some conclusions that I would like to share. I hope it could contribute to the development . 1, If the parameters are set too risky, the account is definitely to go bust on some extreme trends. Enlarging your account does not help. 2, Try not to hold the wrong position, which is against the longer trend. Though the ea is able to fix the position sometimes, you would have made more money if not holding the wrong position. Or the wrong position would simply kill the account. So you had better manually fix those positions which are against the trend. And if possible, adjust the parameters to make the ea open less wrong positions. By the way, only FIFO is allowed on some platform. However, in the closeAll function, positions opened later are closed first. That would fail on some platform. I have tried to fix that. It's simple. Just change the for loop.
Hi trevone/ fhunter,
see my earlier conclusions. I think we share some same conclusions.
I hope i help trevone with my remarks to help to improve milestone. I think milestone it getting better and better. The backtest are important for me. If the trend is strong up or down (see EUR/USD chart) i posted, the account goes bust. I think that its important too handle extreme or strong trends. USD/JPY was for a long time in a downtrend but has a major bullrun. In the backtest you see that the account goes bust because you sell against an uptrend. So trend changes must be seen early. And if the trend changes you have to take the opposite direction, of you like it or not :-) How to translate this in a EA? I dont know.
I suggest to use the RSI parameter. If there is an overbought situation. Don't buy! The chance of going down is bigger.
All have a great trading week!
Greetings
Devke
Thanks Devke, this is a contribution I will gladly accept. Merry Xmas from sunny South Africa
After a few days backtest, I have come to some conclusions that I would like to share. I hope it could contribute to the development . 1, If the parameters are set too risky, the account is definitely to go bust on some extreme trends. Enlarging your account does not help. 2, Try not to hold the wrong position, which is against the longer trend. Though the ea is able to fix the position sometimes, you would have made more money if not holding the wrong position. Or the wrong position would simply kill the account. So you had better manually fix those positions which are against the trend. And if possible, adjust the parameters to make the ea open less wrong positions. By the way, only FIFO is allowed on some platform. However, in the closeAll function, positions opened later are closed first. That would fail on some platform. I have tried to fix that. It's simple. Just change the for loop.
Hi trevone/ fhunter,
see my earlier conclusions. I think we share some same conclusions.
I hope i help trevone with my remarks to help to improve milestone. I think milestone it getting better and better. The backtest are important for me. If the trend is strong up or down (see EUR/USD chart) i posted, the account goes bust. I think that its important too handle extreme or strong trends. USD/JPY was for a long time in a downtrend but has a major bullrun. In the backtest you see that the account goes bust because you sell against an uptrend. So trend changes must be seen early. And if the trend changes you have to take the opposite direction, of you like it or not :-) How to translate this in a EA? I dont know.
I suggest to use the RSI parameter. If there is an overbought situation. Don't buy! The chance of going down is bigger.
All have a great trading week!
Greetings
Devke
Thanks Devke, this is a contribution I will gladly accept. Merry Xmas from sunny South Africa
Hi Trevone,
You also merry chrismas!!! Also from a sunny Holland :-), it's only cold here. :-( I rather like a better temperature :-)
Greetings
Devke
Hi Trevone,
Gentlemen's agreement are fine by me. Maybe you can do something with copyrights for youreself and an honourfull statement in the code for everybody who helped you :-)
Just kidding :-)
I saw 22.4 is online, any major changes from 22.3?
Greetings,
Devke.
P.S. I dont know how to use the setfiles link, and what it does, works etc. Shortage of knowledge :-)
Hi Trevone,
Another suggestion. I see that you put text into the graph. It's not always good to read because of the bars in the graph. Damn things :-)
Is it possible to position the text on een other place in the graph? Or in a logfile or something? Or do you of anyone else have an better suggestion?
So keep up the good work!!
Greetings
Devke
Hi Trevone,
Gentlemen's agreement are fine by me. Maybe you can do something with copyrights for youreself and an honourfull statement in the code for everybody who helped you :-)
Just kidding :-)
I saw 22.4 is online, any major changes from 22.3?
Greetings,
Devke.
P.S. I dont know how to use the setfiles link, and what it does, works etc. Shortage of knowledge :-)
yeah yeah no problem. i have a domain for the project now, i will also have to upgrade teh set file side of things. all in good time
Hi Trevone,
Another suggestion. I see that you put text into the graph. It's not always good to read because of the bars in the graph. Damn things :-)
Is it possible to position the text on een other place in the graph? Or in a logfile or something? Or do you of anyone else have an better suggestion?
So keep up the good work!!
Greetings
Devke
i am thinking very carefully about the user acceptance standards not to worry about that.