Issues

Need a container so that the program can run on systems that aren't explicitly supported

#47

· dhodgson615 opened

on Sep 20, 2025

Everything needs to be in classes when possible for organization

#46

· dhodgson615 opened

on Sep 20, 2025

Google style docstrings needed on every function and class for consistency (including nested ones)

#43

· dhodgson615 opened

on Sep 20, 2025

Add a tool so that the script tracks the amount of times each position appears in games and use heuristics to precompute positions

#32

· dhodgson615 opened

on Sep 19, 2025

Precompute a lookup table for common positions (such as book openings)

#31

· dhodgson615 opened

on Sep 19, 2025

Make Stockfish run constantly, even when waiting on user input

#30

· dhodgson615 opened

on Sep 19, 2025

Figure out a way to cache Stockfish evaluations whenever possible

#29

· dhodgson615 opened

on Sep 19, 2025

Refactor functions to use `lru_cache` whenever possible without breaking test cases

#28

· dhodgson615 opened

on Sep 19, 2025

Consider Cython for slow parts

#27

· dhodgson615 opened

on Sep 18, 2025

Add support for full game analysis with realistic feedback for who made what mistakes, who was winning at any moment, rate of change, etc.

#26

· dhodgson615 opened

on Sep 18, 2025

Add support for 6-7 piece tablebases based on heuristics of which pieces are most likely to be the last remaining ones (or based on whichever Stockfish can compute more efficiently for low `EVAL_DEPTH` values)

#22

· dhodgson615 opened

on Sep 18, 2025

Linting and testing need to be automated based on if the relevant files were changed (so if the timestamp updates, `pytest` it)

#21

· dhodgson615 opened

on Sep 18, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Need a container so that the program can run on systems that aren't explicitly supported

Everything needs to be in classes when possible for organization

Google style docstrings needed on every function and class for consistency (including nested ones)

Add a tool so that the script tracks the amount of times each position appears in games and use heuristics to precompute positions

Precompute a lookup table for common positions (such as book openings)

Make Stockfish run constantly, even when waiting on user input

Figure out a way to cache Stockfish evaluations whenever possible

Refactor functions to use `lru_cache` whenever possible without breaking test cases

Consider Cython for slow parts

Add support for full game analysis with realistic feedback for who made what mistakes, who was winning at any moment, rate of change, etc.

Add support for 6-7 piece tablebases based on heuristics of which pieces are most likely to be the last remaining ones (or based on whichever Stockfish can compute more efficiently for low `EVAL_DEPTH` values)

Linting and testing need to be automated based on if the relevant files were changed (so if the timestamp updates, `pytest` it)

Search results