Comment on revision r61c548c9fa330594ae4d10f55267c80e102cdeb1 in pychess

2 views
Skip to first unread message

pyc...@googlecode.com

unread,
Jan 11, 2014, 4:01:05 AM1/11/14
to pychess-c...@googlegroups.com
Comment by matt...@gmail.com:

Score: Positive

General Comment:
You don't think 3 seconds as the default for analysis time is a little low?
I think between 100 and 300 seconds or so might be more appropriate. I
changed mine to 1000.

For more information:
http://code.google.com/p/pychess/source/detail?r=61c548c9fa330594ae4d10f55267c80e102cdeb1

pyc...@googlecode.com

unread,
Jan 11, 2014, 5:04:00 AM1/11/14
to pychess-c...@googlegroups.com
Comment by gbtami:

General Comment:
The issue was opened as a complaint about 100% cpu usage by hint/spy
engines, so I set it to 3 to easy testing and see how/when engines stop
analyzing. On the other side 3 sec is enough for crafty, sjeng, gnuchess
etc. to reach 10 ply search, and stockfish to reach 15-16 ply (at least on
my PC). This is more than enough to get a basic hint/spy suggestion when
kibitzing on FICS or something.
Are you getting unusable hints with 3 sec ?

pyc...@googlecode.com

unread,
Jan 11, 2014, 5:16:23 AM1/11/14
to pychess-c...@googlegroups.com
Comment by matt...@gmail.com:

Score: Positive

General Comment:
I didn't try it with the default 3 sec, and immediately set it to 1000 sec.
Reply all
Reply to author
Forward
0 new messages