Discussing the strategy VECTORIAL DAX (M5)

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

Viewing 15 posts - 511 through 525 (of 1,261 total)
  • #113273

    You are not in the same time zone as Grahal…

    If you change your time zone or the code you will get the same result

    If you are on CET+1 you can change to:

     

    2 users thanked author for this post.
    #113341
    Probably a really obvious solution here – but any idea why my IG CFD Demo account is rejecting orders for ‘Wall Street Cash (£1)’ using the code below.
    I get the message: Rejected:Size below minimum requirement.
    Position size = 1

     

    #113366

    On CFD the min position size is 2 x Wall Street Cash (£1) or 1 x Wall Street Cash (£2)?

    1 user thanked author for this post.
    #113369

    On CFD the min position size is 2 x Wall Street Cash (£1) or 1 x Wall Street Cash (£2)?

    Thanks for this. I can see Wall Street Cash £1 – which I can set the position size to 2.

    I cant see the £2 option in the list – should I be using $2 option?

     

     

    #113370

    On CFD the min position size is 2 x Wall Street Cash (£1) or 1 x Wall Street Cash (£2)?

    That’s interesting as I’m sure when I last checked the minimum size on DJI for spread betting was 0.2

    It used to be a minimum size of 1 but soon after the ESMA changes that meant you needed 5 times as much margin IG divided the minimum size by 5. I haven’t checked it for a while so perhaps I should.

    #113374

    the minimum size on DJI for spread betting was 0.2

    It may well be (or 0.5?), but my comment was about CFD position size.

    #113375

    I cant see the £2 option in the list – should I be using $2 option?

    I meant $2 anyway 🙂 … which I can see you have got.

    I find it easier to use the $2 contract and then if I swap a System from SB to CFD then a position size = 1 (already coded in the strategy)  works fine  on a $2 contract (with no changes needed).

    1 user thanked author for this post.
    #113525

    Bjr Fifi, je n arrive pas a ajouté le code de clôture de position exemple, du vendredi pour ne pas être over-week. Merci

    #113532

    sublime06 – English only in the English speaking forums please.

    #113605

    I can not add the code to not be in position at the weekend. Thank you

    #113690

    thank you, I found without your help VONASI

    #113694

    Hello @sublime06. You can publish the itf file that you managed to do?

    1 user thanked author for this post.
    #113695

    thank you, I found without your help VONASI

    As a moderator I am tasked to keep the forums tidy and point out to forum members when they are breaking forum rules. If you’d posted in English in the English speaking forum rather than posting in French then your chances of me being able to assist with your question would be far higher. I’m pleased for you that you found your solution without me having to use a translation tool unnecessarily.

    #113871

    Good afternoon.
    It is the first time I write here and I wanted to talk about the possible over-optimization of the DAX 6.2 Vector proposed by Fifi.

    I wanted to know if it is possible to make another optimization different from the one proposed by Fifi.
    The first thing I did was to unify the “Filtre_Prise_Position” indicator with the Vectorial Dax system.
    Then I estimated that the main system variables are PeriodeA, PeriodeB, ChandelierA, ChandelierB, AngleA and AngleB.
    What I am doing is optimizing month by month and getting the best results for each month.
    With that data you can do several things:
    – An arithmetic average with 15 periods or more.
    – Its weighted calculation as if it were an Exponential Average to give more weight to the last months
    – A weighted calculation relative to the amount of money earned each month
    – Calculation of arithmetic averages between maximum benefit and maximum% success.
    – more ….
    The options to estimate the optimal values ​​without falling into over optimization are many and all of them are giving positive values.

    Regarding the bad results obtained this month by the system proposed by Fifi with its values, I think it is something transitory. All estimates with variables of all types give a drop in this last month.
    And in part it is logical because seeing the code we see the great importance of the “Weekpoints” as points of support and resistance that indicate the exits of the operations. Let’s note that this month the DAX was atypically very flat, which makes the system fail.

    I still think the system is good, very good.

    It takes me one day to get maximum optimization for each month and I am doing it a second time because I detected a failure in my procedure.
    When I have all the values ​​obtained again, I will share them here.

    Many thanks to those who collaborated in this system and in this forum, especially Balmora, Fifi, GraHal, Gubben …

    3 users thanked author for this post.
    #113874

    Edurecio – thank you for your contribution to this topic but please only post in one language (the language of the forum that you are posting in) otherwise threads become very large if every possible language is catered for.

    The platform has a built in translation tool that others can use if they feel the need.

     

Viewing 15 posts - 511 through 525 (of 1,261 total)

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