Fixed FunctionSet issue, planned testbench evaluator interface, will implement tomorrow.

1 files changed, 19 insertions, 1 deletions

diff --git a/README b/README
index 52c2ef9..0b886c9 100644
--- a/README
+++ b/README
@@ -45,6 +45,24 @@ so long as it extends Chromosome. In conjunction with modularized FF, EA and mut
 flexible and versatile system. The Population class itself is immutable, since the system relies heavily on it.
 Finally, it is Iterable to for access to the chromosomes within.
 
+
 Arity may vary across functions, but all nodes contain enough connections to cope with the largest arity.
     
-   
\ No newline at end of file
+FunctionSet presents a bit of a problem in case the user retains references to the Functions passed into it.
+
+
+3/2
+
+Solved the FunctionSet problem; since Function does not specify a way to modify the function once it is instantiated,
+concurrent accesses should not be a problem. Should the user extend Function and implement a way to modify it at 
+runtime, the CGP program won't really use it; if the user modifies the CGP program to use it, then the user must
+be ready to deal with the consequences.
+
+A fitness evaluation testbench of sorts will be implemented next. This testbench will take a set of "stimuli" (inputs),
+use them to compute outputs with each chromosome, and compare those with the expected outputs, thus assigning fitness.
+
+This will be achieved for now using a TestCase object which contains a set of inputs and outputs. The evaluator simply
+sets the chromosome inputs and compares outputs for all TestCase objects given, and computes a fitness function
+accordingly.
+
+