Topics
Replies
rkokerti
20 Nov 2012, 17:55
( Updated at: 21 Dec 2023, 09:20 )
One other comment...
If I remove "using cAlgo.Indicators;" from robot code and press "Build Robot" button then an error message come. It said "Maybe one using directive is missing" or something like that. (sorry for translation) So, this is the reason why I think it is important is case of reference indicators. Or not?
see below:
@rkokerti
rkokerti
20 Nov 2012, 17:03
( Updated at: 21 Dec 2023, 09:20 )
OK, durring I used cAlgo 1.0.16 all backtest ran normally. There was a lot of trade in result table and on balance/equity chart.
Now, I received new version 1.0.18 (yesterday evening) I wanted to run backtest again, but the result contains only one trade, see below:
I didn't change anything in code of robot and reference indicator between two version 1.0.16 and 1.0.18.
@rkokerti
rkokerti
19 Nov 2012, 15:33
Currently I use FxPro UK cAlgo ver. 1.0.16, but previously I tried FxPro cAlgo (not UK), and also tried Spotware cAlgo... but more or less with similar result. Maybe Spotware cAlgo was little better. I didn’t know that is relevant which version of cAlgo is running on my computer… Is it relevant? Which one you recommend?
And no, I don’t logged in to two different instances of cAlgo with the same account at the same time. But, as I mentioned previously I tried all version of cAlgo (UK, Spotware, not UK) then each version I logged in.
@rkokerti
rkokerti
14 Nov 2012, 18:07
RE:
I understand and trust me, I do not build it every time. But what you wrote down dosen't eliminate the cause, only a temporary solution to.You only need to build it once when you have completed coding. After that all you need to do to load it, is to add an instance. Then the indicator should be loaded in a very short time. You do not need to build it every time you want to load it to the chart.
{
int index = MarketSeries.Close.Count-2;
if(_dms.DIPlus[index] > _dms.DIMinus[index])
{
Trade.CreateBuyMarketOrder(Symbol, Volume);
}
{
Trade.CreateSellMarketOrder(Symbol, Volume);
}
}
@rkokerti
rkokerti
14 Nov 2012, 13:22
RE:
Unfortunately, still the same slow! 28 seconds, nothing has changed...Your code is actually loading fast. Nowhere close to 28 seconds. Could you test it for instance on EURUSD and see if the loading time is still slow? It could be that the symbol you are using has more historical trendbars and it takes longer to calculate.
@rkokerti
rkokerti
07 Nov 2012, 13:13
( Updated at: 21 Dec 2023, 09:20 )
Hello,
I try to visualize the issue on screeshot below:
You find the differece in row 26, if you copy the code back into cAlgo.
1. case : I dosen't use DMS as condition (1 sec)
if(MarketSeries.Open[index] < MarketSeries.Close[index]) // & _dms.DIPlus[index] > _dms.DIMinus[index])
2. case: I use DMS as condition (28 sec)
if(MarketSeries.Open[index] < MarketSeries.Close[index] & _dms.DIPlus[index] > _dms.DIMinus[index])
Thanks for your help!
@rkokerti
rkokerti
06 Nov 2012, 15:17
( Updated at: 21 Dec 2023, 09:20 )
Hello,
Thanks for your answer!
But, as I mentioned this is a very important index-number in a risk management point of view. So, I would like to know what is the measure of the decline, from a historical peak (when I reached a new higher-high in account balance)
see below the last bold arrow on picture:
If it’s possible please implement it into the backtest result table.
Thanks for your help!
@rkokerti
rkokerti
27 Nov 2012, 14:50
OK, thanks!
Can I maybe download an older version somehow, until solution will available?
Thanks for your help!
@rkokerti