>> Exactly. While moving back, you have calculated and deepened >> lines which actually happened in the game. While moving forward, >> you have many lines which are no longer relevant. >> > You don't imagine the tricky stuff I had to do to make Scid analyse a > whole game, recursively taking into account all variants and > sub-variants ! I had to make some stacks to keep track of score changes, > etc. > So the idea is certainly good, but would mean big rewrite of code. > Not today ! ;-)
Who said, that it is to happen today ;-) But there is a reason why most (all?) chessbase programs analyse back. To give you even more things to consider, some tools (like CA) use multipass schemes. Details vary, but usually you first quickly scan through the game (using 1-5 sec/move), then analyse it normally, but give some more time in places where evaluation significantly raised/dropped, and sometimes makes even deeper analysis in crucial points of the game... ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
