fxDreema

    • Register
    • Login
    • Search
    • Back to the main page
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    1. Home
    2. tonyramirez
    3. Posts
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 25
    • Posts 66
    • Best 3
    • Controversial 1
    • Groups 0

    Posts made by tonyramirez

    • RE: Restricting optimization of parameters to matching values

      @roar said in Restricting optimization of parameters to matching values:

      @tonyramirez If you want matching values, use the same constant for both MAs đŸ˜„

      In case constants are new to you, you can declare them in Constants (Inputs) menu and then insert to any field by right-clicking
      0_1599298960949_17fc436e-9f27-4345-b6fe-c80ef949549a-image.png

      Thanks for that! Until now I hadn't got round to using variable and constants.

      posted in Questions & Answers
      T
      tonyramirez
    • Where to find description of various stop loss and take profit methods

      The 'buy now' node offers 7 different ways to implement a stop loss or take profit. Is there any documentation about these somewhere?

      Thanks

      posted in Questions & Answers
      T
      tonyramirez
    • RE: Restricting optimization of parameters to matching values

      @l-andorrĂ  I thought it might be done using variables somehow but haven't figured out if it's possible.

      posted in Questions & Answers
      T
      tonyramirez
    • Restricting optimization of parameters to matching values

      When you optimise a range of values for various parameters, you get to specify the start, step and end values but in some cases you end up testing a lot of combinations you are not interested in.

      For example if I have a block that checks to see if MA was greater than the same MA, x periods ago ( ie, checking to see if MA was rising), that's easy enough to do. The 'problem' arises if I then want to optimise for a range of MA values say 5 to 15, with step 5. Ideally, I would like to only compare MA 5 with MA 5, and MA 10 with MA 10 etc, but of course the optimiser will also compare MA 5 with MA 10 and MA 15. Obviously it gets worse the more steps you have.

      Is there any way to design the algorithm in fxdreema so that optimization can be restricted to matching values?

      posted in Questions & Answers
      T
      tonyramirez
    • RE: Help for newbie

      ...........

      posted in Questions & Answers
      T
      tonyramirez
    • Help for newbie

      UPDATE *****************
      After another couple of hours of fiddling, I got it right.

      Thanks to all those who took the time read and if you did try to build, I'd still like to see your take as it might be more elegant.

      I tried to construct a very simple EA but can't get it to work as expected after trying for hours 10 different ways. Something about the block flow which I don't understand.

      Rather than getting someone to debug my attempts. It might be quicker to explain what the this short EA does and someone could reproduce it? - that way I might understand how the wiring works. Should only take a couple of minutes...

      Basically the idea is to keep going long or short using PSAR AND MA as opening conditions but ONLY the PSAR as a closing condition:

      If no position

      1. Branch 1

      a. (Buy market if PSAR < ask ) AND if (MA 20 > MA 20, 2 periods ago)
      b. When PSAR > ask, close position

      otherwise

      1. Branch 2

      (Which is just the reverse of branch 1 so as to open and close short positions)

      1. If no positions are open, start all over again.

      Thanks

      posted in Questions & Answers
      T
      tonyramirez
    • 1
    • 2
    • 3
    • 4
    • 4 / 4