Not logged inRybka Chess Community Forum
Up Topic Rybka Support & Discussion / Aquarium / RTHomeServer.ini file
- - By cma6 (****) Date 2020-08-07 16:35
A great deal has changed in SF builds since we got the old RTHomeServer.ini file with very old SF parameters. Is there a way to update RTHomeServer.ini to accommodate today's SF-NNUE devel builds?
My RTHomeServer files date from 2014. My RTHomeServer.ini files looks like this:

[main]
port=5013
allow_anyone=1

[Settings]
Autoscroll=1
Log Level=1

[pipe]
; Settings for how the server interacts with SF engine
latency=1
skip_lvl=0
; 0 - skip none
; 1 - skip minor
; 2 - skip most
priority=1
; 0 - low
; 1 - normal
affinity_mode=0
;0 - do not control affinity
;1 - set only to physical cores
;2 - set only to virtual cores
;3 - set first to physical, then to virtual cores
aff_recheck=0
;interval of automated affinity check - in seconds; 0 - disabled
aff_readyok_time=5
;interval of affinity setup after 'readyok' command; 0 - no interval

[server_default]
engine=SF5.exe
option_filter=1
; 0 - allow only options from 'client' section
; 1 - allow all options except 'client' section
; 2 - allow all options
uci_from_file=0
; 0 - uci command is sent to engine
; 1 - response to uci command is read from .uci-file
allowed_commands=post*,take*,#*
; * works as any number of any sumbols
; # works as any digit
; * allowed only as last symbol (temporary, for algorithm boost)

[client]

[engine]

[servers]
1=0
[1]
engine=SF5.exe
type=1

[1_engine]
; The remote engine settings
Hash=1024
Threads=1
Contempt=0
MultiPV=1
Move Overhead=30

[1_client]
; The engine parameters. Interpretation depends on option_filter
Write Debug Log=
Contempt=
Threads=
Hash=
Clear Hash=
Ponder=
MultiPV=
Skill Level=
Move Overhead=
Minimum Thinking Time=
Slow Mover=
nodestime=
UCI_Chess960=
SyzygyPath=e:\tb6
SyzygyProbeDepth=
Syzygy50MoveRule=
SyzygyProbeLimit=

[Form]
Left=105
Top=263
Width=571
Height=418
WindowState=0

In particular, we need updates on the Engine parameters section.
Parent - By centipawn (*) Date 2020-08-08 05:36
I haven't tried this, but I would assume that anything in the [1_client] section simply gets passed as UCI parameter to the engine and that therefore simply adding the new parameters there would do the trick.
Parent - - By Dadi Jonsson (Silver) Date 2020-08-08 08:09 Edited 2020-08-08 08:14 Upvotes 1
Here is an example based on the latest Stockfish version (assuming you want to use NNUE). I've added some comments on top of those that come with the standard RTHomeServer.ini. The highlighted lines are those that you may need to modify. In particular, make sure that you use a different port number for each remote engine (on the same server). Otherwise bad things will happen :eek:

When you get a new version of the engine with different UCI parameters, then run it in command line mode to get a list of all the parameters (using the UCI command) and update this file accordingly.

--------------------------------------

; Stockfish NNUE ini-file for RTHomeServer version 1.3.0.42
[main]
; Specify the port to be used for the remote engine. It's vital that no two engines use the same port on the same server
port=7817
allow_anyone=1

[Settings]
Autoscroll=1
Log Level=2

[pipe]
; Settings for how the server interacts with the engine
latency=1
skip_lvl=0
; 0 - skip none
; 1 - skip minor
; 2 - skip most
priority=1
; 0 - low
; 1 - normal
affinity_mode=0
;0 - do not control affinity
;1 - set only to physical cores
;2 - set only to virtual cores
;3 - set first to physical, then to virtual cores
aff_recheck=0
;interval of automated affinity check - in seconds; 0 - disabled
aff_readyok_time=5
;interval of affinity setup after 'readyok' command; 0 - no interval

[server_default]
engine=
option_filter=1
; 0 - allow only options from 'client' section
; 1 - allow all options except 'client' section
; 2 - allow all options
speed=2000
uci_from_file=0
; 0 - uci command is sent to engine
; 1 - response to uci command is read from .uci-file
allowed_commands=post*,take*,#*
; * works as any number of any sumbols
; # works as any digit
; * allowed only as last symbol (temporary, for algorithm boost)

[client]

[engine]

[servers]
1=0
[1]
; The path to the remote chess engine
engine=..\stockfish.exe
type=1

[1_engine]
; The remote engine settings. Only specify the value of UCI parameters that are different from the default values
Analysis Contempt=Off
Contempt=0
Use NNUE=true
EvalFile=..\nn.bin
Hash=1024
Syzygy50MoveRule=false
SyzygyPath=C:\Syzygy\3-4-5rtbw;C:\Syzygy\6rtbw;C:\Syzygy\3-4-5rtbz;C:\Syzygy\6rtbz
Threads=1


[1_client]
; Since options_filter=1 these parameters cannot be changed by Aquarium (except lines starting with ';')
Analysis Contempt=
;Clear Hash=
Contempt=
Debug Log File=
EvalFile=
Hash=
Move Overhead=
;MultiPV=
nodestime=
Ponder=
Skill Level=
Slow Mover=
Syzygy50MoveRule=
SyzygyPath=
SyzygyProbeDepth=
SyzygyProbeLimit=
Threads=
;UCI_AnalyseMode=
;UCI_Chess960=
UCI_Elo=
UCI_LimitStrength=
UCI_ShowWDL=
Use NNUE=


[Form]
Left=105
Top=263
Width=571
Height=418
WindowState=0
Parent - - By dickie (**) Date 2020-08-08 10:00 Upvotes 1
I preferred to control all the engine personality settings from Aquarium, so I commented out all the engine settings in the RTHomeServer.ini file with a leading ; . I found it easier to update multiple engine instances on the server that way.

However I now use Windows 10 SSH in place of RTHomeServer. It requires just one copy of the engine on the server and one personality setting in Aquarium to run as many instances as I have threads on the server. Updating the server engine has become straightforward.
Parent - By cma6 (****) Date 2020-08-08 17:26 Edited 2020-08-08 21:15
dickie, this looks like a useful idea. With 4 slave systems, it is a great deal of work to constantly update engines and nets on slave systems. I will read up a bit on Win 10 SSH and see if I can then ask you how to replace RTHomeserver with a Win10 SSH implementation.

" to run as many instances as I have threads on the server."
This seems to imply that you are not using the cores on your slave systems to run Aqr?!
Parent - By cma6 (****) Date 2020-08-08 17:24
Thanks to Dadi for an extremely useful updating of RTHomeserver.ini parameters. I have never understood the purpose of the [1_client] section of the .ini file, since one is already specifying engine parameters in the [1_engine] section; and the unspecified parameters would be default SF settings.

; Since options_filter=1 these parameters cannot be changed by Aquarium (except lines starting with ';')
Up Topic Rybka Support & Discussion / Aquarium / RTHomeServer.ini file

Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill