One up, seven to go!

Created at 24 Dec 2019, 11:21
Subscribe
How’s your experience with the cTrader Platform?
Your feedback is crucial to cTrader's development. Please take a few seconds to share your opinion and help us improve your trading experience. Thanks!
NI

nikolay.shirokikh

Follow

Joined 24.12.2019

One up, seven to go!
24 Dec 2019, 11:21

Hooray! It seems we are getting the multi-symbol, multi-timeframe backtesting (with caveats, but still) in the 3.7!

Great job - the platform is getting better!

So I am crossing out the first point in my list from 17th of August, 2019, as below.

What about the other points, Spotware?

 

General suggestion for critically missing features

The critically missing features are:

  1. Multi-symbol, multi-timeframe backtesting. It is just not serious without it! Mentioned by others a gazillion of times. Surely, we can implement it ourselves with FIX API. But why Automate to exist then?
  2. Program and bot autostart on reboot/crash/restart/update/accidental closure etc.
  3. A new method in cBots that would allow to control other bots, start/stop them with a configurable set of parameters and ideally also check some overall performance characteristics.
    These control cBots can be made in a separate class of bots (for safety, so only when someone wants it, they would make or use these), and it is them that could be exclusively made configurable to autostart on program/computer start.
  4. Backtesting that acquires and displays equity and balance per tick.

Less critical but still very much desirable and missing features are:

  1. Flexible timeframes. Yes, this is possible. And we do not have to have myriads of timeframes. Just pick boxes for type and ‘unit length’ and a plus/minus button to configure a desirable number of these.
  2. Auto-storing backtesting results (that can be switched on and off on demand) and the top pickable number of optimisation results. Together with the parameters. So, these can be loaded/viewed later. And these results (again) need to be per tick and not per trade. Currently, we have no idea what the actual equity flex was in between trades.
  3. Use of parallel/async methods throughout in the program (I am talking about the cTrader program itself and not just cBots) and use of OpenCL whenever possible. Currently it got better, I admit that, but from the overall performance it still looks that there were far too many shortcuts made in the base programming and it does not seem optimal at all.
  4. Folders for storing data configurable from the program. We all are annoyed to check AppData all the time.
cTrader Automate
@nikolay.shirokikh
Replies

Shares4UsDevelopment
22 Feb 2022, 12:44

RE:

nikolay.shirokikh said:

Hooray! It seems we are getting the multi-symbol, multi-timeframe backtesting (with caveats, but still) in the 3.7!

Great job - the platform is getting better!

So I am crossing out the first point in my list from 17th of August, 2019, as below.

What about the other points, Spotware?

 

General suggestion for critically missing features

The critically missing features are:

  1. Multi-symbol, multi-timeframe backtesting. It is just not serious without it! Mentioned by others a gazillion of times. Surely, we can implement it ourselves with FIX API. But why Automate to exist then?
  2. Program and bot autostart on reboot/crash/restart/update/accidental closure etc.
  3. A new method in cBots that would allow to control other bots, start/stop them with a configurable set of parameters and ideally also check some overall performance characteristics.
    These control cBots can be made in a separate class of bots (for safety, so only when someone wants it, they would make or use these), and it is them that could be exclusively made configurable to autostart on program/computer start.
  4. Backtesting that acquires and displays equity and balance per tick.

Less critical but still very much desirable and missing features are:

  1. Flexible timeframes. Yes, this is possible. And we do not have to have myriads of timeframes. Just pick boxes for type and ‘unit length’ and a plus/minus button to configure a desirable number of these.
  2. Auto-storing backtesting results (that can be switched on and off on demand) and the top pickable number of optimisation results. Together with the parameters. So, these can be loaded/viewed later. And these results (again) need to be per tick and not per trade. Currently, we have no idea what the actual equity flex was in between trades.
  3. Use of parallel/async methods throughout in the program (I am talking about the cTrader program itself and not just cBots) and use of OpenCL whenever possible. Currently it got better, I admit that, but from the overall performance it still looks that there were far too many shortcuts made in the base programming and it does not seem optimal at all.
  4. Folders for storing data configurable from the program. We all are annoyed to check AppData all the time.

5. Threadsave cTrader!

@Shares4UsDevelopment
Copyright © 2024 Spotware Systems Ltd. All rights reserved.
cTrader Ltd offers through its group of companies the cTrader platform. The information on this website is for general informational purposes only and does not constitute financial or investment advice. cTrader does not solicit retail investors. Reliance on this information is at your own risk.