Skip to content
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

The algorithm gets lost in deep functions #7

Closed
Sakarah opened this issue Jun 8, 2016 · 3 comments
Closed

The algorithm gets lost in deep functions #7

Sakarah opened this issue Jun 8, 2016 · 3 comments
Labels

Comments

@Sakarah
Copy link
Owner

Sakarah commented Jun 8, 2016

Often when you test the program with the standard depth, it does not converge toward a solution because the population quickly get too much complex before having an approximate solution.
How could we solve that ?

@Gabzcr
Copy link
Collaborator

Gabzcr commented Oct 14, 2016

We could create another way of evaluating fitness which would slightly decrease the fitness of deep functions so that the algorithm would choose the simplest solution between two identical ones (considering fitness). Also depending on how we penalize deep functions, this could filter noise in experimental measures or even simplify a problem by making an approximation with a simpler function.

@Gabzcr Gabzcr changed the title The algorithm get lost in deep functions The algorithm gets lost in deep functions Oct 14, 2016
@Sakarah
Copy link
Owner Author

Sakarah commented Jan 15, 2017

We should look to "Dynamic limits for bloat control in genetic programming and a review of past and current bloat theories" in order to solve this problem.

@Sakarah
Copy link
Owner Author

Sakarah commented May 17, 2017

Taking size into account in fitness is enough to avoid this problem. This is what I do in regexp-search with the multi-objective fitness evaluator.

@Sakarah Sakarah closed this as completed May 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants