The talkchess.com community reported a problem with Prodeo and Scid.
I did some debugging and found out that there are 2 engine issues with Prodeo
and Scid
Problem #1: Prodeo does not seem to analyze according to the UCI
specifications.
On the command line I tried:
uci
isready
position fen rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1
go ponder infinite
and I get from Prodeo 1.2: info depth 1 score 1
Trying the above commands with a few other engines, I see actual
analysis being displayed. The problem is that Prodeo does NOT analyze
on "go ponder infinite" but instead does analysis only on "go
infinite".
Problem #2:
Even with "go infinite", prodeo sometimes reports "info depth 1 score 1" and
scid expects score cp ..
Prodeo returns the score cp line most of the time, but the score 1
confuses scid (which can be easily configured to be ignored by scid).
So, in order to patch scid, we could do one of the following:
1. Add special case for engine prodeo where scid issues "go infinite" instead
of "go ponder infinite"
2. Add a dialogue where the command "go ponder infinite" can be specially
configured by engine.
I think option 2 is better, though it involves a small UI change.
and we also need
1. Better handling of score from UCI engines, if cp is not provided in output,
we should simply ignore line.
Any thoughts from others?
Thanks, Shiv
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
