Weini questions

[Gabor Szots]

1. What is its approximate strength?
2. Does it accept level command (and other commands) from the GUI or will it take time control from json?

[xr_a_y]

1. Between 2200 and 2300
2. Yes winboard TC commands are available (json tc things are here only for debug purpose)

[Gabor Szots]

Thanks. A few more:

Why the name? By its look it is more like a German nickname than a French word.
Does it support the memory command? Or a command line parameter to set hash?

[xr_a_y]

The name "Weini" has the same letter as my first name "vveini" -> "vivien" and also means "WisEness Is Not Inside". For the record there is also a climbing route with this name (https://www.camptocamp.org/waypoints/35 ... e-gournier) in Auvergne where I leave.

Weini does not support memory command, you can use the json config file to set different hash table size or use

Code: Select all

setoption XXXX YYYYY

inside the GUI or cutechess (via CLOP for example).

The TT size are

"ttSize" : TT for negamax
"ttQSize" : TT for QSearch
"ttESize" : TT for evaluation
"ttELSize" : TT for lazy evaluation (not used by default)
"ttEPSize" : TT for pawn evaluation

The most influent TT size are negamax, evaluation and pawn evaluation.

[xr_a_y]

It should be easy to made all option available also by the command line... I'll play with this soon.

[Gabor Szots]

Thanks Vivien.

[Gabor Szots]

Those TT sizes are a bit nebulous. I have figured out that "ttSize" increases the hash size by approximately in the sequence 37MB-74MB-148MB-292MB. E.g. to set 148 MB I have to give "ttSize" a value in the 2100000 - 4100000 range (Weini makes a rounding down).
I have not come to a formula regarding the rest of the tables. Some more easy to understand values (e.g. direct MB's) could certainly help.

[xr_a_y]

Yes oops, it isn't clear at all indeed.

All TT size work as follows :
- the TT size is the number of bucket in the TT, not the Mb used.
- the TT size given is always rounded to the previous power of 2

If you run Weini in the command line without any argument, you'll get more detail on memory really used.

Code: Select all

#INFO    - 2018-08-08 13:39:49-161: Init TT
#INFO    - 2018-08-08 13:39:49-161: Adapted TT size 1048576
#INFO    - 2018-08-08 13:39:49-161: Size of TT 36Mo
#INFO    - 2018-08-08 13:39:49-185: Init TTQ
#INFO    - 2018-08-08 13:39:49-185: Adapted QTT size 262144
#INFO    - 2018-08-08 13:39:49-190: Size of QTT 9Mo
#INFO    - 2018-08-08 13:39:49-190: Init TTE
#INFO    - 2018-08-08 13:39:49-190: Adapted ETT size 524288
#INFO    - 2018-08-08 13:39:49-190: Size of ETT 8Mo
#INFO    - 2018-08-08 13:39:49-194: Init TTEL
#INFO    - 2018-08-08 13:39:49-194: Adapted ETT size 262144
#INFO    - 2018-08-08 13:39:49-194: Size of ETT 4Mo
#INFO    - 2018-08-08 13:39:49-196: Init TTEP
#INFO    - 2018-08-08 13:39:49-196: Adapted ETT size 262144
#INFO    - 2018-08-08 13:39:49-196: Size of ETT 4Mo

[Gabor Szots]

Yes oops, it isn't clear at all indeed.

All TT size work as follows :
- the TT size is the number of bucket in the TT, not the Mb used.
- the TT size given is always rounded to the previous power of 2

If you run Weini in the command line without any argument, you'll get more detail on memory really used.

Code: Select all

#INFO    - 2018-08-08 13:39:49-161: Init TT
#INFO    - 2018-08-08 13:39:49-161: Adapted TT size 1048576
#INFO    - 2018-08-08 13:39:49-161: Size of TT 36Mo
#INFO    - 2018-08-08 13:39:49-185: Init TTQ
#INFO    - 2018-08-08 13:39:49-185: Adapted QTT size 262144
#INFO    - 2018-08-08 13:39:49-190: Size of QTT 9Mo
#INFO    - 2018-08-08 13:39:49-190: Init TTE
#INFO    - 2018-08-08 13:39:49-190: Adapted ETT size 524288
#INFO    - 2018-08-08 13:39:49-190: Size of ETT 8Mo
#INFO    - 2018-08-08 13:39:49-194: Init TTEL
#INFO    - 2018-08-08 13:39:49-194: Adapted ETT size 262144
#INFO    - 2018-08-08 13:39:49-194: Size of ETT 4Mo
#INFO    - 2018-08-08 13:39:49-196: Init TTEP
#INFO    - 2018-08-08 13:39:49-196: Adapted ETT size 262144
#INFO    - 2018-08-08 13:39:49-196: Size of ETT 4Mo

Ah, that certainly helps.

[AndrewGrant]

Yes oops, it isn't clear at all indeed.

All TT size work as follows :
- the TT size is the number of bucket in the TT, not the Mb used.
- the TT size given is always rounded to the previous power of 2

If you run Weini in the command line without any argument, you'll get more detail on memory really used.

Code: Select all

#INFO    - 2018-08-08 13:39:49-161: Init TT
#INFO    - 2018-08-08 13:39:49-161: Adapted TT size 1048576
#INFO    - 2018-08-08 13:39:49-161: Size of TT 36Mo
#INFO    - 2018-08-08 13:39:49-185: Init TTQ
#INFO    - 2018-08-08 13:39:49-185: Adapted QTT size 262144
#INFO    - 2018-08-08 13:39:49-190: Size of QTT 9Mo
#INFO    - 2018-08-08 13:39:49-190: Init TTE
#INFO    - 2018-08-08 13:39:49-190: Adapted ETT size 524288
#INFO    - 2018-08-08 13:39:49-190: Size of ETT 8Mo
#INFO    - 2018-08-08 13:39:49-194: Init TTEL
#INFO    - 2018-08-08 13:39:49-194: Adapted ETT size 262144
#INFO    - 2018-08-08 13:39:49-194: Size of ETT 4Mo
#INFO    - 2018-08-08 13:39:49-196: Init TTEP
#INFO    - 2018-08-08 13:39:49-196: Adapted ETT size 262144
#INFO    - 2018-08-08 13:39:49-196: Size of ETT 4Mo

Ah, that certainly helps.

You need to change this to match convention. Rounding to power of 2 below is common place. Cryptic sizes to TTsizes are not