Taken into account the random nature of the generation of thousands of children, 3 consecutive runs for each pair were chosen. Since each consecutive run initiated a fresh new parent co-evolution, to avoid duplicates previous children were kept in RAM memory by the algorithms. Most of the runs required 10-50 Gb RAM memory, variations depending on each pair. Monitoring heap memory by Java Jconsole garbage collector (-19_windows-x64_bin.msi), were used to control for possible memory excess causing program crashes The number of raw children increased proportionally from 1 to 3 runs. The number of automatically stopped runs was limited to reduce demands for excessive memory resources.