What's New in cTrader Automate API 4.0

Hi dwalkhul,

Yes you are correct.

Best Regards,

Panagiotis 

Join us on Telegram

Timeline for Python support

Is there any Timeline estimation for implementing a later version of .Net that would support using Python for Artificial Intelligence cBots?

Previously, Panagiotis and Paul said that 4.0 would implement .Net Core but that got cancelled. 

Current framework is still .Net Framework 4 Client Profile which is extremely old and not compatible with anything current, let alone anything in current use.

Without upgrading to a current .Net Framework I don't see why this version is a major version from 3.8 to 4.0, am I missing something?

Hi prosteel1,

The plan is for v4.2. Hopefully it will come in the summer.

Best Regards,

Panagiotis 

Join us on Telegram

RE: Timeline for Python support

Guys you can just upgrade any bot to use .net versions I use .net 4.7.2 but you could use 4.8 if you install the framework.

I have developed a generic ML framework using ML.NET with AutoML. AutoML with Python is so slow its a joke. I have developed generic algos as well and these work in almost all markets and conditions. Although most people build algos that suit specific conditions but dont work very well. But my generic algos work even much better than the ML.

prosteel1 said:

Is there any Timeline estimation for implementing a later version of .Net that would support using Python for Artificial Intelligence cBots?

Previously, Panagiotis and Paul said that 4.0 would implement .Net Core but that got cancelled. 

Current framework is still .Net Framework 4 Client Profile which is extremely old and not compatible with anything current, let alone anything in current use.

Without upgrading to a current .Net Framework I don't see why this version is a major version from 3.8 to 4.0, am I missing something?

RE:

PanagiotisCharalampous said:

Hi abtraderdemo,

The plan is for Q3 2021.

Best Regards,

Panagiotis 

Join us on Telegram

This version will be with .NET 6.0 LTS?

Microsoft publish a preview verion :

Tick Timeframes now in the Tick Database!

Great to see the Tick Timeframe Names are now in the database so they can be referenced by name. My previous Workaround for this which I only implimented yesterday was to create an array with the index as the hirachy and during Optimisation mode to check if the analysis timeframe had a lower index than the trading timeframe and if it did to do Stop() so it didn't use up time in the optimization. The result was it iterated through all combinations of timeframes where it analysed on longer timeframe and entered on shorter timeframe.

This update means that tick timeframes can be hard coded without having to manually select them by making them a parameter :) When using my multi time frame method which seperates the chart timeframe from the analysis and trading timeframe, Multi time frame optimization is now quite easy! 

This will likely help a great deal in making the selection of timeframes to use more plastic during a cbot running - changing timeframes while its running based on volatility for eg. :)

In 3.8 the right side of the screenshot would show all the timeframes as 1 hour, and the tick timeframes would have to be selected manually for this to work, but because 4.0 now has the names of the Tick timeframes in the database,  they now map correctly rather than defaulting to 1 hour because the names weren't in the database before:)

I'm looking forward to figuring out dynamic Timeframes now :) Great job Spotware! 

I'll try to post an example multi timeframe optimization cbot in the next few weeks that makes use of this upgrade.