Timeline for What are good ways to check blunders after the match?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2014 at 18:10 | comment | added | Alan | @wisnuops I think the harder part of the problem is, given a set of moves and position evaluations, what is a blunder? What's the difference between your opponent's brilliancy and your blunder? Obviousness? I think you'll likely get a list of potential blunders unless you create a more sophisticated approach then comparing evals before/after. A blunder for a master may be nothing to a novice. | |
| Jun 4, 2014 at 18:06 | comment | added | Alan | @wisnuops Not exact tips, I'd start by understanding the format of everything. You know PGN is your input, figure out how to separate each game and each move. Chess engines use UCI communication interface I think, You'd probably start the process in python and grab it's standard input/output. Write the moves, wait X time, grab evaluation. For Python, you need to research launching a process (chess engine), getting its standard in and out, parsing text, writing text files. Build it step by step, test each part, put them together. Post problems you have on stackoverflow.com =) | |
| Jun 4, 2014 at 17:08 | comment | added | wisnuops | That's a cool idea. Do you have any tips for me about writing the program with Python? | |
| Jun 4, 2014 at 14:21 | history | answered | Alan | CC BY-SA 3.0 |