Yes, but also to KnockOut.Graham Banks wrote:A successor to Surprise.
Surprise was released in 2004, KnockOut in 2010, Jumbo in 2016.
Moderators: hgm, Rebel, chrisw
Yes, but also to KnockOut.Graham Banks wrote:A successor to Surprise.
I sense a patternSven Schüle wrote: Yes, but also to KnockOut.
Surprise was released in 2004, KnockOut in 2010, Jumbo in 2016.
mar wrote:I sense a patternSven Schüle wrote: Yes, but also to KnockOut.
Surprise was released in 2004, KnockOut in 2010, Jumbo in 2016.
Congratulations
Code: Select all
By year:
2016 xx
2014 ..
2012 ..
2010 xx
2008 ..
2006 ..
2004 xx
Surprise KnockOut Jumbo
By target elo:
3000 xx
2700 ..
2400 ..
2100 xx
1800 xx
Surprise KnockOut Jumbo
Hi Gabor,SzG wrote:Thanks Sven.
I have a problem, though. Maybe I'm doing something wrong but I have had 75 time forfeits by Jumbo out of 139 games. WinBoard 4.0.8b used under 64-bit Win10.
It may very well be the well-known problem of the engine not counting the moves fed by an external book.
Is that mixed time control really supported by xboard programs?SzG wrote:Hi Sven,Sven Schüle wrote:Hi Gabor,SzG wrote:Thanks Sven.
I have a problem, though. Maybe I'm doing something wrong but I have had 75 time forfeits by Jumbo out of 139 games. WinBoard 4.0.8b used under 64-bit Win10.
It may very well be the well-known problem of the engine not counting the moves fed by an external book.
I guess you did not use WinBoard 4.0.8b but a more recent version ...
Moves fed by an external book should usually not cause a problem, Jumbo should handle that correctly. It may be a problem of the time management code, though. Which TC did you use, and do you have a debug log?
It was a typo, I use 4.8.0b.
I use 40 moves in 1 minutes and 50 seconds. No debug yet but I'll switch it on for a couple of games.
The XBoard protocol allows a level command to be in minutes:seconds form, so a 40/1m50s would be a "level 40 1:50 0" string. UCI handles this by using milliseconds as its native time management granularity.SzG wrote:Although I have seen exceptions, in general: yes.Guenther wrote:
Is that mixed time control really supported by xboard programs?
I guess we have a missunderstanding. I thought Gabor means 40/1m +50s inc.ZirconiumX wrote:The XBoard protocol allows a level command to be in minutes:seconds form, so a 40/1m50s would be a "level 40 1:50 0" string. UCI handles this by using milliseconds as its native time management granularity.SzG wrote:Although I have seen exceptions, in general: yes.Guenther wrote:
Is that mixed time control really supported by xboard programs?
Actually, XBoard protocol *also* supports that. Increment is what the third field in "level" is for. So 40 moves in 1 minute plus 50 seconds increment per move would be "level 40 1 50". But I don't see why you'd ever want to do that.Guenther wrote:I guess we have a missunderstanding. I thought Gabor means 40/1m +50s inc.ZirconiumX wrote:The XBoard protocol allows a level command to be in minutes:seconds form, so a 40/1m50s would be a "level 40 1:50 0" string. UCI handles this by using milliseconds as its native time management granularity.SzG wrote:Although I have seen exceptions, in general: yes.Guenther wrote:
Is that mixed time control really supported by xboard programs?
AFAIK it is supported since not too long ago, but a lot of programs might choke on this.ZirconiumX wrote:Actually, XBoard protocol *also* supports that. Increment is what the third field in "level" is for. So 40 moves in 1 minute plus 50 seconds increment per move would be "level 40 1 50".Guenther wrote:I guess we have a missunderstanding. I thought Gabor means 40/1m +50s inc.ZirconiumX wrote:The XBoard protocol allows a level command to be in minutes:seconds form, so a 40/1m50s would be a "level 40 1:50 0" string. UCI handles this by using milliseconds as its native time management granularity.SzG wrote:Although I have seen exceptions, in general: yes.Guenther wrote:
Is that mixed time control really supported by xboard programs?
Well people do a lot of weird things ;-)ZirconiumX wrote:But I don't see why you'd ever want to do that.