I’m experiencing trouble with the run time limit of Galapagos. It doesn’t seem to matter whether I set it or not – in both cases, Galapagos will go on making new generations until I manually stop it.
This issue is especially bothersome because I’m benchmarking Galapagos, Goat, and an optimization plug-in I have been building, so I need to make sure to compare the same run times.
Is there anything I could be doing wrong? Or is this a bug?
PS: I’ve also noted that Galapagos always takes the existing solution as a gene, which means that I have to randomize it, or set it back to a fixed starting position. One can see this use of the existing solution as a bug or feature, but it took me awhile to realize what was happening.
PPS: I also have a feature request: It’d be great if one could automatically run Galapagos multiple times (assuming the run time limit works), with Galapagos logging the several runs. (For that to work, one would have to randomize ALL the genes, or at least have the option.) Actually, allowing multiple runs is not only useful for benchmarking, but also not unheard of from a global optimization point of view – it would allow a multi-start approach (e.g. http://link.springer.com/chapter/10.1007%2F978-3-319-20469-7_6).