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

Fitness function modularity changes. #4

Merged
merged 2 commits into from
Apr 20, 2017
Merged

Fitness function modularity changes. #4

merged 2 commits into from
Apr 20, 2017

Conversation

JedS6391
Copy link
Owner

This PR builds upon the existing fitness function implementation, to provide a more modular API.

The main changes are:

  • The fitness function type no longer operates on a program and a set of fitness cases. Instead, it takes a set of program outputs and a set of fitness cases.
  • A fitness context builds a set of program outputs for the fitness cases and applies the fitness function appropriately.

In further work, it may be worthwhile to consider modularising this to allow for custom fitness contexts, for cases where multiple program outputs are used as there is no way to currently handle this.

Also, a way should be given to determine which register is used as the output register (probably best done through a field in the config).

@JedS6391 JedS6391 merged commit 8693544 into master Apr 20, 2017
@JedS6391 JedS6391 deleted the feature-fitness branch May 20, 2017 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant