BitString crossover issue
eugene-kamenev opened this issue · comments
Describe the bug
I think there might be a bug in implemented BitString crossover/mutation. If crossover rate is low, and same Chromosome is returned as an offspring and then mutated, my assumption is that fitness score should be resetted as well. Right now it is not resetted and returns wrong score (from previous generation).
Expected behavior
If mutation happens and fitness score exists it should be resetted.
Actual behavior
Same fitness score persists even if Chromosome got a mutation.
Code snippet
Input data
The sample data
Additional context
- latest smile version
My apologize, have to investigate more. I will reopen with concrete example if find something.