A complete rewrite of Nirvana has been done. This brought the engine into the modern age by converting to bitboards. This also allowed me to clean up a lot of the code and will make future improvements even easier. The biggest part of this release is addition of multithreading support. This was done via the lazy smp method described elsewhere on this board.
fantastic.
I will switched in my still running tourney to NirvanaChess 2.0.
Do you saw that NirvanaChess 1.8 have a really big Problem in KingSafty compare to version 1.7. Your version 1.8 lost a lot of games very very fast. That is the reason that version 1.7 is around 10-20 Elo stronger as version 1.8.
Thanks for your new version.
I will delete the 300 games I have for version 1.8 in my FCT1 - 2015 - tourney and will replay the games with version 2.0.
Yes this is due to the lazy evaluation, which gained the engine a lot of speed at the expense of having a less accurate king safety function. This wasn't an issue in self play but as you saw, and as I later saw, in gauntlet play this is actually a fairly large regression. This has been removed in this version.
As always, thank you very much for your testing. Its very good to see how Nirvana preforms under various conditions and against various opponents.
After the still running Equinox 3.30 x64 round Robin (Need around 6.5 days, started in the night) your version 2.0 will replay the games from version 1.8.
An other Problem I have with Tornado 6 in my still running FCT1 - 2015 - tourney. Version 5.0 is clearly stronger.
Tornado development is stopped. I will replaced Tornado 6.0 with DisasterArea and in this case two changes I have to make if I restart this tourney in 6.5 days.
Very interesting in testing NirvanaChess ... I am waiting of your new version, available now after the big work you do in the last months!
cetormenter wrote:A complete rewrite of Nirvana has been done. This brought the engine into the modern age by converting to bitboards. This also allowed me to clean up a lot of the code and will make future improvements even easier. The biggest part of this release is addition of multithreading support. This was done via the lazy smp method described elsewhere on this board.
So were talking about an improvement of 100-120 Elo comparing to version 1.8
Dr.D
_No one can hit as hard as life.But it ain’t about how hard you can hit.It’s about how hard you can get hit and keep moving forward.How much you can take and keep moving forward….
problem here: does NOT run on AMD-FX6300 (six core)
no problems on Intel (older C2D, i5-520, i7)
could you provide a compile which runs on AMD too?
would be nice...
same problem as @Gabor: readme says "three" different versions, but rar-file only contains one .exe which is not limited to modern systems but to Intel (seemingly)...
Could anyone with similar (AMD) hardware countercheck? Ray?
So were talking about an improvement of 100-120 Elo comparing to version 1.8
Dr.D
Hopefully! We shall see soon on the rating lists. Just in raw speed there quite a significant gain. Not to mention the bug fixes to the evaluation function.
Gabor Szots wrote:
Thomas, I have found only one exe in the package. Is that 64-bit? It does run on my Q6600, which makes me wonder.
Yes there is only a 64 bit compile but I suppose it doesn't hurt to create a 32 bit compile too.
Wolfgang Battig wrote:
PostPosted: Wed Dec 17, 2014 6:00 pm Post subject: Re: Nirvanachess 2.0 Release
problem here: does NOT run on AMD-FX6300 (six core) Sad
no problems on Intel (older C2D, i5-520, i7)
could you provide a compile which runs on AMD too?
would be nice... Wink
same problem as @Gabor: readme says "three" different versions, but rar-file only contains one .exe which is not limited to modern systems but to Intel (seemingly)...
Could anyone with similar (AMD) hardware countercheck? Ray?
I think the AMD cpu must not have access to the bitscan functions. I have reuploaded this time including both a 64 bit compile without those functions and a 32 bit compile. This does incur a slight speed drop however it is only about 2%. Hopefully this fixes the issue. If not then I am at a loss.