Jumbo 0.6.34

[Sven]

just released

Mainly Gaviota EGTB support was improved/fixed. For that purpose I also added a configuration file "jumbo.ini". Strength should be about the same as 0.6.31 (around 2480-2500 @CCRL 40/40).

[tpoppins]

There must be a problem with this new file, jumbo.ini. With it present jumbo64-0.6.34-bb.exe produces a blank screen with a blinking cursor that accepts no input, when run from the command line. In Cute Chess GUI the engine doesn't move. Without jumbo.ini everything is fine. You can config the engine options directly from the GUI, like with v0.6.10:



The format of the INI file is odd. Every line begins with a "#" plus a space. Does that mean they are all commented out by default? Removing those part produces a stackdump on program termination, though:

Code: Select all

Exception: STATUS_ACCESS_VIOLATION at rip=0010044E618
rax=00000003FEF6C5E0 rbx=0000000001000000 rcx=0000000600018040
rdx=0000000000000000 rsi=0000000000000000 rdi=00000003FEF6C5E0
r8 =00000000FFFF9B0C r9 =000000018013D2D0 r10=0000000100000000
r11=00000003FEF0F852 r12=00000000FFFFA0A0 r13=00000000FFFF9BF0
r14=00000000FFFFA0D0 r15=00000000FFFF9C03
rbp=0000000000000100 rsp=00000000FFFF9B60
program=C:\Program Files\ChessBase\Engines.x64\jumbo64-0.6.34-bb.exe, pid 8540, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

Running on Win7 x64 Pro.

[Graham Banks]

There must be a problem with this new file, jumbo.ini. With it present jumbo64-0.6.34-bb.exe produces a blank screen with a blinking cursor that accepts no input, when run from the command line. In Cute Chess GUI the engine doesn't move. Without jumbo.ini everything is fine. You can config the engine options directly from the GUI, like with v0.6.10:



The format of the INI file is odd. Every line begins with a "#" plus a space. Does that mean they are all commented out by default? Removing those part produces a stackdump on program termination, though:

Code: Select all

Exception: STATUS_ACCESS_VIOLATION at rip=0010044E618
rax=00000003FEF6C5E0 rbx=0000000001000000 rcx=0000000600018040
rdx=0000000000000000 rsi=0000000000000000 rdi=00000003FEF6C5E0
r8 =00000000FFFF9B0C r9 =000000018013D2D0 r10=0000000100000000
r11=00000003FEF0F852 r12=00000000FFFFA0A0 r13=00000000FFFF9BF0
r14=00000000FFFFA0D0 r15=00000000FFFF9C03
rbp=0000000000000100 rsp=00000000FFFF9B60
program=C:\Program Files\ChessBase\Engines.x64\jumbo64-0.6.34-bb.exe, pid 8540, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

Running on Win7 x64 Pro.

Rename the ini file to Jumbo1.ini

[Sven]

There must be a problem with this new file, jumbo.ini. With it present jumbo64-0.6.34-bb.exe produces a blank screen with a blinking cursor that accepts no input, when run from the command line. In Cute Chess GUI the engine doesn't move. Without jumbo.ini everything is fine. You can config the engine options directly from the GUI, like with v0.6.10:

[...]

The format of the INI file is odd. Every line begins with a "#" plus a space. Does that mean they are all commented out by default? Removing those part produces a stackdump on program termination, though:

[...]

Thanks for this detailled bug report. I already heard about the bug yesterday. Version 0.6.34 is definitely broken. Introduction of an ini file was one of the main changes after I was told that it was not possible to configure the EGT path with ChessGUI (in the meantime I believe it was mainly due to the lack of the "gtbPath" option but ini files seem to be necessary in some special cases anyway). Obviously I messed up something right before releasing a version that had already been working before.

The format of the ini file is as intended, and pretty standard IMO. By default all possible settings are commented out with a '#' character so that the compile time defaults are used. Changing one of the settings requires to remove the comment character.

Up to now I had no spare time to work on a fix. I will try to do so tonight and upload a new version, probably 0.6.35, as soon as possible. As reported, 0.6.34 can be used without an ini file (renaming or removing it is the same since Jumbo expects a fixed file name "jumbo.ini") but that does not make much sense since there would be no relevant difference to 0.6.31 in that case.

[Sven]

Up to now I had no spare time to work on a fix. I will try to do so tonight and upload a new version

Jumbo 0.6.35 is there, fixes exactly the bug mentioned above. "jumbo.ini" can now be used if necessary.

[CMCanavessi]

The link in your website still points to 0.6.34 zip file, is that ok?


Edit: here's the correct link for every1: http://www.schuelebln.de/chess/jumbo/ju ... 35-x64.zip

[Sven]

The link in your website still points to 0.6.34 zip file, is that ok?


Edit: here's the correct link for every1: http://www.schuelebln.de/chess/jumbo/ju ... 35-x64.zip

Oops - thanks for reporting! I'll fix that tomorrow.

[tpoppins]

[...]
I will try to do so tonight and upload a new version, probably 0.6.35, as soon as possible. As reported, 0.6.34 can be used without an ini file (renaming or removing it is the same since Jumbo expects a fixed file name "jumbo.ini") but that does not make much sense since there would be no relevant difference to 0.6.31 in that case.

Thank you for the explanation, Sven.

If I understand you correctly, there are no other functional differences between v0.6.31 and v0.6.35 (nothing that should affect playing strength, at any rate), so we can safely proceed to combine the two versions on our lists, right?

[Sven]

[...]
I will try to do so tonight and upload a new version, probably 0.6.35, as soon as possible. As reported, 0.6.34 can be used without an ini file (renaming or removing it is the same since Jumbo expects a fixed file name "jumbo.ini") but that does not make much sense since there would be no relevant difference to 0.6.31 in that case.

Thank you for the explanation, Sven.

If I understand you correctly, there are no other functional differences between v0.6.31 and v0.6.35 (nothing that should affect playing strength, at any rate), so we can safely proceed to combine the two versions on our lists, right?

No. Either use one or the other. I am always against combining results of two different versions. There might be strength differences since I also made a change in the evaluation (first attempt of introducing material imbalance evaluation) and performed the usual tuning afterwards. My own tests with ultra-fast games showed no relevant difference - therefore my comment - but LTC may be different. So my advice is, as always, treat a different version as a different thing.

[Sven]

The link in your website still points to 0.6.34 zip file, is that ok?


Edit: here's the correct link for every1: http://www.schuelebln.de/chess/jumbo/ju ... 35-x64.zip

Oops - thanks for reporting! I'll fix that tomorrow.

Fixed.