Page 1 of 1

Arasan 10.4

PostPosted: 27 Jun 2008, 23:38
by jdart
Arasan 10.4 is available from http://www.arasanchess.org.

This is not exactly the version that played in the recent WCRCC tourney, but it is close to it.

Changes in Arasan 10.4:
1) Speedup illegal move detection in search.
2) Speedups in move generation.
3) Improved move ordering for check evasions.
4) Use IID more sparingly.
5) Several scoring changes, esp. fixes/improvements to material scoring.
6) Fix to "bk" command (to list opening book moves).
7) Time usage fixes/improvements.
8) A couple of locking fixes for more stable SMP operation.
9) Fix for invalid moves propagated to pv list
10) Clear history data before each search in testsuite mode.

Plus open book additions/fixes, as usual.

--Jon

Re: Arasan 10.4

PostPosted: 10 Jul 2008, 16:08
by Richard Allbert
Thanks for the notification.

An engine close to my heart - the first one I ever downloaded to play against before I even looked at programming :)

Richard

Re: Arasan 10.4

PostPosted: 21 Jul 2008, 23:00
by Vegan
I not sure why but I have had trouble using Arasan in Arena with Win XP x64

Re: Arasan 10.4

PostPosted: 26 Jul 2008, 15:00
by Gábor Szots
Vegan wrote:I not sure why but I have had trouble using Arasan in Arena with Win XP x64


Please be specific else no one will be able to help you. I for one have never had any problem using Arasan under Arena with Win XP x64. Maybe you tried to use te 32-bit executable?

Re: Arasan 10.4

PostPosted: 29 Jul 2008, 03:31
by Norm Pollock
Arasan 10.4 does not see this under-promotion mate:

Code: Select all

[Event "Q-234"]
[Site "?"]
[Date "2008.07.28"]
[Round "2.3"]
[White "Xpdnt 080716"]
[Black "Arasan 10.4"]
[Result "1-0"]
[ECO "E15"]
[Annotator "0.27;0.06"]
[PlyCount "91"]
[EventDate "2008.07.28"]
[EventType "tourn"]
[Source "Pollock"]
[TimeControl "60+1"]

