Re: [Sharpneat-developers] Hi

[<men...@gm...>]

On 11/22/05, Colin Green <cg...@ds...> wrote:
> Yeh this is just wrong. Have made the change here. You probably also
> noticed I often don't call clear right at the start, which is normally
> Ok because the network was normally just built, but in the general case
> it's an assumption and that's bad.

I've noticed that in running an experiment, saving a population and
then re-loading it to continue the experiment, networks that were
previously optimal and had remained stable for a while tend to go out
of whack, but I've never really chased the issue.  I wonder if this
lacking of an beginning initialization is what's throwing it off.

Hmmm.... However, I'm always clearing the signals before even setting
the first input signal, so that's probably not it.

> Maybe if networks set a flag when
> they are created (which resets on the first activation) we can check
> this to determine if a full clear is really required, then we can call
> clear at the top of all experiments, safe in the knowledge we won't be
> doing an unnecessary clear.

Certainly.  Another option is having a network preference
"InitialAutoClear" , which defauls to True, which checks said flag on
call to "SetInputSignals" to see if an initial clearing is necessary.


Ricardo J. M=E9ndez
http://ricardo.strangevistas.net/