I have the same problem. Has your strategy now become visible? So, yes... do you know what caused it to not be visible?
No my strategy is still not visible in strategy list and all what i co do its done. So i dont know i still have this information. no one can help i see.
Requirements for Inclusion in the Strategy List:
A positive account balance.
At least one open position.
At least one deal executed within the last 72 hours.
More than -90% in the overall ROI.
My strategy is not visible as well. Further more, I have see strategies visible with NO open position! Why is that?
The timeframe will change as soon as you start backtesting again.
Best regards,
Panagiotis
Hi Panagiotis,
I think there's some misunderstanding here. I do not want to rerun the backtest on a different timeframe. I want to for example backtest on H1, and when the backtest finishes change the timeframe on the backtest window to M30 or M15 to analyze in more detail what actually happened in the lower timeframes, while still keeping the trade history of the H1 backtest. I'm fairly new to cTrader and automated trading in general, but I would've thought this would be a common scenario for testing and finetuning?
Maybe I could to set the cBot timeframe as an input parameter (H1), and then run the backtest with M15 timeframe? Or would this not be possible?
Kind regards
Beyers
Hi Beyers,
Ok understood. Such an option is not available at the moment.
Thank you for reporting this issue. Could you pleasesend us some troubleshooting information the next time this happens? Please paste a link to this discussion inside the text box before you submit it.
Hi, off course, sorry. I created this code to get data from my local api, show on the chart and connect the different values to a line. The last error I keep getting is Error CS1503: argument 3: CannotUnloadAppDomainException convert from 'system.DataTime' to 'int' I tried everything :)
Hi Said,
The message is self explanatory. You cannot use a DateTime in the place of an int. Also you are using an obsolete method. Try something like the below instead
This is by design. If the price jumps more that one bar, then the method is only executed once for the last bar.
Best regards,
Panagiotis
Any suggestions on how to keep the drawing behavior consistent would be greatly appreciated.
Thanks
On each bar you should keep track how many bars have been added using Bars.Count. If more than one bars have been added then you would need to add the numbers using a loop for all the new bars added
We have received the exception and the issue will be solved in an upcoming release.
Regarding the SL issue, we would need the cBot code and backtesting parameters in order to reproduce this and explain what happens.
Best regards,
Panagiotis
Hi Panagiotis,
Here is the test code that produce the SL issue, I'm using Nikkei225, Hm1 for testing
using System; using System.Collections.Generic; using System.Linq; using System.Text; using cAlgo.API; using cAlgo.API.Collections; using cAlgo.API.Indicators; using cAlgo.API.Internals;
namespace cAlgo.Robots { [Robot(AccessRights = AccessRights.FullAccess, TimeZone = TimeZones.EasternStandardTime)] public class Test2 : Robot { [Parameter(DefaultValue = 10, MinValue = 0, MaxValue = 500, Step = 10)] public int lossCut { get; set; } [Parameter(DefaultValue = 10, MinValue = 0, MaxValue = 500, Step = 10)] public int takeProfit { get; set; } double volume = 0.0; protected override void OnStart() { // To learn more about cTrader Automate visit our Help Center: // https://help.ctrader.com/ctrader-automate }
Can you also tell me the broker? This usually happens when your SL falls within the symbol's spread. Please check if this is the case
Hi there,
You can use Positions.Opened event and check if the stop loss was set. If the stop loss is null you can act accordingly i.e. place it at a valid distance.
We have received the exception and the issue will be solved in an upcoming release.
Regarding the SL issue, we would need the cBot code and backtesting parameters in order to reproduce this and explain what happens.
Best regards,
Panagiotis
Hi Panagiotis,
Here is the test code that produce the SL issue, I'm using Nikkei225, Hm1 for testing
using System; using System.Collections.Generic; using System.Linq; using System.Text; using cAlgo.API; using cAlgo.API.Collections; using cAlgo.API.Indicators; using cAlgo.API.Internals;
namespace cAlgo.Robots { [Robot(AccessRights = AccessRights.FullAccess, TimeZone = TimeZones.EasternStandardTime)] public class Test2 : Robot { [Parameter(DefaultValue = 10, MinValue = 0, MaxValue = 500, Step = 10)] public int lossCut { get; set; } [Parameter(DefaultValue = 10, MinValue = 0, MaxValue = 500, Step = 10)] public int takeProfit { get; set; } double volume = 0.0; protected override void OnStart() { // To learn more about cTrader Automate visit our Help Center: // https://help.ctrader.com/ctrader-automate }
I've been looking for the optimization / backtesting section for my cBot. Since the update, I haven't been able to locate it. I'm using Desktop version 5.0.25
After the backtest finishes it is possible to change the timeframe
How do I do that? When my backtest finishes, I am unable to change the timeframe on the backtest tab, the options are greyed out. Changing the timeframe under the Algo left panel does not update the backtest window timeframe either.
Hi there,
It looks like a bug. You should be able to change it from the instance.
Best regards,
Panagiotis
Hi Panagiotis,
I can indeed change the timeframe from the instance as per you screenshot, but the problem is when you change it there the chart on the finished backtesting tab is not changed, it stays on the timeframe of when you ran the backtest.
Kind regards
Beyers
Hi Beyers,
The timeframe will change as soon as you start backtesting again.
PanagiotisCharalampous
19 Jun 2024, 05:05
RE: RE: RE: RE:
Investec said:
Hi there,
How do you know that there is no open position?
Best regards,
Panagiotis
@PanagiotisCharalampous