Embla 2.0.5 released

[flok]

* http://vanheusden.com/Embla/files/Embla-2.0.5-win64.zip

I'll put them sources on the githubs some day.

[Graham Banks]

Thanks Folkert. Merry Christmas to you.

[flok]

Thanks Folkert. Merry Christmas to you.

Thanks!

Forgot to mention that it is a bit stronger. If I'm right about 14 elo (in single threaded mode).

[Gabor Szots]

Hi Folkert,

It seems you have removed syzygy support. Why is that?

FYI, I still cannot delete the log files created by version 1.0.3 a couple of months ago. Even administratory rights don't allow that. It seems it cast its anchor quite deeply.

[flok]

Hi Folkert,

It seems you have removed syzygy support. Why is that?

Because it doesn't help Embla. I tested it and it played worse by them on average.

FYI, I still cannot delete the log files created by version 1.0.3 a couple of months ago. Even administratory rights don't allow that. It seems it cast its anchor quite deeply.

That's odd!
Are there ':' in the filename?

[Gabor Szots]

Hi Folkert,

It seems you have removed syzygy support. Why is that?

Because it doesn't help Embla. I tested it and it played worse by them on average.

FYI, I still cannot delete the log files created by version 1.0.3 a couple of months ago. Even administratory rights don't allow that. It seems it cast its anchor quite deeply.

That's odd!
Are there ':' in the filename?

The situation is this: I can use a command line switch '-l' with a file name. If the file name is nul or nul.log, the file is written but cannot be deleted. If the file name is left empty it creates a trace.log file which can be deleted. If I use some other file name it can be deleted too.
It seems only the name 'nul' causes trouble. Not a big trouble of course, it does no harm to anything, it is just there.

No : in the filenames I have used.

Oh, and trace.log is created even if I give some other file name after -l. The contents of the files are different, e.g.
trace.log

2018-12-24 16:56:55.825998 OK Number of cores/threads detected: 4
2018-12-24 16:56:55.833599 OK Start this program as follows to see a list of options: /Embla/Embla_1.0.5-x64 -h
2018-12-24 16:57:46.457072 OK Number of cores/threads detected: 4
2018-12-24 16:57:46.464258 OK Start this program as follows to see a list of options: /Embla/Embla_1.0.5-x64 -h
2018-12-24 16:57:55.877880 OK Number of cores/threads detected: 4
2018-12-24 16:57:55.884358 OK Start this program as follows to see a list of options: /Embla/Embla_1.0.5-x64 -h

otherfile:

2018-12-24 16:56:55.836900 OK Embla v2.0.5 _1757, (C) 1996-2018 by folkert@vanheusden.com
2018-12-24 16:56:55.840461 OK cfg:
2018-12-24 16:56:55.845858 OK no _DEBUG
2018-12-24 16:56:55.849903 OK no WSJS
2018-12-24 16:56:55.853208 OK no ALWAYS_PONDER
2018-12-24 16:56:55.856421 OK no TRACE_THREADS
2018-12-24 16:56:55.860893 OK USE_TT
2018-12-24 16:56:55.864485 OK BLIND
2018-12-24 16:56:55.867608 OK WITH_CONTEMPT
2018-12-24 16:56:55.870704 OK QUIESCENCE
2018-12-24 16:56:55.874447 OK QS TT UPDATE
2018-12-24 16:56:55.878432 OK MAX_QUIESCENCE_DEPTH: 99
2018-12-24 16:56:55.882111 OK NULL_MOVE
2018-12-24 16:56:55.885269 OK NULL_MOVE_JUMP_MAX 3
2018-12-24 16:56:55.888698 OK TPT_IO_BUFFER_SIZE 1048576
2018-12-24 16:56:55.892109 OK TPT HASH-SIZE 16
2018-12-24 16:56:55.895809 OK TPT HASH-GROUP-SIZE 128
2018-12-24 16:56:55.899127 OK no VERY_BASIC_EVAL
2018-12-24 16:56:55.902218 OK REQUIRE_ALL_POSSIBLE_MOVES
2018-12-24 16:56:55.909206 OK ASPIRATION_WINDOW_SIZE 75
2018-12-24 16:56:55.913162 OK POLLING_TIMEOUT 250
2018-12-24 16:56:55.916535 OK BOOK_WDL_MIN_HITS 12
2018-12-24 16:56:55.919839 OK no WITH_MYSQL_BOOKS
2018-12-24 16:56:55.922935 OK no W_SYZYGY
2018-12-24 16:56:55.925967 OK no W_SQLITE3
2018-12-24 16:56:55.930523 OK DEFAULT_HASHTABLE_SIZE 256
2018-12-24 16:56:55.934899 OK AVERAGE_MOVELIST_SIZE 31
2018-12-24 16:56:55.938218 OK SE_MIN_PROBE_DEPTH 0
2018-12-24 16:56:55.941380 OK no USE_MMAP
2018-12-24 16:56:55.945003 OK IT_DEEPENING_MAX_REPEAT_MOVE_SEL 32
2018-12-24 16:56:55.948423 OK MMAP_1GB_THRESHOLD 939524096
2018-12-24 16:56:55.951676 OK WITH_LMR
2018-12-24 16:56:55.954771 OK LATE_MOVE_RED_AFTER_N_MOVES_1 1
2018-12-24 16:56:55.957824 OK LATE_MOVE_RED_AFTER_N_MOVES_2 4
2018-12-24 16:56:55.961311 OK Move size: 8
2018-12-24 16:56:55.965961 OK ChessPieceState size: 20
2018-12-24 16:56:55.970146 OK BoardState size: 40
2018-12-24 16:56:55.973551 OK SceneState size: 336
2018-12-24 16:56:55.976944 OK Rev Board $Revision: 4635 $
2018-12-24 16:56:55.981120 OK Rev Brain $Revision: 4923 $
2018-12-24 16:56:55.984506 OK Rev IO_UCI $Revision: 4914 $
2018-12-24 16:56:55.987794 OK Rev MoveSort $Revision: 4748 $
2018-12-24 16:56:55.990995 OK Rev Scene $Revision: 4694 $
2018-12-24 16:56:55.994571 OK Rev Tpt $Revision: 4915 $
2018-12-24 16:56:55.998559 OK Initial move list size: 32, size of Move-structure: 8, total: 256
2018-12-24 16:56:56.001963 OK Hash size: 256MB
2018-12-24 16:56:56.124441 OK initial move list size: 32
2018-12-24 16:56:59.169074 OK IN: exit
2018-12-24 16:56:59.173247 OK Terminating

[Sven]

The situation is this: I can use a command line switch '-l' with a file name. If the file name is nul or nul.log, the file is written but cannot be deleted. If the file name is left empty it creates a trace.log file which can be deleted. If I use some other file name it can be deleted too.
It seems only the name 'nul' causes trouble. Not a big trouble of course, it does no harm to anything, it is just there.

"nul" is a reserved name under Windows. You should be able to delete files named "nul" with a trick that is shown here.

[Gabor Szots]

"nul" is a reserved name under Windows. You should be able to delete files named "nul" with a trick that is shown here.

That worked great, Sven! Now I may include Jumbo in one of my upcoming tournaments...

Cheers,

[flok]

Gabor,

Do you require a special release that emits no logging at all?
I just realised it is not much work for me to create such a version so let me know if...

[Gabor Szots]

Gabor,

Do you require a special release that emits no logging at all?
I just realised it is not much work for me to create such a version so let me know if...

It depends upon how big that trace.log can grow in time. Until it is only a couple of MB's it does not cause problems. Maybe best is if you can make it an uci option.
I don't know how others see it.