lichess.org
Donate

New Tool: ChessDB Explorer

@Toscani said ^

Load a game and then press refresh "F5" function key. What should happen ?

I am assuming that you will get the fresh application, as data is not persisted.

@Toscani said [^](/forum/redirect/post/QncSF98I) > Load a game and then press refresh "F5" function key. What should happen ? I am assuming that you will get the fresh application, as data is not persisted.

@HollowLeaf said ^

I do have a Repertoire Builder for building a database (with ChessDB being one of many analytics cards), but that is a different application, however, this application is mainly to allow users to view games using ChessDB.

A viewer huh? That makes more sense now. You see, when I loaded my db, I assumed those games were analyzed and sorted on the DB panel. So it does look like a repertoire builder because it does what a repertoire builder does, at least in principle, with the missing features of saving and creating.

But then I loaded a singular game. So I assumed the moves in the DB would dissappear at the first fork, as there is no extra games from my DB, but the optional moves still persist. So IDK where are those moves being pulled from, but they are not from my games.

So, a viewer from a singular game with engine/LLM huh?.

If so, then its a different thing of what I was expecting. There is no point of adding commentary then, nor the w/d/l ratio. Those arent your games and the data is not persistent, unless you make it.

Nah, forget what I said, its another entirely different thing.

@HollowLeaf said [^](/forum/redirect/post/nqN1LFee) > I do have a Repertoire Builder for building a database (with ChessDB being one of many analytics cards), but that is a different application, however, this application is mainly to allow users to view games using ChessDB. A viewer huh? That makes more sense now. You see, when I loaded my db, I assumed those games were analyzed and sorted on the DB panel. So it does look like a repertoire builder because it does what a repertoire builder does, at least in principle, with the missing features of saving and creating. But then I loaded a singular game. So I assumed the moves in the DB would dissappear at the first fork, as there is no extra games from my DB, but the optional moves still persist. So IDK where are those moves being pulled from, but they are not from my games. So, a viewer from a singular game with engine/LLM huh?. If so, then its a different thing of what I was expecting. There is no point of adding commentary then, nor the w/d/l ratio. Those arent your games and the data is not persistent, unless you make it. Nah, forget what I said, its another entirely different thing.

@Alientcp said ^

I do have a Repertoire Builder for building a database (with ChessDB being one of many analytics cards), but that is a different application, however, this application is mainly to allow users to view games using ChessDB.

A viewer huh? That makes more sense now. You see, when I loaded my db, I assumed those games were analyzed and sorted on the DB panel. So it does look like a repertoire builder because it does what a repertoire builder does, at least in principle, with the missing features of saving and creating.

But then I loaded a singular game. So I assumed the moves in the DB would dissappear at the first fork, as there is no extra games from my DB, but the optional moves still persist. So IDK where are those moves being pulled from, but they are not from my games.

So, a viewer from a singular game with engine/LLM huh?.

If so, then its a different thing of what I was expecting. There is no point of adding commentary then, nor the w/d/l ratio. Those arent your games and the data is not persistent, unless you make it.

Nah, forget what I said, its another entirely different thing.

Check out my repertoire builder, that does exactly what you are describing, DM if you want free access.

@Alientcp said [^](/forum/redirect/post/O0Yn4O4d) > > > > I do have a Repertoire Builder for building a database (with ChessDB being one of many analytics cards), but that is a different application, however, this application is mainly to allow users to view games using ChessDB. > > A viewer huh? That makes more sense now. You see, when I loaded my db, I assumed those games were analyzed and sorted on the DB panel. So it does look like a repertoire builder because it does what a repertoire builder does, at least in principle, with the missing features of saving and creating. > > But then I loaded a singular game. So I assumed the moves in the DB would dissappear at the first fork, as there is no extra games from my DB, but the optional moves still persist. So IDK where are those moves being pulled from, but they are not from my games. > > So, a viewer from a singular game with engine/LLM huh?. > > If so, then its a different thing of what I was expecting. There is no point of adding commentary then, nor the w/d/l ratio. Those arent your games and the data is not persistent, unless you make it. > > Nah, forget what I said, its another entirely different thing. Check out my repertoire builder, that does exactly what you are describing, DM if you want free access.

Nah, forget what I said, its another entirely different thing.

ChessDB is a live database based on SF evaluations. Imagine a move tree; initially, SF shows you the PV (Principal Variation), but this sometimes changes. What the DB does is save the evaluation, meaning it's persistent. If you analyze your game, you'll reach a point where several moves aren't in the database, but because you analyzed them within the database, they remain pending. If you check them the next day (or insist on analyzing them), it will give you the evaluation. Evaluations for new nodes are 22-level deep. The tool is currently in beta, so if you upload your database, it doesn't analyze it automatically; you have to go through it pgn by pgn, move by move manually. However, there are already Python scripts that allow you to do this; I hope they will be added to the tool. There are positions where SF marks high values, but ChessDB, due to its retention and billions of saved positions, knows the value to be 0.0. There are also other cases where SF doesn't see the best play but DB already knows it.

> Nah, forget what I said, its another entirely different thing. ChessDB is a live database based on SF evaluations. Imagine a move tree; initially, SF shows you the PV (Principal Variation), but this sometimes changes. What the DB does is save the evaluation, meaning it's persistent. If you analyze your game, you'll reach a point where several moves aren't in the database, but because you analyzed them within the database, they remain pending. If you check them the next day (or insist on analyzing them), it will give you the evaluation. Evaluations for new nodes are 22-level deep. The tool is currently in beta, so if you upload your database, it doesn't analyze it automatically; you have to go through it pgn by pgn, move by move manually. However, there are already Python scripts that allow you to do this; I hope they will be added to the tool. There are positions where SF marks high values, but ChessDB, due to its retention and billions of saved positions, knows the value to be 0.0. There are also other cases where SF doesn't see the best play but DB already knows it.