Comments on https://lichess.org/@/totalnoob69/blog/did-you-know-lichess-can-do-this-opening-explorer-and-tablebase/VNqhhHnD
You are right, many features like these are ignored in lichess. Thanks for highlighting them!
You are right, many features like these are ignored in lichess. Thanks for highlighting them!
Nice write up. This will help people see the cool features.
I like the Explorer Evaluation on the opening database. It very useful and looks futuristic.
@TotalNoob69
Nice write up. This will help people see the cool features.
I like the Explorer Evaluation on the opening database. It very useful and looks futuristic.
I was already familiar with Opening Explorer and had used it occasionally, but the many details about its options and filters were new to me.
Thank you for your helpful article - great stuff!
I was already familiar with Opening Explorer and had used it occasionally, but the many details about its options and filters were new to me.
Thank you for your helpful article - great stuff!
The problem is the player section only works about a quarter of the time. The other time it just endlessly says indexing other players first.
The problem is the player section only works about a quarter of the time. The other time it just endlessly says indexing other players first.
@RematchMe said in #5:
The problem is the player section only works about a quarter of the time. The other time it just endlessly says indexing other players first.
The indexing for a specific set of parameters is being done automatically for the Lichess database, but on demand for players. So the idea is you have to request it and wait. Next time it should be available. But if a lot of players ask this, you are stuck, indeed.
I am not familiar with the server architecture of the Explorer database, but extracting all the games of a player, determining all of the positions in them and then aggregating the results is not trivial. If you think of each rating bracket and each time interval in months since the beginning of Lichess and each time control, you get about 100 or 1000 "columns" that you could assign to a position. If you add all the players in Lichess, things explode.
Maybe I can think of a way to solve this with LiChess Tools, but it's a bit wild.
@RematchMe said in #5:
> The problem is the player section only works about a quarter of the time. The other time it just endlessly says indexing other players first.
The indexing for a specific set of parameters is being done automatically for the Lichess database, but on demand for players. So the idea is you have to request it and wait. Next time it should be available. But if a lot of players ask this, you are stuck, indeed.
I am not familiar with the server architecture of the Explorer database, but extracting all the games of a player, determining all of the positions in them and then aggregating the results is not trivial. If you think of each rating bracket and each time interval in months since the beginning of Lichess and each time control, you get about 100 or 1000 "columns" that you could assign to a position. If you add all the players in Lichess, things explode.
Maybe I can think of a way to solve this with LiChess Tools, but it's a bit wild.
Perhaps I'm not understanding it correctly. If you leave the screen after requesting the service, the request continues and you come back at a later time? If so making that clear would be useful. I assumed that if you leave the opening explorer screen that the process would have to start over. Still not convenient but at least it would be better understood with clear messaging
Perhaps I'm not understanding it correctly. If you leave the screen after requesting the service, the request continues and you come back at a later time? If so making that clear would be useful. I assumed that if you leave the opening explorer screen that the process would have to start over. Still not convenient but at least it would be better understood with clear messaging
Very nice and clear explanation of this feature.
Imho articles like this one are more tutorials than "just" Blog posts (that appear only temporarily on the frontpage) and as such they deserve to be collected under an extra menu entry on the front page like "Tutorials" or "Features description" to be easily available permanently.
Very nice and clear explanation of this feature.
Imho articles like this one are more tutorials than "just" Blog posts (that appear only temporarily on the frontpage) and as such they deserve to be collected under an extra menu entry on the front page like "Tutorials" or "Features description" to be easily available permanently.
Why not put in the home page something like a "did you know?" widget? Something discreet but visible?
Why not put in the home page something like a "did you know?" widget? Something discreet but visible?
I have been considering adding some feeds in LiChess Tools: chess news, LiChess Tools updates, selected blogs I guess, but there is always the issue of curation. I wouldn't want to be the one choosing what is good and what is bad.
I have been considering adding some feeds in LiChess Tools: chess news, LiChess Tools updates, selected blogs I guess, but there is always the issue of curation. I wouldn't want to be the one choosing what is good and what is bad.





