b130 fitness is not calculated correctly in custom projects builder

Voted for this task.

Voted for this task.

I can confirm i noticed that too,

When i set only Maximize # of Trades, The fitness Column wont sort the # of Trades Column correctly, they wont got from the highest to lowest, as if they was not following the fitness function..

Please fix this..

Voted for this task.

Voted for this task.

Voted for this task.

A restart of SQX was able to get this working.

Voted for this task.

hmm now it's not working again even after a restart.

Maybe a hint:
When I copied config from a task it copied the config correctly except for the "strategy Quality Ranking Fitness" settings were from a different task.

Also not working in custom project optimizer task.

Voted for this task.

Voted for this task.

can you attach your roject? 

there could be reason for this discrepancy, ut it works the same in Builder and Custom project Builder.

Fitness is always computed from the configured metrics - be it number of trades, Profit factor, or whatever else.

But there is a special handling that applies a coefficient to the fitness if number of trades is too small, see below.

The reason is to penalize strategies that have very good result (for exmaple Net profit) but on low number of trades, which makes the results strategically insignificant.

The coefficient applied to the computed fitness is:

if(trades < 20) {

fitness *= 0.3;

} else if(trades < 30) {

fitness *= 0.4;

} else if(trades < 50) {

fitness *= 0.6;

} else if(trades < 70) {

fitness *= 0.8;

} else if(trades < 100) {

fitness *= 0.85;

} else if(trades < 150) {

fitness *= 0.9;

}

Any single weight fitness seems to be giving incorrect calculations in custom project tasks. In this sample builder config I have attached, the fitness is sharpe ratio only. If I sort by fitness it's totally not the same as sort by sharpe ratio. It should be the same except for maybe a few rounding issues. But you can see for yourself it's not even close. 

But if I use this same config in main builder then the fitness sort matches the sharpe ratio sort as expected. Fitness in custom project is clearly not calculated the same way as main builder.

as I said in previous comment - THERE IS a coefficient applied to the computed fitness value if number of trades is too small.

It is applied the same for both simple and weighted fitness, and as same in custom project and main builder.

If you think it is not please attach a screenshot of databanks from main builder and custom project builder where I can see this..

There is a filter on number of trades no strategies have such few trades. Many with lower number of trades AND smaller Sharpe ratio are rated higher fitness so nope it's definitely not caused by such a coefficient applied to  number of trades. 

Screenshot 176.png = project build task
177 = regular builder.

Both the same config which I posted above.

Custom project fitness is bugged.

BTW the number of trades coefficient is good idea but can I change the number of trades coefficient formula in a snippet somewhere? 150 trades is way to low for me usually.

I can no longer reproduce it, it is most possible that it was already fixed. I'm not sure if it works in 131 Dev 1 build already, but it will work in Dev 2