Problem with ProBackTest, records disappear during optimization

Forums › ProRealTime English forum › ProRealTime platform support › Problem with ProBackTest, records disappear during optimization

Viewing 15 posts - 16 through 30 (of 30 total)
1 2
  • 10/19/2020 at 3:22 PM #147768
    GraHal

    For info … I just did a backtest on one of my Algos and it all acted as normal.

    I  can’t explain why, but it would be worth trying different variable values in the optimiser to see if the Issue ceases?

     

    10/19/2020 at 3:40 PM #147771
    Nicolas

    We are still investigating .. please be patient 🙂

    1 user thanked author for this post.
    avatar GraHal
    10/20/2020 at 7:54 AM #147818
    IcaroFM
    GraHal wrote:

    I concur with @IcaroFM findings, check …

    1. Image 1 during backtest … shows lots of results at 1808.8 and 1797.7 … as highest Gain result.
    2. Image 2 at end of backtest … shows only 1389.3 … as highest Gain result.

    What is going on??

    Hi @GraHal

    I was looking your results, but are different from mine. Have you changed something in the code?

    10/20/2020 at 9:46 AM #147862
    GraHal
    IcaroFM wrote:

    Have you changed something in the code?

    No changes, but my backtest was probably over less bars than yours?

    I think I had the bars set to 200.

    10/20/2020 at 11:18 AM #147884
    Nicolas

    The issue is being fixed, please wait until the next update.

    2 users thanked author for this post.
    avatar IcaroFM, avatar GraHal
    10/20/2020 at 7:06 PM #147953
    OboeOpt

    Can I trust the results in backtest and optimization right now or should I wait for a update?

    10/21/2020 at 8:00 AM #147972
    IcaroFM
    Nicolas wrote:

    The issue is being fixed, please wait until the next update.

    Thank you Nicolas. I’ve some algo in standby for this bug. Could you write here when the bug fix is online?

    10/29/2020 at 9:49 PM #148938
    IcaroFM

    Hi @Nicolas, do you have a forecast for the next update?

    10/30/2020 at 1:24 AM #148952
    robertogozzi

    @IcaroFM

    yours is a sort of abuse of the “@” sign, do not use it to urge some attention or an answer after just a few days!  Wait a bit longer before urging replies, if ever needed!

    Moreover, please do no abuse QUOTING, as well. Writing thank you Nicolas is enough to know you are referring Nicolas, quoting (NEVER quote code, please) makes posts longer and a bit annoying.

    Thank you 🙂

     

    10/30/2020 at 8:26 AM #148973
    Nicolas

    There were few updates since my post, but not seen anything about that in the changelog. Will let you know.

    1 user thanked author for this post.
    avatar IcaroFM
    10/30/2020 at 8:27 AM #148974
    IcaroFM

    Hi Roberto, I used the @ symbol to make Nicolas have notification of the request. It’s been 10 days since this important bug was fixed, honestly it doesn’t seem too short to me to ask when the fix will be released. My last question I asked because I did not receive an answer to the penultimate and there was no answer to the interesting question of the other user (are the results of all the backtests at risk?). I know that Nicolas is very busy but I only need one answer, I seem to have always asked questions with courtesy. I will be more careful in the future in using the forum. Thank you

    10/30/2020 at 1:48 PM #149008
    Nicolas

    The bug fixing is “in process” status, it should not take long to get it right. Thanks for being patient 🙂

    10/30/2020 at 8:57 PM #149059
    OboeOpt

    I appreciate that a fix is on it´s way and I understand that it can take some time. What I don´t understand is:

    -Is it not recommended to perform backtests at the moment because the results can be wrong?
    -Can backtests performed X days/weeks/months before this problem was discovered be wrong? (I had some problems with backtest results before this that I have written about in other threads)

    11/13/2020 at 1:39 PM #150378
    IcaroFM
    Nicolas wrote:

    The bug fixing is “in process” status, it should not take long to get it right. Thanks for being patient 🙂

    Hi Nicolas, to know if the release came out I have to look at the date on this window?

    12/11/2020 at 2:19 PM #153400
    IcaroFM

    It seems to be ok with PRT 11 version. Thank you

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 30 total)
1 2

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
bug probacktest duplicate limit orders
créer probacktest avec indicateur ssl hybrid
customizing optimization report (adding variable)
high low mid during trading hour
how do i speed up backtest optimization?
nested loops problem
optimization oddities with uneven numbers
optimization of systems not possible
optimization results different from backtest
optimization speed with back test very slow

Create your free account now and post your request to benefit from the help of the community
Register or Login