To reproduce the problem go to Algo → Backtesting → Run backtest → Generate report and then in the report you can find Parameters with wrong/empty values
Best regards
Thank you, it's a known issue and it will be fixed in the upcoming release.
We didn't have any similar reports. Did you try debugging your cBot i.e. adding logs and understand what happens after this first week? Did you try comparing by executing using your own VPS? Is there a difference in execution?
Best regards,
Panagiotis
Hi Panagiotis,
Thanks for the advise. I will add in logs and run the bots simultaneously on my own VPS and the cloud server to understand the issues. Once I spot a discrepancy I will let you know.
I did a check with backtesting, and the bot definitely misses trades. One position from last week was not taken and closed, and another one at the end of the week was not opened. See the screenshot of the trades that were taken in the backtest, but not with my bot running.
Unfortunately I cannot help you with such information. You need to follow my advise in my previous post. Add logs to your cBot to understand what happens in real time execution. Also compare it with execution on a VPS
Hello. I came across the same problem this morning. I think it is due to incorrect value of the MACD. See attached images.
MACD is the leading indicator to close positions. At 06:00 the MACD flipped negative, meaning that the position should be closed. But the value is not printed as negative, but as a formula: -8.282095762690567E-05. At 10:00 am the MACD is printed as -0,0001373403922979577 and the position is closed.
Can you look into this?
Thanks,
Vince
Any ideas? Is it possible to stop the formula results but calculate the MACD as a absolute value?
Hi there,
The way the results are printed is just the scientific notation and this is used for convenience when there are too many decimals in the actual value. It does not affect how the values are used in your cBot.
Thank you for reporting this issue. Unfortunately we were not able to reproduce this behavior. 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.
Can you please provide more information e.g. videos? You did not even mention the application you are using, you posted your issue in third party products.
We always try to keep the two applications as close as possible but there times when a feature is ready on one bot not on the other and in this case we choose to release it instead of waiting for both applications to be ready. Tools missing in each application will be released in upcoming updates.
Any chance you can provide a simpler code (the minimum required to reproduce the issue)? I have a hard time navigating through all of this code and understand the problem.
Hm, indeed on your side it is correct… My account is in USD, it is a usual Pepperstone demo account. Is it possible that “TickValue” value is filled in in the database by the broker and not by Spotware? Here is the full screenshot from my side:
Hi Alexey,
Since it is a demo account, can you share access with me? Also share the full cBot code. I will try to reproduce this using your account.
This problem should have been resolved by now. Please restart your cTrader and in case you still experience problems, please send us some troubleshooting information quoting this thread.
Best regards,
Panagiotis
Today I left my PC optimizing a bot, came back after 3h and the system was totally unresponsive. I had to kill cTrader from the task manager, it happened twice already, I don't seem to be able to complete a full optimization round.
Anything info I can gather? I am on cTrader 5.0.46.
Thanks
Hi there,
Please create a separate thread, describe the issue in detail and send us some troubleshooting information so that we can investigate further.
The SecurityListRequest returns the symbols offered by the specific broker. The number seems reasonable to me. How many entries do you expect to be returned?
PanagiotisCharalampous
09 Dec 2024, 06:56
RE: RE: Backtesting report - wrong parameters values
Hlautameki said:
Thank you, it's a known issue and it will be fixed in the upcoming release.
Best regards,
Panagiotis
@PanagiotisCharalampous