When you program and develop a new feature in your engine, how do you know it is a possitive one?
I mean, lets suppose you have a little possitional improvement of knowing when your king it is better placed in other square. How do you know is good enaught, and it is better than don't calculate it and improve in calculaton time???
I think in lot of examples. What I am asking for is a good way to measure my effors.
thx
Test you engine
Moderators: hgm, Rebel, chrisw
-
- Posts: 27808
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Test you engine
I always play a standard gauntlet of 480 games (Nunn matches against 24 opponents) to get a rough impression if a change works or not. Even then the improvement should be substantial, as the statistical error over 480 games is still 2%.
-
- Posts: 792
- Joined: Wed Jul 19, 2006 9:58 am
Re: Test you engine
Hi,hgm wrote:I always play a standard gauntlet of 480 games (Nunn matches against 24 opponents) to get a rough impression if a change works or not. Even then the improvement should be substantial, as the statistical error over 480 games is still 2%.
At what time control do you run the gauntlet?
Thanks
Richard
-
- Posts: 27808
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Test you engine
That depends. I usually start with 40/1', to check if I have not broken anything, without wasting too much CPU time if I have. Eventually I do 40/10'.