It seems to me that I should be able to test evaluation weight (changed values of PSQT, changed values of outposts... ect) with incredibly low time controls. Something like 1+.01s.
This will be my first time playing around with just evaluation weights, so I've never done this testing before. Is there any reason that 1+.01s won't cut it?
Time controls for testing when changing evaluation weights
Moderators: hgm, Rebel, chrisw
-
- Posts: 1756
- Joined: Tue Apr 19, 2016 6:08 am
- Location: U.S.A
- Full name: Andrew Grant
Time controls for testing when changing evaluation weights
#WeAreAllDraude #JusticeForDraude #RememberDraude #LeptirBigUltra
"Those who can't do, clone instead" - Eduard ( A real life friend, not this forum's Eduard )
"Those who can't do, clone instead" - Eduard ( A real life friend, not this forum's Eduard )
-
- Posts: 20943
- Joined: Mon Feb 27, 2006 7:30 pm
- Location: Birmingham, AL
Re: Time controls for testing when changing evaluation weigh
AndrewGrant wrote:It seems to me that I should be able to test evaluation weight (changed values of PSQT, changed values of outposts... ect) with incredibly low time controls. Something like 1+.01s.
This will be my first time playing around with just evaluation weights, so I've never done this testing before. Is there any reason that 1+.01s won't cut it?
All you really want is a time control where you don't see many losses on time...
-
- Posts: 4833
- Joined: Sun Aug 10, 2008 3:15 pm
- Location: Philippines
Re: Time controls for testing when changing evaluation weigh
What do you mean by the following?AndrewGrant wrote:It seems to me that I should be able to test evaluation weight (changed values of PSQT, changed values of outposts... ect) with incredibly low time controls. Something like 1+.01s.
This will be my first time playing around with just evaluation weights, so I've never done this testing before. Is there any reason that 1+.01s won't cut it?
Is there any reason that 1+.01s won't cut it?
-
- Posts: 1756
- Joined: Tue Apr 19, 2016 6:08 am
- Location: U.S.A
- Full name: Andrew Grant
Re: Time controls for testing when changing evaluation weigh
What i mean is this:
Using 1+.01s time control will not be useful when you make a change regarding null pruning above depth 12. Or any other search features that are not triggered due to low time = low depth. That is a case I would say does NOT cut it
Using 1+.01s time control will not be useful when you make a change regarding null pruning above depth 12. Or any other search features that are not triggered due to low time = low depth. That is a case I would say does NOT cut it
#WeAreAllDraude #JusticeForDraude #RememberDraude #LeptirBigUltra
"Those who can't do, clone instead" - Eduard ( A real life friend, not this forum's Eduard )
"Those who can't do, clone instead" - Eduard ( A real life friend, not this forum's Eduard )
-
- Posts: 4833
- Joined: Sun Aug 10, 2008 3:15 pm
- Location: Philippines
Re: Time controls for testing when changing evaluation weigh
Most programs use their eval at depth 0 or below, sometimes at higher depths. Even if tc is low, what matters are the eval values that are produced as a result of tuning. The tuned values should be tested at longer TC, can be TC 40/4 or TC 40/40 and others. There are eval parameters that would scale well with time and there are others that would not (king safety for example) probably depends on the program.AndrewGrant wrote:What i mean is this:
Using 1+.01s time control will not be useful when you make a change regarding null pruning above depth 12. Or any other search features that are not triggered due to low time = low depth. That is a case I would say does NOT cut it