lichess.org
Donate

Opening Inaccuracies Tool

@mtritchler said in #37:

I have been unable to get the tool to work. It ran yesterday for over 5 hours, spending the last 2+ hours at 99% complete, but returned nothing. Tried again overnight. The tool ran for 12 hours and was on 74% complete when I stopped it. Any ideas or suggestions?

Try with lower settings first as all the processing runs on your computer and can take time. Out of curiosity, what settings did you use?

@mtritchler said in #37: > I have been unable to get the tool to work. It ran yesterday for over 5 hours, spending the last 2+ hours at 99% complete, but returned nothing. Tried again overnight. The tool ran for 12 hours and was on 74% complete when I stopped it. Any ideas or suggestions? Try with lower settings first as all the processing runs on your computer and can take time. Out of curiosity, what settings did you use?

@koenver12 said in #40:

i will like a option to not have bullet games in it

Yee, in the final version I am going to update it so that you can choose a date range and time controls.

@koenver12 said in #40: > i will like a option to not have bullet games in it Yee, in the final version I am going to update it so that you can choose a date range and time controls.
  1. Prune the analysis to only considering moves where eval ≥ -0.5 for the side to move.
  2. Auto-adjust ply based on color
  3. Analyse a FEN might be another approach.
  4. Let the user type or past the game ID to analyse.
  5. Compare the local analysis to the server analysis. Get a server analysis first, then use Lichess export with evals=true to get %eval comments in PGN. Do a local analysis (maybe with a different engine) and generate a second opinion about the inaccuracies.
1. Prune the analysis to only considering moves where eval ≥ -0.5 for the side to move. 2. Auto-adjust ply based on color 3. Analyse a FEN might be another approach. 4. Let the user type or past the game ID to analyse. 5. Compare the local analysis to the server analysis. Get a server analysis first, then use Lichess export with evals=true to get %eval comments in PGN. Do a local analysis (maybe with a different engine) and generate a second opinion about the inaccuracies.

@HollowLeaf said in #41:

I have been unable to get the tool to work. It ran yesterday for over 5 hours, spending the last 2+ hours at 99% complete, but returned nothing. Tried again overnight. The tool ran for 12 hours and was on 74% complete when I stopped it. Any ideas or suggestions?

Try with lower settings first as all the processing runs on your computer and can take time. Out of curiosity, what settings did you use?

I used whatever the defaults were when I opened the tools link. I thought that it must be running in the cloud and did not realize that it ran on my PC. Tried it the second day and it completed fine. Must have been a resource issue with my laptop.

@HollowLeaf said in #41: > > I have been unable to get the tool to work. It ran yesterday for over 5 hours, spending the last 2+ hours at 99% complete, but returned nothing. Tried again overnight. The tool ran for 12 hours and was on 74% complete when I stopped it. Any ideas or suggestions? > > Try with lower settings first as all the processing runs on your computer and can take time. Out of curiosity, what settings did you use? I used whatever the defaults were when I opened the tools link. I thought that it must be running in the cloud and did not realize that it ran on my PC. Tried it the second day and it completed fine. Must have been a resource issue with my laptop.