Repository navigation
fastchess-gui v0.6.1
Engines that run on another machine, played from this computer: a GPU engine on the GPU box, an engine built for
another system, a machine kept for one engine, read, checked and played over SSH as an engine of this computer.
Engines on a machine
- An engine's card gets Runs on: this computer, or a machine of Settings > Machines. Its program and working folder
are then paths there, typed, or chosen in a browser of the machine's files (over SFTP). Add… offers A program on
<machine>…, Import… every engine of a folder there, and the machine's Add an engine… a program there. - No OpenSSH client is needed, Windows included: the program's own SSH connection, with the machine's key or agent,
carries up to ten engines, each started through a relay (fastchess-gui --remote-engine). A machine whose host key
was not shown and trusted by Test the connection is never connected to. - The engine is read, checked, played in the console, the quick test, the analysis and tournaments as an engine of
this computer. Its program's SHA-256 there tells when it was rebuilt, as for a local one. Check measures the round
trip to the machine. - The new tournament summary says where each engine plays, warns when the round trip takes more than 5 % of the
increment (or of the time a move has without one) with Set a margin of … ms, and refuses a machine never tested,
or a tournament that runs on another machine. A tournament that runs on the engine's machine plays it there as its
own engine. - A key's passphrase is asked once a session, before the first read or the start, and handed to the tournament's
process, which keeps playing when the window closes. - Long runs: a machine that does not answer is one entry of Needs action, its engines' games set aside and tried
again while the others go on; a game lost because the connection broke is voided and played again, and Health
counts it apart, not as the engine's crash; a machine cut off more than three times in an hour has its engines set
aside. The home page shows each machine under the cores, connected or since when it does not answer. - This computer's cores, memory and GPUs no longer count the engines that run elsewhere, only their relays.
Other changes
- The archives carry md4c's MIT notice (the guide's Markdown parser), missing from 0.6.0.
- An engine renamed in the library is renamed in the machines' lists of engines too.
Downloads
| File | Contents |
|---|---|
fastchess-gui-v0.6.1-linux-x86_64.tar.gz |
fastchess-gui, x86-64 Linux (glibc 2.35 or newer). Needs X11 or Wayland. |
fastchess-gui-v0.6.1-windows-x86_64.zip |
fastchess-gui.exe, 64-bit Windows 10 version 1903 or newer. No installer, nothing else to install. |
fastchess-gui-v0.6.1-macos-universal.zip |
fastchess-gui.app and the fastchess command line tool, macOS 13.3 or newer, Apple silicon and Intel. Not signed: Control-click it and choose Open the first time. |
SHA256SUMS.txt |
Checksums of the three archives. |
The binaries are built by this repository's GitHub Actions workflow; the tests run on Linux, Windows and macOS. The
archives carry the licenses of the libraries built in, and of the piece sets (see ATTRIBUTION.md).
Known limitations
They are tracked as issues labelled known limitation.