Wanted to take another look at Drofa...which on my initial test, locked up the Pi. Not sure what happened then, but Drofa calculated a full game this time around...albeit a weak game. Drofa was badly beaten by tabletop Tasc R30...Drofa 14. Qf2?? was Game Over:
Found some info on the web... From the author: "Drofa started as fork of the Shallow Blue chess engine." Well, that explains the weak play...Shallowblue is quite weak.
so...Gave Drofa a chance against Excalibur Ivan...which is about 1800 (I also gave Ivan a time handicap of 10s/mv vs Drofa 30s/mv). Drofa had a winning game by move 22, but blundered with inexplicable 22. Qxd5???? Game Over. That's bad...the author needs to fix that.
Looks like Drofa is very weak, but apparently FF on the Pi (the Pi lockup on the initial test game is a mystery).
Sc@lly likes this post
Guest Guest
Subject: Re: first post Thu Dec 24, 2020 3:38 pm
Your compilation seems buggy, or you were doing something wrong. Neither 2.02dev, nor official 2.00 plays those moves in both games (even compiled 2.02dev today, just to check your strange games).
Just one example, (Qf2 is not considered, but it is no error BTW), the real incredible error Qg3??? never is searched at all
FYI Drofa 2.00 already was over 800! rating points above ShallowBlue...
Piman wrote:
Drofa 2.0.2 Normal
Wanted to take another look at Drofa...which on my initial test, locked up the Pi. Not sure what happened then, but Drofa calculated a full game this time around...albeit a weak game. Drofa was badly beaten by tabletop Tasc R30...Drofa 14. Qf2?? was Game Over:
Found some info on the web... From the author: "Drofa started as fork of the Shallow Blue chess engine." Well, that explains the weak play...Shallowblue is quite weak.
so...Gave Drofa a chance against Excalibur Ivan...which is about 1800 (I also gave Ivan a time handicap of 10s/mv vs Drofa 30s/mv). Drofa had a winning game by move 22, but blundered with inexplicable 22. Qxd5???? Game Over. That's bad...the author needs to fix that.
Looks like Drofa is very weak, but apparently FF on the Pi (the Pi lockup on the initial test game is a mystery).
Piman
Posts : 114 Join date : 2020-11-23
Subject: Re: first post Thu Dec 24, 2020 4:09 pm
temporarily wrote:
Your compilation seems buggy, or you were doing something wrong.
Thank you for the feedback. Just an FYI: I DON'T compile...I just test the Pi3B compiled engines as they are presented to me. You need to have a PM with Scally to figure out what's going on. I test. And clearly my tests have found that something in the compile is not correct....and that initial Pi freeze game (which now I am convinced was not a fluke) is another clue as to what hasn't ported correctly to the Pi.
I'd like to see your engine run, correctly...as it's supposed to ...on the Pi.
This is fixable and issues like this have been seen previously on other engines....and they were fixed. 800 points is an excellent improvement. Let's get Drofa working on the Pi. Your input to Scally will help him.
Piman
Posts : 114 Join date : 2020-11-23
Subject: Re: first post Thu Dec 24, 2020 4:15 pm
I just checked your comment:
Just one example, (Qf2 is not considered, but it is no error BTW), the real incredible error Qg3??? never is searched at all
You are correct, my bad: Qf2 is not the error move....Qg3?? is the loser. Apparently, I was having a small TIA at the time of that typing.