Errors, bugs, questions - page 25

 
joo:

Where in the help it says: "The size of the balance in each optimisation run is 100 times larger than it actually is. But don't pay attention to it, it's just a harmless glitch"?

The help doesn't say anything about a "glitch", I agree, and it can't. It is stated in dry mathematical language in the help:

Balance + Min Drawdown

As you can see from your previous post, you are satisfied with the results of optimization with "Balance Max" parameter. Conclusions about the possible results of the work Balance to the minimum drawdown is up to everyone. Although... drawdown is 4-5%. Accordingly, the second multiplier in the product of the Balance on the minimum drawdown is just about 95%.

 

You should have written: "The "Result" column shows the total value ofthe "Optimisation criterion", which is calculated as....". - This is not the Balance.

This information is scattered in different places in the help and the relationship between them is not obvious.


 
joo:

You should have written: "The 'Result' column shows the total value of the 'Optimisation Criterion', which is calculated as....". - This is not the Balance.

This information is scattered in different places in the help and the relationship between them is not obvious.

Thus, the original question can be considered as settled.

Regarding the content of Help (User's Guide), it is my opinion (and apparently also the opinion of the authors of the Guide) that this part of the information (taking into account that links can be clicked) is clear and logical. You have highlighted this logic yourself.

Itake this opportunity to apologize for my inattentive reading of the clear link (about scanning) indicated byalexey_petrov(https://www.mql5.com/ru/forum/1111/page22/#comment_9188).

 
Yedelkin:

..............

Regarding the content of the Help (User's Manual), in my opinion (and apparently also in the opinion of the authors of the Manual), this part of the information (taking into account the ability to follow the links) is clear and logical. You have also highlighted this logic yourself.

.............

Click on the link (highlighted in blue), where do you go? Not at all to where it says what the"Optimization Criterion" is.

It would make more sense to name the column "Optimization criterion" instead of "Result" (whatever result a user expects to get), then it would be more understandable, and less jumps to links in the help would have to do.

 
joo:

Click on the link (highlighted in blue), where do you go? Not where it says what the 'Optimisation Criterion' is.

I agree on that point. The link address must be corrected. You may write to Service Desk. I myself read the entire "Tester" section at once, so I almost never used links.

joo:

It would be more logical to name the column "Optimization criterion" instead of "Result" (whatever result the user expects to get), then it would be more understandable, and there would be less need to click on references in the help.

The user always expects to get a result with the parameters he or she personally selected in the "Settings" tab. In particular, if the user has personally selected such an optimization criterion as "Balance + Min Drawdown", then you can hardly expect the tester to show results of processing another parameter (for example, "Balance Max"). If you select optimization criteria at random and expect the tester to show results of "Balance Max", then it is not a problem of the tester (or the User Manual).

The formal renaming of the column "Result" into "Optimization Criterion" is illogical as this column reflects not the names of optimization criteria butnumerical testresults by the parameters selected by the user. At that the name of a user-selected optimization criterion can always be viewed in the "Settings" tab.

The number of clicks on the links in the Help (User Guide) is irrelevant to this issue.

 
Yedelkin:

On this point I agree. The link address needs to be corrected. You can write to Service Desk. I myself read the "Tester" section in its entirety, so I hardly ever use the links.

The user always expects to get the result of working with the parameters he/she has personally selected in the "Settings" tab. In particular, if the user has personally selected such an optimization criterion as "Balance + Min Drawdown", then you can hardly expect the tester to show results of processing another parameter (for example, "Balance Max"). If you select optimization criteria at random and expect the tester to show results of "Balance Max" processing, then it is not a problem of the tester (or the User Manual).

The formal renaming of the column "Result" into "Optimization Criterion" is illogical as this column reflects not the names of optimization criteria butnumerical testresults by the parameters selected by the user. At that the name of a user-selected optimization criterion can always be viewed in the "Settings" tab.

The number of clicks on the links in the Help (User Guide) is irrelevant to this issue.

Are you an administrator or something? If not, why are you trying to decide what is logical and right and what is illogical and wrong? Once again, the bug report was addressed to the developers and administration, not you personally. If there is a possibility of misinterpretation of the names of these or those interface elements by the user (I am an example), the developers should think about how to make that understanding was unambiguous and such questions were less (this is not a reproach to the platform developers, but a good advice).
 
joo:
... why are you trying to decide what's logical and right and what's illogical and wrong?

I'm not 'trying to decide', I know :)

I am not an admin. Wait for an official response, if you are still convinced of your rightness and the presence of glitches-bugs, and if the quiet discussion on the forum irritates you.

In squabbles and "switch to personality" is not involved, so the absence of constructive question-replies on this topic means the end of the discussion. Good luck in resolving your questions!

 

Hello, I am looking into margin calculation methods and found a number of possible discrepancies in the help :

1.for Forex - there is no price;

2.for futures - there is noMarketPrice;

I have a question if I have correctly interpreted the following terms in the equation:

double MarketPrice=SymbolInfoDouble(symbol,SYMBOL_LAST);

double Percentage=AccountInfoDouble(ACCOUNT_MARGIN_LEVEL);

double InitialMargin=SymbolInfoDouble(symbol,SYMBOL_MARGIN_INITIAL);

 
These data can be obtained from the properties in the Instrument Information section:
1.for forex
double Ask=SymbolInfoDouble(symbol,SYMBOL_ASK);  
double Bid=SymbolInfoDouble(symbol,SYMBOL_BID);  
2. For Exchange instruments
double Price=SymbolInfoDouble(symbol,SYMBOL_LAST);        

3. Lever size (not the interest)

double leverage=AccountInfoDouble(ACCOUNT_MARGIN_LEVEL);     
4. Initial margin
double InitialMargin=SymbolInfoDouble(symbol,SYMBOL_MARGIN_INITIAL);
To insert the code, use the editor.
 
To the developers - I missed it, has my request #15802 been fulfilled or is it coming up?
Reason: