Siderite / Siderite/lichessTools
Investigate chess pro features
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 92
- Forks
- 20
- Avg merge
- 19h 59m
- Merged PRs (30d)
- 1
Description
I can tell you what are the useful functions I use, as well as pretty much every chess pro out there
- Going through recent games from big events - chessbase has a reasonable but not perfectly up-to-date online database. Ideally this should be up to date, but it's usually about 2-3 weeks delayed.
Chessbase also offers a big DB that they update regularly called "Mega Database", with excellent annotations. However, this is quite expensive, so personally I just maintain my own big database and download new games myself from a site called The Week In Chess (new games every week).
Sometimes I also download from lichess broadcasts and I will just flick through games on chessbase and analyse either with or without the engine.
Using my self-maintained database, I also search for players e.g Magnus Carlsen and flick through their games in the same way.
Preparation for my own opponents: tournaments typically give pairings a few hours before the round, so strong players always check their opponent's repertoire. Again, using my self-maintained DB, I search for my opponent and then hit the "Prepare Against" button on Chessbase which opens up a tree for the given opponent.
Creating my opening databases, and analysing with the engine or the Chessbase online games database.
Chess professionals are all about storing and organising their analysis, building upon the analysis regularly. Obviously this also includes being able to easily access their files and revise the lines regularly.
How do professionals analyse? These days, using cloud engines: chessbase allows you to borrow engines on their cloud engine platform. People loaning the engines have cores of up to 128. Includes Stockfish and Leela. I don't know how significant that is, but for sure it is way more powerful to use their engines than my average ThinkPad :)
I guess a lot of that shows the emphasis on databases and being able to store/organise effectively/stay up to date. Anyway that's a lot of the chess pro's diet!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by organizing the listed professional workflows—game databases, player and opponent preparation, opening analysis, file organization, and cloud engines—into a scoped proposal; done means the supported feature set and concrete next steps are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100