Share your how-to-use (analytic purposes)

Sort:
junji90

Hello, scid users!

I have a laptop running OpenSUSE 13.1 Linux. I have been looking for a way to analyze my game using scid.

I like scid because it is an opensource project and is developing always around the world. And I know scid has tons of attractive features such as
- Tactics: Review game
- Tactics: Calculation of variations
- Tactics: Find best moves
However due to lack of Help descriptions and the internet sources, I am not able to use them. I spent whole days yesterday and today on how to use them, no luck.

The only way I am okay with analyzing my games are this, using Analysis Engine / Annotation.

Step 1: Open my game and run an analysis engine (Stockfish on my machine)
Step 2: Let the engine annotate my game, with following options {"For White(my coloer) moves only", Threshold = 0.5, Uncheck anything else}
Step 3: Move to the position at where those I find as blunders, and play against the engine. You can do this by {Play -> Serious game -> Check 'Coach is watching'}
Step 4: Don't look at the Notation window or so and simulate another line play against the engine
Step 5: After you are okay with the alternative lines, you could fully see the analysis results or anything you want.

Ideally speaking, I expect scid to mark only blunder symbols '?'/'??' to my moves as notation and let me think the alternative moves. But well, the current way is still okay.

Could you share your experiences?

Thanks!

Junji

katar

I just scroll thru moves while the engine is running.  After doing your auto-annotate, you can go to Edit menu, "strip variations" to get rid of all the auto-generated variations if you don't want them.

There are several tutorial videos online that you may find helpful if you search for them.  :)

MrWayne

I am running SCID 4.2.2 with toga as the engine.  I set up anylisis 300 seconds (max time) 5 minutes a move is a long time.  Anylize all moves, threshold 3, then the rest as I preffer.  Usally let this run over night  as it takes a while at 5 minutes per move.  When I review the game I am not just looking for blunders as marked by SCID.  What I really pay attention to is the score changes between my move and opponent.  My main concern at this time is the 1st 15 moves.  If I see a score change that shifts a lot in a negative direction from my perspective, I will run tga to anylize that move no less than 180 seconds for internet games & 300 seconds minimum for OTB games.  I add the information into my repertoire & the tree function for that opening for the 1st 15 moves.  Anything after 15 moves I review as I see fit.  Once the game is completed I transfer it from a working database to my personall games database for future refference usually via the tree search function.  May be this might be of help