Backtests are added and added and added (bug)

Forums › ProRealTime English forum › ProRealTime platform support › Backtests are added and added and added (bug)

Viewing 11 posts - 1 through 11 (of 11 total)
  • 01/24/2021 at 2:19 PM #159244
    PeterSt

    After describing the one bug, I automatically run into the other (time consuming) one …
    See Attachment.

    The description of the previous (won’t save program code”) bug, caused to restart the platform several times. Well, the attachment shows how many times that was. And it will grow as long as I don’t throw out the previous ones (from the previous session(s)).
    Btw, it also causes the arrows to receive different colours each time. Maybe this is a convenient feature for someone, but … not for me and not how I can see that.

    So only the top two are the actual ones. Yes, I now that by now. But if you don’t you throw out the top one as well, and gone is your graphing area or even Detailed Report (connected to the Equity Curve panel – see other bug report). Very hard to get back if you don’t know how to … (yea, restart the platform is an easy one).

    As a side effect, all these backtests really still exist. I mean, at the next startup they really all will “back test”. Maybe now we know why at startup the number of bars is reset to 10K (yet another bug described in another report). Otherwise they’d all do 1M bars. And they would all do exactly the same (this is not 100% correct, but alas).

    Anyway, on each one you can click and close the panel. See 2nd Attachment. After closing them all, start with resizing your screen again (grrr). Yes, do that with your no-grabbing mouse (grrrr again – see yet an other bug report).

    PS: People wonder why I did not report these things earlier on. Answer : because it is undoable, so many of these enormously OBVIOUS matters exist. So PRT, I say again : can’t you please look into ALL these matters yourself, instead of letting customers struggle (that’s what it is the most explicitly – struggle !) or let me struggle (time time time) to report it ?

     

     

    01/24/2021 at 2:39 PM #159254
    PeterSt

    Below (Attachment) you see all the BackTests at work.
    OK, not all, because most fall under the screen.

    01/24/2021 at 2:44 PM #159257
    GraHal
    PeterSt wrote:

    As a side effect, all these backtests really still exist. I mean, at the next startup they really all will “back test”.

    But why don’t you close the backtest before you close the Platform?

    Then when you open the Platform again it would be a few seconds only to click on your chosen Algo and view the equity curve?

     

    01/24/2021 at 3:01 PM #159263
    PeterSt
    GraHal wrote:

    But why don’t you close the backtest before you close the Platform? Then when you open the Platform again it would be a few seconds only to click on your chosen Algo and view the equity curve?

    In the situation I just (had to) run through ? I had better things to do (like closing and opening the platform 8 or so times).

    Of course I understand. But it is not about that. It is about all what adds to make a a pain to only restart the platform. It really is a pain you know. I didn’t tell yet that I currently have three (only three !) strategies running, and that I need to do this for all of them.
    And close the backtest when closing the platform ? why ? I don’t want to close the backtest – I want to restart the platform (for any reason). But sure, if this is the effect, I’d want to close the backtest I actually don’t want to close. But …

    [loop]

    🙂

    01/24/2021 at 3:26 PM #159265
    GraHal

    Okay gotcha now!

    This is relevant to this Issue … how many Systems have you got listed in the Backtesting & AutoTrading window?

    01/24/2021 at 3:33 PM #159267
    PeterSt
    GraHal wrote:

    how many Systems have you got listed in the Backtesting & AutoTrading window?

    Now I don’t know which window(s ?) you mean ? (sorry !)

    01/24/2021 at 3:40 PM #159268
    GraHal

    I should have said Indicator & Trading Systems window (attached)

    01/24/2021 at 3:52 PM #159270
    PeterSt

    40 or so …
    Edit : I am a good estimator. See attached.

    01/24/2021 at 4:41 PM #159277
    GraHal

    I used to get loads of weird Issues, most of which I do not experience since I cut my Systems down listed in the window I show above.

    Try it you may be surprised, it may help the hogging RAM Issue and the not saving Issue?

    I am not just referring to RAM, but to the maybe less than 100% effective Indexing when you are trying to save!

    It takes seconds to export to your PC … where you can even save them in folders!

    1 user thanked author for this post.
    avatar PeterSt
    01/24/2021 at 6:18 PM #159286
    PeterSt

    GraHal, I’ll be d*mned if you are not correct.

    The last thing I did just prior to your last post in here, was copying to again a new system so I could mess in there with something new again. From then on I hardly could work any more. Even after not running any BackTests at all, the Editor would play up against me. Up to failure. So this was new to me.

    Then following your advice I removed 19 of the strategies in there, et voilá. The immediate difference is that the system now initialises to just under 5GB instead of over 6GB. See attachment. After over 5 minutes it is still at 5GB so there it stabilises. If I then start to run BackTests on two instruments (same BackTest), even up to 100K bars no graph commands added or removed, the first I notice is that it is way faster (something like over 5 times) and the next thing I see is that *that* stabilises at 6.7GB or so.

    The same thing IMO will apply as what I wrote originally – as long as that invisible threshold is not crossed, you can do what you want forever (not sure whether this is really so). But with this the base is enormously lowered – theoretically with a 1.2GB.

    So … PRT … What’s up ? is this to be expected ?

    For other people, I think I have an other exhibit which may be telling you, you crossed lines. Look (3rd attachment) :
    When the system is near limits, it starts to automatically NOT show the best option from that Optimisation list. Even if you have only one (fixed variable) option in there. You would need to click that line after the calculations finish. The past weeks I saw that getting worse and worse, up to today that it would not want to work at all any more (like this morning I hardly could do something from the start). And now ? it happily shows the result in the chart of the instrument, automatically.

    GraHal, you’re gold.

    PRT, two bugs spring from this :

    1. The system not behaving once that threshold is crossed (hence try to solve that internal limit);
    2. The system consuming a lot of memory just and only because of too many strategies / codes (/ Indicators ??) in there. Maybe that can be solved as well.
    01/24/2021 at 6:41 PM #159292
    GraHal
    PeterSt wrote:

    GraHal, you’re gold.

    hahah glad to help!

    I’ve been through all this sh1t 3+ years ago and found my own workarounds to a lot of Issues!

    I’ve told a few on here about problems when too many Systems are listed in the window I posted above, but they didn’t believe me!

    Up to now it had only been a hunch of mine, but now – after your tests – we have proof!!

    Good Work to both of US! 🙂

    1 user thanked author for this post.
    avatar JC_Bywan
  • Author
    Posts
Viewing 11 posts - 1 through 11 (of 11 total)

Find exclusive trading pro-tools on ProRealCode Marketplace

Similar topics:
backtests not saving results when platform closed and reopened
bladescalper indicator and screener : updates backtests and customizations
creation of backtests and automatic trading systems

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