Conditional Parameter Optimization solution needed!

I see. There will be redundant passes. I think this is something which can be addressed to service support. 

This looks more like a feature request, rather than something which can be solved on the forum. 

Maybe a moderator can answer to this.

Hi

Thanks for your reply. I really didn't catch what you said.

a moderator?

how can i get in touch? 

I've already posted an order, on the freelance section but so far was not successful.   https://www.mql5.com/en/job/91806

Just wait for a moderator to reply to your thread or you can send the problem to service desk yourself.

I think this is a feature request to enhance the MT5 optimization tool to have "Conditional Parameter Optimization", rather than simply doing code changes.

I doubt code changes will produce the effect that you want, and I also doubt in the short to medium term, you will have the solution ready to your issue.

There will always be a forum moderator around. He is more experienced in issues than any of the forum members.

input bool Psar_Active=...

#define STEP_DEFAULT=0.02;
input double step=STEP_DEFAULT;

#define MAX_DEFAULT=0.20;
input double max=MAX_DEFAULT;

:
if(!Psar_Active && (
   step != STEP_DEFAULT ||
   max  !=  MAX_DEFAULT )) return INIT_PARAMETERS_INCORRECT;

I have a problem like this in MT4.
I have some boolen parameter in a expert. One of them If I do not set any option for optimization and the default value of this parameter is false, a result will be displayed, while if it is True, the result will not show any result and optimization work correctly.

when "Send Pending order?" parameter is false I have this result...

I have the exact same need as the OP:

If certain boolean input values are false, it negates the need for certain other inputs to be tested at all.

Currently wasting time, computing resources, and yes even cloud network budget ($) testing useless/irrelevant input parameters.

... Being that it has been some 3 years since this was posted, perhaps there have been some updates regarding this much needed feature (or a suitable workaround)?

Thanks much! =)

The workaround was given.

I used Williams code to "develop" below. I thought I could share with everyone who is visiting this topic to find solution.

Just modify as required obviously, it's just an example of how this could be implemented.

input group "Trailing Stop";
const input int    iprofitToTrigger = 30;
const input double iprofitIncreaseToTriggerAgain = 0.05;
const input double iprofitToTake = 0.2;
const input bool   iincreaseProfitToTake = true;
const input double iincreaseUntil = 0.7;
const input double iincreaseBy = 0.05;

// Check input parameters
bool CheckOptimisationParameters()
{
// in the OnInit check for true/false and return ( INIT_PARAMETERS_INCORRECT ); if false
// this ends EA early and stops optimiser from running this set of parameters. Copy below to OnInit():
// if( CheckOptimisationParameters() == false ) return ( INIT_PARAMETERS_INCORRECT );

// input group "Trailing Stop";
   if ( iprofitToTake + iincreaseBy >= 1 ) return (false);
   if ( iprofitToTake + iincreaseBy >= iincreaseUntil ) return (false);
   if ( iincreaseUntil >= 1 ) return (false);


   return ( true );
}

int OnInit()
{
   if( CheckOptimisationParameters() == false ) return ( INIT_PARAMETERS_INCORRECT );

   return(INIT_SUCCEEDED);
}