Bug: optimizing does not work properly in historical mode

Forums ProRealTime English forum ProRealTime platform support Bug: optimizing does not work properly in historical mode

Viewing 7 posts - 1 through 7 (of 7 total)
  • #172420

    Hi,

    If I select a previous period (e.g. Jan-1 2017 to Jan-1 2019) when the graph is in historical mode, it will show this period on the graph, so you think all is OK. But there is a bug: it keeps using the more recent data (Jan-1 2019 to current) as well.

    If you start optimizing it will include this data without you knowing it (so the results shown are incorrect for this period!). The result shown on the ‘detailed report’ also includes this more recent data and is also incorrect.

    How to recognize it: if you follow the equity line displayed on the graph, it will show a spike or drop at the end. This is the change from the end of the graph to the end of the data used in calculating (e.g. jump from Jan-1 2019 to June-22 2021). The simulated future orders will also show up (combined) on the last bar with a future date on them.

    When it happens: it does not happen all the time. I have the impression it occurs after you first run a backtest on recent data and then change the graph to older data. It is independend of the coding or which strategy I use. The first time I noticed this was in Q3 last year.  I mainly work with 1 minute strategies on NQXXXX with a premium account. You should be able to replicate this with any kind of strategy.

    How I solve it (quick fix): I use ‘date > datamax’ as exit condition in the Strategy code. However, as it still uses the more recent data the optimisation calulation time is considerably longer than it should be.

    It would be nice if there is another way to solve this, or to include this in a version update.

    Best regards

    #172423

    Please alert PRT of this Issue using the link below.

    https://www.prorealtime.com/en/contact?

    Provide a brief summary and then state … refer to Topic link for full details.

    https://www.prorealcode.com/topic/bug-optimizing-does-not-work-properly-in-historical-mode/

    PS

    The screen shot in your post above does not leap out at me as illustrating the Issue … but maybe that is just me not spent enough time reading your text?

    #172426

    How many bars are you using?

    On 1 min TF and 100k bars, I only get back 22 March 2021, so I would find it impossible to go back to Jan-1 2017 to Jan-1 2019 (as you state).

    You would think we could choose a 100k bar period in the past, but no we have to use the most recent 100k bar period. Is this the source of the Issue you are seeing??

    #172427

    I’m using 1mln bars with a premium account, so this is not impossible. As far as I know, you will also need a premium account to get the graph in historical mode.

    If you look at the screenshot, you can see the date of the latest bar is early 2019, showing orders from june 2022… this should not be possible.

    #172441

    Hello,

     

    In order to allow ProRealTime to analyze your platform, please send them a technical report by following these instructions:

    • As soon as you encounter the issue, go to the “Help” menu on the ProRealTime toolbar.
    • Click on “Technical support”
    • Select “Code”
    • In the “Concerned code” field, enter the name of the code related to your problem.
    • Give as many details as possible, explain the issue you are having in the text box and mention the name of the code you are referring to.
    • Click “Send report”

     

    This will send a report containing technical information concerning your platform, which will allow their technical team to run a diagnostic analysis of the issue you have come across.

    Best regards,

     

    #172442

    Sure, I will do that. But as mentioned, this is not realted to the code. So how will this help?

    #172454

    To make it even more clear: here is an image of my dashboard showing 15 years (!) of backtested results on a 1min graph from 1-Jan-2006 tot 1-Jan-2008.

     

    I have now sent an e-mail as suggested by GraHal en reported this in the platform as suggested by RafaelN.

     

    1 user thanked author for this post.
Viewing 7 posts - 1 through 7 (of 7 total)

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