jobenb
04 Jan 2015, 05:28

RE:

olddirtypipster said:

Due to round off errors while using float or double, it is advised that monetary values be represented using the decimal type.

Could someone at Spotware please explain why they decided to use double to represent their prices then? Would this not cause significant issues when performing certain calculations?

Very concerned. considering what this API is intended to do, and the finances that are at stake for professional use.

I have dealt with precision issues many times in the past and as long as the calculations are done with high precision decimals, then totals and averages will be fine, however ratios such as exchange rates are in fact acceptable to be double as the exchange ratio itself does not require precision beyond the precision limits of a double data type. 

jobenb
04 Jan 2015, 05:11

I agree. This would be an awesome new feature. I know that Spotware has been planning this for over a year now.

I think it would be a great idea to enable all objects to be c# readable from the chart not just trend lines...

jobenb
18 Dec 2014, 10:44

RE:

jobenb said:

Hi Spotware

Today I received numerous cBot crashes with the same error... - cBot crashed: Error #65140095

What does this mean?

Thank you.

Kind regards,

 

jobenb

Any answer from Spotware???

jobenb
10 Dec 2014, 14:16

RE:

Spotware said:

Hello,

This bug has been fixed and you are now able to trade micro lots once again.

Regards

Thank you Spotware!!! :-)

jobenb
09 Dec 2014, 15:12

RE:

Spotware said:

Dear Trader,

Please contact your broker regarding this issue.

Dear Spotware

The Spotware cTrader & cAlgo currently requires a minimum of 0.1 lots (10000) in volume per trade. You can also now only increase your lot size in increments of 0.1 lots (10000). 

This never was the case before this week. In the past you could place 0.01 lots (1000) volume as a minimum with the ability to also increase it with increments of a 1000.  

Please could you confirm if this feature of micro lot trading has been removed and why or if this is a bug.

I look forward to your reply.

Thank you.

Kind regards,

jobenb

jobenb
09 Dec 2014, 10:09

RE: RE:

oktrader said:

Spotware said:

Dear Trader,

Please contact your broker regarding this issue.

 

I'm haveing the same problem with spotware cAlgo. Now I can only use 0.1 lots, instead of 0.01 lots as a minimum volume.

Yes I agree.

Spotware cAlgo and Spotware cTrader have both now the same issue! This does not seem like a Broker issue but a Spotware issue!

Spotware, please don't always assume it is a Broker issue when your own platform has the same issue.

jobenb
08 Dec 2014, 10:28

Hi cAlgo

Last week my robot was able to place orders with a volume of 1000. Now it seems that it has been changed to 10000. Why is that? Is it an error? NormalizeVolume now makes 3000 to be a minimum of 10000 even when the broker advertise 0.01 lots.

Can we have our micro lots back please.

Thank you.

jobenb
25 Nov 2014, 13:01

RE:

badmonkeyface said:

Hi All,

Is it possible to download the backtest data to an external format through the platform?

Essentially I'm trying to get the backtest data in a format such as CSV to run through an external system to then feed back into an indicator.

Thanks.

There is unfortunately no such function within the platform.

One option would be to write a cBot that writes every tick in OnTick to a file and then run a backtest with the historical tick data that you want to export.

jobenb
13 Nov 2014, 14:11

RE:

Invalid said:

Hi jobenb, 

There's a feature request Walk Foward Optimization

I know mate, I don't have enough "power" to vote anymore. I used all my votes. :-(

However I want to elaborate on it here so that I can explain a scenario / use case for it and maybe let people realise how valuable this would be! People focus too much on backtesting only while forward testing is where you make or break it!

jobenb
08 Nov 2014, 10:21 ( Updated at: 21 Dec 2023, 09:20 )

Dear Spotware

When I went through some manual demo trades this weekend, I noticed a weird close on the NZDCHF which shows that it was closed at a price above the chart, in other words the candle does not reach that price. How is this even possible? Was this a freak tick from the broker which was corrected later, however the trade was still closed? What would have happened on a real account?

jobenb
03 Nov 2014, 16:10

RE: RE:

jobenb said:

jobenb said:

Hi Spotware

I recently asked a question under a post about issues running HFT algorithms on cAlgo, but I cannot locate it to see your answer. Could you please tell me where it is or why you have removed it from the support thread?

Thank you.

 

 

Google should still have a cached page.

https://www.google.com.au/#q=http:%2F%2Fctdn.com%2Fforum%2Fcalgo-support+HFT

This was the link:

/forum/calgo-support/3479

Dear Spotware

I just googled cAlgo and HFT and I saw that the missing thread of mine appeared. I completely understand if you do not want the thread to be first on google when typing those terms and if that was the reason it was removed then I fully understand. I just don't want this issue to be swept under the carpet as I believe that it will be an important quality for cAlgo to succeed.

Make no mistake, I am a big fan of what you do and what you have achieved! I absolutely love working on your platforms and I will continue to send you issues I pick up as I believe that you will become the best out there, but to actually reach it - you need to become aware of and fix these issues that arise when the platform is stretched to its limits.

