You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,17 @@ A sample content for stockfish in Linux would be:
95
95
}
96
96
```
97
97
98
+
An example for `lc0` (Leela Chess Zero) with CUDA backend:
99
+
100
+
```json
101
+
"name": "lc0",
102
+
"path": "/home/user/lc0/build/release/lc0",
103
+
"engine_params": ["--backend=cuda"],
104
+
"active": true
105
+
```
106
+
107
+
Note: The field "engine_params" is optional and can contain a list of additional parameters for the engine that are given on start.
108
+
98
109
Note: Windows users need to use paths with `\\` or `/` for proper json encoding.
99
110
100
111
### Start
@@ -142,7 +153,7 @@ Do NOT use `sudo` on subsequent starts, or the communication might fail. If scan
142
153
143
154
All engine descriptions in directory 'engines' will now contain the default-UCI options for each engine. Those can be edited e.g. to enable tablebases or other UCI options.
|`name`| e.g. `"stockfish"`| Name of executable of the engine, e.g. `stockfish`. Unfortunately this name must be precisely equal to the name of the json file, and must be referenced in `preferences.json` as either `computer_player_name` or `computer_player2_name` and within `active_agents`. That is subject to improvement in the future. |
217
228
|`path`| e.g. `"/usr/local/bin/stockfish"`| Path to the engine executable. Windows users must either use `\\` or `/` in json files as path separators. |
229
+
|`engine_params`|`["--backend=cuda"]`| Optional list of additional parameters for the engine that are given on start. This entry should be ommited, if no parameter are necessary. |
218
230
|`active`|`true`|`mchess.py` currently uses only the first two active engines. If more engines are configured, the unused ones should be set to `false`|
219
231
220
232
Once the UCI engine is started for the first time, the UCI-options of the engine are enumerated and added to the `<engine-name>.json` config file. That allows further customization of each engine. Some commonly used options are:
0 commit comments