nobulart
06 Dec 2017, 12:29

RE: RE:

Thank you Andrey. I suspected that this might be the case. I look forward to the next update :-)

Andrey Pisarev said:

Hi Nobulart,

The problem is that cAlgo does not support decimal volumes. It causes following issues with BTCUSD and ETHUSD:

• You can't open positions or create pending orders with decimal part via cAlgo APIs
• You won't get correct value for existing Position, PendingOrder or HistoricalTrade if volume has decimal part
• Backtesting for this symbols is not working as Symbol.VolumeStep is equal to 0 after casting from double to long. That's why you get DivideByZeroException

We are fixing this issues. But this fixes will be in the next release of cTrader.

Kind Regards,
Andrey

nobulart
06 Dec 2017, 09:47

I'm experiencing the same problem when attempting to place orders on ETHUSD. Placing an order with a volume between 1ETH and 99ETH crashes with a division by zero error as above. Orders for 100ETH or greater don't result in a crash, but the orders aren't executed, resulting in no trades being placed.

nobulart
06 Dec 2017, 08:32

I see that most queries on this forum are responded to within 2-24 hours by a Spotware representative. This seems like a relatively straightforward query - is this a bug in the cAlgo code or am I doing something incorrectly? Have I posted this in the wrong place? A response would be very much appreciated. Thank you.

nobulart
16 Sep 2015, 10:56

nobulart
22 Jun 2015, 19:54

RE: RE: RE:

aimerdoux said:

nobulart said:

Spotware said:

Dear Traders,

We are aware of this issue with the tick data backtesting. Our team is working on resolving this issue as soon as possible.

 

 

 

Thanks for the update folks. Good to know that the problem is being addressed.

nobulart do you know why the robot Golden Dragon II doesnt run the bactesting?

Hi. As mentioned in the responses from spotware (above), there are errors in the backtest data which are causing problems. Most of the issues appear to be with historical data starting from around the beginning of June. I I don't run backtests further forward than the end of May, they generally work.

nobulart
09 Jun 2015, 14:42

RE:

Spotware said:

Dear Traders,

We are aware of this issue with the tick data backtesting. Our team is working on resolving this issue as soon as possible.

 

 

 

Thanks for the update folks. Good to know that the problem is being addressed.

nobulart
08 Jun 2015, 09:37

Just confirming that I've noticed the same type of corruption in the backtest tick data on several pairs. Time-offset trades, sometimes occurring in long sequences of consecutive winning or losing trades.

nobulart
06 Jun 2015, 23:27

RE:

stevefromnaki said:

tick data backtesting seems to be working again for me.

 

Is it working again for anybody else?

Yip. Up and running again. :-)

nobulart
04 Jun 2015, 13:49

I can confirm that reinstalling cAlgo does not fix this. This appears to be a server-side issue. Spotware folk? Anyone out there?

nobulart
03 Jun 2015, 18:23

Confirmed

Same problem here. Stopped working sometime in the past few hours. Occurred on multiple platforms (WinXP and Win7).

nobulart
21 Oct 2013, 18:29

I'd be happy to see all of these points addressed as well. Being able to export a trade history for external analysis is a crucial missing feature.