Good Work Practices, Tricks & Tips

Forums ProRealTime English forum ProOrder support Good Work Practices, Tricks & Tips

Viewing 15 posts - 1 through 15 (of 19 total)
  • #129620

    erratic issues with the “save” option on my platform

    I get the same. Yesterday I lost a full day’s work – optimisations that were written into the code simply disappeared the following day, in spite of being saved several times.

    #129622

    optimisations that were written into the code simply disappeared the following day, in spite of being saved several times.

    Sorry to hear that, I know too well how frustrating that is! Do you use Mac or PC?

    What I do now is copy and save everything that’s important from a system into a Text Edit, that includes the settings. I even tried saving the startvalue and max etc to the systems notes recently only to find the next day it hadn’t saved them and still had the copy of the code in the notes section that I’d already deleted so I could put the setting in there… smh…

    From October last year when the problems started I don’t trust anything PRT saves, it’s just it seemed to be behaving itself of late and I got out of the habit of using Text Edit so much.

    #129631

    I get the same. Yesterday I lost a full day’s work

    Out of interest … how many Systems do you have listed / showing on the screen attached?

    And are you on a Mac or a Windows PC?

     

    #129633

    I’m on PC. Total systems is + 300. Does that matter?

    #129634

    Does that matter?

    300 Systems stored in the backtest window?

    Going back 3 to 4 years … I used to have loads of weird happenings on PRT, but after I exported / cleared out my stored Systems (I had 100’s also and and Bard has 360) on the backtest screen then the occasions when weird stuff happened  reduced to almost none / zero.

    It is well worth trying anyway … better than losing a days work again!?   That used to make me insane … just like Bard has been this week!

     

    #129639

    Hey thanks Grahal – I’ll do a clear out and see if it helps. A lot are redundant, for sure.

    #129640

    Hey @nonetheless, joining the advice that gave you GraHal, i don’t reccomend you to store all your algos just in the platform.
    1: it is very confusing to search and find what you need
    2: there is a strong risk of losing data, quite a few times I have came across the platform freezes

    Having a folder in your storage is surely more confortable and secure, maybe splitting systems and joining them with robustness tests could help to have everything more accurate

    I also tested hundreds of algos, and 3/4 of them were just trash: deleted or declassed in lower generations, everything more clear for me now 🙂

    1 user thanked author for this post.
    #129675

    A lot are redundant, for sure.

    I don’t delete anything … export bad ones / test beds / redundant to an Archives file … you never know when a spark of an idea may have you thinking … that’s why that didn’t work etc.

    Something else I do is if I have Demo Forward Tested, rather than waste the performance stats altogether, I add to the .itf file name as for example … 25Trd-1569 (25 trades loss 1569). I can then scan down filenames on my PC and see which Systems may be worth reviving and which are probably no-hopers?

    Just a few thoughts.

    declassed in lower generations,

    Yeah I use something similar … Good, Mid, Bad, 4Test, WIP.

    I agree … I feel loads happier and more organised when the .itf’s are in folders.

    1 user thanked author for this post.
    #129680

    Ok, it’s official, I’m a numpty. For months I’ve been cursing the inability to sort systems into folders within PRT. Just export it, dimbo. Thanks for that, I’ll just go sit quietly in the corner.

    1 user thanked author for this post.
    #129687

    Maybe it’s not you being numpty, maybe it’s just us being too affected by obsessive compulsive disorder 🙂

    2 users thanked author for this post.
    #129688

    Maybe this is worth another forum topic: best work practices, tricks and tips? I’m very new to all this, but have also had problems with losing code in PRT so I keep an offline copy as soon as I launch the script in demo. I put everything in excel, including code and screenshots of backtest – including notes on why I think it may or may not work. It helps a lot when I review the strategies after they’ve been running live, also helps me to revisit the ones I thought were dead – i.e. testing on very short TF where there is limited data available, and then re-testing them again with same variables a few weeks after and comparing results. I know some of you hate Excel but… 😉 Then I move the folders back and forward in the fodlers so I can keep track of where each one is in terms of testing / live etc.

    #129695

    to avoid losses of code i work with notepad++ or IDE this save me from PRT bugs…

    my 2 cents

    #129752

    Great idea Francesco!!

    Mods @Vonasi

    Please can you start a new Topic in the Platform Support Forum with posts …

    FROM

    https://www.prorealcode.com/topic/machine-learning-in-proorder/page/27/#post-129620

    TO

    https://www.prorealcode.com/topic/machine-learning-in-proorder/page/28/#post-129695

     

    Please title the new Topic …

    Good Work Practices, Tricks & Tips

    #129773

    Thanks @Moda, Notepad++ is v. useful. What language setting do you use?

    #129774

    Topic split from the ‘Machine Learning in ProOrder ProRealTime’ topic at GraHal’s request (it was a bit off topic!)

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

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