Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pause/ continue option #83

Open
al75an opened this issue Aug 6, 2021 · 3 comments
Open

Pause/ continue option #83

al75an opened this issue Aug 6, 2021 · 3 comments

Comments

@al75an
Copy link

al75an commented Aug 6, 2021

Hi Freddy,
thank you very much for this awesome utility .
Would you kindly consider adding the options 1. to pause the engine analyses and continue from where it stopped
2. to create a file, where the engine can stores the analyses scores and depth to reuse it again

@fsmosca
Copy link
Owner

fsmosca commented Aug 6, 2021

I will consider it.

  • Support interrupt/resume.

    • Read the output file and save the game headers that are already there.
    • If the game that is about to be analyzed is already in the output saved headers then skip the analysis.
  • Save analysis and use the analysis if applicable on the position.

    • For all analyzed positions save the score, depth, and engine name that analyzes the position in sqlite database.
      • Add --save-analysis flag to activate this feature.
      • If the position is already in the database, update the database if engine name is the same and current depth is deeper than what is in the database.
    • For every positions to be analyzed, check it in database, if it is there then just return the score.
      • Add --use-analysis flag to activate this feature.

fsmosca referenced this issue Aug 8, 2021
* If the game that is about to be annotated is already in the output file then the annotation is skipped.

Sample console log:

Annotating game 1...
Skip annotation, game 1 is already fully annotated.
Annotating game 2...
Skip annotation, game 2 is already fully annotated.
Annotating game 3...
Skip annotation, game 3 is already fully annotated.
Annotating game 4...
Skip annotation, game 4 is already fully annotated.
Annotating game 5...
Skip annotation, game 5 is already fully annotated.
Annotating game 6...
Skip annotation, game 6 is already fully annotated.
Annotating game 7...
Skip annotation, game 7 is already fully annotated.
Annotating game 8...
Skip annotation, game 8 is already fully annotated.
Annotating game 9...
Skip annotation, game 9 is already fully annotated.
Annotating game 10...
Skip annotation, game 10 is already fully annotated.
Annotating game 11...
Skip annotation, game 11 is already fully annotated.
Annotating game 12...
Skip annotation, game 12 is already fully annotated.
Annotating game 13...
Skip annotation, game 13 is already fully annotated.
Annotating game 14...
Skip annotation, game 14 is already fully annotated.
Annotating game 15...
Skip annotation, game 15 is already fully annotated.
Annotating game 16...
Skip annotation, game 16 is already fully annotated.
Annotating game 17...
Skip annotation, game 17 is already fully annotated.
Annotating game 18...
side: White, move_num: 1
side: Black, move_num: 1
@al75an
Copy link
Author

al75an commented Aug 12, 2021

Thank you sincerely for the awe-inspiring amount of time and effort .

@shapiro85
Copy link

Hi,
Wonderful Idea (Save analysis and use the analysis if applicable on the position.

For all analyzed positions save the score, depth, and engine name that analyzes the position in sqlite database.
Add --save-analysis flag to activate this feature.
If the position is already in the database, update the database if engine name is the same and current depth is deeper than what is in the database.
For every positions to be analyzed, check it in database, if it is there then just return the score.
Add --use-analysis flag to activate this feature.)
any updates?
this will make chess-artist an unique and powerful tool, specially if you could merge the file and share it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants