RK
Topics
03 Feb 2016, 23:21
5604
17
19 Nov 2015, 09:18
3463
2
16 Jul 2015, 23:25
2665
4
26 Feb 2015, 21:20
3302
3
12 Sep 2014, 09:45
1
1062
1
11 Sep 2014, 22:30
0
3257
2
30 Aug 2014, 16:51
2241
1
22 Aug 2014, 18:05
7547
31
20 Aug 2014, 12:30
3349
3
14 Jul 2014, 12:48
3154
7
16 Jun 2014, 00:39
2701
2
22 May 2014, 16:17
4377
10
02 Apr 2014, 22:03
4104
2
29 Mar 2014, 15:41
3847
4
27 Jan 2014, 08:20
3649
6
09 Jan 2014, 00:35
5126
15
22 Nov 2013, 00:51
3519
6
13 Nov 2013, 11:27
4332
6
06 Nov 2013, 19:16
3710
9
21 Oct 2013, 17:19
3752
6
Replies
rkokerti
04 Oct 2012, 16:04
Hi!
Try this:
Trade.CreateBuyStopOrder(Symbol,Volume,TargetPrice,StopLoss,TakeProfit,Exp);
or
Trade.CreateSellStopOrder(Symbol,Volume,TargetPrice,StopLoss,TakeProfit,Exp);
Where Exp:
DateTime Exp = MarketSeries.OpenTime.LastValue.AddMinutes(60);
or
DateTime Exp = MarketSeries.OpenTime.LastValue.AddDays(1);
or
DateTime Exp = MarketSeries.OpenTime.LastValue.AddHours(1);
depends on your time scale. I hope it will help you.
@rkokerti
rkokerti
23 Sep 2012, 23:05
Hello,
Please check out the code of this robot. /algos/show/115
I hope it will help you.
@rkokerti
rkokerti
06 Nov 2012, 01:51 ( Updated at: 21 Dec 2023, 09:20 )
Dear Support,
Thanks for your quick answer.
After analyzed your example, I understood why I could not reproduced the Max DrawDown in Excel. The reason was the approach.
According to definition as far as I know, the Drawdown is the measure of the decline from a historical peak. The key word is the historical. I think it’s very important, that trader doesn’t loose money that has earned in a given period of time (backtest period).
But, cAlgo continually restart the calculation of Drawdown. So it’s like a block-calculation and not a historical one. And it’s very confusing and misleading for me.
I attached a table below that shows the difference between the result of my calculation and cAlgo. Unfortunately there are significant differences.
Max DD - cAlgo calculation for all: 6.06%
Max DD - My calculation for all: 12,47%
What is your opinion about it?
Thanks
@rkokerti