Topics
Replies
lec0456
21 Mar 2017, 18:46
( Updated at: 21 Dec 2023, 09:20 )
RE:
lec0456 said:
In cTrader, on the positions tab the "Created" column and "Last Modified" Column are in 12hr format. This should be in 24 hr format like every place else in cTrader and cAlgo. I hope you can recognize this as a bug. Of course, you should be usimg one format throught the application. But as it stands, you have some col;umns usung 24hr format and others using 12hr.
Please fix it so all time format for colums are in 24hr format or 12hr format but not both. I don't think there is any place to select this and It is not necessary in my opinion but the application should use a uniform time format.
@lec0456
lec0456
20 Mar 2017, 14:30
Yes, when backtesting a cBot. If use lets say a year worth of tick data, It backtests the bot, but the cpu usage never gets above 30%. Also, I had a c# developer look at the problem to tell me if my computer had any issues and he said the probelm is that cAlgo.exe it is only configured to use one core.
@lec0456
lec0456
08 Mar 2017, 20:19
ok, first and foremost, the CPU usage will not go above 40% when running a backtest. Something is bottlenecking cpu usage. So, the first question is when you backtest does your CPU usage ever reach 100%.
I have tested my processor with the intel diagnosic utility and it reaches 100% and passes the test. I called intel they say its something with the code of cAlgo.
@lec0456
lec0456
21 Jan 2017, 19:18
I specifically bought this PC to get better performance after running my Algo on a celeron 1.6ghz. This PC is a Z170 chipset, I7, 3.4ghz, 16GB ddr4, with aan M.2 Solid State Drive, transfer rate is 32gbs.
I even selected cAlgo in the Task manager and set its priority to high.
Yes, I am using tickdata. But it is really slow. And the memory usage is higher than any program I have ever used. 2.5gigs and the processors are not maxing out, ever. so, it doesn't seem like CAlgo is taking advantage of the resources on the system anyway.
@lec0456
lec0456
15 Aug 2016, 06:25
RE:
lec0456 said:
I would have never in a million years thought the platform backtesting engine would be producing negative spreads as large as 10 pips, but yes you were correct.
I just threw these lines of code in to stop the behavior while backtesting.
if(!Account.IsLive && Symbol.Spread/Symbol.PipSize<=-10) { //Print(MarketSeries.OpenTime[MarketSeries.Close.Count - 1].ToString("MM/dd/yyyy HH:mm")+" Neg Spread: "+Math.Round(Symbol.Spread/Symbol.PipSize,2)); return; }
Correction !Account.IsLive should be IsBacktesting.
@lec0456
lec0456
15 Aug 2016, 02:49
I would have never in a million years thought the platform backtesting engine would be producing negative spreads as large as 10 pips, but yes you were correct.
I just threw these lines of code in to stop the behavior while backtesting.
if(!Account.IsLive && Symbol.Spread/Symbol.PipSize<=-10)
{
//Print(MarketSeries.OpenTime[MarketSeries.Close.Count - 1].ToString("MM/dd/yyyy HH:mm")+" Neg Spread: "+Math.Round(Symbol.Spread/Symbol.PipSize,2));
return;
}
@lec0456
lec0456
28 Mar 2017, 19:27 ( Updated at: 21 Dec 2023, 09:20 )
There is same issue on the cbot Log tab. The time is in 12hr format instead of 24hr.
There is same issue on the cbot Log tab. The time is in 12hr format instead of 24hr.
Still no response from spotware? Hello?
@lec0456