Pathfinder Trading System

Forums ProRealTime English forum ProOrder support Pathfinder Trading System

Tagged: 

Viewing 15 posts - 376 through 390 (of 1,835 total)
  • #17979

    The only reason I ask is that backtesting v3 on DAX30 shows awsome results compared to v4…

    #17980

    Hi Mark,

    the DAX daily version trade only the strongest signal based on daily cross over/under (less signals but higher quality). The DAX 1D consider all 6 breakout signals and has higher profits but also a higher drawdown. I developed the versions based on daily data to have something for a quick check whether the instrument is suitable for the Pathfinder breakout algorithm or not. The test is done in minutes and if profitable I will look deeper and invest more time to create a H4 or H1 version.

    best, Reiner

    #17981

    Adam, as requested here is the code of the last H4 version V6 from today

     

    #17983

    Hello Reiner,

    First I will thank you for this great system. If I run a backtest with the latest version (v6) from 9 aug 2012 – 8 dec 2016 and looked at the losing trades, I came to the conclusion that if you separate the month in four, you probably get better results.

    Im not a programmer, so I don’t know to do that.

    The results of losing trades if you split the month in 4
    1 – 7        5 losing trades     5,95%
    8 – 15     8 losing trades     6,54%
    16 – 23   13 losing trades   11,32%
    24 – 31   5 losing trades     1,6%

    So, if I look back in 4,5 years history, it’s probably better to adapt the seasonal booster for those weeks, or do not trade in week  3.

    Alco

    #18047

    Hi Simon,

    the current Pathfinder DAX version is V6. http://www.prorealcode.com/topic/pathfinder-trading-system/page/25/#post-17954

    Please find attached a comparision of the results from V3 to V6. Pathfinder was created for the DAX and I have no clue if it works with DFB.

    @UK guys: please advise to answer Simons question if Pathfinder works with a DAX DFB – Thanks

    best, Reiner

    #18056

    Yes, works all good. Just adjust start and finish times back 1 hour.

    #18084

    Hello everyone!
    Thank you Reiner for this great system. It works very well for me so far.
    I have been programing my own trading systems for about 7 months so i´m still learning a lot.

    But there is one thing i don´t understand with your system.

    It says in the code that it is active between 09:00 – 21:00 but when i have done the same thing in my own trading systems that i have programmed it has ended open positions after the time has ended.
    But your system can keep positions open for days, even after 21:00
    So my question is what does the timeframe do more exactly in your code?

    Viktor

    #18087

    Hi Reiner,

    Do we set the timezone in platform options to CET (UTC +01:00)?

    Thank You.

    #18088

    Hi Viktor. It sounds like you have incorporated a timecondition correct. However it does not close position. A simple example I often use my self is this. Trades will only be open between 09:00 and 17:00, and all trades will be closed after 22:00

     

    #18089

    Could someone make the v6 version with months seperate in 4 instead of 2? i would really appreciate it.

    Kind regards,

    Alco

    #18095

    @viktor

    If you have general questions about coding, please open a specific topic for each of them, in order to keep this topic clear and dedicated to Reiner’s strategy.

    @Choo Jen-Sin

    Please update your country into your profile. Thank you.

    #18099

    Hi Alco,

    Thanks for your contribution and welcome. I checked  your idea and will deliver an adapted Pathfinder version tomorrow. Is some work to optimize 48 variables :-).

    best, Reiner

    #18100

    Hi Reiner. I a couple of question for you brilliant work. In advance my apologies if the subject already has been mentioned but 385 reply in this thread I might have overlooked a few things 🙂

    First  DAX V6 is the one I looked deeper into, but you published V6b2 before the V6? With all the versions it could be hard to track changes, so why a ver 6b2 before a clean V6? It just the order in me that what this to be at least a V6.5 or am I missing something? Anyway a suggestion would be to make a matrix with the changes up through the version on various instrument as well and post it as perhaps a sticky non reply-able post(Nicolas is this possible for the only mortals?), and yes I know it would probably be very time consuming, but very informative. It sure would be nice to have

    About the order cumulation- it only for Long position and not for Short. But looking at the DAX Seasonality chart it could be profitable in to implement cumulation of short in the saisonal position multiplier.

    • January2
    • February2
    • March1
    • August1
    • August2
    • September2
    • September1
    • October1

    It just a quick look at the DAX Seasonality chart and I know it will overlap of some of the high multiplier for Long, for eksample in September1

    Could this be an idea, or is it already tried?

    Cheers Kasper

    #18101

    Hi Choo Jen-Sin,

    Welcome – could you please set your location code in your profile to check where do come from. Usually it’s sufficient when you adjust the two variables:

    best, Reiner

    #18103

    Just a thought but splitting the months in to 4 will surely become over curve fitted..?

Viewing 15 posts - 376 through 390 (of 1,835 total)

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