cAlgo_Development
16 Aug 2013, 16:15

We are already in progress with this. We plan to release multi-timeframe feature in two-three weeks.

cAlgo_Development
16 Aug 2013, 11:43

Yes. We understand that you can expect indicator to use its own timezone, but currently indicator timezone will be ignored. Indicator timezone is only applied if you add indicator directly to a chart.

cAlgo_Development
15 Aug 2013, 14:13

• In cAlgo (robots / indicators) Server.Time returns UTC time by default.
• The cT/cA interface allows you to select an offset, which displays in orange if not set to your local time. That's right.
• The interface where you select an offset shows the word "Server Time" - it is obsolete, in fact it means nothing, just ignore it.
• Robot's TimeZone is used for all indicators that are created by the robot. This is how it is implemented now.

cAlgo_Development
12 Aug 2013, 14:11

We do not plan such functionality, but you can implement a robot closing a position at specified time in cAlgo.
 

cAlgo_Development
12 Aug 2013, 12:17

We plan to implement tick-based candles built using specified number of ticks (for example one candle is 100 ticks). For now we do not have clear estimates.

cAlgo_Development
12 Aug 2013, 12:13

If cAlgo is disconnected it is impossible to open positions because you can not send your request to the server. You will not also receive OnTick and OnBar events in this case. When it is reconnected, you will start to receive events and it will be possible to execute new trades.

If you close cAlgo (or it is totally crashed) your code is no longer executed, so now trade operations will be executed (except server-side SL, TP and Pendin Orders). When you restart cAlgo  robots will be stopped by default, so you need to run them manually. In nearest future we are going to implement an ability to restarts robots automatically when cAlgo is restarted.

cAlgo_Development
06 Aug 2013, 10:11

Thank you. What we plan to do in near future is integration with Visual Studio. This will allow you to use different languages and the most advanced development tools.

cAlgo_Development
31 Jul 2013, 16:02

The idea is clear. We plan to add one more property to position: Comment. Most probably it will allow to do what you want .

cAlgo_Development
31 Jul 2013, 09:46

Advanced Protection (Trailing Stop Loss) was implemented: /forum/whats-new/1317

cAlgo_Development
31 Jul 2013, 09:27

Thank you. Will fix it.

cAlgo_Development
26 Jul 2013, 15:00

Hi, the idea is really nice and we actually have similar idea - running robots on cloud directly from cAlgo or web UI. But this is not the nearest future plan. Right now the only solution is to use VPS to run cAlgo.

cAlgo_Development
26 Jul 2013, 11:47

Right now backtesting does not check your Equity and Free Margin. This is not very good and in case you have long-living positions you can miss margin call. From our point it is clear that we must improve our backtesting to handle such situations. From trader's point, first of all you can implement margin checks inside your robot, during  backtets it will realize that there is no free margin you will handle this.

As for data, I agree with susantasaren, there is no missing trendbars, but there are gaps in prices that happen sometimes in real life.

cAlgo_Development
24 Jul 2013, 10:46

Thank you. We will try to update it more often.

cAlgo_Development
18 Jul 2013, 18:07

Another major thing to add would definitely be 'magic number' support, or otherwise some kind of trade metadata that could identify, for example, which EA a trade belongs to, which particular strategy of an EA that trade corresponds with, or even the specific parameters of that trade.

We already have similar thing. You can specify Label when creating position or order. Later you can identify your positions using this label.

cAlgo_Development
18 Jul 2013, 14:44

Thank you for your questions. I'll try to reply.

1. There is no way to download more history.

 

You can't do anything without data.

We understand it. Right now we released new version that have access to more data (actually 2+ years). Next step that we plan is to provide much more data or implement an ability to youse your own data in backtesting. This question is a high priority quuestion for us.

2. Algos only have access to data from chart they are on.

 

Why do these platform developers think that an algo is some sort of indicator that you attach to a chart? The fact that they've built a new platform with such limitations is worrying.

This is correct and I completely agree with this. We had historical reasons for this, and now we understand that we wust rework this. Next thing we do in cAlgo is implementing access to data of multiple timeframe and multiple symbols.

3. Algos have to be started manually each time you launch the platform.

 

Useless.

If we understood correctly, you'd like to be able to restart cAlgo and restart all robot instances that were active before restart automatically. This is a valid request that makes cAlgo more useful in automated environments (for example on VPS hosting). We've just started to work in this direction and suggested feature will be deffinetly implemented.

4. Algos don't have access to the trading history.

 

Some trading strategies need to know about previous closed positions, in case there were deposits/withdrawals.

This is a "must have" feature. We haven't implemented it by the following reason: We are now migrating to a new trading domain model that will make cTrader more transparent and flexible for traders. We will provide complete information on order execution process. When this new model is delivered we will give access to all this information tin cAlgo.

cAlgo_Development
16 Jul 2013, 15:40

We do not have a plan to implement an ability to chage labels of existing orders or positions. The reason is that labels migrate from one entity to another. if you have labeled pending order and then the order was execuded and position created it has the same label. What should happen if you modify label of the order after that?

Can you provide an explanation why do you need this functionality?

cAlgo_Development
16 Jul 2013, 15:07

Thank you for the bug report. We'll fix it.

cAlgo_Development
15 Jul 2013, 19:06

Right now the only log you can use is log in robot's "Log" tab. If you need more information you can contact with your broker's support service.

We also have a plan to implement mopre detailed logs in cTrader and cAlgo in the nearest future.

cAlgo_Development
15 Jul 2013, 18:58 ( Updated at: 21 Dec 2023, 09:20 )

This is strange. It works properly on all PCs that we have tested.

Can you send us the example of your output file? Do output from cAlgo backtesting history tab and cTrader history tab have the same blank cells? We also need to now your Windows culture and version of Microsoft Office.

You can post everything here or send to engage@spotware.com

cAlgo_Development
15 Jul 2013, 18:50

There can be several reasons:

1. Using functions not supported properly in backtesting such as system timers or depth of market data
2. Performing some slow operation in OnTick method, in real life it's ok, but backtesting can become very-very slow so you will have to wait hours or days for the results
3. If there is some error in backtesting it is shown in backtesting log

If you post your robot here or send it to engage@spotware.com we will help you to resolve this issue. You can also give us some more details, what do you see when trying to backtest? Is backtesting progress bar completed?