[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] problem with evaluations
From: |
Joern Thyssen |
Subject: |
Re: [Bug-gnubg] problem with evaluations |
Date: |
Thu, 23 Jan 2003 17:33:02 +0000 |
User-agent: |
Mutt/1.4i |
On Wed, Jan 22, 2003 at 03:05:55PM -0500, Gary Wong wrote
> On Wed, Jan 22, 2003 at 06:48:34PM +0000, Joern Thyssen wrote:
>
> I am considering a fix by modifying EvalRace(), EvalContact() and
> EvalCrashed() to keep track of the incremental evaluations independently.
> There would be a single global variable indicating the context the
> evaluation is in (normally -1, indicating that incremental evaluations
> are not useful; during 0-ply evaluations, ScoreMoves() would push a
> unique identifier onto the stack to specify its context, and restore the
> old identifier afterwards). EvalRace(), EvalContact() and EvalCrashed()
> would decide what type of evaluation to use at each call: if the global
> indicator is -1, they would use NNEVAL_NONE; if the indicator is not -1
> but not the same as the last call to that identifer, they would use
> NNEVAL_SAVE; otherwise, NNEVAL_FROMBASE. I think this would solve the
> problem of using more than one neural net during ScoreMoves(), as well
> as coping with cache hits on some but not all evaluations. Is this
> approach reasonable, or are there something I'm missing?
Sounds fine, as long as we handle recursiveness, i.e., ScoreMoves
calling itself.
Jørn