tag:blogger.com,1999:blog-7144957120901661042.post40909856267732841..comments2023-07-20T17:00:19.615+02:00Comments on VICKI Chess Engine: First releaseJaco van Niekerkhttp://www.blogger.com/profile/05438999119366217740noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7144957120901661042.post-5087742688865759222007-04-24T11:02:00.000+02:002007-04-24T11:02:00.000+02:00Yes, it is too much :) Changed it to 10 which also...Yes, it is too much :) Changed it to 10 which also dropped the overall CPU usage to 1% (0% to Vicki when waiting). Thanks for the suggestion. Every milliseconds helps!Jaco van Niekerkhttps://www.blogger.com/profile/05438999119366217740noreply@blogger.comtag:blogger.com,1999:blog-7144957120901661042.post-68637376521015906172007-04-23T20:17:00.000+02:002007-04-23T20:17:00.000+02:00Isn't half a second too much? Just Sleep(1) should...Isn't half a second too much? Just Sleep(1) should be more than enough...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7144957120901661042.post-69729922628292466142007-04-22T23:32:00.000+02:002007-04-22T23:32:00.000+02:00Hi Jonatan. Thank you so much for your interest. ...Hi Jonatan. Thank you so much for your interest. <BR/><BR/>1) The reason for the system resource chow frenzy is that Vicki uses threaded I/O. For input the system went into an "active wait" loop, which caused the problem. I tried adding a sleep time of half a second and presto - problem solved.<BR/><BR/>2) Easy to solve. Thank you for pointing it out.Jaco van Niekerkhttps://www.blogger.com/profile/05438999119366217740noreply@blogger.comtag:blogger.com,1999:blog-7144957120901661042.post-5148695394724084502007-04-22T22:39:00.000+02:002007-04-22T22:39:00.000+02:00Nice!I played a few games and noticed two things.1...Nice!<BR/><BR/>I played a few games and noticed two things.<BR/><BR/>1. Just starting Vicki makes it eat up all the system resources, usually it's only supposed to do that while searching a position. :) Perhaps something with your input loop?<BR/><BR/>It's hard to try it against other engines since it steals the processor time.<BR/><BR/>2. A minor thing but the winboard protocol states you should give the evaluation number from the engine's point of view. So if it is ahead a rook while playing black the score should be +5.0 (and not -5.0).<BR/><BR/>I did this mistake in one of my versions of Mediocre and it messes up the automatic adjudication in interfaces like Arena since the adjudication is based on the engine's evaluation (if the engine gives -9.0 while ahead a queen as black the interface will assume it is actually behind and adjudicate the game in favor of white).Jonatan Petterssonhttps://www.blogger.com/profile/03152085169762414586noreply@blogger.com