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

Islands Optimizer requires Lexicase #323

Open
JorySchossau opened this issue Jan 8, 2020 · 3 comments
Open

Islands Optimizer requires Lexicase #323

JorySchossau opened this issue Jan 8, 2020 · 3 comments
Assignees

Comments

@JorySchossau
Copy link
Member

The Optimizers must all be present in buildOptions for a successful build.
Should be documented (and more clearly named) if this is the correct behavior.

@cliff-bohm
Copy link
Collaborator

I'm not sure how best to address this.
Because of MABEs absolutely crap include process (modules.h, etc.) we must include any optimizer that needs to be used in an island directly. So, currently, yes, you need lexicase and simple optimizer to be in the build if you want to use island optimizer. I'm not sure where to document it. If we add it to the code, it does not help anyone who does not know how to read the code (and if you can read the code it's very clear from the constructor what is happening). If you are not going to look at the code, where should this be documented?

@JorySchossau
Copy link
Member Author

I was thinking we could change the name from Islands to IslandsAddon_Simple_Lexicase or something like that. Yeah it's ugly, but we don't exactly go about typing the name of the optimizer hardly ever.

@cliff-bohm
Copy link
Collaborator

I'm not sure what to do here.
On the one hand, we could move this to extras. But it's the only instance that uses namespaced parameters anywhere in the stuff that ships with core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants