Machine Learning in ProOrder ProRealTime

Forums ProRealTime English forum ProOrder support Machine Learning in ProOrder ProRealTime

Viewing 15 posts - 406 through 420 (of 455 total)
  • #130532

    Bard – Just add GRAPH TRADEON to the bottom of your strategy that has the VRT added to it. Then when you click on each optimized result you will see the ‘randomised’ bars where trades are allowed to open (tradeon = 1) and the bars where they are not allowed to open (tradeon = 0).

    The VRT is simply a way of casino’ing our backtesting. It is like being at a roulette table and then regularly going to the bar and missing a few spins of the wheel and seeing how always betting on a certain number would work out if you did that – but tomorrow night your went to the bar at different times but the wheel still came up with the same numbers as the night before in exactly the same order.

    1 user thanked author for this post.
    #145817

    Hi everybody,

    I have a quick question about optimizations?

    When the strategy bot stops for x reason, are the updates kept in memory, or does it restart from 0 when the bot is restarted?

    Regards

    #145843

    Hi everybody,

    I have a quick question about optimizations?

    When the strategy bot stops for x reason, are the updates kept in memory, or does it restart from 0 when the bot is restarted?

    Regards

    They reset of course

    #145851

    I have a second strategy … suddenly, it is impossible to graph more than a week ….. Is there a way to save the optimization that the algorithm has performed for a longer period?

    #145949

    Is there a way to save the optimization that the algorithm has performed for a longer period?

    You okay now? What timeframe could you not see more than 1 week of?

     

     

    #145992

    playing again with this, 2 values x & y

    The code is looking back at the performance from the last xx trades. (reps)

    However, if valuex is for long & valuey is for short, looking back it mixes things up with reps for long & short together and can’t be used correctly in this way I think, but i’am not sure.

     

    #146013

    looking back it mixes things up with reps for long & short together

    You sure this isn’t due to use of the same variable name for longs and shorts?

    Above tripped me up way back, only found it by running ‘both sides / halves’ separately and then I got the message … ‘this variable is not defined’ and / or ‘this variable is not used’.

    #146074

    Is there a way to save the optimization that the algorithm has performed for a longer period?

    You okay now? What timeframe could you not see more than 1 week of?

    The problem come from the 10 seconds timeframe….no more than 4 days

    #146077

    no more than 4 days

    Yeah same for all of us  … 4 days max on 10 sec TF using v10.3! 🙁

     

    #146112

    You sure this isn’t due to use of the same variable name for longs and shorts?

    no, I don’t think so. An example would be using it for a stoploss, different for long & short.

    Valuex should evaluate only the long positions & set the stoploss, valuey for the shorts, both defined by xx reps.

    countofposition counts trades in similar direction.

    I need to do some test on his. But it will be hard to see how the code handles past trades.Perhaps it’s best use of juanj code is focus on only long or short if using valuex/y.

    1 user thanked author for this post.
    #146665

    again doing a bit of work on this code to fit my purpose.

    I worked on this in the beginning, I want to have a reset daily and tried another way.

    It appeared that min & max values where not respected in all times. Maybe on purpose I don’t know. I changed that I hope.

    The weighting score had to be changed because of that and it was also interesting to see the difference with weighting score on or off.

    Then I found, if I optimise values for 200k bars which are nice (2s timeframe), and load these values on a 100k bar, the last day results where not the same, even though they values were reset at the beginning of the day. So a few more variables had to be reset too. Now it’s close what I seek but still not perfect as there are slight differences in the last day.

    this how the code looks like for now with the changes.

     

     

    #146671

    ive expericed the same issue, when testing on one timeframe then switch to another and then back the results are not even close to the same as when the first test occured, and no values was changed in between.

    #146676

    How many variables can we consider working with …

    Personally, I work with a strategy on which I can adjust up to 7 variables …

    #146677

    yes indeed. A reset should fix that I hoped. The code above is still not good though, now I test a strategy with lots of trades.

    So a reset every day and the last full day(s) should be similar either with 50k or 200k.

    Maybe the problem is even at hour 0, it looks at the performance of the last trade(s) of previous day based on reps which influences every new trade?

    Here’s a pic to show the difference of the same code and the test code

     

     

    #146698

    the results are not even close to the same as when the first test occurred

    If we backtest on for example 100k bars of 10 min TF then test on 100k bars of 1 hour TF then switch back to 10 mins the start date will often not be the same as the 1st 100k bars of 10 min TF.

    In order to  achieve the same start date on subsequent 100k bars of 10 min TF we would have to close the strategy backtesting window and start again.

    Start date can be seen by hovering over the far left hand side of the  chart and reading off the date bar.

    It’s a while since I checked this out, so have a go and let us know please?

Viewing 15 posts - 406 through 420 (of 455 total)

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