Discussing the strategy VECTORIAL DAX (M5)

Forums ProRealTime English forum ProOrder support Discussing the strategy VECTORIAL DAX (M5)

Viewing 15 posts - 661 through 675 (of 1,261 total)
  • #120850

    Alright, got it – I was looking at the order list in the performance window. But the rejection notice just says ‘System error’ … which don’t tell me nuthin.

    #120859

    says ‘System error’ … which don’t tell me nuthin.

    Yeah I agree, I reckon it’s catch all / rubbish message which is used when there is no specific reason that applies??

    I had a System a few days ago getting stopped for ‘System Error’ and it turned out to be the use of While / Wend in the code … Paul helped me remove While / Wend and it has been working a treat ever since, no Rejections / Stoppings at all!

    #121467

    Hi All

    I test the v8, DAX 5M, but seems can’t run properly. Anyone can help? thanks!

    #121473

    change timeframe on your platform to 1 minute

    1 user thanked author for this post.
    #121483

    @fifi743 — could you please explain how this part of the code works?

    What I’m seeing in back test is 15 or 20 positions of 1 contract and then a sudden jump up to 3, or whatever the posmax value, then it goes back to 1 for a while before jumping up to 3 again. I’m sure there’s a method at work here, but whatever it is I don’t get it!?? 🤔🤔

    Is there any way to make this work with a more conventional money management?

    Many thanks!

    #121495

    Lines 895 AND 910 ARE posmax X 2 because for me there was a big potential of
    Success.
    For money management, it’s up to you …..

     

    #121499

    Thanks Fifi, I get it now — posmax is a multiplier, not a fixed amount, so MM applies only to the n value, no problem. 👍

    #121997

    @fifi743 — I’ve been so impressed with your v8_MTF that I adapted it for the Nasdaq. Fully optimized over 100k so curve-fit to the past 3 months but seems like it could have potential. There’s so much in the code that I don’t understand, perhaps there other details that should be changed from the DAX version?

    #122013

    hi,

    i don’t speak english but see backtest and demo?.why the difference for 11mars?

    #122022

    You have to redo all long stops and shorts.
    Yes, there is surely potential.

     

    #122036

    You have to redo all long stops and shorts.

    Do you mean the sections that are commented ‘Fin Long’ and ‘Fin Short’ (everything after the trailing stop)? I tried altering the value for stpposinver but it doesn’t seem to have any effect. What else should I be looking at? Coeff? Fin? VT?

    It’s such an excellent piece of work, really appreciate any suggestions of where to start!

    #122083

    From memory
    stpposinver is to stop the trailling stop.
    stpposinver is activate if it is a hedge position

     

    #122085

    Ac, vt or fin me for the graph

    #122086

    I come to help you no worries

    1 user thanked author for this post.
    #122092

    That would be wonderful! I know these things are time consuming but I’m happy to put in the work if you point me in the right direction. I understand the code up to the trailing stop, after that it’s a mystery…

    So far the NAS version is doing well in forward testing, 3 wins today, but with some fine tuning could be better. Thanks again for a very intelligent algo!

Viewing 15 posts - 661 through 675 (of 1,261 total)

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