ChessMonitor – Analytics for Lichess and Chess.com
chessmonitor.com
chessmonitor.com
Classic chess are way too predictable and players who've managed to learn popular openings have an advantage. Chess960 fixes that.
And due to comparably low popularity of Chess960 I often play it with Stockfish. It has several difficulty levels which are a convenient tool for practice.
So it would be nice to include games with bots (checkbox?) on ChessMonitor as well.
I'm wondering whether people could also prepare for it if it became popular.
Slight nuance: the 960 figure includes the regular starting position, and there's some variation in different tournaments about what would happen if the classical starting position were selected. So, at least in some tournaments, it's actually Chess959. But I guess that has less of a ring to it.
One thing I'd love to know or see is common mistakes I make or the type of mistake/trap I fall into in the pivotal moments of games (some kind of fork/pin combo for me I suspect) ... and/or repeated mistakes I've made in the same position.
The main killer feature I see is combining multiple accounts. Are there any other features didn't notice?
Another key feature Lichess does not have, is the Openings page. It is very powerful when used correctly. You can look at your openings and immediately see for which openings you might need to consume more theory (or which you should not play at all).
Here is an example: https://www.chessmonitor.com/u/cdPiOkUArRJ7shVNJcT3/openings...
Do you mind sharing how it's done? I just published a library [1] that deals with syncing complex state in the URL, and I'd love to hear more about actual use-cases in the wild.
My code for that is rather simple. I'm using Next.js and the code looks something like this (a little simplified):
const router = useRouter(); // get the router/location object
const information = useFetch({ position: router.query.position }); // fetch information from the server
function changeChessPosition(newPosition) { // called when position changes
router.replace({ query: { postition: newPosition } }); // replaces the state in the URL
}
In addition, I have some caching in place so that each position is only downloaded once and the change function looks a little more complicated in my case as there are multiple values that can be change for each page.My only criticism is the search box's height seems to be a few pixels shorter than the search button.
Do you write about design or development anywhere, or have a GitHub profile? I didn't see anything linked in your profile here.
If anyone wants more info on how this works, check out this post with more details: https://www.chessmonitor.com/blog/2023-elo-calculation
I suspect that the online population — especially at lower ratings — is significantly different to the over the board population. I also expect — especially in the FIDE case — that ratings stratify the players into hobbyists, serious amateurs, professionals, etc and so different FIDE rating ranges are likely to scale to online ratings differently.
All of the above should be implicitly accounted for in an isotonic regression so long as monotonicity holds globally. You can easily do it with sklearn and I suspect it may give you better results.