Add an IFitness Variant to Compute Fitness for a Collection of Chromosomes on a Vector Processor#136
Draft
timwood0 wants to merge 2 commits intogiacomelli:masterfrom
Draft
Add an IFitness Variant to Compute Fitness for a Collection of Chromosomes on a Vector Processor#136timwood0 wants to merge 2 commits intogiacomelli:masterfrom
timwood0 wants to merge 2 commits intogiacomelli:masterfrom
Conversation
Extend vector pattern to FuncFitness. TODO: Build out tests.
Author
|
Check failure from version incompatibility of Cake with .NET 6.0. GeneticSharp builds locally under .NET 8.0. |
Author
|
Hi Diego @giacomelli, draft PR here for vector fitness with questions when you can get to them.... thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
** THIS PR IS INCOMPLETE, SPECIFICALLY IN TEST COVERAGE. **
This PR is a draft implementation of the
IVectorFitnessconcept we discussed in email. It has come out much like what I suggested, except the vector extension uses an abstract implementation ofIFitnessand a runtime type check instead of alteringIFitness, for backward compatibility.It is agnostic wrt vector processing (GPU) libraries the user may use.
I'm looking for questions & Feedback on this approach before I extend the tests.
One question: Do I need to worry about consumers of
IFitnessother thanGeneticAlgorithmthat might expect aVectorFitnessto work polymorphically?This also includes the change for issue #135. Thanks!