Bug 494243 - Engine configuration is unimplemented
Summary: Engine configuration is unimplemented
Status: REPORTED
Alias: None
Product: knights
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.6.240780
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Alexander Semke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-07 14:23 UTC by a
Modified: 2024-10-13 16:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description a 2024-10-07 14:23:52 UTC 
Almost all chess engines nowadays come with various options to configure them, from being able to use more cores, using more memory or less memory. 

It would be nice to be able to be able to configure these options, as I believe KNights currently runs all engines on default settings
Comment 1 Alexander Semke 2024-10-13 16:14:16 UTC 
(In reply to a from comment #0)
> Almost all chess engines nowadays come with various options to configure
> them, from being able to use more cores, using more memory or less memory. 
> 
> It would be nice to be able to be able to configure these options, as I
> believe KNights currently runs all engines on default settings
I planned to implement as next the support for uci_limitstrength and uci_elo parameters to better control the strength of UCI engines. Do we really need to expose such technical and internal things like the number of threads, etc. via some engine specific settings (there are hundreds of engines out there...) or is it enough just to limit the strength of the engine in a common way as defined by the protocol?