New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions on specific details of the GP algorithm #674
Comments
Yes, the selection way in the paper is included in TPOT version 0.3-0.6 but we changed it to the mu + lambda evolutionary algorithm in TPOT 0.7 which was documented in the release log |
Thanks! Will close this now. Might reopen if i have further questions |
Sorry for reopening, but is there any literature on the effects of this change on the performance of TPOT yet available? |
Sorry, we don't any literature so far about the effects of this change in TPOT. But definitely, the mu + lambda algorithm is more advanced algorithm. @rhiever |
Thank @weixuanfu! :) |
@weixuanfu going trough the crossover operator i see two things:
|
Yes, that is exactly how crossover operator in GP algorithm in TPOT. We tweaked codes based on varOr in deap. |
Thanks, that explains the second point. Why should they have a primitive in common in order to be eligible for crossover? |
Thanks again @weixuanfu! |
Currently i am going to the literature on TPOT, and there are some unclarities in what i read w.r.t. what i find in the code. The main question i have here is a about the selection of individuals that proceed to the next generation. In the code i see that new population is selected from both the old population and the offspring. In the paper i found, if i understand correctly it is said that the selection is of the new population is done only from the offspring.
It would be really helpful if you could shed some light on these choices. Are these developments in the recent versions? Are there more major changes in the inner workings of TPOT w.r.t. what is written in the latest papers on TPOT? Thanks a lot in advance :) .
The text was updated successfully, but these errors were encountered: