Solution Cloning happening at steps that produce a “new best score” in a row
Something that recently caught my attention was a step being slower than others when a "new best score" is produced. This is definitely the solution cloning that is happening at every step that produces a "new best score". So this is okay if the "new best score" steps are not in a row. If for example we have 50 steps in a row the solution cloning process will be executed 50 times. A smarter way would be to do the cloning process at the end of the sequence(only once). Is this something that can be implemented easily or there is some other thing that would prevent it? Another idea would be to do