[BUG] Fitness BUG CONFIRMED! When using a Custom Project
When using a Custom Project, When pressing the Green "START" button OR "Run project from here" to start building/the project, The Fitness will not calculate properly and give very random results!,
However,
When using a Custom Project, When pressing the "Run this task Only" ,Then suddenly The Fitness is calculated right again..!
THIS IS A MAJOR CRITICAL BUG!,
The Dev team should focus again on the fitness calculation because sometimes even with running a project with "Run this task Only" the fitness shows odd results sometimes, check the screenshot right side where i compare between the fitness in NetProfit, maybe the fitness should be shown with another decimal number? like from 0.00~1.00 rather than 0.0~1.0 this might help too.
Screenshot attached.
==
*IMPORTANT EDIT!
I even downloaded build 135 again installed it in a different folder as a fresh start,
created a new Custom Project and even noticed another way to re-create this fitness bug!,
When you got a project with only 1 Task (1. Builder), the fitness is working great,
however when you got more than 1 Tasks in your Custom Project (1. Builder & 2. Tester), the fitness is messing up again..!,
I attached the 2 projects for you to see by yourself,
It comes with the Fitness Function set to "Complexity" just sort your database by the Fitness Column and check the Complexity Column between those 2 projects,
With "NEWPROJECT_FITNESS_TEST - (ONLY BUILDER)" project Fitness will work just fine no mater how your "Start" the strategies searching process,
if it is Starting with: Green "Start" button / "Run project from here" / "Run this task Only" it will all work perfectly normal.
With "NEWPROJECT_FITNESS_TEST - (WITH RETEST AFTER BUILDER)" project Fitness will work fine ONLY when selecting the Builder task's little icon and starting the project by "Run this task Only",
the other 2 starting methods like WILL MESS THE FITNESS!: Green "Start" button / "Run project from here"
EDIT! FOUND A FIX Thanks to @bentra!
when you place the Tester task before the Builder task like so:
1. Tester
2. Builder
rather than
1. Builder
2. Tester
it solves the bug!,
this is still needs to be resolved in the background though :/
LAST EDIT: I tried to re-create the same thing with build 136 Dev, the bug is still there,
that is: when using a multi tasks project, and Builder is 1. (1st task in that project) the fitness bug is there..,
however when you place the Retester as 1. (1st task in that project) and Builder 2. (2nd task in that project) the bug is solved and fitness works perfectly normal.
-
Votes +9
-
Project StrategyQuant X
-
Type Bug
-
Status Fixed
-
Priority Normal
History
Karish
20.06.2022 18:34Description changed:
When using a Custom Project, When pressing the Green "START" button OR "Run project from here" to start building/the project, The Fitness will not calculate properly and give very random results!,
However,
When using a Custom Project, When pressing the "Run this task Only" ,Then suddenly The Fitness is calculated right again..!
THIS IS A MAJOR CRITICAL BUG!,
The Dev team should focus again on the fitness calculation because sometimes even with running a project with "Run this task Only" the fitness shows odd results sometimes, check the screenshot right side where i compare between the fitness in NetProfit, maybe the fitness should be shown with another decimal number? like from 0.00~1.00 rather than 0.0~1.0 this might help too.
Screenshot attached.
==
*IMPORTANT EDIT!
I even downloaded build 135 again installed it in a different folder as a fresh start,
created a new Custom Project and even noticed another way to re-create this fitness bug!,
When you got a project with only 1 Task (1. Builder), the fitness is working great,
however when you got more than 1 Tasks in your Custom Project (1. Builder & 2. Tester), the fitness is messing up again..!,
I attached the 2 projects for you to see by yourself,
It comes with the Fitness Function set to "Complexity" just sort your database by the Fitness Column and check the Complexity Column between those 2 projects,
With "NEWPROJECT_FITNESS_TEST - (ONLY BUILDER)" project Fitness will work just fine no mater how your "Start" the strategies searching process,
if it is Starting with: Green "Start" button / "Run project from here" / "Run this task Only" it will all work perfectly normal.
With "NEWPROJECT_FITNESS_TEST - (WITH RETEST AFTER BUILDER)" project Fitness will work fine ONLY when selecting the Builder task's little icon and starting the project by "Run this task Only",
the other 2 starting methods like WILL MESS THE FITNESS!: Green "Start" button / "Run project from here"
Attachment NEWPROJECT_FITNESS_TEST - ONLY BUILDER.cfx added
Attachment NEWPROJECT_FITNESS_TEST - WITH RETEST AFTER BUILDER.cfx added
Attachment fitness bug.png added
Karish
20.06.2022 18:53Description changed:
When using a Custom Project, When pressing the Green "START" button OR "Run project from here" to start building/the project, The Fitness will not calculate properly and give very random results!,
However,
When using a Custom Project, When pressing the "Run this task Only" ,Then suddenly The Fitness is calculated right again..!
THIS IS A MAJOR CRITICAL BUG!,
The Dev team should focus again on the fitness calculation because sometimes even with running a project with "Run this task Only" the fitness shows odd results sometimes, check the screenshot right side where i compare between the fitness in NetProfit, maybe the fitness should be shown with another decimal number? like from 0.00~1.00 rather than 0.0~1.0 this might help too.
Screenshot attached.
==
*IMPORTANT EDIT!
I even downloaded build 135 again installed it in a different folder as a fresh start,
created a new Custom Project and even noticed another way to re-create this fitness bug!,
When you got a project with only 1 Task (1. Builder), the fitness is working great,
however when you got more than 1 Tasks in your Custom Project (1. Builder & 2. Tester), the fitness is messing up again..!,
I attached the 2 projects for you to see by yourself,
It comes with the Fitness Function set to "Complexity" just sort your database by the Fitness Column and check the Complexity Column between those 2 projects,
With "NEWPROJECT_FITNESS_TEST - (ONLY BUILDER)" project Fitness will work just fine no mater how your "Start" the strategies searching process,
if it is Starting with: Green "Start" button / "Run project from here" / "Run this task Only" it will all work perfectly normal.
With "NEWPROJECT_FITNESS_TEST - (WITH RETEST AFTER BUILDER)" project Fitness will work fine ONLY when selecting the Builder task's little icon and starting the project by "Run this task Only",
the other 2 starting methods like WILL MESS THE FITNESS!: Green "Start" button / "Run project from here"
EDIT! FOUND A FIX Thanks to @bentra!
when you place the Tester task before the Builder task like so:
1. Tester
2. Builder
rather than
1. Builder
2. Tester
it solves the bug!,
this is still needs to be resolved in the background though :/
LAST EDIT: I tried to re-create the same thing with build 136 Dev, the bug is still there,
that is: when using a multi tasks project, and Builder is 1. (1st task in that project) the fitness bug is there..,
however when you place the Retester as 1. (1st task in that project) and Builder 2. (2nd task in that project) the bug is solved and fitness works perfectly normal.
Karish
20.06.2022 22:42I call it the Fitness Sandwich bug fix :P
You take your project and you sort your project's task like so in this order:
[1. Builder]
[Any other tasks here]
[X. Builder - Clone]
This is a temporary fix until the dev team will fix this MAJOR issue, and from what i heard from @bentra this bug been around for many versions earlier than build 135,
he said that nobody from the Dev team could re-produce this so was left un-fixed.., lets hope it will change for the better soon,
until then Enjoy your Fitness Sandwich bug fix
Cyber
21.06.2022 00:39Karish
21.06.2022 10:02&
Yes you can leave the builder clone turned OFF.
Tamas
05.09.2022 18:56Status changed from New to Fixed
© Copyright. All rights reserved. ProjectPanel.com