{AMD Athlon(tm) XP 3000+ 2100 MHz  W=10.4 ply; 351kN/s; composite.ctg  B=12.0
ply; 606kN/s; composite.ctg} 1. d4 {[%eval 0,0] [%emt 0:00:00]} Nf6 {
[%eval 0,0] [%emt 0:00:00]} 2. c4 {[%eval 0,0] [%emt 0:00:00]} e6 {
[%eval 0,0] [%emt 0:00:00]} 3. Nf3 {[%eval 0,0] [%emt 0:00:00]} b6 {
[%eval 0,0] [%emt 0:00:00]} 4. g3 {[%eval 0,0] [%emt 0:00:00]} Ba6 {
[%eval 0,0] [%emt 0:00:00]} 5. b3 {[%eval 0,0] [%emt 0:00:00]} Bb4+ {
[%eval 0,0] [%emt 0:00:00]} 6. Bd2 {[%eval 0,0] [%emt 0:00:00]} Be7 {
[%eval 0,0] [%emt 0:00:00]} 7. Bg2 {[%eval 0,0] [%emt 0:00:00]} c6 {
[%eval 0,0] [%emt 0:00:00]} 8. Bc3 {[%eval 0,0] [%emt 0:00:00]} d5 {
[%eval 0,0] [%emt 0:00:00]} 9. Nbd2 {[%eval 0,0] [%emt 0:00:00]} Nbd7 {
[%eval 0,0] [%emt 0:00:00]} 10. O-O {[%eval 0,0] [%emt 0:00:00]} O-O {
[%eval 0,0] [%emt 0:00:00]} 11. Re1 {[%eval 0,0] [%emt 0:00:00]} c5 {
[%eval 0,0] [%emt 0:00:00]} 12. e4 {[%eval 0,0] [%emt 0:00:00]} dxc4 {
[%eval 0,0] [%emt 0:00:00]} 13. bxc4 {[%eval 0,0] [%emt 0:00:00]} cxd4 {
[%eval 0,0] [%emt 0:00:00]} 14. Nxd4 {[%eval 0,0] [%emt 0:00:00]} Ne5 {
[%eval 0,0] [%emt 0:00:00]} 15. Nxe6 {[%eval 0,0] [%emt 0:00:00]} fxe6 {
[%eval 0,0] [%emt 0:00:00]} 16. Bxe5 {[%eval 27,9] [%emt 0:00:04]} Bb4 {
[%eval 6,12] [%emt 0:00:06]} 17. Bf4 {(Re2) [%eval 30,9] [%emt 0:00:02]} e5 {
[%eval 18,10] [%emt 0:00:05]} 18. Be3 {[%eval 30,9] [%emt 0:00:03]} Bxd2 {
(Qc7) [%eval 18,10] [%emt 0:00:05]} 19. Qxd2 {[%eval 46,10] [%emt 0:00:04]}
Bxc4 {(Qxd2) [%eval 37,10] [%emt 0:00:04]} 20. Qc3 {
(Qb4) [%eval 41,10] [%emt 0:00:04]} Qd3 {(Qc7) [%eval 50,10] [%emt 0:00:04]}
21. Qxe5 {[%eval 105,9] [%emt 0:00:04]} Rae8 {(Ng4) [%eval 50,9] [%emt 0:00:03]
} 22. Qd4 {(Qb2) [%eval 124,10] [%emt 0:00:04]} Ng4 {
[%eval 150,12] [%emt 0:00:07]} 23. Qxd3 {[%eval 138,11] [%emt 0:00:03]} Bxd3 {
[%eval 150,12] [%emt 0:00:03]} 24. Bf4 {[%eval 143,11] [%emt 0:00:05]} Ne5 {
[%eval 150,11] [%emt 0:00:03]} 25. Rac1 {(Re3) [%eval 163,11] [%emt 0:00:04]}
Bb5 {(a5) [%eval 118,12] [%emt 0:00:03]} 26. Bxe5 {
[%eval 199,12] [%emt 0:00:04]} Rxe5 {[%eval 125,12] [%emt 0:00:03]} 27. f4 {
(Bh3) [%eval 199,12] [%emt 0:00:04]} Rc5 {(Re7) [%eval 125,12] [%emt 0:00:03]}
28. e5 {(Rxc5) [%eval 213,11] [%emt 0:00:03]} Rd8 {
(Re8) [%eval 143,12] [%emt 0:00:03]} 29. Rxc5 {[%eval 251,10] [%emt 0:00:03]}
bxc5 {[%eval 146,11] [%emt 0:00:02]} 30. e6 {[%eval 254,10] [%emt 0:00:03]} Rd6
{(Rd2) [%eval 146,10] [%emt 0:00:02]} 31. h3 {(e7) [%eval 261,9] [%emt 0:00:02]
} Kf8 {(Be8) [%eval 109,12] [%emt 0:00:02]} 32. f5 {
(e7+) [%eval 147,10] [%emt 0:00:04]} Ke7 {[%eval 84,11] [%emt 0:00:02]} 33. Re5
{(Rc1) [%eval 147,10] [%emt 0:00:02]} Rd1+ {[%eval 21,12] [%emt 0:00:02]} 34.
Kh2 {[%eval 147,10] [%emt 0:00:02]} Rc1 {[%eval 84,13] [%emt 0:00:04]} 35. g4 {
[%eval 138,11] [%emt 0:00:03]} Rc2 {(a6) [%eval 75,12] [%emt 0:00:02]} 36. Kg3
{[%eval 143,11] [%emt 0:00:03]} Kf6 {(a6) [%eval 84,11] [%emt 0:00:02]} 37. Re3
{[%eval 168,9] [%emt 0:00:01]} Rxa2 {[%eval 71,11] [%emt 0:00:02]} 38. e7 {
[%eval 193,9] [%emt 0:00:02]} Be8 {(Rd2) [%eval 68,12] [%emt 0:00:02]} 39. Bd5
{(Re6+) [%eval 194,9] [%emt 0:00:01]} Ra6 {[%eval 162,13] [%emt 0:00:04]} 40.
Bg8 {[%eval 207,10] [%emt 0:00:01]} h6 {[%eval 162,12] [%emt 0:00:02]} 41. Bh7
{[%eval 199,10] [%emt 0:00:02]} c4 {(Rd6) [%eval 187,12] [%emt 0:00:02]} 42.
Bg6 {[%eval 206,10] [%emt 0:00:02]} Bb5 {[%eval 246,13] [%emt 0:00:03]} 43. Kh4
{(Kf4) [%eval 2257,11] [%emt 0:00:04]} Be8 {
(Bd7) [%eval 1131,12] [%emt 0:00:02]} 44. Bxe8 {
(Kh5) [%eval 9987,13] [%emt 0:00:00]} c3 {(g5+) [%eval 1,1] [%emt 0:00:00]} 45.
Bg6 {[%eval 9997,3] [%emt 0:00:00]} c2 {[%eval 1,1] [%emt 0:00:00]} 46. e8=N# {
[%eval 9999,3] [%emt 0:00:00]} 1-0



Re: Arasan 10.4

PostPosted: 02 Aug 2008, 15:23
by jdart
I am not quite sure what problem you are seeing.

After Black move 42. .. Bb5, White has a forced mate, but at this point Arasan doesn't have enough search time to get a mate score. It will get one if it searches long enough, though (takes a long time, for some reason).

After 43. .. c3 and 42. .. c2, the output shows a score of 1, if I read it right, which might be a bug, but notice these moves were played in 0 seconds .. Arasan will stop searching if it finds it will be checkmated for sure and so cannot improve its score. Which I am pretty sure is what happened here. So the score output might be wrong but the mate is visible.

I don't see any problem here specifically related to under-promotion (unless I am missing something).