New features are great, but when there is not constant refactoring and improvement on stability of current features then the debt might just pile up, which again could prevent cAlgo to become the best out there which it will become.

Thank you.

jobenb
03 Nov 2014, 15:59

RE: RE:

jobenb said:

Spotware said:

Hello jobenb,

Unfortunately we cannot reproduce the described issue with Optimization. Could you please send code of your cBot to troubleshooting@spotware.com? We will use it for troubleshooting purposes only.

Hi Spotware

Please reproduce with the following:

1. Use a high frequency, always trading bot such as a cBot that opens 10 pending sell orders and 10 pending buy orders and then keeps 10 pending buy orders and 10 pending sell orders in place even when those pending orders get triggered by price, so that you always have pending orders in place as price moves and positions pile up.

2. Optimize that cBot using 7 different currency pairs and 6 optimization parameters each - all at the same time.

 

Unfortunately I cannot provide you with the proprietary strategy, however I am willing to assist in any other way I can to reproduce this and you are welcome to ask me any questions. :-)

Let me know how it goes by following the above two steps. The error should manifest itself under heavy load.

Thank you!!

Dear Spotware

I read what I wrote above and realised No. 1 probably does not make a lot of sense, so I will elaborate on it.

The cBot needs to be high frequency and therefore engage the CPU all the time. a Classical Hedge based strategy would be sufficient where the cBot opens pending buy orders and sell orders spaced 5 pips apart. Once these orders get filled it will then replace them with new ones so that there are always a pending order at each level of the grid 5 pips apart. The positions will grow, but limit the grid to only 10 orders above and below the current price. Modify as price moves and delete orders that falls outside this 10 order above and below "buffer".

This will cause instability in the platform when optimized in parallel with (number of cores - 1) more currencies. The UI becomes unresponsive and the platform disconnects. a Possible fix would be to increase the priority of the UI thread, however I am sure your engineers are more than capable of finding and fixing these issues. :-)

jobenb
03 Nov 2014, 12:34

RE:

jobenb said:

Hi Spotware

I recently asked a question under a post about issues running HFT algorithms on cAlgo, but I cannot locate it to see your answer. Could you please tell me where it is or why you have removed it from the support thread?

Thank you.

 

Google should still have a cached page.

https://www.google.com.au/#q=http:%2F%2Fctdn.com%2Fforum%2Fcalgo-support+HFT

This was the link:

/forum/calgo-support/3479

jobenb
03 Nov 2014, 12:28

Hi Spotware

I recently asked a question under a post about issues running HFT algorithms on cAlgo, but I cannot locate it to see your answer. Could you please tell me where it is or why you have removed it from the support thread?

Thank you.

jobenb
03 Nov 2014, 12:21

RE:

Spotware said:

No, cAlgo doesn't save optimization state between optimization sessions.

Will this become a feature in the near future?

jobenb
03 Nov 2014, 11:47

RE:

Spotware said:

Hello jobenb,

Unfortunately we cannot reproduce the described issue with Optimization. Could you please send code of your cBot to troubleshooting@spotware.com? We will use it for troubleshooting purposes only.

Hi Spotware

Please reproduce with the following:

1. Use a high frequency, always trading bot such as a cBot that opens 10 pending sell orders and 10 pending buy orders and then keeps 10 pending buy orders and 10 pending sell orders in place even when those pending orders get triggered by price, so that you always have pending orders in place as price moves and positions pile up.

2. Optimize that cBot using 7 different currency pairs and 6 optimization parameters each - all at the same time.

Unfortunately I cannot provide you with the proprietary strategy, however I am willing to assist in any other way I can to reproduce this and you are welcome to ask me any questions. :-)

Let me know how it goes by following the above two steps. The error should manifest itself under heavy load.

Thank you!!

jobenb
03 Nov 2014, 11:37

RE:

Spotware said:

Hello jobenb,

Do you use system timer's in your cBot? Do you run your code in a separate thread? Do you see any error in cBot Log or Windows Journal?

Hi Spotware

No timer, no multithreading and no errors unfortunately.

jobenb
02 Nov 2014, 13:42

Hi Spotware

I noticed something odd today. While I was trying to optimize some of my strategies, I noticed that when I stop an optimization run that has been going on for quite a while, then nothing happens to the CPU percentage the instance was using. It does not decrease as would be expected. Any reason for that?

I have also had occasions when I would close the cAlgo window but in task manager cAlgo would still be running in the background? Is this by design?

I am sorry to say, but the experience I had so far with cAlgo is that it is not very stable under heavy load.

Are your thread prioritizations optimized so that the UI thread has the highest priority?

Here is maybe something to consider:

http://stackoverflow.com/questions/2231881/changing-thread-priority-to-make-my-program-and-computer-more-responsive

Thank you!

jobenb
01 Nov 2014, 07:05

Hi,

Use the web cTrader. That should work on a mac. 

jobenb
01 Nov 2014, 06:55

Hi Spotware,

I forgot to add. I was optimizing multiple currency pairs at the same time, so please test the optimization functionality running multiple concurrent optimizations. :-)