@protonspring
I think the problem is, that after Qe7, gray matter wants to play the
illegal move
Kxe7 (puts itself in check due to black's knight).
If i used this FEN string: setboard 5K2/4q3/8/5n2/8/8/8/4k3 w KQkq - 0 1
with arises after Qe7, I get the following debug output:
go
search_base::change changes state from IDLING to THINKING.
search_base::start doing requested work (hash = 6310d21dc4259cf1, status =
THINKING).
: Setting alarm to 749 csecs from now.
: Iterative deepening maxdepth set to 1.
Kxe7: terminal state 2.
Kf7: Opponent's king can be captured - illegal position.
Kg7: Opponent's king can be captured - illegal position.
Ke8: Opponent's king can be captured - illegal position.
Kg8 (Kd1): max of 35 children: 1236.
(Kxe7): max of 5 children: 0.
: Iterative deepening maxdepth set to 2.
Kxe7: terminal state 2.
Kf7: Opponent's king can be captured - illegal position.
Kg7: Opponent's king can be captured - illegal position.
Ke8: Opponent's king can be captured - illegal position.
Kg8 (Kd1): max of 35 children: 1236.
(Kxe7): max of 5 children: 0.
: Iterative deepening maxdepth set to 3.
Kxe7: terminal state 2.
Kf7: Opponent's king can be captured - illegal position.
Kg7: Opponent's king can be captured - illegal position.
Ke8: Opponent's king can be captured - illegal position.
Kg8 (Kd1): max of 35 children: 1236.
(Kxe7): max of 5 children: 0.
And finally, it prints:
move f8e7
1/2-1/2 {Insufficient material}
search_base::change changes state from THINKING to IDLING.
search_base::start doing requested work (hash = 6310d21dc4259cf1, status =
IDLING).
So yes, it wants to play the illegal move Kxe7 here...
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Think I found it.
state is INSUFFICIENT after Kxe7. There is not enough material so the game
is drawn.
This is determined before figuring out the move Kxe7 is an illegal move...
Confirmed. When I disable insufficient material checking, gray matter
finds the mate very fast.
I will close this WR and open another one which better describes this
problem.
This issue moved to defect 44.
I don't seem to be able to close issues.
Is there some power someone could grant?
Comment #11 on issue 19 by brainix: Re8 revisited
http://code.google.com/p/gray-matter/issues/detail?id=19
Hello.
I glanced through the permissions, and I couldn't figure out how to grant
project contributors the power to close issues. I'll close this one for
you, and I'll take a deeper look tonight.
If I can't figure it out, I'll make you a project owner.
Thanks,
Raj
Come to think of it - you should be able to close issues. When you start
typing, you should get some options underneath. And you should be able to
set the status to "Fixed".
I'll confirm this myself with another Google account.
Thanks,
Raj