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

a strangely lost game #3 - plummeting evaluation #98

Open
caissist opened this issue Sep 27, 2024 · 9 comments
Open

a strangely lost game #3 - plummeting evaluation #98

caissist opened this issue Sep 27, 2024 · 9 comments

Comments

@caissist
Copy link

Hi Adam,
this time Patricia ver Aug 06, 2024 was playing!
It looks to me like both games are pretty similar in terms of engine behavior?!

  • ver Aug 06, 2024
  • ver Sep 18, 2024

If my impression is correct, then there is a serious problem...
Patricia game - lost game #03.txt
Patricia game - lost game - logging #03.txt

@Adam-Kulju
Copy link
Owner

The blunders/leaps in evaluation here are only a couple pawns at a time, which is much more in line with what low skill level Patricia should do than the first games - what settings were you running her with?

@caissist
Copy link
Author

caissist commented Sep 28, 2024

The blunders/leaps in evaluation here are only a couple pawns at a time, which is much more in line

So what do you think was happening here: was this game lost by Patricia based on its playing skills, or based on a bad opening line (book)?

Both versions Sep 18, 2024 and Aug 06, 2024 were/are playing with these settings: single threaded, hash 1024/2048 Mb,
MultiPV 1.
EDIT: UCI_LimitStrength false

By the way: what do you think is correct in single threaded mode - hash 512/1024/2048 ?

Thank you.

@Adam-Kulju
Copy link
Owner

Adam-Kulju commented Sep 29, 2024

very weird. The log has it performing multiPV searches:

19:41:16.022<-info multipv 1 depth 1 seldepth 1 score cp 77 nodes 30 nps 2500 time 12 pv e5e4 
19:41:16.023<-info multipv 2 depth 1 seldepth 1 score cp 52 nodes 64 nps 4923 time 13 pv e8g8 
19:41:16.023<-info multipv 3 depth 1 seldepth 1 score cp 48 nodes 96 nps 7384 time 13 pv d8e7 
19:41:16.024<-info multipv 4 depth 1 seldepth 1 score cp 38 nodes 126 nps 9692 time 13 pv a7a5 
19:41:16.024<-info multipv 5 depth 1 seldepth 1 score cp 35 nodes 155 nps 11923 time 13 pv h7h6 

but I can't replicate that behavior when I boot up Patricia and send in those commands myself. Was the Skill_Level or UCI_Elo option turned on or anything?

I'd use a hash of 512 mbs for single threaded play, maybe even lower depending on the time control. CCRL uses 256 mbs of hash for example.

@caissist
Copy link
Author

caissist commented Sep 29, 2024

Here a complete log file for a single game. You see all engine settings which are wanted so far.
And again the engine is performing multiPV searches?!
EDIT: and engine option MultiPV is set, too!?
Patricia game - engine settings - logging.txt

Was the Skill_Level or UCI_Elo option turned on

Please, what does that mean?? To my understanding Skill_Level and UCI_Elo options will be activated only if UCI_LimitStrength is set to true?! It's a simple connection that most people certainly understand.
And on Sep 28th, 2024 I called all the engine options I used, including "UCI_LimitStrength false"...

I'd use a hash of 512 mbs for single threaded play, maybe even lower depending on the time control.

Almost all time controls are Fisher clocks 5 1. Are 512 Mb correct?

@Adam-Kulju
Copy link
Owner

Adam-Kulju commented Sep 29, 2024 via email

@caissist
Copy link
Author

caissist commented Sep 29, 2024

It's because you set the UCI_Elo option:
UCI_Elo value 3000

Adam, that's way too short - not sure if I understood correctly. UCI_Elo value 3000 is a default engine option?!
But I set "setoption name UCI_LimitStrength value false" so UCI_Elo value 3000 should be correct.

@Adam-Kulju
Copy link
Owner

hi, sorry for the late reply.
if you set the UCI_Elo value or the Skill_Level value, the engine will treat it as if UCI_LimitStrength is true. I did it properly before but changed it because people kept trying to set the skill level using only UCI_Elo and wondering why it didn't.

@caissist
Copy link
Author

caissist commented Oct 1, 2024

Adam, again way too short. The Skill_Level and UCI_Elo options are defaulted to the highest level, and setting also UCI_LimitStrength value to false should do it without any doubt - namely playing on highest level, and nothing else?!

people kept trying to set the skill level using only UCI_Elo
That is the point - me, too! To my understanding there is a need for only 2 options:

  1. UCI_LimitStrength. When set to "false" no need for anything else, all is already said. And only when setting to "true"
    then a 2nd option is necessary, namely:
  2. Skill_Level or UCI_Elo - either or!

This is a simple logic everybody can understand...

@Adam-Kulju
Copy link
Owner

It's because you set the UCI_Elo option:
UCI_Elo value 3000

Adam, that's way too short - not sure if I understood correctly. UCI_Elo value 3000 is a default engine option?! But I set "setoption name UCI_LimitStrength value false" so UCI_Elo value 3000 should be correct.

By default it doesn't expect to be sent in any "setoption name UCI_Elo value x" commands. I will fix this for Patricia 4. (I have more bugs than I can shake a stick at it seems!)

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

No branches or pull requests

2 participants