MSC: Update - July 16, 2011

Update 11/7/11
checked again. fitness score still differ.
- another observation is that - all the fitness scores are the same in generation 0,
- but after allowing it to evolve 1 or 2 times, and checked the fitness score of the eg. 2nd generation,
- the fitness score varied again.
started testing the inputs and then will test the number of spikes throughout the run. printing them into a file

Observations:
found out that the inputs of the 3rd/5th generation differ from the new run with the chromo from the run before. It was the same when the cars are still in "get-set" period, but differed after starting to move, which is most likely caused by differing outputs.
saved the source into pendrive to bring home to investigate, while setup the comps in lab to run experiments with v & u being reset every timestep.
no efforts in write up. cannot be like this! must write!!!

Update 14/7/11
tested more vigorously. this time tested for the outputs. found out that the outputs are not the same. causing the spikes to be different.
hence there are only 2 causes.. it's either the inputs or the weights being different.
but the inputs are the same... hence it should be the weight.. then realized that the weights may have longer trailing floating points.
unlike those that are printed into file which only has 6 trailing max. hence i concluded that the printed weights have less precision compared to the weights stored in the variables.
finally found out why the scores are different.
went home running the experiment with the values of v & u being reset at every timestep.

Update 16/7/11
still running experiments with v & u being reset at every timestep. Spent last night here in lab. it's 8pm now. going home to write!
Lord bless and inspire me. hehe. thanks!!!