Discussion of article "Automatic Selection of Promising Signals" - page 2

[Sergey Vradiy]

Let's define risk management right away. There was a suggestion to consider a maximum drawdown of 20% worthy of the highest score. I disagree, and here's why. We should take into account the circumstances under which such a drawdown occurred. It can occur on consolidation with an extreme leverage, but it can also occur on a force majeure like Brexit. These are, as they say, 2 big differences. In the first case we have obvious adventurism, in the second case - competent work with capital. My idea is different. The maximum lot should never go beyond the margin of safety in case of maximum annual volatility. This means that if a pair can move by 3000 pips per year, this movement should be taken into account in the maximum lot. It's even simpler for armoured forces. If in case of force majeure the pair can pass 30 figures, we immediately put this into the risk. We open on this pair so that we can withstand a drawdown of 3000 pips. We do not know when and how the reversal will happen. Therefore, we will not break our heads and immediately put the probability of ANY drawdown into the risk.

[Charles Stangor]

Hello, I'm having problems implementing this program:

In MenuItem.mqh the line before the return seems incorrect.

//--- Leave, if the set type does not match
      if(m_type_menu_item!=MI_SIMPLE && m_type_menu_item!=MI_HAS_CONTEXT_MENU)
        {
         ::Print(__FUNCTION__," > The type of the independent menu item can be only MI_SIMPLE or MI_HAS_CONTEXT_MENU, ",
                 "that is only with a context menu.\n",
                 __FUNCTION__," > The menu item type can be set using the CMenuItem::TypeMenuItem()") method;
         return(false);
        }
     }

Also in Element.mqh I get "Class CWindow is undefined."  Sorry, not sure I can fix this on my own.

[Stan Baftalovskiy]

fxsaber:

It turns out that a custom GUI is offered, but not the selection criteria.

The developers have long been asked to give access to the Signal trading history through Signal-functions. The terminal itself has such access when it displays the history in the form of objects on charts. But MQL does not have it.

It is almost impossible to write something sensible without it. Only GUI, which is what the article shows.

I completely agree - the article just demonstrates that it is impossible to get anything worthwhile from SignalBaseGetxxxxx.

But it's good that it appeared at all - there is an opportunity to draw the developers' team's attention to the real needs of users in terms of SignalBaseGetxxxxx feature set, which apparently hasn't been updated for quite a long time.

For my part, I will try to be brief and objective about what functionality should be added to the SignalBaseGetxxxxx set:

1) we need the SignalBaseGetHistory function, which will allow us to automatically download from the server that file with history in csv format, which is available for downloading through the web-interface,

2) the SignalBaseGetDouble function needs a parameter to get the current drawdown;

3) the SignalBaseGetDouble function needs a parameter to get the % of algo trading;

4) the SignalBaseGetDouble function needs a parameter to get the Total Profit in the account currency;

5) the SignalBaseGetDouble function needs a parameter to get the Total Profit in pips;

6) the SignalBaseGetDouble function needs a parameter to get the Average Position Hold Time;

7) the SignalBaseGetDouble function needs a parameter to get the % of profitable trades.

[Emir Andi]

Hello, I get error when try this EA. Is there any newest version?

https://www.mql5.com/en/articles/3398

[Mike Mohebbi]

Does this expert only evaluate the MT5 signals?

How about MT4? Can we have the MT4 version?

[Pal Toth]

Perhaps not the best place for this question:

I have 3 decimal units trades, but a friend who want to copy it is on 2 decimal. It will works or better I search for a 2 decimal platform?