Siderite / Siderite/lichessTools
Extra chess visualizations
Open
Nobody has claimed this yet.
exploration
- Dominant language
- JavaScript
- Stars
- 92
- Forks
- 20
- Avg merge
- 19h 59m
- Merged PRs (30d)
- 1
Description
This task is just about finding and cataloguing new ideas related to chess data visualization.
Some ideas:
- for a chess game, the average position of all white and black pieces move by move, weighted by the size of each “army” will show the slow movement of overall mass of white and black pieces. (see https://questionsindataviz.com/2017/04/02/how-do-you-visualise-chess-games/)
- for a chess game, show the trajectories of every piece (see https://questionsindataviz.com/2017/04/02/how-do-you-visualise-chess-games/)
- some statistics ? I don't want to overlap with the Lichess Tutor (some ideas here: https://arxiv.org/pdf/2304.11425.pdf)
- take a look at ChessY library (see https://hal.science/hal-02391009/document)
- a way to determine the width of a chess path. For example if there is only one move that doesn't lose the path is narrow, if there are many OK moves, the path would be wide.
- Some huge paper here: Predicting the Outcome of a Chess Game by Statistical and Machine Learning techniques (https://upcommons.upc.edu/bitstream/handle/2117/106389/119749.pdf?sequence=1&isAllowed=y )
- heatmaps (see https://blog.ebemunk.com/a-visual-look-at-2-million-chess-games/ and https://blog.ebemunk.com/visual-look-at-2-million-chess-games-part-2/)
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 implementation file, test, or entry point is identified. Start by narrowing the listed visualization ideas and reviewing the linked chess-visualization references; define one concrete visualization and its completion criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100