Repository navigation
New Game Review and Move Comment in the Engine Window #442
Replies: 2 comments 6 replies
|
Ok, I finally found the game review button. Am trialing it now :) Meh... It's a little wordy for my liking. But it's a bit confusing having two ways/widgets for engines. It took me a while to find this Review feature because i was looking at the old engine widget. But biting the bullet and removing the old interface is easier said than done i guess :). |
|
Upgraded today from .51 to .67 and started testing the new features. Game Review text looks very informative and very interesting to play with. Problem is it introduced a problem in text colour management in the PGN window, at least for me (Windows 11). Game Review text goes directly into the PGN windows in "SCID green". I never could change this colour because it don't react to the setting of colour for comments. After many attemps the problem became bigger because now all the comments that were not done by Game Review are in black and I can't change it's colour. Apparently annotations are not changing colour anymore either and they show in black too, etc. |

Uh oh!
There was an error while loading. Please reload this page.
This feature is all David Crandall’s original work. David designed the Game Review approach, the coach layer, and the report in his game-review plugin for scidCommunity; scidCommunity’s Game Review and Move Comment features are that work brought into the main application. Thank you, David! David has made a number of other contributions (including a better database lock mechanism).
The Engine Window now has two review buttons: Game Review and Move Comment. Both write into the open game, and both run on their own engine connection, so they do not disturb the engine analysis you are watching.
Game Review
Game Review reviews the whole main line. For each move it writes:
[%eval];Moves still inside the opening book are marked Book rather than judged. The board is returned to where you left it, and Cancel writes nothing.
How moves are rated
This is not the old fixed centipawn-drop annotation. The review converts the engine score into an expected win percentage and measures how much that expectation dropped. The label thresholds are adapted from Patzer’s classifier (MIT), and the win-percentage and accuracy math follows Lichess’s published method.
The main ladder is:
Context labels such as Forced, Book, Brilliant, Great and Miss read the position and the engine’s other lines, not just the score. The result is much closer to a Lichess Game Analysis than to the old centipawn-drop annotator: the same two-pawn loss in a level position and in an already winning position is no longer treated as the same mistake.
Coach comments
Coach prose is optional and off by default. It needs a provider and model configured in Coach settings.
With Coach on, a whole-game review adds:
[Coach]line at up to ten mistakes, misses and blunders.The coach is deliberately tightly constrained. It is not asked to analyse the position from scratch. It receives a deterministic FACTS block — the move, the board, attacks, hanging pieces, castling, en passant, the fifty-move clock, repetition, material and the engine’s lines in SAN — and the prompt tells it to use only what is in that block. It is told not to invent moves, squares or numbers, and the label words are named only to be banned. It writes in the UI language, is capped at 600 characters, and never changes a label,
[%eval]or variation.If a coach request fails, the review is still complete; that move or phase simply has no prose. Re-running a review replaces the old coach prose rather than stacking it.
Move Comment
Move Comment judges only the move you are on — the move that produced the position on the board. It writes the label,
[%eval]and the marks that move earns, and leaves the rest of the game alone. It writes no game report and no coach prose.Settings and batch
Review Settings controls lines, depth, the time cap, variations, the variation margin, diagrams and the Coach prose switch. Coach settings opens the provider/model configuration.
The same review writer is used by Batch annotate from the Game List, so a batch of games gets the same labels and report; the batch path does not add coach prose.
To try it: open an Engine Window, load a game, and press Game Review. To comment on one move, put the cursor on it and press Move Comment.
All reactions